SUM Error: Could not detect AS Java release

This post discusses various known issues and solutions to deal with the following error when running Software Upgrade Manager (SUM):

Could not detect AS Java release.
Return code condition success evaluated to false
for process /usr/sap/<SID>/<INST>/j2ee/cluster/bootstrap/scripts/version.sh
for action ACTION_VERSION.

Using DEFAULT configuration fro web methods protection

  1. Edit DEFAULT.PLF file from /usr/sap/(SID)/SYS/profile and set configuration: service/protectedwebmethods = DEFAULT
  2. Restart all the SAP instances (including sapstartsrv) and retry the failed step.

Replace the scripts

  1. Download the latest SERVERCORE.SCA patch file from service market place.
  2. Extract sap.com~bootstrap.sda.sda from SERVERCORE.SCA/DEPLOYARCHIVES with an archiver.
  3. Extract the following files from sap.com~bootstrap.sda.sda/script
    launcher.bat
    launcher.csh
    launcher.sh
    version.bat
    version.csh
    version.sh
    version.jstart
  4. Go to /usr/sap/[SID]/[INSTANCE]/j2ee/j2ee/cluster/bootstrap/scripts directory and backup all the launcher.* and version.* files.
  5. Copy the files from step 3 to this location.
  6. Ensure that the files have execute permissions against <sid>adm user (run the command chmod +x *.sh *.csh if the execute permissions are missing)

Apply latest patch of SAP JVM

The version.sh runs the launcher.sh script, which in turn launches the tool jstart. If there is any issue with the JVM, the tool won't start and the determination of engine release fails. One known solution is to apply the latest SAP JVM,

To troubleshoot any further, you have to tun version.sh manually, check dev_server<X> files or the latest traces in work folder.

Comments

Post a Comment

Popular posts from this blog

OS/DB Migration - CMD. STR, TOC, EXT, R3load, DDLDBS.TPL and more

Image
With increasing need to improve performance or reduce costs or vanishing support for operating systems/databases it becomes inevitable to migrate to a better OS or DB. We feel take a quick look at the primary ingredients of the tools for OS/DB migration handled by R3SETUP. Tools - R3load, R3ldctl and R3szchk R3ldctl creates STRucture files, TemPLate files by reading the technical settings for table/indexes in SAP data dictionary. R3szchk calculates the database size object sizes (EXTent files) for the target system based on the STR files created by R3ldctl. The EXT and STR files can be later split into smaller groups. The most crucial tool R3load is responsible for unloading and loading data from the database. R3load uses the files created by R3ldctl and R3szchk and dumps the data into compressed binary format as .001, .002 .. files. It uses cmd files to achieve the task. If the cmd files are not present, it creates on its own. Files Command files*.cmd  are created i
Read more

Fixing Inconsistent Table - Table activation fails due to inconsistency between DD and DB

If you find a table to be available on the database, but not active in ABAP dictionary, try calling SE14 as DDIC user, enter the table name and choose Table > Reconstruct, Execute. If this method fails follow these steps: Call transaction code SE37 and execute the function module  DD_TABL_ACTM with single test On the next screen, do not change any other field except the following and set them as shown below: MODE: 12 NTAB_PUTSTATE: N TABNAME: <enter the correct table name> Click on Execute The export parameter ACT_RESULT should show 0. To verify if the inconsistency is fixed, call transaction SE14 > Extras > Database Object > Check and  SE14 > Extras > Runtime object > Check.
Read more

301 Redirect Using SAP Web Dispatcher

301 redirects are typically used to redirect accesses that include www to non-www or vice-versa. Example, when you call http://blogger.com, the call is redirected to www.blogger.com. An end-user may prefer to call a URL in any manner. You must ensure that all these calls are redirected to relevant URLs with content. SAP web dispatcher can be configured to send a redirect (301) to the client. To enable redirection add icm/HTTP/redirect_<xx> to the web dispatcher's profile file. The parameter uses the following syntax: icm/HTTP/redirect_<xx> = PREFIX=<URL prefix>[, FROM=<pattern for URL>, FROMPROT=<incoming protocol>, FOR=<pattern for host name:port>,TO=<new URL prefix>, PROT=<protocol>, HOST=<host>, PORT=<port number/name>] Let's say you want to redirect all the HTTP requests on mysource.com on 80 port to mytarget.com on HTTPS 443 port icm/HTTP/redirect_0 = PREFIX=/, FROM=*, FROMPROT=http, FOR=mysource.com:80,
Read more