Hitachi

JP1 Version 12 JP1/Automatic Job Management System 3 Messages


KFPO00107-E

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

An error occurred in a system call issued within the embedded database system.

aa....aa: System call name

bb....bb: Name of the module or function making the system call

cc....cc: Errno value when the system call error occurred

dd....dd: Details on the system call error

(S)

Does one of the following according to the severity of the error:

  • Cancels processing, and terminates the process abnormally.

  • Cancels processing, and returns control to the caller of the running service.

  • Continues processing.

(O)

Determine the cause of the error with the documentation for your OS based on the system call name and the errno value. If a dump has been output to the core file, save the dump and contact the embedded database system administrator.

Action

After determining the cause of the error with the documentation for your OS based on the system call name and the errno value, correct the UAP, change the system definition, or re-create the OS.

The following explains the major corrective actions.

System call name

Calling module

errno

Error details

Action

open

Any

23

The number of open files exceeded the maximum for the system.

If the embedded database server runs on Windows, the work file for shared memory cannot be allocated due to insufficient space on the installation drive.

Increase the value specified in the nfile kernel parameter for the OS. In addition, stop any unnecessary processes and close any unnecessary windows.

If the embedded database server runs on Windows, allocate free space greater than the shared memory size on the installation drive.

24

There are too many open files in the relevant process.

If the embedded database server runs on Windows, the work file for shared memory cannot be allocated due to insufficient space in the installation drive.

If the error occurs during execution of a command that uses the embedded database, increase the value of the maxfiles kernel parameter for the OS.

If the embedded database server runs on Windows, allocate free space greater than the shared memory size on the installation drive.

logblib.c

999

In Windows, the work file in the embedded database may have been corrupted.

Make sure that the embedded database has stopped, and then delete all the following files for recovery.

Note, however, that files after number 4 may not exist.

  1. embedded-database-practical-directory\uxpldir\spool\system\filmng.dat

  2. embedded-database-practical-directory\uxpldir\spool\system\flg.dat

  3. embedded-database-practical-directory\uxpldir\spool\system\shmmng.dat

  4. embedded-database-practical-directory\spool\~pdatmode

  5. embedded-database-practical-directory\spool\~pdipcid

  6. embedded-database-practical-directory\spool\oslmqid

  7. embedded-database-practical-directory\spool\oslsmid

  8. embedded-database-practical-directory\spool\pdprcsts

  9. embedded-database-practical-directory\spool\scdqid1

  10. embedded-database-practical-directory\spool\scdqid2

  11. embedded-database-practical-directory\tmp\pdommenv

  12. All files under embedded-database-practical-directory\uxpldir\spool\shm

  13. embedded-database-practical-directory\uxpldir\spool\system\semmng.dat

  14. embedded-database-practical-directory\uxpldir\spool\system\msgmng.dat

When you start the embedded database after deleting the above files, make sure that no other applications such as Explorer are accessing embedded-database-practical-directory\tmp.

write

uss_dump

uss_dump_h

uss_dump_d

usm_dump

usm_rmdump

usm_svdump

12

The file system containing the embedded database practical directory is full.

Delete the trouble information from under the embedded database practical directory.

To delete the trouble information, use the OS rm command (del command in Windows).

shmat

ommalloc

ommrmalc

22

The shared memory for the embedded database was not found (the shared memory for the embedded database may have been deleted).

Before the OS started, a command that uses the embedded database might have been entered (includes cases in which the command is specified in the /etc/localrc file or any other OS environment file).

In Windows, a work file under the embedded database practical directory might have been deleted while the embedded database was running.

If the shared memory for the embedded database has been deleted, contact system administrator.

If a command for using the embedded database was executed before the OS was started, wait until the OS was started, and then re-execute the command.

If a command that uses the embedded database is specified in the OS environment file /etc/localrc, an error occurred because the command was executed before the OS had started. To prevent such an error, do not specify a command that uses the embedded database in the /etc/localrc file.

In Windows, if the embedded database has not terminated abnormally, forcibly terminate it and then restart the embedded database service.

If this message appears due to execution of a command that can be executed whether or not the embedded database is running, do not treat this message as an error. Since the command is operating normally, check the execution result of the command.

ommrmalc

24

The number of units of shared memory connected to the calling process exceeded the maximum for the system.

Specify an appropriate value for one of the following operating parameters:

  • In HP-UX: shmseg

  • In Solaris: shminfo_shmseg

  • In Linux: SHMSEG

In AIX 5L, set ON for the EXTSHM environment variable.

shmctl

ommfixed

1

The user who executed the command is not a superuser.

The owner of the files under the embedded-database-practical-directory/bin directory might have been changed illegally.

Check the owner of the executable file (the pdommfixed file under embedded-database-practical-directory/bin) and permissions for the owner.

If the owner is not root or does not have s permission (that is, the file mode is not -r-sr-xr-x), the owner of the files under embedded-database-practical-directory/bin was changed after the pdsetup command was executed. A superuser must re-create the embedded database environment. After the environment is created, restart the embedded database.

semget

osysemg

12

In Windows, no more semaphore identifiers are available.

Estimate the number of semaphore identifiers required for the embedded database, and then specify a larger value for the PDUXPLSEMMAX system environment variable. After specifying the setting, terminate the embedded database and then restart the service.

pdi_osm_get

999

For details about other major errno values, see B. Return Codes of System Calls.