The pddbfrz command places a full HiRDB file (used through the last page of the file) that constitutes a user LOB RDAREA in frozen update status. You cannot update or delete LOB data in a HiRDB file that is in frozen update status.

Use this command to back up data without using pdcopy.

HiRDB administrator

pddbfrz [-d] -r {RDAREA-name[,RDAREA-name]...|ALL} [-q generation-number][-W execution-monitoring-interval]

(a) -d

Specifies that HiRDB files are to be released from frozen update status.

When this option is omitted, the command places full HiRDB files in frozen update status. Note that you cannot place the first HiRDB file in an RDAREA in frozen update status.

(b) -r {RDAREA-name[,RDAREA-name]...|ALL}

RDAREA-name ~<identifier> ((1-30))

Specifies the names of the RDAREAs that are to be placed in the frozen update status or released from frozen update status. You can specify only the names of user LOB RDAREAs..

ALL

Specifies that all user LOB RDAREAs are to be placed in the frozen update status. When the -d option is specified, the command releases all user LOB RDAREAs from frozen update status.

Note that when the -q option is specified, the command processes the user LOB RDAREA with the specified generation number.

Rules

1. For the rules for specifying RDAREAs, see 1.5.2 Specification of RDAREAs in operation commands and utilities
2. An error results if a specified RDAREA is not a user LOB RDAREA, a specified user LOB RDAREA contains a plug-in index, or a specified user LOB RDAREA is unused.
3. If you are using the inner replica facility, you can also specify original and replica RDAREAs.

(c) -q generation-number ~<unsigned integer> ((0-10))

Specifies a generation number for a replica RDAREA.

When you specify this option, make sure that an original RDAREA is specified in the -r option. An error results if you specify an original RDAREA whose replica RDAREAs have all been deleted or if you specify a regular RDAREA (one without a replica RDAREA).

(d) -W execution-monitoring-interval ~<unsigned integer> ((0 to 3600))

Specifies (in minutes) the monitoring interval when the execution time of the pddbfrz command is to be monitored. For guidelines on the value to specify and details about the resulting operation, see the description of the pd_cmd_exec_time operand in the system common definition in the manual HiRDB Version 9 System Definition.

If 0 is specified in this option, the command's execution time is not monitored.

If this option is omitted, the value of the pd_cmd_exec_time operand in the system common definition takes effect.

1. The pddbfrz command can be executed only while HiRDB is active.
2. The pddbfrz command must be executed at the server machine that contains the single server or where the system manager is located.
3. When you execute the pddbfrz command, the user LOB RDAREA must be in one of the following statuses:
   
   • Open and shutdown release status
   • Open, and shutdown status placed by the pdhold command
4. The pddbfrz command locks a specified RDAREA. If you execute the pddbfrz command to process an RDAREA that is being accessed by another transaction, the command is placed in wait status until that transaction terminates.
5. Executing the pddbfrz command does not place the first HiRDB file in an RDAREA in frozen update status because this file contains HiRDB management records.
6. You can place only HiRDB files that are filled with data in frozen update status. If a HiRDB file is not full during command execution, it will not be placed in frozen update status later when it becomes full of data.
7. The pddbfrz command is not applicable to RDAREAs that employ updatable online reorganization.

1. The result of the pddbfrz command can be checked by the pddbst command.
2. If you want to update data in a HiRDB that is in frozen update status or if you need to access such an RDAREA for reasons such as reorganization with pdrorg, use the pddbfrz -d command to release the HiRDB file from frozen update status. After updating the RDAREA, back up all HiRDB files again.
3. The following shows the pddbfrz command's return codes:
   0: Normal termination
   4: Warning termination (some RDAREA processing terminated with an error)
   8: Abnormal termination
   12: Abnormal termination (an event occurred that prevented output of an error message)
   If the error code is 12, check the error message in syslogfile at the host where the single server or dictionary server is located, eliminate the cause of the error, and then re-execute the command. If no error message has been output to syslogfile, contact the customer engineer.