In some situations, DB2 may terminate abnormally or issue an
unexpected SQL0727N error while revalidating SQL routines. In
the trap scenario, you will see a stack trace similar to the
following:
0x09000000004BC6BC pthread_kill + 0x88
0x09000000004BC0D0 _p_raise + 0x68
0x0900000000060698 raise + 0x34
0x090000000008C1AC abort + 0xB4
0x0900000078A7C640 sqloExitEDU + 0x240
0x090000007895D750 sqle_panic__Fv + 0x410
0x090000007895DAAC sqle_trap__Fv + 0xC
0x09000000789A4590 sqlzAssertFailedValist + 0x270
0x09000000789A4664 sqlzAssertFailed + 0x64
0x090000007C517900
sqlra_fmt_pkg_seq_lock__FP13SQLP_LOCKNAMEPUcsT2T3T2T3T2 + 0xC0
0x090000007C517C98
sqlra_process_pkg_at_cat__FP8sqlrr_cbPUciT2T3T2T3T2P13SQLP_LOCKN
AMET3 + 0x1D8
0x090000007FA8C0C8 sqlra_pkgversion_opts__FP8sqlrr_cbiT2PUcT2 +
0x2A8
0x090000007FA96DE0
sqlra_set_bind_opts__FP8sqlrr_cbP12bind_options + 0x3DA0
0x090000007FA9A07C
sqlra_create_pkg__FP8sqlrr_cbPUcsT2T3P11sqlrrstringP12bind_optio
ns + 0xB5C
0x090000007A712A08
sqlrr_prepinit__FP14db2UCinterfaceP12bind_options + 0x728
0x090000007FE45C30
initialize__13psmPackageGenFP8sqlrr_cbP3locP12bind_optionsP4FILE
PciPUcT6T7T6T5T6cb + 0x470
...
0x090000007CE52B00
sqlnn_regen_function__FP8sqlrr_cbPUcUsT2UlT2T3P11sqlrg_rtnpdbP17
sqlrl_table_parmsPbN211_ + 0x16E0
Alternatively, you may see an error message similar to the
following, indicating the presence of an SQL0404N error during
implicit revalidation of some database object:
SQL0727N An error occurred during implicit system action type
"3". Information returned for the error includes SQLCODE
"-404",
SQLSTATE "22001" and message tokens "". LINE NUMBER=1.
SQLSTATE=56098
The following initial conditions are required for the problem to
occur:
- Your database was created under DB2 Version 9.7 Fix Pack 5 or
later;
OR
- Your database contains one or more SQL routines that was
created under DB2 Version 9.7 Fix Pack 5 or later.
The following actions may trigger the problem. This is not
necessarily a complete list:
- You attempt an upgrade of the database to any Fix Pack level
of DB2 Version 9.8; for example,
db2 upgrade db DBNAME
- You perform an action which invalidates an SQL routine that
was created under DB2 Version 9.7 Fix Pack 5 or later, then
perform an action which requires DB2 to revalidate the invalid
routine. For example, by calling the routine, if it is an SQL
procedure; using it in a query, if it is a compiled SQL
function; or by explicitly requesting revalidation of the object
via SYSPROC.ADMIN_REVALIDATE_DB_OBJECTS.
Note that the problem is not guaranteed to occur, even if the
initial and triggering conditions are satisfied.
Routines created under any Fix Pack level of DB2 Version 9.8
will
not be affected by this problem. |
If revalidation of an SQL routine fails, and you know which
routine is affected, dropping and recreating the routine will
correct the issue for that routine. If the affected routines
cannot be identified, it may be necessary for you to recreate
your database under Version 9.8.
A fix is forthcoming in DB2 Version 9.8 Fix Pack 5 which will
eliminate the problem without any need for additional action on
your part, even in existing databases upgraded to Version 9.8. |
