Troubleshooting

This Strobe troubleshooting information can help you diagnose some common installation problems.

This section provides information about the following topics:

• Typical Errors
• Strobe Db2 IVP - STRANVER

Typical Errors

Messages received when generating a profile for iStrobe that contains Db2 information and SQL Analysis has been requested.

******STR2968S FATAL ERROR, RC= 72 FROM SQLAF INIT

An attempt to connect to a Db2 subsystem has failed. Typically, this error is due to an invalid Db2 subsystem or the Db2 subsystem is not active on the LPAR that the Strobe Profile job is being executed on. Verify that the SSID from the sample file and 'PF=(SSID=????)' if coded is correct. Also, verify that the Db2 libraries accessed are compatible with the release of Db2 being used and that the LPAR that the profile job is being executed on can access that Db2 subsystem.

******STR2968S FATAL ERROR, RC= 76 FROM SQLAF INIT

An error occurred while attempting to CONNECT to Strobe's Db2 Plan STRANANA. Typically, this error is due to a failure to BIND or GRANT access to STRANANA. Please ensure that installation processes SBDB2INS or SBDB2UPG have been performed for each Db2 subsystem that Strobe will execute on.

******STR2968S FATAL ERROR, RC= 89 FROM SQLAF INIT

An invalid SQLCODE was returned while attempting to access Db2. Typically, this code is returned when DBRM STRDNMOD has not been properly bound. lease ensure that installation processes SBDB2INS or STRBDB2UPG has been executed and that the correct Collection ID has been bound into Strobe's plan STRANANA.

BMC Support may request output from the Db2 IVP, STRANVER (see below).

Strobe Db2 IVP – STRANVER

The installation verification program, STRANVER, creates a report showing which Strobe Db2 load modules are installed, analyzes the Strobe Db2 plan, collection, and packages for the correct DBRMs, and lists the Db2 execute authorizations. Member SQLAFVER in the hlq.SSTRSAMP sample library dataset provides JCL to run STRANVER.

To verify the installation, edit and run SQLAFVER against any Db2 subsystems where Strobe Db2 processing will be used:

1. Edit SQLAFVER as follows:
   1. Change the CNTL value to the name of your PDS that contains the copy of the Strobe sample library dataset.
   2. Change the DB2.LOAD.LIB value to the name of your Db2 load library that contains the DSNTIAR and connection modules.
   3. Change the STRBLIB value to the name of your unauthorized Strobe load library (SSTRLOAD) that contains the Strobe SQL Analysis load modules.
   4. Change the STRBAUT value to the name of your authorized Strobe load library (SSTRAUTH) that contains Strobe load modules.
2. Each time you verify a different Db2 subsystem, change the SSID to the ID of the Db2 subsystem you are targeting for the test.
3. Execute the job and read the SYSPRINT output to make sure the Load Module, Bind, and Grant permissions are correct for the DBRM versions that you are using.
   1. The load module version information should match the DBRM version information.
   2. That version should be bound into the STROBE collection.
   3. The STROBE collection should be bound into Strobe's plan STRANANA.
   4. The plan should have EXECUTE authorization granted to PUBLIC.
   5. The plan should also show that the SQL Agent Authorization ID has been granted TRACE and MONITOR2 authorization.
4. See the following sample SQLAFVER output: