A fix is available
APAR status
Closed as new function.
Error description
Qcapture and SQL capture will see a performance improvement with savepoint rollbacks.
Local fix
Problem summary
**************************************************************** * USERS AFFECTED: 1- Users of the replication admin stored * * procedure * * 2- Customers who use Q Capture to publish * * delimited messages. * * 3- Q/SQL Capture with multiple altered * * tables in the same tablespace. * **************************************************************** * PROBLEM DESCRIPTION: 1- BIND ASNADMSP stored procedure * * DBRMs fails with SQLCODE -104 * * 2- Q Capture abends with S0C4 * * publishing delimited messages when its * * message buffer contains multiple rows * * and there is just enough space * * remaining in the message buffer for * * one delimited message header. * * 3- Capture cannot decode log records * * after a tablespace reorg if the * * tablespace contains multiple altered * * tables. Capture will issue error * * message ASN7130. * **************************************************************** * RECOMMENDATION: * **************************************************************** 1- The BIND for the replication admin stored procedure fails with an SQLCODE -104 when Japanese codepages are involved. This is because the cursor names in the DECLARE CURSOR statement are written in lower case. 2- Q Capture writes one byte beyond the end of its message buffer and overlays the next block of memory. 3- On z/OS, a reorg operation updates the version of all the altered tables in a tablespace to the tablespace version. Capture does not know about the reorg operation and does not know of the new version.
Problem conclusion
Temporary fix
Comments
1- Changed the cursor names in the DECLARE cursor statements to upper case. 2- Modify Q Capture to correct this problem. 3- When capture encounters a log record with an unknown and newer version, it will try to query the information from the system catalogs. ********* * HIPER * ********* Qcapture: Updated data are NOT able to be replicated for bidirectional replication after inserting a addcol signal. Q Capture was incorrectly setting the COL_OPTIONS_FLAG for columns added using the ADDCOL signal in a bi-directional subscription Capture was incorrectly setting the COL_OPTIONS_FLAG to 'NNNNNNNNNN' With PTF UK50647 Q Capture is now setting the COL_OPTIONS_FLAG to 'YNNNNNNNNN'
APAR Information
APAR number
PK95565
Reported component name
WS REPLICATION
Reported component ID
5655L8800
Reported release
910
Status
CLOSED UR1
PE
NoPE
HIPER
YesHIPER
Special Attention
NoSpecatt
Submitted date
2009-09-07
Closed date
2009-09-30
Last modified date
2010-02-26
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
UK50647 UK50648 UK50649 UK50650
Modules/Macros
ASNACMD ASNADMSP ASNAPPLY ASNCAP ASNCCMD ASNMCMD ASNMIG8 ASNMON ASNMUPDT ASNPLXFY ASNQACMD ASNQAPP ASNQBRWZ ASNQCAP ASNQCCMD ASNQCTLZ ASNQDEP ASNQMFMT ASNQSPIL ASNQXFMT ASNRBASE ASNSQLCZ ASNTDIFF ASNTDSQL ASNTRC ASN2BASE ASN2SQLZ
Fix information
Fixed component name
WS REPLICATION
Fixed component ID
5655L8800
Applicable component levels
R910 PSY UK50647
UP09/10/08 P F910
R911 PSY UK50648
UP09/10/08 P F910
R912 PSY UK50649
UP09/10/08 P F910
R913 PSY UK50650
UP09/10/08 P F910
Fix is available
Select the PTF appropriate for your component level. You will be required to sign in. Distribution on physical media is not available in all countries.
[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSDP5R","label":"InfoSphere Replication Server"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"910","Edition":"","Line of Business":{"code":"LOB10","label":"Data and AI"}}]
Document Information
Modified date:
26 February 2010