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

AWSJDB101E

The object "object" was not found.

See message.

object identifies the object.

The operation cannot be performed. The program continues.

Check that you have specified the object correctly. 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.

AWSJDB102E

The global option "property" was not found.

See message.

property identifies the global option.

The operation cannot be performed. The program continues.

Check that you have specified the global option name correctly. If you have, check that the option has not been deleted from the database. You can see a list of the global options from the command line by 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 Planning and Installation Guide for a full description of the options.

AWSJDB201E

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

See message.

object identifies the object.

user_name identifies the user that has locked the object.

The operation cannot be performed. The program continues.

Retry the operation to see if the object is still locked (the lock might have been momentary). If the problem persists, contact the indicated user to have the object unlocked. When it is unlocked, retry the operation.

AWSJDB202E

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

See message.

object identifies the object.

The operation cannot be performed. The program continues.

Check that you have specified the object correctly. If you have, check the object's status in the database. If it is not locked, lock it and retry the operation.

AWSJDB203E

The object "object" cannot be unlocked or updated because it was not originally locked by you ("user1_name"), and is currently locked by user "user2_name".

See message.

object identifies the object.

user1_name identifies the user that has initiated the unlock or update operation.

user2_name identifies the user that has locked the object.

The operation cannot be performed. The program continues.

Check that you are the user identified in the message. Check that you have specified the object correctly. If either are not true, correct the error and retry the operation.

If you are the user and have specified the object correctly, check the object's status in the database. If it is locked by another user, contact the other user to have it unlocked. When it is unlocked retry the operation.

AWSJDB204E

The object "object" cannot be unlocked or updated because it is locked by you ("user_name"), but 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, is treated as a separate session.

This message is displayed when you commence operations on an object which was locked in a different session.

object identifies the object.

user_name identifies the user that has initiated the unlock or update operation.

The operation cannot be performed. The program continues.

Check that you are the user identified in the message. Check that you have specified the object correctly. If either are not true, correct the error and retry the operation.

If you are the user and have specified the object correctly, check the circumstances surrounding the update of this object.

  • 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 recommence the operation you originally intended to perform

There are many scenarios that cover the appearance of this message, but the following are two examples:

Scenario 1 - 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

Scenario 2 - 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. You get this message.
  4. Unlock the object using the force option
  5. Lock the object, edit it and unlock it afterwards.

Note that, 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 receive this message again.

AWSJDB205E

While trying to lock multiple objects (for example, as the result of the use of a wildcard in the selection criteria), at least one of the objects could not be locked, because it was already locked.

See message.

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

Follow this procedure:

  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 that has locked them to have them unlocked
  4. Retry the operation

AWSJDB206E

While trying to unlock multiple objects (for example, as the result of the use of a wildcard in the selection criteria), at least one of the objects could not be unlocked because it was not originally locked by you ("user_name").

See message.

user_name identifies the user that has initiated the unlock operation.

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

Follow this procedure:

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

AWSJDB207E

While trying to unlock multiple objects (for example, as the result of the use of a wildcard in the selection criteria), at least one of the objects could not be unlocked because it was locked by you ("user_name"), but 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, is treated as a separate session.

This message is displayed when you commence operations on an object which was locked in a different session.

user_name identifies the user that has initiated the unlock or update operation.

The operation cannot be performed. The program continues.

Check that you are the user identified in the message. Check that you have specified the object correctly. If either are not true, correct the error and retry the operation.

If you are the user and have specified the object correctly, check the circumstances surrounding the update of this object.

  • 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 recommence the operation you originally intended to perform

There are many scenarios that cover the appearance of this message, but the following are two examples:

Scenario 1 - 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

Scenario 2 - 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. You get this message.
  4. Unlock the object using the force option
  5. Lock the object, edit it and unlock it afterwards.

Note that, 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 receive this message again.

AWSJDB301E

Unused message.

AWSJDB302E

The job "job_key" referenced by object "object_key" does not exist.

See message.

object_key identifies the object that owns the unresolved reference.

job_key identifies the referenced job that does not exist.

The operation cannot be performed. The program continues.

Check the object specification. Correct it to refer to an existing job instance and retry the operation.

AWSJDB303E

The job definition "job_definition_key" referenced by object "object_key" does not exist.

See message.

object_key identifies the object that owns the unresolved reference.

job_definition_key identifies the referenced job definition that does not exist.

The operation cannot be performed. The program continues.

Check the object specification. Correct it to refer to an existing job definition and retry the operation.

AWSJDB304E

The job stream "job_stream_key" referenced by object "object_key" does not exist.

See message.

object_key identifies the object that owns the unresolved reference.

job_stream_key identifies the referenced job stream that does not exist.

The operation cannot be performed. The program continues.

Check the object specification. Correct it to refer to an existing job stream and retry the operation.

AWSJDB305E

The workstation "workstation_key" referenced by object "object_key" does not exist.

See message.

object_key identifies the object that owns the unresolved reference.

workstation_key identifies the referenced workstation that does not exist.

The operation cannot be performed. The program continues.

Check the object specification. Correct it to refer to an existing workstation and retry the operation.

AWSJDB306E

The workstation class "workstation_class_key" referenced by object "object_key" does not exist.

See message.

object_key identifies the object that owns the unresolved reference.

workstation_class_key identifies the referenced workstation class that does not exist.

The operation cannot be performed. The program continues.

Check the object specification. Correct it to refer to an existing workstation class and retry the operation.

AWSJDB307E

The workstation or workstation class "workstation_or_workstation_class_key" referenced by object "object_key" does not exist.

See message.

object_key identifies the object that owns the unresolved reference.

workstation_or_workstation_class_key identifies the referenced workstation or workstation class that does not exist.

The operation cannot be performed. The program continues.

Check the object specification. Correct it to refer to an existing workstation or workstation class and retry the operation.

AWSJDB308E

The calendar "calendar_key" referenced by object "object_key" does not exist.

See message.

object_key identifies the object that owns the unresolved reference.

calendar_key identifies the referenced calendar that does not exist.

The operation cannot be performed. The program continues.

Check the object specification. Correct it to refer to an existing calendar and retry the operation.

AWSJDB309E

The domain "domain_key" referenced by object "object_key" does not exist.

See message.

object_key identifies the object that owns the unresolved reference.

domain_key identifies the referenced domain that does not exist.

The operation cannot be performed. The program continues.

Check the object specification. Correct it to refer to an existing domain and retry the operation.

AWSJDB310E

The resource "resource_key" referenced by object "object_key" does not exist.

See message.

object_key identifies the object that owns the unresolved reference.

resource_key identifies the referenced resource that does not exist.

The operation cannot be performed. The program continues.

Check the object specification. Correct it to refer to an existing resource and retry the operation.

AWSJDB311E

The prompt "prompt_key" referenced by object "object_key" does not exist.

See message.

object_key identifies the object that owns the unresolved reference.

prompt_key identifies the referenced prompt that does not exist.

The operation cannot be performed. The program continues.

Check the object specification. Correct it to refer to an existing prompt and retry the operation.

AWSJDB312E

A master domain manager cannot be created, it must be installed as such.

See message.

The operation cannot be performed. The program continues.

A master domain manager cannot be created. You must use the installation process to install a master domain manager or to promote an appropriate existing workstation.

AWSJDB313E

A master domain cannot be modified to become a lower level domain.

You can change the name of a master domain, but you cannot remove it from its role as master.

The operation cannot be performed. The program continues.

The operation you wanted to perform is not allowed. Examine the existing domain structure and the required domain structure, and plan any changes so that the master always remains the master. For example, if you want the master (A) to have the name of an existing lower domain (B), you must first rename that lower domain to something else (C) and then rename the master domain to the old name of the lower domain (B).

AWSJDB314E

A lower level domain cannot be modified to become the master domain.

Domains cannot be promoted to become the master.

The operation cannot be performed. The program continues.

The operation you wanted to perform is not allowed. Examine the existing domain structure and the required domain structure, and plan any changes so that the master always remains the master. For example, if you want the master (A) to have the name of an existing lower domain (B), you must first rename that lower domain to something else (C) and then rename the master domain to the old name of the lower domain (B).

AWSJDB315E

The master domain cannot be deleted.

See message.

The operation cannot be performed. The program continues.

You cannot remove the master domain. Examine the existing domain structure and the required domain structure, and plan any changes so that the master always remains the master. For example, if you want the master (A) to have the name of an existing lower domain (B), you must first rename that lower domain to something else (C) and then rename the master domain to the old name of the lower domain (B).

AWSJDB316E

The supplied job stream definition contains a duplicate run cycle name: "run_cycle_name".

See message.

run_cycle_name is the run cycle name that is duplicated in the job stream.

The operation cannot be performed. The program continues.

Check the job stream specification. Correct the run cycle information, ensuring that it does not contain duplicate run cycle names, and retry the operation.

AWSJDB317E

The supplied job stream definition contains a duplicate job name: "job_name".

See message.

job_name is the job name that is duplicated in the job stream.

The operation cannot be performed. The program continues.

Check the job stream specification. Correct the job information, ensuring that it does not contain duplicate job names, and retry the operation.

AWSJDB318E

A prompt with name "prompt_name" already exists.

See message.

prompt_name is the prompt name that already exists.

The operation cannot be performed. The program continues.

Check the prompt specification. If you intended to create a prompt with a different name, change the name and resubmit the operation. If the prompt that exists (indicated above) is the one that you require, you need take no further action.

AWSJDB319E

A resource with name "resource_name" defined for workstation or workstation class "workstation_or_workstation_class" already exists.

See message.

resource_name is the resource name that already exists.

workstation_or_workstation_class identifies the workstation or workstation class to which the resource belongs.

The operation cannot be performed. The program continues.

Check the resource specification. If you intended to create a resource with a different name, or for a different workstation or workstation class, change the name and resubmit the operation. If the resource that exists (indicated above) is the one that you require, you need take no further action.

AWSJDB320E

The supplied variable table definition contains a duplicate variable name: "variable_name".

See message.

variable_name is the variable name that is duplicated in the variable table.

The operation cannot be performed. The program continues.

Check the variable table specification. Correct the variable information, ensuring that it does not contain duplicate variable names, and retry the operation.

AWSJDB321E

The object "variable_key" already exists.

See message.

variable_key identifies the object that already exists.

The operation cannot be performed. The program continues.

Correct the variable name or specify a different variable table name and retry the operation.

AWSJDB322E

The variable table "variable_table_key" referenced by object "object_key" does not exist.

See message.

object_key identifies the object that owns the unresolved reference.

variable_table_key identifies the referenced variable table that does not exist.

The operation cannot be performed. The program continues.

Check the object specification. Ensure that it refers to an existing variable table and retry the operation.

AWSJDB323E

The default variable table cannot be found or it is being updated by another user, and cannot be modified to become an ordinary variable table.

The default variable table does not exist in the database or is being updated by a concurrent request.

The operation cannot be performed. The program continues.

Retry the operation (this might be a temporary problem).

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

AWSJDB324E

The default variable table cannot be deleted.

You cannot remove the default variable table.

The operation cannot be performed. The program continues.

To remove this table you must first specify a new default variable table. To do this, create a new table or modify an existing table and set the default flag. The new or updated table becomes the default and you can remove the previous default variable table.

AWSJDB325E

The default variable table cannot be modified to become an ordinary variable table.

You cannot remove the default variable table from its role as default.

The operation cannot be performed. The program continues.

If you want to specify a new default variable table, create a new table or modify an existing table and set the default flag. The new or updated table becomes the default.

AWSJDB326E

The availability calendar "calendar_key" referenced by object "object_key" does not exist.

See message.

object_key identifies the object that owns the unresolved reference.

calendar_key identifies the referenced availability calendar that does not exist.

The operation cannot be performed. The program continues.

Check the object specification. Correct it to refer to an existing availaiblity calendar and retry the operation.

AWSJDB327E

The run cycle group "run_cycle_group_key" referenced by object "object_key" does not exist.

See message.

object_key identifies the object that owns the unresolved reference.

run_cycle_group_key identifies the referenced run cycle group that does not exist.

The operation cannot be performed. The program continues.

Check the object specification. Correct it to refer to an existing run cycle group and retry the operation.

AWSJDB328E

The folder "folder_key" referenced by object "object_key" does not exist.

See message.

object_key identifies the object that owns the unresolved reference.

folder_key identifies the referenced folder that does not exist.

The operation cannot be performed. The program continues.

Check the object specification. Correct it to refer to an existing folder and retry the operation.

AWSJDB329E

The parent folder "parent_key" referenced by object "object_key" does not match the parent identifier "identifier".

See message.

object_key identifies the object that owns the unresolved reference.

parent_key identifies the parent folder that does not match the parent identifer.

identifier identifies the parent folder that does not match the parent key.

The operation cannot be performed. The program continues.

Check the object specification. Correct it to refer to a parent key that matches the parent identifier.

AWSJDB330E

The folder "new_folder_key" already exists. The folder "folder_key" cannot be renamed.

The folder is already existing in the model, or is already present in the plan. When deleting a folder if there are still objects in the plan that reference the folder, then another folder cannot be renamed with the name of the deleted folder for the number of days specified by the global option folderDays. However, a brand new folder can be created with the name of the deleted folder. The default value is 10 days.

new_folder_key identifies the new name of the folder.

folder_key identifies the folder that must be renamed.

The operation cannot be performed. The program continues.

Change the name of the folder.

AWSJDB331E

The root folder "folder_key" cannot be renamed.

See message.

folder_key identifies the folder that must be renamed.

The operation cannot be performed. The program continues.

The operation cannot be executed.

AWSJDB401E

Unused message.

AWSJDB402E

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.

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

AWSJDB403E

An internal error has occurred. The operation "operation_name" cannot be performed because the DAO context state "context_state" is not correct.

See message.

operation_name identifies the action that the program was trying to perform.

context_state is the DAO context state that does not allow the operation to be performed.

The operation cannot be performed. The program continues.

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

AWSJDB404E

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

See message.

error_message is the message that explains what went wrong while parsing the Identifier.

The identifier cannot be created. The program continues.

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

AWSJDB501E

Unused message.

AWSJDB601E

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

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

error_message explains more about the error.

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

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

AWSJDB602E

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

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

error_message explains more about the error.

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

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

AWSJDB603E

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

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

error_message explains more about the error.

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

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

AWSJDB604E

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

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

error_message explains more about the error.

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

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

AWSJDB605E

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

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

error_message explains more about the error.

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

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

AWSJDB606E

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

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

error_message explains more about the error.

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

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

AWSJDB607E

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

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

error_message explains more about the error.

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

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

AWSJDB801E

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

See message.

error_message explains more about the error.

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

An internal error has occurred. It might be a temporary problem. If you cannot resolve the problem, search the HCL Support database for a solution at https://hclpnpsupport.hcltech.com/csm.

AWSJDB802E

An internal error has occurred while connecting to the database. The database connection is not available.

See message.

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

An internal error has occurred. It might be a temporary problem. If you cannot resolve the problem, search the HCL Support database for a solution at https://hclpnpsupport.hcltech.com/csm.

AWSJDB803E

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

See message.

error_message explains more about the error.

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

An internal error has occurred. It might be a temporary problem. If you cannot resolve the problem, search the HCL Support database for a solution at https://hclpnpsupport.hcltech.com/csm.

AWSJDB804E

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

See message.

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

An internal error has occurred. It might be a temporary problem. If you cannot resolve the problem, search the HCL Support database for a solution at https://hclpnpsupport.hcltech.com/csm.

AWSJDB805E

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 by planner, which has locked the database.

The write operation cannot be performed. The database transaction is rolled back. The program continues.

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

AWSJDB806W

The collection of database statistics on the pre-production plan tables has failed. The production plan will be generated using the current database statistics.

The statistics used by the database optimizer cannot be updated. Performance cannot be optimized, but the procedure continues.

No database statistics are collected. The program continues.

Make sure you are using a version of the RDBMS that supports this feature and the required stored procedures have been created in the database. Failure to collect the statistics on large and medium-sized databases has an adverse affect on performance.

If you have a small database with little data it is possible to ignore the failure to collect the database statistics on the pre-production plan tables. In this case you need take no action.

AWSJDB807E

An internal error occurred while checking that all the global options and internal global settings are stored in the database. The internal error message is: "error_message".

It is not possible to check that all expected global options and internal global settings are stored in the database.

error_message explains more about the error.

The check operation was not performed. The action is rolled back. The program continues.

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

AWSJDB808E

An internal error has occurred while connecting to the database. The database server may be down or unreachable.

See message.

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

An internal error has occurred. It might be a temporary problem. If you cannot resolve the problem, search the HCL Support database for a solution at https://hclpnpsupport.hcltech.com/csm.

AWSJDB809E

An internal error has occurred while connecting to the database. The requested database was not found.

See message.

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

An internal error has occurred. It might be a temporary problem. If you cannot resolve the problem, search the HCL Support database for a solution at https://hclpnpsupport.hcltech.com/csm.

AWSJDB810E

An internal error has occurred while connecting to the database. The requested table was not found or cannot be accessed.

See message.

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

An internal error has occurred. It might be a temporary problem. If you cannot resolve the problem, search the HCL Support database for a solution at https://hclpnpsupport.hcltech.com/csm.

AWSJDB811E

An internal error has occurred while connecting to the database. The supplied user name and password are not valid.

See message.

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

An internal error has occurred. It might be a temporary problem. If you cannot resolve the problem, search the HCL Support database for a solution at https://hclpnpsupport.hcltech.com/csm.

AWSJDB812E

Multiple threads are trying to access the database using the same transaction. The names of the threads are: "thread_name_list".

See message.

thread_name_list list the threads that are trying to access the database using the same transaction.

The operation requested by the current thread is not performed. The system rolls back the affected transaction. The program continues.

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

AWSJDB813E

Multiple threads are trying to access the database using the same DAO module. The names of the threads are: "thread_name_list".

See message.

thread_name_list lists the threads that are trying to access the database using the same DAO module.

The operation requested by the current thread is not performed. The program continues.

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

AWSJDB814E

The input file "file_path" cannot be found or accessed for reading.

See message.

file_path identifies the path of the input file with contents that must be written to the database.

The file contents cannot be written to the database. The system attempts to roll back the current transaction. The program continues.

An internal error has occurred. However, you might be able to resolve the problem. Check whether the indicated file exists in the path shown, and with read permission for the user performing the operation. If you find an error, fix it. If you cannot resolve the problem, search the HCL Support database for a solution at https://hclpnpsupport.hcltech.com/csm.

AWSJDB815E

The output file "file_path" cannot be created or accessed for writing.

See message.

file_path identifies the path of the output file that must be written using contents read from the database.

The file cannot be written using the contents read from the database. The system attempts to roll back the current transaction. The program continues.

An internal error has occurred. However, you might be able to resolve the problem. Check that there is sufficient disk space to write the file. Check whether the permissions of the indicated path for the user performing the operation allow the file to be written. If you find an error, fix it. If you cannot resolve the problem, search the HCL Support database for a solution at https://hclpnpsupport.hcltech.com/csm.

AWSJDB816E

A property with name "property_name" and object identifier "object_id" already exists.

See message.

property_name is the name of the property that already exists.

object_id is the identifier of the object that owns the property.

The operation cannot be performed. The program continues.

AWSJDB817E

The object "object" cannot be accessed.

See message.

object identifies the object.

The operation cannot be performed. The program continues.

Check that you can access the object. If you have, check that the object's permissions are correctly set in the Security file. If you cannot resolve the problem, search the HCL Support database for a solution at https://hclpnpsupport.hcltech.com/csm.

AWSJDB818E

An internal error has occurred while connecting to the database. The internal error message is: "error_message".

See message.

error_message explains more about the error.

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

An internal error has occurred. It might be a temporary problem. If you cannot resolve the problem, search the HCL Support database for a solution at https://hclpnpsupport.hcltech.com/csm.

AWSJDB819E

An internal error has occurred while connecting to the database. The resource allocation ends with error.

See message.

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

An internal error has occurred. It might be a temporary problem. If you cannot resolve the problem, search the HCL Support database for a solution at https://hclpnpsupport.hcltech.com/csm.

AWSJDB820E

The security domain "domain_key" referenced by access control list does not exist.

See message.

domain_key identifies the referenced security domain that does not exist.

The operation cannot be performed. The program continues.

Check the object specification. Correct it to refer to an existing security domain and retry the operation.

AWSJDB821E

One or more output conditions "outputconditions" cannot be deleted or modified because they are referenced by one or more jobs or job streams "references".

See message.

The operation cannot be performed. The program continues.

Check the references to the output conditions you want to delete, or delete the jobs or job streams that reference the output conditions.

AWSJDB824E

A resource named \"{0}\" already exists. The resource cannot be renamed.

When deleting a resource, if there are still objects in the plan that reference the resource, then another resource cannot be renamed with the name of the deleted resource for the number of days specified by the global option folderDays. However, a new resource can be created with the name of the deleted resource. For more information about global options, see the section about global options in Administration Guide.

The operation cannot be performed. The program continues.

Choose a different name and retry the operation.

AWSJDB825E

A prompt named \"{0}\" already exists. The prompt cannot be renamed.

When deleting a prompt, if there are still objects in the plan that reference the prompt, then another prompt cannot be renamed with the name of the deleted prompt for the number of days specified by the global option folderDays. However, a new prompt can be created with the name of the deleted prompt. For more information about global options, see the section about global options in Administration Guide.

The operation cannot be performed. The program continues.

Choose a different name and retry the operation.

AWSJDB826E

A workstation named \"{0}\" already exists. The workstation cannot be renamed.

When deleting a workstation, if the workstation is still in the plan, then another workstation cannot be renamed with the name of the deleted workstation for the number of days specified by the global option folderDays. However, a new workstation can be created with the name of the deleted workstation. This behavior applies only to dynamic agents, pools, and dynamic pools. For more information about global options, see the section about global options in Administration Guide.

The operation cannot be performed. The program continues.

Choose a different name and retry the operation.