IBM Support

MustGather: Guardium Issues

Troubleshooting


Problem

This document describes the necessary information that needs to be collected to aid in quicker resolution of Guardium issues.
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 Guardium, 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.

Guardium issues specific MustGather information

If you encounter a Guardium issue, collect the following information using either method A or method B as it is related to the issue:
 
Method A - QMGTOOLS

The below steps assume you have the latest version of QMGTOOLS.
To Obtain and Install QMGTOOLS - Refer to TechNote N1011297 or below URL.
http://www.ibm.com/support/docview.wss?uid=nas8N1011297


Configuration information:
1. Issue RUNSQLCMD SQLSTMT('CALL SYSPROC/SYSAUDIT_STATUS()') NAMING(*SYS)

2. Issue CPYF FROMFILE(QSYS2/SYSAUDIT) TOFILE(QTEMP/SYSAUDIT) CRTFILE(*YES)

3. Issue CRTLIB QIBMDATA

4. Issue CRTSAVF QIBMDATA/PMRSAVE

5. Issue SAVOBJ OBJ(SYSAUDSTS SYSAUDIT) LIB(QTEMP) DEV(*SAVF) SAVF(QIBMDATA/PMRSAVE)


**Send in Save file to IBM (this is not sent by QMGTOOLS).**

Trace Collection for Install or if Guardium will not start:

1. Issue STRDBMON OUTFILE(QIBMDATA/DBMON1) JOB(*ALL) TYPE(*DETAIL) INCSYSSQL(*YES)

2. Run the install or try and start STAP. When the failure is seen continue on to step 4.

3. Issue ENDDBMON JOB(*ALL)

4. Issue SAVLIB LIB(QIBMDATA) DEV(*SAVF) SAVF(QIBMDATA/PMRSAVE)

NOTE: Respond with a G to replace the save file if step 7 was from Configuration section

5. Capture joblog of error if possible and send in

6. For install issues also send in IFS file /usr/local/guardium/install_out.txt

** All spool files and save file generated from above steps needs to be sent to IBM (this is not sent by QMGTOOLS). **

Data collection:
1. Issue CHGJOB LOG(4 00 *SECLVL) LOGCLPGM(*YES).

2. Issue ADDLIBLE QMGTOOLS

3. Issue GO MG

3. Take option 6 - Database menu

4. Take option 11 - Guardium

5. Put in full PMR number and specify FTP option.

Use *STDFTP for standard FTP / *BDFTP for Blue Diamond Customers / *NO to not FTP.

NOTE: if *NO is used for FTP then you must manually send data to IBM using the section in Method B below titled Direction for transferring files to IBM if QMGTOOLS was NOT used.

NOTE: Guardium now uses Salesforce cases, not PMRs:



6. Press enter to start and data collection

 
Method B - Manual Collection

PTF information:

1. Version, release, and modification level of system (for example, IBM i 7.2, IBM i 7.3, and so on).

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

3. Issue DSPPTF OUTPUT(*PRINT)

Data Collection:

1. Issue STRSQL

2. Run the following SQL Statement:

SELECT START_USER FROM QSYS2/SYSAUDIT

3. Note the START_USER from step 2 and exit out to a command line

4. Issue DSPUSRPRF USRPRF(user_profile) TYPE(*BASIC) OUTPUT(*PRINT)

NOTE: Replace the user_profile with the profile you noted from step 3.

5. Issue STRSQL

6. Run the following in SQL:

CALL SYSPROC/SYSAUDIT_STATUS()

7. Run the following SQL statement when step 6 completes:

SELECT rtrim(substr(server_job,21,6)) concat '/' concat
rtrim(substr(server_job,11,10)) concat '/' concat
substr(server_job,1,10) from QTEMP/SYSAUDSTS

8. Note the job information freom step 7 and exit out to a command line

9. Issue DSPJOBLOG JOB(NUMBER/USER/JOBNAME) OUTPUT(*PRINT)

NOTE: Replace the job numer/user/jobname with what you found in Step 8

10. Issue DSPJOB JOB(NUMBER/USER/JOBNAME) OUTPUT(*PRINT)

NOTE: Replace the job numer/user/jobname with what you found in Step 8

11. Issue WRKOBJLCK OBJ(user_profile) OBJTYPE(*USRPRF)

NOTE: Replace user_profile with what you found in Step 3

12. Look for the job named QP0ZSPWT and take option 5 to get fully qualified job

13. DSPJOBLOG JOB(NUMBER/USER/JOBNAME) OUTPUT(*PRINT)

NOTE: Replace the job numer/user/jobname with what you found in Step 11

14. DSPJOB JOB(NUMBER/USER/JOBNAME) OUTPUT(*PRINT)

NOTE: Replace the job numer/user/jobname with what you found in Step 11

15. Issue STRSQL

16. Run the following SQL stateement

CALL SYSPROC/SYSAUDIT_STATUS()

17. Exit out to a command line when step 16 is compelte

18. Issue CPYF FROMFILE(QTEMP/SYSAUDSTS) TOFILE(*PRINT)

19. Issue CPYF FROMFILE(QSYS2/SYSAUDIT) TOFILE(QTEMP/SYSAUDIT) CRTFILE(*YES)

20. Issue CRTLIB QIBMDATA

21. Issue CRTSAVF QIBMDATA/PMRSAVE

22. Issue SAVOBJ OBJ(SYSAUDSTS SYSAUDIT) LIB(QTEMP) DEV(*SAVF) SAVF(QIBMDATA/PMRSAVE)

23. Issue DSPSECAUD OUTPUT(*PRINT)

Trace Collection for Install or if Guardium will not start:

1. Issue STRDBMON OUTFILE(QIBMDATA/DBMON1) JOB(*ALL) TYPE(*DETAIL) INCSYSSQL(*YES)

2. Run the install or try and start STAP. When the failure is seen continue on to step 4.

3. Issue ENDDBMON JOB(*ALL)

4. Issue SAVLIB LIB(QIBMDATA) DEV(*SAVF) SAVF(QIBMDATA/PMRSAVE)

NOTE: Respond with a G to replace the save file if step 22 was issued above.

5. Capture joblog of error if possible and send in

6. For install issues also send in IFS file /usr/local/guardium/install_out.txt


** All spool files and save file generated from above steps needs to be sent to IBM. **
 
Direction for transferring files to IBM if MGTOOLS was NOT used

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



o In Step 4, you should use cd /toibm/os400

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

Document Information

Modified date:
26 December 2019

UID

nas8N1019889