2.11 KFPO messages


KFPO00100-E E+L

Error occured in system call aa....aa, errno=bbb, function name=cc....cc

A system call that was issued from within a HiRDB system function resulted in an error.
aa....aa: Name of system call
bbb: Return code from the system call (errno)
cc....cc: Name of function resulting in the error
S: Continues processing if processing can be continued. If not, interrupts processing.
O: Contact the HiRDB administrator.
Action
Take one of the following actions:
  • If an error message or warning message was output before or after this message, follow the action indicated in that message.
  • See 4.3 System call return codes, and take action.
If none of these actions is effective, contact the customer support center.

KFPO00103-E E

Shared memory pool damaged. location=0xaaaaaaaa (0xbbbbbbbb, 0xcccccccc)

A segment was damaged; the damaged segment is located at address 0xaaaaaaaa from the beginning of the shared memory pool.
aaaaaaaa: Location of the damaged segment relative to the beginning of the shared memory pool
bbbbbbbb: Contents of the first 8 bytes of the damaged segment
cccccccc: Contents of the last 8 bytes of the damaged segment (if the contents cannot be displayed, ******** is displayed)
S: Terminates abnormally.
O: Record the location and segment contents displayed in this message and contact the HiRDB administrator. In UNIX, if a core file dump is output, save it and contact the customer support center.
Action
Check the cause of the damage to the shared memory pool.

KFPO00104-E E

Shared memory subpool damaged. location=0xaaaaaaaa (0xbbbbbbbb, 0xcccccccc)

A memory block was damaged; the damaged memory block is located at address 0xaaaaaaaa from the beginning of the shared memory subpool.
aaaaaaaa: Location of the damaged memory block relative to the beginning of the shared memory subpool
bbbbbbbb: Contents of the first 8 bytes of the damaged memory block
cccccccc: Contents of the last 8 bytes of the damaged memory block (if the contents cannot be displayed, ******** is displayed)
S: Terminates abnormally.
O: Record the location and memory block contents displayed in this message and contact the HiRDB administrator. In UNIX, if a core file dump is output, save it and contact the customer support center.
Action
Check the cause of the damage to the shared memory subpool.

KFPO00105-E E

Server aa....aa (process ID=bb....bb) killed by code=cc....cc

The HiRDB server process terminated due to an error.
aa....aa: Server name for the abnormally terminating process
(if the server name cannot be determined, ******** is displayed)
bb....bb: Process ID of the abnormally terminating process
cc....cc: ABORT code (for details on the ABORT code, see 3. ABORT Codes)
S: If the server process terminated during the processing of system services, HiRDB (in the case of HiRDB/Parallel Server, the unit) terminates abnormally. If the server process was terminated during UAP processing, post-processing is executed. Restart the server if necessary.
O: Save files in the following directories and contact the HiRDB administrator:
  • %PDDIR%\spool
  • %PDDIR%\tmp\home
Action
Take action according to the output abort code.

KFPO00106-E E

{"Malloc(aa....aa)"| "Realloc(bb....bb,aa....aa)"| "Calloc(cc....cc, aa....aa)"}failed,process ID=dd....dd, type=0xee....ee

Process private area cannot be allocated due to an error in the standard C function malloc, realloc, or calloc.
aa....aa: Size specified in the malloc, realloc, or calloc function issued internally in the HiRDB system
bb....bb: Area address specified in the realloc function issued internally in the HiRDB system
cc....cc: Number of array elements specified in the calloc function issued internally in the HiRDB system
dd....dd: ID of the process that issued the malloc, realloc, or calloc function
ee....ee: Type code (identification information set by each component of the HiRDB system)
S: If it is possible to continue system operation, resumes processing. Otherwise, terminates the HiRDB system abnormally.
O: Record this message and contact the HiRDB administrator. In UNIX, if a core file dump is output, save it and contact the HiRDB administrator.
Action
Take one of the following actions:
  • If system processing is being resumed, terminate any unneeded processes.
  • Reevaluate the value of the pd_max_users operand.
  • Add a system swap area.
  • Add the main storage device.

KFPO00107-E E+L

"aa....aa(bb....bb)" failed, errno=cc: dd....dd

An error occurred in a system call that was issued internally in the HiRDB system.
aa....aa: Name of system call
bb....bb: Name of module or function that issued the system call
cc....cc: Value of errno set by the system call error
dd....dd: Nature of system call error
S: Takes one of the following actions according to the severity of the error:
  • Cancels processing and terminates the process abnormally.
  • Cancels processing and returns control to the executing process that was the source of the call.
  • Resumes processing.
O: Refer to the applicable OS manual in order to check the cause of the error on the basis of the system call name and the value of errno. In UNIX, if a core file dump is output, save it and contact the HiRDB administrator.
Action
Refer to the applicable OS manual in order to check the cause of the error on the basis of the system call name and the value of errno, and correct the UAP, change the system definitions, or regenerate the operating system.
Following are the principal methods by which this problem can be resolved:
System call nameCall moduleerrnoError descriptionAction
openArbitrary23In UNIX, the number of open files exceeds the maximum value defined for the system.
In Windows, a work file for shared memory could not be allocated due to a capacity shortage in installed drives.
In UNIX, increase the value specified for nfile in the operating system kernel parameters. Also, close any extraneous processes and windows.
In Windows, allocate free space on installed drives greater than or equal to the shared memory size.
24In UNIX, too many files are opened by the indicated process.
In Windows, a work file for shared memory could not be allocated due to a capacity shortage in installed drives.
In UNIX, if the error occurred during execution of a HiRDB operating command or utility, increase the value specified for maxfiles in the operating system kernel parameters.
In Windows, allocate free space on installed drives greater than or equal to the shared memory size.
47In AIX an attempt was made to open a write-protected volume in write-enabled mode.If Real Time SAN replication is used, execute the pdrisechk command to verify that the pair logical volume group is configured correctly.
openlogblib.c999In the case of Windows, HiRDB work file may have been damaged.First, ensure that HiRDB has stopped, then delete all the files listed below and recover. Note that the files from number 4 may not always exist.
  1. %PDDIR%\uxpldir\spool\system\filmng.dat
  2. %PDDIR%\uxpldir\spool\system\flg.dat
  3. %PDDIR%\uxpldir\spool\system\shmmng.dat
  4. %PDDIR%\spool\...pdatmode
  5. %PDDIR%\spool\...pdipcid
  6. %PDDIR%\spool\oslmqid
  7. %PDDIR%\spool\oslsmid
  8. %PDDIR%\spool\pdprcsts
  9. %PDDIR%\spool\scdqid1
  10. %PDDIR%\spool\scdqid2
  11. %PDDIR%\tmp\pdommenv
  12. All files under %PDDIR%\uxpldir\spool\shm
  13. %PDDIR%\uxpldir\spool\system\semmng.dat
  14. %PDDIR%\uxpldir\spool\system\msgmng.dat
When starting HiRDB after deleting all these files, check that no other applications, such as Explorer, are accessing %PDDIR%\tmp.
writeuss_dump
uss_dump_h
uss_dump_d
usm_dump
usm_rmdump
usm_svdump
12The file system containing the HiRDB operation directory is full.Delete troubleshooting information under the HiRDB directory.
In UNIX, to delete troubleshooting information, use either the OS rm command or the HiRDB pdcspool command.
In Windows, to delete troubleshooting information, use either the OS del command or the HiRDB pdcspool command.
Arbitrary47In AIX, an attempt was made to write to a write-protected volume.If Real Time SAN replication is used, execute the pdrisechk command to verify that the pair logical volume group is configured correctly.
lio_listioiosplwrt5In AIX, could not write to the volume.Take action according to the errno displayed in the KFPO00107-E message (system call name: write, call module name: iosplwrt) that is output immediately after this message.
shmatomminit
ommalloc
ommrmalc
12Consider one of the following:
  1. The number of available resources is insufficient. This includes the case in which no contiguous free area can be allocated in the process space to which shared memory is to be attached.
  2. In Windows, an error occured while referencing the Windows registry.
  3. In Windows, the HiRDB service is not started when shared memory is allocated to the paging file.
Take the following corrective action according to the cause of the error:
  1. For Windows, specify the number of required resources (size of required shared memory) in the system environment variable PDUXPLSHMMAX. For details about how to compute the size of the shared memory to be used, see the Determining Environment Variables Related to the Number of Resources section in the HiRDB Version 9 Installation and Design Guide.
    Note that the default value of the system environment variable PDUXPLSHMMAX is 4096. If usable memory cannot be made available, change the HiRDB system definition (for example, by reducing the number of global buffers) to reduce the shared memory requirements.
  2. Check the value specified for the pdntenv command's -shmfile operand. If it is other than regular, page, or blank, the Windows registry might be corrupt. If that is the case, contact the customer support center.
  3. If the shared memory is allocated to the paging file, confirm that the HiRDB service is started. If the HiRDB service is stopped, start the service.
ommalloc
ommrmalc
22No HiRDB shared memory (HiRDB shared memory might have been deleted).
In UNIX, it is possible that a HiRDB command was entered before the OS was fully started (this includes the case in which a HiRDB command was coded in an OS environment file such as /etc/localrc).
In the case of Windows, the work file under %PDDIR% may have been deleted while HiRDB was active.
Take the following actions:
In UNIX:
  • If a HiRDB command was executed before the OS was started, re-execute the command after the activation of the OS is completed.
  • If a HiRDB command was coded in the OS environment file /etc/localrc, the command is executed before the OS is started, which results in an error. Therefore, a HiRDB command should not be coded in the /etc/localrc file.
In Windows:
  • If a HiRDB command was executed before the OS was fully started, wait for the OS to finish starting, and then re-execute the command.
  • If HiRDB did not shut down, terminate it forcibly, and then restart HiRDB.
If the above actions do not resolve the problem, contact the customer support center, because the HiRDB shared memory might have been deleted. If a command that is executable regardless of the operation of HiRDB was executed, you can safely ignore this message. In this case, check the execution result of that command to verify that it is working properly.
ommrmalc24The number of common memory devices connected to the invocation source process exceeded the system limit.Specify an appropriate value in the relevant system parameter shown below. For details about how to perform system estimates, see the HiRDB Version 9 Installation and Design Guide.
  • HP-UX: shmseg
  • Solaris: shminfo_shmseg
  • Linux: SHMSEG
For AIX set ON in the EXTSHM environment variable.
shmctlommfixed1The user executing this command is not a super-user. It is possible that the file was improperly modified by the owner of a file under $PDDIR/bin.Check the owner of the execute form file (pdommfixed under $PDDIR/bin) and the owner's privileges. If the owner is not root or his or her execution privilege is not s (with file mode -r-sr-xr-x), the owner of a file under $PDDIR/bin was changed after the pdsetup command had been executed. As a superuser, execute the pdsetup -d command, reply y to the message, and then re-create the HiRDB execution environment by using the pdsetup command. After that, restart HiRDB.
closeArbitrary47In AIX, an attempt was made to write to a write-protected volume.If Real Time SAN replication is used, execute the pdrisechk command to verify that the pair logical volume group is configured correctly.
semgetosysemg12In the case of Windows, there is no room for semaphore identifiers.Estimate the number of semaphore identifiers required by HiRDB and set a value greater than the value in the PDUXPLSEMMAX system environment variable. After setting, terminate HiRDB and restart the service.
For the procedure for estimating the number of semaphore identifiers, see the HiRDB Version 9 Installation and Design Guide.
pdi_osm_get999
See 4.3 System call return codes, for other representative errnos.

KFPO00109-E L

Shared memory pool(shared memory ID aa....aa, server type=bb....bb) for HiRDB server damaged. location=0xcccccccc(0xdddddddd, 0xeeeeeeee)

A shared memory pool for user server (shared memory ID = aa....aa, server identifier = bb....bb) was damaged.
aa....aa: Identifier of the damaged shared memory pool for user server
bb....bb: Server identifier (if this information cannot be displayed, ******** is displayed)
cccccccc: Location of the damaged segment relative to the beginning of the shared memory pool
dddddddd: Contents of the first 8 bytes of the damaged segment
eeeeeeee: Contents of the last 8 bytes of the damaged segment (if the contents cannot be displayed, ******** is displayed)
S: Terminates abnormally.
O: Record the location and segment contents displayed in this message and contact the HiRDB administrator. In UNIX, if a core file dump is output, save it and contact the HiRDB administrator.
Action
Contact the customer support center. Correct the program, modify the system definitions, or regenerate the operating system.

KFPO00111-E L

Insufficient memory on aa....aa, size=bb....bb

A memory shortage occurred.
aa....aa: Name of defined variable
bb....bb: Size (in bytes) That was to be allocated
S: Terminates processing.
O: Contact the HiRDB administrator and check the cause of the error.
Action
Contact the customer support center.

KFPO00112-E L

Getarea request error, size=aa....aa

A work area shortage occurred.
aa....aa: Size (in bytes) That was to be allocated
S: Terminates abnormally.
O: Contact the HiRDB administrator and check the cause of the error.
Action
Contact the customer support center.

KFPO00113-E L

"shmget(manager)" failed. size=aa....aa, errno=bbb

An error occurred with the shmget system call issued to collect the unit controller shared memory.
aa....aa: Size (in bytes) of shared memory that was to be allocated
bbb: errno value of the shmget system call
S: Terminates abnormally.
O: Take action appropriate to the errno value of the shmget system call:

KFPO00114-E L

"shmget(aa....aa)" failed, size=bb....bb, errno=ccc

An error occurred in the shmget system call while allocating the shared memory for server aa....aa.
aa....aa: Server identifier
bb....bb: Size (in bytes) of shared memory that was to be allocated
ccc: errno value of the shmget system call
S: Terminates processing.
O: Take action appropriate to the errno value of the shmget system call:
errnoCauseAdministrator's action
12Specified size of shared memory is not available in the operating system.Terminate the other control statements using the shared memory on the same machine and restart the server where the error occurred. Or, shut down the HiRDB system and increase the real memory in the operating system.
22The shared memory size exceeded the maximum value for the operating system.Shut down the HiRDB system and reduce the number of servers defined in the same unit. Or, increase the maximum segment size of the shared memory in the operating system, and re-create the kernel.
28The shared memory identifiers count exceeded the maximum value for the operating system.Terminate the other control statements using the shared memory on the same machine and restart the server where the error occurred. Or, shut down the HiRDB system, either reduce the number of shared memory sectors in the operating system or increase the maximum number of shared memory identifiers, then re-create the kernel.
Other--Contact the customer support center.
--: Not applicable

KFPO00115-W E+L

Server aa....aa (process ID=bb....bb) killed by code=cc....cc

A process was terminated forcibly due to an error. This message is output if a process is terminated forcibly when a transaction is canceled.
aa....aa: Name of the server where the process terminated abnormally
If the server name cannot be determined, ******** is displayed.
bb....bb: Process ID of the process that terminated abnormally
cc....cc: ABORT code
For ABORT codes, see 3. ABORT Codes.
S: Re-activates the user server process as necessary. In this case, HiRDB (in the case of a HiRDB/parallel server, a unit) does not terminate abnormally.
O: Error information is output if put is specified in the pd_cancel_dump operand. If it is not needed, the error information can be deleted.