Displays the after-image journal configuration in the form
required for the Aij_Options qualifier. You can use the Aij_
Options qualifier with the RMU Copy_Database, RMU Move_Area,
RMU Restore, RMU Restore Only_Root, and RMU Set After_Journal
commands.
Optionally, this command initializes the RDM$AIJ_BACKUP_SEQNO,
RDM$AIJ_COUNT, RDM$AIJ_CURRENT_SEQNO, RDM$AIJ_ENDOFFILE, RDM$AIJ_
FULLNESS, RDM$AIJ_LAST_SEQNO, RDM$AIJ_NEXT_SEQNO, and RDM$AIJ_
SEQNO global process symbols.
NOTE
Prior to Oracle Rdb Version 6.0, the ability to display an
.aij specification was provided through the Rdbalter Display
Root command. The Rdbalter Display Root command no longer
provides this capability.
1 – Description
The output of the RMU Show After_Journal command appears in the
form shown in Output from the RMU Show After_Journal Command.
This is the form required by the Aij_Options qualifier for the
RMU Copy_Database, Move_Area, and Restore commands. When you
issue the RMU Show After_Journal command, you may see fewer items
than shown in Output from the RMU Show After_Journal Command;
some options do not appear unless you specified them when you
created your after image journal file configuration (for example,
with the RMU Set After_Journal command).
Figure 1 Output from the RMU Show After_Journal Command
(B)0[mJournal [Is] {Enabled | Disabled} -
[Reserve n] -
[Allocation [Is] n] -
[Extent [Is] n] -
[Overwrite [Is] {Enabled|Disabled}] -
[Shutdown_Timeout [Is] n] -
[Notify [Is] {Enabled|Disabled}] -
[Backups [Are] {Manual|Automatic} -
[[No]Quiet_Point] [File filename]] -
[Cache [Is] {Enabled File filename|Disabled}]
Add [Journal] journal-name -
! File file-specification
File filename -
[Allocation [Is] n] -
[Backup_File filename] -
[Edit_String [Is] (edit-string-options)]
When you use the output from the Show After_Journal command as a
template for the Aij_Options qualifier of the RMU Copy_Database,
Move_Area, and Restore commands, note the following regarding the
syntax:
o As shown in Output from the RMU Show After_Journal Command,
you can use the DCL continuation character (-) at the
end of each line in the Journal and Add clauses. Although
continuation characters are not required if you can fit each
clause (Journal or Add clause) on a single line, using them
might improve readability.
o The Journal Is clause must precede the Add clause.
o Because the Journal clause and the Add clause are two separate
clauses, a continuation character should not be used between
the last option in the Journal clause and the Add clause (or
clauses).
o The journal options file can contain one Journal clause only,
but it can contain several Add clauses. However, the number of
Add clauses cannot exceed the number of reservations made for
.aij files. In addition, if you are enabling journaling, you
must add at least one journal.
o You can specify only one of each option (for example, one
Extent clause, one Cache clause, and so on) for the Journal Is
clause.
The clauses and options have the following meaning:
o Journal Is Enabled
Enables after-image journaling. At least one Add clause must
follow. If this option is omitted, the current journaling
state is maintained.
o Journal Is Disabled
Disables after-image journaling. You can specify other options
or Add clauses but they do not take effect until journaling
is enabled. The Add clause is optional. If this option is
omitted, the current journaling state is maintained.
o Reserve n
Allocates space for an .aij file name for a maximum of n .aij
files. By default, no reservations are made. Note that you
cannot reserve space in a single-file database for .aij files
by using this option with the RMU Move_Area command with the
Aij_Options qualifier. After-image journal file reservations
for a single-file database can be made only when you use the
RMU Convert, RMU Restore, or RMU Copy_Database commands.
o Allocation Is n
Specifies the size (in blocks) of each .aij file. If this
option is omitted, the default allocation size is 512 blocks.
The maximum allocation size you can specify is eight million
blocks.
See the Oracle Rdb Guide to Database Maintenance for guidance
on setting the allocation size.
o Extent Is n
Specifies the maximum size to extend an .aij journal if it is,
or becomes, an extensible .aij journal (in blocks). (If the
number of available after-image journal files falls to one,
extensible journaling is employed.)
If there is insufficient free space on the .aij journal
device, the journal is extended using a smaller extension
value than specified. However, the minimum, and default,
extension size is 512 blocks.
See the Oracle Rdb Guide to Database Maintenance for guidance
on setting the extent size.
o Overwrite Is Enabled
Enables overwriting of journals before they have been backed
up. If this option is omitted, overwriting is disabled.
This option is ignored if only one .aij file is available.
When you specify the Overwrite Is Enabled option it is
activated only when two or more .aij files are, or become,
available.
o Overwrite Is Disabled
Disables overwriting of journals before they have been backed
up. If this option is omitted, overwriting is disabled.
o Shutdown_Timeout Is n
Sets the delay from the time a journal failure is detected
until the time the database aborts all access and shuts itself
down. The value n is in minutes.
If this option is omitted, the shutdown timeout is 60 minutes.
The maximum value you can specify is 4320 minutes.
o Notify Is Enabled
Enables operator notification when the journal state changes.
If this option is omitted, operator notification is disabled.
o Notify Is Disabled
Disables operator notification when the journal state changes.
If this option is omitted, operator notification is disabled.
o Backups Are Manual
Automatic backup operations are not enabled. This is the
default behavior.
o Backups Are Automatic [File filename]
Automatic backup operations are triggered by the filling of
a journal. The backup file will have the specified file name
unless a different file name or an edit string is specified in
the Add clause. If this option is omitted, backup operations
are manual.
o Edit String Is (edit-string-options)
Specifies a default edit string to apply to the backup file
when an .aij is backed up automatically. See the description
of the Edit_Filename keyword in Set After_Journal for a
description of the available options. An Edit_String that
appears with the definition of an added journal takes
precedence over this edit string.
o Quiet_Point
Specifies that the after-image journal backup operation is
to acquire the quiet-point lock prior to performing an .aij
backup operation for the specified database.
o Noquiet_Point
Specifies that the after-image journal backup operation will
not acquire the quiet-point lock prior to performing an .aij
backup operation for the specified database.
o Cache Is Enabled File filename
Specifies that a journal cache file should be used. The cache
file must reside on a nonvolatile solid-state disk. If it
does not, caching is ineffectual. See Set After_Journal
for information on what happens if the cache file becomes
inaccessible.
By default, caching is disabled.
o Cache Is Disabled
Specifies that a journal cache file should not be used. This
is the default behavior.
o The Add clause or clauses specify the name and location of the
journal file and the backup file generated by automatic backup
operations as follows:
- Add [Journal] journal-name
Specifies the name for the after-image journal file
described in the Journal clause. The journal-name is the
name of the journal object. A journal object is the journal
file specification plus all the attributes (allocation,
extent, and so on) given to it in the journal clause.
- ! File file-specification
Provides the full file specification and version number of
the .aij file named in the Add clause. This line of output
is provided because the next line (File filename) provides
the string that the user entered when he or she created
the .aij file. For example, if the user entered a file name
only, and this line of output was not provided, you would
have to issue the RMU Dump command to determine in which
directory the file resides.
- File filename
Specifies the file name for the .aij file being added. This
option is required.
- Allocation Is n
Specifies the size of the .aij file (in blocks). If this
option is omitted, the default allocation size is 512
blocks.
See the Oracle Rdb Guide to Database Maintenance for
guidance on setting the allocation size.
- Backup_File filename
Specifies the backup file name for automatic backup
operations. Note that it is not valid to specify a Backup_
File clause in the Add clause if you have specified Backups
Are Manual in the Journal clause; Oracle RMU returns an
error if you attempt to do so.
- Edit String Is (edit-string-options)
Specifies an edit string to apply to the backup file when
the .aij is backed up automatically. See the description
of the Edit_Filename keyword in Set After_Journal for a
description of the available keywords.
2 – Format
(B)0[m RMU/Show After_Journal root-file-spec
[4mCommand[m [4mQualifiers[m x [4mDefaults[m
x
/[No]Backup_Context x /Nobackup_Context
/Output[=file-name] x SYS$OUTPUT
3 – Parameters
3.1 – root-file-spec
The root file specification of the database for which you want
the after-image journal configuration to be displayed.
4 – Command Qualifiers
4.1 – Backup Context
Backup_Context
Nobackup_Context
The Backup_Context qualifier specifies that the following
symbols be initialized, unless you have issued a DCL SET
SYMBOL/SCOPE=(NOLOCAL, NOGLOBAL) command:
o RDM$AIJ_SEQNO
Contains the sequence number of the last .aij backup file
written to tape. This symbol has a value identical to RDM$AIJ_
BACKUP_SEQNO. RDM$AIJ_SEQNO was created prior to Oracle Rdb
Version 6.0 and is maintained for compatibility with previous
versions of Oracle Rdb.
o RDM$AIJ_CURRENT_SEQNO
Contains the sequence number of the currently active .aij
file. A value of -1 indicates that after-image journaling is
disabled.
o RDM$AIJ_NEXT_SEQNO
Contains the sequence number of the next .aij file that
needs to be backed up. This symbol always contains a positive
integer value (which may be 0).
o RDM$AIJ_LAST_SEQNO
Contains the sequence number of the last .aij file available
for a backup operation, which is different from the current
sequence number if fixed-size journaling is being used. A
value of -1 indicates that no journal has ever been backed up.
If the value of the RDM$AIJ_NEXT_SEQNO symbol is greater than
the value of the RDM$AIJ_LAST_SEQNO symbol, then no more .aij
files are currently available for the backup operation.
o RDM$AIJ_BACKUP_SEQNO
Contains the sequence number of the last .aij file backed
up (completed) by the backup operation. This symbol is set
at the completion of an .aij backup operation. A value of -
1 indicates that this process has not yet backed up an .aij
file.
o RDM$AIJ_COUNT
Contains the number of available .aij files.
o RDM$AIJ_ENDOFFILE
Contains the end of file block number for the current AIJ
journal.
o RDM$AIJ_FULLNESS
Contains the percent fullness of the current AIJ journal.
o RDM$HOT_STANDBY_STATE - Contains the current replication
state. Possible state strings and the description of each
state are listed below:
- "Inactive" - Inactive
- "DB_Bind" - Binding to database
- "Net_Bind" - Binding to network
- "Restart" - Replication restart activity
- "Connecting" - Waiting for LCS to connect
- "DB_Synch" - Database synchronization
- "Activating" - LSS server activation
- "SyncCmpltn" - LRS synchronization redo completion
- "Active" - Database replication
- "Completion" - Replication completion
- "Shutdown" - Replication cleanup
- "Net_Unbind" - Unbinding from network
- "Recovery" - Unbinding from database
- "Unknown" - Unknown state or unable to determine state
o RDM$HOT_STANDBY_SYNC_MODE - Contains the current replication
synchronization mode when replication is active. Possible
synchronization mode strings are listed below:
o "Cold"
o "Warm"
o "Hot"
o "Commit"
o "Unknown"
The Nobackup_Context qualifier specifies that the preceding
symbols will not be initialized.
The Nobackup_Context qualifier is the default.
Note that these are string symbols, not integer symbols, even
though their equivalence values are numbers. Therefore performing
arithmetic operations with them produces unexpected results.
If you need to perform arithmetic operations with these symbols,
first convert the string symbol values to numeric symbol values
using the OpenVMS F$INTEGER lexical function. For example:
$ SEQNO_RANGE = F$INTEGER(RDB$AIJ_LAST_SEQNO) -
_$ - F$INTEGER(RDB$AIJ_NEXT_SEQNO)
4.2 – Output
Output[=file-name]
Specifies the name of the file where output is sent. The default
is SYS$OUTPUT. The default output file extension is .lis, if you
specify only a file name.
5 – Usage Notes
o To use the RMU Show After_Journal command for a database, you
must have the RMU$BACKUP, RMU$RESTORE, or RMU$VERIFY privilege
in the root file access control list (ACL) for the database or
the OpenVMS SYSPRV or OpenVMS BYPASS privilege.
6 – Examples
Example 1
The following example shows the output from the RMU Show After_
Journal command when one journal is available, which means
extensible journaling will be used. The commented line is
generated by the RMU Show After_Journal command to display the
full file specification for the added .aij file. The next line
shows the actual file specification entered by the user when he
or she created the .aij file configuration. In this example, the
user did not enter a full specification, therefore only the file
name appears in the uncommented portion of the code.
$ RMU/SHOW AFTER_JOURNAL MF_PERSONNEL
JOURNAL IS ENABLED -
RESERVE 1 -
ALLOCATION IS 512 -
EXTENT IS 512 -
OVERWRITE IS DISABLED -
SHUTDOWN_TIMEOUT IS 60 -
NOTIFY IS DISABLED -
BACKUPS ARE MANUAL -
CACHE IS DISABLED
ADD JOURNAL AIJ_ONE -
! FILE USER2:[JOURNALONE]AIJ1.AIJ;1
FILE AIJ1.AIJ -
BACKUP DISK1:[BACKUP_AIJ]AIJ1BCK.AIJ; -
EDIT_STRING IS (SEQUENCE)
ALLOCATION IS 512
Example 2
The following example shows the output from the RMU Show After_
Journal command when two journal files are enabled, which means
fixed-size journaling will be used. In this example, the user
entered a full file specification for the .aij file when the .aij
file configuration was created. Thus, the commented line and the
one appearing below it are identical with the exception of the
file version:
$ RMU/SHOW AFTER_JOURNAL MF_PERSONNEL
JOURNAL IS ENABLED -
RESERVE 2 -
ALLOCATION IS 512 -
EXTENT IS 512 -
OVERWRITE IS DISABLED -
SHUTDOWN_TIMEOUT IS 60 -
NOTIFY IS DISABLED -
BACKUPS ARE MANUAL -
CACHE IS DISABLED
ADD JOURNAL AIJ_ONE.AIJ -
! FILE DISK2:[AIJ]AIJ1.AIJ;1
FILE DISK2:[AIJ]AIJ1.AIJ -
BACKUP DISK1:[BACKUP_AIJ]AIJ1BCK.AIJ; -
EDIT_STRING IS (SEQUENCE)
ALLOCATION IS 512
ADD JOURNAL AIJ_TWO.AIJ -
! FILE DISK3:[AIJTWO]AIJ2.AIJ;1
FILE DISK3:[AIJTWO]AIJ2.AIJ -
BACKUP DISK1:[BACKUP_AIJ]AIJ2BCK.AIJ; -
EDIT_STRING IS (SEQUENCE)
ALLOCATION IS 512
Example 3
The following example uses the RMU Show After_Journal command
to show the settings of the symbolic names for the .aij sequence
numbers before and after the RMU Backup command is executed:
$ RMU/SHOW AFTER_JOURNAL/BACKUP_CONTEXT MF_PERSONNEL
JOURNAL IS ENABLED -
RESERVE 4 -
ALLOCATION IS 512 -
EXTENT IS 512 -
OVERWRITE IS DISABLED -
SHUTDOWN_TIMEOUT IS 60 -
NOTIFY IS DISABLED -
BACKUPS ARE MANUAL -
CACHE IS DISABLED
ADD JOURNAL AIJ2 -
! FILE DISK2:[DB]AIJ_TWO;1
FILE DISK2:[DB]AIJ_TWO -
ALLOCATION IS 512
ADD JOURNAL AIJ3 -
! FILE DISK3:[DB]AIJ_THREE;1
FILE DISK3:[DB]AIJ_THREE -
ALLOCATION IS 512
$ SHOW SYMBOL RDM$AIJ*
RDM$AIJ_COUNT == "2"
RDM$AIJ_CURRENT_SEQNO == "0"
RDM$AIJ_ENDOFFILE == "1"
RDM$AIJ_FULLNESS == "0"
RDM$AIJ_LAST_SEQNO = "-1"
RDM$AIJ_NEXT_SEQNO = "0"
$ RMU/BACKUP/AFTER MF_PERSONNEL AIJ_TWO, AIJ_THREE
%RMU-I-LOGBCKAIJ, backing up after-image journal RDM$JOURNAL
%RMU-I-AIJBCKSEQ, backing up current after-image journal sequence
number 0
$ RMU/SHOW AFTER_JOURNAL/BACKUP_CONTEXT MF_PERSONNEL
.
.
.
$ SHOW SYMBOL RDM$AIJ*
RDM$AIJ_BACKUP_SEQNO == "-1"
RDM$AIJ_COUNT == "2"
RDM$AIJ_CURRENT_SEQNO = "1"
RDM$AIJ_ENDOFFILE == "1"
RDM$AIJ_FULLNESS == "0"
RDM$AIJ_LAST_SEQNO = "0"
RDM$AIJ_NEXT_SEQNO = "1"
RDM$AIJ_SEQNO == "-1"