J2EE

[Former Member]

Dear all,

We are setting up Diaster recover  (DR ) where we are doing the mirror copy of the Source System to Target System.

After mounting all the files in Target DR System, i made the following changes in Target System.

OS: AIX

Dual stack System(ABAP +JAVA)

Instance number used :

00--ASCS00

02-- DVEBMGS02

01--SCS01

03--D03 -------------------------------------------------------------------------->  It is maintained in another DR Server

Database Used: Oracle

a)renamed the Profiles (/usr/sap/KBP/SYS/profile).

b)Changed the dbenv files (/home/kbpadm)  and (/home/orakbp)

c)set right permissions in all files and folders in /usr/sap.

d)Oracle is running and DB is also up

e)Started the profiles using sapcpe

e)After switching user (sidadm), Started the SAP Applications and SAP applications are up.

When i checked the GetProcess list according to instance wise, i am getting below output.

kbpadm>  sapcontrol -nr 02 -function GetProcessList

31.07.2013 13:16:55

GetProcessList

OK

name, description, dispstatus, textstatus, starttime, elapsedtime, pid

disp+work, Dispatcher, YELLOW, Running, Message Server connection ok, Dialog Queue time: 0.00 sec, J2EE status info unavailable, 2013 07 31 11:26:41, 1:50:14, 14549078

rslgcoll, Central Syslog Collector, GREEN, Running, 2013 07 31 11:26:41, 1:50:14, 11141296

rslgsend, Central Syslog Sender, GREEN, Running, 2013 07 31 11:26:41, 1:50:14, 11862158

igswd_mt, IGS Watchdog, GRAY, Stopped, , , 13631708.

kbpadm> sapcontrol -nr 01 -function GetProcessList

31.07.2013 14:41:22

GetProcessList

OK

name, description, dispstatus, textstatus, starttime, elapsedtime, pid

msg_server, MessageServer, GREEN, Running, 2013 07 31 11:25:53, 3:15:29, 14614568

enserver, EnqueueServer, GRAY, Stopped, , , 14483586

kbpadm> sapcontrol -nr 00  -function GetProcessList

31.07.2013 14:41:55

GetProcessList

OK

name, description, dispstatus, textstatus, starttime, elapsedtime, pid

msg_server, MessageServer, GREEN, Running, 2013 07 31 11:26:17, 3:15:38, 10879188

enserver, EnqueueServer, GRAY, Stopped, , , 13041698

J2EE is not coming up. ALSO plz tel where to update 'system/type'  .

There is a warning msg :

J2ee Startup: profile parameter 'system/type' not correctly set to start J2EE; use 'J2EE' for Java only and 'DS' for double stack instance

Server0 is not running.

[Former Member]

Hi Gayathri,

You mentioned about "setting up Diaster recover  (DR ) we are doing the mirror copy of the Source System to Target System".

How did you installed the Target System then?

Because it's a dual-stack system, if you use the system-copy method, you need to export the ABAP and JAVA stack separately (2 times), also the import-phase.

I hope this will help you.

Regards,

Andre

[willi_eimler]

Hi Gayathri,

it seems you are trying to do a systemcopy with a dual stack system. This is not as easy as sap explains it in the systemcopy guide. Please look at:

http://scn.sap.com/docs/DOC-14191

The reason why your system is not starting is because of leaking parameters in your DEFAULT and Instance parameters at /sapmnt/SID/profile.

Best regards

Willi Eimler

[Jozsó]

Hi,

what do you see at the end of dev_jstart file?

Does it try to start the server0 process?

If yes, what is the error in std_server0.out?

These are located in the ../DVEBMGS02/work directory.

Kind regards,

Jozsef

[Former Member]

HI,

The corrected version of jlaunch does not rely on the profile parameter "system/type" anymore, but checks the existance "rdisp/j2ee_start=1" as an indicator for double stack system (type DS). If this parameter is not set, then the Java-Only stack (type J2EE) is assumed.

2. Workaround

You can set the profile parameter to eliminate the problem:

system/type = J2EE

You have to restart the system to make the change active.

Please note you have to set this parameter in the instance profiles as well not only in DEFAULT profile that will not work.

Kind Regards,

Johan

[former_member188883]

Hi Gayathri,

The parameter 'system/type' should be included in the environment variables for <sid>adm.

As you perform mirror copy, you may need to adjust the hostnames for DR environment to match the target system hostnames in the J2EE instance.

Regards,

Deepak Kori