Skip to Content

2. Import Phase

As I described before, I will perform a SAP distributed installation in the target side/server, this is, the SAP itself on Windows Server 2012 (R2) and the Oracle database (11.2.0.4) in Linux SLES 11 SP3. For this installation activity I will use the export dump that was created during the export phase that I described in the PART 2 of this document. During the following procedure I will show you how to perform the import phase of this heterogeneous system copy activity. As I said before, for the SAP installation you should never use the <sid>adm user, use a non-SAP OS user, for example in my case I have a specific OS user for this task: sapadmin (this user must be administrator of the server).

I ask you attention for some details that I will mention here, specialty the task that it´s necessary to run in linux side, in order to run the Oracle database installation you must first prepare this host with specific user (<sid>adm) and groups (sapsys; sapinst), thus avoiding some errors, at level permissions, during the Database Instance installation. This user and group must previously exist in the linux side for this type of implementation and for this reason you need to run the “Global Host Preparation for an ABAP System” that I will mention more later in this document.


This import phase was performed in both target server, in Windows Server 2012 (R2) and Linux SLES 11 SP3 (sapwinci and saplindb). For this I used the Software Provisioning Manager tool (version 70SWPM*). For this purpose I will run the following four phases:

s

      • 2.1. ASCS Instance installation (sapwinci host – Win Srv 2012 (R2));
      • 2.2. Global Host Preparation for an ABAP System (saplindb host – SLES 11 (SP3));
      • 2.3. Database Instance installation (saplindb host – SLES 11 (SP3));
      • 2.4. Central Instance installation (sapwinci host – Win Srv 2012 (R2)).

2.1. ASCS Instance installation (sapwinci host – Win Srv 2012 (R2))

SNAG-0187.jpg

SNAG-0188.jpg

SNAG-0189.jpg

SNAG-0190.jpg

Press “OK”


SNAG-0191.jpg

SNAG-0192.jpg

SNAG-0193.jpg

SNAG-0194.jpg

SNAG-0195.jpg

SNAG-0196.jpg

SNAG-0197.jpg

SNAG-0198.jpg

Press “No”


SNAG-0199.jpg

SNAG-0200.jpg

SNAG-0201.jpg

SNAG-0202.jpg

SNAG-0203.jpgSNAG-0204.jpg

You can see in the following video all the details of the “Parameter Summary” screen:

SNAG-0205.jpg

Finish with success:

SNAG-0206.jpg

– New LOD system in SAPMMC console (ASCS Instance):

SNAG-0207.jpg

– New OS administrators users lodadm and sapadm:

SNAG-0208.jpg

– New OS users — lodadm, SAPServiceLOD and sapadm:

SNAG-0209.jpg


2.2. Global Host Preparation for an ABAP System (saplindb host – SLES 11 (SP3))

In way to understand why I run this phase (that is not mentioned in SAP installation guide), please read the introduction section at the beginning of this document part 3.


– As “root” run the Software Provisioning Manager (70SWPM version):

SNAG-0210.jpg

SNAG-0211.jpg

SNAG-0212.jpg

SNAG-0213.jpg

SNAG-0214.jpg

SNAG-0215.jpg

SNAG-0216.jpg

SNAG-0217.jpg

SNAG-0218.jpg

SNAG-0219.jpg

SNAG-0220.jpg

You can see in the following video all the details of the “Parameter Summary” screen:

SNAG-0221.jpg

Finish with success:

SNAG-0222.jpg

As you can see in the following images, the specific user and groups were created in linux host (lodadm; sapsys; sapinst). For this verification you just need to check the content of /etc/group by running the command cat /etc/group:

SNAG-0239.jpg

SNAG-0240.jpg

Note: Now this server are ready to host the oracle database, now you can start the next step – Database Instance installation.




=> CHECK THE CONTINUATION OF THIS DOCUMENT IN THE FOLLOWING LINK:

SAP Migration – Win/MaxDB <=> Win & Linux/Oracle DB – PART 4


To report this post you need to login first.

Be the first to leave a comment

You must be Logged on to comment or reply to a post.

Leave a Reply