Oracle Primavera Contract Management 13.

1 Reports Migration Utility Instructions

Overview
The Contract Management Reports Migration Utility converts reports and forms that were designed for Sybase SQL Anywhere databases for use with Oracle or Microsoft SQL Server. For each folder containing PBLs, the utility: Makes a backup copy of the folder. Extracts the queries, and converts them. Updates the PBLs with the converted queries.

The converted PBLs can then be used with Contract Management connecting to the new database platform. Every effort has been made to make this utility as complete and robust as possible. However, since SQL syntax dialect tends to vary between vendors, it is not possible to cover every possible scenario. This utility will modify most reports and forms written for Sybase SQL Anywhere, and will then migrate them to work with Oracle or Microsoft SQL Server. This reduces the manual work that might have to be done. Any reports that are not successfully migrated must be modified manually in InfoMaker.

Prerequisites
The Contract Management Reports Migration Utility requires several Sybase DLL files in order to execute properly. This means that the Reports Migration Utility must be run on a machine with InfoMaker 12.0 installed. If such a machine is not conveniently available, InfoMaker 12.0 can be installed from the Contract Management release media or download. This is described in the Oracle Primavera Contract Management Installation Guides (for Oracle or for Microsoft SQL Server). The Java Development Kit, or the Java Runtime Environment 1.6 or later, is required in order to run the Reports Migration Utility. The JDK that is installed with Contract Management 13.1 will meet this requirement. If necessary, the JDK or JRE can be downloaded from the following site: http://java.sun.com/ It may be necessary to add the JDK's BIN folder to the PATH environment variable on the system if not there already. The Reports Migration Utility will create a TCP/IP connection to the destination (Oracle or Microsoft SQL Server) database servers to validate queries. A network connection from the machine running the Reports Migration Utility to the machine running the database servers is required, and must be unobstructed by firewalls. Connection information (server names, login credentials, etc.) is also required. This information detailed later in this document. The Reports Migration Utility uses JDBC connections, and will not need client software installed for Oracle or Microsoft SQL Server to establish a connection. The Reports Migration Utility requires a Contract Management schema in your destination database. If you have not migrated your Contract Management databases from Sybase SQL Anywhere to Oracle or Microsoft SQL Server, you must do so before running this utility. Otherwise, the utility will be unable to validate the queries properly and will report them as failures. Although the Reports Migration Utility will automatically create a Backup of your PBL files, you should back up all Report and Form folders before migration. If your PBL files are in InfoMaker 7 (used with Expedition 10.x and earlier) or InfoMaker 10.5 format, please convert them to InfoMaker 12.0 format. This process is described in the Oracle Primavera Contract Management Installation Guides (for Oracle or for Microsoft SQL Server).

Page 1

Launching the Reports Migration Utility

You can open the Reports Migration Utility by doing one of the following: From your Contract Management 13 install media, launch SETUP.EXE from the root folder. Select Other Applications, and then select Launch Reports Migration Utility. From your Contract Management 13.1 install media, navigate into the ReportMigrationUtility folder and launch CONVERTERUI.bat.

Running the Reports Migration Utility

1. After you launch the Reports Migration Utility, you will enter data in a series of fields in order to migrate your PBLs. The following table describes these fields: Field Location of report(.pbl) files Description Specify a folder containing Contract Management Reports or Forms to be migrated. The path may be entered manually, or click the <...> button to browse to the folder. Use the dropdown to specify "Oracle" or "Microsoft SQL Server" depending on which database platform you are using with Contract Management. This is the IP Address or the network name of the Database Server machine. If the Reports Migration Utility is running on the database server itself, the values "localhost" or "127.0.0.1" may also be used. The port number for the Database Server. The name of the instance or SID containing the Contract Management schemas. The name of the Contract Management database (for example, CMDEMO). The login name of the Oracle Schema Owner or User (for example, EXP). login name of the database user (usually EXP). The password for the Oracle Schema Owner or MSSQL Database User (usually SQL).

Destination database type

Host Name

Port Instance Name: (Oracle) Database Name: (MSSQL) Schema Owner: (Oracle) User Name: (MSSQL) Password:

2. Press the Test Connection button to verify the connection details are correct. 3. When ready, press the Convert button to begin the process. A progress meter will replace the Convert button, and will indicate what the utility is doing. A message displays when the process is complete. It displays how many reports were successfully converted and tested out of the total number of reports in the folder. Click OK to dismiss the message. 4. Either enter another path to a folder of PBLs, and click Convert again, or exit the utility.

Page 2

After Migrating the Reports

After the migration completes, the migrated folder contains the following files and folders:

File or Folder
Backup folder, with the date and time of migration SUCCESS.TXT file

Description
Contains a copy of the contents of the folder being migrated, made before any files were modified. Contains a list of each report for which the Reports Migration Utility considers the migration "Successful." Contains a list of each report that the Reports Migration Utility was unable to convert, or that was not executed properly against the destination database. The modified query will be displayed after the error message. If an error was returned by the database server itself, that error will also be displayed. Use this log file to review any failures, so that the report may be updated manually in InfoMaker.

FAILED.TXT

DWSQLTOOL.XML

This file is used internally by the Reports Migration Utility. It contains the source SQL queries from the original PBLs. This file is used internally by the Reports Migration Utility. It contains the source SQL queries from the original PBLs, the updated SQL queries being written back to the PBLs, and status messages regarding the status of conversion or testing. This file is written by the Reports Migration Utility when writing to the PBLs.

DWSQLWRITER.XML

DWSQLTOOL. LOG

Review the FAILED.TXT file for any failures that must be addressed. Test any important reports or forms through Contract Management or InfoMaker to verify that they are retrieving the correct data.

Understanding the Logs

The log files will contain a status message for each report. These messages explain the status of the reports through the migration process, and may indicate if additional action is required. The following table lists and describes these messages. Log Message READ_FAILED CONVERSION_PASSED CONVERSION_FAILED WRITE_SUCCESS Explanation An error was encountered extracting the query from the source PBL. The query was successfully converted. The query could not be converted. The query was successfully written to the PBL.

Page 3

Log Message WRITE_FAILED DB_RUN_SUCCESS DB_RUN_FAILED

Explanation An error was encountered writing the query to the PBL. The query was successfully executed against the database. The database server returned an error when the query was executed. The error returned by the database server will accompany this message. Some queries are not executed against the database due to known limitations (for example, queries saved in InfoMaker "Graphics" format). These queries are not expected to cause problems in the new database environment.

DO_NOT_RUN_FOR_DB

Known Issues
This section describes known issues associated with the Reports Migration Utility. Custom Fields Reports that include Custom Fields may fail if they are run against a group database that does not contain matching Custom Fields. For example, if a Report was modified to include a Custom Field from the CMDEMO group that does not exist in CMPROJ, the utility will fail to validate it if CMPROJ is specified in the database connection details. Reports and Forms that were written specifically for one group should be validated against that same group.

Unions
When a query contains a UNION, the datatypes on both sides must match. Sometimes, migrated queries may result in mismatched datatypes (usually due to functions). The query may not execute against the destination database and, therefore, must be modified manually in InfoMaker

Query Validation
Queries are executed against the destination database to verify that they are syntactically valid. No actual data is retrieved, and no data validation is performed. Therefore, it is beneficial to test reports and forms through Contract Management to verify they are retrieving the correct results.

Microsoft SQL Server to Oracle, or Oracle to Microsoft SQL Server Migrations

The Reports Migration Utility currently does not support these types of migrations. The utility will not prevent an attempt to migrate PBLs from MSSQL or Oracle, but it may not produce correct results.

Comments
InfoMaker does not rigidly enforce correct syntax for Comments within queries. Comments that do not have the correct closing tags, especially at the end of a query, may return an error.

Page 4