SID and Java Instance ID related dilema during System Copy

[One_Idea]

Hi Yatin,

Sorry for the confusion. I actually changed the the logon properties on the configtool as well. Let me get to more specifi errors and provide some screenshots as well.

Most likely I will be proposing to make the copy with SAP standard way because I will be upgrading this system later on and I don't think it's a good idea to work on upgrade when the patching hasn't been done the right way to begin with, to bring the system up. I really hate to deviate from the standar copy procedure but these are the circumstances where I am being expected to provide what has been provided earlier from some other party.


Shival

[man_in_black]

Hey One_Idea,

Yatin is right. Fix your Securestore first. Unless you fix it, no matter what else you change, it's not going to work out.

When you open configtool, it should be able to connect to the J2EE schema without any error with the new schema. If that works, the configtool shows your server and dispatcher instance details there and then you go around and make necessary changes to your UME settings for JAVA Apps to start up.

But, having standard naming would be better if you are going for an upgrade of the system.

Good Luck,
MIB

[One_Idea]

Hello,

I would like to close this thread. Unfortunately I couldn't get to the end of this and how these work-arounds work to have the system up and running without using SAPInst.

We have decided to start-from-scratch and go with the standard SAP System Copy procedure using SAPInst instead.

Thanks all for your prompt attention to this issue,


Shival