Error message displayed when you configure Registry Services after applying a database fix pack

Technote (troubleshooting)


Problem(Abstract)

When you install a DB2 fix pack on the environment where Registry Services is installed, you must configure some required DB2 settings before you can set Registry Services configurations.

Symptom

After you apply a DB2 fix pack to your environment, you must configure some required DB2 settings. These settings are required for you to configure any other settings that might be required for Registry Services daily operations.

For example, if you run a Registry Services query operation, and this query returns more than 500 records, you must set the maxPageSize parameter. You use the config CLI command to set this parameter to a number higher than 500 and ensure that your query returns all the records that you are searching.

In this scenario, if you do not apply the required DB2 settings before you run the config CLI command, you get this error message:

Feb 20, 2013 4:29:19 AM com.ibm.frs.cli.DisCli main
INFO: CTJFO0019I Build version is 1.1.0.201302111648.
Feb 20, 2013 4:29:20 AM com.ibm.frs.cli.DisCli doIt
SEVERE: CTJFO0008E The Registry Services CLI command has failed due to an internal error. The specific error message is: DB2 SQL Error: SQLCODE=-443, SQLSTATE=38553, SQLERRMC=SYSIBM.SQLCOLUMNS;COLUMNS;SYSIBM:CLI:-805, DRIVER=3.63.123
Throwable occurred: <openjpa-2.2.0-r422266:1244990 nonfatal general error> org.apache.openjpa.persistence.PersistenceException: DB2 SQL Error: SQLCODE=-443, SQLSTATE=38553, SQLERRMC=SYSIBM.SQLCOLUMNS;COLUMNS;SYSIBM:CLI:-805, DRIVER=3.63.123
at org.apache.openjpa.jdbc.meta.MappingTool.record(MappingTool.java:559)
at org.apache.openjpa.jdbc.meta.MappingTool.record(MappingTool.java:455)
at org.apache.openjpa.jdbc.kernel.JDBCBrokerFactory.synchronizeMappings(JDBCBrokerFactory.java:160)
at org.apache.openjpa.jdbc.kernel.JDBCBrokerFactory.synchronizeMappings(JDBCBrokerFactory.java:164)
at org.apache.openjpa.jdbc.kernel.JDBCBrokerFactory.newBrokerImpl(JDBCBrokerFactory.java:122)
at org.apache.openjpa.kernel.AbstractBrokerFactory.newBroker(AbstractBrokerFactory.java:209)
at org.apache.openjpa.kernel.DelegatingBrokerFactory.newBroker(DelegatingBrokerFactory.java:156)
at org.apache.openjpa.persistence.EntityManagerFactoryImpl.createEntityManager(EntityManagerFactoryImpl.java:227)
at org.apache.openjpa.persistence.EntityManagerFactoryImpl.createEntityManager(EntityManagerFactoryImpl.java:154)
at org.apache.openjpa.persistence.EntityManagerFactoryImpl.createEntityManager(EntityManagerFactoryImpl.java:60)
at com.ibm.frs.persistence.PersistenceMgr.createEntityManager(PersistenceMgr.java:158)
at com.ibm.frs.persistence.PersistenceMgr.getEntityManager(PersistenceMgr.java:167)
at com.ibm.frs.persistence.config.ConfigurationManager.addConfigItem(ConfigurationManager.java:108)
at com.ibm.frs.config.cli.ConfigCli.executeSetProperty(ConfigCli.java:497)
at com.ibm.frs.config.cli.ConfigCli.run(ConfigCli.java:237)
at com.ibm.frs.cli.DisCli.doIt(DisCli.java:185)
at com.ibm.frs.cli.DisCli.main(DisCli.java:85)
Caused by: com.ibm.db2.jcc.am.SqlException: DB2 SQL Error: SQLCODE=-443, SQLSTATE=38553, SQLERRMC=SYSIBM.SQLCOLUMNS;COLUMNS;SYSIBM:CLI:-805, DRIVER=3.63.123
at com.ibm.db2.jcc.am.fd.a(fd.java:682)
at com.ibm.db2.jcc.am.fd.a(fd.java:60)
at com.ibm.db2.jcc.am.fd.a(fd.java:127)
at com.ibm.db2.jcc.am.ho.b(ho.java:2317)
at com.ibm.db2.jcc.am.ho.c(ho.java:2300)
at com.ibm.db2.jcc.t4.cb.l(cb.java:370)
at com.ibm.db2.jcc.t4.cb.f(cb.java:98)
at com.ibm.db2.jcc.t4.q.e(q.java:81)
at com.ibm.db2.jcc.t4.sb.k(sb.java:160)
at com.ibm.db2.jcc.am.ho.jb(ho.java:2266)
at com.ibm.db2.jcc.am.io.b(io.java:4319)
at com.ibm.db2.jcc.am.CallableStatement.cc(CallableStatement.java:144)
at com.ibm.db2.jcc.am.kc.a(kc.java:7810)
at com.ibm.db2.jcc.am.kc.b(kc.java:6705)
at com.ibm.db2.jcc.am.kc.getColumns(kc.java:6635)
at org.apache.commons.dbcp.DelegatingDatabaseMetaData.getColumns(DelegatingDatabaseMetaData.java:218)
at org.apache.openjpa.lib.jdbc.DelegatingDatabaseMetaData.getColumns(DelegatingDatabaseMetaData.java:122)
at org.apache.openjpa.lib.jdbc.LoggingConnectionDecorator$LoggingConnection$LoggingDatabaseMetaData.getColumns(LoggingConnectionDecorator.java:743)
at org.apache.openjpa.lib.jdbc.DelegatingDatabaseMetaData.getColumns(DelegatingDatabaseMetaData.java:122)
at org.apache.openjpa.jdbc.sql.DBDictionary.getColumns(DBDictionary.java:4110)
at org.apache.openjpa.jdbc.schema.SchemaGenerator.generateTables(SchemaGenerator.java:524)
at org.apache.openjpa.jdbc.schema.SchemaGenerator.generateSchema(SchemaGenerator.java:364)
at org.apache.openjpa.jdbc.schema.SchemaGenerator.generateSchemas(SchemaGenerator.java:300)
at org.apache.openjpa.jdbc.schema.SchemaTool.getDBSchemaGroup(SchemaTool.java:1166)
at org.apache.openjpa.jdbc.schema.SchemaTool.add(SchemaTool.java:366)
at org.apache.openjpa.jdbc.schema.SchemaTool.run(SchemaTool.java:343)
at org.apache.openjpa.jdbc.meta.MappingTool.record(MappingTool.java:505)
...


Resolving the problem


After you upgrade DB2 to a new fix pack, rebind the bind files to recreate necessary packages in the database.

Related information

OSLC parameters for querying

Rate this page:

(0 users)Average rating

Document information


More support for:

Tivoli Components
Jazz for Service Management

Software version:

1.1, 1.1.0.1

Operating system(s):

AIX, Linux, Windows

Reference #:

1627464

Modified date:

2014-02-20

Translate my page

Machine Translation

Content navigation