High Availability Data Guard, Sharding and Global Data Services (MOSC)

MOSC Banner

Is DG smarter in 23c?

in High Availability Data Guard, Sharding and Global Data Services (MOSC) 2 comments

I had an issue with the network connection for a 19c DG standby database this weekend. It started just after I left the office on Friday (of course). This caused the standby to get very far behind, and the primary to start complaining on our backup summary report about not being able to remove archive log files due to being needed by standby.

So I came in today, fixed the issue, and started the slow standby catch up. But...

For whatever reason the DG code causes the primary to send not only the files close to where it left off (good), but also some of the latest files. When you are hundreds of log files behind, with only so much room for those logs to stack up on the standby, you know what will happen. Out of disk space. The code recognizes this on the standby and it deletes some of those newer unnecessary (for now) log files. And it stays with this tactic for a bit, but then falls back into the shiny new object is good trap

Howdy, Stranger!

Log In

To view full details, sign in to My Oracle Support Community.

Register

Don't have a My Oracle Support Community account? Click here to get started.

Category Leaderboard

Top contributors this month

Instructions for posting

×

1. Select a discussion category from the picklist.


2. Enter a title that clearly identifies the subject of your question.


3. In the body, insert detailed information, including Oracle product and version.


Please abide by the Oracle Community guidelines and refrain from posting any customer or personally identifiable information (PI/CI).


Cloud / Fusion customers - Our Cloud community has moved! Please go to Cloud Customer Connect .


New to My Oracle Support Community? Visit our Welcome Center

MOSC Help Center