Job Management Partner 1/Automatic Job Management System 3 Messages 2

1.3 Messages beginning with KFP (Messages about an embedded database)

KFPA11561-E
Specified authorization identifier aa....aa has no connect privilege (A)

The specified authorization identifier aa....aa has no CONNECT privilege.

aa....aa: Authorization identifier that has no CONNECT privilege

(S)

Terminates processing.

Action

Check the value of the RDBAUTHID environment setting parameter.

KFPA11720-E
Error occurred in HiRDB/client, inf1=aa....aa, inf2=bbbb (L+A)

An internal contradiction occurred in the client library for the embedded database system.

The probable causes are:

The host specified in the ajsembdbstart command and the host specified in PDHOST cannot communicate with the client system over the network. Alternatively, the communication load is heavy.

aa....aa: Name of the source file in which the error was detected

bbbb: Location where the error was detected (line number)

(S)

Terminates processing.

Action

Back up the error log file to which the error was output, and then contact the system administrator.

KFPA11723-E
Communication error occurred, reason=aa....aa (L+A)

An error occurred during communication with the embedded database system or embedded database server. Alternatively, the embedded database system or embedded database server has gone down.

aa....aa: Character string indicating the details of the error

CLIENT MEMORY: A memory shortage occurred in the client library.

FES (SDS) CLOSE: The server is being terminated.

FES (SDS) NOT UP: The server is not running or is being started.

HiRDB BUSY: The embedded database (server) cannot be connected because it is busy.

HiRDB DATA ERROR: Communication data from the embedded database system or embedded database server is invalid.

HiRDB INITIALIZE: The embedded database system or embedded database server is being initialized.

HiRDB NOT UP: The embedded database system or embedded database server is not running. Alternatively, Listen queues on the embedded database server are insufficient.

HiRDB SYSTEM ERROR: A system error was detected in the HiRDB system or HiRDB server.

HiRDB MEMORY: A memory shortage occurred in the embedded database system or on the embedded database server.

INIT ERROR: An error occurred during initialization for communication.

INVALID SERVER TYPE: The server type of the embedded database (server) differs from PDSRVTYPE (client environment definition).

NETWORK: A network failure occurred. Alternatively, the connection was released due to abnormal termination of the embedded database server.

(S)

Terminates processing.

(P)

When aa....aa is HiRDB BUSY:

Wait a while, and then retry. If this message reappears, contact the embedded database system administrator.

When aa....aa is not HiRDB BUSY:

Report the details of the error to the embedded database system administrator, and then correct the error and retry.

Action

Determine the cause of the error from the error log file output by the embedded database client, correct the cause of the error, and then retry.

If this message (aa....aa is HiRDB NOT UP) still appears during connection even after the embedded database has started, recheck the JP1/AJS3 environment setting parameters. In addition, use a syslog (or Windows event log in Windows) to check for errors on the embedded database server.

If the values of JP1/AJS3 environment setting parameters are correct and the message KFPZ02444-E (func=connect and errno indicating ETIMEDOUT or ECONNREFUSED) is output to the error log file, it is possible that too many requests have been made to the embedded database server. In this case, wait a while and then retry. Alternatively, increase the value specified for the Listen queues.

Note that when this message appears, connection with the embedded database server has been released. Therefore, you must retry starting from the CONNECT statement.

KFPA11724-E
Environment definition error, variable=aa....aa, reason=bb....bb, identifier="cc....cc" (L+A)

The specification of the environment variable contains an error.

aa....aa: Environment variable name containing the error

bb....bb: Cause of the error

INVALID CHAR: A character string that cannot be specified was found.

NET ENVIRONMENT: The specified contents do not match the network environment.

NO VALUE: No value is specified.

OUT OF RANGE: The specified value is outside the specifiable range.

NOT ENVIRONMENT GROUP: The specified environment variable group was not found in the registry.

INVALID IDENTIFIER: The identifier is invalid.

cc....cc: Invalid identifier (If the identifier exceeds 30 bytes, the first 30 bytes are displayed.)

This information is displayed only when the cause of the error is INVALID IDENTIFIER.

(S)

Terminates processing.

(P)

Specify the environment variable correctly, and then retry.

KFPA11732-E
Time over, no response from HiRDB (L+A)

The embedded database server has stopped. Alternatively, processing for the embedded database server required more time than the timer monitoring period. As a result, a query cannot be sent to the embedded database server.

(S)

Terminates processing.

(P)

If the embedded database server stopped, make sure that it has started again, and then retry.

If the embedded database server has not stopped, increase the timer monitoring period specified in the PDCWAITTIME environment variable, and then re-execute the UAP. Note that when this message appears, connection with the embedded database server has been released. Therefore, you must re-execute the UAP from the CONNECT statement.

KFPA11756-E
No available pages in RDAREA, RDAREA=aa....aa (A)

There are no available pages in the RDAREA.

aa....aa: Name of the RDAREA that has insufficient free space

(S)

Invalidates the transaction.

Action

Take one of the following actions, and then re-execute the transaction:

Expand the RDAREA.
Use the ajsembdbaddarea command to expand the size of the RDAREA that has insufficient free space.

Reorganize the table.
Use the ajsembdbrorg command to reorganize the table stored in the RDAREA.

Reclaim free pages.
Execute the ajsembdbstatus command with the -db option to analyze the status of the RDAREA. If required, execute the ajsembdbreclaim command for the index.

KFPA11770-I
aaaa [bb....bb cc....cc] currently in use, resource id=dd....dd (A)

An exclusive-wait timeout occurred.

aaaa: Maintenance information

bb....bb: Maintenance information

cc....cc: Maintenance information

dd....dd: Maintenance information

(S)

Terminates processing.

(O)

Take corrective action according to the message displayed before or after this message.

KFPA11912-E
Insufficient memory for DB exclusive contr (A)

The work area for exclusive control was insufficient.

(S)

Terminates processing, or cancels command processing.

(P)

If the error occurred during operation of JP1/AJS3:

Check the current resource lock status. Wait until the load decreases, and then retry the operation.

If the error occurred during execution of the ajsembdbrorg command:

Check the current resource lock status. Wait until the load decreases, and then retry the operation.

If the error occurs even when the load is light, the locked resource management table required for the utility to process the appropriate table cannot be allocated.

Action

If the resources for locking tables are insufficient, increase the value specified for the pd_lck_pool_size operand in the system definition of embedded database, and then start the embedded database.

KFPA11928-I
RDAREA aa....aa held pdhold command in proce (L)

The specified RDAREA aa....aa is undergoing block processing.

aa....aa: RDAREA name

(S)

Invalidates the transaction.

Action

Recover the RDAREA and re-execute the transaction.

KFPA11932-E
Number of connect users exceeded max use (A)

The number of connections to the embedded database server exceeded the maximum number of concurrent connections.

(S)

Terminates processing.

(P)

Wait until other jobs or commands terminate, and then re-execute the UAP or the utility.

Action

When this message is output:
If possible, increase the value specified for the pd_max_users operand.

KFPA11990-E
Incompatible character code set,HiRDB=aa....aa,client=bb....bb (A)

The character encodings of the environment variables for the environment linked with the embedded database do not match.

aa....aa: Embedded-database character encoding

bb....bb: Character encoding of the corresponding environment variables for the environment

LANG-C: 7-bit ASCII

Other than the above: Unsupported

(S)

Cancels processing.

(O)

Change LANG environment variable setting for the command execution environment related to the error or the start environment for JP1/AJS3 services related to the error. Make the new value the setup value corresponding to the character encoding of the embedded database specified in the -lc option in the ajsembdbbuild command. After the change, retry the operation.

KFPH00115-I
aa....aa command fail (L+S)

The embedded database command aa....aa cannot be processed.

aa....aa: Command name

(S)

Ignores the entered command and terminates processing.

KFPH00131-E
pdhold command failed due to RDAREA already held, RDAREA=aa.... (L)

The command cannot block the specified RDAREA because it is already blocked due to an error.

aa....aa: RDAREA name

(S)

Ignores the RDAREA processing and executes other processing.

(O)

Correct the error, release the RDAREA from the blocked state, and then re-execute the command.

KFPH00211-I
RDAREA usage aaa%, RDAREA = "bb....bb"cc....cc (L)

The meaning of the message depends on the situation, as shown below:

For users:

Of the segments in the entire RDAREA "bb....bb", the system began to use the segment whose usage is aaa % . The current number of unused segments is cc....cc.

aaa: One of the following is displayed.

Relative position of the used segment in the last file in the RDAREA

Segment usage in the entire RDAREA

Relative position of the used segment in the entire RDAREA

bb....bb: Relevant RDAREA name

cc....cc: Additional information for the segment usage , dd....dd segments unused

(dd....dd: number of remaining segments)

(S)

Continues processing.

Even if a new segment cannot be allocated due to insufficient space in the RDAREA for which this message is displayed, the system continues processing by adding or updating existing segments when these segments have free space.

After the segment displayed in the message has been released due to deletion or reorganization of the table, this message appears again if the same segment is used.

(P)

Contact the embedded database system administrator.

Action

Execute the ajsembdbstatus -db command to check the free space in the database, and then do the following:

Check the additional information about the segment usage output by the ajsembdbstatus -db command or displayed in the message to check the usage of the target RDAREA.

Reorganize the table or expand the RDAREA as required.

KFPH00212-I
Table should be reorganized,RDAREA="aa....aa",AUTHID=bb....bb,TABLE=cc....cc (L)

Reorganization of the table is required.

aa....aa: RDAREA name

bb....bb: Authorization identifier

cc....cc: Table identifier

(S)

Continues processing.

Action

Use the ajsembdbreclaim command to perform maintenance or use the ajsembdbrorg command to reorganize the table. However, you must expand the RDAREA size if either of the following situations occurs:

This message appears frequently for a table in the same RDAREA.

This message appears during or immediately after reorganization of a table.

KFPH22014-E
RDAREA "aa....aa" not found in dictionary server (L)

The required RDAREA "aa....aa" was not found on the dictionary server.

aa....aa: RDAREA name

*masterdirectory*: Master directory

*datadirectory*: Data directory

*datadictionary*: Data dictionary

(S)

Abnormally terminates the embedded database.

Action

If the RDAREA has been corrupted, recover the data and then retry the operation.

KFPH22024-W
Extension completed in RDAREA "aa....aa",FILE "bb....bb",ccccc(dd....dd) segments created (L)

The "bb....bb" file in the "aa....aa" database area was incremented by ccccc segments. The total number of segments is dd....dd.

aa....aa: Database area name

bb....bb: File name (If the file name is 113 or more characters long, only the last 112 characters are output.)

ccccc: Incremented number of segments

dd....dd: Total number of segments

(S)

Continues processing.

Action

Check whether the increase in the amount of job operations (the number of job definitions and the number of executed jobs) is within the intended range.

KFPH22025-E
Error occurred while Extension,RDAREA "aa....aa",FILE "bb....bb",reason code ccccc (L)

An error occurred during automatic incrementing of the "bb....bb" file in the "aa....aa" database area. The reason code is ccccc.

aa....aa: Database area name

bb....bb: File name (If the length is 122 or more characters, only the last 121 characters are output.)

ccccc: Reason code

-1535: Disk capacity shortage or expansion limit

(S)

Continues processing.

Action

Take corrective action as follows:

When the reason code is -1535:

Provisional measures
Delete unnecessary job definitions and unregister the execution of jobnets.
Execute the ajsembdbreclaim command to release free pages and segments.
Execute the ajsembdbrorg command to reorganize the database.

Permanent measure
As required, review (expand) the disk environment or split the scheduler service and embedded database environment.

KFPH23100-E
HiRDB file aa....aa error,errno=bb....bb, HiRDB file name=cc....cc (L)

An error occurred during file access.

aa....aa: File function

close: File closing

creat: File creating

open: File opening

read: File reading

write: Writing to a file

bb....bb: Error code

-1544: Input/output error

cc....cc: File name (If the length is 132 or more characters, only the last 131 characters are output.)

(S)

Terminates processing.

Action

Take corrective action as follows:

When the error code is -1544:

If the database area is blocked because of a fault, recover it from the backup.

KFPH27008-E
aa....aa command failed due to DATA DICTIONARY RDAREA(bb....bb) status invalid, RDAREA = cc....cc (L+S)

The database operation command aa....aa for the specified RDAREA cc....cc cannot be processed because the data dictionary RDAREA bb....bb cannot be referenced.

aa....aa: Command name

bb....bb: Name of the data dictionary RDAREA

cc....cc: RDAREA name (***** appears if the RDAREA name cannot be obtained.)

(S)

Invalidates the RDAREA processing, and continues processing.

(O)

Correct the status of the data dictionary RDAREA, and then re-execute the command.

KFPH27058-E
Unable to use specified command option aa for bb....bb, command=cc....cc, RDAREA name="dd....dd" (L+S)

The aa option cannot be specified for bb....bb in the command cc....cc.

aa: Option name

-u

bb....bb: Cause of the error

shared RDAREA: Shared RDAREA

cc....cc: Command name

pdhold

dd....dd: RDAREA name

(S)

Invalidates the RDAREA "dd....dd" processing, and continues processing.

Action

Delete the aa option and then re-execute the command.

KFPK00002-E
aa....aa: file open failed, file_kind:bb....bb file_name:cc....cc errno=dd....dd (D+E)

The specified file or the file temporarily created by the command cannot be opened.

aa....aa: Command type

Pddbst: ajsembdbstatus

bb....bb: File type

control file: Control statement file

edit work file: Work file

sort data file: Work file for sort

unload log file: Unload log file

DAT file: DAT file

predict csv file: CSV output file

cc....cc: File name

dd....dd: errno returned by the open system call

(S)

When the message is output to the standard error output:

Terminates processing.

When the message is output to the error message dialog box:

Redisplays the window that was displayed immediately before the error occurred.

(O)

Correct the error indicated by the errno value by using the errno.h file and the documentation for your OS, and then re-execute the command.

KFPK00003-E
aa....aa: file close failed, file_kind:bb....bb file_name:cc....cc errno=dd....dd (D+E)

The file cannot be closed.

aa....aa: Command type

Pddbst: ajsembdbstatus

bb....bb: File type

control file: Control statement file

edit work file: Work file

sort data file: Work file for sort

unload log file: Unload log file

predict csv file: CSV output file

cc....cc: File name

dd....dd: errno returned by the close system call

(S)

When the message is output to the standard error output:

Terminates processing.

When the message is output to the error message dialog box:

Redisplays the window that was displayed immediately before the error occurred.

(O)

Correct the error indicated by the errno value dd....dd, and then re-execute the command.

KFPK00004-E
aa....aa: I/O error, cause:bb....bb file_name:cc....cc errno=dd....dd (D+E)

An I/O error occurred.

aa....aa: Command type

Pddbst: ajsembdbstatus

bb....bb: Type of the system call in which the error occurred

LSEEK: lseek system call

READ: read system call

WRITE: write system call

cc....cc: File name

dd....dd: errno returned by the system call

(S)

When the message is output to the standard error output:

Terminates processing.

When the message is output to the error message dialog box:

Redisplays the window that was displayed immediately before the error occurred.

(O)

Correct the error indicated by the errno value dd....dd, and then re-execute the command.

KFPK00005-E
aa....aa: system call error, func=bb....bb, errno=cc....cc (D+E)

An error occurred in the system call (function).

aa....aa: Command type

Pddbst: ajsembdbstatus

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

cc....cc: errno returned by the system call

(S)

When the message is output to the standard error output:

Terminates processing.

When the message is output to the error message dialog box:

Redisplays the window that was displayed immediately before the error occurred.

(O)

Correct the error indicated by the errno value cc....cc, and then re-execute the command.

KFPK00006-E
aa....aa: unrecovable error, func=bb....bb, errno=ccc (D+E)

An unrecoverable error occurred.

aa....aa: Command type

Pddbst: ajsembdbstatus

bb....bb: Type of the system call in which the error occurred

CLOSEDIR: closedir system call

CREATE: create or open system call

DELETE: unlink system call

OPENDIR: opendir system call

READDIR: readdir system call

ccc: errno returned by the system call

(S)

When the message is output to the standard error output:

Terminates processing.

When the message is output to the error message dialog box:

Redisplays the window that was displayed immediately before the error occurred.

(O)

Correct the error indicated by the errno value ccc, and then re-execute the command. If the error number is ***, determine the cause of the error from the preceding error message.

KFPK00013-E
aa....aa: system call error, func=bb....bb, file_name=cc....cc, errno=dd....dd (D+E)

An error occurred in the system call (function) that accesses the file.

aa....aa: Command type

Pddbst: ajsembdbstatus

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

cc....cc: File name

dd....dd: Error number set for errno

(S)

Terminates processing if the message is output to the standard error output. If the message is output to the message dialog box, the system redisplays the window that was displayed immediately before the error occurred.

(O)

Correct the error indicated by the errno value dd....dd, and then re-execute the command.

KFPK00050-E
aa....aa: insufficient memory, size=bb....bb (D+E)

Memory was insufficient.

aa....aa: Command type

Pddbst: ajsembdbstatus

bb....bb: Size of the memory that was to be allocated (unit: bytes)

(S)

When the message is output to the standard error output:

Terminates processing.

When the message is output to the error message dialog box:

Redisplays the window that was displayed immediately before the error occurred.

(O)

Check whether another process is using a large amount of memory.

If another process is using a large amount of memory:

Wait until the process terminates, and then re-execute the command.

If another process is not using a large amount of memory:

Take one of the following actions to increase the amount of free space in memory:

Reduce the number of processes running concurrently.

Increase the swap area.

Add real memory.

KFPK00100-E
aa....aa: interface error, func:bb....bb, return code=cccc (D+E)

An interface error between program functions occurred.

aa....aa: Command type

Pddbst: ajsembdbstatus

bb....bb: Name of the function that returned the invalid code

cccc: Detail code

(S)

When the message is output to the standard error output:

Terminates processing.

When the message is output to the error message dialog box:

Redisplays the window that was displayed immediately before the error occurred.

(O)

Contact the embedded database system administrator.

KFPK00207-E
aaaaaa: unable to assume user id (E)

The value specified for the -a or -ap option is invalid.

aaaaaa: Utility type

Pddbst: ajsembdbstatus

(S)

Terminates processing.

(O)

Specify the correct value for the -a or -ap option, and then re-execute the command.

KFPK10016-E
Insufficient memory in message buffer pool due to concurrent execution of "pddbst" (D+E)

Memory in the message storage buffer pool for the utility server was temporarily insufficient because more than one ajsembdbstatus command with the -db option was executed concurrently. Note that this error might cause the message KFPS00854-W to be output, although no server error has occurred in this case.

(S)

When the message is output to the standard error output:

Terminates processing.

When the message is output to the message dialog box:

Redisplays the window that was displayed immediately before the error occurred.

(O)

Wait until the ajsembdbstatus command currently being executed terminates, and then retry the operation.

KFPK10101-E
Unable to start pddbst (E)

The ajsembdbstatus -db command cannot be started for either of the following reasons:

The maximum number of concurrent utilities for the entire HiRDB system was exceeded.

The HiRDB entity is now terminating.

(S)

Terminates processing.

(O)

Correct the error and restart.

KFPK10107-W
No data
RDAREA="aa....aa" server=bb....bb (E)

The RD area does not contain any tables or indexes, so the status cannot be displayed.

aa....aa: RD area name

bb....bb: Embedded DB name

(S)

When the message is output to the standard error output:

Terminates processing.

(O)

Execute the ajsembdbsetup command to migrate the database to an embedded database, and then re-execute the command.

KFPK10300-I
Pddbst started (E)

Execution of the ajsembdbstatus -db command has started.

(S)

Continues processing.

KFPK10301-I
Pddbst terminated, return code=aa....aa (E)

Execution of the ajsembdbstatus -db command has terminated.

aa....aa: Return code

0: Normal termination

4: Normal termination, but with a warning message output. Alternatively, part of the processing was skipped.

8: Processing was canceled due to an error.

(S)

Terminates processing.

(O)

When the return code is 4 or 8, correct the error by checking the warning message or error message output to the standard error output or message log file.

KFPL00712-I
aa....aa started, table=bb....bb.cc....cc, server=dd....dd,spacelvl=e, generation=ff (L)

Unloading or reloading of the table bb....bb.cc....cc on the server dd....dd has started.

aa....aa: Executed processing

{Reload | Unload}

bb....bb: Authorization identifier

cc....cc: Table identifier

dd....dd: Server name

e: Blank conversion level

(S)

Continues processing.

KFPL00714-I
aa....aa ended, table=bb....bb.cc....cc, server=dd....dd, return code=ee (L)

For the table bb....bb.cc....cc on the server dd....dd, unloading, reloading, releasing of the free page being used, or reading of the page being used has terminated.

aa....aa: Executed processing

{Unload|Reload|Reclaim|Page read}

bb....bb: Authorization identifier

cc....cc: Table identifier

dd....dd: Server name

ee: Return code

(S)

Continues processing if the return code is 0 or 4, or terminates processing if the return code is not 0 or 4.

(O)

If the return code is not 0 or 4, correct the cause of the error according to the error message output to the message log file, and then re-execute the command.

KFPL00715-I
Index load started at aa....aa, index=bb....bb."cc....cc", RDAREA=dd....dd, generation=ee (L)

Index loading has started.

aa....aa: Server name

bb....bb: Authorization identifier

cc....cc: Index identifier

dd....dd: RDAREA name

(S)

Continues processing.

KFPL00716-I
Index load ended at aa....aa, index=bb....bb, RDAREA=cc....cc, return code=dd (L)

Index loading has terminated with the return code dd.

aa....aa: Server name

bb....bb: Index identifier

cc....cc: RDAREA name

dd: Return code

0: Normal termination

8: Abnormal termination

(S)

Continues processing.

(O)

For abnormal termination, correct the cause of the error according to the error message that was output before this message.

KFPL00717-I
Pdrorg started, func=aaaa (L)

Processing aaaa of the ajsembdbrorg command has started.

aaaa: Type of processing

rorg: Table reorganization

unld: Table unloading

reld: Table reloading

ixmk: Batch creation of indexes

ixrc: Index re-creation

ixor: Index reorganization

rclm: Reclaiming of free pages in use

bfon: Reading of pages

(S)

Continues processing.

KFPL00719-I
Pdrorg terminated, return code=aa (E+L)

Processing of the ajsembdbrorg command has terminated.

aa: Return code

0: Normal termination

4: Normal termination, but with a warning-level error not related to the processing occurring.

8: Abnormal termination

(S)

Terminates processing.

(O)

When the return code is not 0 or 4, correct the error by checking the error message output to the standard output or message log file, and then re-execute the command.

When the return code is 4, ignore the message and continue processing.

KFPL00721-I
aa....aa in table bb....bb.cc....cc deleted, RDAREA=dd....dd (L)

Line data in the table bb....bb.cc....cc has been deleted from the RDAREA dd....dd.

aa....aa: Deleted data

Data: Line data

bb....bb: Authorization identifier

cc....cc: Table identifier

dd....dd: RDAREA name

(S)

Continues processing.

KFPL00732-I
aa....aa started, table=bb....bb.cc....cc, spacelvl=d, generation=ee (L)

Unloading or reloading of the table bb....bb.cc....cc has started.

aa....aa: Executed processing

{Reload | Unload}

bb....bb: Authorization identifier

cc....cc: Table identifier

(S)

Continues processing.

KFPL00734-I
aa....aa ended, table=bb....bb.cc....cc, return code=dd (L)

Unloading or reloading of the table bb....bb.cc....cc has terminated.

aa....aa: Type of processing

Unload: Unloading

Reload: Reloading

bb....bb: Authorization identifier

cc....cc: Table identifier

dd: Return code

(S)

When the return code is 0 or 4:

Continues processing.

When the return code is not 0 or 4:

Terminates processing.

(O)

When the return code is not 0 or 4:

Correct the cause of the error according to the error message output to the log file, and then re-execute the command.

KFPL00736-I
Pdrorg restarted, at aa....aa,table=bb....bb."cc....cc"dd....dd (L)

Table reorganization was restarted at aa....aa.

aa....aa: Type of processing

unload: Unloading

delete: Deletion of data

reload: Reloading

ixrc: Index re-creation

status clear: Status clear

bb....bb: Authorization identifier

cc....cc: Table identifier

dd....dd: ", server=server-name" is displayed.

(S)

Continues processing.

KFPL00739-I
Pdreclaim terminated, return code=aaa (L)

Processing of the ajsembdbreclaim command has terminated with return code aaa.

aaa: Return code

0: Normal termination (Reclaiming of free pages in use has finished.)

4: Timeout (Reclaiming of free pages in use is in progress.)

8: Abnormal termination (Reclaiming of free pages in use failed).

Value other than above: Abnormal termination (The ajsembdbreclaim command cannot be started, or has terminated abnormally.)

(S)

Terminates processing.

(O)

When the return code is 4:
Wait for termination of the job that is accessing the table whose free pages are being reclaimed, and then re-execute the command.

When the return code is 8:
Correct the error by checking the message that was output before this message, and then re-execute the command.

When the return code is not 0, 4, or 8
The value is a return value from the system function. Determine the cause of the abnormal termination by checking the standard error output, message log file, Windows event log or syslog, correct the problem, and then re-execute the ajsembdbreclaim command.

KFPL00810-I
aa....aa restart at bb....bbth row (E+L)

Command processing was restarted at line number bb....bb.

aa....aa: Command name

Pdrorg: ajsembdbrorg

bb....bb: Number of lines from the beginning of the unload data file

(S)

Continues processing.

KFPL15047-E
File I/O error occurred, reason=aa....aa, func=bb....bb, errno=cc....cc, (dd....dd) (E+L)

An error occurred during file I/O.

aa....aa: Cause of the error

Empty-file:

The specified file is empty (0 bytes).

File-format:

The specified file name is invalid.

File-lock:

Another user is using the file. The file name specified on the command line or in the control statement might be a file name that is being used by another user. Alternatively, file-lock resources specified in an OS kernel parameter might be insufficient.

If the ajsembdbcond-sample script is being executed, wait until the current execution terminates, and then re-execute the command. If the ajsembdbcond-sample script is not being executed, check the values of the kernel parameters for the file system.

Invalid-device:

The entry type (attribute) of the specified file is invalid. A directory name might be specified in a location that requires a file name (or vice versa), or a character type special file might be assigned to a file that cannot use a character type special file.

Invalid-path:

The path name is invalid.

Invalid-permission:

The permission for the specified file is invalid (access permission error). It is possible that the embedded database system administrator does not have access permission to use the file.

No-file:

The file to be read was not found. Alternatively, the file being written to was deleted.

No-space:

The file to be written to does not have sufficient free space.

In UNIX:

If this error occurs when there is sufficient free space on the disk, the embedded database file system area might not be defined as a large file, or the limit value of an OS kernel parameter might have been exceeded.

Specify 2 gigabytes or unlimited as the maximum file size that can be handled in the kernel parameter for file settings. Especially in AIX, care is required because the default file size limit is 1 gigabyte.

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

A system function name is displayed if the error was detected in the OS.

A function name, beginning with p_f_ios, for the embedded database file system is displayed if the error was detected in the embedded database file system.

In all other cases, *** is displayed.

cc....cc: Error code

The error number returned by the system function (errno: external reference variable indicating the error status) is displayed if the OS detected the error.

The error code of the embedded database file system is displayed if the error was detected in the embedded database file system. For details about the error codes, see C. Error Codes Returned from Access Requests for an Embedded Database File System. The probable causes of the error and the corrective actions are as follows:
-1511:
The specified file path name might violate the file naming rules of the embedded database file system. Make sure that the area name contains no more than 117 characters and the file name contains no more than 30 characters.
-1532:
The specified file path name might be invalid. Correct the file path name. If you specify the embedded database file system name without specifying a file name, also specify a file name.
-1534:
The specified file name might be a file name that is being used by another job. Change the file name.
-1535:
Insufficient space. If space becomes insufficient as soon as the processing starts, the file size specified on the command line or in the control statement might exceed the limit of the embedded database file system. Use the ajsembdbaddarea command to add space.
-1540:
The embedded database system administrator does not have access permission for the embedded database file system. Grant access permission to the embedded database system administrator.

For any other cause, 0 is displayed.

dd....dd: Troubleshooting information (source file and line number in which the error was detected)

(S)

Terminates processing.

(O)

Using the cause of the error, function name, and error code, correct the error by referring to the errno.h file, the documentation for your OS, and C. Error Codes Returned from Access Requests for an Embedded Database File System. Then retry.

KFPL15227-E
Unable to aa....aa without bbbbbb privilege (E)

The aa....aa command cannot be executed because you do not have access permission for the table.

aa....aa: Command

pdrorg: ajsembdbrorg

pdreclaim: ajsembdbreclaim

bbbbbb: Required access permission

DBA: DBA permission

delete: DELETE permission

insert: INSERT permission

select: SELECT permission

(S)

Terminates processing.

(O)

Re-execute the command as the following user:

In Windows: User who has logged as a member of the Administrators group

In UNIX: User who has superuser privileges

If you executed the ajsembdbsetup command with the -a and -ap options, specify the same values as these options in the ajsembdbrorg or ajsembdbreclaim command and then execute that command.

KFPL20001-E
Insufficient memory in message buffer pool due to concurrent execution of aa....aa (L)

Memory in the message storage buffer pool was temporarily insufficient when the ajsembdbreclaim and ajsembdbrorg commands were executed concurrently or more than one command with the same name was executed concurrently for the same embedded database. Note that this error might cause the message KFPS00854-W to be output, although no server error has occurred in this case.

aa....aa: Program name

{"pdrorg"}

(S)

Terminates processing.

(O)

Wait until the currently executed ajsembdbreclaim and ajsembdbrorg commands terminate, and then retry the operation.

KFPL20020-E
Transaction (aa....aa) error occurred, code=bbbbb (L)

The transaction could not be started or determined.

aa....aa: Type of transaction

{ begin | commit | rollback }

bbbbb: Error details code

(S)

Terminates processing.

(O)

Correct the error by referring to B. Return Codes of System Calls, and then re-execute the command.

KFPL25005-E
Invalid attribute exists in Control file, line=aa....aa (E)

The value of the line number aa....aa in the control information file is invalid.

The probable causes are as follows:

The path specified in the -d option of the ajsembdbrorg command is invalid.

The path specified in the -b option of the ajsrpdbsync command is invalid.

aa....aa: Line number in which the error occurred during analysis

(S)

Terminates processing.

(O)

Specify an absolute path in the -d option of the ajsembdbrorg command or -b option of the ajsrpdbsync command, and then re-execute the command.

KFPL25361-E
Lock time out error occurred,RDAREA=aa....aa (E+L)

The lock on the aa....aa database area for acquiring data timed out.

aa....aa: Database area name

(S)

Terminates processing.

(O)

Wait for a time when there are fewer job operations, and then re-execute the command.

KFPL27500-E
Transaction wait time over,index=aa....aa."bb....bb",RDAREA=cc....cc (L)

A timeout occurred during execution of the ajsembdbreclaim command because a transaction accessing the index could not be determined.

aa....aa: Authorization identifier

bb....bb: Index identifier

cc....cc: RDAREA name

(S)

Terminates processing.

(O)

Wait until the job currently being executed terminates, and then retry the operation.

KFPL31010-E
Invalid row length, line=aa....aa (R)

The length of the line data for the line number aa....aa in the input file is invalid.

This message is output when a problem is found in the data file stored in the directory specified in the -d option of the ajsembdbrorg command.

aa....aa: Line number

(S)

Terminates processing.

(O)

The character set or the endian form used in the data file stored in the directory specified in the -d option of the ajsembdbrorg command might be inconsistent. Make sure that the specified file is correct, and then retry the operation.

KFPL90002-I
Process aa....aa ended. return code=bb,yyyy/mm/dd,hh:mm:ss (S)

The processing indicated by aa....aa will now end.

aa....aa: Type of processing

rorg: Reorganization

bb: Return code

0: Normal termination. Reorganization of all tables terminated.

4: Normal termination. Reorganization of tables is in progress.

8: Termination with an error. The data was recovered from the backup.

12: Termination with an error. The data could not be recovered from the backup.

yyyy/mm/dd: Execution end date

hh:mm:ss: Execution end time

(S)

Terminates processing.

(O)

When the return code is 4:
The command might be delayed because of a heavy host load caused by other programs.
Re-execute the command when the host load has decreased.

When the return code is 8 or 12:
For details about the error, see the contents of the execution information file indicated in the message KFPL90003-E. If the ajsembdbcond-sample script is being executed, correct the error and then take appropriate action for the actions to be taken for errors, in Supplementary notes in 10.2.2(2)(c) Customizing the reorganization scripts in the Job Management Partner 1/Automatic Job Management System 3 Administration Guide.
If the ajsembdbrorg command is being executed, correct the error and then re-execute the command.

KFPL90003-E
Eliminationg the cause of the error, refer to executed information file="aa....aa" (E)

The error indicated in the execution information file is found.

aa....aa: Execution information file name

(S)

Terminates processing.

(O)

Obtain the error details by checking the contents of the execution information file, and then correct the error.

KFPL90021-I
DB hold step ended (S)

Block processing for the database has ended.

(S)

Continues processing.

KFPL90022-I
Before backup step ended (S)

Backup processing before the main processing has ended.

(S)

Continues processing.

KFPL90023-I
aa....aa step started (S)

aa....aa processing will now start.

aa....aa: Type of processing

Reorganize: Reorganization

(S)

Continues processing.

KFPL90024-I
aa....aa step ended (S)

aa....aa processing will now end.

aa....aa: Type of processing

Reorganize: Reorganization

(S)

Continues processing.

KFPL90025-I
After backup step ended (S)

Backup after the main processing has ended.

(S)

Continues processing.

KFPL90026-I
DB release step ended (S)

Processing to release the database from the blocked state has ended.

(S)

Continues processing.

KFPL90027-I
DB stop process started (S)

The database will be stopped for error recovery processing.

(S)

Continues processing.

KFPL90028-I
Recover step started on aa....aa error (S)

Database recovery from the backup file has started.

aa....aa: Type of processing

rorg: Reorganization

(S)

Continues processing.

KFPL90101-I
aa....aa (R)

This message shows the command line used to execute the command.

aa....aa: Command line used to execute the ajsembdbrorg command

(S)

Continues processing.

KFPL90102-I
aa....aa (R)

This message shows one line of the control statement used to execute the ajsembdbrorg command.

aa....aa: Control statement used to execute the ajsembdbrorg command

(S)

Continues processing.

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.

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

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

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

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

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

embedded-database-practical-directory\spool\oslmqid

embedded-database-practical-directory\spool\oslsmid

embedded-database-practical-directory\spool\pdprcsts

embedded-database-practical-directory\spool\scdqid1

embedded-database-practical-directory\spool\scdqid2

embedded-database-practical-directory\tmp\pdommenv

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

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

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 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.

KFPR00754-I
Pdcopy started (L+S)

Processing of the ajsembdbbackup command has started.

(S)

Continues processing.

KFPR00756-I
Pdcopy terminated, return code=aa (L+S)

Processing of the ajsembdbbackup command terminated with a return code shown below.

aa: Return code for the ajsembdbbackup command

0: Normal termination

8: Abnormal termination (An error occurred during copy processing, but some backups were created successfully.)

12: Abnormal termination (All copy processing failed.)

(S)

Continues processing.

(O)

For abnormal termination, correct the error by checking the error message that was output before this message, and then retry the operation.

KFPR00764-I
Pdrstr started (L+S)

Processing of the ajsembdbrstr command has started.

(S)

Continues processing.

KFPR00765-I
Pdrstr terminated, return code=aa (L+S)

Internal processing of the ajsembdbrstr command terminated with a return code shown below.

aa: Return code for internal processing of the ajsembdbrstr command

0: Normal termination

4: Termination with a warning (A close error occurred in the backup file or unload log file, or the data of the RDAREA to be recovered was not found in the backup file.)

8: Abnormal termination (An error occurred, but one or more RDAREAs were recovered successfully.)

12: Abnormal termination (Recovery failed for all RDAREAs.)

(S)

Continues processing.

Action

For abnormal termination, correct the cause of the error according to the error message that was output before this message.

KFPR16003-E
aaaaaa error occurred, file=bb....bb (E+L)

A file I/O error occurred.

aaaaaa: Processing in which an error occurred

Close: Close processing

Open: Open processing

Read: Read processing

Reopen: Open processing for the second or later volume in a multi-volume file

Write: Write processing

bb....bb: File name

(S)

Terminates processing. However, the system may continue processing if a file close error occurred.

Action

Correct the cause of the error according to the message that was output after this message, and then re-execute the command.

KFPR16005-E
Insufficient memory for PROCESS, size=aa....aa (L+S)

An attempt to allocate the work area required for executing the ajsembdbbackup command has failed due to insufficient memory.

aa....aa: Size of the area that was to be allocated (unit: bytes)

(S)

Terminates processing.

Action

Terminate unnecessary processes to free memory, and then retry the operation. Alternatively, add real memory for the OS.

KFPR16014-E
Pdcopy version aa....aa and HiRDB version bb....bb do not match (L+S)

The version of the command used internally by the ajsembdbbackup command differs from the version of the embedded database.

The database area specified in the -d option of the ajsembdbbackup command might differ from the area of the embedded database specified in the -id option.

aa....aa: Version or revision number of the command used internally by the ajsembdbbackup command

bb....bb: Version or revision number of the embedded database

(S)

Terminates processing.

(O)

Make sure that the values specified in the -d and -id options of the ajsembdbbackup command match the combination of the values of the -d and -id options used when the ajsembdbbuild command was executed, and then retry the operation.

KFPR16101-E
File I/O error occurred, reason=aa....aa, func=bb....bb, errno=cc....cc, (dd....dd) (L+S)
An error occurred during file I/O processing.

aa....aa: Cause of the error

File-lock:

The file you want to use cannot be read or written to because it has been locked by another utility. The file name specified on the command line or in the control statement might be a file name that is being used by another job. Alternatively, file-lock resources specified in an OS kernel parameter might be insufficient.

Invalid-device:

The entry type (attribute) of the specified file is invalid. A directory name might be specified in a location that requires a file name (or vice versa), or a character type special file might be assigned to a file that cannot use a character type special file.

Invalid-path:

The path name is invalid.

Invalid-permission:

The permission for the specified file is invalid (access permission error). It is possible that the embedded database system administrator does not have access permission to use the file.

No-file:

The file that was to be opened for reading was not found. Alternatively, the file being written to was deleted.

No-space:

The file to be written to does not have sufficient free space. Allocate sufficient free space.

In UNIX, if this error occurs when there is sufficient free space on the disk, the limit value of an OS kernel parameter might have been exceeded.

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

A function name, beginning with p_f_ios, for the embedded database file system is displayed if the error was detected in the embedded database file system.

*** is displayed if the error was detected in the embedded file system in those cases in which a function was not being used.

In all other cases, a system function name is displayed.

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

The error code of the embedded database file system is displayed if the error was detected in the embedded database file system.

The error number returned by the system function (errno: external reference variable indicating the error status) is displayed if the OS detected the error.

dd....dd: Source file name and line number where the error was detected

(S)

Terminates processing.

Action

Take appropriate action according to the following table.

Cause of the error Action

The error was detected in the embedded database file system. Correct the error by referring to C. Error Codes Returned from Access Requests for an Embedded Database File System, and then retry the operation.

The error was not detected in a function. Correct the error indicated by aa....aa, and then retry the operation.

The OS detected the error. Correct the error by referring to the OS documentation, and then retry the operation.
 
KFPR16205-E
Insufficient memory for PROCESS, size=aa....aa (L+S)

An attempt to allocate the work area required for executing the ajsembdbrstr command has failed due to insufficient process-specific area.

aa....aa: Size of the area that was to be allocated (unit: bytes)

(S)

Terminates processing.

Action

Check whether another process is using a large amount of memory.

If another process is using a large amount of memory:

Wait until the process terminates, and then re-execute the command.

If another process is not using a large amount of memory:

Take one of the following actions to increase the amount of free space in memory:

Reduce the number of processes running concurrently.

Increase the swap area.

Add real memory.

KFPR16214-E
Pdrstr version aa....aa and HiRDB version bb....bb do not match (L+S)

The version of the command used internally by the ajsembdbrstr command differs from the version of the embedded database.

The database area specified in the -d option of the ajsembdbrstr command might differ from the area of the embedded database specified in the -id option.

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

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

(S)

Terminates processing.

(O)

Make sure that the database area specified in the -d option of the ajsembdbrstr command is the area of the embedded database specified in the -id option.

KFPR16318-E
Backup data not found, RDAREA name="aa....aa" (L+S)

The specified backup file does not contain a backup of the RDAREA.

aa....aa: Name of the RDAREA name without backup data

(S)

Recovers the RDAREA without using the backup data. If the unload log file is specified and the update log for the RDAREA is found, the system recovers the RDAREA by using the log only.

(O)

Verify the following, correct the error, and then retry the operation:

Before executing the ajsembdbrstr command, make sure that the RDAREA is in a recoverable state.

Make sure that the backup file is specified correctly.

KFPR16330-E
Log was not found when backup aa....aa at bb....bb-cc....cc, server=dd....dd (L+S)

When the -l option has been specified in the ajsembdbrstr command, the unload log file does not include the information for the period required for recovery.

aa....aa: Dates not included

started: Time copy acquisition started

ended: Time copy acquisition ended

bb....bb: System log record number 1

cc....cc: System log record number 2

dd....dd: Name of the server for which recovery is being performed

(S)

Interrupts embedded database recovery processing.

(O)

When the -l option in the ajsembdbrstr command is specified, specify an unload log file that includes the information for the period required for recovery, and then retry the operation. If the required unload log file does not exist, use only the backup file for recovery.

KFPR26001-E
Communication "aa....aa" error occurred, code=bbbbb (L+S)

A communication error occurred during execution of the ajsembdbbackup command.

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

bbbbb: Error code of the RPC-related function in which the error occurred

(S)

Terminates processing.

Action

Correct the error by referring to B. Return Codes of System Calls, and then retry the operation. If an error that the embedded database system administrator cannot handle has occurred, contact system administrator.

KFPR26006-E
Invalid parameter aa....aa exists at -b option in command line (L+S)

An option in the command line may contain an invalid parameter. A list RDAREA is not copied or recovered.

aa....aa: Invalid parameter

b: Option name

(S)

Waits until the analysis of the command line terminates, and then cancels processing. However, the system continues processing when all the following conditions are satisfied:

The -J option and the -r option are specified.

The message KFPR26061-W is output.

Action

Correct the specification on the command line, and then re-execute the command.

KFPR26012-E
HiRDB file aa....aa error, errno=bb....bb, HiRDB file name=cc....cc (L+S)

The error indicated in aa....aa occurred in the file indicated in cc....cc.

aa....aa: Error details

close: File close

create: File creation

fstat: Acquisition of file information

open: File open

read: File reading

write: File writing

expand: File expansion

reopen: Open of the second or later file during processing of multiple files

bb....bb: Error code

0: The requested size could not be read or written.

Other than 0: See C. Error Codes Returned from Access Requests for an Embedded Database File System.

cc....cc: Name of the file in which the error occurred

(S)

Cancels processing for a backup file. However, the system continues processing if there is another backup file or if all of the following conditions are satisfied:

The file is an embedded database file in an RDAREA.

The -J option is specified.

The error details indicate open or close.

The message KFPR26061-W was output.

There is another RDAREA that has not been processed yet.

Action

When the file is used for a database:

Recover the appropriate RDAREA, and then retry.

When the file is used for backup:

Correct the cause of the error according to C. Error Codes Returned from Access Requests for an Embedded Database File System, and then retry.

When the error code is -1556 or -1562, the probable causes are as follows:

Error code Cause

-1556 After the embedded database file exceeded the initial allocation size, an attempt to expand the file using the secondary allocation size failed.

An attempt was made to expand the file beyond the limit on the number of times the embedded database file system area can be increased.

An attempt was made to expand the embedded database file more than the maximum number of times, which is 23.

-1562 The type of the embedded database file system area is not UTL.

If you cannot determine the cause of the error, contact system administrator.

KFPR26017-E
Insufficient memory in message buffer pool due to concurrent execution of "pdcopy" (L+S)

Memory in the message storage buffer pool for the utility server was temporarily insufficient when ajsembdbbackup commands were executed concurrently. Note that this error might cause the message KFPS00854-W to be output, although no server error has occurred in this case.

(S)

Terminates processing.

(O)

Wait until the ajsembdbbackup command currently being executed terminates, and then retry the operation.

KFPR26021-E
Unable to output result of pdcopy (L+S)

The processing result of the ajsembdbbackup command cannot be output because of the error displayed in the message output before this message.

(S)

Terminates processing.

Action

Correct the error, and then re-execute the command. Note that if no other error has occurred, the backup processing has terminated. Accordingly, re-execution is unnecessary if you do not need the execution result.

KFPR26022-I
Output result of pdcopy to aa....aa (L+S)

The processing result of the ajsembdbbackup command will be output to the aa....aa file.

aa....aa: Name of the output file

(S)

Terminates processing.

KFPR26072-E
Invalid time stamp found, RDAREA name=aa....aa, file name=bb....bb, offset=cc....cc, time stamp=(dd....dd,ee....ee) (L+S)

A page containing an invalid time-stamp was found.

aa....aa: RDAREA name

bb....bb: Embedded database file name. The last 64 bytes are displayed.

cc....cc: Decimal number indicating the relative record position of the page containing the invalid time-stamp as calculated from the beginning of the embedded database file

dd....dd: Time-stamp at the beginning of the page, converted to the date format YYYY/MM/DD HH:MM:SS

ee....ee: Time-stamp at the end of the page, converted to the date format YYYY/MM/DD HH:MM:SS

(S)

Terminates processing.

(O)

When using the ajsembdbbackup command with the -s option specified to create a backup:

The backup could not be created because the page to be backed up was being output. Re-execute the ajsembdbbackup command.

When using the ajsembdbbackup command without the -s option specified to create a backup:

The area in the displayed RDAREA is corrupted. You must recover the area by using the previously created backup.

KFPR26201-E
Communication "aa....aa" error occurred, code=bbbbb (L+S)

A communication error occurred during execution of the ajsembdbrstr command.

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

bbbbb: Error code of the RPC-related function in which the error occurred

(S)

Terminates processing.

Action

Correct the error by referring to B. Return Codes of System Calls, and then retry the operation.

KFPR26203-E
System call error, func=aa....aa, errno=bbb (L+S)

An error occurred during internal processing.

aa....aa: Maintenance information

bbb: Maintenance information

(S)

Terminates processing.

Action

Take corrective action according to the message displayed before or after this message.

KFPR26212-E
HiRDB file aa....aa error, errno=bb....bb, HiRDB file name=cc....cc (L+S)

The error indicated by aa....aa occurred in the file indicated by cc....cc.

aa....aa: Error details

close: File close

create: File creation

fstat: Acquisition of file information

open: File open

read: File reading

write: File writing

expand: File expansion

bb....bb: Error code

0: The requested data size could not be read or written.

Other than 0: See C. Error Codes Returned from Access Requests for an Embedded Database File System.

cc....cc: Name of the file in which the error occurred

(S)

When the file is a database file:

Skips recovery processing of the RDAREA, and continues recovery of other RDAREAs.

When the file is a backup file:

Cancels recovery processing.

(O)

When the file is a database file:

Use the ajsembdbbuild command to re-create the environment of the embedded database, and then retry the operation.

When the file is a backup file:

Retry with another backup file.

When the error details indicate write and the error code is 0, the file system for the OS might not have sufficient free space.

KFPR26217-E
Insufficient memory in message buffer pool due to concurrent execution of "pdrstr" (L+S)

Memory in the message storage buffer pool for the utility server was temporarily insufficient when ajsembdbrstr commands were concurrently executed. Note that this error might cause the message KFPS00854-W to be output, although no server error has occurred in this case.

(S)

Terminates processing.

(O)

Wait until the ajsembdbrstr command currently being executed terminates, and then retry the operation.

KFPR26220-E
System manager "aa....aa" failed, return code=bb....bb (L+S)

A system-related "aa....aa" function error occurred.

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

bb....bb: Error code of the system-related function in which the error occurred

(S)

Terminates processing.

Action

When the name of the system function with the error is pdi_omm_attach and the error code is -144:

The probable causes are as follows. Specify the correct host name in the -mh option, and then re-execute the command.

A host name is not specified in the -mh option, and the specified master directory RDAREA was not found on the server host on which the ajsembdbrstr command was entered.

A master directory RDAREA was not found on the server host for the host name specified in the -mh option.

For other cases:

Correct the error by referring to B. Return Codes of System Calls, and then retry the operation.

KFPR26221-E
Unable to output result of pdrstr (L+S)

The processing result of the ajsembdbrstr command cannot be output because of the error that was displayed in the message output before this message.

(S)

Terminates processing.

Action

Correct the error, and then re-execute the command. Note that if no other error has occurred, the backup processing has terminated. Accordingly, re-execution is unnecessary if you do not need the execution result.

KFPR26222-I
Output result of pdrstr to aa....aa (L+S)

The processing result of the ajsembdbrstr command will be output to the aa....aa file.

aa....aa: Name of the output file

(S)

Continues processing.

KFPR26226-E
SystemID of aa....aa is invalid (L+S)

The system cannot recover the database because the system ID for aa....aa does not match the running embedded database.

aa....aa: File type

backup file: Backup file

sys log file: System log file

unload log file: Unload log file

(S)

Terminates processing.

Action

Take one of the following actions:

For a backup file or an unload log file:
Specify the correct file, and then retry the operation.

For a system log file
The system log might have been corrupted. Use the ajsembdbbuild command to re-create the environment of the embedded database, and then recover the data from the backup created with the ajsembdbbackup command.

KFPR26227-E
-l or -d option is not specified for backup file with -M s option (L+S)

An unload log file is not specified when the backup file to be obtained with the -M s option specified is used for recovery.

(S)

Terminates processing.

Action

When the -l option is specified:

Specify the unload log file, and then retry.

When the -d option is specified:

Specify the directory containing the unload log file, and then retry.

KFPR26229-E
To recover Master RDAREA, pdstart should be executed with -r option (L+S)

To recover the master directory RDAREA, use the ajsembdbstart command with the -r option to start the embedded database.

(S)

Terminates processing.

(O)

Use the ajsembdbstop command to terminate the embedded database, use the ajsembdbstart command with the -r option to restart the embedded database, and then retry the operation.

KFPR26270-W
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" (L)

Not all of the unload log files required for recovering the database are specified in the -l option of the ajsembdbrstr command. This message indicates the log information stored in the RDAREA and the log information in the unload log files specified in the -l option of the ajsembdbrstr command.

Cautionary note

If a backup was created in the following ways, this warning message appears even when all of the unload log files required for recovering the database are specified. In such cases, ignore the warning message.

A backup was created after normal termination of the database:
This message appears even when all of unload log files containing the system logs used after the next normal startup are specified in the -l option.

When the ajsembdbbackup command was executed, the scheduler service database was updated (for example, a jobnet was updated):
This message appears even when all of unload log files containing the system logs used after swapping of the system log file are specified in the -l option.

aa....aa: Log information (log server run ID of the system log file) in the first unload log file^#1 specified in the -l option

bb....bb: Log information (generation number of the system log file) in the first unload log file^#1 specified in the -l option

cc....cc: Log information (log server run ID of the system log file) stored in the RDAREA^#2

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

ee....ee: RDAREA name

#1 The first unload log file is the applicable unload log file.

#2 The log information is stored in the RDAREA when the embedded database terminates normally.

Action

According to the values in cc....cc and dd....dd, specify all the unload log files required for recovering the database in the -l option of the ajsembdbrstr command, and then retry the operation.

KFPR26272-W
No unload log file in specified directory, directory name = aa....aa (S+L)

The unload log file was not found under the specified directory.

aa....aa: Directory name (If the length is more than 100 characters, only the last 100 characters are output.)

(S)

Continues processing.

Action

Check the aa....aa directory name. If the directory file is incorrect, correct the error and then retry the operation.

KFPR26273-E
Error occurred directory analysis, directory name = aa....aa (S+L)

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

aa....aa: Directory name (If the length is more than 100 characters, only the last 100 characters are output.)

(S)

Terminates processing.

Action

Check whether the specified directory name is correct. If the directory file is incorrect, correct the error and then retry the operation.

KFPR26280-E
Specified backup file invalid. filename=aa....aa, code=bb....bb (S+L)

The specified backup file is invalid.

aa....aa: Name of the backup file in which the error occurred (When the name contains more than 100 characters, the last 100 characters of the backup file name are output.)

bb....bb: Cause of the error

other: A backup file that was not created by using the ajsembdbbackup command

error: A backup file created by pdcopy, but which terminated with an error (return code 12)

(S)

Terminates processing.

(O)

Specify the correct backup file name, and then retry the operation.

KFPS00705-E
Error found while analyzing definition file (L)

An error was detected during analysis of the system definition file of the embedded database.

(S)

Waits for the embedded database to start.

Action

Check whether the system definition file of the embedded database was unintentionally changed. If the system definition file was changed, restore it to its original state, and then execute the ajsembdbstart command.

If other messages were output before or after this message, also check those messages. If you cannot correct the error, contact system administrator.

KFPS00715-E
Unable to continue processing serious error occurred (reason code=aaa). enter pdrpause (E+L)

An error that prevents further processing of the embedded database occurred.

aaa: Reason code

1: There is a problem with the installation environment of the embedded database.

2: A memory shortage occurred

3, 4, 5, 8, 9, 10, 11, 13, 14, 15, 42, 43, 44, 101, 102, 103, 104, and 105: An attempt to access the system file of the embedded database has failed.

6: Processing to acquire the system time has failed.

7: The embedded database terminated abnormally three consecutive times within 30 minutes during restart processing of the embedded database.

20: The system definition of the embedded database has an error.

(S)

Terminates processing.

Action

Take action as follows:

If the ajsembdbstart command did not terminate after this message was output, execute the ajsembdbstop -f command to terminate it.

If other messages were output before or after this message, also check those messages.

Correct the error indicated by the reason code.
1:
- Make sure that installation of the embedded database terminated normally.
- In UNIX, check whether the /etc/inittab file was unintentionally changed.
2:
- Check the status of the running process to make sure that the amount of memory available is greater than the estimated value.
3, 4, 5, 8, 9, 10, 11, 13, 14, 15, 42, 43, 44, 101, 102, 103, 104, and 105:
- Check whether the system file of the embedded database was unintentionally changed.
6:
- Check the running status of the OS for any problems (for example, insufficient resources).
7:
- Check whether all the system log files of the embedded database are full and unable to be overwritten.
- Check whether the environment settings of the embedded database (such as a directory and port number) duplicate any other settings on the same host.
- In UNIX, make sure that the character set types of the OS and the embedded database match.
20:
- Check whether the system definition file of the embedded database was unintentionally changed.

In UNIX, execute the ajsembdbstart -R command.

In Windows, restart the embedded database service (HiRDB/EmbeddedEdition embedded-database-ID). If the service has not stopped, stop the service and then restart it.

If the embedded database does not start automatically, execute the ajsembdbstart command.

If the error persists after you take the above actions, contact system administrator.

KFPS00993-I
Accepted process abnormal end request. PID=aa....aa, TRNGID=bb....bb, TRNBID=cc....cc, REQUEST=dd....dd (L)

This message can be output in the following cases:

The embedded database system has terminated abnormally.

An error has occurred during access to the embedded database.

The ajsembdbcancel command canceled processing of the embedded database operation command.

aa....aa: Maintenance information

bb....bb: Maintenance information

cc....cc: Maintenance information

dd....dd: Maintenance information

(S)

Terminates the processing.

Action

Usually, you can ignore this message. If JP1/AJS3 has output any other error messages, take action based on those messages.

KFPS01040-E
aa....aa error occurred in physical status file bb....bb. reason code=cc....cc (E+L)

An error occurred during access to the system file indicated by bb....bb in the embedded database.

aa....aa: Maintenance information

bb....bb: Path name of the system file

cc....cc: Reason code

(S)

Switches to another system file and continues processing.

Action

Determine the cause of the error from the following reason codes, and take appropriate action.

Reason code Cause Action

0000000006 The file was not found. Make sure that the system file exists in the directory that was specified when the environment of the embedded database was created.

0000000020 You do not have access permissions. Make sure that you have permission to access the directory that was specified when the environment of the embedded database was created and the created system files.

0000000021 You do not have access permissions. Make sure that you have permission to access the directory that was specified when the environment of the embedded database was created and the created system files.

0000000022 A lock error (the target is being used by another process) occurred.

Wait a while and then retry the operation.

For a cluster system, check whether both the primary node and secondary node access a system file on the shared disk.

0000000023 System resources (file lock) are insufficient. Check the system parameters for the OS.

0000000024 You do not have access permissions. Make sure that you have permission to access the directory that was specified when the environment of the embedded database was created and the created system files.

0000000025 System resources (file descriptors) are insufficient. Check the system parameters for the OS.

0000000026 The file was not found. Make sure that the system file exists in the directory that was specified when the environment of the embedded database was created.

0000000027 An I/O error occurred. Check whether a disk error or other OS-related error occurred. Also check whether you can access the directory that was specified when the environment of the embedded database was created.

0000000028 A memory shortage occurred. Check the system parameters for the OS.

0000000029 The file was not found. Make sure that a system file exists in the directory that was specified when the environment of the embedded database was created.

0000000030 In UNIX, the number of open character type special files exceeds the limit. In Windows, the number of open files exceeds the limit. Check the system parameters for the OS.

0000000031 The file name is invalid. The probable causes are:

An invalid character is specified in the file name.

The length of the file name exceeds the limit.

Check the directory name that was specified when the environment of the embedded database was created.

0000000037 The file was not found. Make sure that the system file exists in the directory that was specified when the environment of the embedded database was created.

KFPS01150-E
Auto log unload service terminated. server=aa....aa:create dir=bb....bb:reason=cccc (L)

The auto log unload function has terminated on the aa....aa server.

aa....aa: Embedded database server name

bb....bb: Name of the directory in which unload log files are created

cccc: Reason code indicating the error details

1660: Unloading of the system log file has failed in the directory in which all unload log files are created.

1661: An attempt to create a process for the auto log unload processing has failed.

1664: The unload log file you attempted to create is being used by another process.

(S)

Continues processing.

Action

Take one of the following actions:

When the reason code is 1660:
The disk does not have sufficient free space for the directory in which unload log files are created. Alternatively, a disk failure occurred. Allocate sufficient free space on the disk or recover from the disk failure. Next, execute the ajsembdboplog -r command or restart the embedded database normally to resume the auto log unload function.

When the reason code is 1661:
Check the maximum number of processes that can be executed on the server host and terminate unnecessary processes. In addition, make sure that sufficient system resources such as memory are available.

When the reason code is 1664:
Check whether any process is using a file in the directory in which unload log files are created. Then, execute the ajsembdboplog -r command to restart the embedded database normally to resume the auto log unload function.

When the reason code is other than above:
Collect the following data, and then contact system administrator:
- All files under embedded-database-practical-directory/spool or embedded-database-practical-directory\spool
- System definition file
- Windows event log or syslog
- Execution result of the ajsembdbstatus -l command

KFPS01153-I
Auto log unload service restart. server=aa....aa:create dir=bb....bb:reason=cccc (L)

The automatic log unload functionality for the embedded database will now restart.

aa....aa: Maintenance information

bb....bb: Name of the directory in which unload log files are created

cccc: Reason code

1662: The ajsembdboplog -r command was executed to restart the automatic log unload functionality.

(S)

Continues processing.

KFPS01154-I
Auto log unload service stopped. server=aa....aa:create dir=bb....bb:reason=cccc (L)

The automatic log unload functionality for the embedded database has stopped.

aa....aa: Maintenance information

bb....bb: Name of the directory in which unload log files are created

cccc: Reason code

1662: The ajsembdboplog -t command was executed to stop the automatic log unload functionality.

(S)

Continues processing.

KFPS01200-E
Failure to open aaaa(xx....xx)log file. element file: bb....bb, system A/B: c,reason code=dddd-ee (L)

An attempt to open the embedded database system file has failed.

aaaa: File type

sys: System log file

xx....xx: Maintenance information

bb....bb: File name

c: System type

a: System A

b: System B

dddd: Reason code

ee: Maintenance information

The following table lists the reason codes and describes the actions to be taken.

(S)

Blocks the file in which the error occurred, and continues processing.

Action

Take action according to the reason codes.

Reason code Meaning Action to be taken by the embedded database system administrator

101 A memory shortage occurred. Re-estimate memory.

201 The file name is invalid. The probable causes are:

An invalid character is specified in the file name.

The length of the file name exceeds the limit.

Specify the file name correctly, and then re-execute the command.

202 The specified file name is not a RAW file. Alternatively, the device for this file was not found. Check the settings specified when the environment of the embedded database was created.

203 The embedded database system file was not found.

207 The number of open files exceeded the limit. Check the system parameters for the OS.

208 You do not have access permissions. Make sure that you have permission to access the directory that was specified when the environment of the embedded database was created and the created system files.

209 An I/O error occurred. Check whether a disk error or other OS-related error occurred. Also check whether you can access the directory that was specified when the environment of the embedded database was created.

210 The embedded database system file is inconsistent. Re-create the environment of the embedded database. If the error persists after re-creating the environment, contact system administrator.

211 You do not have access permissions. Make sure that you have permission to access the directory that was specified when the environment of the embedded database was created and the created system files.

212 The file was not found. Make sure that the system file exists in the directory that was specified when the environment of the embedded database was created.

218
219 The specified file cannot be used as a log file. Use another file. If a new file is required, use the ajsembdbaddlog command to add the new file.

220 The specified file is not a log file. Check the settings specified when the environment of the embedded database was created.

221 Lock segments are insufficient. Check the system parameters for the OS.

222 A lock error (the target is being used by another process) occurred.

Wait a while and then retry the operation.

For a cluster system, check whether both the primary node and secondary node access a system file on the shared disk.

KFPS01202-E
Failure to write to aaaa(xx....xx) log file. element file: bb....bb, system A/B: c,reason code=dddd-ee (L)

An attempt to write to the embedded database system file has failed.

aaaa: File type

sys: System log file

xx....xx: Maintenance information

bb....bb: File name

c: System type

a: System A

b: System B

dddd: Reason code

209: An I/O error occurred.

ee: Maintenance information

(S)

Blocks the file in which the error occurred, and continues processing.

Action

Take the following action:

When the reason code is 209
Check whether a disk error or other OS-related error has occurred. Also check whether you can access the directory that was specified when the environment of the embedded database was created.

KFPS01220-E
Request to swap aaaa(xx....xx) log file unable to be executed because there is no standby log file group available. (L)

A factor causing system log swapping occurred, but there was no system log file that could be swapped in.

The reasons for no available system log file are as follows.

(1) There was no standby system log file.

(2) The standby system log file group was one of the following states:

Was waiting for unloading

State in which overwriting was not possible (a sink point dump related to a particular system log file was being collected)

Was being read during recovery processing for the embedded database

Was being used for command processing

aaaa: Maintenance information

xx....xx: Maintenance information

(S)

Stops the embedded database system.

Action

Take appropriate corrective action as follows:

If the automatic unload function has stopped, remove the cause of the stoppage.

Unload the system log file.

Add a system log file.

Restore the system log file to operability.

KFPS01228-W
Error occurred aaaa(bb....bb) log for waiting syncpoint acquisition opportunities. reason code=cccc (L)

A timeout occurred while the system was waiting for the internal processing of the embedded database to finish.

aaaa: Maintenance information

bb....bb: Maintenance information

cccc: Maintenance information

(S)

Continues processing.

Action

If this message appears during execution of the ajsembdbbackup command, wait a while and then re-execute the command. If this message still appears after re-execution of the command or appears at a time other than during execution of the ajsembdbbackup command, contact system administrator.

KFPS01251-E
Aaaa(xx....xx) log file group bb....bb is in invalid state; change file group state. (L)

The status of the bb....bb log file group in aaaa (xx....xx) is invalid. Change the status of the file group.

The invalid status of the log file group is caused by an online fault that has occurred in the previous cycle in the group. If the status is left as is, it will not be possible to acquire log information. Specify the -g or -o option in the ajsembdboplog command to unload the log file. The status of the log file group will change to unloading completed.

aaaa: Log file type

sys: System log file

xx....xx: HiRDB server name

bb....bb: Name of a log file group with the invalid status

(S)

Continues processing to start the log service function.

(O)

Execute the ajsembdboplog command to acquire the log information and change the file group status. For details about the ajsembdboplog command, see ajsembdboplog in 2. Commands in the manual Job Management Partner 1/Automatic Job Management System 3 Command Reference 1.

KFPS01256-E
No standby file groups of aaaa(xx....xx) log are available. (L)

There is no system log file group that can be used.

aaaa: Maintenance information

xx....xx: Maintenance information

(S)

Interrupts the processing to start the embedded database.

Action

See the "Action" section for the KFPS01220-E message.

KFPS01271-I
Unloading comleted. generation number=aa....aa, start block number=bb....bb, end block number=cc....cc (E+L)

Unloading has been completed. The range of unloaded blocks are indicated.

aa....aa: Generation number of the log file group being unloaded

bb....bb: Number of the first unloaded block

cc....cc: Number of the last unloaded block

Note:

If any unloaded log blocks are missing, ******** is displayed for cc....cc. Note that this message is displayed only when the automatic log unloading function is used.

KFPS01277-E
Log point information is invalid. info=aaaa (L)

An environment error was detected when the embedded database was being restored.

aaaa: Maintenance information

(S)

Continues processing.

Action

Check the following and take appropriate action:

Whether the backup file specified in the ajsembdbrstr command is invalid.

If neither of these problems exists, contact system administrator.

KFPS01278-W
Failure to processing log file group. type: aaa(bb....bb),file group: cc....cc,reason code=dddd-ee (L)

The cc....cc log file group used by the bb....bb server will be ignored because the file status cannot be referenced for the reason indicated in dddd.

aaa: Log type (sys or lar)

bb....bb: Embedded database server name

cc....cc: File group name

dddd: Reason code

209: Log file I/O error

213: Log file open error

215: Input to the log file is impossible.

222: Another process is using this file group.

1601: There is no applicable log file.

ee: System maintenance information

(S)

Continues processing, ignoring the log file group indicated in the message.

(O)

There is no problem if you do not use the log file indicated in the message.

During execution of the ajsembdbrstr command
If you have used the log file from the time a backup was obtained until the current time, it may not be possible to recover the database correctly. If the message KFPS01279-W was output, consider its contents, and after contacting the system administrator, take corrective action. After taking corrective action, re-execute the command.

For other cases
Take action according to the reason code, and then re-execute the command. If the message KFPS01279-W was output, take corrective action for the error indicated in the message, and then re-execute the command.

Action

There is no problem if the log file indicated in the message is not required for executing the ajsembdbrstr command. If the log file is required for executing this command, check the following and then take action.

If an error occurred in the log file group or if the log file group was initialized after being used online, check whether the log file can be recovered. If it can be recovered, recover it and then retry.

Check whether the log file specification in the server definition is correct. Correct any error, and then retry.

If neither of the above is applicable, contact system administrator.

KFPS01279-W
Unable to use log file. element file: aa....aa, system A/B: b,reason code=cccc-dd (L)

The status of the aa....aa log file cannot be referenced for the reason indicated in cccc. This log file will be ignored.

aa....aa: Log file name

b: The system where an error occurred (a or b)

cccc: Reason code

dd: System maintenance information

(S)

Continues processing, ignoring the log file.

(O)

There is no problem if you do not use the log file indicated in the message, or if the message KFPS01278-W for the file group containing the log file is not output immediately after this message. If neither of the above is applicable, determine the cause of the error according to the reason code, and then contact the administrator.

Action

There is no problem if the log file shown in the message is not required for executing the ajsembdbrstr command. If the log file is required for executing this command, determine the cause of the error according to the reason code, and perform recovery by following the instructions in the message KFPS01278-W, and then, retry. The following lists the reason codes.

Reason code Meaning Operator action Action by the embedded database system administrator

101 A memory shortage occurred. Wait until the currently running process terminates, and then re-execute the command. Re-estimate memory.

201 The file name is invalid. Probable causes are:

An invalid character is specified in the path name.

The length of the embedded database file name exceeded the limit (30 characters).

Specify the file name correctly, and then re-execute the command --

202 The name of the embedded database file system area for the specified path is not an embedded database file system area. Check the name of the embedded database file system area for the specified path, and then re-execute the command Check the file specification in the pdlogadpf operand.

203 The specified path device is not initialized for the embedded database file system. --

207 The upper limit was exceeded when the embedded database file system area for the specified path was opened. --

208 You do not have permission to access the embedded database file system area for the specified path. Check access permissions for the embedded database file. Check the file specification in the pdlogadpf operand.

209 An I/O error occurred. Determine the cause of the I/O error, and take action. --

210 The version of the embedded database file system is inconsistent. -- Check the file specification in the pdlogadpf operand.

211 You do not have permission to access the specified file. Check the access permission for the log. --

212 The specified file is not found. -- Check the file specification in the pdlogadpf operand.

221 Lock segments are insufficient. Check the number of record lock segments that is specified when the OS is started.

222 The system log file is being used by another process. Check the operation status of the system log file or its file group, and then re-execute the command. --

603 Management information on the file is corrupted. Initialize this file.

605 The file structure of the file differs from the current file structure. The file structure might have been changed. Contact the embedded database system administrator to find out if the file structure has been changed. If the file structure has not been changed, initialize this file. Check the definition to make sure that the file group that uses the file and the system log file have not been changed. If the file structure has been changed, return the file structure in the definition to its original state.

1607 The file has not been used in the embedded database. Check the file group. --

(Legend)

--: Not applicable

KFPS01286-E
Unable to perform swapping because no standby log file group is available. (E)

Swapping is not possible because there is no system log file to be swapped in.

(S)

Cancels command processing.

(O)

Take corrective action as follows, and if required, re-execute the command:

If the automatic log unloading function has stopped, remove the cause of the stoppage and then restart the function.

Use the ajsembdbaddlog command to add the system log file.

For details about the ajsembdbaddlog command, see ajsembdbaddlog in 2. Commands in the manual Job Management Partner 1/Automatic Job Management System 3 Command Reference 1.

KFPS01390-W
Unable to expand sys(aa....aa) log file, file group=bb....bb, system A/B=c, reason=dd....dd (L)

The system log file cannot be expanded. From this point, the corresponding system log file is removed as a candidate for expansion.

aa....aa: Maintenance information

bb....bb: System log file name

c: System type

a: System A; b: System B

dd....dd: Reason code

The reason code and the action are summarized in the table below.

(S)

Continues processing.

(O)

Take the corrective action described for the applicable reason code in the table below.

Action

Take the corrective action suggested for the applicable reason code in the following table.

Reason code Meaning Operator action Embedded DB system administrator action

205 The disk is full. None Make sure there is sufficient free disk space.

209 An input/output error occurred. Read the message displayed before or after this message, identify the cause of the error, and take corrective action. If the corresponding system log file is included again as a candidate for expansion, you need to reconfigure the embedded database environment.

1691 The size of an added system log file has exceeded the limit on file size. None None

1692 The size of the system log file has reached the limit on file size. None None

KFPS01391-W
Sys(aa....aa) log files expansion bb....bb[, output file name=cc....cc] (L)

Expansion of the system log file has started or ended. The [, output file name=cc....cc] part is output when expansion starts.

aa....aa: Maintenance information

bb....bb: Processing description

start: Processing started

complete: Processing ended

cc....cc: Maintenance information

(S)

Continues processing.

Action

If the automatic log unloading function has stopped, remove the cause (such as a full disk) and try to start the function again.

Use the ajsembdbaddlog command to add the system log file.

For an operation targeting a large number of units, consider distributing the load (for example, split the operation into several smaller operations).

KFPS01801-E
Unable to start HiRDB unit due to improper operational environment. reason code=aa....aa (E)

The embedded database cannot be started because the operation environment is not ready.

aa....aa: Reason code

(S)

Cancels startup of the embedded database.

Action

Take the appropriate action shown in the following table, and then start the embedded database.

Reason code Cause Action

MEMORY Process-specific memory or shared memory is insufficient. See the descriptions of SHM_EINVAL, SHM_ENOMEM, and SHM_ENOSPC.

PAUSE An error that prevents further processing of the embedded database occurred. See other messages output to the command input window, Windows event log, or syslog.

PROGRAM A prerequisite product was not found. Install the prerequisite product.

SETUP The embedded database is not registered in the OS. In Windows, the embedded database service has stopped. In UNIX, use the ajsembdbbuild command to register the embedded database in the OS. In Windows, start the embedded database service.

SHM_EINTR A signal was received during processing to allocate shared memory. Determine the cause of the signal and take corrective action, and then restart the embedded database.

SHM_EINVAL The shared memory size exceeded the maximum for the system. In Windows, the work file for shared memory cannot be allocated due to insufficient space on the installation drive. Increase the maximum size of the shared memory segment for the system. In Windows, allocate free space greater than the shared memory size on the installation drive.

SHM_EMFILE The number of open files exceeded the maximum for the system. Reduce the number of the open files, or increase the number of files that can be opened in the system.

SHM_ENOMEM Memory for the shared memory size was not found in the system. Increase the amount of real memory in the system.
If the message KFPO00107-E or KFPO00113-E was output before or after this message, also check that message.

SHM_ENOSPC In UNIX, the number of shared memory IDs exceeded the maximum defined in the system. In Windows, the installation drive does not have sufficient free space required for allocating the required size of shared memory. In UNIX, reduce the number of shared memory segments, or increase the maximum number of shared memory IDs.
In Windows, if the message KFPO00107-E or KFPO00113-E was output before or after this message, also check that message.

SHM_EOVER An internal contradiction occurred. Contact system administrator.

SHM_CALC*** An internal contradiction occurred. *** is any character string (maintenance information). Contact system administrator.

KFPS01819-I
Server aa....aa failed information. process ID=bb....bb, C-PID=cc....cc(dd....dd), TIME=eeffgg, PROGRAM=hh....hh (L)

This message contains maintenance information for the embedded database.

aa....aa: Maintenance information

bb....bb: Maintenance information

cc....cc: Maintenance information

dd....dd: Maintenance information

eeffgg: Maintenance information

hh....hh: Maintenance information

(S)

Continues processing.

KFPS01820-E
Server aa....aa failed. process ID=bb....bb, service group name=cc....cc, run mode=dd....dd, critical state=e,critical mask=ff....ff, end state=gg....gg, server type=hhh (E+L)

The server aa....aa has stopped. The following status is detected.

Value of gg....gg Description

007f
0009 The system accepted a request for forced termination of the server process. This message appears when the ajsembdbcancel command is executed. Determine the cause of the forced termination request for the process (including execution of the ajsembdbcancel command) based on the message output before or after this message, and then take action as required.

0003
0083 The system accepted a request of forced termination of the server process. Determine the cause of the forced termination request for the process based on the status of the executed transaction and the message output before or after this message, and then take action as required.

0006
0086
0100
0800 The embedded database process terminated abnormally because an error was detected during processing.
Determine the cause of the abnormal termination based on the message output before or after this message, and then take action as required.

8000 An attempt to start a process failed or a process terminated abnormally due to insufficient memory. Take one of the following actions:

Reduce the number of processes running on the same server host.

Increase the swap area.

Add real memory.

In Windows, check the specified value of the desktop heap.

c000 A connect system call was issued, but connection was not established because the connection destination had gone down or because a network failure occurred.

c100 The second or later SQL response could not be sent because the connection destination had gone down or because a network failure occurred.

c200 A timeout of the embedded database client was detected during a transaction when the embedded database client had control.

c300 The remote communication socket was closed because an error occurred in the destination during communication processing.

c400 A timeout of the client was detected when the client had control and a transaction was not in progress. Alternatively, a timeout related to pd_watch_pc_client_time specified in the embedded database system was detected during connection of a Windows embedded database client.

c500 A special file (FIFO) could not be obtained when the server was started.

c600 The maximum number of transactions that can be processed concurrently on the embedded database was exceeded. Since many rollbacks might have occurred, wait for completion of the rollbacks and then re-execute the UAP.

c700 Abnormal termination was detected on the client requesting SQL (JP1/AJS3 scheduler service process) during execution of SQL on the embedded database.

c800 An attempt to send an SQL request has failed because a network failure occurred between the server and the system manager.

c900 An attempt to receive a second or later SQL request has failed because a network failure occurred between the sender and the system manager.

d000 The child process was killed because the parent process was killed during transaction processing.

d100 Server processing was canceled because the UAP processing did not terminate within the monitoring period specified in PDSWAITTIME and PDSWATCHTIME in the client environment definitions. Alternatively, the related server processing was canceled because the pdcancel command was executed.

d300 Although an error was detected, the system terminated processing without outputting troubleshooting information because the specification of the pd_dump_suppress_watch_time operand was valid.

d500 An error occurred during determination of a transaction.

000f
ff00 The server process of the embedded database was forcibly terminated by the OS kill command.

008b An OS stack overflow may have occurred while the embedded database was running. The following are the actions to be taken for the causes of the stack overflow.
Cause 1
The probable cause is:

A user-defined routine that performs many calls or enters an infinite loop was executed.

Action

Check the value of the maxssiz kernel parameter, and then increase the stack size.

Cause 2
An attempt to expand the stack failed due to insufficient OS memory.
Action
Terminate unnecessary programs to increase the amount of free space in memory.

aa....aa: Name of the stopped server

bb....bb: Process ID of the stopped server

cc....cc: Service group name of the stopped server

dd....dd: Run mode of the server immediately before it stopped

PDBSV: Embedded database server

PDBSYS: Embedded database being processed

e:

N: Not a critical state

Y: Critical state

Since information on the embedded database is shared by multiple processes, the management table in the shared memory is referenced or updated. If a process that is updating the shared memory terminates abnormally, table information becomes inconsistent, disabling subsequent processing, which includes processing by other processes. As much as possible, the system prevents a forced termination from occurring in this processing period (called the critical period). If the system cannot prevent a forced termination in the critical period due to a failure, the embedded database terminates, and the integrity of the table information will be recovered when the embedded database is restarted.

ff....ff: Critical information

gg....gg: End status of the process returned by wait(2) (**** is displayed for an embedded database command.)

hhh: Server type (*** is displayed for a server other than an embedded database server)

(S)

Terminates processing on the server on which an error occurred, and then restarts the server if necessary.

Action

Determine the cause of the server stop according to the message output before this message or from the troubleshooting information (dump or trace), and then take action. If necessary, restart the server. Note that troubleshooting information is not output when gg....gg is c000, c100, c200, c300, c400, c500, c600, c700, c800, c900, d000, d100, d200, d300, or d500.

KFPS01826-I
HiRDB dir = aa....aaHiRDB vrs = bb....bbunit run ID = cc....ccHiRDB ID = ddddunit ID = eeee (L)

This message shows the environment of the embedded database.

aa....aa: Embedded database practical directory name

bb....bb: Embedded database version

cc....cc: Maintenance information

dddd: Maintenance information

eeee: Maintenance information

(S)

Continues processing.

KFPS01829-E
aa....aa invalid; stops unit startup (E)

The contents of aa....aa were changed without a normal stopping of the embedded database.

aa....aa: Contents of the change

System Version: Embedded database version

(S)

Cancels startup of the embedded database.

Action

Restore the embedded database to its old version, restart the embedded database, and then terminate it normally. Next, change the version of the embedded database and then restart the embedded database.

KFPS01851-E
Server aa....aa initialization error occurred; return code=bb....bb (E+L)

An initialization error occurred during startup of the embedded database.

aa....aa: Maintenance information

bb....bb: Maintenance information

(S)

The embedded database is abnormally terminated.

Action

Restart the embedded database. If this message still appears after the embedded database is restarted, contact system administrator.

KFPS04619-E
Unable to execute aa....aa command due to HiRDB unit not offline or not terminate normally (S+R)

The aa....aa command cannot be executed because the embedded database has not stopped.

aa....aa: Command name

(S)

Terminates processing.

Action

The embedded database might have been running (including start and end processing when the command was executed). This command cannot be executed if the database is running.

If the embedded database is running, use the ajsembdbstop command to perform a normal termination and then retry the operation. If the embedded database is not running, first start the embedded database, use the ajsembdbstop command to perform a normal termination, and then retry the operation.

Cautions applying only to the UNIX version

The ajsembdbunset command cannot be entered if the embedded database has terminated abnormally or if it has been forcibly terminated by the ajsembdbstop -f command.

KFPS05120-W
Waiting for UAP and/or utility disconnect in HiRDB unit aaaa, current connect user count = bbb (L)
The system is waiting for termination of the UAP or a utility.

aaaa: Unit ID for waiting for termination

bbb: Number of connected users who are waiting for termination

(S)

Continues processing. A new user cannot connect to the embedded database. Termination processing of the embedded database is delayed (15 minutes) until the UAP or utility processing terminates. When the UAP or utility processing terminates, the embedded database termination processing starts.

The system outputs detailed information about the user connected to the embedded database to the connected user information file (embedded-database-practical-directory/spool/cnctusrinf or embedded-database-practical-directory\spool\cnctusrinf). The system outputs the execution results of commands to the connected user details file (embedded-database-practical-directory/spool/cnctusrdtl or embedded-database-practical-directory\spool\cnctusrdtl).

If the UAP or utility stops before or after this message is output, the above information may not be included in the detail information for the user connected to the embedded database.
(O)

Check the connected user based on the connected user information file (embedded-database-practical-directory/spool/cnctusrinf or embedded-database-practical-directory\spool\cnctusrinf) and take action. If you cannot determine the connected user, use information output to the connected user details file (embedded-database-practical-directory/spool/cnctusrdtl or embedded-database-practical-directory\spool\cnctusrdtl) to check the connected user, and then take action.

The following shows an output example of the connected user information file.

Output example:
UNIT ID : M350(173420)
UID  PID    GID  SVID  TIME   PROGRAM
C-GRP  C-PID  C-IP
334  22118  300  fes1  173330 uap00
WS     22205  172.17.32.37
UNIT ID:

Indicates the unit ID and the time when the cnctusrinf file was created (hour, minute, and second).

UID:

Indicates the user ID of the user currently connected to the embedded database.

PID:

Indicates the process ID of the user currently connected to the embedded database.

GID:

Indicates the group ID of the user currently connected to the embedded database.

SVID:

Indicates the name of the server to which the user is connected.

Nothing might be displayed immediately after the server process of the embedded database has started.

TIME:

Indicates the time when the embedded database accepted the service request (hour, minute, and second). For a server to which the user is not connected, 999999 is displayed.

PROGRAM:

Indicates the connection process name.

The name of a JP1/AJS3 command or process is output using 30 or fewer characters. If a command for the embedded database is executed, a name other than the name of the executed command may be displayed.

****** may be displayed immediately after the server process of the embedded database has started.

C-GRP:

Always blank.

C-PID:

Indicates the process ID of the client.

C-IP:

Indicates the IP address of the client.

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. embedded-database-practical-directory\uxpldir\spool\system\filmng.dat embedded-database-practical-directory\uxpldir\spool\system\flg.dat embedded-database-practical-directory\uxpldir\spool\system\shmmng.dat embedded-database-practical-directory\spool\~pdatmode embedded-database-practical-directory\spool\~pdipcid embedded-database-practical-directory\spool\oslmqid embedded-database-practical-directory\spool\oslsmid embedded-database-practical-directory\spool\pdprcsts embedded-database-practical-directory\spool\scdqid1 embedded-database-practical-directory\spool\scdqid2 embedded-database-practical-directory\tmp\pdommenv All files under embedded-database-practical-directory\uxpldir\spool\shm embedded-database-practical-directory\uxpldir\spool\system\semmng.dat 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 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

Cause of the error	Action
The error was detected in the embedded database file system.	Correct the error by referring to C. Error Codes Returned from Access Requests for an Embedded Database File System, and then retry the operation.
The error was not detected in a function.	Correct the error indicated by aa....aa, and then retry the operation.
The OS detected the error.	Correct the error by referring to the OS documentation, and then retry the operation.

Error code	Cause
-1556	After the embedded database file exceeded the initial allocation size, an attempt to expand the file using the secondary allocation size failed. An attempt was made to expand the file beyond the limit on the number of times the embedded database file system area can be increased. An attempt was made to expand the embedded database file more than the maximum number of times, which is 23.
-1562	The type of the embedded database file system area is not UTL.

Reason code	Cause	Action
0000000006	The file was not found.	Make sure that the system file exists in the directory that was specified when the environment of the embedded database was created.
0000000020	You do not have access permissions.	Make sure that you have permission to access the directory that was specified when the environment of the embedded database was created and the created system files.
0000000021	You do not have access permissions.	Make sure that you have permission to access the directory that was specified when the environment of the embedded database was created and the created system files.
0000000022	A lock error (the target is being used by another process) occurred.	Wait a while and then retry the operation. For a cluster system, check whether both the primary node and secondary node access a system file on the shared disk.
0000000023	System resources (file lock) are insufficient.	Check the system parameters for the OS.
0000000024	You do not have access permissions.	Make sure that you have permission to access the directory that was specified when the environment of the embedded database was created and the created system files.
0000000025	System resources (file descriptors) are insufficient.	Check the system parameters for the OS.
0000000026	The file was not found.	Make sure that the system file exists in the directory that was specified when the environment of the embedded database was created.
0000000027	An I/O error occurred.	Check whether a disk error or other OS-related error occurred. Also check whether you can access the directory that was specified when the environment of the embedded database was created.
0000000028	A memory shortage occurred.	Check the system parameters for the OS.
0000000029	The file was not found.	Make sure that a system file exists in the directory that was specified when the environment of the embedded database was created.
0000000030	In UNIX, the number of open character type special files exceeds the limit. In Windows, the number of open files exceeds the limit.	Check the system parameters for the OS.
0000000031	The file name is invalid.	The probable causes are: An invalid character is specified in the file name. The length of the file name exceeds the limit. Check the directory name that was specified when the environment of the embedded database was created.
0000000037	The file was not found.	Make sure that the system file exists in the directory that was specified when the environment of the embedded database was created.

Reason code	Meaning	Action to be taken by the embedded database system administrator
101	A memory shortage occurred.	Re-estimate memory.
201	The file name is invalid.	The probable causes are: An invalid character is specified in the file name. The length of the file name exceeds the limit. Specify the file name correctly, and then re-execute the command.
202	The specified file name is not a RAW file. Alternatively, the device for this file was not found.	Check the settings specified when the environment of the embedded database was created.
203	The embedded database system file was not found.
207	The number of open files exceeded the limit.	Check the system parameters for the OS.
208	You do not have access permissions.	Make sure that you have permission to access the directory that was specified when the environment of the embedded database was created and the created system files.
209	An I/O error occurred.	Check whether a disk error or other OS-related error occurred. Also check whether you can access the directory that was specified when the environment of the embedded database was created.
210	The embedded database system file is inconsistent.	Re-create the environment of the embedded database. If the error persists after re-creating the environment, contact system administrator.
211	You do not have access permissions.	Make sure that you have permission to access the directory that was specified when the environment of the embedded database was created and the created system files.
212	The file was not found.	Make sure that the system file exists in the directory that was specified when the environment of the embedded database was created.
218 219	The specified file cannot be used as a log file.	Use another file. If a new file is required, use the ajsembdbaddlog command to add the new file.
220	The specified file is not a log file.	Check the settings specified when the environment of the embedded database was created.
221	Lock segments are insufficient.	Check the system parameters for the OS.
222	A lock error (the target is being used by another process) occurred.	Wait a while and then retry the operation. For a cluster system, check whether both the primary node and secondary node access a system file on the shared disk.

Reason code	Meaning	Operator action	Action by the embedded database system administrator
101	A memory shortage occurred.	Wait until the currently running process terminates, and then re-execute the command.	Re-estimate memory.
201	The file name is invalid.	Probable causes are: An invalid character is specified in the path name. The length of the embedded database file name exceeded the limit (30 characters). Specify the file name correctly, and then re-execute the command	--
202	The name of the embedded database file system area for the specified path is not an embedded database file system area.	Check the name of the embedded database file system area for the specified path, and then re-execute the command	Check the file specification in the pdlogadpf operand.
203	The specified path device is not initialized for the embedded database file system.	--
207	The upper limit was exceeded when the embedded database file system area for the specified path was opened.	--
208	You do not have permission to access the embedded database file system area for the specified path.	Check access permissions for the embedded database file.	Check the file specification in the pdlogadpf operand.
209	An I/O error occurred.	Determine the cause of the I/O error, and take action.	--
210	The version of the embedded database file system is inconsistent.	--	Check the file specification in the pdlogadpf operand.
211	You do not have permission to access the specified file.	Check the access permission for the log.	--
212	The specified file is not found.	--	Check the file specification in the pdlogadpf operand.
221	Lock segments are insufficient.	Check the number of record lock segments that is specified when the OS is started.
222	The system log file is being used by another process.	Check the operation status of the system log file or its file group, and then re-execute the command.	--
603	Management information on the file is corrupted.	Initialize this file.
605	The file structure of the file differs from the current file structure. The file structure might have been changed.	Contact the embedded database system administrator to find out if the file structure has been changed. If the file structure has not been changed, initialize this file.	Check the definition to make sure that the file group that uses the file and the system log file have not been changed. If the file structure has been changed, return the file structure in the definition to its original state.
1607	The file has not been used in the embedded database.	Check the file group.	--

Reason code	Meaning	Operator action	Embedded DB system administrator action
205	The disk is full.	None	Make sure there is sufficient free disk space.
209	An input/output error occurred.	Read the message displayed before or after this message, identify the cause of the error, and take corrective action.	If the corresponding system log file is included again as a candidate for expansion, you need to reconfigure the embedded database environment.
1691	The size of an added system log file has exceeded the limit on file size.	None	None
1692	The size of the system log file has reached the limit on file size.	None	None

Reason code	Cause	Action
MEMORY	Process-specific memory or shared memory is insufficient.	See the descriptions of SHM_EINVAL, SHM_ENOMEM, and SHM_ENOSPC.
PAUSE	An error that prevents further processing of the embedded database occurred.	See other messages output to the command input window, Windows event log, or syslog.
PROGRAM	A prerequisite product was not found.	Install the prerequisite product.
SETUP	The embedded database is not registered in the OS. In Windows, the embedded database service has stopped.	In UNIX, use the ajsembdbbuild command to register the embedded database in the OS. In Windows, start the embedded database service.
SHM_EINTR	A signal was received during processing to allocate shared memory.	Determine the cause of the signal and take corrective action, and then restart the embedded database.
SHM_EINVAL	The shared memory size exceeded the maximum for the system. In Windows, the work file for shared memory cannot be allocated due to insufficient space on the installation drive.	Increase the maximum size of the shared memory segment for the system. In Windows, allocate free space greater than the shared memory size on the installation drive.
SHM_EMFILE	The number of open files exceeded the maximum for the system.	Reduce the number of the open files, or increase the number of files that can be opened in the system.
SHM_ENOMEM	Memory for the shared memory size was not found in the system.	Increase the amount of real memory in the system. If the message KFPO00107-E or KFPO00113-E was output before or after this message, also check that message.
SHM_ENOSPC	In UNIX, the number of shared memory IDs exceeded the maximum defined in the system. In Windows, the installation drive does not have sufficient free space required for allocating the required size of shared memory.	In UNIX, reduce the number of shared memory segments, or increase the maximum number of shared memory IDs. In Windows, if the message KFPO00107-E or KFPO00113-E was output before or after this message, also check that message.
SHM_EOVER	An internal contradiction occurred.	Contact system administrator.
SHM_CALC***	An internal contradiction occurred. *** is any character string (maintenance information).	Contact system administrator.

Value of gg....gg	Description
007f 0009	The system accepted a request for forced termination of the server process. This message appears when the ajsembdbcancel command is executed. Determine the cause of the forced termination request for the process (including execution of the ajsembdbcancel command) based on the message output before or after this message, and then take action as required.
0003 0083	The system accepted a request of forced termination of the server process. Determine the cause of the forced termination request for the process based on the status of the executed transaction and the message output before or after this message, and then take action as required.
0006 0086 0100 0800	The embedded database process terminated abnormally because an error was detected during processing. Determine the cause of the abnormal termination based on the message output before or after this message, and then take action as required.
8000	An attempt to start a process failed or a process terminated abnormally due to insufficient memory. Take one of the following actions: Reduce the number of processes running on the same server host. Increase the swap area. Add real memory. In Windows, check the specified value of the desktop heap.
c000	A connect system call was issued, but connection was not established because the connection destination had gone down or because a network failure occurred.
c100	The second or later SQL response could not be sent because the connection destination had gone down or because a network failure occurred.
c200	A timeout of the embedded database client was detected during a transaction when the embedded database client had control.
c300	The remote communication socket was closed because an error occurred in the destination during communication processing.
c400	A timeout of the client was detected when the client had control and a transaction was not in progress. Alternatively, a timeout related to pd_watch_pc_client_time specified in the embedded database system was detected during connection of a Windows embedded database client.
c500	A special file (FIFO) could not be obtained when the server was started.
c600	The maximum number of transactions that can be processed concurrently on the embedded database was exceeded. Since many rollbacks might have occurred, wait for completion of the rollbacks and then re-execute the UAP.
c700	Abnormal termination was detected on the client requesting SQL (JP1/AJS3 scheduler service process) during execution of SQL on the embedded database.
c800	An attempt to send an SQL request has failed because a network failure occurred between the server and the system manager.
c900	An attempt to receive a second or later SQL request has failed because a network failure occurred between the sender and the system manager.
d000	The child process was killed because the parent process was killed during transaction processing.
d100	Server processing was canceled because the UAP processing did not terminate within the monitoring period specified in PDSWAITTIME and PDSWATCHTIME in the client environment definitions. Alternatively, the related server processing was canceled because the pdcancel command was executed.
d300	Although an error was detected, the system terminated processing without outputting troubleshooting information because the specification of the pd_dump_suppress_watch_time operand was valid.
d500	An error occurred during determination of a transaction.
000f ff00	The server process of the embedded database was forcibly terminated by the OS kill command.
008b	An OS stack overflow may have occurred while the embedded database was running. The following are the actions to be taken for the causes of the stack overflow. Cause 1 The probable cause is: A user-defined routine that performs many calls or enters an infinite loop was executed. Action Check the value of the maxssiz kernel parameter, and then increase the stack size. Cause 2 An attempt to expand the stack failed due to insufficient OS memory. Action Terminate unnecessary programs to increase the amount of free space in memory.

[Contents][Back][Next]

[Trademarks]