G
George Potemkin
Guest
Fortunately the documentation is wrong. On screen: 13:59:38 BROKER 0: Multi-user session begin. (333) 13:59:38 BROKER 0: Crash Recovery Status Interval (-crStatus): 1 seconds (18186) 13:59:38 BROKER 0: Crash Recovery Transaction Display (-crTXDisplay): ON (18187) 13:59:38 BROKER 0: Begin Physical Redo Phase at 2880 . (5326) 13:59:38 BROKER 0: Physical Redo Phase Completed at blk 2976 off 8144 upd 2975. (7161) 13:59:38 BROKER 0: At end of Physical redo, transaction table size is 128. (13547) 13:59:38 BROKER 0: Begin Physical Undo 1 transactions at block 2976 offset 8180 (7163) 13:59:38 BROKER 0: Transaction 404 by user 5 at 2018/02/25@13:57:43. Counter: 26 13:59:39 BROKER 0: Physical Undo 30% at block 2064. 913 blocks processed in 1 seconds. Counter: 58 13:59:40 BROKER 0: Physical Undo 59% at block 1186. 1791 blocks processed in 2 seconds. Counter: 44 13:59:41 BROKER 0: Physical Undo 87% at block 228. 2621 blocks processed in 3 seconds. Counter: 31 13:59:41 BROKER 0: Physical Undo Phase Completed at 1086 . (5331) 13:59:41 BROKER 0: Begin Logical Undo Phase, 1 incomplete transactions are being backed out. (7162) 13:59:41 BROKER 0: Logical Undo Phase begin at Block 1086 Offset 6840. (11231) 13:59:41 BROKER 0: Logical Undo 100% at block 1086. 2915 blocks processed in 3 seconds. Counter: 26 13:59:41 BROKER 0: Logical Undo Phase completed at block 1086, offset 6840. (12095) In db log: [2018/02/25@13:59:38.016+0300] P-19741 T-140406907832064 I BROKER 0: (333) Multi-user session begin. [2018/02/25@13:59:38.272+0300] P-19741 T-140406907832064 I BROKER 0: (18186) Crash Recovery Status Interval (-crStatus): 1 seconds [2018/02/25@13:59:38.272+0300] P-19741 T-140406907832064 I BROKER 0: (18187) Crash Recovery Transaction Display (-crTXDisplay): ON [2018/02/25@13:59:38.272+0300] P-19741 T-140406907832064 I BROKER 0: (5326) Begin Physical Redo Phase at 2880 . [2018/02/25@13:59:38.279+0300] P-19741 T-140406907832064 I BROKER 0: (7161) Physical Redo Phase Completed at blk 2976 off 8144 upd 2975. [2018/02/25@13:59:38.279+0300] P-19741 T-140406907832064 I BROKER 0: (13547) At end of Physical redo, transaction table size is 128. [2018/02/25@13:59:38.280+0300] P-19741 T-140406907832064 I BROKER 0: (7163) Begin Physical Undo 1 transactions at block 2976 offset 8180 [2018/02/25@13:59:38.280+0300] P-19741 T-140406907832064 I BROKER 0: (-----) Transaction 404 by user 5 at 2018/02/25@13:57:43. Counter: 26 [2018/02/25@13:59:41.614+0300] P-19741 T-140406907832064 I BROKER 0: (5331) Physical Undo Phase Completed at 1086 . [2018/02/25@13:59:41.614+0300] P-19741 T-140406907832064 I BROKER 0: (7162) Begin Logical Undo Phase, 1 incomplete transactions are being backed out. [2018/02/25@13:59:41.614+0300] P-19741 T-140406907832064 I BROKER 0: (11231) Logical Undo Phase begin at Block 1086 Offset 6840. [2018/02/25@13:59:41.618+0300] P-19741 T-140406907832064 I BROKER 0: (12095) Logical Undo Phase completed at block 1086, offset 6840. I don't understand why Progress writes the "Transaction by user at" message to both destinations because the message in promsgs file does not have the "%B" tag and the message is not dublicated/embedded into the Progress executables: In promsgs file: Transaction %l by user %d at %s. Counter: %l Another side note: as we see in this message the recovery notes contains the user numbers but 'rfutil -S scan verbove' reports only user's names stored in RL_TBGN notes. It's very inconvenient when we need tp parse the transactions generated by batch processes that share the same login name. Conclusion: use the -crTXDisplay parameter to start a database. Especially after db crash.
Continue reading...
Continue reading...
