Things To Do After DB Refresh To Make Java Up

Things to do after DB refresh to make java stack up.
Index
1> Introduction . 1
2> Steps to Follow.. 2
3> Virtual Memory setting / Initialization ..9
4> Appendix9
Introduction
Most of times java stack wont come up after DB refresh.This is because, you are
using backup of some other <SID> and of different host name.
Even Schema name and Instance ID also get changed.
( Lets assume its Db refresh from production to quality system )
Prod SID DE1
Quality SID XE1 )
Steps to follow
1> Logon with the configtool (if it didnt work please verify the DB Settings) and
change the securestore parameter jdbc/pool/SID/user and jdbc/pool/SID/password
For this check at DB level which java schema is present in your database.
2> Check instance ID
3> Go to instance profile and change j2ee/instance_id = ID00xxxxx (Which you have
noted in step 2 )
4> ( Use following if both of system belongs to same environment)

Copy instance.property and bootstrap.property files from production server and place
it on quality server at respective location. Before this rename instance.property and
bootstrap.property file on quality server. DO NOT DELETE.
Now edit both files.
Replace SID and hostname of prod with SID and hostname of quality.
(If your system number changes take care of parameter related with system number
and port)
5> ( Use following if both of system belongs to different environment)

Take back up of instance.property and bootstrap.property files.
Change Instance ID to ID which you have noted in step 2. Do this for both of files.
6> Now go back to configtool and switch to configuration editor mode.

Select propertysheet instance.property.IDxxxxx
Switch to change mode and confirm the warning.
A change configuration dialog box appears.
Instance.property file refer this propertysheet for few parameter value. Only changing
value in instance.property file at OS level will not help, as when ever cluster restarts it
reads parameter value from DB level. Hence we have change value in property sheet.
Replace SID and hostname of prod with SID and hostname of quality.
And save the configuration.
(If your system number changes take care of parameter related with system number
and port)
7> Switch back to normal mode and take care of following parameter.
o Global dispatcher configuration managers ClusterManager
ms.host
o Global dispatcher configuration managers ClusterManager
ms.port
o Global dispatcher configuration managers LockingManager
enq.profile.filename

enqu.host
enqu.port
o Global server configuration managers ClusterManager
ms.host
o Global server configuration managers ClusterManager
ms.port
o Global server configuration managers LockingManager
enq.profile.filename
enqu.host
enqu.port
o Global server configuration services
com.sap.security.core.ume.serviceume.r3.connection.master.client
com.sap.security.core.ume.service ume.r3.connection.master.r3name
o Global server configuration services dbpool
sysDB.DBConnectInfo
o Global server configuration services dbpool
sysDS.dataSourceName
o Instance_IDxxdispatcher_IDxx00managersConfigurationMana
gerrdbms.connection
gerrdbms.driverLocation
gersecstorefs.keyfile
com.sap.security.core.ume.serviceume.r3.connection.master.ashost
gersecstorefs.lib
gersecstorefs.secfile
gersystem.name
o Instance_IDxxdispatcher_IDxx00servicesp4port
o Instance_IDxxdispatcher_IDxx00servicesp4httptunneling
o Instance_IDxxdispatcher_IDxx00servicesp4ssl
o Instance_IDxxdispatcher_IDxx00servicesr3startupelement_0
_dir
o Instance_IDxxdispatcher_IDxx00servicestelnetPort
o Instance_IDxxserver_IDxx50managersClusterManagereleme
nt.jointPort
o Instance_IDxxserver_IDxx50managersConfigurationManager
rdbms.connection
secstorefs.keyfile
secstorefs.keyfile
secstorefs.lib
secstorefs.secfile
system.name
o Instance_IDxxdispatcher_IDxx00serviceshttpPorts
Save the configuration.
8> Again switch back to configuration editor mode.

Go to propertysheet of dispatcher configuration manager
And change value for following parameters relevant to your SID and hostname
9> Go to propertysheet of server configuration manager.
And change value for following parameters relevant to your SID and hostname
Save the configuration.
Virtual Memory Settings / Initialization

10> Check VM setting as per the note 723909 or 861215 ( which is relevant to your
system)
11> Apply changes (File Apply).
12> Again your *.vmprp files contain entries of instance ID and Virtual memory
parametrs. If possible correct this. If not, delete the file, it will be created again the
next time you start the engine.
Appendix
13> Related notes
Note 831812 - Config Tool shows incorrect parameters after System Copy
Abhijeet Rathi
C5088311

Things To Do After DB Refresh To Make Java Up

Uploaded by

Copyright:

Available Formats

Things To Do After DB Refresh To Make Java Up

Uploaded by

Document Information

Original Description:

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Things To Do After DB Refresh To Make Java Up

Uploaded by

Copyright:

Available Formats

Things to do after DB refresh to make java stack up.

2> Check instance ID

4> ( Use following if both of system belongs to same environment)

5> ( Use following if both of system belongs to different environment)

6> Now go back to configtool and switch to configuration editor mode.

Switch to change mode and confirm the warning.

A change configuration dialog box appears.

o Global dispatcher configuration managers LockingManager

8> Again switch back to configuration editor mode.

9> Go to propertysheet of server configuration manager.

Save the configuration.

Virtual Memory Settings / Initialization

You might also like