ASN8000 - 10999

ASN Message ID Message Explanation User Response

ASN10501E

 Internal error occurred while adding MQ certificate to MQS keystore on target host hostname.

The requested REST API initiated on the Q Replication source to trust the Q Replication target failed. Exchanging MQ certificates between the source and target MQ keystore did not complete because target could not import the source MQ certificates after the source imported the target certificate. The Q Replication target was not trusted.

Examine the Q Replication REST logs inside the container on the source and target systems for details.

ASN10502E

 Invalid script script_name arguments.

The script listed in the error message could not be run because the arguments were incorrect or the required input arguments were missing.

Use -h option to get script usage.

ASN10503E

 Failed to catalog source db alias database_alias_name.

The requested REST API failed to run the script bludr-catalog-db2alias.sh to catalog the source database alias in the target Db2U container. This is required to perform row-organized table replication.

Verify if the host hostname, dbname database_name, and db port database_port_number are correct and database is available.

ASN10504E

 Failed to catalog node database_node_name.

The requested REST API failed to run the script bludr-catalog-db2alias.sh to catalog the source database node in the target Db2U container. This is required to perform row-organized table replication.

Verify if the host hostname, dbname database_name, and db port database_port_numberare correct and database is available.

ASN10507E

 Trust target failed because the target host host_name has not been activated for replication.

The requested REST API detected that the replication had not been activated on the local host. Trust target or Exchange the Db2 SSL certificates between the replication source and target require both source and target to have replication activated. You can activate replication using put /dr/v2/source/{dbHost}/{dbPort}/{dbName} for Db2U standalone and the web console for Db2U on Cloud Pak for Data, Db2 Warehouse on Cloud, IBM Integrated Analytics System, and Db2 Warehouse Private.

Verify that the source system was enabled for replication.

ASN10508E

 Error encountered while writing remote system certificate from target_host into file on local system.

The requested REST API failed to import the remote system certificate from target host into file on local system. This is required to perform row-organized table replication.

Add the remote DB2 SSL certificate and run bludr-add-db2-sslcert.sh script manually on local system.

ASN10509E

 The database alias database_alias_name is already in use by other node.

The requested REST API failed to run the script bludr-catalog-db2alias.sh to catalog the source database alias in the target Db2U container because the same database alias was already used by another host. This is required to perform row-organized table replication.

Verify if the host hostname, dbname database_name, and db port database_port_number are correct.

ASN10510E

 Db node database_node_name is used by another host and port.

The requested REST API failed to run the script bludr-catalog-db2alias.sh to catalog the source database node in the target Db2U container because the same database node was already used by another host. This is required to perform row-organized table replication.

Verify if the host hostname, dbname database_name, and db port database_port_number are correct.

ASN10512E

 Kubectl command script_name failed with exit code exit_code.

The requested REST API failed to send a command from the Q Replication container to the Db2U container using kubectl command because the Db2U pod name could not be found. Examine the Q Replication log files in the Q Replication container for details.

Verify if the target pod pod_name in namespace namespace is available.

ASN10513E

 Error fetching file path for remote Db2 SSL certificate from server.env on local system.

The requested REST API failed to retrieve store the remote Db2 SSL certificate on the local path. The remote Db2 SSL certificate could not be imported into the local Q Replication trust store to connect to the remote Db2 database.

Verify if MQ_CERT_PATH key exists in server.env and contains a valid value on local system.

ASN10514E

 Error encountered while fetching local Db2 SSL certificate on host hostname.

The requested REST API failed to exchange Db2 SSL certificates between the replication source and target because the local Q Replication container could not send the local Db2 SSL certificate to the remote Q Replication container.

Check if the Db2 SSL certificate rootCA.pem is present on local system host hostname and that it is a valid certificate file.

ASN10515E

 Error encountered while fetching remote Db2 SSL certificate from host hostname.

The requested REST API failed to exchange Db2 SSL certificates between the replication source and target because the local Q Replication container could not retrieve the remote Db2 SSL certificate.

Check if the remote hostname host_name is valid, and if BLUDR server is active on this system.

ASN10516E

 Error fetching REST URL for host target_rest_api_url due to syntax error in URL target_rest_api_url.

The requested REST API had an URI syntax error when sending a request to either the remote Q Replication container to import MQ certificate for trusting target or the Db2 SSL certificate for exchanging Db2 SSL certificate. The remote Q Replication container did not complete the request.

Add the remote Db2 SSL certificate and run bludr-add-db2-sslcert.shscript manually on local system.

ASN10517E

 Error finding and retrieving Db2 SSL certificate at certificate_file_path in the system.

The requested REST API failed to retrieve the local Db2 SSL certificate to be sent to the remote Q Replication container to exchange Db2 SSL certificates.

Verify if the Db2 SSL certificate exists at {0) and check if the file has appropriate file permissions for DR_ADMIN user.

ASN10519E

 Db2 SSL key store could not be found.

The requested REST API failed to run the script bludr-import-ssl-cert.sh to import the remote Db2 SSL certificate to the Db2U client key database because the Db2 SSL server key database was not found. This is required to perform Q Replication REST APIs.

Verify if Db2 SSL keystore has the correct path.

ASN10520E

 No SSL certificate uploaded on the local system.

The uploaded console certificate did not pass the validation check and could not be used by the Q Replication REST API server. The common name in the console certificate must match the local hostname when you generate the console certificate.

Regenerate and upload the console certificate with the correct common name (CN) and retry the trust target REST API.

ASN10522E

 No namespace details found in the server.env.

The requested REST API failed to derive the local Db2U pod name using the key HOSTNAME saved in /opt/ibm/apiserver/wlp/usr/server/bludr/server.env. Check if the HOSTNAME value has the correct cluster hostname.

Verify if the key key_name is defined in server.env.

ASN10523E

 Db alias cannot be empty or null.

The request REST API failed to catalog the source database alias in the target Db2U container for row-organized table replication because the source database alias name was null or empty. Verify if replication target was initialized properly and the /opt/ibm/apiserver/wlp/usr/server/bludr/server.envhas the correct source REST API server properties.

Verify if the host hostname, dbname database_name, and db port database_port_number are correct.

ASN10524E

 Error encountered requesting remote system target_host_name to import local Db2 SSL certificate to remote keystores.

The requested REST API failed to import the remote Db2 SSL certificate into the local Q Replication REST API server trust store.

Check BLUDR server status and server logs on host hostname.

ASN10525E

 Db2 SSL certificate could not be found.

The requested REST API failed to run the script bludr-import-ssl-cert.sh to import the remote Db2 SSL certificate to the Db2U client key database because the remote Db2 SSL certificate could not be found. This is required to perform Q Replication REST APIs.

Verify if the SSL certificate is copied from the remote system.

ASN10527E

 Error encountered while running bludr-add-db2-sslcert.sh script on local system. Message: error_message.

The requested REST API failed to import the remote Db2 SSL certificate into the local Q Replication REST API server trust store. Examine the error message and the Q Replication log files in the container for details.

Run bludr-add-db2-sslcert.sh script manually on local system to add Db2 SSL certificate.

ASN10528E

 Error encountered while running bludr-add-mq-target.sh script on underlying system.

The requested REST API failed to import the remote MQ into the local Q Replication REST API server trust store. Examine the error message and the Q Replication log files in the container for details.

Examine the Q Replication REST logs inside the container on the source and target systems for details.

ASN10529E

 Error encountered while running bludr-trust-targets.sh script on underlying system.

When processing the trust target V2 REST API, the target MQ certificate could not be imported into the source MQ keystore on the replication source. Examine the output from running the script bludr-add-mq-target.sh in the source container under the directory ${BLUDR_SHARED_DIR}/logs/server.

Correct the problem and retry.

ASN10530E

 Db2 server SSL keystore could not be found.

The requested REST API could not locate the Db2 server key database. The remote Db2 SSL certificate could not be imported into the local Db2 server key database. Some Q Replication REST APIs may fail because of the connectivity between the source and target Db2U pods was not configured.

Verify if the Db2 DBM CFG SSL_SVR_KEYDB has the correct path.

ASN10531E

 Db2 client SSL keystore could not be found.

The requested REST API failed to run the script bludr-import-ssl-cert.sh to import the remote Db2 SSL certificate to the Db2U client key database because the Db2 server stash file could not be found. Some Q Replication REST APIs may fail because of the connectivity between the source and target Db2U pods was not configured.

Verify if the Db2 DBM CFG SSL_CLNT_KEYDB has the correct path.

ASN10532E

 Process interrupted.error_message.

The requested Q Replication REST API failed with a system interruption while waiting for the requested action to finish.

Examine the Q Replication logs in $BLUDR_SHARED_DIR/logs for details.

ASN10533E

 Error occurred creating MQ objects for consistency group consistency_group_name on the system_type system.

The request to create or update a replication set failed because the dependent MQ objects could not be created on the target system.

Examine the Q Replication logs in $BLUDR_SHARED_DIR/logs for details.

ASN10534E

 Error attempting to stop asnmon.

The requested Q Replication REST API failed to stop the Q Replication asnmon.

Examine the Q Replication logs in $BLUDR_SHARED_DIR/logs for details.

ASN10535E

 Unable to retrieve the parameters for deleting Q Replication control tables.

The request to delete Q Replication target failed because the corresponding Q Replication apply server control tables were not found.

Verify that the Q Replication apply server exists and is active.

ASN10536E

 Failed to add database db2_database_alias_name to the metadata application context.

The request to delete Q replication apply server failed because the corresponding target database information could not be accessed.

Verify that the Q Replication apply server exists and is active.

ASN10537E

 Unable to read the asnclp argument file file_with_absolute_path while deleting a replication set or subscription.

The request to delete a replication set or subscription failed because the corresponding consistency group parameters could not be retrieved.

Verify the correct names for replication set or subscription name.

ASN10538E

 The number of arguments passed number_of_arguments is incorrect.

The requested Q Replication REST API failed because asnclp log file name could not be generated for working files and logs. The generated asnclp command could not be run.

Examine the Q Replication log files in $BLUDR_SHARED_DIR/logs for details.

ASN10539E

 Could not retrieve target table table_name information for stopping replication.

The requested Q Replication REST API to stop replication failed because the table subscription for the replication set does not reference a valid table name.

Verify that the target table is existing and active.

ASN10540E

 Unable to resolve table mapping found for subscription name subscription_name in consistency group consistency_group_name under replication set replication_set_name.

The requested Q Replication REST API to stop replication failed because the table subscription for the replication set does not reference a valid table name.

Verify that the target table exists and is active.

ASN10541E

 Error occurred obtaining the consistency group consistency_group_namefor the replication set replication_set_name.

The requested Q Replication REST API failed to remove the specified replication set.

Verify that the replication set exists and running.

ASN10542E

 No billing data fetched during this call, due to the script bludr-calculate-billing-data.sh failing to run.

The requested Q Replication REST API could not fetch any billing data because there were no capture or apply activities found.

Examine the log file $BLUDR_SHARED_DIR/logs/billing_calculation.log.

ASN10543E

 Failed to connect to the database db2_database_alias_nameon host tcpip_port_number and port tcpip_port_number when accessing the Q Replication REST API properties table.

The Q Replication REST API server properties could not be retrieved or changed because the required database connection could not be established. The request to add the Q Replication apply server could not be completed.

Verify that the Q Replication apply server host, database, port, and database credentials are correct, and the database is active.

ASN10544E

 Error creating directory directory_path.

The requested action could not be completed. The requested Q Replication REST API failed to create log directory for working files and log files.

Verify that your file system has sufficient disk storage and is healthy.

ASN10545E

 system_type Queue Managers are not available.

The Q Replication health check REST API failed to check the status of the Q Replication capture or apply queue manager because the Queue Manager name was empty.

Ensure that the MQ manager exists and is enabled. Examine the Q Replication log files in $BLUDR_SHARED_DIR/logs for details.

ASN10546E

 system_type Queue Managers are not running.

The Q Replication health check REST API detected either the Q Replication capture or the apply queue manager not running.

Ensure that the MQ manager is enabled and running. Verify that Q Replication REST API server was started correctly with the corresponding capture, apply, capture MQ manager, and apply MQ manager. Examine the Q Replication log files in $BLUDR_SHARED_DIR/logs for details.

ASN10547E

 Error getting the file transfer directories.

The external table file path could not be retrieved. For columnar table replication, a working directory is required to stage the external tables files to be used by Db2.

For Db2 Warehouse on Cloud, verify Db2 DB CFG parameter EXTBL_LOCATION is setup properly. For other runtime environments, verify the system environment BLUDR_DB2_DATA_PATH in the container where Q Replication is deployed has the correct value, and the deployment of Q Replication was successful.

ASN10548E

 Failed to execute replication job job_type .

The requested Q Replication REST API failed to start the capture server.

Ensure that the capture MQ manager is running. Examine the capture log in $BLUDR_SHARED_DIR/logs/replication for details.

ASN10549E

 Failed to execute asnmon job job_type.

The requested Q Replication REST API failed to start asnmon either when the REST API was started or after adding apply alert conditions.

Examine the Q Replication log files in $BLUDR_SHARED_DIR/logs for details.

ASN10550E

 Error creating request URL with pattern internal_url, using input replication_parameters.

The requested Q Replication REST API failed to build an internal REST API to the remote system.

Verify that the correct API parameters are specified. Examine the Q Replication log files in $BLUDR_SHARED_DIR/logs for details.

ASN10551E

 The MQ certificate could not be added to the MQ keystore.

The requested Q Replication REST API failed to add source certificate to target MQ keystore.

Examine the log files in $BLUDR_SHARED_DIR/logs for details.

ASN10552E

 Error attempting to execute URL rest_url.

The requested Q Replication REST API either failed to add Q Replication apply server or to update the user credentials.

Examine the Q Replication log files in $BLUDR_SHARED_DIR/logs for details.

ASN10553E

 Error fetching remote QReplication REST API server port number for host host_name, db db2_database_alias_name, and port tcpip_port_number.

The request to add a Q Replication apply server failed because the Q Replication Rest API server's external port number could not be found on the target database.

Verify that the add target hostname, database name, and database port number are correct, and that the target Q Replication container was deployed and initialized properly.

ASN10554E

 Operation not supported for operation_detail for type system_type.

The requested Q Replication REST API attempted to retrieve and verify the managed Q Replication apply servers, but one or more apply servers did not have the expected type as a target system.

Verify that the API parameters are correct.

ASN10555E

 Error encountered while running bludr-import-target-server-ssl.sh script on underlying system.

The requested Q Replication REST API failed to trust the Q Replication apply server while running the script bludr-import-target-server-ssl.sh script on the source system.

Examine the script log files in $BLUDR_SHARED_DIR/logs on both the source and target systems.

ASN10556E

 Encountered Input/Output Exception starting replication.

The requested Q Replication REST API failed with an input or output error.

Examine the Q Replication log files in $BLUDR_SHARED_DIR/logs for details.

ASN10557E

 Error encountered while running the MQ certificate scripts or Db2 SSL certificate scripts.

The requested Q Replication REST API failed to run the script to trust target and exchange Db2 SSL certificates between the Q Replication capture and apply servers.

Examine the Q Replication log files in $BLUDR_SHARED_DIR/logs for details.

ASN10558E

 Error attempting to retrieve db2_database_alias_name alias.

The request to fetch or update the Q Replication user credentials on the Q Replication apply server failed.

Verify that the target database host, database name, and database ports are correct. Verify that the system is healthy.

ASN10559E

 Error occurred running MQ command name_of_mq_command.

The request could not be completed. The requested Q Replication REST API failed to run the dependent MQ commands.

Examine the $BLUDR_SHARED_DIR/logs/server/messages.log file for details.

ASN10560E

 Unable to create queue manager queue_manager_name. Process completed with return code return_code.

The requested Q Replication REST API failed to create MQ manager for capture or apply when activating replication, enabling source, or adding target.

Examine the log files in $BLUDR_SHARED_DIR/logs for details.

ASN10561E

 Failed to catalog the source or target database alias when enabling replication source or adding replication target. The cataloged Db2 node entry was null or empty.

The request to catalog the database on the local environment failed because the node name is null or empty.

Verify the connection information and ensure that the database is available.

ASN10562E

 Unable to retrieve database using alias alias_name.

The requested Q Replication REST API failed to delete apply control tables.

Verify that the database alias name is correct. Verify the system is healthy.

ASN10563E

 Request request_path failed with status code response_code and entity response_entity.

The REST API did not complete. The requested REST API failed with the http response code listed in the error message.

Verify that the request is valid.

ASN10564E

 Failed to get MQ Certificate.

The requested Q Replication REST API failed to get MQ certificate.

Examine the log files in $BLUDR_SHARED_DIR/logs for details.

ASN10565E

 The credential file credential_file was not found on the system.

The requested Q Replication REST API failed to obtain the database credentials file due to a configuration error.

Verify that the password file is existing and readable.

ASN10566E

 Error code return_code was returned when reading the credential file credential_file.

The requested Q Replication REST API failed to obtain the database credentials from the password file.

Verify that the password file is existing and readable.

ASN10567E

 Failed executing http request http_request.

The REST API did not complete. The requested Q Replication REST API failed to validate the http requester using the authorization header.

Verify that the request is valid.

ASN10568E

 Timed out while trying to stop capture or apply server.

The requested Q Replication REST API timed out while stopping capture or apply. You can re-attempt to stop the capture or apply server.

Re-attempt to stop the capture or apply server.

ASN10569E

 The credential for database alias database_alias was not found in the file password_file.

The requested Q Replication REST API failed to retrieve the replication user credential using asnclp, because the returned value was empty or null.

The Q Replication configuration might not be valid, or the password file was corrupted.

ASN10570E

 Failed to encrypt queue for queue manager queue_manager_name.

The requested REST API failed to encrypt the queue with given Certificate DN and queue manager name.

Examine the Q Replication log files in $BLUDR_SHARED_DIR/logs for details.

ASN10571E

 Failed to select, insert, update, or delete the Q Replication REST API server properties in the database when adding replication target. The error was error_message.

The requested REST API failed to retrieve the REST API server properties in the database when adding replication target.

Verify that the target hostname, database name, and port number are correct, and the target Db2 is active.