- What's New
- Service Overview
- Getting Started
-
User Guide
- Database Evaluation
- Object Migration
- SQL Statement Conversion
- Conversion Configuration
- SQL Audit
- Data Source Management
- Permissions Management
- Interconnection with CTS
- Change History
- Best Practices
- Security White Paper
-
API Reference
- Before You Start
- API Types
- Calling APIs
-
API
- API Version Management
- Quota Management
- SQL Statement Conversion
- Evaluation Project
-
Migration Project
- Creating a Migration Project
- Querying Migration Projects
- Querying the Status of a Migration Project
- Checking Target Database Permissions
- Querying Permission Check Results
- Querying Migration Project Details
- Submitting Syntax Conversion of Objects
- Querying Syntax Conversion Progress of Objects
- Submitting Verification
- Querying the Verification Progress
- Downloading a Migration Error Report
- Deleting a Migration Project
- Permissions Policies and Supported Actions
- Appendixes
- SDK Reference
-
FAQs
-
Product Consulting
- Instance Freezing, Release, and Deletion
- Which Schemas in Source Databases Are Ignored for Migration?
- What Are the Differences Between Syntax Conversion and Migration & Verification in a Migration Project?
- What Are the Database Schema Changes After an Oracle Database Is Migrated to the Target Database?
- Why Cannot I Use Some Functions?
- What Is the Function of the dsc_ora_ext Schema Generated After Migration to the Target Database?
- What Should I Do If Data Collection Fails or Is Slow Due to the Small Values of Certain Oracle SGA Parameters?
- What Should I Do If Data Collection Fails and a Message SNAPSHOT TOO OLD Is Displayed?
- What Is the Mapping Between the GaussDB Versions Displayed on the UGO Console and Self-built GaussDB Versions?
- What Are VPCEP Resource Quotas?
-
Database Connections
- What Should I Do If I Cannot Connect to the Source Oracle Database During Database Evaluation Project Creation?
- What Should I Do If I Failed To Connect to the Source Database as User sys?
- How Do I Create GaussDB Databases Compatible with Source Databases?
- What Should I Do If My Database Fails to be Connected?
- SQL Server Connection Test Failed (Error Code=0, SQLState=08S01)
-
Evaluation Project
- 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 Compatibility, Conversion Compatibility, Partial Compatibility, or Incompatibility?
- 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?
- What Do I Do If the Assessment Task Is Connected but the Pre-check Fails?
- What Is the Impact of the Collection on the Source Database?
-
Migration Project
- 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?
- How Do I Solve ERROR: syntax error at or near "@"?
- What Are the Possible Causes for an Object Verification Failure?
- 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?
-
Product Consulting
- Videos
- General Reference
Show all
Copied.
Viewing File Details
Scenarios
You can view details about the uploaded SQL files.
Prerequisites
A file has been uploaded.
Procedure
- Log in to the UGO console.
- In the navigation pane on the left, choose SQL Audit > Statement Audit. Click the SQL from Files tab.
- Locate a task and click View Details in the Operation column to view the SQL file audit information and collected SQL statements.
- Export SQL: Select one or more SQL statements to be exported and click Export SQL to export them to a .tar.gz file.
- By default, all SQL statements are exported. You can also select SQL statements to export, or set search criteria to export desired ones.
- By default, The exported Excel file contains existing SQL statements is selected. If the existing SQL statements are too large, do not select this option.
- If the existing SQL statements in the exported file are too large, save them in a separate file whose name will be displayed in the SQL Statement column in the Excel file.
- You can export a maximum of 5,000 objects to an Excel file.
- If the table structure information which the SQL statement to be audited depends on contains more than 30,000 characters, it is exported as a SQL file.
- In the File Audit Information area, you can view the file name, audit status, and data source information.
- In the SQL Statements area, you can view SQL ID, SQL statement, description, risk level, and status.
Figure 1 Audit details
- Click the value next to Rule Template to view the specific template information.
- The status can be:
- New: The collected SQL statement is waiting for audit.
- Completed: The audit is complete.
- Analyze_error: Failed to parse SQL statements.
- Error: An exception occurred during the audit.
- Ignore: The SQL statement cannot be audited or the size of a single SQL statement exceeds the threshold. The default threshold is 100 KB.
- Parsing failure cause:
- line:1, position:14, token:table indicates the SQL statement contains table.
- line:1, position:3, token:<EOF> indicates that the SQL statement is incomplete.
- Export SQL: Select one or more SQL statements to be exported and click Export SQL to export them to a .tar.gz file.
- Locate a SQL statement and click View Details in the Operation column to display the basic information, violated rules, and table structure of the SQL statement.
- If multiple SQL statements are collected, you can click Previous or Next.
Figure 2 Viewing SQL audit details
- Basic Information: The specific SQL statement and description are displayed.
- Violated Rules: Based on the selected rule template, the system provides the violated rule name, risk level, and suggestions.
Click the content in the Problem Segment column to highlight the problem segment in the text. To cancel the highlight, click the content again. The PL/SQL code may have multiple problem fragments. Click on the left to display all problem fragments.
- Unmatched Rules: The rules related to the source database are not matched because: no data source is selected, the data source connection fails, the user permission is insufficient, the schema is incorrectly selected, or the table is not found. The displayed information includes the rule name, risk level, and unmatched reason.
- Table Structure: Based on the selected rule template, the system provides the table structure information that the SQL statement to be audited depends on, including the object name, object type, and owner.
- Execution Plans: The execution plans of the SELECT, UPDATE, DELETE, and INSERT statements are displayed.
NOTE:
To obtain the table structure, you must have the permissions to read system catalogs and system views.
GaussDB system catalogs: tables, pg_class, pg_namespace, relnamespace, pgxc_class, pg_settings, pg_get_viewdef, columns, pg_tables, pg_index, table_constraints, pg_partition, pg_get_tabledef, check_constraints, key_column_usage, pg_get_keywords, gs_package, db_constraints, and adm_ind_columns.
MySQL system catalogs: information_schema.tables, information_schema.columns, information_schema.statistics, and information_schema.table_constraints.
- If multiple SQL statements are collected, you can click Previous or Next.
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.
Chatbot