How Do I Solve ERROR: syntax error at or near "@"?
Symptom
Causes
The enable_set_variables parameter is not configured.
Solution
Method 1: Configuring the value of enable_set_variables and applying the new value in a specified database
- Connect to the database as the root user.
- Run the following command to configure the enable_set_variables parameter:
alter database databasename set b_format_behavior_compat_options = 'enable_set_variables';
Method 2: Configuring the value of enable_set_variables and applying the new value in a specified instance
- Connect to the instance as the root user.
- Run the following command to switch to the instance user:
su - omm
In the preceding command, omm"indicates the instance user. Change it based on the site requirements.
- Run the following command to set the instance parameters:
gs_guc reload -Z datanode -N all -I all -c "b_format_behavior_compat_options='enable_set_variables'";
Migration Project FAQs
- Why Is There No Available Evaluation Project During Migration Project Creation?
- When Should I Use the Conversion Config Function?
- What Should I Do If SQL Modifications Failed to Be Saved During Object Correction?
- Why Is a Name Error Reported During Database Migration?
- How Do I Solve ERROR: syntax error at or near "@"?
- What Is the Impact of the Migration on the Source Database?
- What Are the Impacts of GUC Parameter Settings of GaussDB on Migration?
- Why Is the Number of Indexes Different After Oracle Data is Migrated to GaussDB?
- What Should I Do If There Are ctid, xc_node_id, and tableoid Columns in GaussDB?
- Why Is Data Inconsistent When SELECT Statements Without ORDER BY Are Used for Query in Distributed GaussDB?
Feedback
Was this page helpful?
Provide feedbackThank you very much for your feedback. We will continue working to improve the documentation.See the reply and handling status in My Cloud VOC.
For any further questions, feel free to contact us through the chatbot.
Chatbotmore