Package cannot be found when starting Apply process after a DB2 version upgrade
Procedures to fix an issue when run into the below error when starting Apply process after a DB2 upgrade: 2009-05-01-21.01.57.504760 SQL0805N "Apply" : "IWAPP" : "WorkerThread" : Package "NULLID.ASNDB2SQ 0X3038313231300000" was not found. SQLSTATE=51002
If you have an environment which has Data Propagator (DPROP) setup, and you need to upgrade the DB2 version from v8.1 FixPack 17 to v9.5 FixPack 3a, you might run into an issue where a package cannot be found when starting the Apply process.
Let's suppose we have the following scenario:
- DB2 v8.1 FixPack 17 is setup in the source server (where Capture process runs);
- DB2 v8.1 FixPack 17 is setup in the target server (where Apply process runs). We want to upgrade the DB2 version in this server from v8.1 to v9.5 FixPack 3a;
- The data is replicated from source to target server;
When starting the Apply on target server, after DB2 has been upgraded to v9.5, you might see this kind of error in the apply log, as the below example:
2009-05-01-21.01.57.504760 SQL0805N "Apply" : "IWAPP" : "WorkerThread" : Package "NULLID.ASNDB2SQ 0X3038313231300000" was not found. SQLSTATE=51002
To fix that, a few packages should be bounded on both source and target servers. So, run the below on target local database:
db2 connect to <db_on_target>
db2 bind asndb2cn.bnd isolation ur blocking all grant public
db2 bind asndb2sq.bnd isolation ur blocking all grant public
db2 bind asnluwcon.bnd isolation ur blocking all grant public
Now, from target server, connect to the remote database located in the source server and issue the same commands:
db2 connect to <db_on_source_from_target>
db2 bind asndb2cn.bnd isolation ur blocking all grant public
db2 bind asndb2sq.bnd isolation ur blocking all grant public
db2 bind asnluwcon.bnd isolation ur blocking all grant public
After executing those, the Apply should start normally.
Note: This has been corrected in DB2 v9.5 FixPack 4