SAP SYBASE IQ Diagnostics and Hang Analysis


 
IQ Diagnostics and Analysis for Hung Server

 
1)      Symptoms

Some of the symptoms, that could lead you (or users) to think that IQ server is hung are :

- No new connections can be made to the server either from the same host machine or different host machine over TCP/IP network.

- No tasks seems to be working and there is no new messages seen in the IQ server log (.iqmsg file), if no existing connections doing work.

- The messages appear to be sparse in .iqmsg file, no task how-ever simple, does appear to get completed in a timely manner.

- Catalog .db and .log time not getting updated on any IQ nodes.

- Hardware bottleneck – IO stuck

 
2)      IQ Diagnostics checklist

Collect and analyzethe following diagnostic information for all IQ problems and/or symptoms

- Know clear problem description and/or exact error message.

- Has anything changed recently on IQ or the OS?

- It is useful to know details like timing of the problem/symptom, duration of the symptom, whether there are any recent changes in the environment.

 
3) DIAGNOSTICS DATA NEEDED TO ANALYZE THE SYMPTOMS

- Analyze the IQ log files - IQMSG.log, IQSRV.log, STDERR.log

- Analyze the Operating System (OS) information: version, patch level, Total memory , and number of CPUs/cores - DSTAT o/p, NMON o/p

- Analyze the OS error logs - /var/log/messages from affected node

- Know if any other tool involved in the problem

- Get Minimum 3 pstack/procstack taken for IQ server PID, 2 to 3 minute apart

- From Coordinator check:

            -- sp_iqmpxinfo

-- sp_iqcontext

            -- sp_iqconnection

            -- sp_iqtransaction

            -- sp_iqstatus

            -- sp_iqversionuse

            -- copy of the IQ cfg file

Comments

Post a Comment

Popular posts from this blog

Enable and Disable Trace in SAP Sybase IQ database Enable Trace in IQ DB   1.   Check the table meta info in dbisql:     sp_iqobjectinfo [owner],[table_name];   2.   Enable SQL or Query Plan generator – On the load target IQ server – run these commands with DBA: create a temp folder to save trace and logs:     mkdir /tmp/log_iqload   SQL Trace: in dbisql:     call sa_server_option('request_level_logging', 'SQL');     call sa_server_option('request_level_log_file','/tmp/log_iqload/sqltrace.log');   Query plan: in dbisql:     set option query_plan='on';     set option query_detail='on';     set option query_plan_as_html = 'on';     set option dml_options10='on';     set option query_plan_after_run='on';     set option query_name ='load_plan';     set option query_plan_text_caching='on'     set option query_plan_as_html_dire
Read more
How to find Invalid views on SAP Sybase IQ database This section shows list of invalid view in IQ (SQL: “select U.user_name , T.table_name as object_name from sysobject O, systab T, sysuser U where T.object_id=O.object_id and U.user_id=T.creator and O.status=2 ”). select U . user_name + '.' + T . table_name from sysobject O , systab T , sysuser U where T . object_id = O . object_id and U . user_id = T . creator and O . status = 2 /* Invalid */ and O . object_type = 2 /* views */   SYSOBJECT status TINYINT The status of the object. Values include: 1 (valid) - The object is available for use by the database server. This status is synonymous with ENABLED. That is, if you ENABLE an object, the status changes to VALID. 2 (invalid) - An attempt to recompile the object after an internal operation has failed, for example, after a schema-altering modification to an object on which it depen
Read more
SAP SYBASE IQ Index Advisor sp_iqindexadvice Procedure Displays stored index advice messages. Optionally clears advice storage. SQL> select * from sa_conn_options() where OptionName like '%Index_Adv%' and number=connection_property ('Number') Enable Index Advisor in IQ DB   Option1: 1.       SET OPTION index_advisor = 'ON'; 2.       SET OPTION index_advisor_max_rows = 100; 3.       commit; 4.       <query to be analyzed>; 5.       call sp_iqindexadvice ();   Option2: 1.       set temporary option INDEX_ADVISOR = on; 2.       set temporary option INDEX_ADVISOR_MAX_ROWS = 20; 3.       commit; 4.       -- sql statements 5.       call sp_iqindexadvice (); The above code does two things for you- 1. It tells you that your option are set correctly. 2. If table structure is not optimal relative to query, the advisor should give some advice.
Read more