SAP Knowledge Base Article - Preview

2894304 - SQL20249N The statement was not processed because the package named NULLID.* SQL0595W, SQL0082C, SQLCODE=-20249 - DB6 IBM

Symptom

Following an upgrade of the database or kernel, you encounter the following rebind errors pertaining to some packages in the upgrade logs. 
The Administrative Task Scheduler can also report the following errors. 
In a Java environment, the db2diag.log reports rebind errors, the database is up and running, however the JAVA application cannot start due to "Error while accessing porting layer for DB2_UDB database via getDatabaseName()"
 

The following logs report similar errors. 

  • db2diag.log
     . . .
       YYYY-MM-DD-24.mm.ss.msmsms+### I#######F####        LEVEL: Error
       PID     : ####                 TID : ####           PROC : db2bp.exe
       INSTANCE: DB2<SID>             NODE : 000           DB   : <SID>
       APPID   : *LOCAL.DB2<SID>.############
       HOSTNAME: <hostnm>
       EDUID   : ####
       FUNCTION: DB2 UDB, base sys utilities, sqleUpgradeTS, probe:1485
       DATA #1 : String, 49 bytes
       failed to check if db is enabled for text search.
       DATA #2 : SQLCA, PD_DB2_TYPE_SQLCA, 136 bytes
        sqlcaid : SQLCA     sqlcabc: 136   sqlcode: -20249   sqlerrml: 15
        sqlerrmc: NULLID.SQLE0O07
     

     . . .
       YYYY-MM-DD-24.mm.ss.msmsms+### E#######F### LEVEL: Error
       PID : #### TID : #### PROC : db2bp.exe
       INSTANCE: DB2<SID> NODE : 000 DB : <SID>
       APPID : *LOCAL.DB2<SID>.############
       HOSTNAME: <hostnm>
       EDUID : ####
       FUNCTION: DB2 UDB, Administrative Task Scheduler, AtsDbInfo::validateBaseTables, probe:300
       MESSAGE : ZRC=0xFFFFB0E7=-20249
       SQL20249N The statement was not processed because the package named
       "" needs to be explicitly rebound.
      
       DATA #1 : <preformatted>
       [IBM][CLI Driver][DB2/NT64] SQL20249N The statement was not processed because the package named "NULLID.SYSSH200" needs to be explicitly rebound.

  • db2ubind_lst.log
     . . .
       LINE MESSAGES FOR db2uimpm.bnd . . . db2clpcs.bnd . . . db2clprr.bnd . . . db2clpur.bnd . . . db2clprs.bnd . . . db2clpnc.bnd
       ------ --------------------------------------------------------------------
                 SQL20249N The statement was not processed because the
                 package named "NULLID.SQLABO02" needs to be explicitly
                 rebound.
     . . .
                SQL0595W Isolation level "NC" has been escalated to "UR".
                SQLSTATE=01526
     . . .
      LINE MESSAGES FOR db2ubind.lst
      ------ --------------------------------------------------------------------
                SQL0082C An error has occurred which has terminated
                processing.

  • Starting the Java instance fails. Checking the log files reports the error and cause.

    jvm_bootstrap.out  may contain the following errors

    Caused by: com.sap.engine.frame.core.configuration.ConfigurationException: Error while connecting to DB.
    Caused by: com.sap.sql.log.OpenSQLException: Error while accessing porting layer for DB2_UDB database via getDatabaseName().

        at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:104)
        at com.sap.sql.jdbc.direct.DirectConnectionFactory.createPooledConnection(DirectConnectionFactory.java:532)
        at com.sap.sql.jdbc.direct.DirectConnectionFactory.createDirectPooledConnection(DirectConnectionFactory.java:157)
        at com.sap.sql.jdbc.direct.DirectConnectionFactory.createDirectPooledConnection(DirectConnectionFactory.java:117)
        at com.sap.sql.connect.factory.PooledConnectionFactory.createPooledConnection(PooledConnectionFactory.java:119)
        at com.sap.sql.connect.factory.DriverPooledConnectionFactory.getPooledConnection(DriverPooledConnectionFactory.java:38)
        at com.sap.sql.connect.datasource.DBDataSourceImpl.createPooledConnection(DBDataSourceImpl.java:707)
        at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceImpl.java:1051)
        at com.sap.sql.connect.datasource.DBDataSourceImpl.create(DBDataSourceImpl.java:48)
        at com.sap.sql.connect.pool.CreatedObjectsPool.create(CreatedObjectsPool.java:95)
        at com.sap.sql.connect.pool.Pool.get(Pool.java:761)
        at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl.java:266)
        ... 16 more
    Caused by: com.ibm.db2.jcc.am.SqlException: DB2 SQL Error: SQLCODE=-20249, SQLSTATE=     , SQLERRMC=NULLID.SYSSH200,  <----REBIND Package name 

   


Read more...

Environment

Db2 LUW IBM

Product

SAP ERP 6.0

Keywords

BOOTSTRAP, OpenSQLException caught, 
Error: Couldn't connect to DB, Storage access initialization failed due to OpenSQL error.  Check if your db driver file is available on the file system or if the user has correct permissions for that file,
Exception of type com.sap.sql.log.OpenSQLException caught: Error while accessing porting layer for DB2_UDB database via getDatabaseName(). .
FODC , KBA , BC-DB-DB6 , DB2 Universal Database for Unix / NT , BC-UPG-TLS-TLA , Upgrade tools for ABAP , BC-UPG-TLS-TLJ , Upgrade tools for Java , Problem

About this page

This is a preview of a SAP Knowledge Base Article. Click more to access the full version on SAP for Me (Login required).

Search for additional results

Visit SAP Support Portal's SAP Notes and KBA Search.