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

MOSC Banner

Repairing Corrupted Standby DB Indexes

edited May 28, 2009 12:21AM in High Availability Data Guard, Sharding and Global Data Services (MOSC) 4 commentsAnswered
Hello,

Our production SAP BW database is connected to standby database in a remote data center.  Every year we activate and test the standby database twice.  To speed the daily BW data loads, we have more than 250,000 indexes created with the nologging option.  The problem is that changes made to these indexes are not shipped to the standby DB because they are not logged in the archive logs. After the standby DB gets activated, these indexes are corrupt.  It takes us around 14 hours to rebuild these indexes before our BW users could test the activated system. We rebuild the indexes using scripts with "alter index

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