Diagnostics Agent Doesn’t Start on LINUX


Cause

  • The kernel bundled with the installer 7.3 SP02 or lower is not supported on Linux 3.x
  • Error message “”This patch level of the Startup Framework 720 has not been released for OS release Linux 3.x”

  Resolution

Upgrading kernel of Diagnostic Agent is generally not recommended. In any doubt on any issue being related or not to diagnostic agent kernel version, please raise a support message


Approach 1:-


Diagnostics Agent – How to upgrade SAP Kernel


You are in one of the following cases:

  • After upgrading the operating system you get an error message during the Diagnostics Agent restart like: “OS release <…> is not supported with this kernel (<…>)” or “<…> has not been released for OS release <…> <…>”.
  • Your operating system is only released with Kernel 720_EXT.
  • Your operating system is only released with Kernel 721_EXT.


1. Obtaining the Archives

Download the latest SAPEXE archive from the SAP Service Marketplace under:


Software Downloads -> Support Packages and Patches -> A-Z Index -> K -> SAP KERNEL * UNICODE, and rename it from SAPEXE_<XXX>.SAR to SAPEXE.SAR.


If you upgrade from a Diagnostics Agent that was installed using a Diagnostics Agent Standalone Installer, you should expect up to 3 GB additional disk space consumption during and after the upgrade.

2. Preparations

1. Stop all the Diagnostics Agents available on your host.

2. Stop sapstartsrv

On UNIX: kill -2 <PID of sapstartsrv>

3. Remove any IPC objects that still exist (Unix only)

  Cleanipc <instance no> remove


3. Importing the new kernel on UNIX

Copy the kernel into a temporary directory <newkernel>.

1. Log on as user<dasid>adm and switch to the directory /usr/sap/<DASID>/SYS/exe/uc/<platform>

2. Save the sdiagag.lst file if it exists (from the <platform> directory)

3. Recommend saving the old kernel before deploying the new kernel.

4. Delete all of the files from the <platform> directory, including the subdirectories. This ensures that there are no remaining files from the earlier release.

    • ATTENTION: Make sure you are in directory /usr/sap/<DASID>/SYS/exe/uc/<platform>
      Execute: rm -rf *

5. Create a new <platform> directory and navigate to this directory to restore the sdiagag.lst file saved in step 2 (if it exists).

6. Unpack the new kernel in the <platform> directory:

           SAPCAR -xvf <new kernel>/SAPEXE.SAR

7. Switch to the Diagnostics Agent instance exe directory /usr/sap/<DASID>/SMDA<XX>/exe and save the sapjvm* files and directories.

8. Delete all content from Diagnostics Agent instance exe directory.

    • ATTENTION: Make sure you are in directory /usr/sap/<DASID>/SMDA<XX>/exe
      Execute: rm -rf *

9. Restore the sapjvm* files and directories you saved in step 7.

10. Since executables from the local instance executable directories may already be executed during the start, before sapcpe runs, perform an initial copy of the executables:

           cd /usr/sap/<DASID>/SMDA<XX>/work
sapcpe pf=/usr/sap/<DASID>/SYS/profile/<DASID> _SMDA<XX>_<hostname>


Approach 2:-


Diagnostics Agent – How to perform Agent Replacement

To replace a Diagnostics Agent, install a new Diagnostics Agent, and uninstall the previous Diagnostics Agent. This procedure can be relevant in the following scenarios:

  • Replace a Diagnostics Agent, which has problems that cannot be easily resolved.
  • “Upgrade” a Diagnostics Agent system, e.g.
  • Install a new Diagnostics Agent using a newer installer and a newer kernel, and get a Diagnostics Agent that has a new SAP JVM and a new SAP Kernel.
  • uninstall the previous Diagnostics Agent and Reset the server name in SOLMAN.
To report this post you need to login first.

3 Comments

You must be Logged on to comment or reply to a post.

Leave a Reply