on 08-14-2014 6:55 AM
Hi,
As continued to the discussion of "
I am trying to deploy one of the CORE component "SERVERCORE" using "TELNET" on my SAP NW7.3 EHP1 System but getting error that " SCA's aborted"
and unable to deploy the component. Please help me to get out of this.
Hi Chandrababu,
Hope you are doing good.
As of now please refrain from using batchdeployer; this should the last resort as changes will be made straight to the DB without any dependency checks. This can lead to future consistency issues and hence you will not find this info in any SAP official document .
Please can you try the below workaround with telnet first:
1. Create new directory /tmp/dpl
2. Add all the files that are to be deployed into /tmp/dpl directory. Include all the core files mentioned in note 1794179 (download the latest patches of these files ) .
3. connect to the telnet service of the NetWeaver J2EE server
4. jump 0 (to server node)
5. execute following command
deploy /tmp/dpl version_rule=all
6. The system will restart (telnet will take care of this).
Let us know how this goes.
Kind regards,
Hemanth Kumar
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Chandra,
Can you check SMP for minimum patch levels for these components:
For eg, Look at he below link for ServerCore SP04 Patch 56
Just map you Patch level with minimum required level and share.
Regards,
Divyanshu
Hi Chandra,
Sorry i did not understand your last reply. When you load all the core SCAs (put them into and folder) and then trigger the telnet option, the tool itself will take care of the dependencies and deploy the SCAs in the correct manner.
What was the error you were getting when you tried this?
You mentioned:
"
Did same using telnet as mentioned you and didn't update SPS to latest.
still they showing same as previous.
"
Does that mean that the deployment went fine, but still system info etc. shows old values? This is VERY strange. You can get the latest list from the configtool. Just check the attached screenshot for an example.
If this still shows old version, please run the force bootstrap once:
1)
Stop the j2ee server. Under cluster directory (/usr/sap/<SID>/J<nr>/cluster) rename server0 and subsequent nodes to ".old" respectively. The intention here is to create a backup of the existing files. Do not rename the bootstrap folder as this is needed for the sync process.
2)
Change bootstrap.properties file to ensure it has element.resynch=force as per SAP note 710663.
3)
Restart the J2EE Engine. The new server folders should be created during the bootstrapping and this is a time consuming process as all the contents of the server nodes will be syched with the DB content.
4)
Remove the element.resynch=force property or change it to element.resynch=detect which is the default setting.
Regards,
Hemanth
Hi Chandra,
Did you refer : http://service.sap.com/sap/support/notes/1794179 ?
What are you trying to deploy ? SP or Patch ?
Regards,
Divyanshu
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Srivastava,
I read the note and we are at the situation of " Installed SAP NW 7.3 ehp1 and later try to update all the SPS from SP01 to Sp10 using SUM tool, It deployed all the remaining CORE components shown in the note 1794179 except SERVERCORE.
I try to deploy it by using TELET but not possible.
Regards,
Chandrababu
Hemanth will probably know best but my guess is that SERVERCORE (as many other core SCAs) needs to be deployed in offline mode.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
85 | |
10 | |
10 | |
10 | |
7 | |
6 | |
6 | |
5 | |
4 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.