How to Run Remote Diagnostic Agent on OSB Domain

I’ve been asked to look into the problem that happened in a live OSB instance. After years of working with Oracle Fusion Middleware products like WebLogic, OSB, and SOA Suite, I don’t want to take the error at face value. This is because I’ve learned that sometimes the error we see in the logs isn’t really the problem, but just a sign of the real problem. The errors I saw were linked to security, and someone suggested that I set up Cross Domain Security. But I know that’s not the problem, because I fell for that trick myself and the problem still happens.

So never again.

I asked them to run RDA (Remote Diagnostics Agent) on their OSB domain so I could get a general idea of how their domain is set up while I looked into the problem. The Diagnostic Repository, which keeps track of events that have happened in the instance, will also be used. Diagnostic Repository is helpful because it keeps a readme.txt file that describes the problem along with other files that help, like a JRF file and a thread dump. Then I was able to figure out that their Work Manager is giving them trouble because it has hit its limits.

So you see, it’s a good thing to run when investigating an issue – or helping someone who’s doing the investigation.

The Remote Diagnostic Agent (RDA) is a critical tool for diagnosing and troubleshooting issues within Oracle environments, including Oracle Service Bus (OSB) domains. It’s designed to collect a comprehensive set of diagnostic information that can help pinpoint the root cause of problems, especially in complex middleware setups like WebLogic, OSB, and SOA Suite.

When investigating an issue in an Oracle environment, it’s common to encounter misleading error logs. These logs may suggest problems like security configuration errors or prompt unnecessary actions like setting up Cross Domain Security. However, the real issue might be entirely different, as in the case where a Work Manager hits its operational limits.

Running the Remote Diagnostic Agent (RDA) provides a broader view of the OSB domain setup. It gathers data from the Diagnostic Repository, which tracks events and creates a detailed record of the system’s state, including helpful files like JRF (Java Required Files) and thread dumps. These can reveal the actual cause of the issue, enabling you to address the real problem rather than getting sidetracked by misleading error messages.

For anyone managing Oracle middleware products, running RDA should be a go-to step in your diagnostic process. It not only helps you avoid common pitfalls but also ensures you have a solid understanding of your domain’s configuration, leading to more effective troubleshooting and problem resolution.

Here’s how to run RDA on OSB:

Setup RDA Configuration for OSB Domain

You can execute the following commands to declare the ORACLE_HOME and DOMAIN_HOME environment variables:

</>Shell

1.   export ORACLE_HOME=/u01/app/oracle/Middleware/Oracle_Home
2.   export DOMAIN_HOME=/u01/app/oracle/Middleware/Oracle_Home/user_projects/domains/my_OSB_domain

… or if you don’t want to do that, you can run this command to initialize those variables

</>shell

1.  source $DOMAIN_HOME/bin/setDomainEnv.sh

</>Batch

1.  %DOMAIN_HOME%\bin\setDomainEnv

Run RDA to Configure the Data Collection

Go to the RDA_HOME and run rda.sh:

</>Shell

1.  cd $ORACLE_HOME/oracle_common/rda
2.  
3.  ./rda.sh -S -p FM12c_OsbMin

Run RDA Again to Start Data Collection

1.  cd $ORACLE_HOME/oracle_common/rda
2.  
3.  ./rda.sh

Collect the RDA Zip File

RDA will create a zipped file of the data collected and put it in the RDA Home.

So there you go! You can extract that folder and open __RDAstart.htm to see the output.


In conclusion, the Remote Diagnostic Agent (RDA) is an invaluable tool for anyone working with Oracle Fusion Middleware products like OSB, WebLogic, and SOA Suite. It offers a comprehensive diagnostic approach that goes beyond surface-level error logs, allowing you to uncover the true cause of issues in your domain. By incorporating RDA into your troubleshooting process, you can avoid common diagnostic pitfalls and ensure that you’re addressing the root cause of problems, leading to more efficient and effective resolution. Always remember, the key to successful problem-solving lies in understanding the complete picture, and RDA provides exactly that.

Still need guide? Must Read our Posts

Remote Diagnostic Agent (RDA)

Little Things Worth Knowing: Enhancing Your Use of the Remote Diagnostic Agent with Profiles

Comprehensive Guide to Oracle Remote Diagnostic Agent (RDA) Setup and Usage