Displays an after-image journal (.aij) file, a backed up .aij
file (.aij if the backup is on disk, .aij_rbf if the .aij file
was backed up to tape), or an optimized after-image journal
(.oaij) file in ASCII format. Use this command to examine the
contents of your .aij, .aij_rbf, or .oaij file. Whenever the
term .aij file is used in this RMU Dump After_Journal command
description, it refers to .oaij and .aij_rbf files, as well as
.aij files.
An .aij file contains header information and data blocks. Header
information describes the data blocks, which contain copies of
data stored in the database file.
1 – Description
The RMU Dump After_Journal command specifies an .aij file, not a
database file, as its parameter, and is a separate command from
the RMU Dump command used to display database areas and header
information.
The .aij file is in binary format. This command translates the
binary file into an ASCII display format.
The RMU Dump After_Journal command always includes the header of
the .aij file in the display. You can use the Nodata qualifier to
exclude data blocks from the display entirely, or you can use the
Start and End qualifiers to restrict the data block display to
a specific series of blocks. If you do not specify any of these
qualifiers, Oracle RMU includes all data blocks.
2 – Format
(B)0[mRMU/Dump/After_Journal aij-file-name
[4mFile[m [4mQualifiers[m x [4mDefaults[m
x
/Active_IO=max-reads x /Active_IO=3
/Area=integer x None
/[No]Data x /Data
/Encrypt=({Value=|Name=}[,Algorithm=]) x See description
/End=integer x See description
/First=(select-list) x See description
/Format={Old_File|New-Tape} x Format=Old_File
/Label=(label-name-list) x See description
/Larea=integer x None
/Last=(select-list) x See description
/Librarian[=options] x None
/Line=integer x None
/[No]Media_Loader x See description
/Only=(select-list) x See description
(B)0[m/Option={Statistics|Nostatistics} x Option=Statistics
/Output=file-name x /Output=SYS$OUTPUT
/Page=integer x None
/Prompt={Automatic|Operator|Client} x See description
/No]Rewind x Norewind
/Start=integer x See description
/State=Prepared x See description
3 – Parameters
3.1 – aij-file-name
The .aij file you want to display. The default file type is .aij.
For .oaij files, you must specify the file type of .oaij.
4 – Command Qualifiers
4.1 – Active IO
Active_IO=max-reads
Specifies the maximum number of read operations from a backup
device that the RMU Dump After_Journal command will attempt
simultaneously. This is not the maximum number of read operations
in progress; that value is the product of active system I/O
operations.
The value of the
Active_IO qualifier can range from 1 to 5. The default value
is 3. Values larger than 3 can improve performance with some tape
drives.
4.2 – Area
Area=integer
Identifies a physical database storage area by number. Dump
output is limited to the specified area. The minimum value is
1.
4.3 – Data
Data
Nodata
Specifies whether you want to display data blocks of the .aij
file, or just the .aij file header.
The Data qualifier is the default. It causes the display of the
.aij file data blocks (in addition to the file header) in an
ASCII display format.
The Nodata qualifier limits the display to the record headers of
the .aij file.
4.4 – Encrypt
Encrypt=({Value=|Name=}[,Algorithm=])
The Encrypt qualifier decrypts the file of an after-image journal
backup.
Specify a key value as a string or the name of a predefined key.
If no algorithm name is specified the default is DESCBC. For
details on the Value, Name and Algorithm parameters type HELP
ENCRYPT at the OpenVMS prompt.
This feature requires the OpenVMS Encrypt product to be installed
and licensed on your system.
This feature only works for a newer format backup file which
has been created using the Format=New_Tape qualifier. You must
specify the Format=New_Tape qualifier with this command if you
use the Encrypt qualifier.
4.5 – End
End=integer
Specifies the number of the last data block that you want to
display. The default integer is the number of the last data block
in the file. If you do not use the End qualifier, Oracle RMU
displays the entire .aij file.
4.6 – First
First=(select-list)
Allows you to specify where you want the dump output to begin.
(See the Last=(select-list) qualifier for the end of the range.)
If you specify more than one keyword in the select-list, separate
the keywords with commas and enclose the list in parentheses.
If you specify multiple items in the select list, the first
occurrence is the one that will activate Oracle RMU. For example,
if you specify First=(Block=100,TSN=0:52),the dump will start
when either block 100 or TSN 52 is encountered.
The First and Last qualifiers are optional. You can specify both,
either, or neither of them. The keywords specified for the First
qualifier can differ from the keywords specified for the Last
qualifier.
The select-list of the First qualifier consists of a list of one
or more of the following keywords:
o BLOCK=block-number
Specifies the first block in the AIJ journal.
o RECORD=record-number
Specifies the first record in the AIJ journal. This is the
same as the existing Start qualifier, which is still supported
but obsolete.
o TID=tid
Specifies the first TID in the AIJ journal.
o TIME=date_time
Specifies the first date and time in the AIJ journal, using
absolute or delta date-time format.
o TSN=tsn
Specifies the first TSN in the AIJ journal, using the standard
[n:]m TSN format.
By default, the entire .aij file is dumped.
4.7 – Format
Format=Old_File
Format=New_Tape
Specifies whether the backup or optimized .aij file was written
in the old (disk-optimized) or the new (tape-optimized) format.
If you enter the RMU Dump After_Journal command without the
Format qualifier, the default is the Format=Old_Tape qualifier.
You must specify the same Format qualifier as was used with the
RMU Backup After_Journal command or the RMU Optimize After_
Journal command. If your .aij file resides on disk, you should
use the Format=Old_File qualifier.
If you specified the Format=Old_File qualifier when you optimized
or backed up the .aij file to tape, you must mount the backup
media by using the DCL MOUNT command before you issue the RMU
Dump After_Journal command. Because the RMU Dump After_Journal
command uses RMS to read the tape, the tape must be mounted as
an OpenVMS volume (that is, do not specify the /FOREIGN qualifier
with the MOUNT command).
If you specify the Format=New_Tape qualifier, you must mount the
backup media by using the DCL MOUNT /FOREIGN command before you
issue the RMU Dump After_Journal command.
Similarly, if you specify OpenVMS access (you do not specify
the /FOREIGN qualifier on the DCL MOUNT command) although your
.aij backup was created using the Format=New_Tape qualifier, you
receive an RMU-F-MOUNTFOR error.
The following tape qualifiers have meaning only when used in
conjunction with the Format=New_Tape qualifier:
Active_IO
Label
Rewind
4.8 – Label
Label=(label-name-list)
Specifies the 1- to 6-character string with which the volumes
of the backup file have been labeled. The Label qualifier is
applicable only to tape volumes. You must specify one or more
label names when you use the Label qualifier.
You can specify a list of tape labels for multiple tapes. If you
list multiple tape label names, separate the names with commas
and enclose the list of names within parentheses.
In a normal dump after-journal operation, the Label qualifier
you specify with the RMU Dump After_Journal command should be
the same Label qualifier you specified with the RMU Backup After_
Journal command to back up your after-image journal file.
The Label qualifier can be used with indirect file references.
See Indirect-Command-Files for more information.
4.9 – Larea
Larea=integer
Identifies a logical database storage area by number. Dump output
is limited to the specified area. The minimum value is 0.
4.10 – Last
Last=(select-list)
Allows you to specify where you want the dump output to end. (See
the First=(select-list) qualifier for the beginning range.) If
you specify more than one keyword in the select-list, separate
the keywords with commas and enclose the list in parentheses.
If you specify multiple items in the select list, the first
occurrence is the one that will activate Oracle RMU.
The First and Last qualifiers are optional. You can specify both,
either, or neither of them. The keywords specified for the First
qualifier can differ from the keywords specified for the Last
qualifier.
The select-list of the Last qualifier consists of a list of one
or more of the following keywords:
o BLOCK=block-number
Specifies the last block in the AIJ journal.
o RECORD=record-number
Specifies the last record in the AIJ journal. This is the same
as the existing End qualifier, which is still supported but
obsolete.
o TID=tid
Specifies the last TID in the AIJ journal.
o TIME=date_time
Specifies the last date and time in the AIJ journal, using
absolute or delta date-time format.
o TSN=tsn
Specifies the last TSN in the AIJ journal, using the standard
[n:]m TSN format.
By default, the entire .aij file is dumped.
4.11 – Librarian
Librarian=options
Use the Librarian qualifier to restore files from data archiving
software applications that support the Oracle Media Management
interface. The file name specified on the command line identifies
the stream of data to be retrieved from the Librarian utility. If
you supply a device specification or a version number it will be
ignored.
Oracle RMU supports retrieval using the Librarian qualifier only
for data that has been previously stored by Oracle RMU using the
Librarian qualifer.
The Librarian qualifier accepts the following options:
o Trace_file=file-specification
The Librarian utility writes trace data to the specified file.
o Level_Trace=n
Use this option as a debugging tool to specify the level of
trace data written by the Librarian utility. You can use a
pre-determined value of 0, 1, or 2, or a higher value defined
by the Librarian utility. The pre-determined values are :
- Level 0 traces all error conditions. This is the default.
- Level 1 traces the entry and exit from each Librarian
function.
- Level 2 traces the entry and exit from each Librarian
function, the value of all function parameters, and the
first 32 bytes of each read/write buffer, in hexadecimal.
o Logical_Names=(logical_name=equivalence-value,...)
You can use this option to specify a list of process logical
names that the Librarian utility can use to specify catalogs
or archives where Oracle Rdb backup files are stored,
Librarian debug logical names, and so on. See the specific
Librarian documentation for the definition of logical names.
The list of process logical names is defined by Oracle RMU
prior to the start of any Oracle RMU command that accesses the
Librarian utility.
The following OpenVMS logical names must be defined for use with
a Librarian utility before you execute an Oracle RMU backup or
restore operation. Do not use the Logical_Names option provided
with the Librarian qualifier to define these logical names.
o RMU$LIBRARIAN_PATH
This logical name must be defined so that the shareable
Librarian image can be loaded and called by Oracle RMU backup
and restore operations. The translation must include the file
type (for example, .exe), and must not include a version
number. The shareable Librarian image must be an installed
(known) image. See the Librarian utility documentation for
the name and location of this image and how it should be
installed.
o RMU$DEBUG_SBT
This logical name is not required. If it is defined, Oracle
RMU will display debug tracing information messages from
modules that make calls to the Librarian shareable image.
You cannot use device specific qualifiers such as Rewind,
Density, or Label with the Librarian qualifier because the
Librarian utility handles the storage meda, not Oracle RMU.
4.12 – Line
Area=integer
Identifies a database line number. Dump output is limited to
the specified line. The minimum value is 0. This qualifier is
intended for use during analysis or debugging.
4.13 – Media Loader
Media_Loader
Nomedia_Loader
Use the Media_Loader qualifier to specify that the tape device
from which the file is being read has a loader or stacker. Use
the Nomedia_Loader qualifier to specify that the tape device does
not have a loader or stacker.
By default, if a tape device has a loader or stacker, Oracle
RMU should recognize this fact. However, occasionally Oracle RMU
does not recognize that a tape device has a loader or stacker.
Therefore, when the first tape has been read, Oracle RMU issues a
request to the operator for the next tape, instead of requesting
the next tape from the loader or stacker. Similarly, sometimes
Oracle RMU behaves as though a tape device has a loader or
stacker when actually it does not.
If you find that Oracle RMU is not recognizing that your tape
device has a loader or stacker, specify the Media_Loader
qualifier. If you find that Oracle RMU expects a loader or
stacker when it should not, specify the Nomedia_Loader qualifier.
4.14 – Only
Only=(select-list)
Allows you to specify one select list item to output. (See also
the First=(select-list) and Last=(select-list) qualifiers for
specifying a range.) If you specify more than one keyword in the
select-list, separate the keywords with commas and enclose the
list in parentheses. If you specify multiple items in the select
list, the first occurrence is the one that will activate Oracle
RMU.
The Only qualifier is optional.
The select-list of the Only qualifier consists of a list of one
or more of the following keywords:
o TID=tid
Specifies a TID in the AIJ journal.
o TSN=tsn
Specifies a TSN in the AIJ journal, using the standard [n:]m
TSN format.
o Type=type-list
Specifies the types of records to be dumped. The type-list
consists of a list of one or more of the following keywords:
- Ace_header
Type=A records
- Checkpoint
Type=B records
- Close
Type=K records
- Commit
Type=C records
- Data
Type=D records
- Group
Type=G records
- Information
Type=N records
- Open
Type=O records
- Optimize_information
Type=I records
- Prepare
Type=V records
- Rollback
Type=R records
By default, the entire .aij file is dumped.
4.15 – Option
Option=Statistics
Option=Nostatistics
The Option=Statistics qualifier specifies that you want Oracle
RMU to include statistics on how frequently database pages are
referenced by the data records in the .aij file. In addition, if
the database root file is available, the output created by the
Options=Statistics qualifier includes the value to specify for
the Aij_Buffers qualifier of the RMU Recover command. If several
.aij files will be used in your recovery operation, perform an
RMU Dump After_Journal on each .aij file and add the recommended
Aij_Buffer values. Use the total as the value you specify with
the Aij_Buffers qualifier. See Example 2 in the Examples help
entry under this command for an example using this qualifier.
Note that the value recommended for the RMU Recover command's
Aij_Buffers qualifier is the exact number of buffers required
by the data records in the specified .aij file. If you specify
fewer buffers, you may see more I/O, but you will not necessarily
see performance degrade. (Performance also depends on whether
asynchronous batch-writes are enabled.)
Using more buffers than are recommended may result in your
process doing more paging than required, and if so, performance
degrades.
If you specify the recommended value, note that this does not
mean that no buffers are replaced during the recovery operation.
The Oracle RMU buffer replacement strategy is affected by
whether asynchronous prefetches and asynchronous batch-writes are
enabled, and on the contents of the buffers before the recovery
operation begins.
If the database root file is not available, the Option=Statistics
qualifier does not provide a value for the RMU Recover command's
Aij_Buffers qualifier. However, it does provide the statistics on
the frequency with which each page is accessed.
Specify the Option=Nostatistics qualifier to suppress .aij
statistics generation.
The default for the RMU Dump After_Journal command is
Option=Statistics.
4.16 – Output
Output=file-name
Specifies the name of the file where output will be sent. The
default is SYS$OUTPUT. The default file type is .lis, if you
specify a file name.
4.17 – Page
Page=integer
Identifies a database page number. Dump output is limited to
the specified page. The minimum value is 1. This qualifier is
intended for use during analysis or debugging.
4.18 – Prompt
Prompt=Automatic
Prompt=Operator
Prompt=Client
Specifies where server prompts are to be sent. When you specify
Prompt=Automatic, prompts are sent to the standard input device,
and when you specify Prompt=Operator, prompts are sent to the
server console. When you specify Prompt=Client, prompts are sent
to the client system.
4.19 – Rewind
Rewind
Norewind
Specifies that the magnetic tape that contains the backup file
will be rewound before processing begins. The tape is searched
for the backup file starting at the beginning-of-tape (BOT). The
Norewind qualifier is the default and causes a search for the
backup file to be started at the current tape position.
The Rewind and Norewind qualifiers are applicable only to tape
devices.
4.20 – Start
Start=integer
Specifies the number of the first data block that you want to
display. If you do not use the Start qualifier, the display
begins with the first record in the .aij file.
4.21 – State
State=Prepared
Specifies a list of all records associated with unresolved
transactions.
For more information on listing unresolved transactions with
the RMU Dump After_Journal command, see the Oracle Rdb7 Guide to
Distributed Transactions.
5 – Usage Notes
o The First and Last qualifiers have been added to make
dumping portions of the .aij file easier. The Start and End
qualifiers were intended to provide similar functionality,
but are difficult to use because you seldom know, nor can you
determine, the AIJ record number prior to issuing the command.
o Be careful when searching for TSNs or TIDs as they are not
ordered in the AIJ journal. For example, if you want to
search for a specific TSN, use the Only qualifier and not
the First and Last qualifiers. For example, assume the AIJ
journal contains records for TSN 150, 170, and 160 (in that
order). If you specify the First=TSN=160 and Last=TSN=160
qualifiers, nothing will be dumped because TSN 170 will match
the Last=TSN=160 criteria.
o To use the RMU Dump After_Journal command for an .aij file,
you must have the RMU$DUMP privilege in the root file access
control list (ACL) for the database or the OpenVMS SYSPRV or
BYPASS privilege.
o You receive a file access error message regarding the
database's .aij file if you issue the RMU Dump After_Journal
command with the active .aij file when there are active
processes updating the database. To avoid the file access
error message, use the RMU Close command to close the database
(which stops entries to the .aij file), then issue the RMU
Dump After_Journal command.
o See the Oracle Rdb Guide to Database Maintenance for
information on the steps Oracle RMU follows for tape label
checking when you execute an RMU Dump After_Journal command
using magnetic tapes.
o Use of the wrong value for the Format qualifier typically
results in a failure, but sometimes may produce unintelligible
results.
o The RMU Dump After_Journal command does not validate the file
being dumped. If the file is not an .aij file or a backup
of an .aij file, the RMU Dump After_Journal command produces
unintelligible output.
6 – Examples
Example 1
The following command generates a list of records associated with
unresolved transactions in the .aij file:
$ RMU/DUMP/AFTER_JOURNAL/STATE=PREPARED PERSONNEL.AIJ
Example 2
The following example shows the value to specify with the Aij_
Buffers qualifier along with information on how frequently each
page is accessed. The output from this example shows that you
should specify the Aij_Buffers=29 qualifier when you recover
aij_one.aij. In addition, it shows that pages (1:623-625) were
referenced 37 times which means that 8.9% of all data records in
the dumped after-image journal file reference this page.
$ RMU/DUMP/AFTER_JOURNAL/OPTION=STATISTICS aij_one.aij
.
.
.
Use "/AIJ_BUFFERS=29" when recovering this AIJ journal
1 recovery buffer referenced 37 times (1:623-625): 8.9%
1 recovery buffer referenced 23 times (4:23-25): 5.5%
1 recovery buffer referenced 22 times (4:5-7): 5.3%
1 recovery buffer referenced 21 times (4:44-46): 5.0%
1 recovery buffer referenced 20 times (4:50-52): 4.8%
1 recovery buffer referenced 19 times (4:41-43): 4.6%
2 recovery buffers referenced 18 times (4:38-40): 8.7%
1 recovery buffer referenced 17 times (4:17-19): 4.1%
1 recovery buffer referenced 16 times (4:29-31): 3.8%
2 recovery buffers referenced 15 times (4:35-37): 7.2%
1 recovery buffer referenced 14 times (4:2-4): 3.3%
2 recovery buffers referenced 13 times (4:11-13): 6.3%
3 recovery buffers referenced 12 times (4:8-10): 8.7%
2 recovery buffers referenced 11 times (5:2-4): 5.3%
4 recovery buffers referenced 10 times (4:14-16): 9.7%
1 recovery buffer referenced 9 times (4:47-49): 2.1%
2 recovery buffers referenced 8 times (1:617-619): 3.8%
1 recovery buffer referenced 6 times (4:20-22): 1.4%
1 recovery buffer referenced 2 times (1:503-505): 0.4%
Journal effectiveness: 97.3%
175 data records
412 data modification records
423 total modification records
2 commit records
3 rollback records
See the Oracle Rdb Guide to Database Maintenance and the Oracle
Rdb7 Guide to Distributed Transactions for more examples of the
RMU Dump After_Journal command.
Example 3
The following example shows how to start a dump from Block 100 or
TSN 52, whichever occurs first.
$ RMU/DUMP/AFTER_JOURNAL /FIRST=(BLOCK=100,TSN=0:52) mf_personnel.aij
Example 4
This example shows how to dump committed records only.
$ RMU/DUMP/AFTER_JOURNAL /ONLY=(TYPE=COMMIT) mf_personnel.aij
Example 5
This example shows the dump output when you specify an area, a
page, and a line.
RMU/DUMP/AFTER_JOURNAL/AREA=3/PAGE=560/LINE=1 mf_personnel.aij
*-----------------------------------------------------------------------------
* Oracle Rdb X7.1-00 3-NOV-2005
10:42:23.56
*
* Dump of After Image Journal
* Filename: DEVICE:[DIRECTORY]MF_PERSONNEL.AIJ;1
*
*-----------------------------------------------------------------------------
2/4 TYPE=D, LENGTH=122, TAD= 3-NOV-2005 10:31:12.56, CSM=00
TID=6, TSN=0:640, AIJBL_START_FLG=01, FLUSH=00, SEQUENCE=1
MODIFY: PDBK=3:560:1, LDBID=0, PSN=0, FLAGS=00, LENGTH=84
0022 0000 line 1 (3:560:1) record type 34
00 0001 0002 Control information
.... 79 bytes of static data
86726576696C6F54343631303000010D 0005 data '...00164Toliver.'
5020363431411120846E69766C410420 0015 data ' .Alvin. .A146 P'
009820876563616C50206C6C656E7261 0025 data 'arnell Place. ..'
3330484E12208B6175726F636F684307 0035 data '.Chocorua. .NH03'
20F03100630F72B31C00004D373138 0045 data '817M...³r.c.1ð '
2/6 TYPE=D, LENGTH=224, TAD= 3-NOV-2005 10:31:12.56, CSM=00
TID=6, TSN=0:641, AIJBL_START_FLG=01, FLUSH=00, SEQUENCE=3
MODIFY: PDBK=3:560:1, LDBID=0, PSN=1, FLAGS=00, LENGTH=84
0022 0000 line 1 (3:560:1) record type 34
00 0001 0002 Control information
.... 79 bytes of static data
86726576696C6F54343631303000010D 0005 data '...00164Toliver.'
5020363431411120846E69766C410420 0015 data ' .Alvin. .A146 P'
009820876563616C50206C6C656E7261 0025 data 'arnell Place. ..'
3330484E12208B6175726F636F684307 0035 data '.Chocorua. .NH03'
20F03100630F72B31C00004D373138 0045 data '817M...³r.c.1ð '
3/9 TYPE=D, LENGTH=330, TAD= 3-NOV-2005 10:31:12.73, CSM=00
TID=6, TSN=0:642, AIJBL_START_FLG=01, FLUSH=00, SEQUENCE=5
MODIFY: PDBK=3:560:1, LDBID=0, PSN=2, FLAGS=00, LENGTH=84
0022 0000 line 1 (3:560:1) record type 34
00 0001 0002 Control information
.... 79 bytes of static data
86726576696C6F54343631303000010D 0005 data '...00164Toliver.'
5020363431411120846E69766C410420 0015 data ' .Alvin. .A146 P'
009820876563616C50206C6C656E7261 0025 data 'arnell Place. ..'
3330484E12208B6175726F636F684307 0035 data '.Chocorua. .NH03'
20F03100630F72B31C00004D373138 0045 data '817M...³r.c.1ð '
Use "/AIJ_BUFFERS=3" when recovering this AIJ journal.
Make sure you have enough working set and pagefile quota
for the recommended number of buffers.
1 recovery buffer referenced 3 times (3:559-561): 50.0%
1 recovery buffer referenced 2 times (3:436-438): 33.3%
1 recovery buffer referenced 1 time (3:134-136): 16.6%
Journal effectiveness: 54.5%
3 data records
6 data modification records
11 total modification records
3 commit records