Hitachi

JP1 Version 12 JP1/Automatic Job Management System 3 Messages


KNAC1508-E

An error occurred while accessing the database.:maintenance-information-1:maintenance-information-2

An error occurred while the database was being accessed.

(S)

If the database was disconnected, the system reconnects the database.

However, if agent management is stopped, the system continues processing without reconnecting the database.

If reconnection is successful, the system outputs the KNAC1520-I message, and continues processing.

If reconnection fails, or for any reason other than above, the system cancels processing.

(O)

Check whether this message was output for the standby logical host in a cluster configuration when the JP1/AJS3 service was started. If it was output, the common definition information on the executing host might not have been set on the standby host after the database was set up.

Make sure that the common definition information on the logical host matches on both the executing and the standby hosts. If the information is inconsistent, set the common definition information residing on the executing host, on the standby host. For details, see 8.2.5 Changing the common definition information in the JP1/Automatic Job Management System 3 Configuration Guide (for hosts under Windows), or 17.2.5 Changing the common definition information in the JP1/Automatic Job Management System 3 Configuration Guide (for hosts under UNIX).

If this message is output when the ajsagtadd, ajsagtalt, or ajsagtdel command is executed, the database might have been disconnected.

If the KNAC1520-I message is output immediately after this message, no problem exists, despite the reported error.

If the command terminated abnormally, make sure that the database is running, and then re-execute the command. If this message is output when the agent automatic definition function is used to execute the job for an undefined execution agent, the database might have been disconnected. If the KNAC1520-I message is output immediately after this message, no problem exists, despite the reported error.

If a job terminated abnormally, make sure that the database is running, and then re-execute the job.

If this message is output when agent management stops, the database might have been disconnected. Because an update of the database has been completed, no problem exists, despite the reported error.

If the above does not apply, take corrective action according to a previously output message.

If a message was not output previously, collect data and then contact the system administrator.

For details about the data to be collected, see 1.3 Data to be collected when a problem occurs in the manual JP1/Automatic Job Management System 3 Troubleshooting and 1.4 Collecting data for troubleshooting in the manual JP1/Automatic Job Management System 3 Troubleshooting.