Demo presentation text:
Hello! Let me show you the presentation of the migration tools provided by Ispirer Systems for the Oracle to Db2 AS/400 database migration.
First of all I’d like to mention that Ispirer Systems provides tools and services for automating the database and application migration processes for a variety of conversion directions. The list of tools supplied for such kind of automation is as follows:
SQLWays Wizard – a GUI tool that is designed to simplify the database conversion process tuning for the SQLWays command-line tool. Works with the source database using the ODBC connection.
SQLWays Studio – a GUI tool that is designed to simplify the database or application script conversion process tuning for the SQLWays command-line tool. Works with one script at a time.
SQLWays Commander - a GUI tool that is designed to simplify the database or application scripts conversion process tuning for the SQLWays command-line tool. Works with several scripts at a time.
Sqlways.exe – a command line tool that can be run in a batch mode and can perform the automatic conversion of the database using the ODBC connection or the database and application code provided in scripts.
In this demo I will show you the Oracle to Db2 AS/400 migration using SQLWays Wizard, SQLWays Studio and SQLWays Commander Tools mentioned in the list provided.
First let’s start with SQLWays Wizard.
This is the tool that can connect to the Oracle database using the ODBC connection only. So, to migrate from Oracle to Db2 AS/400 database, you need to provide the ODBC DSN for Oracle on the “Choose a Source Database” page. Also you need to specify a user and a password with the appropriate rights for making selects from systems tables from Oracle.
On a “Choose a Target Database” page you need to choose the target database from the list of the supported databases. As you can see the Db2 AS/400 database is specified here. You also need to provide other credentials for the Db2 AS/400 database for a support of definitions and data load using native utilities of this database.
All the objects that SQLWays manages to extract from the Oracle it depicts in a tree view on the “Specify Database Objects or Query” page. Here you can select all the objects required for the migration.
After that you can specify different options for automatic Oracle to Db2 AS/400 conversion, like option that controls the schema name conversion, reserved words conversion, data types conversion, identifier names conversion and etc. Also there are options that can help you to run the definitions and data migration in separate processes.
On the “Specify Export File Options” page you need to provide the directory, which serves as an intermediate repository for the whole migration process and stores all the automatically generated files, like SQL files with the converted definitions of the objects, TEXT files with the data prepared to be loaded into the target database, BAT or SH files with the commands for native utilities to load both definitions and data on Windows or on Unix like OS.
All the Oracle to Db2 AS/400 migration process is performed in two steps. Each of them has separate logging information.
For the Export process there are provided the sqlways.log files with the information about: the objects read from the Oracle database, their number, number of rows of data and the size of the data per each table extracted, the number of lines of code (LOC) per each business logic objects, like views, synonyms, stored procedures, functions, triggers, packages and etc. At the end of the export log file there is a summary information per each object type regarding the number of objects, the common size of data, number of rows of data or lines of code, depending on the object type, the export status regarding whether there were any failures or no during the export process and the Total information for the whole database export.
Similar information but in more readable format is provided in the sqlways_report.html file. There is a summary table with the complete export status and statistics per each object type and there are also tables with the list of objects and more detailed statistics for each object extracted from Oracle database.
As for the import process, SQLWays generates a sqlways_imp.log file for the import in the DB2 AS/400 database that contains information about what object is being loaded and whether there are any issues during the import process or no.
Now let’s turn to the SQLWays Studio and SQLWays Commander tools that are designed for database scripts and application scripts conversion purposes.
In SQLWays Studio to convert from Oracle to Db2 AS/400 all you need to do is to provide the conversion direction using the “Source” and “Target” options, place the source Oracle code to the right pane of the tool and Run the conversion. At the bottom of the tool you can see the log of the conversion process that shows if there are any errors during the script conversion from Oracle to DB2 AS/400 database. After the conversion you can compare both source and target scripts in the tool side-by-side for your convenience.
In SQLWays Commander there are also two panes which give you the opportunity to specify the file or files or the whole directory for the conversion. So, to convert from Oracle to Db2 AS/400 you just specify the source and target from the list of supported databases, specify the files for conversion and click Run. When you specify the directory for the conversion you also need to provide the template for the files that you would like to convert from Oracle to Db2 AS/400 database and provide the target directory. At the bottom there is generated the conversion log with the information about conversion issues if any. After the conversion by double-clicking the file in the source and in the target pane you can review the conversion results side-by-side like in SQLWays Studio.
OK. This is all information I’ve got for this demo. The information about the peculiarities for Oracle to Db2 AS/400 migration and the information about other tools that Ispirer Systems provides for the databases migration support will be described in our next demos or can be found on our website.
Thank you very much for your attention. Bye.