How to migrate aix to linux?

The following diagram shows the pre-migration, on-premises AIX legacy system architecture:

Download a Visio file of this architecture.

The following diagram shows the Azure RHEL post-migration system architecture:

Download a Visio file of this architecture.

The system also contains the following components:

Azure App Service environments are appropriate for application workloads that require high scale, isolation, and secure network access. This feature offers fully isolated and dedicated environments for securely running App Service apps at high scale. App Service environments can host the following types of apps:

One distinct difference between the legacy system and the cloud implementation is in handling network segmentation. The legacy system segmented networks with firewalls. A cloud platform like Azure segments networks with virtual networks and network security groups that filter traffic based on several criteria.

Another difference between the systems is their high availability (HA) and disaster recovery (DR) models. In the legacy system, HA/DR primarily used backups, and to some extent used redundant servers in the same datacenter. This configuration provided modest DR, but almost no HA capabilities. Improving HA/DR was a key driver for moving to the Azure platform. Azure uses clustering, shared storage, and Azure Site Recovery to provide a high level of HA/DR.

Key drivers for moving from on-premises IBM AIX to RHEL in Azure might include the following factors:

The following considerations, based on the Microsoft Azure Well-Architected Framework, apply to this solution:

For proactive monitoring and management, consider using Azure Monitor for monitoring migrated AIX workloads.

This article is maintained by Microsoft. It was originally written by the following contributors.

Principal author:

1. Current AIX licenses may be expiring and renewal may cost more to the company.

2. Company would like to do a POC for upgrade from AIX to Linux.

3. Slowly Companies plan to move onto HANA. Since AIX currently is not supported for HANA they would like to upgrade. Which OS are supported can be found in SAP Note: 2235581 – SAP HANA: Supported Operating Systems.

The first blog of the series shows how to do export preparation along with Table splitting Preparations.

The second blog of the series shows how to export the AIX DB.

The third blog of the series shows how to install PI 74 ASCS, SCS.

The fourth blog of the series shows how to import DB exported from AIX and install Primary Application Server and Secondary application servers on Linux.

The fifth blog shows Post upgrade process.

We have picked PI dual stack for this blogs because the process of dual stack covers both ABAP and JAVA. The same process applies to any other SAP systems.

My Current Landscape:  AIX OS, Oracle DB, SID is PIQ and it is 74 dual installation. Host DB name is piqdb01 and standard installation (ascs, scs, pas running on same host)

After OS Upgrade Landscape:  Linux OS, Oracle DB, SID is PIQ. Host names are piqascs00, piqscs00, piqdb00, piqapp01, piqapp02 (Distributed landscape)

Without any delays let’s start our first process which is to export the existing DB along with Export and Table Splitting Preparations.

Assumptions:

1. We have enough /tmp space

2. Downloaded the necessary software like SWPM, Kernel etc.

3. File mounts to export the existing DB.

1. Set your display and Uncar SWPM. Kick the sapinst process from SWPM directory.

2. Before we export the DB, we will do export preparation and Table splitting preparation steps.

Export Preparation: Once SWPM fired up go the path: SAP Netweaver 7.4 –> Oracle –> System Copy –>  Source System –> Based on AS ABAP and AS Java –> Export Preparation –>

3.   Specify the profile directory.

4.   Specify DB host and DB SID.

5.   Specify the location of the exported DB.

6.   Specify Target Database.

7.   Select Generate database size file and click Next.

8.   Select database specific implementation.

9.   Specify the secure store key Phrase.

10.   Specify No for update Statistics as we will update the stats manually once the upgrade process is completed.

11.   Check the parameters and click Next.

12.   If we don’t run into any issues it will finish the export preparation step successfully.

Table Splitting Process:

Concept for this in simple words is if we have a big table at DB level we split up while exporting. From OS level with a SQL query we pulled up top 10 tables. Given below is the list for this system. Yours may vary.

So simple formula what we have used is to only split table which is more than 10GB. From the above list we have only one table which is 12.2 GB. So we have created a txt file called PIQ_SPLIT.txt and add this formula for this table.

SXMSCLUR%2

Note: In CRM, ECC, BW we will have more tables which are greater than 10GB. So please add all tables in this txt file accordingly.

1.  Start again SWPM process –> Now select Table Splitting Preparation like shown below and click Next.

2.   Select Profile Directory.

3.   Specify DB SID and DB Host.

4.   Select the export location for Database Export and Table Splitting location file which we created above.

5.   Specify ABAP Schema and its password.

6.   Since we selected above Show Table Splitter dialog checkbox it shows the below dialog box.

7.   Check all the parameters and select Next.

8.   Once the process successfully finish we will receive the below screen.

9.   Verify the Split files created by the above process.

• Stop all the queue managers.
• Uninstall the earlier version of the product.
• Migrate all the queue managers and applications to the later version.