Fixes are available
DB2 Version 9.7 Fix Pack 3 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 3a for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 4 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 5 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 6 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 7 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 8 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9a for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 10 for Linux, UNIX, and Windows
APAR status
Closed as program error.
Error description
Engine Fixes for V97FP3
Local fix
fix in the code
Problem summary
. The following problems have been fixed in DB2 LUW V9.7 FP3 . Release: v97 User Affected: Windows Q and SQL Replication customers. Problem Description: Q and SQL Replication programs could hang attempting to open the satadmin.aut file if the satadmin.aut file is corrupt. Q and SQL Replication programs check for existence of the Replication password file before they connect to a DB2 server. If the Replication password file does not exist or does not contain the user id and password necessary to connect to the DB2 server, Q and SQL Replication programs attempt to open the satadmin.aut file to obtain userid/password for the DB2 server. Problem Summary: Only SQLAPPLY executing in the Satellite environment should access the satadmin.aut file. Problem Conclusion: This fix introduces a new environment . The following problems have been fixed in DB2 LUW V9.7 FP3 . Release: v97 User Affected: Windows Q and SQL Replication customers. Problem Description: Q and SQL Replication programs could hang attempting to open the satadmin.aut file if the satadmin.aut file is corrupt. Q and SQL Replication programs check for existence of the Replication password file before they connect to a DB2 server. If the Replication password file does not exist or does not contain the user id and password necessary to connect to the DB2 server, Q and SQL Replication programs attempt to open the satadmin.aut file to obtain userid/password for the DB2 server. Problem Summary: Only SQLAPPLY executing in the Satellite environment should access the satadmin.aut file. Problem Conclusion: This fix introduces a new environment variable, ASNSATELLITE. SQLAPPLY will access the satadmin.aut file to obtain a userid/password only if the ASNSATELLITE environment variable is set to a value (ASNSATELLITE=Y for example) and SQLAPPLY is not able to obtain a userid/password from the replication password file. . Release: v97 User Affected: QCAPTURE and QAPPLY customers who run the asnqccmd/asnqacmd STATUS SHOW DETAILS commands. Problem Description: The STATUS SHOW DETAILS command shared memory segment is not released when the STATUS SHOW DETAILS command terminates. Problem Summary: QCAPTURE and QAPPLY do not detach from the STATUS SHOW DETAILS command shared memory segment after they write STATUS SHOW DETAILS information. Problem Conclusion: Modify QCAPTURE and QAPPLY to fix this problem. . Release: v97 User Affected: QCAPTURE and SQLCAPTURE customers who use the TERM=N option. Problem Description: QCAPTURE and SQLCAPTURE started with TERM=N stop after a DB2 FORCE APPLICATION command. Problem Summary: QCAPTURE and SQLCAPTURE terminate after a DB2 log read API call receives a DB2 terminated SQLCODE. Problem Conclusion: Modify SQLCAPTURE and QCAPTURE to fix this problem. .
Problem conclusion
See above
Temporary fix
Comments
APAR Information
APAR number
JR36630
Reported component name
REPLICATION SER
Reported component ID
5724N9800
Reported release
970
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2010-05-18
Closed date
2010-09-29
Last modified date
2010-09-29
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
IC69217
Fix information
Fixed component name
REPLICATION SER
Fixed component ID
5724N9800
Applicable component levels
R970 PSY
UP
Document Information
Modified date:
12 October 2021