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

MOSC Banner

applying Archive is to slow on physical standby database

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

Primary DB ==Log Shipping to ==> Physical Standby DB (Its in mount mode) ====Again Log shipping to ====> Cascade Standby DB (This will convert as Snapshot standby during Day time and convert to physical standby during night time.


> Here the issue is log apply slow on Cascade Standby after converted to Physical standby, earlier it was took only 2 hours to catchup older archives and get in to sync.


> But last 2 days it was taking more than 12 hours.


> As per CT resent changes on the Primary DB was Index rebuild and Gather stats.


> After that Actual standby not reporting any issues, only case cade standby taking time to apply Archive gaps which was generated during Snapshot time.

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