APAR status
Closed as canceled.
Error description
OEM vendor products that have caused problems in DB2 or IRLM ---------------------------------------------------------------- ======================== lsk 3/31/2006 ====================== DB2 HUNG erep shows S0c4 and S073 rc08 with DB2 running disabled and holding CPU lock and CPU lock is not released DSNT369I -DB4G DSNTLPLK A NOTIFY PROCESS APPEARS TO BE HUNG Also see 0c7 and 33e abend073 abend0c7 abend33e ABEND0C4 in IEAVTSFR with R14 = IEAVRT05 DB2 thread got abends while holding a system agent latch class30 ( class 30 ) and hangs until DB2 is recycled. QM does a TIME USED TIMEUSED FROM CQMMESQL Query Monitor from Rocket Software has R210 apar PK21697 R220 is PK22632/UK13387 and now SUPERSEDED BY: UK13995 ========================== lsk 3/06/2006 =================== Hung Thread in DB2 with Enq seen on Major name SPACVOLA MINOR PRS40040 and Tcb in DB2dbm1 asid has taken an abend s138 ( abends138 abend138 ). Systrace shows tcb holding eng procressing in PRS90020 V7R2M1 BASE721 BMC module. Later tcb caused an ENQ lockout on SPACVOLA/PRS40040. BMC The fixing PTF is BPG3703. ================ GEPutintsev 03/03/06 ===================== The BMC resolution R212029 makes Catalog Manager V8.1.00 treat a DB2 V8 CM system as V7. This affects DB2 Query performance and forcing tablespace scanning on DSNDB06.SYSDBASE, running Queries like this: DECLARE TPTSCRSR CURSOR FOR SELECT A . * FROM CATTABLEPART A WHERE A . DBNAME = : H AND A . TSNAME = : H ORDER BY A . PARTITION FOR FETCH ONLY (CATTABLEPART is a SYNONYM of SYSIBM.SYSTABLEPART) The equivalent access path on V7 is a non-matching index scan of SYSIBM.DSNDPX01 - MATCHCOLS = 0. The ZAP is to be removed when migrating to ENFM / NFM. The customer provided BMC fix info: R212029, and stated that BMC are working on an update to Catalog Manager that will detect CM / ENFM / NFM and behave accordingly. ========================= lsk 02/27/06 ===================== *DSNV086E DB2 ABNORMAL TERMINATION REASON=00F30801 SYSTEM COMPLETION CODE=0D7 REASON CODE=00000025 and 00000027 DSNAPRHX abend004E at UQ96632 R15 = 00F30801 applied fixes to the Computer Associates CA90 product ======================= lsk 02/23/06 ======================== We just upgrade our production db2 to v8 compt mode. DSNL027I :DB2P SERVER DISTRIBUTED AGENT WITH 311 LUWID=A19C67F5.GA71.BE4BFA7A039B=29126 THREAD-INFO=ECSSPD3:*:*:* RECEIVED ABEND=04E FOR REASON=00E20017 Abend0c6 psw is on an odd byte & in TMDB637= Tmon from Allen Systems Group. The ebskb address for the failing eb is not in the primary asid (dbm1) but it was in the home asid (DIST). The ace for the failing eb does not point back to the eb. There was an abend0c4 in DSNIDMPS just prior to the rc00e20017 00e20017 that appears to be related (same eb). Abend0c4 pic11 IEAVEEE at ua05113 with bad reg5 SXSB and IRB overlaid . Abend058 rc10 also caused by overlaid storage. Fix: maintenance from the tmon vendor solved the problem. ======================= lsk 02/06 =========================== DB2 abend0d5 rsn21 SYSTEM COMPLETION CODE= 0D5 REASON CODE= 00000021 Also dump COMPON=SUPVCNTL,COMPID=SC1C5,FUNCTION=RESUME, MODULE=IEAVETCL also abendAC7, abend0fcb IEAVTSRB, rsn00090001 IEAVTRTM 00090001 abend058 IEAVEDS0 IEF196I IAT6809 JOB Z1P2DBM1 (JOB10627) - TERMINATED BY END OF MEMORY DSNV086E -Z1P2 DB2 ABNORMAL TERMINATION REASON=00F30408 rc00f30408 00f30408 DBM1 EOM . Root cause was User application passing bad plist to ACF2 and ACF overlaying WEBs in ESQA. Eyecatchers in overlay in ESQA had EWEB MSNETWRK N.SYSDA URPOOL ====================== LSK 02/06/006============================ abnormal termination ABEND0C4 pic10 00E50702 rc00E50702 DSNWDSDM ABENDED DURING DUMP PROCESSING r13 is DSNWDSDM there is storage missing ( overlaid overlay bad ) Vendor CA has acknowledged a problem with their "Detector" product that led to this ABEND. They recommended CA fixes UDTD248 and UDTD251 ============== 5740XYR00 = CRR 12/12/05 ==================== S0C1 DSNGEGBK+0960 S0C1 DSNB1PER+0172 S0C4 DSNB1SWD+0BB4 OEM CA-Detector Module GETZDATA is using an invalid Base to OR a double word of date. Offset being used is x'03F8'. The use of the x'03F8' and invalid base value cause DB2 executable code to be altered resulting in various AbEnds. Verify using the IPCS Find command: F X'D60703F8' MA(X'FFFF0FFF') NOBREAK. The offset x'03F8' is the offset from the previous page address to the first observation of the bit overlay. CA Hiper Fix UTTE061 ===================== 11/29/05 SGC ============================= ABEND0C4 DSNJDS04 and/or ABEND0C1 IEEAB401 dynamic allocation involving an archive log data set. Customer reported the resolution involved OEM products CONTROL-M for z/OS and CONTROL-O for z/OS with fix PA11414 applied. CMEM msg CMEM0000 DTC IS FOR CURRENT RELEASE may appear in the console syslog. . The customer provided BMC fix info: PA13317 . ===================== 09/30/2005 CRR =========================== RC00F30801 DSNAPRHX+1A8A ; Latches Held ; FRR not entered . SysTrace shows an OEM Authorization Exit, loaded as DSNX@XAC is intercepting DB2 code and had removed the DB2 FRR. Since the FRR was removed from the FRR Stack the code which would normally release any held latches was not executed. This resulted in RC00F30801 DSNAPRHX+xxxx AbEnds. . OEM CA ENF/DB2 is the cause of the problem. Fix # Unknown. . Reference PMRs 78960,487 & 54731,211,848 . ================= 07/15/05 SGC ================================= Hang of DB2 threads (CICS applications in the reported case) and unable to cancel them. Systrace full of EXT and DSP entries with PSW pointing into OEM ( Compuware ) Strobe code and found to be in a tight loop. Eyecatcher shows Strobe csect STRBPOST. LMOD names may include STRBDSNA and STRBVPH2. Customer advised that the product is Strobe for Sysplex V3.2 at FS005938 level with the DB2 option active and running SQL Analysis feature (STRSSA). Customer reports the following fixes are needed: FS005973, FS005993, FS005881, FS005885 AND FS005997 . ============================== lsk 5/19/05 =================== ABND=04E 00C90101 R710 DSNIBMCL:500B at UQ80406 abend04e rc00c90101 erqual500b DSNIBMCL DSNI014i msgDSNI014I -DB2 -DSNIBMCL Data in use during abend type 302 - data page type 00000302 type302 partitioned tablespace 00c90101 erqul500B . Check index worked on the partitions, CC=0. REPAIR DBD TEST showed a mismatch between the catalog and directory - OBDPSLTH . However running REBUILD (which ran clean) but did not help the problem. Then they got abend04e ERQUAL2004 in DSNIONEX in logrec they saw prior abendu0101 rns108 SIBPX004 at L170662 SUBFUNCTION: IXFP NPXDMQ PC FAILURE Compuware found the fix S005810 and S005951 fixed this S04E problem from Strobe 3020 version. Abend0c4 in Strobe caused overlaid and lead to the DB2 errors ============ GPUT 5/06/05 ================================ Customer reported getting -4499 sqlcode on Java build which can occur with SIMM 2000. This is a new error code introduced with Maint for an old problem which is that the HFS files are not in sync with the DSNLOD2 library and/or the WLM proc has an APF authorized steplib. Once the customer cleared these up the problem was resolved. . Customers should be current with SIMM 2000 and monitor for DBM1 library concatenation conflicts with their copy of DSNXGRDS for DB2 z/OS 390. =--------------------------------------------------------------= environment: z/OS 1.5, DFSMS R1H0, DB2 R710 V7.1 symptoms: DSNP011I message RC00D70014 00D70014 D70014 Customer dump showed OEM DTS EOV EXTEND support software active in system. Requested customer contact DTS to confirm their modules were at appropriate level for customer's new z/OS system DTS confirmed this, but noted also that DTS fix # DTS41027 explains and fixes this error condition. Customer disabled DTS for the dataset involved and the problem was no longer reproducible. Customer has obtained DTS41027 and is proceeding with tests. >>>> messages observed in syslog **DB2HDBM1 issued IGD17216I JOBNAME (DB2ADBM1) PROGRAM NAME (DSNYASCP) STEPNAME (DSNYASCP) DDNAME (N/A ) DATA SET (TRWTTRC.DSNDBD.DBTRCTRD.TSJDGTR1.I0001.A002 ) WHICH WAS INITIALLY ALLOCATED TO STORAGE GROUP (DB2IDE) WAS EXTENDED SUCCESSFULLY TO EXTEND STORAGE GROUP (CNRPOOL) **DB2HMSTR issued DSNP011I -DB2A DSNPXTN0 - MEDIA MANAGER SERVICES 108 ERROR FOR TRWTTRC.DSNDBC.DBTRCTRD.TSJDGTR1.I0001.A002 MMRC=256 DSMRC=00D70014 CONNECTION-ID=UTILITY, CORRELATION-ID=DBJDGLOD, LUW-ID=* ________________________________________________________________ ============KLK 7/29/2005 ====================================== PMR 53131,L6Q Job hung in contention w/JES2 SYSZJES2 holding RNAME (Track group allocation and awaiting spool space) From console dump 'ip summ format asid(db2asid)' find the TCB in question that DB2 gave the control to COMPUWARE waitin for the post to be returned in | TGABAS***COPYRIG || ESERVED UNDER TH | | HT (C) 1976, 200 || E COPYRIGHT LAWS | | 3 COMPUWARE COR || OF THE UNITED S | | PORATION. UNPUBL || TATES. ***0.0.0. | | ISHED - RIGHTS R || 0}0K0M0O0Q0.0.0. | . Customer reported the following findings and solutions from OEM: This second instance occurred when the CA ?Strobe product was ex executing to trace and log activity against one of our CICS region and dumps sent to CA for further analysis. CA concluded there were code fixes (FS005973, FS005993, FS005881, FS005885 & FS005997) needed for Strobe for Sysplex V3.2 PTF Level FS005938. No reoccurrance, thus pmr was closed per customer's request. =============================================================== ====================KLK 10/06/2005============================= PMR (21997,004) DB2 crash with RC00E50702 prior abend to abend04F is abend0c4 pic4 DSN3SY00 +0156 v7. The EB Reg6 pointed to a disconnected DDF thread as follows: ACE: 122AD3B8 Status: DA* Req: 0000 System Chain Authid: NONE Plan: DISTSERV Corrid: NONE Corrname: DISCONN Token: 0001C607 EB Primary(Asid) Home(Asid) EBSPAWND TCB/SRB -Status 122AD448 DSNKDIST(00B6) DSNKDIST(00B6) 80000000 00000000 Running A7415A30 10/05/2005 17:19:29.740346 . Developer (JS) helped review the PC stack save area and informed the following: Following the EB->RMVT->RMFT linkage for this RMRQ, it expanded PC 0001F704. From the PC table: 0001F703 FF00 00B6 A74DBAA0 S 21462440 00000000 0100 00 00 0000 7E68AD80 0000 0001F704 FF00 00B6 98B9B5A0 S 21462440 00000000 0100 00 00 0000 7E68AD80 0000 0001F705 FF00 00B6 A74ED130 S 21462440 00000000 0100 00 00 0000 7E68AD80 0000 . The target of the PC is 98B9B5A0, which takes us to: DT$DIIC7V05.0001 /07/0507.36 MVS4 30DB2710(c)1993- 2005 Computer As sociates Interna tional Inc. . Comp Assoc is intercepting our PCs to DSNLDALB and apparantly invoking SYNC (DSN3SY00) invalidly (with an invalid FRB). So, the customer is pursuing with OEM CA support for fix now. . CA support reported that this is a code defect in Detector and it is as DB2 developer's finding that CA code intercepting db2 module dsn3sy00 causing db2 crash. CA support said that based on the products code history the potential for this error has been around for approximately 4 years and since this is the first occurrance they are aware of it is not likely that it will reoccur soon,but cannot completely rule out the possibility. . The permanent fix for this problem will require some product red redesign, targeted to require about a week of effort and would target for r11 and r11.5. . If an immediate P01 level fix is required CA could provide one that should reduce, but not completely eliminate, the possibilit of prob reoccurring. 01/14/2010 Customer provided fix number --- PTF UDTE231 RJL 05/31/2006 BKH The following symptoms have also been observed (70956,487): ABEND04E AB04E S004E 04E 04E-00D30014 00D30014 RC00D30014 DSNLTACT DSNLTACT:0002 0002 VRADC0002 ABNDID0002 ABID0002 DSNLATRN DSNLATRN:0002 0002 VRADC0002 ABNDID0002 ABID0002 DSNLAGNT is called (by DSNLQCRP) to create a "disconnected DBAT" (pool thread) to service newly received work on an existing Type 2 Inactive connection. But by the time the DBAT gets fully created, the work got serviced by another DBAT so this newly created DBAT has nothing to do after all and just suspends in case it's still needed later. But the DBAT goes unused for the DSN6FAC POOLINAC interval so the DBAT gets terminated. During its termination processing, DSNLAGNT RMRQs to DSNLDALB, which is a "PC'ed to" module, but the PC entry address has been hijacked by Computer Associates code and apparently DSNLDALB is either not called at all, or it is called but with a bad R6 (EB) address. The end result is that DSNLDALB is unable to remove the DBAT's TRAN from the TLISAHSH hash chain and the DBATs DPSB is left pointing to the TRAN (DPSBTMP). So when DSNLAGNT gets back control from the DSNLDALB RMRQ, DPSBTMP still points to the TRAN (but DPSBTMP s/b zero at this point). This leads to: 1. DPSBTMP still points to TRAN - DSNLTACT:0002 2. TRAN was not removed from TLISAHSH chain - DSNLATRN:0002 ============================================================ ===================11/11/2005 KLM ========================== DB2 v7 recall migrated db2 dataset from archive fails with rc00d70024 -904 resource unavailable . Manual recall of the dataset works fine. Syslog shows: DSNP012I + DSNPCNP0 - ERROR IN VSAM CATALOG LOCATE 894 FUNCTION FOR DB2NNN.DSNDBC.DBxxxxxx.TSxxxxxx.I0001.A001 CTLGRC=AAAAAA08 CTLGRSN=AAAAAA08 Global trace shows dsnpsctc rc00d70002 . Computer Associates is providing ptfs QO73744 and QO73746 . ============== 5740XYR00 = EDW 06/13/06 ====================
Local fix
Problem summary
Problem conclusion
Temporary fix
Comments
information apar
APAR Information
APAR number
II14036
Reported component name
PB LIB INFO ITE
Reported component ID
INFOPBLIB
Reported release
001
Status
CLOSED CAN
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2005-05-06
Closed date
2005-05-19
Last modified date
2010-01-14
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
Fix information
Applicable component levels
[{"Business Unit":{"code":null,"label":null},"Product":{"code":"SG19O","label":"APARs - MVS environment"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"001","Edition":"","Line of Business":{"code":"","label":""}},{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSEPEK","label":"Db2 for z\/OS"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"001","Edition":"","Line of Business":{"code":"LOB10","label":"Data and AI"}}]
Document Information
Modified date:
14 January 2010