Porting user-defined data from IBM Optim Performance Manager to IBM Data Server Manager

Content

You can use the attached scripts to export user-defined data from IBM® Optim Performance Manager and import it into IBM® Data Server Manager. To ensure data schema compatibility, the export script supports Optim Performance Manager at version 5.3 or later, while the import script supports any version of Data Server Manager.

The scripts port only the following user-defined data:

• Job definitions – Definitions for all jobs except the Report and Query Tuning jobs are exported. The scripts used by the jobs (for example, CLP script, shell script) and job execution history logs are not exported.

• Blackout events – Only the job description and schedule defined for the blackout event are exported. Blackout event execution history is not exported.

• User-defined alerts, such as alerts with "SQL Only Script" or "Executable/Shell Scripts" job type.

1. Download the OPMximport.zip file and unzip it into your directory of choice (for example, C:\my_dir).
   
2. Run the export_data script to export data from the Optim Performance Manager repository database. This script file is stored in the my_dir/OPMximport/os_type directory, where my_dir is the directory that you extracted the zip file into and os_type is the type of operating system where you run the script. For example, on Windows, if you unzip the file into my_dir, the script file is in C:\my_dir\OPMximport\win.
   
• Windows: Run my_dir\OPMximport\win\export_data.bat as a user with EXPORT privilege on the repository database for Optim Performance Manager.
• Linux and UNIX: Run my_dir/OPMximport/unix/export_data.sh as a user with EXPORT privilege on the repository database for Optim Performance Manager and with write access to the my_dir directory.
  
3. Respond to the export_data script’s prompt by entering the database name used as the repository for Optim Performance Manager. If you don’t enter a database name and just press Enter, the default name, PERFDB, will be used.
   
4. The output message is redirected to the my_dir\OPMximport\logs\EXPORT.LOG file.
   
5. The user-defined data is exported into the my_dir\OPMximport\data directory. This data will be used by the import script. If you will run the import script from the same machine where you ran the export script, you won’t need to transfer the data. However, if you will run the import script on another machine, then you will need to transfer the data directory and the import scripts to that machine. This can be done by zipping the entire OPMximport directory, which includes the exported data, and then unzipping it into your directory of choice (for example, my_dir on the target machine).
   
6. Run the import_data script to import data into the Data Server Manager repository database. The import_data script file is stored in the same directory as the export_data script.
   
• Windows: Run my_dir\OPMximport\win\import_data.bat as a user with LOAD and IMPORT privileges on the repository database for Data Server Manager.
• Linux and UNIX: Run my_dir/OPMximport/unix/import_data.sh as a user with LOAD and IMPORT privileges on the repository database for Data Server Manager and with write access to the my_dir directory.
  
7. Respond to the import_data script’s prompt by entering the database name used as the repository for Data Server Manager. Note: There is no default database name.
   
8. The output message is redirected to the my_dir\OPMxImport\logs\IMPORT.LOG file. In some cases, the log may contain warning messages during the LOAD processing. The warnings are caused by job child entries that do not have job parent entries. The export script filters out these parent records, which may result in orphan child records on import. You can ignore the warnings because these orphans are not imported, per constraint rules.

• You can verify data is imported into Data Server Manager by checking that there are entries in the Jobs, User-defined Alerts, and Blackout views.

• The export and import scripts do not validate the syntax nor the existence of the SQL/CLP scripts specified in the scheduled jobs. You must ensure that the SQL/CLP scripts are correctly set up for the jobs migrated to Data Server Manager. For example, the import script does not validate if exported data from a Linux server is incorrectly imported into a Windows server, and vice versa.

• Separately, you also need to export database connections from Optim Performance Manager to a CSV file and then import them into Data Server Manager. To do this, you can use the export and import functions in the Database Connections view of Optim Performance Manager and Data Server Manager.