To use the inner replica facility, you need the HiRDB Staticizer Option. For details on the inner replica facility, see the manual Inner Replica Facility HiRDB Staticizer Option Version 8.

156) pd_inner_replica_control = inner-replica-maximum-group-count

<unsigned integer>((1-4194296))<<0>>

Specifies the maximum number of inner replica groups to be used. For this operand, specify a value that is greater than the number of inner replica groups used during normal startup of HiRDB.

For a HiRDB/Parallel Server, specify the largest inner replica group count among those managed by back-end servers For example, specify at least 31 for this operand for the following back-end server configuration:

• Back-end server 1: has 10 inner replica groups.
• Back-end server 2: has 20 inner replica groups.
• Back-end server 3: has 30 inner replica groups.

Notes

• If the actual number of inner replica groups is greater than the value specified for this operand, HiRDB cannot be started.
• The number of inner replica groups to be defined cannot exceed the value specified for this operand.
• Increasing the specification value of this operand increases the shared memory used by a single server or back-end server. Therefore, do not specify an unnecessarily large value. If a shortage occurs in the shared memory, HiRDB may not be able to start. For details on the shared memory used by a single server and back-end servers, see the HiRDB Version 8 Installation and Design Guide.
• Real Time SAN Replication based on the log-only synchronous method cannot be used together with the inner replica facility. If an attempt is made to use them together, HiRDB cannot be started.

Relationship to other operands

When this operand is specified, NONE is assumed in the pd_indexlock_mode operand.

157) pd_lv_mirror_use = Y | N

Specifies whether to set the open attribute of the replica RDAREA to SCHEDULE.

Y:

Sets the open attribute of the replica RDAREA to SCHEDULE.

N:

Sets the open attribute of the replica RDAREA to that of the original RDAREA. The open attribute of the original RDAREA is specified by the following operands:

• pd_rdarea_open_attribute_use
• pd_rdarea_open_attribute

Specification guidelines

• If you use the inner replica facility under Logical Volume Manager (LVM), the open attribute of the replica RDAREA must be set to SCHEDULE. Therefore, specify Y for this operand. For details, see Notes on Operation in Logical Volume Management in the manual Inner Replica Facility HiRDB Staticizer Option Version 8.
• If you do not use LVM, specify N for this operand.

Note

Note that specifying Y for this operand increases the shared memory used by a single server or back-end server. If a shortage occurs in the shared memory, HiRDB may not be able to start. For details on the shared memory used by a single server and back-end servers, see the HiRDB Version 8 Installation and Design Guide.

158) pd_max_reflect_process_count = number-of-processes-to-be-allocated-for-reflection-processing

<unsigned integer>((1-256))

Specify this operand if you plan to perform updatable online reorganization. If you omit this operand, you cannot perform updatable online reorganization.

For this operand, specify the number of processes to be used for reflection processing. HiRDB allocates the number of processes specified by this operand. For a HiRDB/Parallel Server, the value specified for this operand indicates the number of processes per front-end server.

Specification guidelines

• The value of this operand must satisfy the following condition. Otherwise, HiRDB cannot be started.
  pd_max_reflect_process_count-value + pd_max_users-value 2000 (maximum value of pd_max_users)
  
• For the number of processes to be allocated for reflection processing (formula for estimating the value for the pd_max_reflect_process_count operand), see the manual Inner Replica Facility HiRDB Staticizer Option Version 8.

159) pd_log_org_reflected_logpoint = keep | release

Specify this operand if you plan to perform updatable online reorganization.

This operand specifies whether to change the status of the system log file for which reflection processing has been completed.

keep:

Does not change the status of the system log file for which reflection processing has been completed. Even when reflection processing has been completed for all update logs inside the file, the system log file is kept in the overwriting-denied status for online reorganization.

release:

Changes the status of the system log file for which reflection processing has been completed. When reflection processing has been completed for all update logs inside the file, the system log file status is changed from the overwriting-denied status for online reorganization to the overwriting-permitted status for online reorganization.

Note that in the following cases, the system log file status is changed from the overwriting-denied status for online reorganization to the overwriting-permitted status for online reorganization regardless of the value specified for this operand.

• All reflection processes have been terminated.
• The pdorbegin -u command is executed.
• The pdorend -u command is executed.

Specification guidelines

The values specified for this operand and the pd_log_org_no_standby_file_opr operand determine how the overwriting-denied status for online reorganization of the system log file changes and how updatable online reorganization is performed. For the specification guidelines for this operand, the manual Inner Replica Facility HiRDB Staticizer Option Version 8.

Note

Following forcible termination, abnormal termination, or planned termination, you can change the specification value of this operand from keep (default value) to release only.

160) pd_log_org_no_standby_file_opr = stop | continue

Specify this operand if you plan to perform updatable online reorganization.

This operand specifies the processing for HiRDB when system log file swapping occurs while all system log files are in the overwriting-denied status for online reorganization.

stop:

Forcibly terminates HiRDB. For a HiRDB/Parallel Server, the applicable unit is forcibly terminated.

continue:

The overwriting-denied status for online reorganization is changed to the overwriting-permitted status for online reorganization, and processing continues. For a HiRDB/Parallel Server, this option applies to the system log files inside the server.

Specification guidelines

The values specified for this operand and the pd_log_org_reflected_logpoint operand determine how the overwriting-denied status for online reorganization of the system log file changes and how updatable online reorganization is performed. For the specification guidelines for this operand, the manual Inner Replica Facility HiRDB Staticizer Option Version 8.

Note

If you forcibly release the overwriting-denied status for online reorganization by specifying continue for this operand. System log files used after that time do not go into the overwriting-denied status for online reorganization. Consequently, if a system log file that has an update log that has not been reflected to the main-system RDAREA is overwritten, reflection processing may not be executed. In this case, HiRDB continues executing jobs using only the current sub-system RDAREAs. To return the main-system RDAREA to the current status or to re-execute updatable online reorganization, you need to restore the main-system RDAREA from the sub-system RDAREA in advance. For the procedure for restoring the main-system RDAREA, see the manual Inner Replica Facility HiRDB Staticizer Option Version 8.