All Products
Search

This Product

    Database Autonomy Service:FAQ and error codes for traffic playback

    Document Center

    Database Autonomy Service:FAQ and error codes for traffic playback

    Last Updated:Mar 28, 2026

    This document covers common questions and error codes for the traffic playback feature in Database Autonomy Service (DAS).

    FAQ

    How do I create a service-linked role?

    In the Resource Access Management (RAM) console, create the AliyunServiceRoleForDAS role. For step-by-step instructions, see Create a service-linked role.

    What are the credentials for the ECS instance that DAS automatically purchases?

    The username is root. The password is cloudbench@ followed by the first eight characters of the traffic playback task ID.

    To find the task ID, check the name of the Elastic Compute Service (ECS) instance DAS purchased. Instance names follow the format traffic-playback-<traffic playback task ID>-do-not-delete-******. For example, if the instance name is traffic-playback-98a2e6f7-de2a-******-do-not-delete-******, the root password is cloudbench@98a2e6f7.

    SQL statements are truncated during playback — how do I fix this?

    Increase the SQL log length limit by modifying the parameter in your database:

    • MySQL 5.6 and 5.7: loose_rds_audit_max_sql_size

    • MySQL 8.0: loose_rds_audit_log_event_buffer_size

    Note the following limits:

    • The change applies only to subsequent SQL statements. Historical archived statements are not affected.

    • This is a session-level parameter. It does not take effect for existing persistent connections — close and re-establish those connections after the change.

    • Traffic playback supports SQL statements up to 8,192 bytes. Statements larger than this limit cannot be played back regardless of the parameter value.

    Playback progress has stopped updating — what should I check?

    Run the following commands on the ECS instance to diagnose the issue:

    • Check whether the playback process is running:

      ps -aux | grep "dbgateway.*cmd*"

    • View the latest log entries for the task:

      tail /mnt/das/cloudbench/{task ID}.log

    Replace {task ID} with your actual traffic playback task ID.

    Error codes

    The following tables list error codes grouped by category to help you locate the relevant area quickly.

    General errors

    Error codeDescription
    1010001Traffic playback is not supported in this region.
    1010002The traffic playback type is not supported.
    1010003The traffic playback version is not supported.
    1010004The task timed out.
    1010900An unknown internal error occurred.

    Agent errors

    Error codeDescription
    1010005The system agent failed to send the instruction.
    1010006The user agent does not exist. Check the running status of the agent.
    1010007The user agent version is not supported. Upgrade the agent.
    1010008The user agent failed to execute the instruction. Check the running status of the agent.

    Permission errors

    Error codeDescription
    1010009The account does not have the service-linked role for DAS. Create the AliyunServiceRoleForDAS role.
    1010101Incorrect username or password for the source instance.
    1010102Incorrect username or password for the target instance.

    Configuration errors

    Error codeDescription
    1010103The queries per second (QPS) of the source instance is too low. Confirm that the source instance has active service traffic.
    1010105The database to be played back is missing from the target instance.
    1010106The number of selected databases for playback exceeds the limit. Play back traffic from all databases without filtering.
    1010107The configuration of the target instance is incorrect. Enable 7-day log indexing and SQL Explorer on the target instance.
    1010108The configuration of the source instance is incorrect. Enable cold data storage and SQL Explorer on the source instance.
    1010109The traffic playback time is earlier than the effective time of SQL Explorer or cold data storage for the source instance.
    1010110The target instance is in an abnormal state. Check whether the target instance is running.
    1010112The time range for the task is configured incorrectly. The duration must be longer than 5 minutes and shorter than 24 hours, and the time range must fall within the last 30 days.

    Environment and resource errors

    Error codeDescription
    1010104ECS instances with the preset specifications are out of stock in this region. Prepare your own ECS instance.
    1010111Failed to prepare the ECS environment required for traffic playback.
    1010201Failed to create the target instance. Make sure the source instance is in the Normal state, or select an existing instance for playback.
    1010202Failed to create an ECS security group.
    1010203The Virtual Private Cloud (VPC) where the target instance resides does not have a vSwitch. Create a vSwitch and retry.
    1010204The ECS instance failed to connect to the target database instance. Check the whitelist configuration of the target instance.
    1010208The ECS instance has insufficient disk space. Delete unnecessary files and retry.
    1010212Failed to download the executable file required for traffic playback. Retry the operation.
    1010213The file or folder does not exist on the ECS instance. Check whether the file or folder exists.
    1010214The ECS instance was not found. Check whether the instance status is Normal.

    SQL file processing errors

    Error codeDescription
    1010205The archived SQL file has expired or does not contain service traffic SQL.
    1010206An error occurred during SQL file archiving.
    1010207Failed to download the archived SQL file.
    1010209Failed to merge the archived SQL files.
    1010210Failed to parse the archived SQL files.
    1010211Failed to load the parsed SQL files into the cache.
    1010215The generation of the traffic playback comparison report timed out.