Integration mode extraction process exception abend
Ggserr.log log log prompts are as follows
ERROR OGG-02028 Failed to attach to logmining server OGG$ABCD error 26927 - ORA-26927: altering an outbound server with a remote capture is not allowed
After querying MOS, it was found that the problem was a potential logminer error. There was a problem releasing PGA memory for the process, resulting in the process failure
Potential logminer bug.Problem when the PGA memory is being freed for the process resulting in the process failure.
The official gives three methods, and I use the second one here
Copyright (c) 2021, Oracle. All rights reserved. Oracle Confidential. Click to add to Favorites IE abends with ERROR OGG-02028 Failed to attach to logmining server ORA-26927 (Doc ID 2127219.1) To BottomTo Bottom In this Document Symptoms Changes Cause Solution References Applies to: Oracle GoldenGate - Version 11.2.1.0.3 to 11.2.1.0.39 [Release 11.2] Information in this document applies to any platform. Symptoms IE abends with ERROR OGG-02028 Failed to attach to logmining server OGG$ABCD error 26927 - ORA-26927: altering an outbound server with a remote capture is not allowed Changes None Cause Potential logminer bug.Problem when the PGA memory is being freed for the process resulting in the process failure. Solution -- Solution #1 -- Double the MAX_SGA_SIZE parameter for the affected Extract and restart. This is to see if the abend is related to memory. TRANLOGOPTIONS INTEGRATEDPARAMS (MAX_SGA_SIZE 512, parallelism 2) -- Solution #2 -- Un-register and register the extract again ggsci> UNREGISTER EXTRACT <ext_name> DATABASE ggsci> REGISTER EXTRACT <ext_name> DATABASE ggsci> start <ext_name> -- Solution #3 -- Downgrade to classic extract
The second pro test is available.
Article ID (DOC ID 2127219.1)
Similar Posts:
- Extraction process integration mode registration error, ogg-08221, OCI error ora-44004 invalid qualified SQL name
- Simple Steps to use LogMiner for finding high redo log generation
- [Solved] Oracle Error: SGA_MAX_SIZE cannot be set to more than MEMORY_TARGET
- How to Solve Ora-01109 Error: database not open
- ORA-609 : opiodr aborting process unknown ospid
- [Solved] Opatch apply Run Error: OPatch failed with error code 73
- [Solved] ORA-12162: TNS:net service name is incorrectly spe
- jhsdb jmap –heap –pid 1 Command Error [How to Solve]
- How to Solve Error: Oracle11g alarm log error ora-04030
- How to Solve __autoload() does not execute error