Identify End of Recovery on the Client Machine With a Consistent Notification Through DB_EVENT_REP_STARTUPDONE
(Doc ID 471844.1)
Last updated on AUGUST 23, 2021
Applies to:
Berkeley DB - Version 4.6.21 and laterInformation in this document applies to any platform.
NOTE: In the images and/or the document content below, the user information, the object name information, the database name information and data used represents fictitious data from the Oracle sample schema(s) or Public Documentation delivered with an Oracle database product or other training material. Any similarity to actual persons, living or dead, is purely coincidental and not intended in any manner.
Symptoms
When trying to exactly determine when the startupdone procedure is fully done on the client machine, and it's databases are ready for read-only access, the DB_EVENT_REP_STARTUPDONE event notification cannot be used because:
- DB_EVENT_REP_STARTUPDONE is fired too early (before recovery actually completes);
- DB_EVENT_REP_STARTUPDONE is not fired after each launch of the replication process on the client machine, but only once upon the initial launch.
The following steps should reproduce the issue:
- Load the primary with a lot of data;
- Launch the replication process on the client machine;
- Try to open a database on the client machine;
- BDB sleeps and then returns an error: "Operation locked out. Waiting for replication lockout to complete".
Changes
Cause
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
| Symptoms |
| Changes |
| Cause |
| Solution |
| Solution |