Kbase P184676: rfutil roll forward seems to stop being able to apply ai files to a hot backup / hot standby databas
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
29/03/2011 |
|
Status: Unverified
SYMPTOM(s):
rfutil roll forward seems to stop being able to apply ai files to a hot backup / hot standby database intermittently.
Can apply ai files to hot standby 99% of the time.
Problem is noticed when ai roll forward stops reporting information in the database log file about the ai file being applied. (Like # of in-flight transactions as well as new and completed transactions once the ai file is applied).
Example of results when rolling forward an ai file prior to experiencing the problem:
RFUTIL : (451) Roll forward session begin for root on batch.
RFUTIL : (515) ** This session is running with the non-raw (-r) parameter.
RFUTIL : (5326) Begin Physical Redo Phase at 5120 .
RFUTIL : (7161) Physical Redo Phase Completed at blk 6620 off 4187 upd 0.
RFUTIL : (13547) At end of Physical redo, transaction table size is -(.
RFUTIL : (660) Beginning roll forward of after-image file /pathname/of/aifile/being/applied/123456789.ai.
RFUTIL : (1633) After-image dates for this after-image file:
RFUTIL : (1640) Last AIMAGE BEGIN Sat Jul 24 00:13:23 2010
RFUTIL : (1641) Last AIMAGE NEW Fri Dec 3 17:33:54 2010
RFUTIL : (1642) This is aimage file number 3207 since the last AIMAGE BEGIN.
RFUTIL : (1643) This file was last opened for output on Fri Dec 3 18:17:48 2010.
RFUTIL : (1634) 386263 notes were processed.
RFUTIL : (3785) 1 in-flight transactions.
RFUTIL : (1635) 24757 transactions were started.
RFUTIL : (11138) 24757 transactions were completed.
RFUTIL : (1636) At the end of the .ai file, 1 transactions were still active.
RFUTIL : (662) Roll forward completed.
RFUTIL : (334) rfutil -C roll forward session end.
Example of results when rolling forward an ai file and the problem or condition occurs:
RFUTIL : (451) Roll forward session begin for root on batch.
RFUTIL : (515) ** This session is running with the non-raw (-r) parameter.
RFUTIL : (5326) Begin Physical Redo Phase at 7168 .
RFUTIL : (7161) Physical Redo Phase Completed at blk 9117 off 10916 upd 158057.
RFUTIL : (13547) At end of Physical redo transaction table size is -(.
RFUTIL : (334) rfutil -C roll forward session end.
All ai files that attempt to be applied after the problem occurs, will result in the same behavior or lack of transactional information being reported when they are being applied.
Hot standby is no longer viable at this point.
Online backup has to be taken from the production database and then restored on the hot standby in order to now be able to start applying ai files again without the bad behavior.
Issue only being experienced on 2 sites.
Issue not being experienced 100% of the time. In other words, during other online schema changes, they do not see this behavior).
Has been able to take a previous backup, restore it and never truncate the bi file on the hot backup / standby database and will still have a problem with these same ai files being applied on these machines.
If the hot backup / hot standby database is started after applying all ai files including the ones without transactional information showing above, the schema changes and other completed changes made to the production database are missing. Even though no errors were reported.
FACT(s) (Environment):
ia64 (Itanium)
OpenEdge 10.1C04 64-bit Service Pack
No errors being reported when rolling forward the ai files.
No errors being reported in the production database where the ai files were created initially.
rfutil dbname -C aimage scan verbose >outfile for ai files that are not showing the transactional type of information does actually show in-flight transactions and new transactions being started and ended. (e.g. transactional information).
Same online schema changes are able to be applied to many other sites (28 sites).
Issue does not appear to be associated with specific types of online schema changes.
The bi file is being truncated on the hot backup / standby machine sometimes when no in-flight transactions are reported.
CHANGE:
Occurs periodically after online schema changes have been made to the production database and ai files created during and after that period are being applied to the hot backup / standby database.
CAUSE:
Wrong binaries installed on the hot backup / standby machine is causing the issue. The production machine is HP-UX Itanium machine with OpenEdge bits for HP Itanium machine. The hot backup / standby machine is an HP-UX Itatium machine but has OpenEdge PA-RISC bits installed on the machine.
CAUSE:
Bug# OE00206134
FIX:
Progress does not support running our products produced for one platform on another platform. This is not supported nor tested. Although an issue exists, it will not be investigated further as this is an unsupported configuration.
If the correct OpenEdge binaries for the HP-UX Itanium platform are installed on the HP-UX Itanium platform the problem no longer occurs.