KAVS0932-E

An error occurred while accessing the database.

(S)

Terminates processing.

(O)

The probable causes are as follows. Take action according to the cause of the error. If an error message was output before or after this message, also see the instructions given by that message.

Cause 1

Database files were corrupted due to a disk error, CPU error, or other hardware error.

Action

Reorganize the scheduler database or job execution environment database . If the reorganization does not correct the error, you must re-create the database.

For details about reorganizing ISAM files, see 9.3 Reorganizing a database when QUEUE jobs and submit jobs are used in the JP1/Automatic Job Management System 3 Administration Guide.

For details about re-creating ISAM files, see 2.11 Troubleshooting problems related to invalid ISAM files in the manual JP1/Automatic Job Management System 3 Troubleshooting.

Cause 2

Database files were corrupted because the primary node and secondary node in a cluster configuration accessed the database at the same time.

Action

Same as for Cause 1.

Cause 3

When an embedded database is used as the scheduler database, the embedded database has already stopped by the time the JP1/AJS3 service stopped.

Action

If the JP1/AJS3 service has stopped, there is no problem caused by this error. Do not stop the embedded database first.

Cause 4

When ISAM is used for the scheduler database in a cluster configuration, because sync was not specified for the ISAMWRITEMODE environment setting parameter for the scheduler service, the status of ISAM files becomes inconsistent during failover.

Action

Reorganize the scheduler database. If the reorganization does not correct the error, you must re-create the database.

Cause 5

Database files were corrupted because a disk operation was performed during JP1/AJS3 operation.

Action

Same as for Cause 1.

Cause 6

The file sizes that can be handled on the OS are restricted.

Action

Check the estimated file size in the kernel parameter, and set the appropriate value. For details about estimating the kernel parameters, see Release Notes.

Cause 7

The size of the ISAM file used for the scheduler database or job execution environment database reached 2 GB.

Action

Decrease the size of the ISAM file according to 9.3 Notes on the JP1/AJS3 database in the JP1/Automatic Job Management System 3 System Design (Configuration) Guide.

Cause 8

Database files were corrupted because the OS was stopped unexpectedly due to power interruption while JP1/AJS3 was running or for any other reason.

Action

Same as for Cause 1.

Cause 9

If an access from JP1/AJS3 - View causes an error, the OS user who is mapped to the JP1 user who logs in to JP1/AJS3 - View does not have update permission for the scheduler database.

Action

Check permission for accessing the scheduler database directory and scheduler database files, and set the access permissions appropriately.

Cause 10

If an embedded database is used for the scheduler database, the embedded database is not running.

Action

Start the embedded database, and then restart the scheduler service that is using the embedded database as the scheduler database.

Cause 11

When an unexpected failover occurs in a cluster configuration due to OS power failure or OS error, the status of ISAM files becomes inconsistent.

Action

Same as for Cause 1.

Cause 12

The embedded database was disconnected during operation of JP1/AJS3.

Action

If the KNAC1520-I message was output immediately after this message, there is no problem despite the reported error. If the ajsagtadd, ajsagtalt, or ajsagtdel command terminated abnormally, make sure that the embedded database is running, and then re-execute the command. If a job terminated abnormally when the agent automatic definition function was being used, make sure that the embedded database is running, and then re-execute the job.

Cause 13

A database access error occurred in an environment where an external database is used.

Action

For details about how to take action, see 2.15 Troubleshooting problems related to the external database in the manual JP1/Automatic Job Management System 3 Troubleshooting.