Displays a recovery-unit journal (.ruj) file in ASCII format. Use this command to examine the contents of an .ruj file. You might find .ruj files on your system following a system failure. An .ruj file contains header information and data blocks. Header information describes the data blocks, which contain copies of data modified in the database file.
1 – Description
The RMU Dump Recovery_Journal command specifies an .ruj 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 .ruj file is in binary format. This command translates the binary file into an ASCII display format.
2 – Format
(B)0[m RMU/Dump/Recovery_Journal ruj-file-name [4mCommand[m [4mQualifiers[m x [4mDefaults[m x /[No]Data x /Data /Output = file-name x /Output=SYS$OUTPUT
3 – Parameters
3.1 – ruj-file-name
The .ruj file. The default file type is .ruj.
4 – Command Qualifiers
4.1 – Data
Data Nodata Specifies whether you want to display data blocks of the .ruj file or just the .ruj file header. The Data qualifier is the default. It causes the display of the .ruj file data blocks (in addition to the file header) in an ASCII display format. The Nodata qualifier limits the display to the file header of the .ruj file.
4.2 – Output
Output=file-name The name of the file where output will be sent. The default is SYS$OUTPUT. The default output file type is .lis, if you specify a file name.
5 – Usage Notes
o You do not need Oracle RMU privileges to use the RMU Dump Recovery_Journal command. However, you must have OpenVMS READ access to the .ruj file or OpenVMS BYPASS privilege to use the RMU Dump Recovery_Journal command. o The RMU Dump Recovery_Journal command does not validate the file being dumped. If the file is not an .ruj file, the output from the RMU Dump Recovery_Journal command is unintelligible. o See the Oracle Rdb Guide to Database Maintenance for examples showing the RMU Dump Recovery_Journal command.