Connections

4.9.1 Generic Issues

4.9.1.1 Missing role information in event header

Issue: User tries to perform an operation related to a connection through other means than UI, like CLI or Postman etc.

Resolution: Add the role_id with appropriate role and try running the API request again.

Cause: The role_id parameter is missing from the body of the API request made.

4.9.1.2 User action is not permitted

Issue: User tries to perform an operation related to connections functionality.

Resolution: Request the admin to be added the user as an authorized user to this connection.

Cause: The user requesting to perform an operation on this connection is neither the creator of it nor was mentioned as an authorized user

4.9.1.3 Unsupported connection type {user_entered_entry}

Case-1

Issue: When the user tries to create a connection from the UI

Resolution: Create a bug ticket to the ADC team

Cause: The connection type in the response is faulty

Case-2

Issue: When the user tries to create a connection through other means than UI, like CLI or Postman etc.

Resolution: Add an appropriate connection type, currently supported through UI, in the API request made.

Cause: The connection type in the API request made has an unsupported/empty entry.

4.9.1.4 All users in the given list are Un-authorised Users - {user_entered_entry}

Case-1

Issue: When the user tries to create a connection from the UI.

Resolution: Remove the invalid username(s) and proceed.

Cause: The selected user might have been removed from the system during the time of connection creation.

Case-2

Issue: When the user tries to create a connection through other means than UI, like CLI or Postman etc.

Resolution: Remove any invalid username(s) from the API request made.

Cause: The username(s) listed in the API request might not exist in the system.

4.9.1.5 A connection with name {user_entered_entry} exists, please choose different name

Issue: When the user tries to create a connection from the UI.

Resolution: Choose a unique connection name other than the one entered.

Cause: The user entered connection name already exists.

4.9.2 JDBC Connection Creation

4.9.2.1 Invalid JDBC URL

Issue: User tries to create a JDBC connection.

Resolution: should re-check if the JDBC url is entered and in proper format.

Cause: Either the JDBC url is not at all entered or is entered in improper format.

4.9.2.2 Must pass Username, Password, and ssl in Connection Details for API connection type

Issue: User tries to create a JDBC connection.

Resolution: Should re-check if the username, password and ssl details are filled in.

Cause: The username, password and ssl details are mandatory fields for establishing an JDBC connection.

4.9.2.3 Unable to create glue connection with error {dynamic_error_message}

Issue: User tries to create a JDBC connection.

Resolution: Create a bug ticket to the ADC team.

Cause: Unsuccessful creation of the Glue job might be due to various reasons.

4.9.2.4 A connection with name {connection_name} exists, please choose different name

Issue: User tries to create a JDBC connection.

Resolution: Choose a unique connection name other than the one entered.

Cause: The user entered connection name already exists.

4.9.2.5 Unsupported source '{source_type}', only [mysql,aurora,oracle] are supported for now

Case-1

Issue: User tries to create a JDBC connection through UI.

Resolution: Choose the options that are supported by the ADC platform.

Cause: User tries to choose a different source_type than the ones currently supported i.e. mysql, aurora or oracle

Case-2

Issue: User tries to create a JDBC connection through other means than UI, like CLI or Postman etc.

Resolution: Re-check your API call to include only supported source_type(s).

Cause: The source_type in the API request made doesn’t exist or is not currently supported.

4.9.2.6 creating

Issue: User tries to create a JDBC connection.

Resolution: Create a bug ticket to the ADC team.

Cause: Creation of the source endpoint has failed due to unknown reason

4.9.2.7 Test connection lambda failed with error - {error_msg}

Issue: User tries to create a JDBC connection.

Resolution: Create a bug ticket to the ADC team.

Cause: Creation of test connection lambda failed due to the aforementioned error message

4.9.2.8 Create connection failed, user {user_name} credentials are invalid, please verify credentials

Issue: User tries to create a JDBC connection.

Resolution: resubmit the username, password provided in the connection details.

Cause: The JDBC connection test was not successful due to wrong credentials entered

4.9.2.9 unable to store secret key, please try again later.

Issue: User tries to create a JDBC connection.

Resolution: Create a bug ticket to the ADC team.

Cause: There is a problem storing the Access & Secret Keys in the SSM store

4.9.2.10 Failed to update the dynamoDB even after creating the connection object, admin must cleanup this inconsistency.

Issue: User tries to create a JDBC connection.

Resolution: Create a bug ticket to the ADC team.

Cause: Technical issues with the backend storing the connection details, causing the resources created to be unaccounted for

4.9.2.11 Invalid connection id - {connection_id}

Case-1

Issue: User tries to create a JDBC connection or tries to test the connection of an existing JDBC connection from the UI

Resolution: Refresh the page to check if the connection exists. If it does and the problem still persists, create a bug ticket to the ADC team

Cause: The JDBC connection might have been deleted prior to or during the process of testing the connection

Case-2

Issue: User tries to create a JDBC connection or tries to test the connection of an existing JDBC connection through other means than UI, like CLI or Postman etc.

Resolution: Provide a valid connection id in the API request being made.

Cause: The JDBC connection id passed in the API request made might be invalid.

Case-3

Issue: User tries to run a JDBC connection task.

Resolution: Refresh the page to check if the connection exists. If it does and the problem still persists, create a bug ticket to the ADC team.

Cause: The JDBC connection might have been deleted prior to running the task but was not reflected on the webpage.

Case-4

Issue: User tries to list the tasks under a JDBC connection.

Resolution: Refresh the page to check if the connection exists. If it does and the problem still persists, create a bug ticket to the ADC team.

Cause: The JDBC connection might have been deleted prior to or during the process of listing the tasks.

Case-5

Issue: When the user tries to register datasets in a bulk load JDBC connection from the UI.

Resolution: Refresh the page to check if the connection exists. If it does and the problem still persists, create a bug ticket to the ADC team.

Cause: The JDBC connection might have been deleted prior to or during the process of listing the tasks.

Case-6

Issue: User tries to start/stop/pause the tasks under a JDBC Bulk Load connection.

Resolution: Refresh the page to check if the connection exists. If it does and the problem still persists, create a bug ticket to the ADC team.

Cause: The JDBC connection might have been deleted prior to or during the process of listing the tasks

4.9.2.12 Unsupported source '{source_type}', only [mysql,aurora,oracle] are supported for now

Case-1

Issue: User tries to update a JDBC connection through UI.

Resolution: Choose the options that are supported by the ADC platform.

Cause: User tries to choose a different source_type than the ones currently supported i.e. mysql, aurora or oracle

Case-2

Issue: User tries to update a JDBC connection through other means than UI, like CLI or Postman etc.

Resolution: Re-check your API call to include only supported source_type(s).

Cause: The source_type in the API request made doesn’t exist or is not currently supported

4.9.2.13 updating.

Issue: User tries to update a JDBC connection.

Resolution: Create a bug ticket to the ADC team.

Cause: Modification of the source endpoint has failed due to unknown reason.

4.9.2.14 unable to update secret key in ssm, please try again later.

Issue: User tries to update a JDBC connection.

Resolution: Create a bug ticket to the ADC team.

Cause: There is a problem updating the Access & Secret Keys in the SSM store.

4.9.2.15 Failed to update the dynamoDB even after updating the connection object, admin must cleanup this inconsistency.

Issue: User tries to update a JDBC connection.

Resolution: Create a bug ticket to the ADC team.

Cause: Technical issues with the backend storing the connection details, causing the resources created to be unaccounted for.

4.9.2.16 Updating connection failed with new credentials of {user_name}, please verify

Issue: User tries to update a JDBC connection.

Resolution: Re-check the new credentials provided in the connection and try again.

Cause: The JDBC connection test was not successful due to wrong credentials entered.

4.9.2.17 User {user_name} is not authorized to update connection details

Issue: User tries to update a JDBC connection.

Resolution: Request the admin to be added the user as an authorized user to this connection.

Cause: The user requesting to modify the connection details is neither the creator of it nor was mentioned as an authorized user.

4.9.2.18 User {user_name} is not authorized to delete connection details

Issue: User tries to delete a JDBC connection.

Resolution: Request the admin to be added the user as an authorized user to this connection.

Cause: The user requesting to delete the connection details is neither the creator of it nor was mentioned as an authorized user.

4.9.2.19 Extract source schema’s & tables lambda failed with error - {error_msg}

Issue: User tries to run a JDBC connection task to load data from source.

Resolution: Re-run the task and if the issue still persists, create a bug ticket to the ADC team.

Cause: The aforementioned error message occurs when there is an issue while scouting the data from the source.

4.9.2.20 User {user_name} is not authorized to get source list

Issue: User tries to run a JDBC connection task to load data from source.

Resolution: Contact the admin to request access to this connection and try again.

Cause: The user that’s trying to perform this operation is not a creator nor is in the authorized users list for that connection.

4.9.2.21 User {user_name} is not authorized to get list of tasks for a connection

Issue: User tries to list the tasks under a JDBC connection.

Resolution: Contact the admin to request access to this connection and try again.

Cause: The user that’s trying to perform this operation is not a creator nor is in the authorized users list for that connection.

4.9.2.22 Hello user, dataset names {0} are already taken. Please choose different name for them before submitting again

Issue: When the user tries to register datasets in a bulk load JDBC connection from the UI.

Resolution: Consider unique dataset name and try again.

Cause: The dataset name user is after is already in use.

4.9.2.23 Missing mandatory param TargetLocation in the input body

Issue: When the user tries to run a JDBC bulk load task from the UI.

Resolution: Target location is a mandatory parameter, please add it and try again. Currently S3 or auroramysql are supported.

Cause: The mandatory parameter TargetLocation is missing in the body of API request made.

4.9.2.24 Not all mandatory params are set for scheduling the job, please verify

Issue: When the user tries to schedule a JDBC bulk load task from the UI.

Resolution: Re-check the form and fill out all the mandatory parameters and try again.

Cause: All the mandatory parameters are not set.

4.9.2.25 CDC start time {start_time} should be in format 'YYYY-MM-DDTHH:mm:ss'

Issue: When the user tries to create a JDBC bulk load task from the UI.

Resolution: Correct the CDC timestamp to match “YYYY-MM-DDTHH:mm:ss”.

Cause: The CDC timestamp format is not of the format “YYYY-MM-DDTHH:mm:ss”

4.9.2.26 Create job schedule lambda failed with error - {error_msg}

Issue: When the user tries to create a JDBC bulk load task from the UI.

Resolution: Create a bug ticket to the ADC team.

Cause: Lambda that creates job schedule failed with the aforementioned error message.

4.9.2.27 Failed to update the dynamoDB table, admin must cleanup this inconsistency.

Issue: When the user tries to create a JDBC bulk load task from the UI.

Resolution: Create a bug ticket to the ADC team.

Cause: Technical issues with the backend storing the connection details, causing the resources created to be unaccounted for.

4.9.2.28 Schedule creation failed with error {error_msg}

Issue: When the user tries to schedule a JDBC bulk load task from the UI.

Resolution: Create a bug ticket to the ADC team.

Cause: Lambda that creates job schedule failed with the aforementioned error message.

4.9.2.29 User {user_name} is not authorized to register datasets for the task

Issue: When the user tries to register datasets by running a JDBC bulk load task from the UI.

Resolution: Request the admin to be added the user as an authorized user to this connection.

Cause: The user requesting to register datasets is neither the creator of the connection nor was mentioned as an authorized user to it.

4.9.2.30 Invalid task-id - {task_id}

Issue: When the user tries to get the details of a JDBC bulk load task from the UI.

Resolution: Refresh the page to check if the task exists. If it does and the problem still persists, create a bug ticket to the ADC team.

Cause: The task might have been deleted prior to or during the process of listing that task.

4.9.2.31 TaskAction param is required from input body

Issue: User tries to perform an operation on a JDBC connection task through other means than UI, like CLI or Postman etc.

Resolution: Add an appropriate TaskAction parameter to the API request body and try again.

Cause: TaskAction parameter is missing from the API request made.

4.9.2.32 Task action of {task_action} is not supported for full-load type

Issue: User trying to perform either of Stop, Resume or Restart operations on a JDBC Full load connection task.

Resolution: Refrain from using the above tasks on a full load JDBC connection task.

Cause: stop, resume & restart task options are not supported for the full-load type.

4.9.2.33 CDC data sync to S3 failed for task {task_name} with error {error_msg}

Issue: User tries to run a JDBC connection task with SyncToS3 on.

Resolution: Create a bug ticket to ADC team.

Cause: The task failed with the aforementioned error message.

4.9.2.34 Task is still in starting state, please wait for some time to stop

Issue: User trying to stop a task from JDBC connection.

Resolution: Wait until the task status shows it’s running and then try stopping it.

Cause: The task has to be in running state for it to be stopped.

4.9.2.35 Failed to stop data migration task, please try after some time

Issue: User tries to stop a data migration task.

Resolution: Retry after some time and if the problem still persists, create a bug ticket to the ADC team.

Cause: The task failed due to unknown reason.

4.9.2.36 Task is not running, wait for task to start before stopping again

Issue: User trying to stop a task from JDBC connection.

Resolution: The task has not started yet, so no need to stop it.

Cause: Task should be in running state to be eligible for being stopped.

4.9.2.37 Task can be resumed only in stopped state

Issue: User trying to resume a task from JDBC connection.

Resolution: Resume operation is not applicable here as the task is not stopped.

Cause: Task should be in stopped state for it to be eligible for resume operation.

4.9.2.38 Failed to resume CDC data migration task, please try after some time

Issue: User trying to resume CDC data migration task.

Resolution: Retry after some time and if the problem still persists, create a bug ticket to the ADC team.

Cause: The task failed due to unknown reason.

4.9.2.39 Task is already running

Issue: User tries to start a task.

Resolution: Wait for the existing run to complete before restarting it again.

Cause: A running instance of the same task is already present.

4.9.2.40 Task can be restarted only in stopped state

Issue: User tries to restart a task.

Resolution: Wait for the job to finish before attempting to restart.

Cause: The task is not in stopped state for it to be restarted.

4.9.2.41 Failed to restart CDC data migration task, please try after some time

Issue: User trying to restart a CDC data migration task.

Resolution: Wait for some time before attempting to restart it again. If the problem still persists, create a bug ticket to the ADC team.

Cause: Task failed to restart due to unknown reason.

4.9.2.42 User {user_name} is not authorized to perform any action on task

Issue: User tries to perform an operation on a JDBC connection task.

Resolution: Request the admin to be added the user as an authorized user to this connection.

Cause: The user trying to perform an operation on the connection task is neither the creator of the connection nor was mentioned as an authorized user.

4.9.2.43 Task is in running state, wait for current run to complete

Issue: User tries to run a DMS migration task of a JDBC connection.

Resolution: Wait for the task to finish before attempting to run again.

Cause: Task is already in running state, “start” operation doesn’t apply here.

4.9.2.44 Cleanup is in progress

Issue: User tries to run a DMS migration task of a JDBC connection.

Resolution: Wait for the cleanup task to complete before attempting to run again.

Cause: Task is already in cleanup state, cannot run during this time.

4.9.2.45 Replication instance creation failed with error - {error_msg}

Issue: User tries to run a DMS migration task of a JDBC connection.

Resolution: Create a bug ticket to the ADC team.

Cause: Task failed due to the aforementioned error message.

4.9.2.46 Failed to update the dynamoDB table, admin must cleanup this inconsistency.

Issue: User tries to run a DMS migration task of a JDBC connection.

Resolution: Create a bug ticket to the ADC team.

Cause: Technical issues with the backend storing the cleanup progress, causing the metadata to become inconsistent.

4.9.2.47 Please delete schedule '{schedule_name}' associated with this task before deleting the task

Issue: User attempting to delete JDBC connection task(s).

Resolution: Try removing the associated schedule first before attempting to delete the task.

Cause: The associated schedule for the task is still active causing the task delete operation to fail.

4.9.2.48 Failed to cancel data migration task, please try after some time

Issue: User attempting to stop the data migration task of a JDBC connection.

Resolution: Create a bug ticket to the ADC team.

Cause: Attempting to stop during the replication step of a data migration task has encountered an error.

4.9.2.49 Unable to get the current status of migration task

Issue: User attempting to stop the data migration task of a JDBC connection.

Resolution: Create a bug ticket to the ADC team.

Cause: Upon successful termination of the data migration task, describing the task status encountered an issue.

4.9.2.50 Failed to update the dynamoDB table, admin must cleanup this inconsistency.

Case-1

Issue: User starts a data migration task of a JDBC connection.

Resolution: Create a bug ticket to the ADC team.

Cause: Technical issues with the backend storing the cleanup progress, causing the metadata to become inconsistent.

Case-2

Issue: User attempting to stop the data migration task of a JDBC connection.

Resolution: Create a bug ticket to the ADC team.

Cause: Technical issues with the backend storing the cleanup progress, causing the metadata to become inconsistent.

4.9.2.51 Unable to cancel/delete data migration task {task_name}, please try after some time

Issue: User tries to cancel/delete a data migration task of JDBC connection.

Resolution: Wait for some time and retry the operation.

Cause: Several reasons like the task being in starting/running state would cause the cancel/delete operation to fail.

4.9.2.52 User {user_name} is not authorized to delete task

Issue: User tries to delete a data migration task of a JDBC connection from the UI.

Resolution: Request the admin to be added the user as an authorized user to this connection.

Cause: The user requesting to delete the data migration task is neither the creator nor was mentioned as an authorized user for that connection.

4.9.2.53 Unable to get the current status of migration task

Issue: User tries to view details of a data migration task of a JDBC connection from the UI.

Resolution: Usually this error needs no action from the user if the error occurs during intermediate states of the task. But If the problem arises after the task completes as well, create a bug ticket to the ADC team.

Cause: Technical issues with the backend storing the latest status of the task, causing the metadata to become inconsistent.

4.9.2.54 Failed to update the dynamoDB table, admin must cleanup this inconsistency.

Issue: User tries to view details of a data migration task of a JDBC connection from the UI.

Resolution: Create a bug ticket to the ADC team.

Cause: Technical issues with the backend storing the cleanup progress, causing the metadata to become inconsistent.

4.9.2.55 User {user_name} is not authorized to see task details

Issue: User tries to view the details of a data migration task of a JDBC connection from the UI.

Resolution: Request the admin to be added the user as an authorized user to this connection.

Cause: The user requesting to view details of the data migration task is neither the creator nor was mentioned as an authorized user for that connection.

4.9.2.56 Mandatory params of InstanceClass/AllocatedStorage are missing from input object

Issue: User tries to update the dms task instance through other means than UI, like CLI or Postman etc.

Resolution: Add the missing mandatory parameters listed in the error message and try again.

Cause: Mandatory params InstanceClass/AllocatedStorage are missing in the body of API request made.

4.9.2.57 Replication instance can only be modified for running tasks.

Issue: User tries to update the dms task instance of JDBC connection.

Resolution: Start a DMS task and try modifying the instance.

Cause: The data migration task is not in running state to be able to modify the instance.

4.9.2.58 Allocated storage should be more than '10%' of the original

Issue: User tries to update the dms task instance of JDBC connection.

Resolution: Increase the instance storage size to match the criteria and try again.

Cause: The DMS instance storage is supposed to be more than 10% of the data source size.

4.9.2.59 Replication instance is currently in modifying state, please wait before submitting changes again

Issue: User tries to update the dms task instance of JDBC connection.

Resolution: Wait for some time to let the old changes to take into effect before attempting to enforce new changes.

Cause: The recently requested changes are yet to be finalized before requesting new changes on the DMS instance.

4.9.2.60 Replication instance modification failed with error - {error_msg}

Issue: User tries to update the dms task instance of JDBC connection.

Resolution: Create a bug ticket to the ADC team.

Cause: Modification of the replication instance failed due to the aforementioned error message.

4.9.2.61 Failed to update the dynamoDB table, admin must cleanup this inconsistency.

Issue: User tries to update the dms task instance of JDBC connection.

Resolution: Create a bug ticket to the ADC team.

Cause: Technical issues with the backend storing the cleanup progress, causing the metadata to become inconsistent.

4.9.2.62 Out of range for items per page, Limit is 1000

Case-1

Issue: User tries to list the registered datasets through UI.

Resolution: Create a bug ticket to the ADC team.

Cause: The number of datasets returned are greater than the limit of 1000.

Case-2

Issue: User tries to list the registered datasets through other means than UI, like CLI or Postman etc.

Resolution: Add a limit condition to the API request made to less than 1000.

Cause: The number of datasets returned are greater than the limit of 1000.

4.9.2.63 Missing mandatory query param 'bulkdataload' for creating a connection

Issue: User tries to create a bulk data load JDBC connection through other means like postman or api etc. than UI.

Resolution: Add the missing parameter and try running the API request again.

Cause: Mandatory parameter 'bulkdataload' is missing from the body of API request made.

4.9.2.64 Test connection failed

Issue: User tries to test a JDBC connection by fetching the list of schema and tables in the source.

Resolution: Create a bug ticket to the ADC team.

Cause: Failed to fetch the schema and tables from the source due to unknown error.

4.9.2.65 Required parameters missing from input for S3 engine BucketName or BucketFolder

Issue: User tries to create a task of JDBC bulk load connection.

Resolution: Fill the BucketName and BucketFolder parameter and try again.

Cause: BucketName or BucketFolder parameter missing.

4.9.2.66 Required parameters missing from input for kinesis engine StreamArn

Issue: User tries to create a task of JDBC bulk load connection.

Resolution: Enter the KinesisARN parameter and try again.

Cause: Kinesis Stream ARN not entered.

4.9.2.67 Required parameters missing from input for elasticsearch engine EndpointUri

Issue: User tries to create a task of JDBC bulk load connection.

Resolution: Enter the EndpointUri and try again.

Cause: EndpointUri parameter missing.

4.9.2.68 Required parameters missing from input for {EngineName} engine DatabaseName

Issue: User tries to create a task of JDBC bulk load connection.

Resolution: Enter the DatabaseName and try again.

Cause: When EngineName is either of mysql/aurora/aurora-postgresql and DatabaseName parameter missing in the connection details.

4.9.2.69 Required parameters missing from input for {EngineName} engine OracleService name

Issue: User tries to create a task of JDBC bulk load connection.

Resolution: Enter the OracleService parameter and try again.

Cause: When EngineName is oracle and OracleService parameter not present in the connection details

4.9.2.70 Required parameters missing from input for S3 engine BucketName or BucketFolder

Issue: User tries to modify a task of JDBC bulk load connection.

Resolution: Fill the BucketName and BucketFolder parameter and try again.

Cause: BucketName or BucketFolder parameter missing

4.9.2.71 Required parameters missing from input for kinesis engine StreamArn

Issue: User tries to modify a task of JDBC bulk load connection.

Resolution: Enter the KinesisARN parameter and try again.

Cause: Kinesis Stream ARN not entered.

4.9.2.72 Required parameters missing from input for elasticsearch engine EndpointUri

Issue: User tries to modify a task of JDBC bulk load connection.

Resolution: Enter the EndpointUri and try again.

Cause: EndpointUri parameter missing.

4.9.2.73 Required parameters missing from input for {EngineName} engine DatabaseName

Issue: User tries to modify a task of JDBC bulk load connection.

Resolution: Enter the DatabaseName and try again.

Cause: When EngineName is either of mysql/aurora/aurora-postgresql and DatabaseName parameter missing in the connection details.

4.9.2.74 Required parameters missing from input for {EngineName} engine OracleService name.

Issue: User tries to modify a task of JDBC bulk load connection.

Resolution: Enter the OracleService parameter and try again.

Cause: When EngineName is oracle and OracleService parameter not present in the connection details.

4.9.2.75 Script upload to S3 ETL bucket failed, please verify.

Issue: When user tries to create a JDBC bulk load connection.

Resolution: Create a bug ticket to the ADC team.

Cause: The glue script upload to S3 failed due to unknown reason.

4.9.2.76 Unable to create the GLUE job, try again later.

Issue: When user tries to create a JDBC bulk load connection.

Resolution: Create a bug ticket to the ADC team.

Cause: Creation of the connection failed due to unknown reason.

4.9.2.77 Unable to update the GLUE job, try again later.

Case-1

Issue: When user tries to update a JDBC bulk load connection.

Resolution: Create a bug ticket to the ADC team.

Cause: Updating the connection failed due to unknown reason.

Case-2

Issue: When user tries to delete a JDBC bulk load connection.

Resolution: Create a bug ticket to the ADC team.

Cause: Deleting the connection failed due to unknown reason.

4.9.2.78 Glue script delete from S3 ETL bucket failed, please verify

Issue: When user tries to delete a JDBC bulk load connection.

Resolution: Create a bug ticket to the ADC team.

Cause: Deleting the connection failed due to unknown reason.

4.9.2.79 Failed to update the dynamoDB table, admin must cleanup this inconsistency.

Issue: User tries to perform one of the following tasks - register datasets, start a task replication task creation, deleting a DMS connection.

Resolution: Create a bug ticket to the ADC team.

Cause: Technical issues with the backend storing the task status, causing the metadata to become inconsistent.

4.9.2.80 Delete datasets lambda failed with error - {error_msg}

Issue: User fails to create a JDBC connection causing rollback process to trigger.

Resolution: Create a bug ticket to the ADC team.

Cause: Something went wrong with the rollback process while trying to delete the datasets registered during this process with the aforementioned error message.

4.9.2.81 Create dataset metadata lambda failed with error - {error_msg} for dataset {dataset_name}

Issue: User tries to create a JDBC bulk load connection.

Resolution: Create a bug ticket to the ADC team.

Cause: Technical issues with the backend storing the task status, causing the metadata to become inconsistent.

4.9.2.82 Extract source dataset schema lambda failed with error - {error_msg} for dataset {dataset_name}

Issue: User tries to create a JDBC bulk load connection.

Resolution: Create a bug ticket to the ADC team.

Cause: Lambda that extracts source dataset schema failed due to aforementioned error.

4.9.2.83 Complete dataset registration lambda failed with error - {error_msg} for dataset {dataset_name}

Issue: User tries to create a JDBC bulk load connection.

Resolution: Create a bug ticket to the ADC team.

Cause: Lambda that completes the registration status failed due to aforementioned error.

4.9.2.84 Unable to get the current status of migration task

Issue: User tries to delete a JDBC bulk load connection.

Resolution: Create a bug ticket to the ADC team.

Cause: Task failed while trying to fetch table statistics due to unknown error.

4.9.2.85 Failed to create glue partition for table {dataset_name}

Issue: User runs a DMS task of JDBC connection.

Resolution: Create a bug ticket to the ADC team.

Cause: Actual file load to the DWH is successful, but the Glue partition metadata is not updated due to unknown reason.

4.9.2.86 Unable to update metadata of file in file loads table.

Issue: User runs a DMS task of JDBC connection.

Resolution: Create a bug ticket to the ADC team.

Cause: Actual file upload was successful but storing the metadata of the file failed due to unknown reason.

4.9.2.87 unable to delete secret key, please try again later.

Issue: User tries to delete a JDBC connection.

Resolution: Create a bug ticket to the ADC team.

Cause: There is a problem deleting the Secret Key in the SSM store.

4.9.3 S3 Connection Creation

4.9.3.1 Must pass S3Bucket, AccessKey, and SecretKey in ConnectionDetails for S3 connection type.

Issue: User tries to create a S3 connection.

Resolution: Should re-check if the S3Bucket, AccessKey, and SecretKey are filled in.

Cause: The S3Bucket, AccessKey, and SecretKey are mandatory fields for establishing an S3 connection.

4.9.3.2 unable to store secret key, please try again later.

Issue: User tries to create a S3 connection.

Resolution: Create a bug ticket to the ADC team.

Cause: There is a problem storing the Access & Secret Keys in the SSM store.

4.9.3.3 Unable to create the GLUE job, try again later.

Issue: User tries to create a S3 connection.

Resolution: Create a bug ticket to the ADC team.

Cause: There is a problem creating Glue job for the connection.

4.9.3.4 unable to delete secret key, please try again later.

Issue: User tries to create a S3 connection.

Resolution: Create a bug ticket to the ADC team.

Cause: There is a problem deleting the Access & Secret keys from the SSM store.

4.9.3.5 Glue script delete from S3 ETL bucket failed, please verify

Issue: User tries to create a S3 connection.

Resolution: Create a bug ticket to the ADC team.

Cause: There is a problem deleting the Glue script from S3 bucket.

4.9.3.6 In connections.delete_s3_connection, Unable to delete glue job, please verify.

Issue: User tries to create a S3 connection.

Resolution: Create a bug ticket to the ADC team.

Cause: There is a problem deleting the Glue job created for the connection.

4.9.4 External File System Connection Creation (Deprecated)

4.9.### 4.1 Must pass HostOS in ConnectionDetails for ext-fs connection type.

Issue: User tries to create an External File System connection.

Resolution: Should re-check if the Host OS is selected.

Cause: The HostOS is a mandatory field for establishing External File System connection.

4.9.5 External API Connection Creation

4.9.5.1 Connection failed, please ensure that URL and query params passed are valid.

Issue: User tries to create an External API connection.

Resolution: Re-check the URL & query params to be in proper format. If issue still persists, raise a support ticket to the ADC team.

Cause: The URL or query params entered are invalid.

4.9.5.2 Unable to create the GLUE job, try again later.

Issue: User tries to create an External API connection.

Resolution: Create a bug ticket to the ADC team.

Cause: There is a problem creating Glue job for the connection.

4.9.5.3 Failed to update the dynamoDB even after creating the connection object, admin must cleanup this inconsistency.

Issue: User tries to create an External API connection.

Resolution: Create a bug ticket to the ADC team.

Cause: Technical issues with the backend storing the connection details, causing the resources created to be unaccounted for.

4.9.6 Get Connection Details

4.9.6.1 Invalid HostOS - {hostname}.

Issue: User tries to view the details of a particular connection from the UI.

Resolution: Create a bug ticket to the ADC team.

Cause: The host os for which the connection was created is invalid or not supported anymore.

4.9.6.2 User {user_name} is not authorized to view connection details.

Issue: User tries to view the details of a particular connection from the UI.

Resolution: Request the admin to be added the user as an authorized user to this connection.

Cause: The user requesting to view the connection details is neither the creator of it nor was mentioned as an authorized user.

4.9.7 Update Connections

4.9.7.1 Invalid connection id - {}.

Issue: User tries to update an existing connection.

Resolution: Refresh the webpage to see if the connection still exists. If it does, and the problem persists, create a bug ticket to the ADC team.

Cause: The connection which user is trying to update might have been deleted before the update has finished by another authorized user.

4.9.7.2 Unable to update glue connection with error {error_msg}

Issue: User tries to update an existing JDBC connection.

Resolution: Refresh the page and try to update the connection again. If the problem still persists, create a bug ticket to the ADC team.

Cause: Updating glue job definition has failed to aforementioned message.

4.9.7.3 unable to update secret key, please try again later.

Issue: User tries to update an existing S3 connection.

Resolution: Refresh the page and try again. If the problem still persists, create a bug ticket to the ADC team.

Cause: The update failed as it was not able to update the secret key on SSM store due to unknown reason.

4.9.7.4 Failed to update the dynamoDB even after creating the connection object, admin must cleanup this inconsistency.

Issue: User tries to update an existing connection.

Resolution: Bring this to the admin’s attention to cleanup inconsistency.

Cause: The update was successfully completed but the status/metadata of this task was not successfully stored in the backend leaving it in an inconsistent state

4.9.7.5 User {user_name} is not authorized to update connection details.

Issue: User tries to update an existing connection.

Resolution: Request admin to grant you access as an authorized user on the connection to continue with this operation.

Cause: The user trying to update the connection is neither the creator nor an authorized user for the connection.

4.9.8 Delete Connections

4.9.8.1 Unable to delete glue connection with error {error_msg}.

Issue: User tries to delete an existing JDBC connection.

Resolution: Create a bug ticket to the ADC team with the error_msg.

Cause: There was an issue while deleting the glue job with the aforementioned error message.

4.9.8.2 Failed to delete entry in dynamoDB even after deleting the connection object, admin must cleanup this inconsistency.

Issue: User tries to delete an existing connection.

Resolution: Contact the admin so that this inconsistency can be cleaned.

Cause: The connection was successfully deleted but has failed to log it in the backend. This leaves the application with an inconsistent metadata.

4.9.8.3 User {user_name} is not authorized to delete connection.

Issue: User tries to delete an existing connection.

Resolution: Request admin to grant you access as an authorized user on the connection to continue with this operation.

Cause: The user trying to delete the connection is neither the creator nor an authorized user for the connection.