Migrating Automic Automation database and/or versions

Products

• CA Automic Workload Automation - Automation Engine
• CA Automic One Automation

Issue/Introduction

We offer several utilities that can be used to facilitate moving the AWA database to a separate or even different database type (i.e. Oracle to PostgreSQL).

Environment

SQL Server

Oracle

PostgreSQL

Cause

N/A

Resolution

Disclaimer: even with the methods described below, there are limitations to those as case-sensitivity can be an issue when migrating to case-sensitive database to non-case sensitive and vice-versa. For more information, please refer to this Knowledge Base Article. 

Here are two ways to do this:

1. Use the DB Unload and use the 'Unload all objects'. This will put the content of the database in a transport case that can then be then loaded to another environment (with the new database and automation engine components) using the DB Load utility (reports and statistics are not moved)

2. Use the Client Copy utility to copy client(s) over to another environment (reports and statistics are moved, but this must be done between the exact same version)

It is highly recommended reducing the number of statistics and reports before using either option.

Migrating from an older version to a new system on a later version

If migrating from an older version like 12.3 (base version) to a newer version like 21.0 (target version) on a new server, the following can be used in conjunction with the client copy utility:

1. Create the new server and database schema
2. Install the utilities for the base or old version (in this case 12.3)
3. Copy the base version db folder into the utility directory
4. Use the db load utility to load the initialdata for the base version 
5. Use the db client copy utility (from either system) to copy the working clients across from the old db to the db
6. Upgrade the utilities on the new system to the target version (in this case 21.0)
7. Copy the target version db folder into the utility directory on the new server
8. Use the db load utility and update the initialdata to the target version on the new server

Another way to migrate everything would be to install a target version fully, upgrade the base version, and then use the client copy to move those objects to the new system; oftentimes this is doublework due to changes between the base and target version when many times the base version will ultimately be decommissioned.