An OpenEdge database which was in use when it was created using an operating system copy operation is not considered a viable database for use.
- You are likely to see timestamp mismatch and/or record fragmentation errors when you start to use it.
- Any data that was in memory at the time of the copy will be missing.
- This may result in crashes when trying to access the database.
In a multi-user database, where an Enterprise Database license is installed, the database can be quiesced with the PROQUIET feature to stall the database during an OS-COPY operation in order to avoid problems with the resultant copy.
Syntax
proquiet dbname -C {{ enable [ nolock ]| disable }
Note: The quite point is not enabled until the message "(5583) Quiet point has been enabled by the broker." shows in the DB log.
For further information refer to Articles:
