Kbase P171241: Getting 834 error even though the database is marked backed up prior to running the aimage begin com
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
21/09/2010 |
|
Status: Unverified
SYMPTOM(s):
Getting 834 error even though the database is marked backed up prior to running the aimage begin command.
** Cannot do AIMAGE/2PHASE BEGIN. You must backup the database first. (834)
There was an active transaction before the database was marked backed up:
[2010/08/06@12:15:23.345-0400] P-13410 T--1210628416 I RFUTIL : (1636) At the end of the .ai file, 1 transactions were still active.
Each time the error occurs, there is a message 7163 in the database log file when starting after imaging.
Begin Physical Undo transactions at block offset (7163)
Database had an ai file roll forwarded against the database prior to the Mark backed up command being ran against the database.
FACT(s) (Environment):
Command being issued: proutil dbname -C aimage begin
The database was marked as backed up:
[2010/08/06@12:15:23.401-0400] P-13463 T--1210526016 I RFUTIL : (451) Mark backedup session begin for root on /dev/pts/0.
[2010/08/06@12:15:23.402-0400] P-13463 T--1210526016 I RFUTIL : (334) Mark backedup session end.
Return code of the command used to back up the database is successful.
If the mark backedup command is re-run after receiving the 834 error, after imaging can then be successfully enabled.
All Supported Operating Systems
Progress/OpenEdge Product Family
CAUSE:
rfutil dbname -C aimage begin initiates a warm start / crash recovery within a database. If a transaction is applied or backed out in this database as a result of the warm start/crash recovery, the aimage begin option to rfutil will fail as a result of the changes made to the database.
FIX:
If making use of a script to mark a database as backed up and then start after imaging, you may want to check the return code associated with rfutil dbname -C aimage begin command. If the return code is not = to 0, then grep the database log file to see if you can detect message (7136) which indicates that a transaction was applied to the database since the last mark backed up command was issued. Take another backup of the database (because a change was made to the database). Then mark the database as backed up (rfutil dbname -C mark backedup) again and then restart after imaging (rfutil dbname -C aimage begin).
Another option would be that after applying an ai file to a database, prior to attempting to initiate after imaging against the database, you should truncate your bi file. The truncation would result in the database going through crash recovery which would also bring the database into a consistent state prior to the issuing of the mark backedup command. If you choose to make use of the truncate command, please see solution P2676, "Grow the before image file (.bi) with bigrow to improve performance". This solution will give you information regarding making use of the bigrow option to proutil that will help to minimize the performance impact associated with truncating a bi file.