Skip to main content
GoldenGate

OGG-02028 Failed to attach to logmining server Error code 1304

By December 13, 2014September 12th, 2016No Comments

OGG-02028  Failed to attach to logmining server Error code 1304, error message: ORA-01304: subordinate process error

In this post, I would liketo share my experience of an error which I had faced recently.

For a project, I Configured Oracle GoldenGate 12c Integrated Mode for replicating between two Oracle Databases. I faced an issue and the Integrated Extract got ABENDED due to the below Error.

2014-11-12 10:30:43 ERROR OGG-02028 Failed to attach to logmining server Error code 1304, error message: ORA-01304: subordinate process error. Check alert and trace logs.2014-11-12 10:30:43 ERROR OGG-01668 PROCESS ABENDING.

I then analyzed the report of the Extract Process.,

 

Everything went fine, it seemed that there was some problem with the Logmining Server. On analyzing the alertlog I found the below error.,

ORA-1653: unable to extend table SYS.LOGMNRLT_123_COL$ by 64 in tablespace SYSAUX
krvxerpt: Errors detected in process 156, role builder.
krvxmrs: Leaving by exception: 604
Errors in file /ifc/oradba/admin/GGDB1/dbdump/diag/rdbms/GGDB1/GGDB1/trace/GGDB1_ms0d_24707164.trc:
ORA-00604: error occurred at recursive SQL level 1
ORA-01653: unable to extend table SYS.LOGMNRLT_123_COL$ by 64 in tablespace SYSAUX
LOGMINER: session#=20 (OGG$CAP_TRAEXT), builder MS0D pid=156 OS id=24707164 sid=770 stopped
Errors in file /ifc/oradba/admin/GGDB1/dbdump/diag/rdbms/GGDB1/GGDB1/trace/GGDB1_ms0d_24707164.trc:
ORA-01653: unable to extend table SYS.LOGMNRLT_123_COL$ by 64 in tablespace SYSAUX
Wed Nov 12 10:30:43 2014
LOGMINER: session#=20 (OGG$CAP_TRAEXT), preparer MS0E pid=184 OS id=17957008 sid=1036 stopped
Wed Nov 12 10:30:43 2014
LOGMINER: session#=20 (OGG$CAP_TRAEXT), reader MS0C pid=142 OS id=22282372 sid=1417 stopped

SYSAUX tablespace was filled. Increased the size of the SYSAUX tablespace. You can purge the SYSAUX tablespace.

Started the Extract and it ran well.

GGSCI (OGG1) 12> info extract TRAEXT

EXTRACT TRAEXT Last Started 2014-11-12 10:43 Status RUNNING
Checkpoint Lag 00:00:01 (updated 00:00:02 ago)
Process ID 17170546
Log Read Checkpoint Oracle Integrated Redo Logs
2014-11-12 10:47:50
SCN 1708.3296197740 (7339100339308)

 

Check whether Integrated capture started by seeing the ggserr.log

2014-11-12 10:43:08 INFO OGG-02068 Oracle GoldenGate Capture for Oracle, traext.prm: Integrated capture successfully attached to logmining server OGG$CAP_TRAEXT using OGGCapture API.
2014-11-12 10:43:09 INFO OGG-00993 Oracle GoldenGate Capture for Oracle, traext.prm: EXTRACT TRAEXT started.
2014-11-12 10:43:09 INFO OGG-01052 Oracle GoldenGate Capture for Oracle, traext.prm: No recovery is required for target file /ogg/dirdat/tt000000, at RBA 0 (file not opened).

SUMMARY:

SYSAUX tablespace should be considered while we go for GoldenGate Integrated Mode. Because, Unlike Classic Mode, here Logminer Plays an important role in Integrated Mode. Logminer is the one which captures the changes from the Redologs and gives it to the Extract Process to write it to the Trail files.

So by default Logminer uses the SYSAUX tablespace. From the output of the below query you can see it clearly.

col OCCUPANT_NAME for a30
col OCCUPANT_DESC for a60
col schema_name for a10

select OCCUPANT_NAME,OCCUPANT_DESC,SCHEMA_NAME,MOVE_PROCEDURE,SPACE_USAGE_KBYTES from V$SYSAUX_OCCUPANTS;

 

 

Leave a Reply

© 2020 ORACLE-SCN. All Rights Reserved.