why my extract is so slow, some goldengate processes freezes, they still are tagged as RUNNING but they don't work.
(Doc ID 2178817.1)
Last updated on MARCH 21, 2019
Applies to:Oracle GoldenGate - Version 220.127.116.11.2 and later
Information in this document applies to any platform.
On the Windows operating system, after a moment, some goldengate processes freezes, they still are tagged as RUNNING but they don't work.
Every 5 minutes, we launch a backup log via a stored proc:
BACKUP LOG @p_base TO DISK = @v_temp_chemin WITH
NOFORMAT, NOINIT, NAME = @v_nom_sauvegarde, DESCRIPTION = @v_description_sauvegarde,
SKIP, NOUNLOAD, NO_COMPRESSION, STATS = 10, CHECKSUM
When we stop the backup job, the replication works well and processes don't freeze, but the size of journal file is growing up.
The customer's backup strategy is likely causing this issue. There is no evidence that the extract is hanging. It is likely just taking a very long time because of 2 reasons:
1.The customer is not only appending their tran logs but they are also using the same file for their full database backup. The more backups in the file, the longer it is going to take. The GoldenGate manual states that we do not recommend appended backups due to this reason.
2. The networked backup is also adding to the latency problem
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