- 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
- 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?
- How Do I Set GaussDB GUC Parameters?
- 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
Copied.
Creating a Database Audit Task
Scenarios
You want to check whether database objects for audit meet specifications and affect performance
Prerequisites
A data source has been created and connected successfully.
Constraints
- The audited database objects can only be tables, views, sequences, indexes, functions, procedures, triggers, or packages.
- A maximum of 10,000 schemas can be audited at a time.
- During the database audit, do not delete database objects that are being audited, or audit results may be affected.
- If a system template is used, the audit results before and after a version upgrade will be inconsistent. You are advised to use a custom template.
Procedure
- Log in to the UGO console.
- In the navigation pane, choose SQL Audit > Database Audit.
- Click Create Audit Task.
Figure 1 Creating a Database Audit Task
Table 1 Parameter description Parameter
Example Value
Description
Task Name
db_audit_01
Enter a task name, which is mandatory.
The value is a string of 5 to 50 characters, including letters, digits, underscores (_), and hyphens (-). It must start with a letter (case-insensitive) and end with a digit or letter.
Database Type
GaussDB
Select a database type. Only the GaussDB database is supported. This parameter is mandatory.
Data Source
app_db_01
Select a data source. Currently, only GaussDB is supported. This parameter is mandatory.
If there is no available data source, click Create Data Source.
Schema
demo_schema_01
Select a schema. This parameter is optional and only available for GaussDB databases.
- If this parameter is not specified, all schemas are audited by default. However, up to 10,000 schemas can be audited.
- If the parameter is specified, you can select up to 10,000 schemas.
Rule Template
baseline_template_01
Select a template based on the selected database type.
You can set the template information by referring to Adding a Rule Template.
Description
Audit task for service database objects
Enter a task description, which contains up to 100 characters. This parameter is optional.
- Click OK. The task is displayed in the list.
If a running task is terminated due to a database exception, you can click Retry.
- If the task is terminated during object collection, delete the collected objects and reconnect to the database to collect objects after the retry.
- If the task is terminated during an audit, the audit will be resumed after the retry.
Figure 2 Audit task listThe task status can be:
- Pending: The database audit task is to be scheduled.
- Collecting objects: DDL statements in the schema of a specified database.
- Auditing SQL statements: The database is being audited.
- Audit completed: The database audit is complete only after all database objects are audited.
- Audit failed: An exception occurred during the audit.
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