Troubleshooting › Diagnose DB2 Problems

Diagnose DB2 Problems

This section describes problems that you may encounter with DB2.

Database Connection Cannot Be Established

If the following message appears in the ReportCenter Java Task log:

Cannot establish database connection. Message: DB2SQLJConnection error in native method: constructor: 
RRS "IDENTIFY" failed using DB2 system:D…

Proceed as follows, according to the REASON code:

• If the REASON code is 00f30012, verify that the DB2 subsystem has started.
• If the REASON code is 00f30049, verify that the statements in the supplied CC2DSAMP(WRBD2GRA) member have run.
• If the REASON code is 00f30091, verify that RRS/MVS has started.

Note: If RRS is recycled, you must recycle DB2; therefore, you must recycle the ReportCenter Java Task when your DB2 subsystem is recycled.

Database Connection Cannot Be Established-No Suitable SQLJ/JDBC Driver

If the following message appears in the ReportCenter Java Task log, ensure that you have implemented the REPORTCENTER parameter group in the ReportCenter control region correctly.

Cannot establish database connection. Message: No suitable driver…

Ensure that the REPORTCENTER parameter group is completed correctly in terms of the HFS path for DB2 JDBC classes and the DB2 subsystem location name, for example:

 REPORTCENTER - ReportCenter Control Region 
                                                                             
 DB2 Database and JDBC information: (Get these values from your DB2 DBA)     
                                                                             
      JDBC Driver Name .............. ibm.sql.DB2Driver                      
                                                                             
      JDBC Class File (eg. /usr/lpp/db2/db2710/classes/db2j2classes.zip )    
          /sys/usr/lpp/db2/db2710/classes/db2j2classes.zip                   
                                                                             
      JDBC DLL Directory (eg. /usr/lpp/db2/db2710/lib )                      
          /sys/usr/lpp/db2/db2710/lib                                        
                                                                             
      JDBC Properties File                                                   
        (eg. /usr/lpp/db2/db2710/classes/db2sqljjdbc.properties )            
          /sys/usr/lpp/db2/db2710/classes/db2sqljjdbc.properties             
                                                                             

This information should carry through to the last five lines of the Adaptor.ini file as follows:

For the Legacy Driver

WebReportsDB2JDBC.driver=ibm.sql.DB2Driver
WebReportsDB2JDBC.url=jdbc:db2os390:
WebReportsDB2JDBC.SQLType=DB2

For the Universal Driver using Type 2 Connectivity

WebReports.driver=com.ibm.db2.jcc.DB2Driver
WebReports.url=jdbc:db2:Db2LocationName
WebReports.SQLType=DB2

For the Universal Driver using Type 4 Connectivity

WebReports.driver=com.ibm.db2.jcc.DB2Driver
WebReports.url=jdbc:db2://Ipaddress:port/Db2LocationName
WebReports.user=user
WebReports.password=password
WebReports.SQLType=DB2

Database Information Cannot Be Retrieved

If the following message appears in the ReportCenter Java Task log, ensure that you have run the statements in the supplied CC2DSAMP(WRBD2GRA) member.

Cannot get database information: DB2JDBCCursor Received Error in Method prepare:SQLCODE==> -551
SQLSTATE ==> 42501 Error Tokens ==> <<DB2 6.1 ANSI SQLJ-0/JDBC 1.0>> jsname SELECT SYSIBM.SYSxxxxxx     com.ca.syd.utils.datawarehouse.ExpiryService.009

Key Range Does Not Exist

This is indicated by the following message in the ReportCenter Java Task log:

Key range for table database-table-name does not exist

Check the following:

• In the db2sqljjdbc.properties file, check that your DB2 subsystem name is specified correctly.

  If you find a problem, correct the file, and then rerun the db2genJDBC utility and the DSNTJJCL job to recreate and rebind the DBRMs.

• Check the output of the WRDB2CRE job to ensure that no errors were encountered, and that all table spaces, tables, and indexes are created correctly.
• The DB2 subsystem that contains your ReportCenter databases has been brought down while you have been collecting data. Restart the ReportCenter Java Task so that new database connections can be obtained.