Kbase P140697: How to use an (AI) After Image file to find a long running transaction that was not completed?
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
16/08/2010 |
|
Status: Verified
GOAL:
How to use an (AI) After Image file to find a long running transaction that was not completed?
GOAL:
How to scan an ai file to identify a long running transaction?
GOAL:
Can an ai file be used to identify which user was running a long standing transaction that may have caused the bi file to grow?
GOAL:
How to use the rfutil dbname _C aimage scan verbose command to scan an ai file?
FACT(s) (Environment):
All Supported Operating Systems
Progress/OpenEdge Product Family
FIX:
The rfutil command with the aimage scan verbose option can be used to view the contents of an AI file. Reviewing the contents of an ai file is a tedious task and should not be entered into lightly. There is an abundance of information contained within the ai file. The username, when a transaction was started, and what DBkeys were modified within a transaction. The ai file however does not contain any information associated with what programs were running at the time. The ai file, in unison with client logging may help to give better insight from a 4GL perspective. For more information on how to configure client logging see solution: P9893, "How to turn on 4GLtracing within WebSpeed, AppServer and the 4GL Client?"
The command syntax is:
rfutil dbname -C aimage scan verbose -a aifilename > outputfilename
The output from this command will be redirected to an output file that you can review. The following is an example of an ai file where there is an active transaction is still in process. This active transaction could be resulting in excessive bi growth.
For the sample output provided below, note that we do not have a transaction end for the 1st transaction.
$ rfutil dbname -C aimage scan verbose -a dbname.a1
OpenEdge Release 10.1B03 as of Fri Nov 2 20:43:40 EDT 2007
After-image dates for this after-image file: (1633)
Last AIMAGE BEGIN Mon Feb 2 11:46:52 2009 (1640)
This is aimage file number 1 since the last AIMAGE BEGIN. (1642)
This file was last opened for output on Mon Feb 2 11:46:56 2009. (1643)
Trid: 0 code = RL_INMEM version = 3 (12528)
Trid: 0 dbkey = 0 update counter = 0 (12530)
Trid: 0 code = RL_LSTMOD version = 2 (12528)
Trid: 0 area = 6 dbkey = 32 update counter = 107 (12529)
Trid: 1481 Mon Feb 2 11:47:44 2009. (2598) <=================== Information as to when the 1st transaction was started
Trid: 1481 User Id: osborne (12531) <=================== Information associated with the user that started the 1st transaction
Trid: 1481 code = RL_TBGN version = 1 (12528) <=================== The beginning of the 1st transaction
Trid: 1481 dbkey = 0 update counter = 0 (12530)
Trid: 1481 code = RL_SEINC version = 1 (12528)
Trid: 1481 area = 6 dbkey = 96 update counter = 40 (12529)
Trid: 1481 code = RL_TMSAVE version = 2 (12528)
Trid: 1481 dbkey = 0 update counter = 0 (12530)
Trid: 1481 code = RL_RMCR version = 2 (12528)
Trid: 1481 area = 9 dbkey = 1344 update counter = 22 (12529)
Trid: 1481 code = RL_CXINS version = 2 (12528)
Trid: 1481 area = 10 dbkey = 640 update counter = 220 (12529)
Trid: 1481 code = RL_IXDEL version = 2 (12528)
Trid: 1481 dbkey = 0 update counter = 0 (12530)
Trid: 1481 code = RL_BKREPL version = 1 (12528)
Trid: 1481 area = 10 dbkey = 640 update counter = 221 (12529)
Trid: 1481 code = RL_CXINS version = 2 (12528)
Trid: 1481 area = 10 dbkey = 640 update counter = 222 (12529)
Trid: 1481 code = RL_CXINS version = 2 (12528)
Trid: 1481 area = 10 dbkey = 544 update counter = 52 (12529)
Tri.d: 1481 code = RL_CXINS version = 2 (12528)
Trid: 1481 area = 10 dbkey = 224 update counter = 1120 (12529)
Trid: 1482 Mon Feb 2 11:47:50 2009. (2598) <=================== Information as to when the 2nd transaction was started
Trid: 1482 User Id: osborne (12531) <=================== Information associated with the user that started the 2nd transaction
Trid: 1482 code = RL_TBGN version = 1 (12528) <=================== The beginning of the 2nd transaction
Trid: 1482 dbkey = 0 update counter = 0 (12530)
Trid: 1482 code = RL_TMSAVE version = 2 (12528)
Trid: 1482 dbkey = 0 update counter = 0 (12530)
Trid: 1482 code = RL_CXREM version = 2 (12528)
Trid: 1482 area = 10 dbkey = 256 update counter = 224 (12529)
Trid: 1482 code = RL_CXINS version = 2 (12528)
Trid: 1482 area = 10 dbkey = 512 update counter = 29 (12529)
Trid: 1482 code = RL_RMCHG version = 2 (12528)
Trid: 1482 area = 9 dbkey = 96 update counter = 29 (12529)
Trid: 1482 Mon Feb 2 11:47:50 2009. (2598) <=================== Information as to when the 2nd transaction was ended
Trid: 1482 code = RL_TEND version = 1 (12528) <=================== The end of the 2nd transaction
Trid: 1482 dbkey = 0 update counter = 0 (12530)
18 notes were processed. (1634)
0 in-flight transactions. (3785)
2 transactions were started. (1635)
1 transactions were completed. (11138)
At the end of the .ai file, 1 transactions were still active. (1636) <============ Number of active transactions at the end of the AI file..