本文共 54693 字，大约阅读时间需要 182 分钟。
利用Oracle RDA（ Remote Diagnostic Agent）快速收集Oracle产品分析数据
原文地址： 作者：
Remote Diagnostic Agent (RDA) - RDA文档索引 (文档 ID 1540377.1)
|
|
文档内容
适用于:
OSS Support Tools - 版本 8.05 和更高版本本文档所含信息适用于所有平台
用途
为 RDA 编写的知识文章概述。
适用范围
提供 RDA 相关知识文章的概述及索引。
详细信息
| RDA 主链接 | |||||
|---|---|---|---|---|---|
RDA 文档索引
| 文档 | 知识文章 | 上次更新时间 |
|---|---|---|
| Getting Started | 9-December-14 | |
| Download RDA | 9-December-14 | |
| RDA Release Notes | 9-December-14 | |
| FAQ | 9-December-14 | |
| Training | 9-December-14 | |
| Troubleshooting Guide | 9-December-14 | |
| RAC Cluster Guide | 9-December-14 | |
| HP OpenVMS Guide | 9-December-14 | |
| HP OpenVMS Troubleshooting Guide | 9-December-14 | |
| RAC/Cluster FAQ | 9-December-14 | |
| PDA in RDA | 9-December-14 | |
| HCVE in RDA | 9-December-14 | |
| Man Pages:--RDA Man Pages--IRDA Man Pages--Content Modules Man Page--Core Engine Man Pages--Profile Manual Pages --IRDA plugin Documentation--RDA Setup Questions | 9-December-149-December-149-December-149-December-149-December-149-December-149-December-14 |
Remote Diagnostic Agent (RDA) - Getting Started (文档 ID 314422.1)
|
|
APPLIES TO:
OSS Support Tools - Version 8.16 and laterInformation in this document applies to any platform.
MAIN CONTENT
RDA Getting Started
| RDA Documentation Links | |||||
|---|---|---|---|---|---|
| You are here | | | | | |
In This Document
| | |
RDA Overview
| Note: Please review installation and execution instructions below. If you experience difficulties or receive errors please follow the and for instructions on reporting problems. |
Overview
Remote Diagnostic Agent (RDA) is a command-line diagnostic tool that is executed by an engine written in the Perl programming language. RDA provides a unified package of support diagnostics tools and preventive solutions. The data captured provides Oracle Support with a comprehensive picture of the customer's environment which aids in problem diagnosis.
Oracle Support encourages the use of RDA because it greatly reduces service request resolution time by minimizing the number of requests from Oracle Support for more information. RDA is designed to be as unobtrusive as possible; it does not modify systems in any way. It collects useful data for Oracle Support only and a is provided if required.
This guide provides users with an overview of RDA, the download instructions, and general steps about how to execute RDA within a UNIX, Windows, and Mac OS X environment.
What's New in this RDA Release
See the for information about new features. The next release in RDA 8.x series is scheduled for release in mid-September 2017.
Platforms Supported
At this time, RDA has been successfully tested to run on the following Supported platforms:
- Apple Mac OS X/Darwin
- HP OpenVMS Alpha 7.3-2 and above
- HP OpenVMS Itanium
- HP Tru64 UNIX
- HP-UX Itanium
- HP-UX PA-RISC (32 and 64 bit)
- IBM AIX on POWER Systems(32 and 64 bit)
- IBM Dynix/Ptx
- IBM Linux on POWER
- IBM zSeries Based Linux
- Linux Itanium
- Linux x86 (32 and 64 bit)
- Microsoft Windows 7
- Microsoft Windows 2000 Workstation and Server
- Microsoft Windows 2003 Server
- Microsoft Windows 2008
- Microsoft Windows 2012
- Microsoft Windows Vista
- Microsoft Windows XP Professional
- Sun Solaris Intel
- Sun Solaris SPARC (32 and 64 bit)
Following Platforms are NOT Supported:
- IBM Z/OS (OS/390)
You can run RDA also on other platforms that support Perl 5.005 and later. However, Oracle Support recommends testing on a non-production server first because the performance is unpredictable. For example, you will receive errors when RDA attempts to run utilities and commands that are not supported on these platforms.
Products Supported
RDA collects information that is useful for diagnosing issues related to the following Supported Oracle products
- OLAP Products (Express Server, Financial Analyzer, and Demand Planning Server)
- Oracle Application Server (iAS 1.0.2.x/9.0.x/10.1.2.x/10.1.3.x,10.1.4.x,WebLogic Server (WLS) Release 9.x and 10.x,11g (WLS), HTTP Server,WebCache,J2EE/OC4J)
- Oracle Billing and Revenue Management products
- Oracle BPEL Process Manager
- Oracle Collaboration Suite (Email Server,Calendar,Discussions,Content Services,Workspaces,WebClient,and Wireless)
- Oracle Data Integrator
- Oracle Developer (Forms and Reports)
- Oracle Ebusiness Suite 11i and 12
- Oracle Enterprise Content
- Oracle Enterprise Single Sign-on
- Oracle Enterprise performance management (Hyperion) products
- Oracle Guardian
- Oracle Identity Management products
- Oracle JDBC/PRO *C/ODBC and other development client related information
- Oracle Management Server and Intelligent Agent (Grid Server, Agent Server, DB Control)
- Oracle Networking products
- Oracle RAC Cluster (Single/Multiple Nodes, Automatic Storage Management, Oracle Cluster File System, Data Guard)
- Oracle RDBMS Server (Standard and Enterprise Editions)
- Oracle Retail (Retek)
- Oracle SQL*Plus/iSQL*Plus
- Oracle TimesTen In-Memory Database
- Oracle Universal Archive (11g)
- PeopleSoft
- Siebel
Additional new Oracle products will be supported in future releases. We are constantly enhancing and refining RDA, so make sure you have the latest version! For more detailed information see the Knowledge.
Versions Supported
RDA supports most supported versions of the Oracle products listed in . In most cases, it runs on desupported versions as well, although the collected information may not be as extensive.
Why use RDA?
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. 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, ORA-4030 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
Oracle Configuration Manager
The Oracle Configuration Manager (OCM) is a data collector that collects key Oracle and system statistics of the system that it is running on. As a key component of Oracle Configuration Manager, the OCM collector (scheduler) optimizes the customer benefits of OCM by automating the configuration collections. OCM simplifies your ability to automate your configuration and diagnostics uploads to Oracle. Oracle Configuration Manager bundle provides the following benefits:
- HealthCheck recommendations based on Support best practices when using configuration auto-collection
- Improves Oracle's understanding of your business needs
- Personalized access to best practices and the Oracle Knowledge base
- Pro-active configuration-specific notification of Security and General Alerts
- Project cataloging of key milestones and contacts associated with your configurations
- Secure, automated configuration collection
- Simplified Service Request logging, tracking and reporting
For troubleshooting information or to learn more about Oracle Configuration Manager see the following Oracle Knowledge .
Diagnostic Assistant
The Diagnostic Assistant (DA) tool provides a common, light-weight interface to multiple diagnostic collection tools (ADR, RDA, OCM, Explorer). To learn more about Diagnostic Assistant see the following Oracle Knowledge .
For your benefit, Oracle created an . This bundle contains RDA, OCM, and DA software and it allows customers to install OCM and DA as part of the RDA data collection process.Download
- click the zip file for your platform
- save it locally as rda.zip
Each file contains all of the required files so choose only one to download.
| RDA Bundle (Released MON, D YYYY) | |
|---|---|
| Platform | Download File |
| Apple Mac OS X on Power PC | |
| Apple Mac OS X on x86 | |
| HP OpenVMS | |
| HP Tru64 | |
| HP-UX Itanium | |
| HP-UX PA-RISC | |
| IBM AIX on POWER Systems (32-bit) | |
| IBM AIX on POWER Systems (64-bit) | |
| IBM Dynix/Ptx | |
| IBM Linux on POWER | |
| IBM zSeries Based Linux | |
| Linux Itanium | |
| Linux x86 (32-bit) | |
| Linux x86 (64-bit) | |
| Microsoft Windows (32-bit) | |
| Microsoft Windows (64-bit) | |
| Oracle Solaris SPARC (32-bit) | |
| Oracle Solaris SPARC (64-bit) | |
| Oracle Solaris x86 (32-bit) | |
| Oracle Solaris x86 (64-bit) | |
| Other UNIX platforms | |
| Note: RDA is written in Perl and is a command-line script. Besides Perl and a few basic Perl libraries it is not necessary to install extra software. If for some reason Perl 5.005 or above is not available or is inaccessible on your environment, then a is available for download on major platforms. For additional information please read the - Knowledge Article . |
| Note: In this document represents the different RDA OS command to execute RDA. Therefore substitute rda.sh, rda.pl, or perl rda.pl on UNIX and rda.cmd on Windows in place of . |
Installation Instructions
Instructions for UNIX/ZLinux Type Operating Systems
- Choose or create a directory or area on your UNIX server. Make sure you have sufficient space for the RDA output (~150MB). It does not matter where you create this directory or what it is named, but the same user that runs RDA must own it. Do not use a directory that contains an older version of RDA unless you have deleted the previous version of RDA first. If necessary, you can reuse prior setup files.
Note: The rda.zip creates a directory named "rda" containing all the required files when you extract it.Do not extract the contents of the RDA archive on a Windows client first or you will have to remove the ^M characters from the end of each line in all of the shell scripts in order for them to run. - FTP the rda.zip file to your UNIX server in binary mode and place it in the directory chosen in step 1.
- Extract the .zip archive contents into a new directory, preserving the directory structure of the archive. Do not extract into a directory that contains an older RDA version. For example:
unzip rda.zip
- Make sure the RDA command (rda.sh and rda.pl) is executable. To verify, enter the following command:
chmod +x
- You can verify the RDA installation using the following command:
./ -cv
Instructions for Microsoft Windows Based Operating Systems
- Create a new directory or area on your Windows server. Make sure you have sufficient space for RDA output (~150MB). It does not matter where you create this directory or what it is named, but it should have access to the Oracle software installation. Do notuse a directory that contains an older version of RDA unless you have deleted the previous version of RDA first.
Note: The rda.zip file creates a directory named " rda" containing all the required files when you extract it. - Transfer the rda.zip file to your Windows server and place it in the directory chosen in step 1. If transferring the zip file from one system to another using FTP, remember to transfer it in binary mode.
- Extract the .zip archive contents into a new directory, preserving the directory structure of the archive. For ease of use, please be sure to use a utility such as WinZip or 7z rather than the built in Windows extract facility. Do not extract into a directory that contains an older RDA version.
- You can verify the RDA installation using the following command:
-cv
Instructions for HP OpenVMS Based Operating Systems
Due to the special nature of HP OpenVMS environment, Oracle created a separate document. See the RDA - OpenVMS Users Guide: Knowledge Article .
Instructions for RDA in OPatch Format
RDA is supplied in OPatch format for Fusion Middleware. This can be downloaded from .
Instructions on how to install this are in the Readme provided with the patch.
Running RDA
| Note: It is impossible to tell how long RDA will take to execute, as it depends on many variables, such as system activity, the options chosen, network settings, and so on. On an average system, RDA takes just a few minutes to run. Most scripts are designed to stop if for some reason they cannot complete within 30 seconds, (for example, the lsnrctl status command will stop if the listener is not responding.) It is not unusual for RDA to take 15 minutes or more on a busy server, especially if there are many Oracle listener processes active. |
Instructions for UNIX type operating systems (including ZLinux):
-
- Before you begin: Log on as the UNIX user that owns the Oracle installation. On some operating systems, this user will not have the necessary permissions to run all of the commands and utilities called by RDA (e.g. sar, top, vmstat, etc). If you are running RDA to assist in resolving a service request, the analyst will most likely need the information pertaining to the Oracle owner. The exception to this rule is when RDA is used to assist in a performance related issue. In this case, Oracle support recommends that you run RDA as the UNIX user who owns the Oracle software.
Note: If you use su to connect to root or a privileged user, do not use "su -" as the minus resets the environment. - Select the RDA command line script that you will be using. Choose one of the following:
rda.sh - Use this command if Perl is not available.
rda.pl - Use this command if Perl is available.
Use the following command to verify that Perl is installed and available in the path:perl -V
Inspect the command output, checking that '.' (i.e. tells perl to look for libraries in current directory) is present in @INC section. Notice the last entry "." in the example below:
- Before you begin: Log on as the UNIX user that owns the Oracle installation. On some operating systems, this user will not have the necessary permissions to run all of the commands and utilities called by RDA (e.g. sar, top, vmstat, etc). If you are running RDA to assist in resolving a service request, the analyst will most likely need the information pertaining to the Oracle owner. The exception to this rule is when RDA is used to assist in a performance related issue. In this case, Oracle support recommends that you run RDA as the UNIX user who owns the Oracle software.
| @INC:/usr/lib/perl5/5.8.0/i386-linux-thread-multi/usr/lib/perl5/5.8.0/usr/lib/perl5/site_perl/5.8.0/i386-linux-thread-multi/usr/lib/perl5/site_perl/5.8.0/usr/lib/perl5/site_perl/usr/lib/perl5/vendor_perl/5.8.0/i386-linux-thread-multi/usr/lib/perl5/vendor_perl/5.8.0/usr/lib/perl5/vendor_perl/usr/lib/perl5/5.8.0/i386-linux-thread-multi/usr/lib/perl5/5.8.0. |
- The data collection requires an initial setup to determine which information should be collected. Enter the following command to initiate the set up:
/ -S
After setup completes, you can review the setup file output.cfg by opening in a text editor such as vi. The output.cfg file is located in the directory that RDA was executed from. i.e. If RDA was installed in /rda and executed from /tmp directory, then the setup file is located in /tmp.
-
You can also choose to collect only specific data. For more details, view the command usage help by specifying the -h option, or complete manual page with the -M option.
- Make sure you have ample space for RDA output (approximately 150 MB) in the output location you have chosen in STEP 6. Sometimes, depending on the size of your data files (alert.log, *.trc, install*.log, apache logs, networking logs, etc) of the Oracle installation the final size of your RDA collection may reach over 1000 MB in size.
- At this point, you can collect diagnostic information. sqlplus should connect to the database with the userid that you specified during the setup. Start the data collection using the following command:
./ [-v]
The -v option is optional; it allows you to view the collection progression. Additionally, if you want to re-run the RDA collection, you can use the "-fv" option, for example, ./ -fv. For additional information read the .
- A more targeted way of executing RDA and a way to limit the number of setup questions asked is the use of Diagnostic profiles ( -p ), see for list of various profiles or run -L profiles. e.g:. ./ -p DB10g
- The output is a set of HTML files that are located in a directory created by RDA by default in the working directory that RDA was executed from. The default output directory is called output. You can review the data collected by using a Web Browser to open the following file located in:
/RDA__start.htm
Note: Do not submit any health, payment card or other sensitive production data that requires protections greater than those specified in the Oracle GCS Security Practices (). Information on how to remove data from your submission is available at note - The final output is also packaged in an archive located in the directory that RDA was executed from -- the packaged output file will have a .zip, .tar, .tar.gz, or .tar.Z extension. If the data collection was generated to assist in resolving a Service Request, send the report archive (for example, RDA_output_.tar) to Oracle Support by uploading the file via My Oracle Support. If FTP'ing the file, please be sure to FTP in BINARY format. Please do notrename the file, as the file name helps Oracle Support quickly identify that RDA output is attached to the service request or bundle with other files such as trace or log files into a single or common archive file (.tar, .zip, .jar, etc.)
-
Note: The final output may not generate an archive file (.zip, .tar, .tar.gz, or .tar.Z). If the archive is missing, please archive all of the files in the manually and send them to Oracle Support. You can use a packaging/archive utility program such as to perform this task.
For more information or clarification please review the demonstration viewlets located in the document or please read the . If you still have problems please follow .
Instructions for Microsoft Windows Based Operating Systems
- Before you begin: Log on as the WINDOWS user that owns the Oracle installation. On some operating systems, this user will not have the necessary permissions to run all of the commands and utilities called by RDA (e.g. WinMsd utility, MSInfo32 on Windows 2000, Windows 2003) If you are running RDA to assist in resolving a service request, the analyst will most likely need the information pertaining to the Oracle owner. The exception to this rule is when RDA is used to assist in a performance related issue. In this case, Oracle support recommends that you run RDA as the user who owns the Oracle software.
- Choose one RDA command line script that you will be using, either:
rda.cmd Use this command if Perl is not available.
rda.pl Use this command if Perl is available in the path. To verify if Perl is available, enter the following command:
perl -V
In the command output, verify that '.' (i.e. the current directory) is present in @INC section.
The RDA command rda.cmd or rda.pl you choose is represented as in the rest of this procedure.
- The data collection requires an initial setup to determine which information should be collected. Enter the following command from the Windows Command or DOS prompt to initiate the set up: REMEMBER: means use either rda.cmd or rda.pl.
-S
After setup completes, you can review the setup file output.cfg by opening it a text editor like wordpad. The output.cfg file is located in the directory that RDA was executed from. i.e. If RDA was installed in \rda and executed from \temp directory, then the setup file is located in \temp.
You can also choose to collect only specific data. For more details, view the command usage help by specifying the -h option, or complete manual page with the -M option.
- Make sure you have ample space for RDA output (approximately 150 MB) in the output location you have chosen. Sometimes, depending on the size of your data files (alert.log, *.trc, install*.log, apache logs, networking logs, etc) of the Oracle installation the final size of your RDA collection may reach over 1000 MB in size.
- At this point, you can collect diagnostic information. Sqlplus should connect to the database with the userid that you specified during the setup. Start the data collection using the following command:
[-v]
The -v option is optional. It allows you to view the collection progression. Additionally, if you want to rerun RDA collection again, you can use the "-fv" option like -fv . For additional information, read the .
- A more targeted way of executing RDA and a way to limit the number of setup questions asked is the use of Diagnostic profiles ( -p), see for list of various profiles. e.g: -p DB10g
- The output is a set of HTML files that are located in a directory created by RDA by default in the working directory that RDA was executed from. The default output directory is called output. You can review the data collected by using a Web Browser to open the following file located in:
/RDA__start.htm
Note: Do not submit any health, payment card or other sensitive production data that requires protections greater than those specified in the Oracle GCS Security Practices (). Information on how to remove data from your submission is available at - The final output is also packaged in an archive located in the directory that RDA was executed from -- the packaged output file will have a .zip, .tar, .tar.gz, or .tar.Z extension. If the data collection was generated to assist in resolving a Service Request, send the report archive (for example, RDA_output_.zip) to Oracle Support by uploading the file via My Oracle Support. If FTP'ing the file, please be sure to FTP in BINARY format. Do not rename the file, as the file name helps Oracle Support quickly identify that RDA output is attached to the service request.
The final output may not generate an archive file (.zip, .tar, .tar.gz, or .tar.Z). If the archive is missing, please archive all the files in the manually and send them to Oracle Support. You can use a packaging/archive utility program such as
- When you send/upload an RDA report in a compressed file (such as .zip, .tar, .tar.gz, or .tar.Z), please do so in a separate file and start is named with 'RDA'; this ensures our internal tools and users can find and analyze it correctly. When sending RDA output to Oracle Support via a My Oracle Support Service Request, we highly recommend that you attached the output file as a single file. Do not bundle with other files such as trace or log files into a single or common archive file (.tar, .zip, .jar, etc.)
For more information or clarification please review the demonstration viewlets located in the document or read the . If you still have problems please follow .
Instructions for Oracle RAC Cluster or Multi-Node Environment
Due to the special nature of Oracle RAC Cluster environment a separate document was created. Please refer to RDA - RAC Cluster/Multi-Node Users Guide -
Instructions for HP OpenVMS Based Operating Systems:
Due to the special nature of HP OpenVMS environment a separate document was created. Please refer to RDA - OpenVMS Users Guide - Knowledge
Upgrading RDA
Use the following procedure to manually upgrade the RDA:
- Delete the rda directory and all it's contents. If you want to use the same output.cfg file again, move it to another location first. Also, move any output files you wish to save.
- Download the new version of RDA from this .
- Extract the files in the directory you want to install RDA. It will recreate the rda directory for you.
Remember that the directory structure in the archive is important; don't move any RDA files.
Automated update of RDA
As of March 28, 2011, RDA is automatically upgraded in the following scenario:
OCM is installed and configured in "Connect" mode. OCM auto-update will nowupgrade RDA as part of its normal deployment procedure. For finer control of the RDA upgrade seeSpecial Notes On Userids And Passwords
As a means of providing higher security when using RDA, passwords are no longer stored in plain text in the setup.txt file. As result, RDA prompts for the required passwords when collecting the data.
If the Perl implementation installed on your operating system supports it, RDA will suppress the character echo during password requests. When the character echo is suppressed, the password is requested twice for verification. If both entered passwords do not match after three attempts, the request is cancelled.
RDA can perform OS authentication, which eliminates having to enter a password for database information gathering. It also accepts "/" as a username to avoid entering a password when RDA is gathering database information.
For executing RDA at regularly scheduled intervals via cron, passwords can be encoded inside the setup file. For instance, to encode the system password, use the following command:
-A system
The password will be requested interactively.
Special Note on the Output Directory
To limit security vulnerabilities, the permissions of the RDA output directory should be set as restrictive as possible. The output directory could contain sensitive configuration information and, when no other mechanism is available, temporary data collection files.
Viewing RDA Report Output Files
RDA output is not encrypted and can be viewed by anyone. You can view the RDA report files using almost any web browser by opening the /output/RDA__start.htm.
We recommend using 1.x ( or Higher), Netscape 4.x (or higher), or Internet Explorer 4.x (or higher).
Special Note on Security Filters
The following table is a snapshot of the 'System Settings' section of the end report to demonstrate exactly what Filtering does. The result below is dependent on the system configuration.
| Machine and Version | SunOS 5.6 Generic 105181-29 sun4u |
| Fully qualified host name | |
| Platform | 32 - bit Sun O/S Version 2.6 |
| Logged in as | |
| Last run as | uid=52279 ()gid=101(dba) groups=101(dba) |
| Executed as Oracle home owner? | Yes |
| Sensitive information removed? | Yes |
| Output file prefix | RDA |
| Output file directory | /emea/oracle/ /home/rda2/security/output |
| RDA install directory | /emea/oracle//home/rda2 |
The host names (machine names), are substituted by ''. Similarly, user names are substituted by '' instead of 'oracle'. The group of the software owner is 'dba', which is not substituted by the default filter.
Note that the above report was run as the owner of the Oracle home directory, which was different from 'oracle'. This is the reason why we see '' instead of 'oracle'. The group of the Oracle software owner is 'dba', which is not substituted by the default filter.
The RDA filter substitutes sensitive information (such as user names) using something like in the reports. As shown later in this document, you can customize what information RDA filters out and how RDA substitutes this information.
RDA provides you with a default filter, which currently filters out the information in the list below.
- Domain names
- Group names
- Host names
- IPv4 and IPv6 addresses
- LDAP domain components
- Network masks
- User names
Using Security Filters
RDA allows you to remove sensitive data from RDA reports. The security profile can be used to turn on filtering and can be combined with other profiles. For example:
-S -p DB10g-Security
This will do the RDA setup for the DB10g profile and turn on filtering through the Security profile. If you want to enable the filtering for an existing setup:
-X Filter enable
When the filter is not yet defined, this command will also generate the default filter configuration, based on the system configuration.
Reporting Problems or Feedback
If you have issues with the Remote Diagnostic Agent (RDA), you can file an Non-Technical SR in My Oracle Support. Subject line "Remote Diagnostic Agent (RDA) Issue" and complete the SR.
| Note: Do not let an RDA issue prevent you from progressing on your technical issue that you are running RDA for. Please inform the engineer that owns your technical issue that you are having trouble with RDA and request that he give you instructions on collecting necessary data manually to resolve the issue. RDA is designed to speed up the resolution time of technical issues and we do not want it to interfere with resolution. However, it is important that we get the RDA issue resolved so that it can be used to help speed up resolution for future technical issues |
COPYRIGHT NOTICE
Copyright (c) 2002, 2015, Oracle and/or its affiliates. All rights reserved.
TRADEMARK NOTICE
Oracle and Java are registered trademarks of Oracle and/or its affiliates. Other names may be trademarks of their respective owners.
LEGAL NOTICES AND TERMS OF USE
By downloading and using RDA, you agree to the following: .
DOCUMENTATION ACCESSIBILITY
Our goal is to make Oracle products, services, and supporting documentation accessible to all users, including users that are disabled. To that end, our documentation includes features that make information available to users of assistive technology. This documentation is available in HTML format, and contains markup to facilitate access by the disabled community. Accessibility standards will continue to evolve over time, and Oracle is actively engaged with other market-leading technology vendors to address technical obstacles so that our documentation can be accessible to all of our customers. For more information, visit the Oracle Accessibility Program Web site at
Accessibility of Code Examples in Documentation
Screen readers may not always correctly read the code examples in this document. The conventions for writing code require that closing braces should appear on an otherwise empty line; however, some screen readers may not always read a line of text that consists solely of a bracket or brace.
Accessibility of Links to External Web Sites in Documentation
This documentation may contain links to Web sites of other companies or organizations that Oracle does not own or control. Oracle neither evaluates nor makes any representations regarding the accessibility of these Web sites.
Deaf/Hard of Hearing Access to Oracle Support Services
To reach Oracle Support Services, use a telecommunications relay service (TRS) to call Oracle Support at 1.800.223.1711. An Oracle Support Services engineer will handle technical issues and provide customer support according to the Oracle service request process. Information about TRS is available at , and a list of phone numbers is available at.
Remote Diagnostic Agent (RDA) - FAQ (文档 ID 330363.1)
APPLIES TO:
OSS Support Tools - Version 8.16 and laterMicrosoft Windows (32-bit)
z*OBSOLETE: Microsoft Windows 2000
Linux x86
HP-UX PA-RISC (32-bit)
MAIN CONTENT
Enter the Main Content
RDA FAQ
| RDA Documentation Links | |||||
|---|---|---|---|---|---|
| | You are here. | | | | |
In This Document
| Linux/Unix/Windows/MacOS Issues | |||
|---|---|---|---|
| | | | |
| RAC/Cluster/Multi-Node Environments | |||
| See | |||
| OCM_Related_issues | |||
| | |
| |
Frequently Asked Questions
-
- What is the purpose of Remote Diagnostic Agent (RDA)?
RDA is designed to be platform independent; there is no longer a separate version for UNIX and Windows. RDA code is readable by the customer so that if there are any concerns about security, they can see exactly what is collected. Documentation is included with the RDA code so that customers can understand and troubleshoot RDA themselves. Also, the RDA documentation has been rewritten and is more comprehensive than in the past to give the customer (internal and external) better understanding.
- Is RDA required in order to resolve my SR?
We strongly encourage the use of RDA as it can greatly assist the analyst in resolving your SR, it contain vast amount of configuration and diagnostic data that reduces the "round trip" time needed to resolve most issues.
RDA has a strong focus on robustness and supportability, in the rare case you are unable to use RDA, please update the SR to inform your analyst, and request that work on the SR continue without the benefit of RDA. Oracle engineers are trained to work issues without the aid of RDA.
- What is required to run RDA?
RDA is command line program written in Perl. It uses only basic Perl libraries so the customer should never have to install anything, as long as Oracle software is available. It uses the Perl libraries that are shipped with Oracle or shipped with some UNIX platforms. RDA has been certified and tested on Perl versions 5.005 - 5.10.x. If for some reason Perl is not available or is inaccessible on the customer environment, then a is available for download on major platforms.
Additionally, RDA users need access to the user that owns the Oracle installation. On some operating systems, this user will not have the necessary permissions to run all of the commands and utilities called by RDA on UNIX (e.g. sar, top, vmstat, etc) or on Windows (WinMsd utility and (MSInfo32 on Windows 2000, Windows 2003). If you are running RDA to assist in resolving a SR, the analyst will most likely need the information pertaining to the Oracle owner. The exception to this rule is when RDA is used to assist in a performance related issue. In this case, Oracle support recommends that you run RDA as the UNIX user who owns the Oracle software.
- How much space do I need run RDA?
RDA requirements for space on the host environment for install; 6 - 80 MB depending on the RDA package you decide to install from (.tar, tar.gz, or .zip) and whether you require the RDA file.
Regarding RDA output directory requirements, we have observed 80% of the data collected will require less than 150 MB for the final output files generated. We would recommend you allocate at least 150MB to be on the safe side. Sometimes depending on the size of your data and trace files (alert.log, *.trc, install*.log, apache logs, networking logs, etc) of the Oracle installation the final size of your RDA collection may reach over 1000 MB in size. Review the your Oracle trace and log files sizes and calculate to have space to have copies of those files, formatted RDA html files, and a compressed RDA package.
- Where can I download the RDA package?
You can download RDA from Knowledge Article , the Main RDA page. Select the RDA zip file for your platform by clicking on the related link. Each zip file contains all the files you need, so only choose one to download.
- I don't have Perl. Where can I get a binary or complied version of RDA? rda.sh and rda.cmd do not assume that components containing Perl are installed. As long as RDA finds an ORACLE_HOME and Perl 5.005 and above in the path, it tries to locate itself where the library modules are and sets the environment appropriately. Therefore, we can run RDA even when perl -V does not work correctly and when @INC is not configured. In most recent builds, it also ignores Perl from the path when it can't find some standard required Perl modules. That also prevents using a nonstandard miniperl environment. For performance reasons, we restrict the search to some well known areas.If you still can't run RDA because of problems with Perl, you can download the following binary version for your platform. For RDA versions 4.19 and earlier:1. You must first ensure you have RDA downloaded and installed on the environment you will be running RDA (see Knowledge Article 314422.1 for the latest available version).2. Select and download one of the below binary/compiled versions specific to your operating system where RDA will execute from.
- The zip file below contains the following files specific to the platform:
- readme.txt
- rda_ --> Binary RDA for use on more recent operating systems. Windows binary has ".exe" extension (e.g. rda_win.exe)
- rda_56 --> Binary RDA with old libraries intended for use on older operating systems.
- The zip file below contains the following files specific to the platform:
- readme.txt
- rda_ --> Binary RDA for use on more recent operating systems. Windows binary has ".exe" extension (e.g. rda_win.exe)
- rda_56 --> Binary RDA with old libraries intended for use on older operating systems.
Note: PERL5LIB environment variable must not be set in order to use the following compiled binaries of rda.pl. Make sure your PERL5LIB does not point to any Perl installation.
Platform Specific Compile Agent (Binary) Versions (Released MON, D YYYY) Platform Download File Apple Mac OS X (Power PC and x86) HP Tru64 HP-UX (PA-Risc and Itanium) IBM AIX on POWER Systems Linux (x86 and Itanium) Microsoft Windows Oracle Solaris (SPARC and x86) - The zip file below contains the following files specific to the platform:
- I want to download RDA with OCM, where can I get the RDA/OCM bundles?
RDA Bundle (Released MON, D YYYY) Platform Download File HP-UX Itanium HP-UX PA-RISC IBM AIX on POWER Systems (32-bit) IBM AIX on POWER Systems (64-bit) IBM Linux on POWER IBM zSeries Based Linux Linux Itanium Linux x86 (32-bit) Linux x86 (64-bit) Microsoft Windows (32-bit) Microsoft Windows (64-bit) Oracle Solaris SPARC Oracle Solaris x86 For detailed information on RDA installation, review MOS document .
- How do I download Standalone (generic) RDA?
- How do I run an RDA collection?
The following published document detail how to run RDA. There are also, detailed instructions in the README_Unix.txt and README_Windows.txt files contained inside RDA packages.
- Knowledge Article 314422.1
- How do I force RDA to run Setup again?
RDA will read the values it finds in "output.cfg" first before requiring to answer any setup questions. You can force RDA to start the setup process again in two(2) ways.
- Deleting or renaming the "output.cfg" file $ ./rda.pl -S or c:\>rda.cmd -S or$ ./rda.sh -S
- Running the following RDA command: $ ./rda.pl -Sfn orc:\>rda.cmd -Sfn or$ ./rda.sh -Sfn
- How long does it take to run RDA collection?
One common question people ask is "How fast does RDA run on machine x". The answer is complex and depends on several factors:
1. the processing power of the machine/server that RDA has been executed on. For example, it will run faster on a 4 CPU machine than a single CPU machine.
2. the availability of free system resources at the time RDA executes. If your system is running at 95% CPU utilization then RDA will take much longer on that system than on a system running at 45% CPU utiltzation. Other factors such as I/O and memory also play an important role.
3. the number of RDA modules to be executed. RDA is comprised of individual modules processing specific tasks from operating commands to log file collection. Each module can take a varying amount of time, depending on the amount of data that needs to be processed. In most RDA collections several modules are executing in sequence or parallel, depending on the operating system and modules in question.
4. the size of the files that need to be parsed by RDA. For example, a 100Kb file will be parsed much quicker than a 2Mb file.
5. the performance of the underlying operating system calls. Some commands such as netstat -an can take over 15 minutes to process.
RDA has been configured with a timeout mechanism to avoid certain modules from taking too long to process. The timeout mechanism has been set to thirty (30) seconds for each command and SQL execution.
We cannot, therefore, give exact numbers on how long RDA will take to execute on your environment. However, here are some averages:
- Based on 100 random real world customer RDA outputs uploaded to Support Services, average time was: 438 seconds or 7 mins.
- Based on internal tests.
rda_4.1-051205 Operating system: RHEL AS 3.0 Update 4 - Kernel 2.4.21-20.ELsmp on an i686 CPU: 1 x Xeon 2.80GHz Memory: 1536 MB Database: Oracle Database 10g Enterprise Edition Release 10.1.0.2.0 - ProductionWith the Partitioning, OLAP and Data Mining options Memory (Free) total used free shared buffers cachedMem: 1538936 1495756 43180 0 98844 726916-/+ buffers/cache: 669996 868940 Disks: 2 x 73GB 7200RPM SCSI drives Load (top): 16:30:46 up 355 days, 1:06, 1 user, load average: 0.10, 0.30, 0.20141 processes: 127 sleeping, 1 running, 13 zombie, 0 stopped RDA modules executed: Processing Initialization module ...Processing CFG module ...Processing Sampling module ...Processing OS module ...Processing PROF module ...Processing PERF module ...Processing NET module ...Processing networking information (pings, network files, sql*net files)...Listener and network checks may take a few minutes. please be patient...Processing listener status, services and log for listener LISTENERProcessing Oracle installation module ...Processing RDBMS module ...Processing LOG module ...Processing Web Server module ...Processing Web Server (iAS 1.x) module ...Processing HTTP Server ...Processing End module ... Average execution Time(seconds) over 5 runs: 357 seconds or ~6 minutes
- How do I force RDA to collect data again?
RDA will read the values it finds in directory first. If it finds data that has not been collected it will attempt to collect that data. However if you want RDA to collect data again you can execute the following commands. (-v: verbose , C: collect , R: render into html, P: Package contents of output directory into archive, and f : force execution of all commands.
$ ./rda.sh -vCRPf or
c:\>rda.cmd -vCRPf or $ ./rda.pl -vCRPf or $./rda.sh -vf or c:\>rda.cmd -vfFinally, if you need to run data collection for specific module again you can just run the following command (OS: Operating system and DBA: Database)
$ ./rda.sh -vCRP OS DB or
c:\>rda.cmd -vCRP OS DBANote: The collection process will execute must faster and you will not receive any notices when it completes. This also overwrite the data in the output directory.
- Where is the RDA output located?
The output is a set of HTML files that are located in the working directory that executed RDA, in the "output" directory. You can review the data collected, by using a Web Browser to open the following file located in the output directory:
RDA__start.htm
The final output is also packaged in an archive, located in the working directory that executed RDA -- the packaged output file will have a .zip, .tar, .tar.gz, or .tar.Z extension. If the data collection was generated to assist in resolving a Service Request, send the report archive (note: file name varies, but ends in .zip, .tar, .tar.gz, or .tar.Z ; e.a: RDA_.zip) to Oracle Support by uploading the file via My Oracle Support. If FTP'ing the file, please be sure to FTP in BINARY format. Do not rename the file, as the file name helps Oracle Support quickly identify that RDA output is attached to the service request. >
Note: The final output directory may not contain an archive file (.zip, .tar, .tar.gz, or .tar.Z ). If the archive is missing, please archive all the files in the manually and send them to Oracle Support. You can use a packaging/archive utility program like to perform this task.
- Is there a localized version of RDA?
No. Currently this utility is written in the English language only, including the built in documentation. In the future, Oracle might offer other versions based on customer demand.
- Will RDA find the solution to my SR?
No. RDA is a tool to assist in resolving the customer's issue. As stated above, RDA's purpose is to collect accurate information about the Oracle installation environment. In many cases RDA will collect information that you think is unnecessary, but may be needed during a later stage of the SR or by the next person reviewing the SR (e.g. escalations, development, etc.). In its first phase, RDA is a collection agent. The long term plan is that the next phase RDA will involve a diagnostic component to analyze the information collected.
- There are sections missing my RDA report, Why ?
There may be some confusion about RDA not displaying all reports or sections. A new feature was added to improve search efficiency and consistency between modules; if a report or section does not contain information, then it is not generated. This was already the case for some modules in the previous version of RDA and it has been generalized. Another factor for this change is that relevant directories could be different from platforms (e.g. UNIX >< Windows) and can even differ between RAC and non-RAC environments.
If the operating system commands error out, the reports are not generated.
If an unexpected error (e.g. table not found) is encountered, it will be visible in the reports. Some results can be incomplete due to execution timeouts. An overview of SQL execution is provided in the Report Settings report.
SQL Request Overview Module Requests Errors Time-Out Skipped Comment S000INI 1 0 0 0 SQL execution limited to 30s S110PERF 3 0 0 0 S125GTW 1 0 0 0 S200DB 34 0 0 0 SQL execution limited to 30s S300IAS 2 0 0 0 SQL execution limited to 30s S400RAC 3 0 0 0 On another hand, the absences of optional components are not considered as an error. The error explanation (-E) and the readme indicates how to change DFT/N_SQL_TIMEOUT and other timeout parameters.
- What does the RDA-nnnnn error mean when I executed RDA?
RDA has a built in error handling mechanism. You can discover the meaning and possible solution to the error by using the following RDA command line argument: rda.pl -E {ERROR #} . i.e:
-
-
>
> -
>
-
-
-
-
-
> -
> -
-
-
-
>
-
-
-
-
> > > -
-
-
-
-
-
-
-
- What is the purpose of Remote Diagnostic Agent (RDA)?
>
转载地址：http://cpcia.baihongyu.com/