Troubleshooting
Problem
Attempts to log in to Rational Asset Analyzer for System z (RAAz) result in the browser interface displaying message "DMH7775E: Cannot verify that the database schema tables have been fully and correctly defined."
Symptom
Validation of the RAAz schema level attribute (SYS_ATTR_ID=500) in table DMH_SYSTEM_ATTR fails.
Upon inspection of the WsaaWar log, an SQLCODE=-471, SQLSTATE=55023 failure is reported when trying to get access to the RAAz database. This is highlighted by messages in the log similar to the following, specifically referencing a stored procedure failure for DatabaseMetaData and SYSIBM.SQL*:
...
2017/07/26 09:56:11:546 WsaaWar INFO: Detected DBMS vendor=IBM product=DB2_ZOS version=##.#
2017/07/26 09:56:11:591 WsaaWar WARNING: Access to database using method DATASOURCE failed: com.ibm.db2.jcc.am.SqlException,DB2 SQL Error: SQLCODE=-471, SQLSTATE=55023, SQLERRMC=SYSIBM.SQLCOLUMNS;00E7900C, DRIVER=3.68.76
2017/07/26 09:56:11:592¨ WsaaWar FINE: DB2 SQL Error: SQLCODE=-471, SQLSTATE=55023, SQLERRMC=SYSIBM.SQLCOLUMNS;00E7900C, DRIVER=3.68.76
com.ibm.db2.jcc.am.SqlException: DB2 SQL Error: SQLCODE=-471, SQLSTATE=55023, SQLERRMC=SYSIBM.SQLCOLUMNS;00E7900C, DRIVER=3.68.76
at com.ibm.db2.jcc.am.gd.a(Unknown Source)
at com.ibm.db2.jcc.am.gd.a(Unknown Source)
at com.ibm.db2.jcc.am.gd.a(Unknown Source)
at com.ibm.db2.jcc.am.uo.b(Unknown Source)
at com.ibm.db2.jcc.am.uo.c(Unknown Source)
at com.ibm.db2.jcc.t4.bb.l(Unknown Source)
at com.ibm.db2.jcc.t4.bb.f(Unknown Source)
at com.ibm.db2.jcc.t4.p.e(Unknown Source)
at com.ibm.db2.jcc.t4.vb.k(Unknown Source)
at com.ibm.db2.jcc.am.uo.lb(Unknown Source)
at com.ibm.db2.jcc.am.vo.b(Unknown Source)
at com.ibm.db2.jcc.am.CallableStatement.hc(Unknown Source)
at com.ibm.db2.jcc.am.CallableStatement.executeQuery(Unknown Source)
at com.ibm.db2.jcc.am.DatabaseMetaData.executeCatalogQuery(Unknown Source)
at com.ibm.db2.jcc.am.DatabaseMetaData.getColumnsX(Unknown Source)
at com.ibm.db2.jcc.am.DatabaseMetaData.getColumns(Unknown Source)
at com.ibm.ws.rsadapter.jdbc.WSJdbcDatabaseMetaData.getColumns(WSJdbcDatabaseMetaData.java:504)
at com.ibm.dmh.db.DbMetaData.buildProperSqlForSelectTriggers(DbMetaData.java:391)
at com.ibm.dmh.db.DbMetaData.getMetaDataForTriggers(DbMetaData.java:417)
at com.ibm.dmh.db.DbMetaData.<init>(DbMetaData.java:54)
at com.ibm.dmh.db.DbAdmin.initializeDatasource(DbAdmin.java:136)
at com.ibm.dmh.db.DbAdmin.initializeConnection(DbAdmin.java:187)
at com.ibm.dmh.db.DbAdmin.initialize(DbAdmin.java:163)
at com.ibm.dmh.CommonInitializer.init(CommonInitializer.java:148)
at com.ibm.dmh.CommonInitializer.init(CommonInitializer.java:57)
...
Cause
During start up, RAAz goes through a number of validation steps, including listing the database tables and columns. This task is accomplished via JDBC using a stored procedure. When DB2 tried to use the stored procedure, it encountered a problem.
Resolving The Problem
Refer to the DB2 for z/OS documentation for the particular reason code and corresponding Programmer response. For example:
00E79002: https://www.ibm.com/support/knowledgecenter/en/SSEPEK_11.0.0/codes/src/tpc/00e79002.html
Note: The installation-defined time limit expired.
00E7900C: https://www.ibm.com/support/knowledgecenter/en/SSEPEK_11.0.0/codes/src/tpc/00e7900c.html
Note: The WLM application environment name specified for the user-written routine is not defined or is currently not available for use in the active WLM policy. You should verify the WLM application environment name to understand which WLM is intended for use. For example, refer to job DSNTIJMS (in data set <db2hlq>.SDSNSAMP) to identify the WLM that was specified during setup.
Once corrective action has taken place, restart the application server and verify resolution has occurred.
Product Synonym
raaz
Was this topic helpful?
Document Information
Modified date:
02 August 2018
UID
swg22008278