A fix is available
APAR status
Closed as program error.
Error description
SQL apply issued no-id message 'global control record not found' when it encountered sqlcode904 rc00C90096. Apply was started with trlreuse option which directs apply to delete all rows from the ibmsnap_applytrail table. Apply hit max number of locks with the -904 and should have reported that error instead of global control record not found.
Local fix
manaually delete rows from applytrail table incrementally. or start apply without trlreuse option.
Problem summary
**************************************************************** * USERS AFFECTED: 1- Capture * * 2- Q Capture * * 3- Q Capture users with ERROR_ACTION=S * * 4- Q Capture * * 5- Q Capture * **************************************************************** * PROBLEM DESCRIPTION: 1- Error message is not properly * * displayed when user specifies the * * wrong CAPTURE_SCHEMA. The error * * message only comes out when * * LOGSTDOUT=Y * * 2- Q Capture may send incorrect * * LOB/XML data leading to SQL errors or * * data corruption on the target when the * * following conditions are met: 1. Q * * Capture replicates a partitioned table * * with both BRF and RRF partitions, 2. * * An INSERT or UPDATE occurs on a row in * * the RRF partitions where the LOB value * * is NULL or empty followed by an UPDATE * * or INSERT row in a BRF partition of * * the same table. The LOB/XML data from * * the BRF row may be incorrect (NULL, * * empty) or corrupted. * * 3- When send queues encounters an * * error, program stops, but queue also * * transitions to inactive * * 4- Q Capture started with * * COMPATIBILITY 0907 writes invalid * * intentseq values in its transaction * * messages. * * 5- Q Capture started with * * COMPATIBILITY 0907 writes invalid * * commitseq values in its transaction * * messages. * **************************************************************** * RECOMMENDATION: * **************************************************************** 1- Error messages should always be displayed. 2- Incorrect or corrupted LOB/XML values are sent by Q Capture under certain conditions due to a flag that is not reset when processing a combination of BRF and RRF rows for the same table. 3- ERROR_ACTION=S should cause the send queue to remain active 4- Q Apply consumes the Q Capture transaction messages and populates its CCD target table IBMSNAP_INTENTSEQ columns with invalid values. 5- Q Apply consumes the Q Capture transaction messages and populates its CCD target table IBMSNAP_COMMITSEQ columns with invalid values.
Problem conclusion
1- ASN0528E or ASN0552E will be displayed if the CAPTURE_SCHEMA is incorrect. 2- The problem was fixed by resetting the flag correctly. 3- The problem is resolved 4- Q Capture started with COMPATIBILITY 0907 will write valid intentseq values in its transaction messages. 5- Q Capture started with COMPATIBILITY 0907 will write valid commitseq values in its transaction messages.
Temporary fix
Comments
**** PE14/06/12 PTF IN ERROR. SEE APAR PI19975 FOR DESCRIPTION
APAR Information
APAR number
PM94614
Reported component name
WS REPLICATION
Reported component ID
5655L8800
Reported release
A10
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2013-08-06
Closed date
2013-09-04
Last modified date
2014-06-20
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
UK97279 UK97280 UK97281 UK97282 PM98752
Modules/Macros
ASNAAPP ASNACMD ASNACMP ASNADMIN ASNADMSP ASNAFET ASNAISO ASNAMAN ASNAPPLY ASNAPRS ASNAWPN ASNBNDDR ASNBNDMU ASNBNDSR ASNCAP ASNCCMD ASNCCPWK ASNCDINS ASNCLP ASNCLPAP ASNCLPB ASNCLPCL ASNCLPCM ASNCLPCO ASNCLPCT ASNCLPEV ASNCLPMS ASNCLPQA ASNCLPRM ASNCMPLD ASNCSCZ ASNCTLZD ASNDADK ASNDBCON ASNDB2CN ASNDB2SQ ASNDEDE ASNDONE ASNENUP ASNENUS ASNESES ASNFIFI ASNFRFR ASNISLKM ASNISMKD ASNITIT ASNJAJP ASNKOKR ASNLKMSG ASNLOAD ASNMCMD ASNMDATA ASNMIGFB ASNMIGZD ASNMIG1D ASNMIG2C ASNMIG2S ASNMIG3C ASNMIG3S ASNMIG8 ASNMKDIR ASNMON ASNMONIT ASNMPROC ASNMUPDT ASNM2V8 ASNNONO ASNPLPL ASNPLXFY ASNPRUNE ASNPTBR ASNQACMD ASNQAHKT ASNQAPAG ASNQAPP ASNQAROW ASNQASUB ASNQBNDE ASNQBNDL ASNQBNDR ASNQBNDT ASNQBRWZ ASNQCAP ASNQCCMD ASNQCTLZ ASNQDEFQ ASNQDEP ASNQEXRP ASNQFALL ASNQFA10 ASNQFA95 ASNQFA97 ASNQJ001 ASNQJ002 ASNQLODZ ASNQMFMT ASNQMSTP ASNQMZV9 ASNQMZ10 ASNQMZ95 ASNQMZ97 ASNQM2V8 ASNQPROF ASNQP2PA ASNQP2PI ASNQSPC ASNQSPIL ASNQSPS ASNQSTPA ASNQSTPC ASNQSTRA ASNQSTRC ASNQTOFF ASNQTON ASNQXFMT ASNQ1001 ASNRBASE ASNREG ASNRURU ASNSMZV9 ASNSMZ10 ASNSQLCF ASNSQLCZ ASNSTPA ASNSTPC ASNSTPM ASNSTRA ASNSTRC ASNSTRM ASNSVSE ASNS1001 ASNTDIFF ASNTDSP ASNTDSQL ASNTRC ASNTRCON ASNTRDMP ASNTRFLW ASNTRFMT ASNTROFF ASNUOW ASNZHCN ASNZHTW ASNZOSCN ASN2BASE ASN2DBCN ASN2DB2C ASN2DB2Q ASN2SQLF ASN2SQLZ ASN2ZOSC CACINIZ
Fix information
Fixed component name
WS REPLICATION
Fixed component ID
5655L8800
Applicable component levels
RA10 PSY UK97279
UP13/09/13 P F309
RA11 PSY UK97280
UP13/09/13 P F309
RA12 PSY UK97281
UP13/09/13 P F309
RA13 PSY UK97282
UP13/09/13 P F309
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":"A10","Edition":"","Line of Business":{"code":"LOB10","label":"Data and AI"}}]
Document Information
Modified date:
20 June 2014