Assess an Oracle database

In the assessment of an Oracle database, objects and SQL statements are assessed, and the database profiling is performed. You can select the required assessment type by specifying the analyze-types parameter.

Prerequisites

OceanBase Migration Assessment (OMA) is installed. For more information, see Install OMA.

Run the assessment command

Go to the installation directory of OMA and run start.sh with reference to the following sample statement. For more information about the parameters in the statement, see Product form. In Microsoft Windows, replace sh bin/start.sh with start.bat.

sh bin/start.sh \
# The task name, which can be set to any value.
--name TOTAL_TEST \
# The assessment mode. ANALYZE_TOTAL indicates a database assessment.
--mode ANALYZE_TOTAL              \
# The assessment type. Valid values: OBJECT, SQL, and PORTRAIT. OBJECT indicates the assessment of objects. SQL indicates the assessment of SQL statements. PORTRAIT indicates the generation of a database profile.  
--analyze-types OBJECT,SQL,PORTRAIT  \
# The data source. DB indicates a database.
--from-type DB \                 
# The assessment mode.
--evaluate-mode SOURCE_TARGET \  
# The type of the source database.
--source-db-type ORACLE \        
# The version of the source database.
--source-db-version 11g \  
# The address of the source database.      
--source-db-host xxx.xxx.xxx.xxx \    
# The port of the source database.       
--source-db-port port \     
# The username of the source database.     
--source-db-user username \
# The password of the source database.            
--source-db-password password \         
# The service name of the source database. This parameter can be replaced with --source-db-sid, which indicates the SID.
--source-db-service-name orcl11g.us.oracle.com \
# The type of the target database.
--target-db-type OBORACLE \ 
# The version of the target database, including 2.2.50, 2.2.70, 3.1.20, 4.2.x, and 4.3.5. 
# 2.2.50 represents the 2.2.5x versions; 2.2.70 represents the 2.2.7x versions; 3.1.20 represents the 3.1.x versions; and 4.2.x represents 4.2.0, 4.2.1, 4.2.2, and 4.2.5. 
--target-db-version 4.3.5 \ 
# The schema that needs to be assessed. If not filled in, all Schemas will be assessed by default.
--schemas OBDBA,DATAX,DC01,CBS,FUND,TEST

After you run the preceding commands, you can view the progress in real time.

View an assessment report

After the assessment is completed, OMA generates an assessment report in the .pdf format in the report directory and an assessment report in the HTML format in the reportTool directory.

View the assessment report in the .pdf format

To view the assessment report in the .pdf format, go to the report directory and open the PDF file of the name in the path displayed in the CLI.

View the assessment report in the HTML format

To view the assessment report in the HTML format, perform the following steps:

1. Go to the reportTool directory, double-click the index.html file.

2. On the page that appears, click Authorize and View Report.

3. Select and open the oma.sqlite file.

   Generally, the oma.sqlite file is stored in the db folder under the root directory of OMA.

4. On the page that appears after you open the oma.sqlite file, click Select Report in the upper-right corner and select the migration assessment report that you want to view from the drop-down list.

   On the migration assessment page, you can click the SQL Assessment Overview or Object Assessment Overview tab, or Database Profile to view more information.

   • SQL Assessment Overview

     On this tab, you can view information in the SQL Compatibility and Summary of SQL Incompatibilities sections.

   • Object Assessment Overview

     On the Object Assessment Overview tab, you can view information in the General Compatibility and Compatibility Details sections.

   • Database Profile

     You can click Database Profile in the upper-right corner of the page to view more information in the Database Instance Overview, Special Business Statistical Tables, Special SQL Statement Statistical Tables, Data Volume Analysis, and Abnormal SQL Statements in Original Database sections.

     Special business statistical table	Description
     Tables Without Indexes	The tables without indexes.
     Tables Without Visits	The tables that were not read or written during the assessment.
     Tables Without Primary Keys	The data tables without primary keys or non-null unique keys.
     Tables Without Updates	The tables that were not updated during the assessment.
     Large Data Tables	The tables that have more than 1 million rows each.
     Frequently Accessed Tables	The tables that experienced more than 10,000 reads or writes per second.
     Tables With High Growth	The tables that experienced more than 1,000 rows of writes per second.