All Products
Search

This Product

    Data Management:Data change

    Document Center

    Data Management:Data change

    Last Updated:Mar 28, 2026

    This page covers solutions to common errors when submitting data change tickets in DMS.

    SQL statement blocked by security rules

    Error message example:

    Failed to pass the SQL statement type check. According to security rules, forbid execute directly, command type:INSERT, please contact DBA or administrator adjust! To modify the rule, choose Security and disaster recovery (DBS) > Security Rules > Edit > SQL Correct > SQL Execution Rules., Not matched any rules of the command type, default forbid execute.

    Cause: The security rule bound to the database (managed in Secure Collaboration mode) blocks the SQL statement from being executed or submitted.

    Which case applies to you?

    • KNOWN statement — DMS can identify the statement type, but the current security rule blocks it by default.

    • UNKNOWN statement — DMS cannot identify the statement type.

    KNOWN statement

    DMS identified the statement in the error message, but the security rule prohibits it by default. Contact your DBA or DMS administrator to update the rule.

    Step 1: Find the security rule set name.

    Go to the Data Change Ticket Details page and click Operation Logs in the upper-right corner. Note the name of the security rule set.

    Step 2: Update the security rule.

    1. Log on to the DMS console V5.0.

    2. In the top navigation bar, choose Security and disaster recovery (DBS) > Security Rules.

    3. On the Security Rules tab, find the security rule set and click Edit in the Actions column.

    4. In the left-side navigation pane, click SQL Correct.

    5. For Checkpoints, select the option that matches the error message. For the example above, select SQL execution rules.

    6. Find the security rule to modify and click Edit in the Actions column.

      Select the rule based on the SQL statement type shown in the error message. For example, if the error message shows CREATE_INDEX, select a DDL-related security rule.

    7. Add the SQL statement type from the error message to the DSL syntax for the security rule. For example, if CREATE_INDEX is blocked, add it to the DDL syntax as shown below.

      SQLchange-intl

    8. Click Submit.

    Step 3: Retry the precheck.

    On the ticket details page, click Retry in the Precheck section. DMS re-evaluates the statement type against the updated rule.

    UNKNOWN statement

    DMS cannot identify the statement type. First, check whether the SQL statement itself is correct.

    If the SQL statement is incorrect:

    1. Click Modify SQL in the Precheck section.

    2. Correct the statement and confirm the change.

    3. Click Retry to run the statement type check again.

    If the SQL statement is correct:

    1. Click View Details in the Precheck section to view the statements flagged as UNKNOWN.

    2. Contact your DBA or DMS administrator. Ask them to add the UNKNOWN statement to the security rule and allow DMS to execute it.

    3. After they submit the change, click Retry.

    For more information about how to modify a security rule, see Modify a security rule.

    Syntax check failed when checking affected rows

    Error message example:

    Failed to check the number of affected rows. Syntax check failed. Error message: ERROR. pos 37, line 1, column 31, token WHERE.

    Cause: During the Precheck step, DMS checks the number of scanned rows to verify whether the syntax of the SQL statement is correct.

    If the SQL syntax is incorrect:

    Fix the syntax error and click Retry in the Precheck section. DMS reruns the scanned-rows check.

    If the SQL syntax is correct:

    Click Skip to the right of Check the number of scanned rows in the Precheck section. DMS ignores this check and continues processing the ticket.