RDA – Remote Diagnostic Agent

Recently we had been facing crash issues in our Siebel Production Environment for which we opened a SR with Siebel. Now we all know that once that happens then it would take at least 2-3 days to provide all the information required by Siebel to even start looking at issue. Here is small list of what you might have to provide:

 

  • Crash Files
  • Log files
  • Local DBF
  • Core files (if any)
  • crash.txt

Now depending on your issue there could be several other things that might be added to it. To be fair to them to determine the root cause of a crash anyone would need all the information that they can get.  But critical time is wasted in acquiring all this information and provide to them which could be utilized to focus on crash otherwise.  Now there is a tool available that can help in easing your pain and provide all the required information in one shot.

Remote Diagnostic Agent (RDA) (Knowledge Article 314422.1) is the answer to the above problem. RDA is a less known tool developed in house by Oracle engineers to collect the necessary information about your environment and issue. You can download RDA from the following link based on your OS. It is available for almost all OS flavors.

You can follow the steps provided in Doc ID 314422.1 to download and configure RDA for your Siebel Installation.  Once configured and run properly it will create a package that can be uploaded to oracle support for there analysis.  Here are steps that you will need to perform for an Siebel installation on Solaris environment.

 

  1. Download the appropriate OS version of RDA 4.25 from the “Download RDA” section of Doc ID 314422.1 (Remote Diagnostic Agent (RDA) 4 – Getting Started).
  2. Unzip RDA under the SIEBEL_ROOT/siebsrvr directory of the server where you had the crash. The result should be a SIEBEL_ROOT/siebsrvr/rda directory with other files and subdirectories under this one.
  3. Download a copy of the solgrabcore.zip file found in the Solaris Solution section from Doc ID 477520.1 (How To Troubleshoot Siebel Server Component Crashes on UNIX). This file contains the solgrabcore.sh script which should be placed under the SIEBEL_ROOT/siebsrvr/bin directory of the machine.
  4. Please note that all RDA commands and options are case sensative. Run the following command from the SIEBEL_ROOT/siebsrvr/rda directory and provide the appropriate input values:
    ./rda.sh -vT siebel
    Note: Please have the following details available to input for the prompts:
    Siebel Server Home (same as SIEBEL_ROOT above)
    Application Enterprise Name
    Application Server Name
    Advanced collection enabled – Y
    Process Identifier
    Core File location – (please verify the directory location of the core file. ensure the entire path including the core file name is provided for this value)
  5. Run the following command from the /siebel/siebsrvr/rda directory and provide the appropriate input responses:
    ./rda.sh -p Siebel
    Note: When it prompts for the Oracle Home, it will default to an installation of an Oracle application (usually the DB), however please ensure you use the SIEBEL_ROOT directory when prompted for this value.
  6. A zip file willbe be created in rda/output directory. Attach the final RDA*.zip file to the SR. The format of the file will be similar to RDA.RDA_<machine-name>.zip. Refer to command line output for actual file name that is generated.

Below are some screenshots of the RDA package output

RDAHomePage

RDASiebelSection

RDASiebelCrash

 

Happy Debugging!!

Leave a Reply

Contribute