Help Center>
Database and Application Migration UGO>
FAQs>
Migration Project>
Why Is a Name Error Reported During Database Migration?
Updated on 2023-07-25 GMT+08:00
Why Is a Name Error Reported During Database Migration?
Symptom
When DB2 for LUW is used as the source database and GaussDB is used as the target database, an error similar to the following picture is reported during object correction.
Causes
DB2 for LUW supports variables in DECLARE statements with same name followed by a different number of spaces, UGO does not support this scenario for conversion to GaussDB.
Solution
Manually delete redundant spaces during object correction.
Parent topic: Migration Project
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?
- What Should I Do If Migration & Verification Failed to be Performed?
- 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.
The system is busy. Please try again later.
For any further questions, feel free to contact us through the chatbot.
Chatbotmore
