on 07-23-2014 10:43 AM
Hi,
I'm scripting a validation script on linux and can't find any spec on exitstatus of dbsrv12 when it is started with the -ad option to apply transaction log files.
And I'm finding the route to validate a backup a bit cumbersome. First make a copy of the last full backup, and all the incremental transaction log files.
Then apply all transactions log files.
Make another copy, so that you could apply new transaction logs to the one you have.
Validate the copy.
Anyone who have a validation script for linux. Or windows, and I'll translate it to unix.
Best regards
Ove Halseth
The exit codes for the server process are defined here:
I agree that the validation process is cumbersome and needs some work. We are working on making it simpler in a future release.
hth,
--Jason
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Ove,
And I'm finding the route to validate a backup a bit cumbersome. First make a copy of the last full backup, and all the incremental transaction log files. Then apply all transactions log files.
Just a quick note that you do not neccessarily have to do this specific procedure today to validate the database and transaction log files:
BACKUP DATABASE DIRECTORY 'c:\\backup'
WAIT BEFORE START
WITH CHECKPOINT LOG NO COPY
BACKUP DATABASE DIRECTORY 'c:\\backup'
WAIT BEFORE START
WITH CHECKPOINT LOG RECOVER
dbbackup -wb -k nocopy ...
dbbackup -wb -k recover ...
dbsrv12 -n validate_engine c:\backup\mydatabase.db -r
Regards,
Jeff Albion
SAP Active Global Support
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
91 | |
10 | |
10 | |
9 | |
9 | |
7 | |
6 | |
5 | |
5 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.