Migration of SAP Portal from AIX to Linux

[Former Member]

Hi Experts,

We are migrtaing our Portal system which has got CI & DB running on One aix host & 4 application servers (diaglog instances) running on separate 4 hosts.

We are migrating CI & DB using SAPINST using load based migration.

After migration when we are starting the Config tools, the application server instances are still visible in config tool tree.

When we are installing the application servers on Linux hosts it is picking up the old instance ids & old configuration from AIX hosts.

We tried deleteing the old application servers from configuration editor of config tool under cluster data & then deleting property sheets of old Application servers & old dispatchers. But again when we install the application servers, it still picks up the same instance id numbers & old configuration of AIX hosts.

Can you please advise if there is any way of preventing the new application servers picking up the old configuration as uninstalling the application server before migration is not feasable for us.

Also if there is any harm in new instances picking up the old instance id numbers & old configuration.

Thanks in advance,

Warn Regards,

Ajay

[Former Member · Accepted solution]

Hi Ajay,

Which Version of AS Java are you Migrating ?

Deleting the Redundant Entries from Configtool's Configuration Editor does the Job.

If I understand correctly , you are saying that after Successfull Migration of CI+DB , you tried to  install Additional Application Servers.

The Instance ID of the installed application servers is same.

I don't see any problems with that .

Are you facing any issues because of this ??

Regards,

Ashish .A. Poojary

[Former Member · Accepted solution]

Hi Ashish,

Thanks for your response.

We are migrating our SAP NW Portal 7.02 SPS14 from AIX/DB2 to Linux/DB2.

You are correct that after Successfull Migration of CI+DB , we tried to  install Additional Application Servers. The Instance ID of the installed application servers is same as old AIX App Servers as we are using the same name, same instance numbers & same virtual host names.

There are no issues as such apart from fact that we we install the new app servers it also picks up old parameters in configtool which we had for old AIX App Servers even though we deleted the all enteries for App servers from Configtool's Configuration Editor after the migration.

Apart from that what we also noticed was when we did the managed system configuration in solman for our System & pushed the introscope agent, though it updated the config tool & instance.properties for CI server, it only updated the instance.properties for App servers. It didnt update the Config tool for App servers & because of that it was giving warning message about inconistency between Config Tool & instance.properties when we were launching the config tool.

Beside at the time of start config tool was not updating the instance.properties for app servers until i manually updated the config tool parameters for additional app servers to remove the warning message.

I am not sure why it happened as i couldnt find any errors.

Regards,

Ajay

[former_member185239]

Hi Ajay,

If  the configtool is showing the old information of instances , it has got two things

1.  JMT phase of your migration has not been performed correctly.

2. If you are using the same hostname , SID , instance name , then it will calculate the same instance number.

In JMT  phase it  should delete all the information of dialog instance  and calculated the new instance id

on the basis of box number calculated from the file cluster_id_switch.properties while migrating the CI.

checked the JMT folder inside sapinst_dir.

Checked the below parameter in cluster_id_switch.properties

src.ci.sid=

src.ci.instance.number=

src.ci.instance.name=

src.ci.host=

Checked the logs for java migration tool phase and java configuration parameter phase.Also do check the box number of the system.If the box number is not correct as per your input then you will not able to patch your system further.

Now in second case, If you are keeping the same hostname , instance name and SID , then it will calculate the same instance id so you don't need to worry in this case.

1644265 - "How to determine the correct box number of the instance"

With Regards

Ashutosh Chaturvedi

[Former Member]

Hi Ashu,

Thanks for your response.

I understand how the instance number is calculated. Yes we are keeping the system name, system nr & virtual host same so it is calculating the same instance number for CI. There are no issues with that. It is doing exactly what it is supposed to do.

The issue i raised was for Dialog Instances which you have to install again after migrating your CI as Application Servers cant be exported/imported. As we are keeping the System name , System no & host same for Apps server as well it is picking up same numbers for App Servers as well which also is not an issue.

The issue is it is picking up old values for certain parameters in config tool for those App Servers.

Regards

Ajay

[former_member185239]

Thank you Ajay sir. Didn't recoznize earlier

Hope you are doing well !!!