cancel
Showing results for 
Search instead for 
Did you mean: 

Installing DI after systemcopy overwrites instance.properties

kai_gebhardt
Participant
0 Kudos

Hello,

I did a systemcopy of our productive CRM-System (CI+DB with Java Addin, Version 7.0 EH1) to move it to new hardware. I used for that the swpm.

After the systemcopy I had problems with the additional Application server. So I deleted and reinstalled on another server a DI with the same SWPM:

After restarting both systems I the J2EE instance on the central host did not start - the reason was that the DI-Installation replaced some values in the instance.properties:

ID5958800.ClassPath=./bin/boot/boot.jar:./bin/system/bytecode.jar:.

ID5958800.Debuggable=no

ID5958800.JLaunchParameters=

ID5958800.JavaParameters=-Djava.security.policy=./java.policy -Djava.security.egd=file:/dev/urandom -Dorg.omg.CORBA.ORBClass=com.sap.engine.system.ORBProxy

-Dorg.omg.PortableInterceptor.ORBInitializerClass.com.sap.engine.services.ts.jts.ots.PortableInterceptor.JTSInitializer -Dcom.sap.jvm.scenario=j2ee -Xss2M -Drdbms.driverLocation=E:/usr/sap/KCP/D00/exe/mssjdbc/sqljdbc.jar -Drdbms.driverLocation=E:/usr/sap/KCP/D00/exe/mssjdbc/sqljdbc.jar

ID5958800.JavaPath=E:/usr/sap/KCP/D00/exe/sapjvm_4

ID5958800.LogName=dispatcher

ID5958800.MainClass=com.sap.engine.boot.Start

ID5958800.MaxHeapSize=256

ID5958800.Name=dispatcher

ID5958800.Parameters=

ID5958800.RootPath=E:/usr/sap/KCP/D00/j2ee/cluster/dispatcher

ID5958800.Type=dispatcher

ID5958850.ClassPath=./bin/boot/boot.jar:./bin/boot/jaas.jar:./bin/system/bytecode.jar:.

ID5958850.DebugMode=no

ID5958850.DebugPort=50021

ID5958850.Debuggable=no

ID5958850.JLaunchParameters=

ID5958850.JavaParameters=-Djava.security.policy=./java.policy -Djava.security.egd=file:/dev/urandom -Dorg.omg.CORBA.ORBClass=com.sap.engine.system.ORBProxy -Dorg.omg.CORBA.ORBSingletonClass=com.sap.engine.system.ORBSingletonProxy

-Xss2M -Drdbms.driverLocation=E:/usr/sap/KCP/D00/exe/mssjdbc/sqljdbc.jar

ID5958850.JavaPath=C:/Program Files/sapinst_instdir/BS2010/CRM701/LM/COPY/MSS/SYSTEM/CENTRAL/AS/sapjvm_4/sapjvm_4

ID5958850.LogName=server0

ID5958850.MainClass=com.sap.engine.boot.Start

ID5958850.MaxHeapSize=2048

ID5958850.Name=server0

ID5958850.Parameters=

ID5958850.RootPath=E:/usr/sap/KCP/D00/j2ee/cluster/server0

ID5958850.Type=server

bootstrap.ClassPath=./bootstrap/launcher.jar

bootstrap.JavaParameters=-Djco.jarm=1 -Djava.security.policy=./java.policy

bootstrap.JavaPath=E:/usr/sap/KCP/D00/exe/sapjvm_4

bootstrap.MainClass=com.sap.engine.offline.OfflineToolStart

bootstrap.MaxHeapSize=512

bootstrap.Name=bootstrap

bootstrap.Parameters=com.sap.engine.bootstrap.Bootstrap ./bootstrap ID0059588

bootstrap.RootPath=E:/usr/sap/KCP/D00/j2ee/cluster

bootstrap.Type=bootstrap

bootstrap_ID5958800.ClassPath=./bootstrap/launcher.jar

bootstrap_ID5958800.JLaunchParameters=

bootstrap_ID5958800.JavaParameters=-Djco.jarm=1 -Djava.security.policy=./java.policy

bootstrap_ID5958800.JavaPath=E:/usr/sap/KCP/D00/exe/sapjvm_4

bootstrap_ID5958800.MainClass=com.sap.engine.offline.OfflineToolStart

bootstrap_ID5958800.MaxHeapSize=256

bootstrap_ID5958800.Name=dispatcher bootstrap

bootstrap_ID5958800.Parameters=com.sap.engine.bootstrap.Bootstrap ./bootstrap ID005958800

bootstrap_ID5958800.RootPath=E:/usr/sap/KCP/D00/j2ee/cluster

bootstrap_ID5958800.Type=bootstrap

bootstrap_ID5958850.ClassPath=./bootstrap/launcher.jar

bootstrap_ID5958850.JLaunchParameters=

bootstrap_ID5958850.JavaParameters=-Djco.jarm=1 -Djava.security.policy=./java.policy

bootstrap_ID5958850.JavaPath=C:/Program Files/sapinst_instdir/BS2010/CRM701/LM/COPY/MSS/SYSTEM/CENTRAL/AS/sapjvm_4/sapjvm_4

bootstrap_ID5958850.MainClass=com.sap.engine.offline.OfflineToolStart

bootstrap_ID5958850.MaxHeapSize=2048

bootstrap_ID5958850.Name=server0 bootstrap

bootstrap_ID5958850.Parameters=com.sap.engine.bootstrap.Bootstrap ./bootstrap ID005958850

bootstrap_ID5958850.RootPath=E:/usr/sap/KCP/D00/j2ee/cluster

bootstrap_ID5958850.Type=bootstrap

instance.box.number=KCPD00kdocrmapp1

instance.en.host=kdocrmprd1

instance.en.port=3202

instance.enabled=yes

instance.install.dir=E:/usr/sap/KCP/D00/j2ee

instance.ms.host=kdocrmprd1

instance.ms.port=3902

instance.osLibsPath=E:/usr/sap/KCP/D00/j2ee/os_libs

instance.runAction=NONE

instance.runMode=normal

instance.system.id=0

As you can see, the Directories were all set to the D00-Instance so the CI could not find the path and did not start.

I had to shutdown both system and copied a backup file of the instance.properties back to the origin location (e:\usr\sap\SID\dvebmgs00\j2ee\cluster).

After that, the central instance started right and it  is green in the MMC. But the Dialog Instance had the same problem now, it could not start thus the directories can't be found.

I.e. the dev_bootstrapID5958850:

Thr 6112] JLaunchIStartFunc: Thread 6112 started as Java VM thread.

[Thr 6112] *** ERROR => Can't change working directory [E:\usr\sap\KCP\DVEBMGS00\j2ee\cluster] (rc = 2) [jlnchxxi.c   397]

[Thr 6112] *** ERROR => Cannot change to working directory [E:\usr\sap\KCP\DVEBMGS00\j2ee\cluster] (rc=-1) [jlnchxxi.c   812]

Thr 6024] Mon Oct 06 21:10:35 2014

[Thr 6024] JLaunchCloseProgram: good bye (exitcode = -1)

I uninstalled the DI, restarted both servers and reinstalled the DI again, but the same behavior:The instance.properties in the CI was overwritten with values from the DI.

Am I missing something? I cant remember how I installed the old DI, I just know that I used other Installation-DVDs. But the swpm has the option to install a DI for CRM so I think it should work!?

Thank you and best regards

Kai

Accepted Solutions (1)

Accepted Solutions (1)

divyanshu_srivastava3
Active Contributor
0 Kudos

Hi Kai,

What are the instance number of your CI and DI.

Also, in bootstrap.properties, remove element.resynch=force parameter

Regards,

Answers (4)

Answers (4)

former_member185239
Active Contributor
0 Kudos

Hi Kai,

You need to have a instance id information for DI as well in configtool.

Which version of SWPM you are using?

You can check the cluster_id_switch.properties file for DI in sapinst. Also do check the java configuaration phase of DI.

Also do let us know the scenario of your landscape.

With Regards

AshutoshChaturvedi

kai_gebhardt
Participant
0 Kudos

Hi,

yes, that makes sense. But funny (not very) that there is no Instance ID of the DI!?

I used the swpm "70SWPM10SP06", downloaded 4-5 weeks ago. The scenario is just a productive SAP CRM 7.0 EHP1-Landscape on two servers:

Server A: Ci+DB, ABAP+Java

Server B: DI

As mentioned above, I've tried the Installation of the DI two times, allways the same result. Perhaps the SWPM has a bug? I will have a look if there is a newer one or just try an a little bit older one.

Cheers

Kai

former_member185239
Active Contributor
0 Kudos

Hi Kai,

You can give a try with SWPM SP05 if available.

With Regards

Ashutosh Chaturvedi

kai_gebhardt
Participant
0 Kudos

Hello all,

1. Divyanshu: both Systemnumbers are 00, this shouldn't be a problem thus they are installed on 2 different servers. The bootstrap-parameter is not set.

2. Rajendra: Its no cluster, just a "simple" CI+DB on server1 and DI on server2. Both with Windows 2008 R2

3. Ashutosh: The parameter j2ee/instance_id is already set to the right ID in the instance profile.

If I can find a timeslot, I will retry the Installation with the latest swpm. This one is from july, hopefilly there is a newer one.

Has anybody other ideas? I have no other ABAP+Java System with DI installed, so I can't compare.

Thank you and best regards

Kai

0 Kudos

Hi Kai,

We can see that ,somewhere your instance number of Ci maintained is wrong.If we see below ,its taking enque port and ms port as 3202 and 3902 respectively.So  I guess its picking instance number as 02 from some where.

Can you please check in config tool  that instance number ports are maintained correctly.

instance.en.host=kdocrmprd1

instance.en.port=3202

instance.enabled=yes

instance.install.dir=E:/usr/sap/KCP/D00/j2ee

instance.ms.host=kdocrmprd1

instance.ms.port=3902

instance.osLibsPath=E:/usr/sap/KCP/D00/j2ee/os_libs

instance.runAction=NONE

instance.runMode=normal

instance.system.id=0


Hope this works!


Thanks,

Needu

kai_gebhardt
Participant
0 Kudos

Hello Needu,

thank you. But I think that those values are OK, because the "SAP Central Service Instance for J2EE" has the instance no. 02.:

# SAP Central Service Instance for J2EE

#-----------------------------------------------------------------------

j2ee/scs/host = kdocrmprd1

j2ee/scs/system = 02

j2ee/ms/port = 3902

The ASCS-Instance has the ID 01 and the CI+DB 00.

Best regards

Kai

0 Kudos

Hi Kai,

OK fine.

Please check once all the entries in config tool as mentioned in the below notes.

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

966752 - Java system copy problems with the Java Migration Toolkit

Thanks,

Needu

divyanshu_srivastava3
Active Contributor
0 Kudos

Hi Kai,

Open bootstrap.properties of both CI and DI and check that below values

install.dir and instance.prefix

They should be instance specific.

In, CI add element.resynch=force to bootstrap.properties and start the system in below order

start DB

start CI and central services

start DI

Then share results.

If there are problem with Instance ID(using BOX number) then refer below link and check value of instance.box.number in addition to the above notes.

Regards,

kai_gebhardt
Participant
0 Kudos

Hello Divyanshu,


I've added the element.resynch=force to the bootstrap.properties and restarted the systems, but no luck.


I'm a little bit confused now. I have just one ID (59588) after installing the CI+DB. Is this right? Are does the DI also has to have one "own" ID? As far as I understand the link you have posted, there is a scenario with 2 J2EE-Engines (Cluster?) and that's why they both have different IDs. Or is it the same when installing a DI?


@Needu: Thank you for the notes, but they both don't help me...


Best regards

Kai

former_member185239
Active Contributor
0 Kudos

Hi Kai,

Just checked the parameter j2ee/instance_id in your central instance profile.

If not maintained , then add the parameter and take a restart.

Hopefully , it seems to be a problem with your SWPM. So in that case use the latest SWPM.

With Regards

Ashutosh Chaturvedi

Former Member
0 Kudos

Dear

your are in cluster envirnoment if yes which os u are using which cluster software u r using

send me the details

Regards