IBM Support

MustGather: Navigator Database Component Issues

Troubleshooting


Problem

This document outlines what to collect for Navigator issues with the database component
Caution: This document will request a DBMON trace.  DBMON traces can negatively impact system performance. If possible, narrow the scope of the issue and start the DBMON shortly before the issue is seen and over specific or generic job names instead of using JOB(*ALL).  For further detail on the impact of taking a DBMON trace refer to the following document: https://www.ibm.com/node/882914

Resolving The Problem

For issues concerning Navigator problems with the database component., this document includes the recommended data collection for debug. This is by no means all inclusive; however, it is meant as a starting point for document collection.

Database component of System i Navigator issues specific MustGather information

If you encounter a Database component of Navigator issue, collect the following information as it is related to the issue:

 
PTF and General Information

1. Version, release, and modification level of system (for example, V5R4M5, V6R1M0, and so on).

2. Issue WRKPTFGRP and press Enter; then press F6 to print a spooled file.

3. Issue DSPPTF OUTPUT(*PRINT)

4. Version of System i Access and the service pack level. To collect this information, refer to document 8N1016053, Checking Access for Windows installed Release and Service Pack Level.

5. Document the steps to re-create the problem. Screen captures are very helpful to accompany this, to reduce the confusion on which menu option/dialog the error is occurring on.

6. The joblog for the host server job. If there is an error coming up in Navigator, get the error up on the screen, do a WRKOBJLCK on the user profile signed in with, and get the i5/OS command server job (QZRCSRVS), and/or the i5/OS Database Host Server (QZDASOINIT). showing the error.

To spool the joblog: DSPJOBLOG JOB(NUMBER/QUSER/JOBNAME) OUTPUT(*PRINT)

7. Database performance monitor. In cases where Visual Explain or Show Statements shows incorrect output, we want the user's performance monitor file saved and sent in. If the error is from an SQL Plan Cache Snapshot or Event Monitor, you should send that in. If the problem is with a particular statement within the SQL Plan Cache, you should create a SQL Plan Cache Snapshot and send that in.

 
Data Collection

Depending upon the Navigator interface being used, the following should also be collected

IBM Navigator for i (web interface):

1. Click on Settings and Console Logging and Tracing





2. Confirm the following setting is listed:

3. Restart the server if a setting was changed in step 2 by doing the following 2 steps:

A. ENDTCPSVR SERVER(*HTTP) HTTPSVR(*ADMIN)
B. STRTCPSVR SERVER(*HTTP) HTTPSVR(*ADMIN)

4. Recreate the issue

5. Collect the messages.log and console.log files from:

'/QIBM/UserData/OS/OSGi/LWISysInst/admin2/lwi/logs/'

OR

'/QIBM/UserData/OS/AdminInst/admin2/wlp/usr/servers/admin2/logs '

Note: If you do not see the log files contact the support rep or send all files in these directories.

6. Collect the log file error_log.QXYYMMDDXX where YY is the year, MM the month, and DD the day when the log was created at:

'/QIBM/UserData/HTTPA/LWI/logs/' path

** Files from step 5 and 6 needs to be sent to IBM. **


ACS issues:

Collect the data from DCF doc :
http://www.ibm.com/support/docview.wss?uid=nas8N1010627
Direction for transferring files to IBM

Refer to DCF doc - MustGather: Instructions for Sending Data to IBM i Support - http://www.ibm.com/support/docview.wss?uid=nas8N1019224

 

[{"Business Unit":{"code":"BU058","label":"IBM Infrastructure w\/TPS"},"Product":{"code":"SWG60","label":"IBM i"},"Component":"Db2 for i","Platform":[],"Version":"All Versions","Edition":"","Line of Business":{"code":"LOB57","label":"Power"}}]

Historical Number

566197467

Document Information

Modified date:
26 December 2019

UID

nas8N1012152