DBRM Timestamp Mismatch SQLCODE -805 During TG4DB2 Select From DB2 V9.1 (Doc ID 1324524.1)

Last updated on MAY 26, 2011

Applies to:

Oracle Database Gateway for DB2 - Version: 10.2.0.3 and later   [Release: 10.2 and later ]
IBM z/OS on System z

Symptoms

After an upgrade to DB2 V9.1 and re-creation of the DUAL table, the Gateway Bind job was run with a STEPLIB pointing to DB2 9.1 SDSNLOAD library. Now the following SQL -


select count(*) from sysibm.sysdatabase ;


via SQL*Plus gives errors  ORA-28500 and SQLCODE = -805;


SQL*Plus: Release 10.2.0.3.0 - Production on Fri May 13 08:17:27 2011
0Copyright (c) 1982, 2006, Oracle. All Rights Reserved.
0SQL> Connected.
SQL> SQL> select count(*) from sysibm.sysdatabase@G7ZJ_LINK
*
ERROR at line 1:
ORA-28500: connection from ORACLE to a non-Oracle system returned this message:
DSNT408I SQLCODE = -805, ERROR: DBRM OR PACKAGE NAME DBZJ.G4DB2V102031A.G4DB2-
PLN.0F1F0F2F00F24040 NOT FOUND IN PLAN G4DB2P7W. REASON 03
DSNT418I SQLSTATE = 51002 SQLSTATE RETURN CODE
DSNT415I


The two primary reasons for -805 "REASON 03" under "Error SQL codes" in the documentation IBM DB2 UDB for z/OS Codes are :

- The DBRM of the version of the application program being executed was
  not  bound (A package with the same consistency token as that of the
  application program was not found.) Refer to the fourth and fifth SQL
  statements under the Problem Determination section.
- The incorrect version of the application program is being executed.


Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms