Oracle strongly encourages the use of Remote Diagnostic Agent (RDA) diagnostics collections because it provides a comprehensive picture of the customer's environment. Providing RDA diagnostic output, especially when submitting a Service Request online, can minimize the requirement for follow up questions that may delay problem resolution.
There are several reasons why RDA is useful in Oracle:
-
1. Proactive monitoring: RDA can be scheduled to run automatically at regular intervals, collecting diagnostic information and alerting database administrators to potential issues before they become critical.
-
2. Detailed diagnostics: RDA collects a wealth of information about the system, including operating system settings, network configurations, and database parameters. This information can help diagnose a wide range of issues.
-
3. Faster resolution of issues: When Oracle support is involved, RDA can provide detailed information that can help speed up the resolution of issues.
-
4. Reduced downtime: By proactively monitoring the system and identifying potential issues early, RDA can help reduce downtime caused by unexpected failures.
-
-
RDA collections are essential for the following types of service requests:
-
# Acquired company product issues
# Developer issues
# Installation/configuration issues
# ORA-600, ORA-7445, ORA-3113, and ORA-4031 errors
# Oracle Database issues
# Oracle Application Server/Fusion Middleware issues
# Oracle Collaboration products (Oracle Collaboration Suite and Oracle Beehive) issues
# Oracle Application issues
# Other corrective issues
# Performance issues
# Upgrade, migration, and linking issues
