AWKJDB - Common objects messages

This section lists error and warning messages that might be generated by the routines that handle common objects.

The message component code is JDB.

AWKJDB101E

The specified object was not found.

See message text.

The operation cannot be performed. The program continues.

Check that you have correctly specified the object. If you have, check that the object has not been deleted from the database. If you cannot resolve the problem, search the HCL Support database for a solution at https://hclpnpsupport.hcltech.com/csm.

AWKJDB102E

The specified global option was not found.

The global option is not found in the database. You might have wrongly specified the name or the option might have been deleted from the database.

The operation cannot be performed. The program continues.

Ensure that the global option name you specified is correct and that the option has not been deleted from the database. You can request a list of the global options using the command optman ls. If you cannot resolve the problem, search the HCL Support database for a solution at https://hclpnpsupport.hcltech.com/csm.

The Installation and Configuration Guide for a full description of the options.

AWKJDB201E

The specified object cannot be locked, updated, or deleted because it is locked by user "user_name".

See message text.

The operation cannot be performed. The program continues.

Retry the operation and if the object is still locked, contact the user indicated in the message. Retry the operation when the object is unlocked.

AWKJDB202E

The object cannot be unlocked or updated because it is not locked.

See message text.

The operation cannot be performed. The program continues.

Ensure that you have specified the correct object. Check the status of the object in the database. If the object is not locked, lock it before retrying the operation.

AWKJDB203E

The object cannot be unlocked or updated because it was not locked by you. you are logged on as user "user1_name"). The object is locked by user "user2_name".

See message text.

The operation cannot be performed. The program continues.

Ensure that you have specified the correct object and that you are the identified user. Make any required corrections and retry the operation. If this is the correct object and it is locked by another user, contact the user to unlock it and them retry the operation.

AWKJDB204E

The object cannot be unlocked or updated because it is locked by you, logged on as "user_name" in another session.

If you lock an object in one session, you can only update or unlock it in that same session. A session is an instance of any of the following:

  • The Dynamic Workload Console
  • The command line
  • A GUI or command line developed by your own organization

Each time you open one of these instances, whether on the same or a different computer, it is treated as a separate session.

The operation cannot be performed. The program continues.

Check that you have specified the correct object and that you are the identified user and if so do the following:

  • If you have used a second session by accident, return to the first session to continue
  • If you have been forced to use a new session for some reason, use the force option to unlock the object and then restart the operation you intended to perform.

If you use the force option in a second session when the first session is still open, trying to edit the object in the first session will cause this message to be displayed again.

This message could appear in many circumstances. Here are two example scenarios:

A second session is opened by accident

  1. You open a command line session on your computer and lock an object for editing.
  2. Something distracts you and when you return to the work you were doing you forget that you had already started and open another command line session.
  3. When you try to lock the object for editing this message is given.
  4. Check to see if you have any other sessions open. When you find the original session, close the second session.
  5. Continue working in the first session, editing and then unlocking the object.

A session fails

  1. You open a Dynamic Workload Console session on your computer and lock an object for editing.
  2. Your computer crashes (for some reason unconnected with HCL Workload Automation), and needs to be rebooted.
  3. After restarting, you open a new Dynamic Workload Console session and try to continue editing the object. This message is displayed.
  4. Unlock the object using the force option.
  5. Lock the object, edit it, and then unlock it.

AWKJDB205E

An error occurred when trying to lock multiple objects because at least one of the selected objects is already locked.

You might attempt to lock multiple objects when they have been selected as the result of a wildcard search.

All objects that could be locked have been locked. Objects that were already locked are not modified. The program continues.

Complete the following steps:

  1. View the details of the objects you want to lock.
  2. Check their status and find out which ones are already locked.
  3. Contact the user who has locked them to have them unlocked.
  4. Retry the operation.

AWKJDB206E

An error occurred when trying to unlock multiple objects because at least one of the selected objects was not locked by you ("user_name").

You might attempt to unlock multiple objects when they have been selected as the result of a wildcard search.

All objects that could be unlocked have been unlocked. Objects that were locked by a different user are not modified. The program continues.

Complete the following steps:

  1. View the details of the objects you want to unlock.
  2. Check their status and find out which ones are locked by another user.
  3. Contact the user that has locked them to have them unlocked.

AWKJDB207E

An error occurred when trying to unlock multiple objects because at least one of the selected objects was locked by you ("user_name"), in another session.

If you lock an object in one session, you can only update or unlock it in that same session. A session is an instance of any of the following:

  • The Dynamic Workload Console
  • The command line
  • A GUI or command line developed by your own organization

Each time you open one of these instances, whether on the same or a different computer, it is treated as a separate session.

All objects that could be unlocked have been unlocked. Objects that were locked in a different session are not modified. The program continues.

Check that you have specified the correct object and that you are the identified user and if so do the following:

  • If you have used a second session by accident, return to the first session to continue
  • If you have been forced to use a new session for some reason, use the force option to unlock the object and then restart the operation you intended to perform.

If you use the force option in a second session when the first session is still open, trying to edit the object in the first session will cause this message to be displayed again.

This message could appear in many circumstances. Here are two example scenarios:

A second session is opened by accident

  1. You open a command line session on your computer and lock an object for editing.
  2. Something distracts you and when you return to the work you were doing you forget that you had already started and open another command line session.
  3. When you try to lock the object for editing this message is given.
  4. Check to see if you have any other sessions open. When you find the original session, close the second session.
  5. Continue working in the first session, editing and then unlocking the object.

A session fails

  1. You open a Dynamic Workload Console session on your computer and lock an object for editing.
  2. Your computer crashes (for some reason unconnected with HCL Workload Automation), and needs to be rebooted.
  3. After restarting, you open a new Dynamic Workload Console session and try to continue editing the object. This message is displayed.
  4. Unlock the object using the force option.
  5. Lock the object, edit it, and then unlock it.

If you use the force option in a second session when the first session is still open, if you return to the first session and try to edit the object you will receive this message again.

AWKJDB301E

Unused message.

AWKJDB401E

Unused message.

AWKJDB402E

An internal error occurred while reading or writing a UUID in the database, or while generating a UUID for a new object.

There is a problem in the algorithm that creates unique identifiers.

The identifier cannot be created. A database transaction might be rolled back. The program continues.

If you cannot resolve the problem, search the HCL Support database for a solution at https://hclpnpsupport.hcltech.com/csm.

AWKJDB403E

An internal error occurred. The operation "operation_name" cannot be performed because the Data Access Object (DAO) context state "context_state" is not correct.

See message text.

The operation cannot be performed. The program continues.

If you cannot resolve the problem, search the HCL Support database for a solution at https://hclpnpsupport.hcltech.com/csm.

AWKJDB404E

An internal error has occurred while parsing the Identifier. The internal error message is: "error".

See message text.

The identifier cannot be created. The program continues.

If you cannot resolve the problem, search the HCL Support database for a solution at https://hclpnpsupport.hcltech.com/csm.

AWKJDB501E

Unused message.

AWKJDB601E

An internal error occurred. A database integrity constraint has been violated. The internal error message is: "error".

The database write operation cannot be started because it violates an integrity constraint.

The write operation was not started. The database transaction is rolled back. The program continues.

If you cannot resolve the problem, search the HCL Support database for a solution at https://hclpnpsupport.hcltech.com/csm.

AWKJDB602E

An internal error occurred. A database not null constraint has been violated. The internal error message is: "error".

The database write operation cannot be started because it violates a not null constraint.

The write operation was not started. The database transaction is rolled back. The program continues.

If you cannot resolve the problem, search the HCL Support database for a solution at https://hclpnpsupport.hcltech.com/csm.

AWKJDB603E

An internal error occurred. A database check constraint has been violated. The internal error message is: "error".

The database write operation cannot be started because it violates a check constraint.

The write operation was not started. The database transaction is rolled back. The program continues.

If you cannot resolve the problem, search the HCL Support database for a solution at https://hclpnpsupport.hcltech.com/csm.

AWKJDB604E

An internal error occurred. A database unique constraint has been violated, the object already exists.

The database write operation cannot be started because it violates a unique constraint.

The write operation was not started. The database transaction is rolled back. The program continues.

If you cannot resolve the problem, search the HCL Support database for a solution at https://hclpnpsupport.hcltech.com/csm.

AWKJDB605E

An internal error occurred. A database foreign key constraint has been violated. The internal error message is: "error".

The database write operation cannot be started because it violates a foreign key constraint.

The write operation was not started. The database transaction is rolled back. The program continues.

If you cannot resolve the problem, search the HCL Support database for a solution at https://hclpnpsupport.hcltech.com/csm.

AWKJDB606E

An internal error occurred. A foreign key constraint prevents the remove operation. The internal error message is: "error".

The database remove operation cannot be started because it is restricted by a foreign key constraint.

error explains more about the error.

The remove operation was not started. The database transaction is rolled back. The program continues.

If you cannot resolve the problem, search the HCL Support database for a solution at https://hclpnpsupport.hcltech.com/csm.

AWKJDB607E

An internal error occurred. The value defined for a database field exceeds its column bounds. The internal error message is: "error".

The database write operation cannot be started because a value exceeds its column bounds.

The operation was not started. The database transaction is rolled back. The program continues.

If you cannot resolve the problem, search the HCL Support database for a solution at https://hclpnpsupport.hcltech.com/csm.

AWKJDB801E

An internal error has been found while accessing the database. The internal error message is: "error".

See message text.

The database cannot be accessed properly. The system attempts to roll back the current transaction. The program continues.

If you cannot resolve the problem, search the HCL Support database for a solution at https://hclpnpsupport.hcltech.com/csm.

AWKJDB802E

An internal error has occurred in the database connection. The internal error message is: "error".

See message text.

The database cannot be accessed properly. The system attempts to roll back the current transaction. The program continues.

If you cannot resolve the problem, search the HCL Support database for a solution at https://hclpnpsupport.hcltech.com/csm.

AWKJDB803E

An internal deadlock or timeout error has occurred while processing a database transaction. The internal error message is: "error".

See message text.

The system attempts to roll back the current transaction. The program continues.

On DB2 a message with code SQLERRMC: 68 identifies a time-out error. This can happen if an overhead occurred or the database server does not have sufficient resources. Check that the number of database connections is not too high with respect to the server capabilities. 16 MB of RAM are required for every 5 connections. You can lower the number of threads in the JobDispatcherConfig.properties file.

If the database is located on a server with insufficient memory, the required buffer pools might not have started correctly. This can cause unexpected behavior. To check the buffer pool status, enter the following command from the DB2 command line:

get snapshot for tablespaces on <tdwb-database_name>

where <tdwb-database_name> is the database name.

If the value of the Buffer pool ID currently in use is different from the value of Buffer pool ID next startup, the buffer pool has not started

In a DB2 8.2 installation, 512 MB are required for the Dynamic Workload Broker buffer pool.

If you cannot resolve the problem, search the HCL Support database for a solution at https://hclpnpsupport.hcltech.com/csm.

AWKJDB804E

The operation cannot be completed because a concurrent update has been detected. Completing the operation would lead to a database inconsistency.

See message text.

The write operation was not started. The database transaction is rolled back. The program continues.

If you cannot resolve the problem, search the HCL Support database for a solution at https://hclpnpsupport.hcltech.com/csm.

AWKJDB805E

The requested operation cannot be performed because the database is locked by the planner process.

Write operations are not allowed because the plan is being generated and the database is temporarily locked.

The write operation was not started. The database transaction is rolled back. The program continues.

Wait until the end of the plan generation process and retry the operation.