Mainframe Lpar Crashed On Starting Extract Process On GG19.1 For DB2 Z/OS
(Doc ID 2683119.1)
Last updated on APRIL 17, 2023
Applies to:
Oracle GoldenGate - Version 19.1.0.0.4 to 19.1.0.0.4 [Release 12.3]Linux x86-64
Symptoms
On our new set up of using OGG 19.1 for DB2 z/OS 11.1, we were able to login to database using DBLOGIN. But upon starting the Extract process Mainframe server lpar had crashed. Below are the messages provided by Mainframe administrator.
11:23:49.25 STC07321 00000281 $HASP100 DBSWLM ON STCINRDR
11:23:49.27 STC07321 00000090 $HASP373 DBSWLM STARTED
11:23:49.27 STC07321 00000291 IEF403I DBSWLM - STARTED - TIME=11.23.49
11:23:49.35 STC07321 00000090 Allocated 1803 bytes of ECSA memory at 13801020.
11:23:49.35 STC07321 00000090 BMC10284S INVALID XST(1380F110) DETECTED ON QUEUE. BMCP
11:23:49.36 STC07321 00000090 BMC10284S INVALID XST(1380F110) DETECTED ON QUEUE. BMCP
11:23:49.36 STC07321 00000090 BMC10284S INVALID XST(1380F110) DETECTED ON QUEUE. BMCP
11:23:49.40 00000090 BMC10284S INVALID XST(1380F110) DETECTED ON QUEUE. BMCP
11:23:49.40 00000281 IEF196I BMC10284S INVALID XST(1380F110) DETECTED ON QUEUE. BMCP
11:23:49.40 00000090 IEA045I AN SVC DUMP HAS STARTED AT TIME=11.23.49 DATE=06/01/2020 909
909 00000090 FOR ASID (0162)
909 00000090 ERROR ID = SEQ38596 CPU00 ASID0162 TIME11.23.49.3
909 00000090 QUIESCE = YES
Changes
Cause
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |
In this Document
| Symptoms |
| Changes |
| Cause |
| Solution |
| References |