Fixes are available
DB2 Version 9.1 Fix Pack 7 for Linux, UNIX and Windows
DB2 Version 9.1 Fix Pack 5 for Linux, UNIX and Windows
DB2 Version 9.1 Fix Pack 6 for Linux, UNIX and Windows
DB2 Version 9.1 Fix Pack 6a for Linux, UNIX and Windows
DB2 Version 9.1 Fix Pack 7a for Linux, UNIX and Windows
DB2 Version 9.1 Fix Pack 8 for Linux, UNIX and Windows
DB2 Version 9.1 Fix Pack 9 for Linux, UNIX and Windows
DB2 Version 9.1 Fix Pack 10 for Linux, UNIX and Windows
DB2 Version 9.1 Fix Pack 11 for Linux, UNIX and Windows
DB2 Version 9.1 Fix Pack 12 for Linux, UNIX and Windows
APAR status
Closed as new function.
Error description
Local fix
Problem summary
. Defect: 334748: ASNMON: remove DAS dependency and use query to engine control tables for status info for both local and remote servers User Affected: LUW Problem Description: DAS was used to query status for remote engine program and also shared memeory for local engine programs. Provided incorrect results. Problem Summary: Fixed ASNMON engine status alert condition by querying engine's control tables Problem Conclusion: No DAs error, or ipc keys issue will use query to engine tables for status. . Defect: 331972: ASNMON: ZOS stop command produced ABENDSOC4 sometimes and monitor was fixed to start from last monitor time in all cases User Affected: start monitor time (ZOS & LUW); ABENDSOC4 (only ZOS) Problem Description: When worker thread was busy and did not stop the main init thread sent a kill request and stopped; when worker thread returned and accessed the information it produced ABENDS0C4; start monitor was not starting at previous cycle in some conditions. Problem Summary: both problems have been fixed. Problem Conclusion: The init thread will delay before it send a kill and stop if the worker thread is busy. The monitor program will start right at each cycle in all cases. . Defect: 340877: QAPPLY SIGSEGVs when checking dependencies between transactions if cols in unique index > 16 User Affected: Any QAPPLY user having subscriptions with > 16 columns in unique index and a high workload Problem Description: Subscriptions with > 16 columns in the unique index were not handled properly during transaction dependency checking Problem Summary: Any subscription that has > 16 columns in unique index could result in QAPPLY SIGSEGV. The problem is workload dependent and is likely to occur with large volumes of transactions for the subscription having > 16 columns in the unique index . Defect: 339511: Messages still left in receive queue when data has already been replicated to target table Problem Description: Some diagnostic print statements in the pruning code needed to be removed. Problem Summary: Removed diagnostic print statements from the pruning code that could flood the QAPPLY output file and be potentially confusing to the customers. Problem Conclusion: Internal print related stuff only. . Defect: 333733: SQLCAPTURE failed to start with warmns after source table altered User Affected: Users altering SQLCAPTURE registered source tables. Problem Summary: SQLCAPTURE need to rebuild SQLDA after source table alter Problem Conclusion: SQLCAPTURE has been modified to fix the problem. . Defect: 326955: QCAPTURE in HADR env does not WARMSTART on standby side; SQL0924N from waitForLogrdInit User Affected: All QCAPTURE users Problem Description: WARMSTART QCAPTURE of standby machine return SQL0924N Problem Summary: QCAPTURE did not handle database rollfoward correctly. . Defect: 155191: Update on added columns might fail User Affected: QCAPTURE Problem Description: Data for newly added columns sometimes did not get replicated Problem Summary: When QCAPTURE receives an ADDCOL signal, the txrdr thread needs to be suspended before processing more log records. Problem Conclusion: Data for newly added columns is now always replicated . . Defect: 334748: ASNMON: remove DAS dependency and use query to engine control tables for status info for both local and remote servers User Affected: LUW Problem Description: DAS was used to query status for remote engine program and also shared memeory for local engine programs. Provided incorrect results. Problem Summary: Fixed ASNMON engine status alert condition by querying engine's control tables Problem Conclusion: No DAs error, or ipc keys issue will use query to engine tables for status. . Defect: 331972: ASNMON: ZOS stop command produced ABENDSOC4 sometimes and monitor was fixed to start from last monitor time in all cases User Affected: start monitor time (ZOS & LUW); ABENDSOC4 (only ZOS) Problem Description: When worker thread was busy and did not stop the main init thread sent a kill request and stopped; when worker thread returned and accessed the information it produced ABENDS0C4; start monitor was not starting at previous cycle in some conditions. Problem Summary: both problems have been fixed. Problem Conclusion: The init thread will delay before it send a kill and stop if the worker thread is busy. The monitor program will start right at each cycle in all cases. . Defect: 340877: QAPPLY SIGSEGVs when checking dependencies between transactions if cols in unique index > 16 User Affected: Any QAPPLY user having subscriptions with > 16 columns in unique index and a high workload Problem Description: Subscriptions with > 16 columns in the unique index were not handled properly during transaction dependency checking Problem Summary: Any subscription that has > 16 columns in unique index could result in QAPPLY SIGSEGV. The problem is workload dependent and is likely to occur with large volumes of transactions for the subscription having > 16 columns in the unique index . Defect: 339511: Messages still left in receive queue when data has already been replicated to target table Problem Description: Some diagnostic print statements in the pruning code needed to be removed. Problem Summary: Removed diagnostic print statements from the pruning code that could flood the QAPPLY output file and be potentially confusing to the customers. Problem Conclusion: Internal print related stuff only. . Defect: 333733: SQLCAPTURE failed to start with warmns after source table altered User Affected: Users altering SQLCAPTURE registered source tables. Problem Summary: SQLCAPTURE need to rebuild SQLDA after source table alter Problem Conclusion: SQLCAPTURE has been modified to fix the problem. . Defect: 326955: QCAPTURE in HADR env does not WARMSTART on standby side; SQL0924N from waitForLogrdInit User Affected: All QCAPTURE users Problem Description: WARMSTART QCAPTURE of standby machine return SQL0924N Problem Summary: QCAPTURE did not handle database rollfoward correctly. . Defect: 155191: Update on added columns might fail User Affected: QCAPTURE Problem Description: Data for newly added columns sometimes did not get replicated Problem Summary: When QCAPTURE receives an ADDCOL signal, the txrdr thread needs to be suspended before processing more log records. Problem Conclusion: Data for newly added columns is now always replicated . Defect: 332003: Fix subscription parsing and tolerate pruning errors in AdminThread. User Affected: ALL Problem Description: Errors when pruning of the DONEMSG table caused the AdminThread to stop. This resulted in many entries in DONEMSG table and the receive queue. Parsing subscription information from TRG_COLS table was not reentrant leading to errors when more than 20 Browsers were used. Stored Procedure query failed with SQL0204N in Japanese environment. Problem Summary: Tolerate pruning errors in AdminThread. Make subscription parsing code reentrant. Uppercase Stored Procedure query to work in Japanese environment. . Defect: 328080: Make reading and parsing of subscriptions reentrant User Affected: ALL Problem Description: When a large number of Browsers (typically 10-15) initialized their subscriptions on startup, a race condition caused subscription information parsing to behave incorrectly. Problem Summary: This problem has been fixed allowing a large number of Browsers to initialize their subscriptions without problems. . Defect: 324498: Delete non-QREP messages or messages with an older sequence time User Affected: ALL Problem Description: QAPPLY stops when it detects non-QREP messages or messages with an older sequence time, making it difficult for the user to selectively delete such messages. Problem Summary: QAPPLY stops when it detects non-QREP messages or messages with an older sequence time. Problem Conclusion: QAPPLY will delete such messages from the queue and continue normal processing. . Defect: 331603: DB2 z/OS V9 2 node BIDI LONG VARCHAR ADD COL INCORR behavior User Affected: QAPPLY Problem Description: P2P/BIDI did not support replication between LONG VARCHAR to VARCHAR columns. Problem Summary: P2P/BIDI configurations failed to start subscriptions replicating between LONG VARCHAR to VARCHAR columns even if the lengths matched. ADDCOL also had failures while adding new LONG VARCHAR columns. Problem Conclusion: P2P/BIDI will now support replication between LONG VARCHAR to VARCHAR as long as the lengths match. ADDCOL succeeds for LONG VARCHAR columns. . Defect: 322148: QAPPLY fails with SQL0945N during apply from spill queue User Affected: QAPPLY Problem Description: QAPPLY fails with SQL0945N during apply from spill queue after a load if there are non-key unique constraints. Problem Summary: QAPPLY fails with AsnRcUnqCnst SQL0945N as it does not handle SQL0803N conflicts during apply from spill queue after a load when DB2 returns a non-key unique constraint instead of a key constraint in the sqlda. Problem Conclusion: Fixed QAPPLY to handle SQL0803N correctly during processing of spill queue after load if DB2 returns a non-key unique constraint, by trying to force the operation once. . Defect: 324482: Prune Donemsg Deltomb slows, Recvq fills due to bad timing calculation User Affected: QAPPLY Problem Description: Timing problem causes pruning of Donemsg Deltomb table to slow down causing receive queue to fillup. Problem Summary: A timing problem causes the Admin thread to calculate wrong return times from the prune DoneMsg and Deltomb loops that causes the pruning to slow down or stop. Problem Conclusion: Fixed the calculations of the timing variables to ensure that they never get stale and have same values. . Defect: 332795: SQLAPPLY receives SQL0300N on zos when it updates register table during RBA translation for FULLREFRESH for internal CCD target. User Affected: SQLAPPLY users Problem Description: SQLAPPLY receives SQL0300N on zos when it updates register table during RBA translation for FULLREFRESH for internal CCD target. Problem Summary: SQLAPPLY buffer for table name is defined as char(18) Problem Conclusion: Change buffer for table name from char(18) to char(128) . Defect: 332795: Linux only: SQLAPPLY does not separate asndone parameter. User Affected: SQLAPPLY users Problem Description: Linux only: ASNDONE failed since SQLAPPLY passes 1 parameter to ASNDONE only Problem Summary: Linux only: SQLAPPLY should separate asndone parameters with blanks. Problem Conclusion: add blanks between parameters in SQLAPPLY . Defect: 332795: Windows SQLAPPLY fails with SQL0103N in conflict compensation User Affected: SQLAPPLY users Problem Description: Windows SQLAPPLY fails with SQL0103N in conflict compensation Problem Summary: the error is caused by incorrect syntax: a blank is needed between "0," and "IBMSNAP_INTENTSEQ" Problem Conclusion: add a blank after "0," in select statement . Defect: 332795: SQLAPPLY fails to fetch from CD & UOW table with SQL0203N on IBMSNAP_COMMITSEQ when target is replica with conf_lvl=0 User Affected: SQLAPPLY users Problem Description: SQLAPPLY fails to fetch from CD & UOW table with SQL0203N on IBMSNAP_COMMITSEQ when target is replica with conf_lvl=0 Problem Summary: correlation id should be added to IBMSNAP_COMMITSEQ Problem Conclusion: correlation id is added on IBMSNAP_COMMITSEQ on failing select statement . Defect: 332795: SQLAPPLY incorrectly advances set synchpoint for statement-only set. User Affected: SQLAPPLY users Problem Description: SQLAPPLY incorrectly advances set synchpoint for statement-only set. Problem Summary: SQLAPPLY should not advance set synchpoint for statement-only set Problem Conclusion: SQLAPPLY should not advance set synchpoint if set is statement-only . Defect: 332795: SQLAPPLY replicates rows with IBMSNAP_OPERATION='D' in FULLREFRESH when source is external CCD User Affected: SQLAPPLY users Problem Description: SQLAPPLY replicates rows with IBMSNAP_OPERATION='D' in FULLREFRESH when source is external CCD Problem Summary: SQLAPPLY should not replicate rows with IBMSNAP_OPERATION='D' in FULLREFRESH from CCD source to target Problem Conclusion: SQLAPPLY does not replicated deleted row from CCD source on FULLREFRESH . Defect: 332795: SQLAPPLY terminates when it failed to connect to control server User Affected: SQLAPPLY users Problem Description: SQLAPPLY terminates when it failed to connect to control server Problem Summary: do not terminate SQLAPPLY when it failed to connect to control server Problem Conclusion: SQLAPPLY sleeps seconds of ERRWAIT when it can not connect to control server if TERM=N . Defect: 317896: SQLAPPLY fails with SQL0452N when LOB is described for type 9 CCD source User Affected: SQLAPPLY users Problem Description: SQLAPPLY fails with SQL0452N when LOB is described for type 9 CCD source Problem Summary: lob sqlda is not set correctly when SQLAPPLY fetches row from type 9 CCD Problem Conclusion: correct lob sqlda so lob column can be fetched successfully . Defect: 317896: SQLAPPLY does not issue "sql commit" before execute 'A' statement when there is no row fetched in current cycle User Affected: SQLAPPLY users Problem Description: SQLAPPLY does not issue "sql commit" before execute 'A' statement when there is no row fetched in current cycle Problem Summary: A "sql commit" should be issued before execute 'A' statement when no row is processed Problem Conclusion: issue a "sql commit" before execute 'A' statement . Defect: 317896: SQLAPPLY does not report error to applytrail table User Affected: SQLAPPLY users Problem Description: SQLAPPLY does not report error to applytrail table Problem Summary: SQLAPPLY does not save error information for applytrail table Problem Conclusion: save error information for applytrail table when an error occurs . Defect: 317896: SQLAPPLY supports taget_key_change from CCD source User Affected: SQLAPPLY users Problem Description: SQLAPPLY supports target_key_change from CCD source Problem Summary: SQLAPPLY supports target_key_change from CCD source Problem Conclusion: SQLAPPLY supports target_key_change from CCD source . Defect: 317896: SQLAPPLY trace file grows to 2G User Affected: SQLAPPLY users Problem Description: SQLAPPLY trace file right shift 1 byte for each cycle incorrectly Problem Summary: SQLAPPLY does not exit certain functions properly Problem Conclusion: trace line won't shift after exit from function . Defect: 317896: FULLREFRESH is not triggered when CCD is source in SQLAPPLY User Affected: SQLAPPLY users Problem Description: FULLREFRESH is not triggered when CCD is source in SQLAPPLY Problem Summary: SQLAPPLY does not start FULLREFRESH when set.sp < ccd_old Problem Conclusion: FULLREFRESH will be triggered when ccd_old_synchpoint > set.sp . Defect: 317896: SQLAPPLY ABENDS0C4 when previous malloc() failed User Affected: SQLAPPLY users Problem Description: SQLAPPLY ABENDS0C4 when previous malloc() failed Problem Summary: SQLAPPLY tries to refer to a NULL member pointer to update control table after malloc() on member information failed Problem Conclusion: correct SQLAPPLY so that it won't try to access the NULL pointer .
Problem conclusion
The reported problems have been fixes and are available in DB2 LUW V9.1 FP5.
Temporary fix
Comments
APAR Information
APAR number
JR27730
Reported component name
REPLICATION SER
Reported component ID
5724N9800
Reported release
910
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2007-10-29
Closed date
2008-06-19
Last modified date
2008-06-19
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
Fix information
Fixed component name
REPLICATION SER
Fixed component ID
5724N9800
Applicable component levels
R910 PSY
UP
Document Information
Modified date:
07 October 2021