An SQL file parsing task is created based on the selected source traffic, and the traffic is organized into a file for replay. This topic describes how to create an SQL file parsing task.
Prerequisites
Before you create an SQL file parsing task, you need to obtain audit logs from the corresponding source database.
When you select Source Database Type as Aurora MySQL, AWS_MYSQL, RDS_MYSQL, POLAR_MYSQL, or GCP_MYSQL, see Obtain traffic files from database instances for details.
When you select HUAWEI_RDS_MySQL as the Source Database Type, see Enable SQL audit log for details.
When you select HUAWEI_DWS as the Source Database Type, see Dump database audit logs for details.
Limitations
Only users with the roles Project Admin and Data Service Admin can create SQL file parsing tasks.
Performance assessment only supports parsing files from the source database.
Procedure
Create an SQL file parsing task.
Log on to the OceanBase Cloud console.
In the left-side navigation pane, click Data Services > Migrations.
On the Migrations page, click the Assess Performance tab.
On the Assess Performance tab, choose Create > SQL File Parsing in the upper-right corner.
On the Set Up Source Database page, configure the parameters.
Parameter Description Assessment Task Name Enter a custom name for the assessment task, which cannot exceed 30 characters in length. Cloud Vendor Select AWS, HUAWEI, ALIYUN, and Google Cloud from the drop-down list. Source Database Type - If Cloud Vendor is AWS, the source database type supports Aurora MySQL and AWS_MYSQL.
- If Cloud Vendor is HUAWEI, the source database type supports HUAWEI_RDS_MySQL and HUAWEI_DWS.
- If Cloud Vendor is ALIYUN, the source database type supports RDS_MYSQL and POLAR_MYSQL.
- If Cloud Vendor is Google Cloud, the source database type supports GCP_MYSQL.
Region The region of the source database. Source Database Instance When Source Database Type is as Aurora MySQL, AWS_MYSQL, HUAWEI_DWS, RDS_MYSQL, POLAR_MYSQL, or GCP_MYSQL, enter the source database instance first. For more information, see Obtain database instance.
Separate multiple database instances with commas (,).Source Database This parameter is only displayed when Cloud Vendor is set to Google Cloud. Click Next. On the Configure Data Collection page, configure the parameters.
If the source instance type is Google Cloud, Data Collected From only supports Import Object Storage (Google Cloud Object Storage).
If the source instance type is AWS, Data Collected From supports S3 Import and Upload File.
If the source instance type is ALIYUN, Data Collected From supports Import Object Storage (OSS) and Upload File.
If you choose to save the audit logs of the Aurora MySQL instance, AWS MySQL instance, or the traffic files of Alibaba Cloud Log Service (SLS) to Amazon S3, Google Cloud Storage (GCS), or Alibaba Cloud OSS, select S3 Import or Import Object Storage (OSS) to import the audit logs for assessment. For more information about how to obtain the audit logs of the MySQL instance, see Prerequisite operations.
Note
We recommend that you create a dedicated user for the migration assessment service and grant only the necessary permissions to the bucket. For more information about the Alibaba Cloud account system, see Access Control.
Parameter Description AccessKey ID Enter the Access Key ID for accessing Amazon S3, Google Cloud Storage (GCS), or Alibaba Cloud OSS. For more information about the Access Key ID of Amazon S3 or GCS, see Create an access key. For more information about the Access Key ID of Alibaba Cloud, see Create an Access Key. AccessKey Secret Enter the Access Key Secret for accessing Amazon S3, Google Cloud Storage (GCS), or Alibaba Cloud OSS. S3/OSS Bucket Enter the name of the S3 or OSS bucket into which the audit logs are imported. Bucket for File Import Enter the name of the GCP bucket into which the audit logs are imported. This parameter is displayed only when the source instance type is Google Cloud. File Directory Enter the directory to which the audit logs are delivered. Traffic Collection Time Range Select the time period for assessment. The maximum time period is 24 hours.
If no data is collected during the specified time period, no log files are generated during the specified period.Click Verify. After the verification succeeds, parsable files are displayed in Valid File List.
If you choose to save the audit logs of the Aurora MySQL instance, AWS MySQL instance, or the traffic files of Alibaba Cloud Log Service (SLS) to a local server, or if the source instance type is HUAWEI or ALIYUN, select the Upload File method to manually import ZIP or GZ files for assessment. Note that the maximum size of a single file is 5 GB.
Click Next.
After the task passes the precheck, click Start to launch the SQL file parsing task.
After the task starts, you can view the assessment report on the Task List page. For more information, see View an assessment report. If a file is parsed in a separate parsing task, you can view the file parsing record by choosing Assess Performance > Parse files.