Function

runDSC.sh or runDSC.bat is used to migrate Teradata, Oracle, Netezza, MySQL, DB2 schemas and queries to GaussDB A and GaussDB(DWS).

Format

Linux:

./runDSC.sh
--source-db<source-database> 
[--input-folder<input-script-path>] 
[--output-folder<output-script-path>]
[-application-lang <application-lang>] 
[--conversion-type<conversion-type>] 
[--log-folder<log-path>] 
[--version-number <Gauss Kernel Version>] 
[--target-db<target-database>

Windows:

runDSC.bat
--source-db<source-database> 
[--input-folder<input-script-path>] 
[--output-folder<output-script-path>]
[-application-lang <application-lang>] 
[--conversion-type<conversion-type>] 
[--log-folder<log-path>] 
[--version-number <Gauss Kernel Version>] 
[--target-db<target-database>

Parameter Description

Usage Guidelines

It is mandatory to specify the source database, input folder path, and output folder path, and optional to specify the migration type and log path.

If no log path is specified, DSC creates the log folder under TOOL_HOME to store logs.

Example

./runDSC.sh --source-db Oracle --input-folder opt/DSC/DSC/input/oracle/ --output-folder /opt/DSC/DSC/output/ --log-folder /opt/DSC/DSC/log/ --application-lang SQL --conversion-type bulk --targetdb gaussdbT

System Response

********************** Schema Conversion Started *************************
DSC process start time : Mon Jan 20 17:24:49 IST 2020
Statement count progress 100% completed [FILE(1/1)]

Schema Conversion Progress 100% completed
************************************************************************** 
Total number of files in input folder : 1
************************************************************************** 
Log file path :....../DSC/DSC/log/dsc.log
DSC process end time : Mon Jan 20 17:24:49 IST 2020
DSC total process time : 0 seconds
********************* Schema Conversion Completed ************************

If there is no sql file present in the input folder, then the following message is displayed in console:

Environment Creation and Restoration Procedure (database and database user)

GaussDBA - DB Creation and Schema Setup

1. Log into postgres :

   gsql -p <port> -d postgres 
   drop database <database name>;
   create database <database name>;
   \c <database name>
   GRANT ALL PRIVILEGES ON DATABASE <database name> TO <user>;
   grant database to <user>;\q
   gsql -p <port> -d <database name> -U <user> -W <password> -h <IP> -f
   drop database <database name>;
   create database <database name>;
   \c <database name>;
   GRANT ALL PRIVILEGES ON DATABASE <database name> TO <user>;
   gsql -p <port> -d <database name> -U <user> -W <password>  -f

2. Run all files in setup.

Commands:

sh runDSC.sh -S oracle -M blogic -I <input path>
sh runDSC.sh -S oracle -M bulk -I <input path>

Post Migration Verification

After DSC converts the source sql files, execute the converted files on target gaussdb and provide a report with details of number of statements succeeded and failed.

After the DSC finishes the translation, it will invoke (controlled through a configuration item) post migration verification script.

The post migration verification script will connect to the target gauss database (details are configured in a configuration file) and executes the scripts.

1. application.properties in config folder

   Execute migrated script on Gauss DB: true/false, default value = false

   executesqlingauss=true

   true: It will execute the migrated script on gaussdb

2. gaussdb.properties in config folder

   #Target Database configurations

   #gauss database user with all privileges 
   gaussdb-user= 
   gaussdb-port= 
   #Database name for GaussDBA 
   gaussdb-name= 
   #gaussdb ip 
   gaussdb-ip=

   Dependency with gsql client:

   1. To make the verification tool to work, it is required to execute the DSC tool with a user having the permission to execute gsql/zsql commands on the node where the Gauss DB instance or client (gsql) is installed, since the dependency on gsql (Gauss A) for executing the scripts on Gauss DB.
   2. Since the Gauss DB Instance/Client can be installed on a linux OS only, this can be used to verify functionality only on a linux environment.
   3. To execute the gsql command on a remote GaussDB instance, it is recommended to add the client system IP/hostname in the following configuration file of Gauss DB instance.

      /home/gsmig/database/coordinator 
      ---pg_hba.conf

Response

GaussDB A

********************** Verification Started ******************************
Sql script execution on Gauss DB start time : Wed Jan 22 17:27:07 CST 2020
Sql script execution on Gauss DB end time : Wed Jan 22 17:27:44 CST 2020

Summary of Verification :
==================================================================================================================================
Statement                | Total               | Passed              | Failed              | Success Rate(%)
-----------------------------------------------------------------------------------------------------------------------------------
COMMENT                  | 15                  | 15                  | 0                   | 100
CREATE VIEW              | 4                   | 3                   | 1                   | 75
CREATE INDEX             | 4                   | 3                   | 1                   | 75
CREATE TABLE             | 6                   | 6                   | 0                   | 100
ALTER TABLE              | 3                   | 3                   | 0                   | 100
---------------------------------------------------------------------------------------------------------------------------------
Total                    | 32                  | 30                  | 2                   | 93

Gauss Execution Log file : /home/gsmig/18Jan/DSC/DSC/log/gaussexecutionlog.log
Gauss Execution Error Log file : /home/gsmig/18Jan/DSC/DSC/log/gaussexecutionerror.log
Verification finished in 38 seconds

********************** Verification Completed ****************************