There are three RMU Server After_Journal commands, as follows:
o The RMU Server After_Journal Start command starts the AIJ log
server (ALS).
o The RMU Server After_Journal Stop command stops the ALS.
o The RMU Server After_Journal Reopen_Output command allows you
to close and reopen the output file specified with the RMU
Server After_Journal Start command.
1 – Reopen Output
Allows you to close the current AIJ log server (ALS) output file
for the specified database and open a new one. This allows you to
see the current contents of the original ALS output file.
1.1 – Description
The RMU Server After_Journal Reopen_Output command allows you
to reopen an ALS output file that was previously created with an
RMU Server After_Journal Start command with the Output qualifier.
(The ALS output file is opened for exclusive access by the ALS
process.)
Reopening the output file results in the current output file
being closed and a new output file being created. The new output
file has the same file name as the original output file, but its
version number is incremented by one.
The ALS is an optional process that flushes log data to the
after-image journal (.aij) file. All database servers deposit
transaction log data in a cache located in the database global
section. If the ALS is active, it continuously flushes the log
data to disk. Otherwise, server processes might block temporarily
if the cache in the global section is full.
1.2 – Format
(B)0[mRMU/Server After_Journal Reopen_Output root-file-spec
1.3 – Parameters
1.3.1 – root-file-spec
Specifies the database root file for which you want to reopen the
ALS output file.
1.4 – Usage Notes
o To use the RMU Server After_Journal Reopen_Output command for
a database, you must have RMU$OPEN privilege in the root file
access control list (ACL) for the database or the OpenVMS
WORLD privilege.
o To issue the RMU Server After_Journal Reopen_Output command
successfully, the database must be opened. Other users can be
attached to the database when this command is issued.
o To determine whether the ALS is running, use the RMU Show
Users command.
1.5 – Examples
Example 1
In the following example the first Oracle RMU command starts the
log server and specifies an output file. The second Oracle RMU
command reopens the ALS output file, so you can view the data
that is contained in the ALS output file so far.
$ RMU/SERVER AFTER_JOURNAL START MF_PERSONNEL/OUT=ALS
$ ! Database updates occur
$ RMU/SERVER AFTER_JOURNAL REOPEN_OUTPUT MF_PERSONNEL
$ ! View the ALS.OUT;-1 file:
$ TYPE ALS.OUT;-1
--------------------------------------------------------------------
16-OCT-1995 13:02:05.21 - Oracle Rdb V7.0-00 database utility started
---------------------------------------------------------------------
.
.
.
2 – Start
Allows you to manually start the AIJ log server (ALS) for the
specified database and specify a file for the AIJ log server
output.
2.1 – Description
The ALS is an optional process that flushes log data to the
after-image journal (.aij) file. All database servers deposit
transaction log data in a cache located in the database global
section. If the ALS is active, it continuously flushes the log
data to disk. Otherwise, server processes might block temporarily
if the cache in the global section is full. The ALS should be
started only when AIJ processing is a bottleneck. Typically,
multiuser databases with medium to high update activity can
benefit from using the ALS.
You can start the ALS either manually, using the RMU Server
After_Journal Start command, or automatically when the database
is opened (by specifying LOG SERVER IS AUTOMATIC in the SQL ALTER
DATABASE command). By default, the ALS startup is set to manual.
2.2 – Format
(B)0[mRMU/Server After_Journal Start root-file-spec
[4mCommand[m [4mQualifier[m x [4mDefault[m
x
/Output=file-spec x See description
2.3 – Parameters
2.3.1 – root-file-spec
Specifies the database root file for which you want to start the
ALS.
2.4 – Command Qualifiers
2.4.1 – Output
Output=file-spec
Specifies the file for the ALS output file. Use this qualifier
in anticipation of issuing an RMU Server After_Journal Reopen_
Output command. By specifying the output file, you will know the
location of, and therefore can view, the ALS output file.
By default, the ALS output file is not available to the user.
2.5 – Usage Notes
o To use the RMU Server After_Journal Start command for a
database, you must have RMU$OPEN privilege in the root file
access control list (ACL) for the database or the OpenVMS
WORLD privilege.
o The ALS can be started only if the database is open and if
after-image journaling is enabled.
o The RMU Server After_Journal Start command can be issued while
users are attached to the database.
o If the ALS process stops abnormally, regardless of whether the
current setting of the ALS is automatic or manual, the only
way to restart it is to use the RMU Server After_Journal Start
command.
o To determine whether the ALS is running, use the RMU Show
Users command.
o Any errors encountered when you try to start the ALS are
logged in the monitor log file. Use the RMU Show System
command to find the location of the monitor log file.
2.6 – Examples
Example 1
The following Oracle RMU command starts the log server.
$ RMU/SERVER AFTER_JOURNAL START MF_PERSONNEL
3 – Stop
Allows you to manually stop the AIJ log server (ALS) for the
specified database.
3.1 – Description
The ALS is an optional process that flushes log data to the
after-image journal (.aij) file. All database servers deposit
transaction log data in a cache located in the database global
section. If the ALS is active, it continuously flushes the log
data to disk. Otherwise, server processes might block temporarily
if the cache in the global section is full.
3.2 – Format
(B)0[mRMU/Server After_Journal Stop root-file-spec [4mCommand[m [4mQualifiers[m [4mDefaults[m /Output=file-name See description
3.3 – Parameters
3.3.1 – root-file-spec
Specifies the database root file for which you want to stop the
ALS.
3.4 – Command Qualifiers
3.4.1 – Output
Output=file-name
Allows you to specify the file where the operational log is to be
created. The operational log records the transmission and receipt
of network messages.
If you do not include a directory specification with the
file name, the log file is created in the database root file
directory. It is invalid to include a node name as part of the
file name specification.
Note that all Hot Standby bugcheck dumps are written to the
corresponding bugcheck dump file; bugcheck dumps are not written
to the file you specify with the Output qualifier.
3.5 – Usage Notes
o To use the RMU Server After_Journal Stop command for a
database, you must have RMU$OPEN privilege in the root file
access control list (ACL) for the database or the OpenVMS
WORLD privilege.
o To issue the RMU Server After_Journal Stop command
sucessfully, the database must be open. Other users can be
attached to the database.
o If the ALS process stops abnormally, regardless of whether the
current setting of the ALS is automatic or manual, the only
way to restart it is to use the RMU Server After_Journal Start
command.
o To determine whether the ALS is running, use the RMU Show
Users command.
o If database replication is active and you attempt to stop
the database AIJ log server, Oracle Rdb returns an error. You
must stop database replication before attempting to stop the
server.
3.6 – Examples
Example 1
The following example stops the log server.
$ RMU/SERVER AFTER_JOURNAL STOP MF_PERSONNEL