What Are the Possible Causes for an Object Collection Failure?
Object collection can fail for various reasons. Some of the possible reasons are as follows:
- The network to the source database is unavailable.
In this case, restore the network connection between UGO and the source database and re-create an evaluation project.
- The target database could not be verified.
If a namespace is specified in the table creation statement, check whether the namespace exists in the target database. If no, create it.
If a view or function fails to be created, check whether it depends on the target database table. If yes, ensure that the table is successfully created.
Evaluation Project FAQs
- How Do I Select a Connection Method?
- How Does UGO Collect Data from Source Databases?
- How Does UGO Check Database Permissions?
- What Are the Possible Causes for an Object Collection Failure?
- In GaussDB, How Do I Configure a Search Path If A Statement Without Schema Name Fails To Be Executed?
- What Is Native Supported, UGO Supported, Supported with Risk, or Unsupported Objects?
- What Is the Relationship Between Migration Risk (Top 10 risk SQL) and Risky SQL Summary?
- What Are Reconstruction Statistics and How Are Reconstruction Points Measured?
- What Should I Do If An Object Collection Error (Closed Connection) Is Displayed During Evaluation Project Creation?
- What Should I Do If "ErrorCode=4036" Is Displayed During Evaluation Project Creation?
- What Should I Do If "ErrorCode=17002" Is Displayed During Evaluation Project Creation?
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