MEET DB2 - Migration Enablement Evaluation Tool for DB2

Table of Contents

About MEET DB2

MEET DB2 evaluates the degree to which DB2 will natively support the procedural logic and data definitions used in an Oracle or Sybase database.

Source procedural SQL and DDL from input files are processed by MEET DB2 to determine which statements and objects found are immediately transferable to DB2. All incompatibilities that are found are identified in a report that provides both summary information as well as detailed technical information about each incompatible feature.

MEET DB2 will also report the line number of every source code attribute it identifies that requires modification in order to execute normally with DB2.

Migrating a database from Oracle to DB2 is often the major technical effort for enabling a system to run on DB2, and therefore the MEET DB2 report can provide a robust assessment of the effort required to move to DB2. However, note that enabling to DB2 may not be the only technical challenge, and in some cases other barriers that MEET DB2 does not evaluate may dominate.

Installation and usage

Syntax of the input file

MEET DB2 expects valid syntax in the input source file. The input should be a text file containing procedures and/or data definitions that are actually executable either on a Sybase system, or in SQL*Plus on an Oracle system. If completely invalid syntax is encountered the MEET DB2 utility will report an unrecoverable parse error.

MEET User Authentication

System Requirements

Installation

To install MEET DB2 simply copy the files from the MEET DB2 download archive.

Usage

Note: MEET DB2 does not require DB2, Oracle or Sybase to be installed. All you need is the source for the objects which can be extracted with the IBM Data Movement Tool or other utilities like TOAD for Oracle, or Sybase PowerDesigner or DB Artisian for Sybase. For Oracle the source input should have all objects terminated with a forward slash "/". For Sybase the source input should contain the keyword "go" separating SQL batches or statements.

License and Notices

License and notices are stored in and can be viewed in the "license" directory.

Feedback

Send any comments to: meetdb2@torolab.ibm.com


Oracle Mode

Syntax of the Input File

The source input should have all objects terminated with a forward slash "/".

General Info

The set of database characteristics that MEET DB2 examines includes:

Other enablement evaluation considerations

MEET will not report syntax constructions that will be automatically corrected by the IBM DMT tool.

All Execute Immediate statements will be only partially evaluated and require review.

Special attention should be paid to the use of:

File Splitting Utility

Known Limitations

Supported but unrecognized

The following language constructs are supported by DB2 but currently being reported by MEET DB2 as unrecognized syntax:

Unrecognized and will not be supported by DB2 9.7

The following are features currently not reported on

The following are reported as unrecognized and need to be added to the unsupported report:

DDL Limits

The following are not evaluated at this time:

When manual evaluation is required

MEET will print informational messages for functionality that needs to be evaluated manually, such as:

Please, review the items listed in the informational section.

False Positives

In rare cases if keywords are used within PL/SQL code MEET may falsely report them as unsupported functionality. If this occurs these statements should be excluded from the final reporting numbers.

Unrecognized Grammars

At the bottom of the detailed technical report, there is a section for unrecognized grammars. These are constructs in the source file which MEET DB2 does not currently recognize.

Currently known unrecognized grammars:

If you encounter any unrecognized grammars (whether from the list above or others) please provide feedback to the MEET DB2 development team via the feedback link below. If possible, please attach both the MEET DB2 report and the input source file as well.


Sybase Mode

Syntax of the Input File

Sybase T/SQL must contain the keyword "go" separating SQL batches or statements to be evaluated, in the same fashion as a script that is fed to the isql command.

It may be necessary to add "set quoted_identifier on" to the input file, if that option was being utilized by the client but was not put into the input file.

Known Limitations

Unrecognized and will not be supported by DB2 9.7.2

The analysis process performed is a syntactical analysis and does not maintain nor can it access table metadata during the analysis process, making certain types of checks unfeasible.

Unrecognized Grammars

The following are not evaluated at this time:

False positives/Manual intervention

These will be described in the report within any potentially questionable features that are found.


© Copyright IBM Corporation 2010
All Rights Reserved.