Upgrade Solman 7.01 to 7.1 -> Errors in ABAP and JAVA during downtime

[Former Member]

Hello,

We want to upgrade our solution manager 7.0 EHP1 to 7.1 but during the SUM process we are having some issues in the DOWNTIME section for both ABAP and JAVA.

I would like to point out that the process is upgrading BI_CONT 706 to 707.I already checked the note and the "fix" that it provides for this kinds of errors was already in place.

Attached to this message are the log files of both java and abap errors and one of the ...SOLMANX... logs related to tabimupg.elg

ABAP Errors:

Checks after phase MAIN_NEWBAS/TABIM_UPG were negative!

Last error code set: Detected 122 errors summarized in 'TABIMUPG.ELG'<br/> Calling 'C:\usr\sap\DSM\DVEBMGS02\exe/tp' failed with return code 8, check D:\SUM\abap\log\SAPup.ECO for details   

Sample errors of this problem:

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ 
MAIN IMPORT ERRORS and RETURN CODE in SAPILDE71SR1SOLMANX1.DSM 
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ 
4 ETW000 no entries for /POSDW/TOLSETT will be imported in this step. 
4 ETW000 table TB028T: entry in DB is 80 bytes bigger than in file. 
4 ETW000 ... ignoring such differences. 
3WETW109 table "/POSDW/BSTSKT" does not exist in nametab. 
4 ETW000 no entries for /POSDW/BSTSKT will be imported in this step. 
2EETW109 table "/POSDW/BSTSKT" does not exist in nametab. 
4 ETW000 no entries for /POSDW/STOGRT will be imported in this step. 
3WETW109 table "/POSDW/STOCT" does not exist in nametab. 
4 ETW000 no entries for /POSDW/STOCT will be imported in this step. 
3WETW109 table "/POSDW/REASONT" does not exist in nametab. 
4 ETW000 no entries for /POSDW/REASONT will be imported in this step. 
2EETW109 table "/POSDW/REASONT" does not exist in nametab. 
4 ETW000 E071-LOCKFLAGs 001617 - 001617 updated ('7', 1 entries). 
3 ETW676 end import of "LANGTABU/POSDW/REASONT" (warnings). 
3WETW109 table "/POSDW/REASGT" does not exist in nametab. 
4 ETW000 no entries for /POSDW/REASGT will be imported in this step. 
2EETW109 table "/POSDW/REASGT" does not exist in nametab. 
4 ETW000 no entries for /POSDW/TOLSETT will be imported in this step. 
4 ETW000 table TB028T: entry in DB is 80 bytes bigger than in file. 
4 ETW000 ... ignoring such differences. 
3WETW109 table "/POSDW/BSTSKT" does not exist in nametab. 
4 ETW000 no entries for /POSDW/BSTSKT will be imported in this step. 
2EETW109 table "/POSDW/BSTSKT" does not exist in nametab. 

..

JAVA

An error has occurred during the execution of the Deploy SDM step.

Nov 2, 2013 9:47:26 PM [Info  ]: Number of source deployed components detected from components provider: 23
Nov 2, 2013 9:47:26 PM [Info  ]: Number of source deployed components detected from components provider: 23
Nov 2, 2013 9:47:26 PM [Info  ]: DeployController release is 7.10. Component version rule UPDATE_LOWER_ONLY will be used.
Nov 2, 2013 9:47:26 PM [Info  ]: Deploy version rule has been set to updateLowerOrChanged in file D:\SUM\sdt\param\jspm_config.txt.
Nov 2, 2013 9:47:26 PM [Info  ]: Deploy error strategy has been set to stop in file D:\SUM\sdt\param\jspm_config.txt.
Nov 2, 2013 9:47:26 PM [Info  ]: Deployment prerequisite check error strategy has been set to stop in file D:\SUM\sdt\param\jspm_config.txt.
Nov 2, 2013 9:47:26 PM [Info  ]: Undeploy error strategy has been set to skipDepending in file D:\SUM\sdt\param\jspm_config.txt.
Nov 2, 2013 9:47:26 PM [Info  ]: Undeploy dependency rule has been set to stop in file D:\SUM\sdt\param\jspm_config.txt.
Nov 2, 2013 9:47:26 PM [Info  ]: Deploy timeout has been set to 7200 seconds in file D:\SUM\sdt\param\jspm_config.txt.
Nov 2, 2013 9:47:26 PM [Info  ]: Start parsing deployment order definition file D:\SUM\sdt\config\dodf.xml.
Nov 2, 2013 9:47:26 PM [Info  ]: File D:\SUM\sdt\config\dodf.xml is parsed and relative deployment data model is extracted.
Nov 2, 2013 9:47:26 PM [Info  ]: Start parsing deployment order definition file D:\SUM\sdt\config\dodfNonsupportedDCType.xml.
Nov 2, 2013 9:47:26 PM [Info  ]: File D:\SUM\sdt\config\dodfNonsupportedDCType.xml is parsed and relative deployment data model is extracted.
Nov 2, 2013 9:47:26 PM [Info  ]: Number of source deployed components detected from components provider: 23
Nov 2, 2013 9:47:26 PM [Info  ]: Updating SDM...
Nov 2, 2013 9:47:26 PM [Info  ]: Unpacking D:/DOWNLOAD/SDMKIT13_0-10006657.JAR to folder D:/SUM/sdt/tmp/unpack_SDMKit...
Nov 2, 2013 9:47:26 PM [Info  ]: Directory D:\SUM\sdt\tmp\unpack_SDMKit has been created.
Nov 2, 2013 9:47:26 PM [Info  ]: Stopping SDM server...
Nov 2, 2013 9:47:26 PM [Info  ]: AS Java process ID 164 has been started.
Nov 2, 2013 9:47:26 PM [Info  ]:   Command line: C:\usr\sap\DSM\DVEBMGS00\exe\sapjvm_5\bin\java.exe -Xmx900M -Djava.ext.dir=c:/usr/sap/DSM/DVEBMGS00/SDM/program/lib;C:/usr/sap/DSM/DVEBMGS00/exe/sapjvm_5/jre/lib/ext -cp . -jar c:\usr\sap\DSM\DVEBMGS00\SDM\program\bin\SDM.jar shutdown Sdmguiport=50018 sdmHome=c:/usr/sap/DSM/DVEBMGS00/SDM/program logfile=D:\SUM\sdt\log\SUM\OperateSDM_01.LOG
Nov 2, 2013 9:47:26 PM [Info  ]:   Standard out: D:\SUM\sdt\log\SUM\OPERATESDM_01.OUT
Nov 2, 2013 9:47:26 PM [Info  ]: Deployment message for component SAP_JAVASL : 
Nov 2, 2013 9:47:26 PM [Error ]: The following problem has occurred during step execution: java.lang.NullPointerException: while trying to invoke the method java.lang.Process.destroy() of an object returned from com.sap.sdt.tools.proc.OsProcess.getProcessObject().

My opinion on the JAVA ERROR

I noticed that it tries to access the "sapjvm_5" in the kernel folder but there is no sapjvm_5 there. Just sapjvm_4. In another attempt i downloaded the sapjvm_5 manually and placed there. The process continue but after that it tried to send a shutdown command to SDM on port 50018 and it failed. Wasn't SUM supposed to migrate to sapjvm_5 on its own? The MOPZ i produced to this dual stack solman didnt bring any jvm upgrade...

DEPLOY-SDM_01.LOG.txt.zip

SAPILEN71SR1SOLMANX2.DSM.txt.zip

TABIMUPG.ELG.txt.zip

[Sriram2009 · Accepted solution]

Hi Borges

1. Kindly refer the SAP Note 1639668 - Error message in SUM after resetting the update
process for "The following problem has occurred during step execution:java.lang.NullPointerException: while trying to invoke the method"

2. Kindly check your system resources is this any low?

Regards

Sriram

[Former Member · Accepted solution]

Hello Sriram,

Tried the sugestion but it didn't fix the issue. I still believe its related to not having sapjvm_5 in the kernel directory. The log is showing that SUM is trying to access it.

Regards,

[Sriram2009 · Accepted solution]

Hi

Thanks for your info

Could you paste the log D:\SUM\sdt\log\SUM\OperateSDM_01.LOG

Regards

[Former Member · Accepted solution]

Currently i don't have that file in the folder.

[Sriram2009 · Accepted solution]

Hi

Could you try this SAP Note 1678193 - SUM Stops in the PREPARE/EXTRACT/EXTRACT_ROMS Phase

Regards

[Former Member · Accepted solution]

Unfortunetly that note is for older releases of SUM and the one we're using already have that issue fixed. we are using SUM SP09 ( latest ).

[Sriram2009 · Accepted solution]

Hi

Could you try this SAP Note

1678780 - Installation or upgrade of BI_CONT/BI_CONT_XT 7x7

1843776 - Central Note - Software Update Manager 1.0 SP09 [lmt_005]

Regards

[Former Member · Accepted solution]

Hello,

We already checked those notes. Sadly none of those provide help for our problem.

[Sriram2009 · Accepted solution]

Hi

What is SPAM/SAINT version ?

[Former Member · Accepted solution]

The upgrade tool ( SUM ) upgraded it to 702 - 51 ( latest spam/saint version )

[Sriram2009 · Accepted solution]

Hi

Kindly refer the SAP Note 1705923 - Wrong SP Level of components contained in an upgrade
export Still you are finding issue better raise the SAP support ticket

[Former Member · Accepted solution]

Hello Pedro,

Did you resolve your issue ?

[Former Member · Accepted solution]

Hello,

No i wasn't able to solve any of the situations so far.

[Former Member · Accepted solution]

Hello Pedro,

we had exactly the same problem as you did, and SAP helped us to solve it yesterday.

Our background:

- Upgrade from SolMan 7.01SP31 to 7.1SP10

- BI-CONT is being upgraded from 706 to 707

- OS: WinServer2008R2;     DB: MSSQL2008R2SP1

Our Symptoms:

- same as described in SAPILDE71SR1SOLMANX1.DSM logfile of your original post, and in OSS note 1678780 section 6 "Known Errors":

"It is not possible to publish a complete error list in this SAP Note. The errors look as follows:
2EETW109 table "/POSDW/LPA_EXDET" does not exist in nametab.
The affected objects start with /POSDW/."

Solution Provided by SAP:

Basically, the "Allowfiles.SAR" attachment of current version of OSS Note 1678780 is not complete, i.e. it does not contain the corrections for Solution Manager upgrade to release 7.1.

SAP provided us with the needed files I am attaching here.

They have to be placed in DIR_PUT/cofiles folder of your SUM upgrade directory (for us it is "E:\usr\sap\<SID>\SUM\abap\cofiles")

BEWARE: Please note that

- I had to rename all three attached files in order to let scn.sap.com allow me to attach them; the original extension was "*.SAP"

- file "SolMan_allowfiles2.SAP" has first to be extracted with SAPCAR, and you must place its content in the above mentioned folder.

Hope it helps you and other people who might face the same issue.

Please provide rewards if this solution suited you.

Best regards

Paolo Croene

[Former Member · Accepted solution]

Hello,

This indeed solved my problem in the abap stack. Thank you so much for sharing with us.

Rep added.

[Former Member]

To solve the JAVA error i just created a new folder in the kernel directory with the name "sapjvm_5" and copied the content of sapjvm_4 into it.

Did the job

[ashwani1]

This is absolutely correct answer.

[former_member606092]

Hello,

I am having the exact same situation and did not find a solution to this problem yet, even though I have applied SAP Notes 1678780, 1722606.

Have you succeded with the upgrade, and if yes, how did you manage to solve the errors from your message ?

Thank you in advance,

Paul

[Former Member]

Hello Paul,

I faced the very same issue and thanks to SAP support I was able to solve it.

Please check my reply to Pedro here above to see the details.

Please let us all known if this worked for you as well.

Best regards

Paolo

[former_member606092]

Hello Paolo,

This is indeed the solution to our problem. The "Allowfiles.SAR" attachment of OSS Note 1678780 was not complete - error 5 when extracting with SAPCAR and it unpacked only 301 files. SAP should update the OSS Note ASAP.

However, I used my own workaround which is most likely the same as your solution. I have manually created 6 allow files needed for the upgrade to continue. I can now find those files in your attachment - which makes me very happy: ALEN71SR1SOLMANX1 ,2, 4 and ALDE71SR1SOLMANX1, 2, 4. Basically, the necessary allow files contained only 1 line:

I 2EETW109 table "/POSDW/

and as other files were identical, I realised that I am doing the right thing.

Thank you for your help !

Kind regards,

Paul

[Matt_Fraser]

I wonder if the references to sapjvm_5 were about the SUM tool's own JVM and not the one for the final SolMan system?  My SolMan 7.1 sp8 system is using sapjvm_4, but SUM uses its own JVM separately (though I don't think it's sapjvm_5 either).