Nonstop Database, HiRDB Version 9 System Operation Guide

[Contents][Index][Back][Next]

20.17.7 Adding system log files

This section explains how to add system log files to a server where a system log file shortage occurred.

Note
Before adding system log files, check whether HiRDB Datareplicator is running. If it is running, terminate it, add system log files, and then restart it.

Figure 20-7 General procedure for adding system log files

[Figure]

Note: The numbers in the figure correspond to the numbers in the explanation below.

Organization of this subsection
(1) Check whether the HiRDB file system area has free space
(2) Create a HiRDB file system area for system files
(3) Create system log files
(4) Modify the server definition
(5) Check the server definition content

(1) Check whether the HiRDB file system area has free space

Execute the pdfstartfs command to check whether the HiRDB file system area has free space for system log files.

If system log files are duplexed, check the free space in the HiRDB file system area of both systems A and B.

Example

[Figure]

In this example, the size of the free space in the HiRDB file system area is 23,978 kilobytes.

If it is determined that there is not enough free space to add system log files, proceed to the next step. If there is sufficient free space, proceed directly to (3).

(2) Create a HiRDB file system area for system files

Execute the pdfmkfs command to create a HiRDB file system area for system files.

Example

 
pdfmkfs  -n 1000 -l 32 -k SYS /hirdb/system_dir/logfiles/ADDLOGA
pdfmkfs  -n 1000 -l 32 -k SYS /hirdb/system_dir/logfiles/ADDLOGB
 

For the -n option, specify the size of the HiRDB file system area (in megabytes). Specify a size that at least equals the size of system log files that will be needed during unit restart.

For the -k option, specify SYS (HiRDB file system area for system files).

This example creates two HiRDB file system areas, one for storing the system log files of system A and another for storing the system log files of system B.

If the disk does not have sufficient free space for creating HiRDB file system areas, add a disk before creating HiRDB file system areas.

(3) Create system log files

Execute the pdloginit command to create system log files.

Example

 
pdloginit -d sys -s bes1 -f /hirdb/system_dir/logfiles/ADDLOGA/log008a -n 500000
pdloginit -d sys -s bes1 -f /hirdb/system_dir/logfiles/ADDLOGB/log008b -n 500000
 

For the -n option, specify the number of system log file records. Specify a value that at least equals the number of records that are needed during unit restart.

This example creates system log files for system A and B.

(4) Modify the server definition

Specify the definition related to the system log files created in (3) in the server definition. Add pdlogadfg and pdlogadpf operands for the server definition.

Example

 
pdlogadfg -d sys -g log008 ONL
pdlogadpf -d sys -g log008 -a /hirdb/system_dir/logfiles/ADDLOGA/log008a
                           -b /hirdb/system_dir/logfiles/ADDLOGB/log008b
 

Modify the server definition of the server to which the system log files are added.

(5) Check the server definition content

Execute the pdconfchk command to check the content of the server definition.

Example

 
pdconfchk
 
KFPS05007-I System definition check ended. return code = 0
 

Since the return code from the pdconfchk command is 0, the server definition has been correctly modified.