Oracle to ASE Migration
Migrating an Oracle database to an ASE (Sybase) database can be challenging, but having the right tools and procedures in place can ensure an efficient and smooth transition. In IT-Conductor, this can be accomplished using a process definition that consists of Terraform and Ansible activities developed to simplify the migration process.
Scenario
In this demo scenario, we have used an existing on-premise Oracle database as the source system and built the target system in an ASE database on Azure.
Also, we used our tenant called “OZSoft” but the process can be cloned and applied to any customer after being onboarded to IT-Conductor as a tenant. IT-Conductor creates and clones the Git repository for each tenant who needs to leverage these types of automation runbooks.
Process Definitions
We have used two process definitions for this migration scenario. To access them, navigate to the Tenant Service Grid → Process Definitions, search, and click on the following:
Oracle to ASE on-prem activities
TEST Migrate Oracle To ASE
Oracle to ASE On-prem Activities
In this process definition, the tasks will be performed on the on-premise system. The SMIGR_CREATE_DDL job will be run using an SSHShellJob. Then the export of the Oracle system will be performed consecutively.
After running the process definition, you can check the execution logs as shown below.
Test Migrate Oracle to ASE
The process begins with provisioning two VMs using Terraform commands. The first VM is for the ASE application and the second is for the ASE database. Once the VMs are provisioned, the migration tasks will be performed using an Ansible playbook.
The process definition contains the following activities:
Provision Azure VM for ASE APP
Pre-Configure ASE APP VM
Install ASCS
Provision Azure VM for ASE DB
Pre-configure ASE DB VM
Import DB
Install PAS
Provision Azure VM for ASE APP Activity (VM 1)
In this activity, select the data file /configure/templates/vm_app.json.
The virtual machine to be provisioned in this activity will be used for installing the SAP application.
The .json file consists of information related to:
Infrastructure (which includes region, resource group, vnet, arm_id, subnet, and nsg)
VMs (which includes VM name, OS image ID, size, disk type, authentication, user name, Storage disk type, size (in GB), and mount points)
sshkey (which includes the path to the public key and the path to the private key)
Provision Azure VM for ASE DB Activity (VM 2)
In this activity, select the data file /configure/templates/vm_db.json.
The virtual machine to be provisioned in this activity will be used for installing the ASE (Sybase) database.
The vm_db.json contains the same information as vm_app.json, however, there will be a different hostname.
Once the changes in both files (App and DB) have been made, proceed to run the Process Definition and fill out the fields as shown below:
Note: Removal Age refers to the instance of process orchestration and is not to be mistaken for the removal of the provisioned system.
Once the process definition is running, it will start changing colors to indicate the status of each activity. After successful completion, the color of the activities will turn GREEN.
Note:
Virtual Machine (VM) Provisioning activities are performed via Terraform and all SAP+DB installation, import, etc. are performed via Ansible.
All codes are fully customizable and can be changed depending on customer requirements.
SAP on Azure Migration Dashboard
IT-Conductor dashboards allow administrators to start/stop source and target systems, and provision VMs or database nodes during migration activities.
Last updated
