KFPR messages

KFPR00754-I L+S

Pdcopy started

Database copy utility (pdcopy) processing has started.

S: Resumes processing.

KFPR00756-I L+S

Pdcopy terminated, return code=aa

Database copy utility (pdcopy) processing terminated with the indicated return code.

aa: Return code of the database copy utility (pdcopy):

0: Normal termination

8: Abnormal termination (error occurred during copy processing, but some of the files were backed up successfully)

12: Abnormal termination (all copy processing failed)

S: Resumes processing.

Action: In the case of abnormal termination, refer to the error message that was output before this message to eliminate the cause of the error.

KFPR00757-I E+L

Retry reopen aa-time of bb after cc-minute, host=dd....dd, file=ee....ee, reason=ff....ff

Multivolume file reopen processing will be executed cc minutes later. The maximum retries count is bb, and the next retry number is aa. The file name is ee....ee at host dd....dd.

aa: Next retry number

bb: Maximum retries count

cc: Retry interval

dd....dd: Host name

ee....ee: File name

ff....ff: Reason for retry:: No-file: File is not set.; Same-file: The same file as before is set.

S: Resumes processing.

Action: Set the next file during the retry.

KFPR00758-I L

File swapping started, file=aa....aa, reason=bb....bb

Processing of second or subsequent volume of multivolume file aa....aa has started.

aa....aa: File name

bb....bb: Reason code:: ENOSPC: Space ran out at the device.; EOV: End-of-volume was detected.

S: Resumes processing.

KFPR00764-I L+S

Pdrstr started

Database recovery utility (pdrstr) processing has started.

S: Resumes processing.

KFPR00765-I L

Pdrstr terminated, return code=aa

Database recovery utility (pdrstr) processing terminated with the indicated return code.

aa: Return code of the database recovery utility (pdrstr):: 0: Normal termination; 4: Termination with warning (close error occurred in the backup file or unload log file; or, the backup file does not contain RDAREA data subject to recovery); 8: Abnormal termination (error occurred, but at least one RDAREA was recovered successfully); 12: Abnormal termination (recovery of all RDAREAs failed)

S: Resumes processing.

Action: In the case of abnormal termination, refer to the error message that was output before this message to eliminate the cause of the error.

KFPR00766-I L

Recovery of "aa....aa" ended bb....bb

Recovery of RDAREA "aa....aa" is complete.

aa....aa: RDAREA name

bb....bb: Completion status:: abnormally: Recovery failed.; normally: Recovery was successful.

S: Resumes processing.

Action: If recovery failed, refer to the error message that was output before this message to eliminate the cause of the error, and re-execute recovery of the corresponding RDAREA.

KFPR00767-I E+L

Retry reopen aa-time of bb after cc-minute, host=dd....dd, file=ee....ee, reason=ff....ff

Multivolume file reopen processing will be executed cc minutes later. The maximum retries count is bb, and the next retry number is aa. The file name is ee....ee at host dd....dd.

aa: Next retry number

bb: Maximum retry number

cc: Retry interval

dd....dd: Host name

ee....ee: File name

ff....ff: Reason for retry

S: Resumes processing.

Action: Set the next file during the retry.

KFPR00768-I L

File swapping started, file=aa....aa, reason=bb....bb

Processing of second or subsequent volume of multivolume file aa....aa has started.

aa....aa: File name

bb....bb: Reason code:: ENOSPC: Space ran out at the device.; EOV: End-of-volume was detected.

S: Resumes processing.

KFPR00786-I L+S

Differential recovery by manual mode

Recovery processing that does not use a differential backup management file is being started.

S: Continues processing.

KFPR16003-E L+S

aaaaaa error occurred, file=bb....bb

A file I/O error occurred.

aaaaaa: Processing resulting in the error:: Close: Close processing; Open: Open processing; Read: Read processing; Reopen: Opening of the second or subsequent volume of a multivolume file; Write: Write processing

bb....bb: File name

S: Terminates processing. In the case of the Close error, the system may resume processing.

Action: Refer to the message that was output after this message to eliminate the cause of the error, and re-execute the command.

KFPR16005-E L+S

Insufficient memory for PROCESS, size=aa....aa

An attempt to allocate a work area needed for executing the database copy utility (pdcopy) failed due to insufficient process private area.

aa....aa: Area size (in bytes) That was to be allocated

S: Terminates processing.

O: Contact the HiRDB administrator.

Action

Determine whether there are other processes that use a large amount of memory.

When there is a process using a large amount of memory:: Wait until the process terminates, and then re-execute the command.

When there is no process using a large amount of memory:

Use one of the following methods to ensure that there is sufficient memory:

Reduce the number of simultaneously executing processes.
Increase the size of the swap area.
Increase the amount of memory.

KFPR16014-E L+S

Pdcopy version aa....aa and HiRDB version bb....bb do not match

The version of the database copy utility (pdcopy) does not match the HiRDB version.

aa....aa: Version revision number of the database copy utility

bb....bb: Version revision number of HiRDB

S: Terminates processing.

Action: Execute the database copy utility using the version revision number that is the same as that of the HiRDB being used.

KFPR16101-E L+S

File I/O error occurred, reason=aa....aa, func=bb....bb, errno=cc....cc, (dd....dd)

An error occurred during file I/O processing.

aa....aa: Cause of error:

File-format:: The specified file format differs from the actual file format. It is possible that the specified file name is incorrect, or the file format specified on the command line or in the control statement does not match the contents.

File-lock:: The file to be used is locked by another utility and the file read/write operation cannot be executed. The file name specified in the command line or control statement might be in use by another job. In UNIX, there might be a shortage of file locking resources for an OS kernel parameter.

File-sequence:: The sequence of volumes of a multivolume file is invalid.

Invalid-device:: Entry type (attribute) of the specified file is invalid. Or, when MTguide is to be used, MTguide has not been started. If the system can identify the entry type, it displays one alphabetic character enclosed in parentheses. This character is the same as the entry in the mode output by the operating system's ls -l command. It is possible that a directory name was specified in a location that requires a file name (or vice versa), or that a character special file was assigned to a file where a character special file cannot be used.

Invalid-environment:: Because the set value obtained by the uname system call is invalid, a streaming tape device cannot be used. Check that the OS has been installed correctly or that the OS version satisfies the prerequisite conditions of the HiRDB system or related program products.

Invalid-parameter:: The combination of specified parameters is invalid.

Invalid-path:: The path name is invalid.

Invalid-permission:: The specified file permission is invalid (access permission error). A file is being used for which the HiRDB administrator has not granted an access privilege, or for MT, the file is write-protected.

No-file:: The file to be opened for read operation was not found, or a file involved in write operation was deleted.

No-space:: There is not enough space in the file subject to write operation. Either review the file size or specify a multivolume file.; UNIX version:; If this error occurs when there is sufficient disk space, it is possible that either the HiRDB file system area is not defined as a large file or an operating system kernel parameter restriction is applied.; It is also possible that the value specified by pdcopy with the -S option is set to a value smaller than the default or backup data value. If OB2_WriteObjData was output to the system function name in error, check the size of the backup data output destination set in JP1/OmniBack II. If the size is sufficient, check the messages output from OmniBack II to determine the source of the problem. If the source of the error cannot be determined, contact the customer engineer.; Windows version:; If this error occurs when there is sufficient disk space, it is possible that the HiRDB file system area is not defined as a large file (2048 MB or greater) in the pd_large_file_use operand.; It is also possible that the value specified by pdcopy with the -s option is set to a value smaller than the default or backup data value.

No swap-file:: Multivolume file cannot be found. Check the size. Or, specify a multivolume file.

Same-file:: The same multivolume file was specified as before (files have not been exchanged). Or, an attempt was made to reuse the same volume during write processing to a multivolume file.

Unmatch-entry:: Header entry for a header file does not match the specification of the control information file. The name of the unmatched entry is enclosed in parentheses.

If the above actions do not eliminate the error, contact the customer engineer.

bb....bb: Name of the system function in which the error occurred

If an error was detected by the HiRDB file system, the HiRDB file system function names beginning with p_f_ios
If an error was detected by OmniBack II, OB2_WriteObjdata
If an error was detected when a function was not being used, ***
If other than the above, the system function name

cc....cc: Error number that is returned by the function (errno)

If an error was detected by the HiRDB file system, the HiRDB file system error code
If an error was detected when a function was not being used or with OmniBack II, 0
If an error was detected by the operating system, the error number returned by the system function (errno: foreign reference variable that displays the error status)

dd....dd: Name of the source file and the line number at which the error was detected

S: Terminates processing.

Action

Take action based on the following table:

Error cause	Action
Error was detected by the HiRDB file system.	See 5.1 Error codes returned from HiRDB file system access requests, remove the cause of the error, and re-execute.
Error was detected by mechanism other than a function or OmniBack II.	From the error cause aa....aa, remove the cause of the error, and re-execute.
Error was detected by the operating system.	See the operating system manual, remove the cause of the error, and re-execute.

If an error occurs on re-execution, contact the customer engineer.

KFPR16102-E E+L

File operation was canceled by aa....aa

Multivolume file exchange was cancelled.

aa....aa: Reason for cancellation:: system: Processing was cancelled by the system.; user: Processing was cancelled by the user.

S: Terminates processing.

P: Re-execute the processing, if necessary.

KFPR16104-E L+S

Dynamic load error occurred, shared library=aa....aa

An error occurred during dynamic loading of a shared library required for processing.

aa....aa: Absolute path name of the shared library

S: Terminates processing.

O: Refer to the KFPR26003-E message that was output before this message.

UNIX version:

Resolve the error as follows, and then re-execute the command:

EasyMT used:
Check that the system has been installed correctly.
EasyMT not used:
Check the specification of the k option flag and correct the specification to nonuse of EasyMT or MTguide.

Windows version:: Review the value specified in the -k option flag, revise it if necessary, and then re-execute the command.

KFPR16108-E L+S

Present directory information conflicts with directory information specified when the backup file was made, RDAREA name="aa....aa", code=b

The present directory information does not match the directory information specified when the previous backup file was created. This mismatch is caused because the structure of the RDAREA has been modified since the previous backup file was made.

aa....aa: Name of RDAREA in which mismatch occurred

b: Error code:: 1: Page size mismatch; 2: RDAREA attribute mismatch; 3: HiRDB file name mismatch; 4: RDAREA name mismatch; 5: Segment size mismatch; 6: Mismatch in the number of HiRDB files comprising the RDAREA; 7: RDAREA initialization date

S: Terminates processing.

Action: Use the pdcopy command to make a full backup. In this step, specify creation of a differential backup management file (specify (S) for the differential backup group name in the -g option).

KFPR16110-I L+S

Unable to get a backup file aa....aa

The backup file of a database cannot be created.

aa....aa: Name of backup file

S: If another backup file is specified, executes backup processing for that file. If no other backup file is specified, terminates processing.

Action: Refer to the error message that was output before this message to eliminate the cause of the error, and re-execute.

KFPR16126-E L+S

Master RDAREA is not initialized

The master directory RDAREA has not been initialized, or the specified file is not the master directory.
Possible causes of this error are as follows:

The database initialization utility (pdinit) did not terminate normally.
The specified file is not the master directory RDAREA.
The contents of the master directory RDAREA are damaged.

S: Terminates processing.

Action

Eliminate the cause of the error, correct the status of the master directory RDAREA, then re-execute.

Possible causes of the error are as follows:

A file other than the master directory was specified.
The database initialization utility (pdinit) did not terminate normally.
The contents of the master directory RDAREA are damaged.

In the case of item 1, make sure the file name of the master directory specified using the -m option is correct. If it is in error, correct it, and re-execute the command.

In the case of item 2, verify that the database initialization utility (pdinit) terminated normally, perform HiRDB startup processing, and re-execute the command.

If the error cannot be resolved by either of the above actions, it is possible that the contents of the master directory RDAREA are damaged. Either restore the master directory or contact a customer engineer.

KFPR16127-E L+S

Page corrupted, RDAREA name="aa....aa", HiRDB file name=bb....bb, page no. =cc....cc

Page corruption was detected.

aa....aa: RDAREA name

bb....bb: HiRDB file name

cc....cc: Page number in HiRDB file bb....bb

S: Cancels RDAREA backup processing. If there is another backup file, the HiRDB system resumes processing.

Action: Contact a customer engineer.

KFPR16128-E L+S

aa....aa error occurred, func=bb....bb, return code=cc....cc

An error occurred during one of the following processing operations:

Sort processing
Magnetic tape I/O processing
OmniBack II (JP1/OmniBack II) processing

aa....aa: Processing that generated the error

SORT: Sort processing
EasyMT: Magnetic tape I/O processing
OmniBack II: JP1/OmniBack II processing

bb....bb: Name of the function resulting in the error

cc....cc: Return code from the function resulting in the error

S: Terminates processing.: Terminates abnormally when the return code from OmniBack II is 1, 2, or 4.

Action

Take the following action:

If aa....aa is SORT:
Refer to 7. Messages Related to Sort Processing, and take corrective action.
Messages related to sort processing are output in the format KBLSnnn-E, where nnn denotes the absolute value of the return code that is output to cc....cc.
The table below summarizes frequently output return codes and the required corrective action:

Return code	Action
-202	Memory shortage. Reduce the work buffer size specified in the sort operand.
-290	Work buffer shortage. Increase the work buffer size specified in the sort operand.
-210, -230	An I/O error occurred. It is possible that the disk space for sort processing is insufficient. If insufficient disk space is the cause of the error, specify a disk with sufficient space in the sort operand, and then re-execute the processing.

If the error cannot be resolved, acquire the sortdump, SORTIODUMP, and SORTDMP2 that are output to C:\Windows (in UNIX, /tmp or /usr/tmp), and contact a customer engineer.

If aa....aa is EasyMT:
Contact a customer engineer.

If aa....aa is OmniBack II:
Take appropriate action based on the return code.
If the return code is 1, 2, or 4, contact a customer engineer.
If the return code is 3, or 5 through 7, using the session ID of the JP1/OmniBack II session that resulted in the error, execute omnidb -session session-ID -report to check the cause of the error. Alternately, use xomnimonitor to check the cause of the error. Look for the session ID from the list of session IDs that are displayed with omnidb -session.
If the name of the function that resulted in the error is OB2_Init, and the return code is 5, make sure that the version of JP1/OmniBack II is 05-20. If it is any other version, change it to 05-20.
For details about how to pinpoint the cause of the error, see the JP1/OmniBack II manual. The meanings of return codes 3, and 5 through 7, are detailed as follows:

Return code	Meaning
3	The function does not match the current operation mode. If the function that caused the error is OB2_Init, use the oministat command to check the JP1/OmniBack II session that is running in the background, wait for that session to end, then re-execute.
5	Operation failed due to a JP1/OmniBack II internal error.
6	Operation failed due to a system error.
7	The privilege for the JP1/OmniBack II service is not adequate. If the name of the function that caused the error is OB2_Init, register the HiRDB administrator as a JP1/OmniBack II user in the admin user class.

KFPR16129-E L+S

EasyMT error occurred, func=aa....aa, reason=bb....bb

An error occurred during I/O processing of a file used by EasyMT.

aa....aa: Function in which the error was detected

bb....bb: Error detail information

S: Terminates processing.

Action: Based on the error detail information, check the documentation for JP1/Magnetic Tape Access or EasyMT, eliminate the cause of the error, and then re-execute.

KFPR16203-E L+S

aaaaaa error occurred, file=bb....bb

A file I/O error occurred.

aaaaaa: Processing resulting in the error:: Close: Close processing; Open: Open processing; Read: Read processing; Reopen: Opening of the second or subsequent volume of a multivolume file; Write: Write processing

bb....bb: File name (If a system log file I/O error occurred, the file group name is indicated.)

S: Terminates processing. In the case of the Close error, the system may resume processing.

Action: Refer to the message that was output after this message to eliminate the cause of the error, and then re-execute the command. If a system log file I/O error occurred, refer to the message output before this message.

KFPR16205-E L+S

Insufficient memory for PROCESS, size=aa....aa

An attempt to allocate a work area needed for executing the pdrstr or pdbkupls command failed, due to an insufficient process private area.

aa....aa: Area size (in bytes) That was to be allocated

S: Terminates processing.

Action

Check whether there are processes that use a large amount of memory.

There are processes that use a large amount of memory:: Wait for the associated processes to terminate, then re-execute the command.

There are no processes that use a large amount of memory:

Use one of the following methods to ensure that there is sufficient memory:

Reduce the number of simultaneously executing processes.
Increase the size of the swap area.
Increase the amount of memory.

KFPR16214-E L+S

Pdrstr version aa....aa and HiRDB version bb....bb do not match

The version of the database recovery utility (pdrstr) does not match the HiRDB version.

aa....aa: Version revision number of the database recovery utility

bb....bb: Version revision number of HiRDB

S: Terminates processing.

Action: Execute the database recovery utility with the version revision number that is the same as that of the HiRDB being used.

KFPR16301-E L+S

File I/O error occurred, reason=aa....aa, func=bb....bb, errno=cc....cc, (dd....dd)

An error occurred during file I/O processing.

aa....aa: Cause of error:

Empty-file:: The specified file is empty (0 bytes).

File-format:: The specified file format differs from the actual file format. It is possible that the specified file name is incorrect or the file format specified on the command line or in the control statement does not match the contents.

File-lock:: The file to be used is locked by another utility and the file read/write operation cannot be executed. The file name specified in the command line or control statement might be in use by another job. In UNIX, there might be a shortage of file locking resources for an OS kernel parameter.

File-missing:: The specification of the unload log file or the backup file is incorrect. See the KFPR26265-I message that was output before or after this message, remove the cause of the error, and re-execute.

File-sequence:: The sequence of volumes of a multivolume file is invalid.

Invalid-device:: The specified file entry type (attribute) is invalid. Or, if MTguide is being used, MTguide is not activated. If the system can identify the entry type, it displays one alphabetic character enclosed in parentheses. This character is the same as the entry in the mode output by the operating system's ls -l command. It is possible that a directory name was specified in a location that requires a file name (or vice versa), or that a character special file was assigned to a file where a character special file cannot be used.

Invalid-environment:: Because the set value obtained by the uname system call is invalid, a streaming tape device cannot be used. Check that the OS has been installed correctly or that the OS version satisfies the prerequisite conditions of the HiRDB system or related program products.

Invalid-file:: A file was specified that was created incorrectly.

Invalid-parameter:: A combination of specified parameters is invalid.

Invalid-permission:: The specified file version is invalid (access privilege error). It is possible that a file is being used, for which an access privilege has not been granted by a HiRDB administrator, or for MT, may be write-protected.

Invalid-path:: The path name is invalid.

No-file:: File to be opened for the read operation was not found, or a file involved in the write operation was deleted.

No-space:: There is not enough space in the file subject to the write operation. Revise the size or specify a multi-volume.; In UNIX, if this error occurs when there is sufficient disk space, it is possible that either the HiRDB file system area is not defined as a large file, or an operating system kernel parameter restriction applies.; In Windows, if this error occurs when there is sufficient disk space, it is possible that the HiRDB file system area is not defined as a large file (2048 MB or greater) in the pd_large_file_use operand.

No swap-file:: Multivolume swap file cannot be found. Check the size. Or, specify a multivolume file.

Same-file:: The same multivolume file as before was specified (files have not been exchanged). An attempt was made to reuse the same volume during write processing to a multivolume file.

Unmatch-entry:: Header entry for header file does not match the specification in the control statements file. The name of the unmatched entry is enclosed in parentheses.

bb....bb: Name of the function in which the error occurred

If an error was detected by the HiRDB file system, the HiRDB file system function names beginning with p_f_ios
If an error was detected when a function was not being used, ***
If other than the above, the system function name

cc....cc: Error number that is returned by the function (errno)

If an error was detected by the HiRDB file system, the HiRDB file system error code
If an error was detected when a function was not being used, 0
If an error was detected by the operating system, the error number returned by the system function (errno: foreign reference variable that displays the error status)

dd....dd: Name of the source file and the line number at which the error was detected.

S: If aa....aa is File_missing, processing continues according to the KFPR26265-I message output before or after this message. Otherwise, terminates processing.

Action

Take action based on the following table:

Error cause	Action
Error was detected by the HiRDB file system.	See 5.1 Error codes returned from HiRDB file system access requests, remove the cause of the error, and re-execute.
Error was detected by mechanism other than a function.	From the error cause aa....aa, remove the cause of the error, and re-execute.
Error was detected by the operating system.	Refer to the operating system manual, remove the cause of the error, and re-execute.

If an error occurs on re-execution, contact the customer engineer.

KFPR16302-E E+L

File operation was canceled by aa....aa

Multivolume file exchange was cancelled.

aa....aa: Reason for cancellation:: system: Cancelled by the system; user: Cancelled by the user

S: Terminates processing.

Action: Re-execute the processing, if necessary.

KFPR16303-E L+S

Invalid aa....aa log file, file=bb....bb

Log file bb....bb is invalid. Check the following:

For unload file:

Whether or not an invalid unload log file is specified
Whether or not both an unload log file before database initialization and an unload log file after database initialization are specified

For system log file:

Whether or not the database was initialized after the backup file was made

aa....aa: Log file type: unload: Unload log file; sys: System log file

bb....bb: Name of the log file for which the error or initialization was detected

For unload log file:: Name of unload log file

For system log file:: File group name

S: Terminates processing.

O:

For unload log file:: Specify the correct unload log file, and then re-execute. If unload log files made both before and after database initialization are specified, specify either unload log files made before database initialization or unload log files made after database initialization, and then re-execute.

For system log file:: Specify the backup file after database initialization, and then re-execute.

KFPR16304-E L+S

Dynamic load error occurred, shared library=aa....aa

An error occurred during dynamic loading of a shared library required for processing.

aa....aa: Full path name of the shared library

S: Terminates processing.

O: Refer to the KFPR26203-E message that was output before this message.

UNIX version:

Resolve the error as follows, and then re-execute the command:

EasyMT used:
Check that the system has been installed correctly.
EasyMT not used:
Check the specification of the -k option flag and correct the specification to nonuse of EasyMT or MTguide.

Windows version:: Review the value specified in the -k option, revise it if necessary, and then re-execute the command.

KFPR16308-E L+S

Present directory information conflicts with directory information specified when the backup file was made, RDAREA name="aa....aa", code=b

A conflict was detected between directory information for an RDAREA as specified in the master directory and as specified when a backup file was made; processing of the RDAREA is terminated.

aa....aa: Name of RDAREA containing contradictory information

b: Error code:: 1: Page length does not match.; 2: RDAREA attribute does not match.; 3: RDAREA file name does not match.; 4: RDAREA name does not match.; 5: Segment size does not match.; 6: RDAREA structure does not match the number of HiRDB files.

S: Processes the next RDAREA without recovering the RDAREA containing contradictory information.

Action

Take one of the following actions:

If the file name specified in the -m option for the first HiRDB file name of the master directory RDAREA is invalid, specify the correct file name, and re-execute the command.
If the configuration of the RDAREA was changed after the applicable backup file was acquired, these RDAREA configuration changes cannot be recovered. Either use a backup file acquired after the RDAREA configuration was changed or specify a time before the RDAREA configuration was changed, and then re-execute the command.

If the error cannot be resolved by either of the above actions, contact a customer engineer.

KFPR16318-E L+S

Backup data not found, RDAREA name="aa....aa"

The specified backup file does not contain the backup data of the appropriate RDAREA.

aa....aa: Name of RDAREA whose backup data is missing

S: Recovers the RDAREA without using its backup data. If the unload log file is specified and the update log of the corresponding RDAREA is available, the system recovers the RDAREA only using log information. If the -L option is specified, the HiRDB system cancels processing.

Action

Check the items listed below, correct the error, and then re-execute:

Check the specification of the backup file for an error. If a tape drive is used, determine whether rewinding is specified.
If the -L option is specified, check that there is an RDAREA to be recovered in the backup file created by specifying the -z option for pdcopy execution.

KFPR16328-E L+S

aa....aa error occurred, func=bb....bb, return code=cc....cc

An error occurred during one of the following processing operations:

Sort processing
Magnetic tape I/O processing
OmniBack II (JP1/OmniBack II) processing

aa....aa: Processing that generated the error

SORT: Sort processing
EasyMT: Magnetic tape I/O processing
OmniBack II: JP1/OmniBack II processing

bb....bb: Name of the function resulting in the error

cc....cc: Return code from the function resulting in the error

S: Terminates processing.: Terminates abnormally when the return code from OmniBack II is 1, 2, or 4.

Action

Take the following action:

Return code	Action
-202	Memory shortage. Reduce the work buffer size specified in the sort operand.
-290	Work buffer shortage. Increase the work buffer size specified in the sort operand.
-210, -230	An I/O error occurred. It is possible that the disk space for sort work is insufficient. If insufficient disk space is the cause of the error, specify a disk with sufficient space in the sort operand, and then re-execute the processing.

If the error cannot be resolved, acquire the sortdump, SORTIODUMP, and SORTDMP2 that are output to C:\Windows (in UNIX, /tmp or /usr/tmp), and contact a customer engineer.

If aa....aa is EasyMT:
Contact a customer engineer.

If aa....aa is OmniBack II:
Take appropriate action based on the return code.
If the return code is 1, 2, or 4, contact a customer engineer.
If the return code is 3, or 5 through 7, using the session ID of the JP1/OmniBack II session that resulted in the error, execute omnidb -session session-ID -report to check the cause of the error. Alternately, use xomnimonitor to check the cause of the error. Look for the session ID from the list of session IDs that are displayed with omnidb -session.
For details about how to pinpoint the cause of the error, see the JP1/OmniBack II manual.
The meanings of return codes 3, and 5 through 7 are detailed as follows:

Return code	Meaning
3	The function does not match the current operation mode. If the function that caused the error is OB2_Init, use the oministat command to check the JP1/OmniBack II session that is running in the background, wait for that session to end, then re-execute.
5	Operation failed due to a JP1/OmniBack II internal error. If the function that caused the error is OB2_Init, make sure the version of OmniBack II is 05-20; if not, install version 05-20.
6	Operation failed due to a system error.
7	The privilege for the JP1/OmniBack II service is not adequate. If the name of the function that caused the error is OB2_Init, register the HiRDB administrator as a JP1/OmniBack II user in the admin user class.

KFPR16329-E L+S

EasyMT error occurred, func=aa....aa, reason=bb....bb

An error occurred during I/O processing of a file used by EasyMT.

aa....aa: Function in which the error was detected

bb....bb: Error detail information

S: Terminates processing.

Action: Based on the error detail information, check the documentation for JP1/Magnetic Tape Access or EasyMT, eliminate the cause of the error, and then re-execute.

KFPR16330-E L+S

Log was not found when backup aa....aa at bb....bb -cc....cc, server=dd....dd

Recovery is to be from the backup copy created with the -M s option specified for the backup mode, but the input log does not contain the following log records required for recovery:

First log record
Last log record

aa....aa: Missing date and time:: started: Copy start time; ended: Copy end time

bb....bb: Log record number 1

cc....cc: Log record number 2

dd....dd: Name of server subject to recovery

S: Cancels recovery of the corresponding server.

Action: Specify the log containing the first or last log record required for recovery, and then re-execute.

KFPR16333-E L+S

RDAREA aa....aa at bb....bb, RDAREA name="cc....cc"

Because aa....aa has been executed on RDAREA "cc....cc", the corresponding RDAREA cannot be recovered from the backup copy that was created before that date. Or, no backup file was specified.

aa....aa: Type of RDAREA processing: added: RDAREA addition; altered: RDAREA alteration; deleted: RDAREA deletion; extended: RDAREA expansion; initialized: Reinitialization

bb....bb: Date and time the RDAREA was expanded

cc....cc: Name of expanded RDAREA

S: Recovers the next RDAREA without recovering the indicated RDAREA.

Action: Recover the RDAREA using the correct backup file and log obtained after the RDAREA processing. If no backup file was obtained after manipulation, specify a time bb....bb earlier than the recovery end time of the -T option, and then recover the RDAREA.

KFPR16334-E L+S

RDAREA was updated by logless process, RDAREA name="aa....aa", update time=bb....bb

Because the indicated RDAREA was updated at time bb....bb by a transaction that does not collect a system log, the RDAREA cannot be recovered.

aa....aa: RDAREA name

bb....bb: Update time

S: Recovers the next RDAREA without recovering the indicated RDAREA.

Action: Re-execute using the backup created after the transaction that does not collect a system log has terminated. If there is no backup, specify a time bb....bb earlier than the recovery end time of the -T option.

KFPR16338-E L+S

Master RDAREA is not initialized

The master directory RDAREA has not been initialized or the specified file is not the master directory. Possible causes of this error are as follows:

The database initialization utility (pdinit) did not terminate normally.
The specified file is not the master directory.
The contents of the master directory are damaged.

S: Terminates processing.

Action: Eliminate the cause of the error, correct the status of the master directory RDAREA, and then re-execute.; Possible causes of the error are as follows:

A file other than the master directory was specified.
The database initialization utility (pdinit) did not terminate normally.
The contents of the master directory RDAREA are damaged.

In the case of item 1, make sure the file name of the master directory specified using the -m option is correct. If it is in error, correct it, and re-execute the command.

In the case of item 2, verify that the database initialization utility (pdinit) terminated normally, perform HiRDB startup processing, and re-execute the command.

If the error cannot be resolved by either of the above actions, it is possible that the contents of the master directory are damaged. Either restore the master directory or contact a customer engineer.

KFPR16339-E L+S

Invalid backup file, file=aa....aa

The specified backup file is invalid. Check the following:

Whether or not the correct volume was specified in the multivolume specification
Whether or not the correct file was specified in the multi-file specification

aa....aa: Invalid file contents

If Mtguide is used: Device symbolic name or device group name
If Mtguide is not used or in the Windows version: File name

S: Terminates processing.

Action: Specify the correct backup file, and then re-execute.

KFPR26001-E E+L

Communication "aa....aa" error occurred, code=bbbbb

A communication error occurred while executing the database copy utility (pdcopy).

aa....aa: Name of RPC-related function resulting in the error

bbbbb: Error code from the RPC-related function resulting in the error

S: Terminates processing.

Action: See 4. Error Detail Codes to eliminate the cause of the error, and then re-execute. If the error cannot be corrected by the HiRDB administrator, contact a customer engineer.

KFPR26002-E L+S

Unable to allocate COMBUF area, size=aaaaaa

A communication area cannot be allocated because a real or virtual memory space shortage occurred.

aaaaaa: Size (in KB) of communication area that was to be allocated

S: Terminates processing.

Action

Re-execute the command after a process that uses a large amount of memory has terminated.
If a value greater than 32 was specified for the buffer size (pd_utl_buff_size operand) in the system common definition, specify 32, and then re-execute the command.

KFPR26003-E L+S

System call error, func=aa....aa, errno=bbb

A system call error occurred.

aa....aa: Name of the system call resulting in the error

bbb: errno value of the system call resulting in the error

S: Terminates processing.

Action: Check the value of the error indicator, refer to errno.h and the applicable OS manual to eliminate the cause of the error, and then re-execute.

KFPR26004-I E

Error exists in command line or control file, usage is as follows

An error was detected in the specified command or control statements file. The correct usage is displayed after this message.

S: Terminates processing.

O: Correct the error in the command or control statements file and re-execute.

KFPR26005-E E+L

Invalid option flag exists in command line

The command line contains an invalid option.

S: Cancels processing after analyzing the command line.

Action: Correct the specification on the command line and re-execute.

KFPR26006-E E+L

Invalid parameter aa....aa exists at -b option in command line

An option on the command line contains an invalid parameter. A list RDAREA is not copied or recovered.

aa....aa: Invalid parameter

b: Option name

S: Cancels processing after analyzing the command line. However, continues processing when all of the following conditions are met:

The -J or -r option is specified.
The KFPR26061-W message was output.

Action: Correct the specification on the command line and re-execute.; When the database copy utility (pdcopy) is used in conjunction with JP1/OmniBack II, re-execute pdsetup if -k o is displayed as the invalid parameter. For pdsetup, specify the OmniBack II parameter for the -p option (pdsetup -p OmniBack).

KFPR26007-E E+L

Duplicate aa....aa at -b option in command line

Information is duplicated in an option on the command line.
If the differential backup facility is used, an existing differential backup file name is specified in the -b option.

aa....aa: Duplicated command name

b: Option name

S: Terminates processing after analyzing the command line.

Action: Correct the specification on the command line and re-execute.

KFPR26008-E E+L

Invalid combination of option flags(-a and -b) exists in command line

There is an invalid combination of option flags on the command line.

a: Option flag combined invalidly

b: Option flag combined invalidly

S: Terminates processing after analyzing the command line.

Action: Correct the specification on the command line and re-execute.

KFPR26009-E E+L

Option flag -a is not specified in command line

A required option flag is missing on the command line.

a: Required option flag

S: Terminates processing after analyzing the command line.

Action: Correct the specification on the command line and re-execute.

KFPR26010-E E+L

Too long parameter exists at -a option in command line

Parameter specification for an option is too long on the command line.

a: Option name

S: Terminates processing after analyzing the command line.

Action: Correct the specification on the command line and re-execute.

KFPR26011-E E+L

Number of -a option flag in a control file exceeds bb

The number of -a option flags in a control statements file exceeds the maximum of bb.

a: Name of the option exceeding the maximum value

bb: Maximum value of -a option flag

S: Terminates processing after analyzing the command line.

Action: Correct the specification on the command line and re-execute.

KFPR26012-E L+S

HiRDB file aa....aa error, errno=bb....bb, HiRDB file name=cc....cc

Error aa....aa occurred in file cc....cc.

aa....aa: Nature of the error:: close: Close file; create: Create file; fstat: Collect file information; open: Open file; read: Read file; write: Write data to file; expand: Expand file; reopen: Opening of the second or subsequent volume of a multivolume file

bb....bb: Error code: 0: Could not perform read or write of the requested size.; Other: See 5.1 Error codes returned from HiRDB file system access requests.

cc....cc: Name of the file where the error occurred

S: For a backup file, aborts processing. However, continues processing when there is another backup file or all of the following conditions are met:

The applicable file is a HiRDB file comprising the RDAREA.
The -J option is specified or the RDAREA is a replica RDAREA.
The content of the error is open or close.
The KFPR26061-W message is output.
Other RDAREAs were not processed.

Action

For database file:: Recover the RDAREA and re-execute.

For backup file:

See 5.1 Error codes returned from HiRDB file system access requests to eliminate the cause of the error and re-execute.

If the error code is -1556 or -1562, the following causes can be assumed:

Error code	Cause
-1556	Secondary allocation expansion of the file failed because the HiRDB file had been expanded the maximum permissible number of times: An attempt was made to expand the file more times than permitted by the increments count specification (-e specification for pdfmkfs) for the HiRDB file system area An attempt was made to expand the HiRDB file more than 23 times (the maximum for the system)
-1562	Type of the HiRDB file system area is not UTL.

If the cause cannot be determined, contact a customer engineer.

KFPR26015-E L+S

Unable to backup RDAREA at inactive server aa....aa

When either of the following options is specified, an RDAREA in an inactive server cannot be backed up:

-M s
-z

aa....aa: Name of the inactive server

S: Terminates processing if the RDAREA included in the applicable server is to be copied. However, if there are other backup files, continues processing if all of the following conditions are met:

The -J option is specified.
The KFPR26061-W message is output.
Other RDAREAs were not processed.

Action: Activate the stopped server and re-execute. Or, back up the RDAREA with the -M x option specified.

KFPR26016-E L+S

Too many backup RDAREAs for backup file aa....aa

The number of RDAREAs to be backed up into backup file aa....aa exceeds the maximum of 1120.

aa....aa: Backup file name

S: Terminates processing.

O: Correct the number of the RDAREAs to be backed up into the backup file to no more than 1120 and re-execute.

KFPR26017-E L+S

Insufficient memory in message buffer pool due to concurrent execution of "pdcopy"

A temporary memory shortage occurred in the message storage buffer pool for the utility server when pdcopy was executed concurrently.
The KFPS00854-W message may be output when this error occurs; however, a server error has not occurred in this case.

S: Terminates processing.

O: Wait until execution of the current pdcopy is completed, then re-execute.

KFPR26018-E L+S

Unable to send message from aa....aa to bb....bb

Data cannot be sent from host aa....aa to host bb....bb because a communication error occurred.

aa....aa: Send source host name: If the system switching facility is being used, the host name of the primary system is indicated.

bb....bb: Send destination host name: If the system switching facility is being used, the host name of the primary system is indicated.

S: Cancels processing of the backup file resulting in the communication error.

Action: Take action appropriate to the KFPR26001-E message that was output before this message. If a physical communication error has not occurred, there may be an inconsistency in the system definitions concerning the relationship between the hosts; check the interhost definitions for the hosts affected by the error and re-execute.

KFPR26020-E L+S

System manager "aa....aa" failed, return code=bb....bb

System-related function "aa....aa" resulted in an error.

aa....aa: Name of the system-related function resulting in the error

bb....bb: Error code set by the system-related function resulting in the error

S: Terminates processing.

Action: See 4. Error Detail Codes to eliminate the cause of the error, and re-execute. If the error cannot be corrected by the HiRDB administrator, contact a customer engineer.

KFPR26021-E L+S

Unable to output result of pdcopy

The result of the database copy utility (pdcopy) cannot be output due to the error reported before this message.

S: Terminates processing.

Action: Eliminate the cause of the error and re-execute. If no other error occurred, backup processing terminated; if the execution result is not needed, there is no need to re-execute the processing.

KFPR26022-I L+S

Output result of pdcopy to aa....aa

The result of the database copy utility (pdcopy) was output to file aa....aa.

aa....aa: Name of output file

S: Terminates processing.

KFPR26023-I L+S

Unable to output result of backup file aa....aa

The processing result of backup file aa....aa cannot be output due to the error reported before this message.

aa....aa: Backup file name

S: Terminates processing.

Action: Eliminate the cause of the error and re-execute. If the KFPR26109 message was issued for the backup file, backup processing was terminated; if the execution result is not needed, there is no need to re-execute the processing.

KFPR26024-E L+S

Unable to remove shared memory, key=aa....aa

Shared memory cannot be deleted.

aa....aa: Shared memory key value

S: Resumes processing.

Action: Use a command to delete the shared memory after processing has terminated.

KFPR26025-E L+S

No RDAREA to copy on aa....aa

Backup file aa....aa does not contain the RDAREA to be copied.

aa....aa: Name of backup file (the last portion of the path name)

S: Terminates processing. However, continues processing when both of the following conditions are met.

The -J option is specified.
Multiple rows in the control statements file are specified.

Action: Correct the specification on the command line and re-execute.

KFPR26026-E L+S

Unable to copy RDAREA's of different servers with -z option

When the -z option is specified, a backup file of RDAREAs in different servers cannot be made concurrently.

S: Terminates processing.

Action: Make the backup file of RDAREAs in the same server and re-execute.

KFPR26027-E L+S

Unable to output Log point information

Log point information cannot be output because of the error indicated by the error message output before this message.

S: Terminates processing.

Action: Eliminate the cause of the error, input the backup file created with pdrstr, then re-create the log point information file by specifying the -z option.

KFPR26028-I L+S

Output Log point information to aa....aa

Log point information has been output to log point information file aa....aa.

S: Resumes processing.

KFPR26029-I L+S

Log point information, (aa....aa, bb....bb, ccc, dd....dd, ee....ee, ff....ff, gg....gg, hh....hh, ii....ii. jj....jj, kk....kk)

Log point has been set.

aa....aa: HiRDB identifier

bb....bb: Unit identifier

ccc: Log file name:: sys: System log file

dd....dd: Server name

ee....ee: Server run ID (8 hexadecimal digits)

ff....ff: Log server run ID (8 hexadecimal digits)

gg....gg: Name of first file group

hh....hh: Generation number of first file group (up to 8 hexadecimal digits)

ii....ii: First block number (up to 8 hexadecimal digits)

jj....jj: Header updates count (up to 8 hexadecimal digits)

kk....kk: Use start time (8 hexadecimal digits)

S: Resumes processing.

KFPR26030-E L+S

Unable to use -M s option to RDAREA for BLOB column with recovery partial or no, RDAREA name=aa....aa

The -M s option cannot be used for the RDAREA containing the target LOB column because recovery partial or recovery no was specified in the LOB column definition of CREATE TABLE.

aa....aa: Name of RDAREA that caused the error

S: Terminates processing if the applicable RDAREA is to be copied. However, continues processing if there are other backup files or all of the following conditions are met:

The -J option is specified.
The KFPR26061-W message is output.
Other RDAREAs were not processed.

O: Specify -M x or -M r and re-execute.

KFPR26031-E L

Unable to output message to standard output, host=aa....aa, file=bb....bb, func=cc....cc, errno=ddd

Messages cannot be output to standard output because a system call error occurred.

aa....aa: Name of the host where the file resulting in the error is located

bb....bb: Name of the file resulting in the error: When the name of the system call resulting in the error is tempnam, ****** is displayed.

cc....cc: Name of the system call resulting in the error: In UNIX, the name of the shell command that was executed is displayed, enclosed in parentheses.

ddd: errno of the system call resulting in the error

S: Resumes processing.

O: Check the value of the error indicator and refer to errno.h or the applicable OS manual to eliminate the cause of the error.

KFPR26032-E L

Unable to remove temporary file, host=aa....aa, file=bb....bb

A temporary file cannot be deleted because of the error that was output before this message.

aa....aa: Name of the host where the file that cannot be deleted is located

bb....bb: File name that cannot be deleted

S: Resumes processing.

O: Waits until processing terminates, then delete the temporary file.

KFPR26033-E L+S

Pdcopy must be executed at unit defined as manager

The database copy utility (pdcopy) must be executed at the unit where the system manager is defined.

S: Terminates processing.

O: Execute remote login at the unit where the system manager (MGR) is defined and re-execute the command.

KFPR26045-I L+S

OmniBack II backup session id=aa....aa

Session whose session ID is aa....aa has been backed up.

aa....aa: JP1/OmniBack II session ID

S: Continues processing.

KFPR26047-I L+S

OmniBack II Information = aa....aa

Displays JP1/OmniBack II message information.

aa....aa: JP1/OmniBack II message information: Only the first 180 characters are displayed when the message information consists of more than 180 characters.

S: Terminates processing.

Action: For details of the JP1/OmniBack II message information, see the JP1/OmniBack II manual.

KFPR26048-E L+S

OmniBack II file not found, host=aa....aa file=bb....bb

Because JP1/OmniBack II file bb....bb was not found at host aa....aa, the database copy utility (dbcopy) could not be executed.

aa....aa: Host name

bb....bb: File name

S: Terminates processing.

Action: Ensure that the JP1/OmniBack II disk agent has been installed at host aa....aa. If it has not been installed, install it. If it has been installed, contact a customer engineer.

KFPR26049-E L+S

Unable to check OmniBack II file, host=aa....aa

Refer to the message that was output before this message. As a result of the error explained in that message, the JP1/OmniBack II file at host aa....aa could not be checked and the database copy utility (dbcopy) could not be executed.

aa....aa: Host name

S: Terminates processing.

Action: Correct the error by referring to the message that was output before this message, then re-execute the utility.

KFPR26051-E L+S

Unable to output history of backup group=aa....aa

Statistical information on differential backup group aa....aa could not be output. For the error cause, refer to the message that was output before this message.

aa....aa: Differential backup group name

S: Terminates processing.

Action: Correct the error and re-execute. If the KFPR26053-I or KFPR26058-I message has been output for the differential backup management file, the backup processing terminated. Therefore, if the history information is not needed, re-execution is not necessary.

KFPR26052-I L+S

Output history of backup group=aa....aa to bb....bb

Displays the statistical information file (file name bb....bb) for differential backup group aa....aa.

aa....aa: Differential backup group name

bb....bb: Name of the statistical information file for the differential backup

S: Continues processing.

KFPR26053-I L+S

Create management file=aa....aa

Differential backup management file aa....aa has been created.

aa....aa: Differential backup management file name

S: Continues processing.

KFPR26054-E L+S

Unable to use management file, reason=aa....aa, name=bb....bb

Differential backup management file bb....bb cannot be used.

aa....aa: Reason:: unfinish maintenance: Maintenance is not completed.; no control block: Control information for the differential backup management file was not found.

bb....bb: Differential backup management file name

S: Terminates processing.

Action

Take one of the following actions:

unfinish maintenance:
If there is a backup of the differential backup management file, use the pdfrstr command to recover the differential backup management file and re-execute. If there is no backup of the differential backup management file, make a backup with the pdcopy command. In this step, specify creation of a differential backup management file (specify (S) for the differential backup group name in the -g option).
no control block:
The specifications of the -g and -K options for the pdcopy command are invalid; make another backup.

KFPR26055-E E+L

Page corrupted, management file name=aa....aa, page number=bb....bb

Page corruption of differential backup management file aa....aa was detected.

aa....aa: Differential backup management file name

bb....bb: Page number in which page corruption was detected

S: Terminates processing.

Action: If there is a backup of the differential backup management file, use the pdfrstr command to recover the differential backup management file and re-execute. If there is no backup of the differential backup management file, make a backup with the pdcopy command. In this step, specify creation of a differential backup management file (specify (S) for the differential backup group name in the -g option).

KFPR26056-E L+S

SystemID of aa....aa is invalid

The file cannot be used because the system ID for aa....aa does not match the system ID of the HiRDB that is running.

aa....aa: File type: management file: Differential backup management file

S: Terminates processing.

Action: The differential backup management file is specified incorrectly. In the KFPR26006-E message that is output simultaneously, check the parameters for the -g and -K options, specify the correct parameters for these options, and re-acquire a differential backup.

KFPR26057-I L+S

Update start, management file name=aa....aa

Updating of differential backup management file aa....aa has begun.

aa....aa: Differential backup management file name

S: Continues processing.

KFPR26058-I L+S

Update complete, management file name=aa....aa

Updating of differential backup management file aa....aa has been completed.

aa....aa: Differential backup management file name

S: Continues processing.

KFPR26059-E E+L

Too many lines for control file

There are too many lines in the command line in the control statements file.

S: Terminates processing.

Action: Correct the command in the control statements file. When using the differential backup facility, enter only one row in the command line described in the control statements file. If the -a or -q option is specified, enter only one line in the command line described in the control statements file.

KFPR26060-I L+S

Backup all used page, RDAREA name=aa....aa, LSN=bb....bb, differential base LSN=cc....cc

Because differential management information for the differential backup could not be obtained, all used pages in this RDAREA will be included. This backup can be used for database recovery.

aa....aa: RDAREA name

bb....bb: Internal information 1

cc....cc: Internal information 2

S: Continues processing.

KFPR26061-W L+S

Unable to backup RDAREA. RDAREA name=aa....aa

aa....aa could not be backed up.

aa....aa: RDAREA name

S: Continues processing.

Action: If RDAREA aa....aa should not be copied, no particular action is required. If RDAREA aa....aa is to be copied, see the message output before or after this message to eliminate the cause of the error, and then re-execute.

KFPR26062-W L+S

Unable to find RDAREA. RDAREA name=aa....aa, generation number=bb

The RDAREA of the specified generation number could not be found. The process for backing up this RDAREA was skipped.

aa....aa: RDAREA name

bb: Generation number

S: Continues processing.

Action: Reevaluate the specified RDAREA name or generation number. If a backup is necessary, correct the RDAREA name or generation number, and then re-execute. If a backup is not required, ignore this message.

KFPR26063-I L+S

Buckup partially ended, file=aa....aa

Backup file aa....aa could not be created. The RDAREA causing an error during the backup process was skipped.

aa....aa: Backup file name

S: Continues processing.

Action: Check if the RDAREA whose processing was skipped is needed as a backup. If it is, eliminate the cause of the error, and then re-execute.

KFPR26066-E L+S

Unable to use the "-k n" option because the JP1/VERITAS NetBackup Agent for HiRDB license not found

The -k n option cannot be specified because the license required to use the JP1/VERITAS NetBackup linkage facility is missing.

S: Terminates processing.

Action: Obtain and install the license required to use the JP1/VERITAS NetBackup linkage facility.

KFPR26067-E L+S

Dynamic load error occurred, shared library=aa....aa, host=bb....bb

Dynamic loading of common library aa....aa on host bb....bb failed.

aa....aa: Full path name of the shared library (in UNIX, the file path name of the shared library)

bb....bb: Host name

S: Terminates processing.

Action: Check if a NetBackup client is installed. If a copy is installed, see the KFPR26003-E message just output to eliminate the cause of the error, and then re-execute.

KFPR26069-E L+S

NetBackup API error occurred, return code=aa....aa(bbbb), func=cc....cc, message=dd....dd

A problem occurred in the application programming interface of NetBackup.

aa....aa: Name of the application programming interface return code for NetBackup

bbbb: Application programming interface return code for NetBackup (hexadecimal)

cc....cc: Application programming interface for NetBackup

dd....dd: The message obtained after the application programming interface error return for NetBackup (displays the first 100 characters if the message length exceeds 100 characters)

S: Terminates processing.

Action

Return code (bbbb)	Return code name (aa....aa)	Meaning	Action
0x03	SYSTEM_ERROR	NetBackup internal error	Check the error cause at the NetBackup management console, take appropriate action, and then re-execute.
0x0D	FEATURE_NOT_LICENSED	No license was found or the license was invalid	Obtain a license.
0x4B	VERSION_NOT_SUPPORTED	NetBackup version is not supported	Check if the NetBackup version is correct.
0x4D	ACCESS_FAILURE	Cannot access the object	Check if the NetBackup master server or NetBackup media server stopped. If the server did not stop, contact a customer engineer^*.
Other			Contact a customer engineer^*.

: Does not apply.

^* Obtain the following data before contacting a customer engineer:

The system log file of the host with a single server or system manager, the host with the -b option specified, or the host with the target RDAREA when executing the utility
Files in the %PDDIR%\spool directory on the host with a single server or system manager, the host with the -b option specified, or the host with the target RDAREA when executing the utility
Error information from the NetBackup management console
Messages output to standard output or standard error
Process results output file from when the utility was executed

KFPR26071-I L+S

NetBackup information, policy=aa....aa, date=bb....bb, time=cc....cc

Obtain a backup with policy name aa....aa.

aa....aa: Policy name

bb....bb: Date (YYYY/MM/DD)

cc....cc: Time (HH:MM:SS)

S: Continues processing.

KFPR26072-E L+S

Invalid time stamp found, RDAREA name=aa....aa, file name=bb....bb, offset=cc....cc, time stamp=(dd....dd,ee....ee)

Some of the pages were found to have an invalid timestamp.

aa....aa: RDAREA name

bb....bb: HiRDB file name. The last 64 bytes are displayed.

cc....cc: Relative position, in decimal, of the pages with an invalid timestamp from the front of the HiRDB file.

dd....dd: Timestamp at the start of the page. It is converted to the format YYYY/MM/DD HH:MM:SS for display.

ee....ee: Timestamp at the end of the page. It is converted to the format YYYY/MM/DD HH:MM:SS for display.

S: Terminates processing.

Action

If the backup is collected in reference updatable mode (pdcopy -Ms):

A backup cannot be acquired because the page to be backed up is undergoing update. Take one of the following actions:

Execute the pdlogsync -w command and re-execute.
Perform an updatable backup hold (pdhold -b -u) and re-execute.
Re-execute in referenceable mode (pdcopy -Mr) or in reference non-updatable mode (pdcopy -Mx).

If backing up in referenceable mode (pdcopy -Mr) or reference non-updatable mode (pdcopy -Mx):

The area of the displayed RDAREA is corrupt. The previous backup must be used to recover.

KFPR26073-E L+S

Unable to backup shared RDAREA with -M s option, RDAREA name="aa....aa"

Backup of the shared RDAREA could not be performed using the pdcopy -M s specification (updatable mode).

aa....aa: RDAREA name

S: Terminates processing.

Action: To back up multiple RDAREAs, including shared RDAREAs, at one time, specify a mode other than updatable mode and re-execute the command.; To back up in multiple parts, specify only the non-shared RDAREAs and re-execute the command. For the shared RDAREAs, specify a backup mode other than updatable mode and re-execute the command.

KFPR26109-I L+S

Backup completed, file=aa....aa

Database has been backed up into backup file aa....aa.

aa....aa: Name of backup file

S: Resumes processing.

KFPR26110-E L+S

Invalid RDAREA status, RDAREA name="aa....aa"

Because the status of the indicated RDAREA is invalid, it cannot be backed up.
Possible causes of this error are as follows:

-M x was specified, but the specified RDAREA was not on closed status.
The specified RDAREA is involved in structure modification.
If -M s is specified and another user executes an SQL that causes the page to be released, a conflict occurs at resource type 0152 or 0004, and there are cases in which the process waits for lock release until the transaction terminates. The following SQL statements cause pages to be released:
DROP TABLE
DROP INDEX
PURGE TABLE
An INSERT statement or UPDATE statement for an indexed column
A DELETE statement for an indexed column (with multiple keys)
A DELETE statement or UPDATE statement with variable row length after executing the LOCK statement
An INSERT statement, DELETE statement, or UPDATE statement for a LOB column

aa....aa: RDAREA name

S: Terminates processing when the applicable RDAREA is to be copied. However, continues processing if there is another backup file or if all the following conditions are met:

The -J option is specified.
The KFPR26061-W message is output.
There are other unprocessed RDAREAs.

Action: Place the corresponding RDAREA on closed status with the pdclose command and re-execute. Alternatively, wait until the other user's process terminates, and then re-execute.

KFPR26111-E L+S

To copy Master RDAREA with -M x option, pdstart should be executed with -r option

Start the HiRDB system with pdstart -r when backing up the master RDAREA with -M x specified.

S: Terminates processing. However, continues processing when all of the following conditions are met.

The -J option is specified.
The KFPR26061-W message was output.
There are other unprocessed RDAREAs.

O: Terminate the HiRDB system using the pdstop command, restart it with pdstart -r, then re-execute.

KFPR26201-E E+L

Communication "aa....aa" error occurred, code=bbbbb

A communication error occurred while the database recovery utility (pdrstr) was being executed.

aa....aa: Name of the RPC-related function resulting in the error

bbbbb: Error code set by the RPC-related function resulting in the error

S: Terminates processing.

Action: See 4. Error Detail Codes to eliminate the cause of the error, and re-execute. If the error cannot be corrected by the HiRDB administrator, contact a customer engineer.

KFPR26202-E L+S

Unable to allocate COMBUF area, size=aaaaaa

A communication area cannot be allocated because a real or virtual memory space shortage occurred.

aaaaaa: Size (in KB) of communication area that was to be allocated

S: Terminates processing.

Action

Re-execute the command after a process that uses a large amount of memory has terminated.
In UNIX, If a value greater than 32 was specified for the buffer size (pd_utl_buff_size operand) in the system common definition, specify 32, and then re-execute the command.

KFPR26203-E L+S

System call error, func=aa....aa, errno=bbb

A system call error occurred.

aa....aa: Name of the system call resulting in the error

bbb: errno value of the system call resulting in the error

S: Terminates processing.

Action: Check the value of the error indicator, refer to errno.h and the applicable OS manual to eliminate the cause of the error, then re-execute.

KFPR26204-I E

Error exists in command line or control file, usage is as follows

An error was detected in the specified command or control statements file. The correct usage is displayed after this message.

S: Terminates processing.

O: Correct the error in the command or control statements file and re-execute.

KFPR26205-E E+L

Invalid option flag exists in command line

The command line contains an invalid option.

S: Terminates processing after analyzing the command line.

Action: Correct the specification on the command line and re-execute.

KFPR26206-E E+L

Invalid parameter aa....aa exists at -b option in command line

An option on the command line contains an invalid parameter. A list RDAREA is not copied or recovered.

aa....aa: Invalid parameter

b: Option name

S: Terminates processing after analyzing the command line.

Action: Correct the specification on the command line and re-execute.; When the database recovery utility (pdrstr) is used in conjunction with JP1/OmniBack II, re-execute pdsetup if -k o is displayed as the invalid parameter. In pdsetup, specify the OmniBack II parameter in the -p option (pdsetup -p OmniBack).

KFPR26207-E E+L

Duplicate aa....aa at -b option in command line

Information is duplicated in an option on the command line.

aa....aa: Duplicated name

b: Option name

S: Terminates processing after analyzing the command line.

Action: Correct the specification on the command line and re-execute.

KFPR26208-E E+L

Invalid combination of option flag (-a and -bb....bb) exists in command line

There is an invalid combination of option flags on the command line.

a: Option flag combined invalidly

bb....bb: Option flag combined invalidly: If "(in control file)" is output after the option flag is combined invalidly, this indicates that the option flags on the command line and the option flags in the control statement are combined invalidly.

S: Terminates processing after analyzing the command line.

Action: Revise the command line or control statement specification and re-execute.

KFPR26209-E E+L

Option flag -aa....aa is not specified in command line

A required option flag is missing on the command line.

aa....aa: Required option flag: If the required option flag is a selection item, all selection candidates are output.

S: Terminates processing after analyzing the command line.

Action: Revise the command line specification and re-execute.

KFPR26210-E E+L

Too long parameter exists at -a option in command line

Parameter specification for an option is too long on the command line.

a: Option name

S: Terminates processing after analyzing the command line.

Action: Correct the specification on the command line and re-execute.

KFPR26212-E L+S

HiRDB file aa....aa error , errno=bb....bb, HiRDB file name=cc....cc

Error aa....aa occurred in file bb....bb.

aa....aa: Nature of error:: close: Close file; create: Create file; fstat: Collect file information; open: Open file; read: Read file; write: Write data to file; expand: Expand file; reopen: Open the second or subsequent volume of a multivolume file

bb....bb: Error code: 0: Could not perform a read or write in the requested size.; Other: See 5.1 Error codes returned from HiRDB file system access requests.

cc....cc: Name of the file resulting in the error

S:

For database file:: Skips recovery processing of the affected RDAREA and resumes recovery processing of other RDAREAs.

For backup file:: Cancels recovery processing.

Action

For database file:: Provide a separate HiRDB file system area for the affected RDAREA and re-execute.

For backup file:: Use another backup file and re-execute.; If the error content is write and the error code is 0, the operating system file system may have a capacity shortage. If the error content is read and the error code is 0, the error may have occurred when only the log was recovered for the RDAREA of the HiRDB file system area created without specifying the -i option with the pdfmkfs command.; If the cause of the error cannot be determined, contact a customer engineer.

KFPR26215-E L+S

Unable to recover RDAREA at inactive server aa....aa

An RDAREA in an inactive server cannot be recovered with -l, -L, or -d specified.

aa....aa: Name of the inactive server

S: Cancels recovery of the RDAREA in this server.

Action: Activate the stopped server and re-execute.

KFPR26216-E L+S

Too many RDAREAs for recovery

The number of RDAREAs to be recovered exceeds the maximum (which is 1120 per server).

S: Terminates processing.

O: Correct the number of RDAREAs to be recovered to no more than 1120 and re-execute.

KFPR26217-E L+S

Insufficient memory in message buffer pool due to concurrent execution of "pdrstr"

A temporary memory shortage occurred in the message storage buffer pool for the utility server when pdrstr was executed concurrently.
The KFPS00854-W message may be output when this error occurs; however, a server error has not occurred in this case.

S: Terminates processing.

O: Wait until execution of current pdrstr is completed, then re-execute.

KFPR26218-E L+S

Unable to send message from aa....aa to bb....bb

Data cannot be sent from host aa....aa to host bb....bb because a communication error occurred.

aa....aa: Send source host name: If the system switching facility is being used, the host name of the primary system is indicated.

bb....bb: Send destination host name: If the system switching facility is being used, the host name of the primary system is indicated.

S: Cancels processing of the backup file resulting in the communication error.

Action: Take action appropriate to the KFPR26201-E message that was output before this message. If the error is not a physical communication error, there may be an inconsistency in the system definitions concerning the relationship between the hosts; check the interhost definitions for the hosts affected by the error and re-execute.

KFPR26220-E L+S

System manager "aa....aa" failed, return code=bb....bb

System-related function "aa....aa" resulted in an error.

aa....aa: Name of the system-related function resulting in the error

bb....bb: Error code set by the system-related function resulting in the error

S: Terminates processing.

Action

The name of the system function in which the error occurred is pdi_omm_attach and the error code is -144.

To resolve one of the following suspected problems, re-execute the command by specifying the correct host name in the -m option:

The host name was omitted in the -m option and the specified master directory RDAREA is not on the server machine into which the pdrstr command was entered.
A master directory RDAREA was not found on the server machine with the host name specified in the -m option.

Other cases:: See 4. Error Detail Codes to correct the cause of the error and re-execute the command. If an error that cannot be corrected by the HiRDB administrator has occurred, contact a customer engineer.

KFPR26221-E L+S

Unable to output result of pdrstr

The result of the database recovery utility cannot be output due to the error reported before this message.

S: Terminates processing.

Action: Eliminate the cause of the error and re-execute. If no other error has occurred, recovery processing has terminated (if the execution result is not needed, there is no need to re-execute the processing).

KFPR26222-I L+S

Output result of pdrstr to aa....aa

The result of the database recovery utility was output to file aa....aa.

aa....aa: Name of output file

S: Resumes processing.

KFPR26224-E L+S

Unable to remove shared memory, key=aa....aa

Shared memory cannot be deleted.

aa....aa: Shared memory key value

S: Resumes processing.

Action: Delete the shared memory with a command after processing has terminated.

KFPR26225-E L+S

No RDAREA to restore

The RDAREA to be recovered was not found.

S: Terminates processing.

Action: Correct the specification on the command line and re-execute.

KFPR26226-E L+S

System ID of aa....aa is invalid

Because the system ID for aa....aa does not match the active HiRDB, the database cannot be recovered.

aa....aa: Type of file:: backup file: Backup file; sys log file: System log file; unload log file: Unload log file; management file: Differential backup management file

S: Terminates processing.

Action

Take one of the following actions:

For backup file or unload log file:
Specify the correct file and re-execute.
For system log file
System log file may have been damaged. Check whether the log file definition has been changed and initialized.
For differential backup management file
The specifications of the -g and -K options are invalid. Specify the correct values and re-execute the pdrstr command.

KFPR26227-E L+S

-l or -d option is not specified for backup file with -M s option

No unload log file was specified for recovering data from a backup file that was created with the -M s option specified.

S: Terminates processing.

Action

If -l is specified:: Specify the unload log file and re-execute.

If -d is specified:: Specify the directory where the unload log file is stored and re-execute.

KFPR26228-E L+S

Invalid RDAREA status, RDAREA name="aa....aa"

Because the indicated RDAREA is not on hold or on closed status or is in use by another user, it cannot be restored.

aa....aa: RDAREA name

S: Cancels recovery of this RDAREA and recovers another RDAREA.

Action: Place the RDAREA on hold or on closed status and re-execute. Or, wait until the other user's process terminates, then re-execute.

KFPR26229-E L+S

To recover Master RDAREA, pdstart should be executed with -r option

To recover the master directory RDAREA, start the HiRDB system with pdstart -r.

S: Terminates processing.

O: Terminate the HiRDB system with the pdstop command, start it with pdstart -r, then execute.

KFPR26230-E L+S

Unable to use -c option, deleted RDAREA "aa....aa" exist in backup file

Although the -c option was specified during execution of pdrstr, RDAREA "aa....aa" in the specified backup file does not exist in the system (the RDAREA may have been deleted after the backup file was made).
Consequently, the -c option cannot be specified for the backup file.

S: Terminates processing.

O: Specify the correct backup file and re-execute. Alternatively, specify the RDAREAs to be recovered with an option other than the -c option, then re-execute.

KFPR26232-E L+S

Unable to output Log point information

Log point information cannot be output because of the error that was output before this message.

S: Terminates processing.

Action: Eliminate the cause of the error and re-execute.

KFPR26233-I L+S

Output Log point information to aa....aa

Log point information was output to log point information file aa....aa.

aa....aa: Name of the log point information file

S: Terminates processing.

KFPR26234-E L+S

Log point information not found in backup

Log point information cannot be found in the backup file. Recovery specified by -L or re-creation of the log point information file (-z) cannot be performed.

S: Terminates processing.

Action: Specify the backup file that was acquired by specifying -z and re-execute.

KFPR26235-E L+S

System log file for recovery not swapped

System log file needed for database recovery has not been swapped out.

S: Terminates processing.

Action: Use the pdlogswap command to swap system log files and re-execute.

KFPR26236-E L+S

Error occurred in log file group, file group=aa....aa, reason=(bbb, ccccc)

An error occurred in a log file group.

aa....aa: Name of the log file group resulting in the error

bbb: Reason code

ccccc: Detail code

S: Terminates processing.

Action

Following are the reason codes and actions:

Reason code	Explanation	Action
-1	Argument is invalid.	Contact a customer engineer.
-2	Fatal error or unexpected error occurred.	Contact a customer engineer.
-31	Error in log file definition analysis function	System log file definition has been changed incorrectly; refer to the detail code to revert to the original definition.

Following are the detail codes:

Detail code	Explanation
-1	File group name in definition is invalid.
-2	System A file name in definition is invalid.
-3	System B file name in definition is invalid.

KFPR26237-E L+S

Error occurred in log element file, file group=aa....aa, system A/B:b, reason=(ccc, ddddd)

An error occurred in a system log file.

aa....aa: Name of the file group resulting in the error

b: System in which the error occurred

ccc: Reason code

ddddd: Detail code

S: If the error did not occur in a log file in the other system, the HiRDB system resumes processing using the log file in the other system.

Action

Take action appropriate to the reason code: If a reason code that is not listed is output, contact the customer engineer.

Reason code	Explanation	Action
-40 -41 -42 -43	I/O error occurred.	Refer to the detailed code and the error code in Section 5.1 Error codes returned from HiRDB file system access requests to eliminate the cause of the error.
-50 -51 -52 -53	File contents are invalid.	The log file may have been damaged. Check whether the log file definition has been changed and initialized and whether an invalid status has been set. The detail code is system maintenance information.

KFPR26238-E L+S

Log is out of -T option value, RDAREA name=aa....aa, bb....bb time=(cc....cc), dd....dd time=(ee....ee)

Recovery based on a time specified in the -T option is not possible because the specified time is not within the period covered by the log.

aa....aa: RDAREA name

bb....bb: Start or end time:: "start": Recovery start time specified in the -T option is later than the log end time; "end": Recovery end time specified in the -T option is earlier than the log start time

cc....cc: Recovery start or end time specified in the -T option

dd....dd: First or last unload log file: ("first"|"last")

ee....ee: Log start or end time

S: Terminates processing.

O: Correct the -T option and re-execute.

KFPR26239-E L+S

Invalid aa....aa value in -T option for RDAREA name=bb....bb, transaction commited at cc....cc

The recovery end time specified in the -T option for RDAREA bb....bb is invalid. Times earlier and later than the transaction synchronization point time are specified in the -T options as the recovery end times for the RDAREAs updated by the transaction.

aa....aa: Recovery end time specified for the RDAREA

bb....bb: RDAREA name

cc....cc: Time when the transaction synchronization point was reached

S: Terminates processing.

O: Set the -T option recovery end times specified for the RDAREAs updated by the transaction so that they all either include or do not include the synchronization point, then re-execute.

KFPR26240-E L+S

Backup is out of aa....aa in -T option value, RDAREA name=bb....bb

The recovery end time specified in the -T option for RDAREA aa....aa is invalid.

aa....aa: Recovery end time specified for the RDAREA

bb....bb: RDAREA name

S: Terminates processing.

O: Specify in the -T option a recovery end time that is later than the backup acquisition time and re-execute.

KFPR26241-W L+S

Transaction is running at recovery end time, RDAREA name=aa....aa, end time=(bb....bb), Transaction count=cc....cc

The recovery end time specified for recovery of RDAREA aa....aa includes a transaction being executed. A transaction being executed at the recovery end time cannot be recovered.

aa....aa: RDAREA name

bb....bb: Recovery end time of the RDAREA

cc....cc: Number of transactions being executed

S: Resumes processing.

O: To recover a transaction being executed at the recovery end time, specify the time that the transaction ended as the recovery end time and re-execute.

KFPR26242-E L

Unable to output message to standard output, host=aa....aa, file=bb....bb, func=cc....cc, errno=ddd

Messages cannot be output to standard output because a system call error occurred.

aa....aa: Name of the host where the file resulting in the error is located

bb....bb: Name of the file resulting in the error: When the name of the system call resulting in the error is tempnam, ****** is displayed.

cc....cc: Name of the system call resulting in the error: In UNIX, the name of the shell command that was executed is displayed, enclosed in parentheses.

ddd: errno of the system call resulting in the error

S: Resumes processing.

O: Check the value of the error indicator and refer to errno.h or the applicable OS manual to eliminate the cause of the error.

KFPR26243-E L

Unable to remove temporary file, host=aa....aa, file=bb....bb

A temporary file cannot be deleted because of the error that was output before this message.

aa....aa: Name of the host where the file that cannot be deleted is located

bb....bb: Name of file that cannot be deleted

S: Resumes processing.

O: Wait until processing terminates, then delete the temporary file.

KFPR26244-E L+S

Pdrstr must be executed at unit defined as manager

The database copy utility (pdcopy) must be executed at the unit where the system manager is defined.

S: Terminates processing.

O: Execute remote login to the unit where the system manager (MGR) is defined and re-execute the command.

KFPR26245-I L+S

OmniBackII backup session id=aa....aa

The database will be recovered using the object with session ID aa....aa as the backup.

aa....aa: JP1/OmniBack II session ID

S: Continues processing.

KFPR26246-E L+S

OmniBackII object not found

The specified JP1/OmniBack II object was not found.

S: Terminates processing.

Action: The object name specified in the -b option is invalid. Specify the correct name and re-execute. A list of object names can be displayed by executing the ominidb -stream command of JP1/OmniBack II.

KFPR26247-I L+S

OmniBackII information =aa....aa

Displays JP1/OmniBack II message information.

aa....aa: JP1/OmniBack II message information: Only the first 180 characters are output when the message information consists of more than 180 characters.

S: Terminates processing.

Action: For details of the JP1/OmniBack II message information, see the JP1/OmniBack II manual.

KFPR26248-E L+S

OmniBack II file not found, host=aa....aa file=bb....bb

Because JP1/OmniBack II file bb....bb was not found at host aa....aa, the database recovery utility (pdrstr) could not be executed.

aa....aa: Host name

bb....bb: File name

S: Terminates processing.

Action: Ensure that the JP1/OmniBack II disk agent has been installed at host aa....aa. If it has not been installed, install it. If it has been installed, contact a customer engineer.

KFPR26249-E L+S

Unable to check OmniBack II file, host=aa....aa

Refer to the message that was output before this message. Because of the error explained in that message, the JP1/OmniBack II file of host aa....aa could not be checked, and therefore the database recovery utility (pdrstr) or the pdbkupls command cannot be executed.

aa....aa: Host name

S: Terminates processing.

Action

See the action listed for the message that was output before the relevant message in the syslogfile, remove the cause of the error, then re-execute.

KFPR26254-E L+S

Unable to use management file, reason=aa....aa, name=bb....bb

Differential backup management file bb....bb cannot be used.

aa....aa: Reason:: unfinish maintenance: Maintenance is not completed.; no control block: Control information for the differential backup management file was not found.

bb....bb: Differential backup management file name

S: Terminates processing.

Action

Take one of the following actions:

unfinish maintenance:
If there is a backup of the differential backup management file, use the pdfrstr command to recover the differential backup management file, and then re-execute the pdrstr command. If there is no backup of the differential backup management file, execute recovery without using a differential backup management file. For the recovery procedure when a differential backup management file is not available, see the HiRDB Version 8 System Operation Guide.
no control block:
The specifications of the -g and -K options for the pdcopy command are invalid; specify the correct values and re-execute the pdrstr command.

KFPR26255-E E+L

Page corrupted, management file name=aa....aa, page number=bb....bb

Page corruption of differential backup management file aa....aa was detected.

aa....aa: Differential backup management file name

bb....bb: Page number in which page corruption was detected

S: Terminates processing.

Action: If there is a backup of the differential backup management file, use the pdfrstr command to recover the differential backup management file, then re-execute the pdrstr command.; If there is no backup of the differential backup management file, execute recovery without using a differential backup management file. For the recovery procedure when a differential backup management file is not available, see the HiRDB Version 8 System Operation Guide.

KFPR26257-I L+S

Update start, management file name=aa....aa

Updating of differential backup management file aa....aa has begun.

aa....aa: Differential backup management file name

S: Continues processing.

KFPR26258-I L+S

Update complete, management file name=aa....aa

Updating of differential backup management file aa....aa has been completed.

aa....aa: Differential backup management file name

S: Continues processing.

KFPR26262-W L+S

Unable to find RDAREA. RDAREA name=aa....aa, generation number=bb

An RDAREA with the specified generation number could not be found. Recovery processing of this RDAREA was skipped.

aa....aa: RDAREA name

bb: Generation number

S: Continues processing.

Action: Reevaluate the specified RDAREA name or generation number. When recovering the RDAREA is necessary, correct the RDAREA name or generation number, and then re-execute. When recovering the RDAREA is not necessary, ignore this message.

KFPR26263-E L+S

Invalid log of RDAREA. RDAREA name=aa....aa(bb,cc), information=(dd....dd,ee....ee,ff....ff), (gg....gg,hh....hh,ii....ii)

When the logs for generation bb and generation cc of RDAREA aa....aa were read in, a log indicating that both generations were updated at the same time was found. It is possible that updating of generation bb and generation cc was performed out of synch with each other.
Recovery of RDAREA aa....aa failed. Recovery using the -x option cannot be performed.

aa....aa: RDAREA name

bb: Generation specified in the -q option

cc: Generation specified in the -x option

dd....dd: Output time of the previous log (format: YYYY/MM/DD HH:MM:SS)

ee....ee: Internal information

ff....ff: Internal information

gg....gg: Output time of the log with updates in reverse order (format: YYYY/MM/DD HH:MM:SS)

hh....hh: Internal information

ii....ii: Internal information

S: Continues processing.

Action: For details about what to do if you cannot use second generation RDAREA system logs to recover the RDAREA (if this KFPR26263-E message was output), see the HiRDB Staticizer Option Version 7 Description and User's Guide.

KFPR26264-I L+S

Backup generation differ from recovery generation. backup generation=aa recovery generation=bb

The generation number specified when data was backed up differs from the generation number specified when the database was recovered. Use the aa generation backup to recover the bb generation.

aa: The generation number specified in the -q option during backup

bb: The generation number specified in the -q option during recovery

S: Continues processing.

KFPR26265-I L+S

File sequence error information, RDAREA name = aa....aa server name = bb....bb information = (cc....cc,dd....dd,ee....ee,ff....ff),(gg....gg,hh....hh,ii....ii,jj....jj)

This message outputs the detail information relating to the KFPR16301-E message (reason=File-missing).

aa....aa: RDAREA name

bb....bb: Server name

cc....cc: Output time of the previous log record^*

dd....dd: Run ID^* of the previous log record output

ee....ee: Generation number^* of the system log output by the previous log record

ff....ff: System internal information

gg....gg: Log report output time

hh....hh: Run ID when the log record is output

ii....ii: Generation number of the system log output by the log record

jj....jj: System internal information

^* If the unload log file is not missing, **....** is output.

S: Terminates the recovery process of all RDAREAs on the applicable server. If a server with other RDAREAs that can be recovered is found, continues the recovery process of that server.

Action

cc....cc	Administrator's action
time	The unload log file including log records output from cc....cc to gg....gg is missing. Specify all unload log files, including the log records output at the applicable time, and then re-execute.
....	Take one of the following actions: An unload log file that must be specified first on each server may be missing. Refer to time gg....gg, specify the missing unload log file(s), and then re-execute. If all unload log files close to time gg....gg are specified, check if the backup file was obtained near time gg....gg. If the backup file was not obtained near the time gg....gg, specify a backup file obtained near time gg....gg, and then re-execute.

cc....cc

Administrator's action

time

The unload log file including log records output from cc....cc to gg....gg is missing. Specify all unload log files, including the log records output at the applicable time, and then re-execute.

**....**

Take one of the following actions:
An unload log file that must be specified first on each server may be missing. Refer to time gg....gg, specify the missing unload log file(s), and then re-execute.
If all unload log files close to time gg....gg are specified, check if the backup file was obtained near time gg....gg. If the backup file was not obtained near the time gg....gg, specify a backup file obtained near time gg....gg, and then re-execute.

KFPR26266-E L+S

Unable to use the "-k n" option because the JP1/VERITAS NetBackup Agent for HiRDB license not found

The -k n option cannot be specified because the license required to use the JP1/VERITAS NetBackup linkage facility is missing.

S: Terminates processing.

Action: Obtain and configure the license required to use the JP1/VERITAS NetBackup linkage facility.

KFPR26267-E L+S

Dynamic load error occurred, shared library=aa....aa, host=bb....bb

Dynamic loading of common library aa....aa on host bb....bb failed.

aa....aa: Full path name of the shared library (in UNIX, the file path name of the shared library)

bb....bb: Host name

S: Terminates processing.

Action: Check if a NetBackup client is installed. If a copy is installed, see the KFPR26003-E message just output to eliminate the cause of the error, and then re-execute.

KFPR26268-E L+S

NetBackup object not found, policy=aa....aa, from=bb....bb, to=cc....cc

A backup of policy name aa....aa obtained in bb....bb to cc....cc cannot be found.

aa....aa: Policy name

bb....bb: The backup search condition start date of the -U option (YYYY/MM/DD HH:MM:SS). ****/**/** **:**:** is output if no start date is specified.

cc....cc: The backup search condition end date of the -U option (YYYY/MM/DD HH:MM:SS). ****/**/** **:**:** is output if no end date is specified.

S: Terminates processing.

Action: Check whether there is a backup file of the policy in the specified period, reevaluate the policy name and specification period, and then re-execute. If the backup search condition start date is ****/**/** **:**:**, the backup search condition start date and time become the policy creation date and time. If the backup search condition end date and time are ****/**/** **:**:**, the backup search condition start date and time are the current new date and time.

KFPR26269-E L+S

NetBackup API error occurred, return code=aa....aa(bbbb), func=cc....cc, message=dd....dd

A problem occurred in the application programming interface of NetBackup.

aa....aa: Name of the application programming interface return code for NetBackup

bbbb: Application programming interface return code for NetBackup (hexadecimal)

cc....cc: Application programming interface name for NetBackup

dd....dd: The message obtained after the application programming interface error return for NetBackup (displays the first 100 characters if the message length exceeds 100 characters)

S: Terminates processing.

Action

Return code (bbbb)	Return code name (aa....aa)	Meaning	Action
0x03	SYSTEM_ERROR	NetBackup internal error	Check the error cause at the NetBackup management console, take appropriate action, and then re-execute.
0x0D	FEATURE_NOT_LICENSED	No license was found or the license was invalid	Obtain a license.
0x4B	VERSION_NOT_SUPPORTED	NetBackup version is not supported	Check if the NetBackup version is correct.
0x4D	ACCESS_FAILURE	Cannot access the object	Check if the NetBackup master server or NetBackup media server stopped. If the server did not stop, contact a customer engineer^*.
Other			Contact a customer engineer^*.

: Does not apply.

^* Obtain the following data before contacting a customer engineer:

The system log file of the host with a single server or system manager, the host with the -b option specified, or the host with the target RDAREA when executing the utility
Files in the %PDDIR%\spool directory on the host with a single server or system manager, the host with the -b option specified, or the host with the target RDAREA when executing the utility
Error information from the NetBackup management console
Messages output to standard output or standard error
The process results output file when executing the utility

KFPR26270-W L+S

Log information, specified log Run ID=aa....aa Gen No=bb....bb, log Run ID=cc....cc Gen No=dd....dd in RDAREA name="ee....ee"

Unload log files required for the recovery of the database are not specified in the -l or -d option of the pdrstr command. The log information stored in the RDAREA and the log information in the unload log file specified in the -l or -d option of the pdrstr command is displayed.

Note:

If the backup was made under one of the following circumstances, this warning message is output even if all unload log files needed for database recovery have been specified; in this case, this warning message can be ignored:

Backup was made after HiRDB terminated normally.
This warning message is also output when all unload log files that store the system logs used in the next and subsequent normal starts are specified in the -l or -d option.
System log files were swapped after the pdclose command had been entered, and then the backup was made.
This warning message is also output when all unload log files that store the system logs used after swapping of system log files are specified in the -l or -d option.
System log files were swapped after reference-possible backup-hold (update WAIT mode) or updatable backup-hold (WAIT mode), and then the backup was made.
This warning message is also output when all unload log files that store the system logs used after swapping of system log files are specified in the -l option.

aa....aa:: ID of the log information stored in the oldest unload log file¹ in the directory specified in the -l option or specified in the -d option (log server run ID of the system log file)

bb....bb:: Log information stored in the oldest unload log file¹ in the directory specified in the -l option or specified in the -d option (generation number of the system log file)

cc....cc:: ID of the log information stored in the RDAREA (log server run ID of the system log file)²

dd....dd:: Log information stored in the RDAREA (generation number of the system log file)²

ee....ee: RDAREA name

¹ The first unload log file at each server is used.

Example:: -l bes1_unlog01, bes1_unlog02, bes2_unlog01, bes2_unlog02; When the -l option is specified as described previously, the log information of unload log files bes1_unlog01 (unload log file of back-end server 1) and bes2_unlog01 (unload log file of back-end server 2) is displayed.

² Log information is stored in an RDAREA in the following cases:

When an RDAREA is on backup-hold
When an RDAREA is closed
When HiRDB has terminated normally

Action: When specifying the -l option of the pdrstr command, specify all unload log files that are required for the recovery of the database. Alternatively, when specifying the -d option of the pdrstr command, either specify all unload log files that are required for the specified directory or increase the number of directories to be specified. Refer to cc....cc and dd....dd to determine which unload log files are required.

KFPR26271-I L+S

NetBackup information, policy=aa....aa, date=bb....bb, time=cc....cc

Backup of policy name aa....aa obtained by date bb....bb and time cc....cc was restored.

aa....aa: Policy name

bb....bb: Date (YYYY/MM/DD)

cc....cc: Time (HH:MM:SS)

S: Continues processing.

KFPR26272-W S+L

No unload log file in specified directory, directory name = aa....aa

There is no unload log file in the specified directory.

aa....aa: Directory name (if it exceeds 100 characters, the last 100 characters are output)

S: Continues processing.

Action: Check the directory name aa....aa. If the directory name is invalid, revise the directory name and re-execute.

KFPR26273-E S+L

Error occurred directory analysis, directory name = aa....aa

An error occurred during analysis of directory aa....aa.

aa....aa: Directory name (if it exceeds 100 characters, the last 100 characters are output)

S: Terminates processing.

Action: On the basis of the KFPR26203-E message output before or after, remove the cause of the error and re-execute.

KFPR26274-E E+L

Too many parameter exists at -a option in command line.

Too many parameters are specified in the command line options.

a: Option name

Action

The option name and action are listed below:

Option name	Action
d	The total number of specified directory names exceeds the maximum number of 128 that can be specified. Revise the specified number of directories to within 128, move the unload log files in the specified directories, then re-execute.

KFPR26275-I S+L

Pdbkupls started.

The pdbkupls command has been started.

S: Continues processing.

KFPR26276-I S+L

Pdbkupls terminated, return code=aa

The pdbkupls command terminated with return code aa.

aa: Command return codes: 0: Normal termination; 12: Error termination

S: Continues processing.

Action: If the return code shows an error termination (12), refer to the error messages output before and after this message to the event log (in UNIX, syslogfile). See the action listed for the error message, remove the cause of the error, then re-execute.

KFPR26277-E S+L

Required backup files not specified.

The backup files required to display the information are insufficient.

S: Terminates processing.

Action: Specify all required backup files and re-execute.

KFPR26278-I L+S

aa....aaGbyte processing.

aa....aa Gigabytes are being read from the backup files.

aa....aa: Size of data read so far

S: Continues processing.

KFPR26279-I L+S

aa....aaGbyte reading completed.

Reading of the backup file has completed approximately aa....aa gigabytes.

aa....aa: Size of the backup file (gigabytes): Rounded up to the nearest 0.01 gigabyte (a backup file of less than 0.01 gigabytes is displayed as 0.01 gigabyte).

S: Continues processing.

KFPR26280-E S+L

Specified backup file invalid. filename=aa....aa, code=bb....bb

The specified backup file is invalid.

aa....aa: Name of the invalid backup file (if it exceeds 100 characters, the last 100 characters of the backup file name are output).

bb....bb: Error cause: diff: Backup file prepared by the differential backup facility; other: Backup file prepared by other than pdcopy; error: Backup file prepared by pdcopy, which terminated with an error (return code 12)

S: Terminates processing.

Action: Specify the correct backup file name and re-execute.

KFPR26309-I S+L

Backup file=aa....aa

Restores by using backup file aa....aa.

aa....aa: RDAREA name

S: Continues processing.

2.13 KFPR messages