利用Oracle RDA（ Remote Diagnostic Agent）快速收集Oracle产品分析数据
内容导读
互联网集市收集整理的这篇技术教程文章主要介绍了利用Oracle RDA（ Remote Diagnostic Agent）快速收集Oracle产品分析数据，小编现在分享给大家，供广大互联网技能从业者学习和参考。文章包含107000字，纯文字阅读大概需要153分钟。
内容图文
利用Oracle RDA（ Remote Diagnostic Agent）快速收集Oracle产品分析数据
Remote Diagnostic Agent (RDA) 是一个工程师用Perl语言编写的命令行诊断工具，RDA提供统一的诊断工具支持包和预防的解决方法。提供给Oracle支持收集的客户环境全面的数据信息能够帮助问题的诊断。
Oracle支持鼓励使用RDA，因为它能对于更多信息最小化请求数量而大大减少服务请求解决的时间。RDA不会对系统做任何的修改，它只为Oracle支持收集有用的数据，如果需要可以提供经安全过滤的数据。
一.支持的平台。
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 Vista
Microsoft Windows XP Professional
Sun Solaris Intel
Sun Solaris SPARC (32 and 64 bit)
目前不支持的平台：
IBM Z/OS (OS/390)
二.支持的Oracle产品。
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
三.安装要求。
1).单独目录。
2).空间大于150M。
3).如果有老版本的RDA，需要删除所有原有的老版本文件。
4).RDA是通过Perl语言开发的工具，可以使用系统的Perl环境，也可以使用RDA自带的Perl环境。
四.安装操作。
1).unzip rda.zip
2).Make sure the RDA command (rda.sh and rda.pl) is executable. To verify, enter the following command:
chmod +x
3).You can verify the RDA installation using the following command:
./ -cv
下面是验证RDA安装的例子：
[oracle@redhat5 rda]$ ./rda.pl -cv
Loading the file list ...
Checking the directory '.' ...
Checking the directory 'IRDA' ...
Checking the directory 'IRDA/CV0100' ...
Checking the directory 'RDA' ...
Checking the directory 'RDA/Archive' ...
Checking the directory 'RDA/Driver' ...
Checking the directory 'RDA/Handle' ...
Checking the directory 'RDA/Library' ...
Checking the directory 'RDA/Local' ...
Checking the directory 'RDA/Object' ...
Checking the directory 'RDA/Operator' ...
Checking the directory 'RDA/Value' ...
Checking the directory 'RDA/Web' ...
Checking the directory 'dfw/cv0100' ...
Checking the directory 'engine' ...
Checking the directory 'hcve' ...
Checking the directory 'modules' ...
五.RDA工具介绍。
1).rda.sh - Use this command if Perl is not available.
2).rda.pl - Use this command if Perl is available.
3).Use the following command to verify that Perl is installed and available in the path:
perl -V
下面是执行perl -V命令的例子：
......
@INC:
/usr/lib64/perl5/site_perl/5.8.8/x86_64-linux-thread-multi
/usr/lib/perl5/site_perl/5.8.8
/usr/lib/perl5/site_perl
/usr/lib64/perl5/vendor_perl/5.8.8/x86_64-linux-thread-multi
/usr/lib/perl5/vendor_perl/5.8.8
/usr/lib/perl5/vendor_perl
/usr/lib64/perl5/5.8.8/x86_64-linux-thread-multi
/usr/lib/perl5/5.8.8
.
返回类似上面的结果表示当前系统用户有Perl环境。
4).如果是Windows环境，那么rda工具有如下的区别：
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验证Perl语言环境。
六.RDA的使用。
1).初始化RDA工具：
The data collection requires an initial setup to determine which information should be collected. Enter the following command to initiate the set up:
./ -S
根据提示完成配置工作。
Including the dot ensures that RDA is executed from the local directory.
After setup completes, you can review the setup file setup.cfg by opening it a text editor such as vi.
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.
2).生成RDA报告：
Make sure you have ample space for RDA output (approximately 150 MB) in the output location you have chosen in STEP 4. 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 RDA FAQ.
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 RDA Profiles 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 the RDA output directory which you specified at setup. You can review the data collected by using a Web Browser to open the following file located in:
/__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 (http://www.oracle.com/us/support/library/customer-support-security-practices-069170.pdf). Information on how to remove data from your submission is available at note 1227943.1
The final output is also packaged in an archive located in the chosen during RDA setup -- 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.RDA_db_autoxyz.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.)
参考文章：
RDA文档索引 (文档 ID 1540377.1)
Remote Diagnostic Agent (RDA) 4 - Getting Started (文档 ID 314422.1)
--end--
Remote Diagnostic Agent (RDA) - RDA文档索引 (文档 ID 1540377.1)
| 类型: 状态: 上次主更新: 上次更新: 语言: |
| BULLETIN PUBLISHED 2014-12-29 2015-1-5 English简体中文 |
文档内容
| 用途 |
| 适用范围 |
| 详细信息 |
| RDA 文档索引 |
| 版权声明 |
| 商标声明 |
| 法律声明和使用条款 |
| 文档可访问性 |
| 参考 |
适用于:
OSS Support Tools - 版本 8.05 和更高版本
本文档所含信息适用于所有平台
用途
为 RDA 编写的知识文章概述。
适用范围
提供 RDA 相关知识文章的概述及索引。
详细信息
| RDA 主链接 | |||||
|---|---|---|---|---|---|
| Getting Started | FAQ | RDA Manual Pages | Troubleshooting Guide | Training | RDA Documentation Index |
RDA 文档索引
| 文档 | 知识文章 | 上次更新时间 |
|---|---|---|
| Getting Started | Note 314422.1 | 9-December-14 |
| Download RDA | Note 314422.1 | 9-December-14 |
| RDA Release Notes | Note: 414970.1 | 9-December-14 |
| FAQ | Note: 330363.1 | 9-December-14 |
| Training | Note: 330344.1 | 9-December-14 |
| Troubleshooting Guide | Note: 330362.1 | 9-December-14 |
| RAC Cluster Guide | Note: 359395.1 | 9-December-14 |
| HP OpenVMS Guide | Note: 171748.1 | 9-December-14 |
| HP OpenVMS Troubleshooting Guide | Note: 366522.1 | 9-December-14 |
| RAC/Cluster FAQ | Note: 359388.1 | 9-December-14 |
| PDA in RDA | Note: 392591.1 | 9-December-14 |
| HCVE in RDA | Note: 250262.1 | 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 | Note: 330364.1 Note: 1275867.1 Note: 330760.1 Note: 330777.1 Note: 391983.1 Note: 1275850.1 Note: 1073385.1 | 9-December-14 9-December-14 9-December-14 9-December-14 9-December-14 9-December-14 9-December-14 |
Remote Diagnostic Agent (RDA) - Getting Started (文档 ID 314422.1)
类型: 状态: 上次主更新: 上次更新: 语言: | DIAGNOSTIC TOOLS PUBLISHED 2017-6-14 2017-6-14 English日本語 |
APPLIES TO:
OSS Support Tools - Version 8.16 and later
Information in this document applies to any platform.
MAIN CONTENT
RDA Getting Started
| RDA Documentation Links | |||||
|---|---|---|---|---|---|
Getting Started | FAQ | Man Pages | Troubleshooting Guide | Training | RDA Documentation Index |
In This Document
|
|
RDA Overview
Note: Please review installation and execution instructions below. If you experience difficulties or receive errors please follow the RDA Troubleshooting Guide and RDA FAQ 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 security filter 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 RDA Release Notes 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 Knowledge330760.1.
Versions Supported
RDA supports most supported versions of the Oracle products listed in Products Supported. 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 369619.1.
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 201804.1.
For your benefit, Oracle created an RDA/DA/OCM bundle. 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 | Download Zip File | ||||||
| Apple Mac OS X on x86 | Download Zip File | ||||||
| HP OpenVMS | Download Zip File | ||||||
| HP Tru64 | Download Zip File | ||||||
| HP-UX Itanium | Download Zip File | ||||||
| HP-UX PA-RISC | Download Zip File | ||||||
| IBM AIX on POWER Systems (32-bit) | Download Zip File | ||||||
| IBM AIX on POWER Systems (64-bit) | Download Zip File | ||||||
| IBM Dynix/Ptx | Download Zip File | ||||||
| IBM Linux on POWER | Download Zip File | ||||||
| IBM zSeries Based Linux | Download Zip File | ||||||
| Linux Itanium | Download Zip File | ||||||
| Linux x86 (32-bit) | Download Zip File | ||||||
| Linux x86 (64-bit) | Download Zip File | ||||||
| Microsoft Windows (32-bit) | Download Zip File | ||||||
| Microsoft Windows (64-bit) | Download Zip File | ||||||
| Oracle Solaris SPARC (32-bit) | Download Zip File | ||||||
| Oracle Solaris SPARC (64-bit) | Download Zip File | ||||||
| Oracle Solaris x86 (32-bit) | Download Zip File | ||||||
| Oracle Solaris x86 (64-bit) | Download Zip File | ||||||
| Other UNIX platforms | Download Zip File | ||||||
Note: RDA is also shipped with multiple Oracle products, for instance: Oracle Fusion Middleware, Oracle Communications Billing and Revenue Management, Oracle Configuration Manager, RAC and DB Support Tools Bundle , Oracle Services Tools Bundle …
| 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 binary version is available for download on major platforms. For additional information please read the RDA FAQ - Knowledge Article 330363.1. |
| 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 downloaded 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 downloadedrda.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 171748.1.
Instructions for RDA in OPatch Format
RDA is supplied in OPatch format for Fusion Middleware. This can be downloaded from here.
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 RDA FAQ.
- 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 RDA Profiles 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 (http://www.oracle.com/us/support/library/customer-support-security-practices-069170.pdf). Information on how to remove data from your submission is available at note 1227943.1 - 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 http://www.info-zip.org/Zip.html to perform this task.
For more information or clarification please review the demonstration viewlets located in the Training document or please read the RDA FAQ. If you still have problems please follow Troubleshooting Steps.
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 RDA FAQ.
- 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 RDA Profiles 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 (http://www.oracle.com/us/support/library/customer-support-security-practices-069170.pdf). Information on how to remove data from your submission is available at 1227943.1 - 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 http://www.info-zip.org/Zip.html
- 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 Training document or read the RDA FAQ. If you still have problems please follow Troubleshooting Steps.
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 - 359395.1
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 171748.1
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 Download RDA.
- 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 now
upgrade RDA as part of its normal deployment procedure.
For finer control of the RDA upgrade see README_upgrade.txt
Special 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 Mozilla 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: Warranties and Disclaimers.
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
http://www.oracle.com/accessibility/
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 http://www.fcc.gov/cgb/consumerfacts/trs.html , and a list of phone numbers is available athttp://www.fcc.gov/cgb/dro/trsphonebk.html.
Remote Diagnostic Agent (RDA) - FAQ (文档 ID 330363.1)
APPLIES TO:
OSS Support Tools - Version 8.16 and later
Microsoft 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 | |||||
|---|---|---|---|---|---|
Getting Started | FAQ | Man Pages | Troubleshooting Guide | Training | RDA Documentation Index |
In This Document
| Linux/Unix/Windows/MacOS Issues | |||
|---|---|---|---|
|
|
| |
| RAC/Cluster/Multi-Node Environments | |||
| See RAC Cluster Guide - Knowledge Article | |||
| OCM_Related_issues | |||
|
|
| |
Frequently Asked Questions
- 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.
- 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.
- Run a few simple tests to verify that Perl is working:
./rda.pl -h (does this work?)
./rda.pl -c (does this work?)
./rda.pl -V (does this work?) - If any of the above steps cause a hang or core dump, than your current Perl installation contains Perl modules (.pm) that have been corrupted, please either install a newer Perl installation or use the RDA binary version
- Test where the failure is occurring during data collection.
rda.sh -vt90 or
rda.cmd -vt90 (This command will run a debug and trace of all the commands executed, and will let you see when it core dumps) - Provide the output of the above command to Oracle Support for Review.
- 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 or
c:\>rda.cmd -Sfn or
$ ./rda.sh -Sfn - 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 binary version 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 RDAbinary version 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 314422.1, 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. 3. Place the binary file from step 2 into the same directory as the "rda.pl" file is located from step 1. (e.g. Place rda_win.exe in the same directory as rda.pl).
4. To execute, enter "rda_ -S" rather than "rda.pl" or "rda.sh" or "rda.cmd". (e.g. Execute rda_win.exe -S). Starting with RDA 4.20 and all future releases:
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.
3. Place the binary file from step 2 into the /rda/engine/ directory used in step 1. (e.g. After moving or copying file. The rda_win.exe path is /rda/engine/rda_win.exe).
4. Confirm that the binary rda in the /rda/engine directory has execute permissions.
5. The rda.cfg in the standard distribution of RDA, RDA, contains the following entries:
RDA_ENG=""
RDA_EXE="rda.exe"
D_RDA=".."
Using the same compiled engine systematically for an RDA installation
---------------------------------------------------------------------
When you want to use a compiled engine through usual RDA commands (rda.cmd or
rda.sh). You must edit the rda.cfg file contained in the engine directory. Its
initial content is:
RDA_ENG=""
RDA_EXE="rda.exe"
D_RDA=".."
After making the file writable, specify the compiled engine name in the RDA_ENG
value. For Windows, you will have:
RDA_ENG="rda_win.exe"
RDA_EXE="rda.exe"
D_RDA=".."
On the first invocation of rda.cmd, the start script will take a copy of the
compiled engine in the RDA installation directory. On subsequent executions,
the start script is checking if a new version of the specified compiled engine
is available. When available, the start script will copy that new version to
rda.exe in the installation directory.
For UNIX, you must use rda.sh to obtain the same result.
Using a compiled engine in a shared or in a read-only installation
------------------------------------------------------------------
When the RDA installation is shared between different systems or different
users, the same compiled engine is not necessarily applicable to everybody or
the installation directory is not necessarily writable for everybody.
In this case, RDA uses the work directory to store the copy of the specified
compiled engine. Create in the working directory an rda.cfg file with the
following content:
RDA_ENG=""
RDA_EXE="rda.exe"
D_RDA=""
For instance,
RDA_ENG="rda_linux.exe"
RDA_EXE="rda.exe"
D_RDA="D:\MyOracleHome\rda"
After that, you can use the usual start scripts.
For UNIX,
/rda.sh
For Windows,
\rda.cmd
On the first invocation of the start script, it will take a copy of the
compiled engine in the RDA installation directory. On subsequent executions,
the start script will check if a new version of the specified compiled engine
is available. When available, the start script will copy that new version to
rda.exe in the installation directory.
The copy mechanism preserves the possibility to upgrade only the shared
installation when a new RDA version is available. Each user will get their
compiled engine copy automatically updated at next run.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) Download Zip File
HP Tru64 Download Zip File
HP-UX (PA-Risc and Itanium) Download Zip File
IBM AIX on POWER Systems Download Zip File
Linux (x86 and Itanium) Download Zip File
Microsoft Windows Download Zip File
Oracle Solaris (SPARC and x86) Download Zip File
- 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 Download Zip File
HP-UX PA-RISC Download Zip File
IBM AIX on POWER Systems (32-bit) Download Zip File
IBM AIX on POWER Systems (64-bit) Download Zip File
IBM Linux on POWER Download Zip File
IBM zSeries Based Linux Download Zip File
Linux Itanium Download Zip File
Linux x86 (32-bit) Download Zip File
Linux x86 (64-bit) Download Zip File
Microsoft Windows (32-bit) Download Zip File
Microsoft Windows (64-bit) Download Zip File
Oracle Solaris SPARC Download Zip File
Oracle Solaris x86 Download Zip File
For detailed information on RDA installation, review MOS document 314422.1 - section "Installation Instructions".
- How do I download Standalone (generic) RDA?
Remote Diagnostic Agent (RDA) Standalone - Download Zip File
- 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.
Remote Diagnostic Agent (RDA) - Overview - 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.
- 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 default 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:
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 - Production
With the Partitioning, OLAP and Data Mining optionsMemory (Free) total used free shared buffers cached
Mem: 1538936 1495756 43180 0 98844 726916
-/+ buffers/cache: 669996 868940Disks: 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.20
141 processes: 127 sleeping, 1 running, 13 zombie, 0 stoppedRDA 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 LISTENER
Processing 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 http://www.info-zip.org/Zip.html 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:
$ ./rda.pl -E RDA-14 RDA-00014: %d issue(s) found in the RDA installation *Cause: issues encountered when checking the RDA installation *Action: A fresh install of RDA is probably the easiest way to fix file alteration problems. However, permission problems can result from other factors: - If RDA has been installed by another user, the default settings could be too restrictive. Please review the local context with that user and your appropriate local authorities. - Execution permissions can be missing on startup scripts for other platforms and when perl is not available from the command line.
- What does the RDA-00010 error mean?
This error generally occurs when running a RDA binary (i.e. rda_win.exe, rda_sunos, etc). This error generally is followed by lines containing "PERL2EXE_STORAGE" and or a Perl *.pm module name.
Cause: The following OS environment variable PERL5LIB is set or your OS environment points to Perl installation. This causes a conflict for the RDA binary to located needed Perl modules binded within the executable.
Action: Unset PERL5LIB environment variable.
- What does the RDA-00006 error mean?
This error generally occurs when RDA cannot find a suitable archiving program like zip or tar in your OS path. You can do two(2) things to resolve this issue: (1) Make you your OS PATH variable contains the location to a "command line" zip or tar program. (2) You can manually compress the RDA directory and sent that to Oracle Support. >
See: $ ./rda.pl -E RDA-00006 or c:\>rda.cmd -E RDA-00006
Cause: No packaging tool paths have been found.
Action: The path to zip or tar commands has not been collected. This typically occurs when the end report has not yet been produced or if these commands have not been found in the current execution path (cf. PATH). - What does the OCM-09004 error mean?
This error generally mean that certain pre-requisites for OCM installation failed. The details of the failed prerequisites can be retrieved in the 'Report Setting' section of RDA output and that more info can be obtained with -E option
See: $ ./rda.pl -E OCM-09004 or c:\>rda.cmd -E OCM-09004
OCM-09004: Java Development Kit not found
*Cause: Java neither found under the $ORACLE_HOME/jdk directory nor JAVA_HOME is set.
*Action: Set JAVA_HOME to a JDK that is 1.2.2 or greater and re-run the OCM module setup. - How to change the default parameters like SQL_TIMEOUT?
There a few ways to set the default parameters in RDA, which useful for certain situations. Changing it temporarily from the command line using "-e" switch (SEE RDA MAN PAGE ) or using built in help system (rda.pl -h):
/rda.pl -vCRP -e DFT/N_SQL_TIMEOUT=120,DFT/N_ATTEMPTS=25
This command collects, generates the new reports and provides up to 120 seconds for executing each SQL statement and retries to execute the same sql statement 25 times temporarily for this time only.
Modifying the output.cfg file using a text editor like "vi" or "wordpad". You will find section with output.cfg file that relates to timeout (#N.SQL timeout (in seconds)).
Changing it more permanently from the command like using setup level "-p" switch (SEE RDA MAN PAGE ) or using built in help system (rda.pl -h):]./rda.sh -S -p advanced DB or
rda.cmd -S -p advanced DB or
rda.pl -S -p advanced DBTurns on advanced setup prompts, more settings can be specified interactively by using the advanced level.
- Can RDA be setup without asking any questions?
Yes. RDA was designed to determine values to setup question from the customer OS environment. You can also, pass all default parameters and values in a single command like this:
$ ./rda.pl -Sy -e DB.DB.B_SYSDBA=1,DB.DB.T_USER=/ OS INST DB
- How can I reduce the size or amount of RDA output files?
RDA has 2 mechanisms to reduce the size and quantity of trace and log files it collects and packages in the output file. The first is built into the advance setup profiles of the various collection modules, specifically for the (INI, DB, WEBC, IAS, GTW, RAC) modules and can be called using the following command(s):
$ rda.sh -S -p expert INI DB or
rda.cmd -S -p expert INI DB or
rda.pl -S -p expert INI DBThe second is using the using "-e" switch when calling RDA (rda.sh, rda.cmd, or rda.pl):
See modules: DB:[DB_TRACE_AGE, ALERT_TAIL], INI:[RDA_TAIL], GTW:[GATEWAY_TAIL], IAS:[DCM_TAIL], WEBC:[WEBCACHE_TAIL], RAC:[CLUSTER_TAIL]
./rda.sh -e DB_TRACE_AGE=5, ALERT_TAIL=1000 or
./rda.cmd -e DB_TRACE_AGE=5, ALERT_TAIL=1000 - Can RDA be scheduled to run automatically via CRON or AT?
Yes. You need to check with your OS documentation regarding running scheduling applications like CRON and AT. Please note you may need purge RDA log files in the directory and encode passwords in your output.cfg when required.
- How do I stop RDA from collecting everything?
RDA has been designed to reduce the number of setup questions and also can be called to only collect certain modules. RDA will call any dependent modules first; for instance OS module will always call the INI module. The list of available diagnostic modules is located here Module Man Pages or can be listed by executing (rda.pl -L):
$./rda.sh -vCRP OS PERF DBA LOG BR RAC or
C:\>rda.cmd -vCRP OS PERF DBA LOG BR RAC or
$./rda.pl -S -p advanced OS or
$ ./rda.pl -S -p advanced INI DB RAC - How do I verify the RDA package that I installed is not corrupted?
RDA has an internal file verification system to handle most types of file corruptions, as long as ./rda.pl, rda.sh, or rda.cmd can be called or not corrupt themselves: It can be run using the following command.
$ ./rda.sh -vc or
C:\>rda.cmd -vc or
$ ./rda.pl -vc - Why is RDA taking a long time to run the setup process?
Command execution can be slow to start when there are difficulties to detect the TCP/IP domain of the server that RDA is running on. The setup process can takes several minutes in some circumstances. The RDA_DOMAIN environment variable can avoid that.
On UNIX:
$RDA_DOMAIN=oracle.com
$RDA_DOMAIN=oracle.com
./rda.sh -S or
$export RDA_DOMAIN
$./rda.sh -S
On Windows:C:\set\RDA_DOMAIN=oracle.com
C:\rda.cmd -S - Why is RDA repeating the same title message several times during setup?
Sometimes a situation will occur where a user will notice a message like " S000INI: Initializes the Data Collection" being repeated over and over and without additional new messages.
If you see such strange behavior during setup process, than your current Perl installation contains Perl modules (.pm) that have been corrupted, please either install a newer Perl installation or use the RDA binary version.
- When I run RDA it creates a "core dump" or segmentation violation, what now?
There could be several things that could cause an OS "core dump"(you local Perl installation is core dumping, the OS libraries/modules is not correctly configured, or JAVA is crashing.
Note: rda.pl can be substituted by rda.sh on UNIX and rda.cmd on Windows.
- When I run RDA there is not .zip file in my [RDA_OUTPUT] directory, what now?
The final output directory may not contain an archive file (.zip, .tar, tar.gz, or tar.Z ) due to problems finding a compression program in your OS environment PATH. If the archive is missing, please archive all the files in the manually using a compression program like zip or Tar and send that to Oracle Support. You can use a packaging/archive utility program likehttp://www.info-zip.org/Zip.html to perform this task.>
- How do I upgrade my RDA installation from the prior release? For RDA 4.x to RDA 4.x upgrades:
The most simplest and reliable way to upgrade your RDA installation is delete or move your old installation to a new location. Then install the new release into the location you had the prior release installed. If you want to reuse you old setup.cfg file, you can place the older version into the new directory and it will try to upgrade your setup.cfg to the new features.
A second approach is to install the latest RDA into another directory, then if needed copy the old setup.cfg file to the new RDA directory. When the new RDA is run for the first time, it will try to upgrade your setup.cfg to the new features.
For RDA 4.x to RDA 8.x upgrades:Upgrade your RDA installation by deleting the current RDA location or creating a new location for RDA 8.x. There is no migration patch for RDA 4.x setup to RDA 8.x setup. RDA 8 does not create or use the old 4.x setup.cfg file.
For RDA 8.x to RDA 8.x upgrades:
The most simplest and reliable way to upgrade your RDA installation is delete or move your old RDA 8.x installation to a new location. Then install the new release into the location you had the prior release installed. If you want to reuse you old output.cfg file, you can place the older version into the new directory and it will try to upgrade your output.cfg to the new features.
A second approach is to install the latest RDA into another directory, then if needed copy the old output.cfg file to the new RDA directory. When the new RDA is run for the first time, it will try to upgrade your output.cfg to the new features.
- When I run the binary version of RDA it asks for newer libraries, what now?
The binary or compiled build of RDA were designed to have fewest library dependencies as possible. However, certain required libraries like libpthread maybe required. Additional binary versions of RDA has been build using older OS library versions for customer who have problems with our Primary binary version of RDA. Use the following secondary builds of RDA ONLY IF you have problems with primary RDA binary builds.
Knowledge Article 335791.1 - Secondary Binary RDA version
- Why is RDA reporting incorrect timestamp's of directory and file listing?
If you noticed that notice the times listed under the Listing of Files from Oracle
Log/Trace Directories are off by 5 or 7 hours, it is because RDA reports all times in GMT instead of local time zone. Also you will notice there are 2 dates in the directory listing, it because they represent:ctime inode change time in seconds since the epoch
mtime last modify time in seconds since the epoch - Can I connect to a remote database using RDA?
RDA is no longer dependent on 'sqlplus' for its database collection.
At setup time select "N" to the question "Is a local connection required (Y/N)?"
Follow prompts.
orYou can use command line -A" option to connect with JDBC to a remote database.
Example: JDBC connect information - @jdbc@
Usage: Review the "-A" command line option for password a use and password to the RDA rule definition setup file.
Simple case on Unix calling a database collection.
> rda/rda.sh -Snvp DB_Assessment
> rda/rda.sh -A @jdbc@
When prompt give password for user.
> rda/rda.sh -vIf you need to use sqlplus:
user AS SYSDBA
user@db
user@db AS SYSDBA
/
/ AS SYSDBA
/@db
/@db AS SYSDBANo password will be required for all '/' combinations.
If @db format is specified and the db must be identical to ORACLE_SID environment variable, RDA will assume that the TNS entry needs to be used instead of ORACLE_SID (and ORACLE_SID is removed from the environment).
- I am having difficulty running RDA 4. What do I do?
Note: If you have issues with the Remote Diagnostic Agent (RDA) , please file a Service Request via My Oracle Support by selecting OSS Support Tools from the product list of values on the Create a SR screen (OSS is above Oracle in the product list). Then select the "*Remote Diagnostic Agent (RDA) Issue*" as the problem type and complete the SR.
Please 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/she 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 issues resolved so that it can be used to help speed up resolution for future technical issues.
- How do I provide RDA output to Oracle Support?
RDA Output can be provided to Oracle Support when creating a Service Request or Updating a Service Request.During Service Request creation, the second step allows you to upload files that may be needed by Oracle Support. 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.). During a Service Request Update, click on the link "upload to support".You can attach your RDA Output in the new window that opens.Remember to upload your RDA output as a separate file.
When a RDA output file is uploaded to a Service Request in My Oracle Support the collection package attached to the SR is identified and the diagnostic information is loaded into a repository. The file is no longer externally accessible as an attachment of the SR. A auto generated message updates the SR that the file was uploaded.
@ ORACLE EMPLOYEES:
- There are connection issues when attempting to connect to OID database SID.
OID SID DB information is required in the "host:port::ServiceName" format, for the prompt "Enter the OID database:". If you do not want RDA to collect information from the database, then enter a dash ('-').
- Why does RDA not collect database information when getting ORA-28002 or ORA-28011?
RDA considers all ORA and SP2 errors at connection time are connection problems and stop collecting database information
- How to disable the parallel collection in RDA 4.18 and later?
Set the default for NO_PARALLEL to 1 in modules/S000INI.cfg, and specify NO_PARALLEL=1 in all setup files already present.
- How much space does Explorer require before running?
Explorer demands that 60Mb is free before starting the collection. RDA requires that by default 100 MiB free space to start (default value of RDA_FREE setting) and since Explorer requires RDA for some of it collections you can say that Explorer needs 100 MiB of free space before starting a collection.
- What does the warning RDA-00031 mean and how to solve it?
Executing rda.sh -E RDA-00031 or rda.cmd -E RDA-00031 and review the warning message and how to increase the sql timeout.
- Why does the RDA install download zip look almost empty?
At the parent level of the RDA install zip you could see just a README and a directory called ".". If you drill down on the "." directory you will see all of the required RDA files to be installed. Instructions for the download and install of RDA can be found in the RDA "Getting Started" MOS note 314422.1
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: Warranties and Disclaimers.
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
http://www.oracle.com/accessibility/
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 http://www.fcc.gov/cgb/consumerfacts/trs.html , and a list of phone numbers is available athttp://www.fcc.gov/cgb/dro/trsphonebk.html.
REFERENCES
NOTE:369111.5 - Oracle Configuration Manager FAQ
NOTE:1073385.1 - RDA - Setup Questions
NOTE:330344.1 - Remote Diagnostic Agent (RDA) - Training
NOTE:314422.1 - Remote Diagnostic Agent (RDA) - Getting Started
NOTE:330760.1 - Remote Diagnostic Agent (RDA) - Content Modules Man Page
NOTE:330362.1 - Remote Diagnostic Agent (RDA) - Troubleshooting Guide
NOTE:330364.1 - Remote Diagnostic Agent (RDA) - Main Man Page
NOTE:330363.1 - Remote Diagnostic Agent (RDA) - FAQ
NOTE:365734.1 - How To Change the CSI, Country code, Metalink_id or proxy details used by OCM.
NOTE:414966.1 - Remote Diagnostic Agent (RDA) - RDA Documentation Index
NOTE:335791.1 - Remote Diagnostic Agent (RDA) - Older RDA 56 or 58 Binary
快速部署RDA Remote Diagnostic Agent
RDA Remote Diagnostic Agent远程诊断代理是Oracle Support售后服务使用的标准工具之一，当用户在Metalink上提交SR(TAR)时可能Oracle GCS(Global Customer Service)支持会需要让用户从MOS上下载RDA工具，通过RDA收集丰富的数据库环境信息(如包含OS、DB、CRS等)，以便原厂售后直接从RDA report中抓取诊断信息，避免了因诊断信息不足 而反复信息交互所浪费的时间 ； 此外Oracle的一些ACS高级客户服务的现场服务过程中也会利用到RDA，例如当用户要求ACS到现场进行月度或季度巡检是RDA就是标准的检查工具。
说了这么多， 你可能还是不太了解RDA。 这不要紧，你可以把RDA看成一套由oracle定义了很多模块的脚本工具盒， 用它可以收集到诊断过程复杂的Oracle产品问题的各种信息。 可以从My Oracle Support(metalink)的《Remote Diagnostic Agent (RDA) 4 – Getting Started [ID 314422.1]》专栏中下载到各个平台的最新版RDA。
虽然RDA是Oracle Support使用的工具 ， 但是并不是说非原厂售后就看不懂RDA也不能利用到这款工具。 RDA从脚本、模块到最后生成的报告都是自然可读的。 譬如Maclean.Liu 我 在诊断较复杂的问题过程中也会用到RDA， 我甚至推荐在数据库巡检、健康检查过程中也使用RDA， 当然是配合其他工具一起使用。
在使用RDA之前我们需要完成配置工作，所谓配置就是选择我们要使用的RDA module和一些临时设置，先来认识一下有哪些module:
将下载到的rda zip包解压
[oracle@vrh8 ~]$ unzip /tmp/p9079828_418_LINUX.zip
[oracle@vrh8 ~]$ cd rda
[oracle@vrh8 rda]$ ./rda.sh -h
Usage: rda.pl [-bcdflntvwxy] [-ABCDEHIKLMPQRSTV] [-e list] [-m dir]
[-s name] [-o out] [-p prof] arg ...
-A Authentify user through the setup file
-B Start background collection
-C Collect diagnostic information
-D Delete specified modules from the setup
-E Explain specified error numbers
-H Halt background collection
-I Regenerate the index
-K Kill background collection
-L List the modules available
-M Display the related manual pages
-O Render output specifications from STDIN
-P Package the reports (tar or zip)
-Q Display the related setup questions
-R Generate specified reports
-S Setup specified modules
-T Execute test modules
-V Display component version numbers
-b Don't backup setup file before saving
-c Check the RDA installation and exit
-d Set debug mode
-e list Specify a list of alternate setting definitions (var=val,...)
-f Set force mode
-h Display the command usage and exit
-l Use a lock file to prevent concurrent usage of a setup file
-m dir Specify the module directory ('modules' by default)
-n Start a new data collection
-o out Specify the file for background collection output redirection
-p prof Specify the setup profile ('Default' by default)
-q Set quiet mode
-s name Specify the setup name ('setup' by default)
-t Set trace mode
-v Set verbose mode
-w Wait as long as the background collection daemon is active
-x Produce module cross reference
-y Accept all defaults and skip all pauses
列出所有可用module
[oracle@vrh8 rda]$ ./rda.sh -L Module
Available data collection modules are:
ACFS Collects ASM Cluster File System Information
ACT Collects Oracle E-Business Suite Application Information
ADBA Collects ACS Oracle Database Assessment
ADX Collects AutoConfig and Rapid Clone Information
AGT Collects Enterprise Manager Agent Information
APEX Collects APEX Information
ASAP Collects Oracle Communications ASAP Information
ASBR Collects Application Server Backup and Recovery Information
ASG Collects Application Server Guard Information
ASIT Collects Oracle Application Server Installation Information
ASM Collects Automatic Storage Management Information
B2B Collects Oracle Business to Business Information
BAM Collects Business Activity Monitoring Information
BEE Collects Beehive Information
BI Collects Oracle Business Intelligence Enterprise Edition Info.
BPEL Collects Oracle BPEL Process Manager Information
BR Collects Database Backup and Recovery Information
BRM Collects Oracle Communications BRM Information
CCR Collects OCM Diagnostic Information
CFG Collects Key Configuration Information
COHR Collects Oracle Coherence Information
CONT Collects Oracle Content Services Information
CRID Collects Oracle Access Manager (COREid) Information
D2PC Collects Distributed Transaction Information
DB Controls RDBMS Data Collection
DBA Collects RDBMS Information
DBC Collects Database Control Information
DBM Collects RDBMS Memory Information
DEV Collects Oracle Developer Information
DG Collects Data Guard Information
DNFS Collects Direct NFS Information
DSCS Collects Discussions Information
DSCV Collects Oracle Discoverer Information
ECM Controls Oracle Enterprise Content Management 11g Data Collection
EM Collects Enterprise Manager OMS and Repository Info (Obsolete)
END Finalizes the Data Collection
EPMA Collects Enterprise Performance Management Architect Information
ESB Collects Enterprise Service Bus Information
ESS Collects Oracle Essbase Information
ESSO Collects Oracle Enterprise Single Sign-On Information
EXA Collects Exadata Information
FLTR Controls Report Content Filtering
GRDN Collects Oracle Guardian Information
GRID Controls Grid Control Data Collection
GTW Collects Transparent/Procedural Gateway Information
HFM Collects Oracle Hyperion Financial Management information
HPL Collects Oracle Hyperion Planning Information
IA Collects Intelligent Agent Information
IAS Collects Web Server Information
IFS Collects iFS (iFS, CMSDK, Files) Information
INI Initializes the Data Collection
INST Collects the Oracle Installation Information
IPSA Collects Oracle Communications IP Service Activator Information
J2EE Collects J2EE/OC4J Information
JDBC Collects Oracle Java DB Connectivity (JDBC) Information
JDEV Collects Oracle JDeveloper Information
JIVE Collects Jive Information
LANG Collects Oracle Language Information
LOAD Produces the External Collection Reports
LOG Collects Database Trace and Log Files
MAIL Collects Oracle Collaboration Suite Mail Information
MSLG Collects Microsoft Languages Information
ND Collects Oracle Communications Network Discovery Information
NET Collects Network Information
NM Collects Oracle Communications Network Mediation Information
NPRF Samples Performance Information (root not required)
OCAL Collects Oracle Calendar Information
OCFS Collects Oracle Cluster File System Information
OCM Setting up Configuration Manager Interface
OCS Controls Oracle Collaboration Suite Data Collection
ODI Collects Oracle Data Integrator Information
ODM Collects Oracle Data Mining Information
OES Collects Oracle Express Server Information
OID Collects Oracle Internet Directory Information
OIM Collects Oracle Identity Manager Information
OLAP Collects OLAP Information
OMM Collects Oracle Multimedia or Oracle interMedia Information
OMS Collects Oracle Management Server Information (obsolete)
ONET Collects Oracle Net Information
OS Collects the Operating System Information
OVD Collects Oracle Virtual Directory Information
OVMM Collects Oracle VM Manager Information
OVMS Collects Oracle VM Server Information
OWB Collects Oracle Warehouse Builder Information
OWSM Collects Oracle Web Services Manager Information
PDA Collects Oracle Portal Information
PDBA Collects PeopleSoft Information from an Oracle Database
PERF Collects Performance Information
PLNC Collects Oracle PL/SQL Native Compilation Information
PROF Collects the User Profile
PS Collects Oracle Communications Policy Services Information
PWEB Collects PeopleSoft Information from Web Application Server
RAC Collects Cluster Information
RACD Performs a Database Hang Analysis
RDSP Produces the Remote Data Collection Reports
RET Collects Oracle Retail Information
REXE Performs the Remote Data Collections
RPRF Samples Performance Information (root privileges required)
RSRC Collects Database Resource Manager Information
RTC Collects Real Time Communication Information
SEBL Collects Siebel Information
SES Collects Oracle Secure Enterprise Search Information
SMPL Controls Sampling
SOA Collects Oracle SOA Suite Information
SP Collects SQL*Plus/iSQL*Plus Information
SSO Collects Single Sign-On Information
STC Collects Streams Configuration Information
STM Collects Streams Monitoring Information
TOPL Collects Oracle TopLink Information
TTEN Collects Oracle TimesTen In-Memory Database Information
UCM Collects Oracle Universal Content Management Information
UOA Collects Oracle Universal Online Archive 11g Information
WAC Collects Web Access Client Information
WCI Collects Oracle WebCenter Information
WEBC Collects Oracle Web Cache Information
WKSP Collects Workspaces Information
WLS Collects Oracle WebLogic Server Information
WMC Collects Webmail Client Information
WRLS Collects Wireless Information
XDB Collects XDB Information
XSMP Samples User Defined Data
XTRA Collects User Defined Data
如以上列表中RAC模块用来Collects Cluster Information收集集群信息， 而RACD模块则负责收集RAC数据库挂起的相关信息Performs a Database Hang Analysis。
我们在配置RDA的时可以直接执行./rda.sh， 脚本会提示我们需要选择启用哪些Module，但是因为Module过多，整个配置过程就会浪费很多时间。
为了避免每配置一套新环境都要大费周章确认那么多模块， 所以在RDA中定义了很多典型场景使用的profile， 这些profile已经配好了固定的一些Module ， 下面我们来看一下RDA profile:
列出所有目前可用的profile [oracle@vrh8 rda]$ ./rda.sh -L profiles Available profiles are: 9iAS Oracle Application Server 9i problems AS10g Oracle Application Server 10g problems AS10g_Identity Oracle Identity Management 10g problems AS10g_MidTier Oracle Application Server 10g Middle Tier problems AS10g_Repository Oracle Application Server 10g metadata repository problems AS10g_WebTier Oracle Application Server 10g WebTier problems AS_BackupRecovery Oracle Application Server backup/recovery problems Act Oracle Application Overview AppsCheck Equivalent to AppsCheck AsmFileSystem Oracle ASM Cluster File System problems Bam Business Activity Monitoring problems Beehive Oracle Beehive problems DB10g Oracle Database 10g problems DB11g Oracle Database 11g problems DB8i Oracle Database 8i problems DB9i Oracle Database 9i problems DB_Assessment Oracle Database assessment collections DB_BackupRecovery Oracle Database backup and recovery problems DB_Perf Oracle Database performance problems DataGuard Data Guard problems DirectNFS Direct NFS problems Discoverer10g Oracle Discoverer 10g problems Discoverer11g Oracle Discoverer 11g problems EnterpriseSearch Oracle Secure Enterprise Search problems Essbase Oracle Essbase problems FM11g_Bi Business Intelligence Enterprise Edition 11g problems FM11g_Ecm Oracle Enterprise Content Management 11g problems FM11g_Forms Oracle Forms 11g problems FM11g_Identity Oracle Identity Management 11g problems FM11g_Odi Oracle Data Integrator Standalone 11g problems FM11g_Portal Oracle Portal 11g problems FM11g_Reports Oracle Reports 11g problems FM11g_Soa Oracle SOA Suite 11g problems FM11g_WebTier Oracle Fusion Middleware 11g Web Tier problems FM11g_WlsBi Business Intelligence Enterprise Edition 11g with WLS FM11g_WlsForms Oracle Forms 11g with WLS problems FM11g_WlsIdentity Oracle Identity Management 11g with WLS problems FM11g_WlsOdi Oracle Data Integrator Suite 11g with WLS problems FM11g_WlsPortal Oracle Portal 11g with WLS problems FM11g_WlsReports Oracle Reports 11g with WLS problems FM11g_WlsWebTier Oracle Fusion Middleware 11g Web Tier with WLS problems FinManagement Oracle Hyperion Financial Management problems GridControl Grid Control problems InterMedia Oracle interMedia problems Linux Linux problems LinuxPerf Linux performance problems Maa_Assessment Maximum Availability Architecture assessment collections Multimedia Oracle Multimedia problems OSMonitor Operating System performance sampling OVMManager Oracle VM Manager problems Pda10g Portal 10g problems Pda11g Portal 11g problems Pda9i Portal 9i problems PeopleSoft_DB PeopleSoft Oracle Database tier assessment collections PeopleSoft_Web PeopleSoft Web application server assessment collections Rac Real Application Cluster problems Rac_AdvancedAsm Cluster with ASM problems (ASM advanced mode) Rac_Asm Cluster with ASM problems Rac_Assessment Real Application Cluster assessment collections Rac_Perf Cluster performance problems Retail Oracle Retail problems Security Filter sensitive information from the reports SupportInformer70 Oracle Communication BRM 7.0 problems SupportInformer72 Oracle Communication BRM 7.2 problems SupportInformer73 Oracle Communication BRM 7.3 problems SupportInformer74 Oracle Communication BRM 7.4 problems TimesTen Oracle TimesTen problems TopLink10g Oracle TopLink 10g problems WebCenter10g Oracle WebCenter 10g problems WebCenter11g Oracle WebCenter 11g problems WebCenterCont10g Oracle WebCenter 10g with Oracle Content Services problems WebLogicServer Oracle WebLogic Server problems
上例列出了该版本RDA默认就有的Profile ， 如DB11g这个profile是用来收集11g Database数据库的诊断信息的， 而DB10g 是收集10g Database诊断信息的， DB_Perf是收集数据库性能诊断信息的。
可以具体了解 这些profile 预设了哪些Module:
[oracle@vrh8 rda]$ ./rda.sh -M -p DB11g NAME Profile DB11g - Oracle Database 11g problems MODULES The DB11g profile uses the following modules: OS Collects the Operating System Information PROF Collects the User Profile PERF Collects Performance Information NET Collects Network Information ONET Collects Oracle Net Information INST Collects the Oracle Installation Information DB Controls RDBMS Data Collection DBA Collects RDBMS Information DBM Collects RDBMS Memory Information LOG Collects Database Trace and Log Files DNFS Collects Direct NFS Information SP Collects SQL*Plus/iSQL*Plus Information GRID Controls Grid Control Data Collection AGT Collects Enterprise Manager Agent Information DBC Collects Database Control Information [oracle@vrh8 rda]$ ./rda.sh -M -p DB10g NAME Profile DB10g - Oracle Database 10g problems MODULES The DB10g profile uses the following modules: OS Collects the Operating System Information PROF Collects the User Profile PERF Collects Performance Information NET Collects Network Information ONET Collects Oracle Net Information INST Collects the Oracle Installation Information DB Controls RDBMS Data Collection DBA Collects RDBMS Information DBM Collects RDBMS Memory Information LOG Collects Database Trace and Log Files SP Collects SQL*Plus/iSQL*Plus Information GRID Controls Grid Control Data Collection AGT Collects Enterprise Manager Agent Information DBC Collects Database Control Information
除了module之外profile可能还定义了一些临时变量如force_onet_tests 是否强制做oracle net网络测试等， 可以用-f( Set force mode)选项来列出这些temporary settings：
[oracle@vrh8 rda]$ ./rda.sh -fM -p DB10g NAME Profile DB10g - Oracle Database 10g problems MODULES The DB10g profile uses the following modules: OS Collects the Operating System Information PROF Collects the User Profile PERF Collects Performance Information NET Collects Network Information ONET Collects Oracle Net Information INST Collects the Oracle Installation Information DB Controls RDBMS Data Collection DBA Collects RDBMS Information DBM Collects RDBMS Memory Information LOG Collects Database Trace and Log Files SP Collects SQL*Plus/iSQL*Plus Information GRID Controls Grid Control Data Collection AGT Collects Enterprise Manager Agent Information DBC Collects Database Control Information SETTINGS The DB10g profile sets the following temporary settings: force_db_tests=1 force_dba_tests=1 force_dbm_tests=1 force_log_tests=1 force_onet_tests=1
也可以列出全部预定义的profile的Module信息:
[oracle@vrh8 rda]$ ./rda.sh -xv profiles Treating profiles ... Profile Cross Reference Defined Profiles: 9iAS S100OS, S105PROF, S110PERF, S120NET, S130INST, S300IAS, S305ASBR, S306ASG, S310J2EE, S330SSO, S340OID, S350WEBC AS10g S100OS, S105PROF, S110PERF, S120NET, S130INST, S300IAS, S305ASBR, S306ASG, S310J2EE, S330SSO, S340OID, S350WEBC AS10g_Identity S100OS, S105PROF, S110PERF, S120NET, S130INST, S300IAS, S305ASBR, S306ASG, S310J2EE, S330SSO, S340OID, S342OVD AS10g_MidTier S100OS, S105PROF, S110PERF, S120NET, S130INST, S249WRLS, S290DEV, S300IAS, S310J2EE, S325PDA, S350WEBC, S390DSCV AS10g_Repository S100OS, S105PROF, S110PERF, S120NET, S130INST, S300IAS, S305ASBR, S306ASG, S310J2EE AS10g_WebTier S100OS, S105PROF, S110PERF, S120NET, S130INST, S300IAS, S310J2EE, S350WEBC, S410GRID AS_BackupRecovery S100OS, S300IAS, S305ASBR Act S100OS, S105PROF, S110PERF, S130INST, S500ACT AppsCheck S100OS, S105PROF, S110PERF, S130INST, S500ACT AsmFileSystem S100OS, S105PROF, S120NET, S122ONET, S130INST, S402ASM, S403ACFS Bam S100OS, S105PROF, S110PERF, S120NET, S374BAM ..........
使用-Q 选项可以更详细地列出profile相关的问题：
[oracle@vrh8 rda]$ ./rda.sh -Q -p DB11g NAME S120NET - Collects Network Information SETTING DESCRIPTION NETWORK_PING_TESTS "Do you want RDA to perform the network ping tests (Y/N)?" LOCAL_NODE "Enter the name of the node the script is running on (used for ping tests)" WAN_NODE "Enter a remote node connecting to this server (used for ping tests)" RDBMS_NODE "Enter the node hosting the database instance (used for ping tests)" WEB_NODE "Enter the node where the Web Server/Forms server is on (used for ping tests)" ...............
通过继承profile的定义可以快速配置RDA，例如我们尝试使用DB11g这个profile:
[oracle@vrh8 rda]$ ./rda.sh -S -p DB11g 使用profile后RDA问你的问题明显减少了哦 之后在运行rda.sh就会收集信息了 [oracle@vrh8 rda]$ ./rda.sh ------------------------------------------------------------------------------- RDA Data Collection Started 06-Feb-2012 01:23:22 ------------------------------------------------------------------------------- Processing Initialization module ... Enter the password for 'SYSTEM': Please re-enter it to confirm: Processing OCM module ... Processing PERF module ... Processing CFG module ... Processing OS module ..
可能你还是觉得麻烦：”我使用oracle操作系统用户登录的，为啥每次还要输密码呢？直接sysdba不行吗？” 对于有些内部视图X$ View的查询也确实需要sysdba权限， 我们可以如下设置来使用sysdba身份：
[oracle@vrh8 rda]$ ./rda.sh -Sy -e SQL_SYSDBA=1,SQL_LOGIN=/ -p DB11g [oracle@vrh8 rda]$ ./rda.sh ------------------------------------------------------------------------------- RDA Data Collection Started 06-Feb-2012 01:27:37 ------------------------------------------------------------------------------- Processing Initialization module ... Processing OCM module ... Processing PERF module ... Processing CFG module ... Processing OS module ...
除了单独使用某个profile外，我们还可以组合使用多个profile，使用-p profile1-profile2这样的语法即可，如:
[oracle@vrh8 rda]$ ./rda.sh -Sy -e SQL_SYSDBA=1,SQL_LOGIN=/ -p DB11g-DataGuard 使用-p profile1-profile2这样的模式即可
RDA经过配置后会默认将配置信息写到其目录下的setup.cfg文件中，之后再使用rda.sh收集信息即会沿用该cfg文件：
cat setup.cfg # Oracle Remote Diagnostic Agent - Setup Information ############################################################################### #------------------------------------------------------------------------------ # Data Collection Overview #------------------------------------------------------------------------------ # S000INI=pending # S010CFG=pending # S020SMPL=pending # S090OCM=pending # S100OS=pending # S105PROF=pending # S110PERF=pending # S120NET=pending # S122ONET=pending # S130INST=pending # S200DB=skip # S201DBA=pending # S203DBM=pending # S204LOG=pending # S205BR=pending # S212DNFS=skip # S213SP=skip # S400RAC=pending # S400RACD=skip # S401OCFS=skip # S405DG=pending # S410GRID=skip # S420AGT=skip # S430DBC=skip # S909RDSP=skip # S919LOAD=pending # S990FLTR=skip www.askmaclean.com www.askmaclean.com # S999END=pending .................
除了最常见的DB11g 、 DB10g外还有一些很有用的profile可以加速我们对问题的诊断， 在这里分享一下：
For 11g ./rda.sh -Sy -e SQL_SYSDBA=1,SQL_LOGIN=/ -p DB11g ./rda.sh -Sy -e SQL_SYSDBA=1,SQL_LOGIN=/,ALERT_TEXT=1 -p DB11g --收集alert文本 ./rda.sh -Sy -e SQL_SYSDBA=1,SQL_LOGIN=/,ALERT_TEXT=1,DBCONTROL_SERVER_IN_USE=1 -p DB11g --收集DBcontrol信息 ./rda.sh -vSCRPfy -e SQL_SYSDBA=1,SQL_LOGIN=/,ALERT_TEXT=1 -p DB11g --收集诊断信息并打包 DB10g ./rda.sh -S -p DB10g ./rda.sh -Sy -e SQL_SYSDBA=1,SQL_LOGIN=/ -p DB10g ./rda.sh -Sy -e SQL_SYSDBA=1,SQL_LOGIN=/,DBCONTROL_SERVER_IN_USE=1 -p DB10g DB9i ./rda.sh -S -p DB9i ./rda.sh -Sy -e SQL_SYSDBA=1,SQL_LOGIN=/ -p DB9i DB_BackupRecovery 收集备份恢复信息 ./rda.sh -S -p DB_BackupRecovery ./rda.sh -Sy -e SQL_SYSDBA=1,SQL_LOGIN=/,RMAN_IN_USE=0 -p DB_BackupRecovery --不使用RMAN备份 ./rda.sh -Sy -e SQL_SYSDBA=1,SQL_LOGIN=/,RMAN_IN_USE=1,RMAN_CATALOG=0 -p DB_BackupRecovery --使用RMAN但不使用CATALOG恢复目录 ./rda.sh -Sy -e SQL_SYSDBA=1,SQL_LOGIN=/,RMAN_IN_USE=1,RMAN_CATALOG=1,RMAN_SCHEMA=rman,RMAN_EXPORT_USER=rman@catlogdb -p DB_BackupRecovery DB_Perf 收集数据库性能信息 ./rda.sh -S -p DB_Perf ./rda.sh -Sy -e SQL_SYSDBA=1,SQL_LOGIN=/ -p DB_Perf ./rda.sh -Sy -e SQL_SYSDBA=1,SQL_LOGIN=/,PERF_START_TIME=11-Mar-2010_12:00,PERF_END_TIME=11-Mar-2010_13:00 -p DB_Perf --指定收集性能信息的时间段 DataGuard 收集dg 信息 ./rda.sh -S -p DataGuard ./rda.sh -Sy -e SQL_SYSDBA=1,SQL_LOGIN=/ -p DataGuard ./rda.sh -Sy -e SQL_SYSDBA=1,SQL_LOGIN=/,ONET_IN_USE=1,ALERT_TEXT=1 -p DataGuard --同时也收集Oracle Net Services信息 RAC 收集Real Application Cluster CRS信息 ./rda.sh -S -p Rac ./rda.sh -Sy -e SQL_SYSDBA=1,SQL_LOGIN=/ -p Rac RAC ASM 收集 Rac + Clusterware + Asm 信息 ./rda.sh -S -p Rac_Asm ./rda.sh -Sy -e SQL_SYSDBA=1,SQL_LOGIN=/,ASM_ORACLE_SID=+ASM1 -p Rac_Asm Rac_AdvancedAsm 收集更详细的Rac + Clusterware + Asm 信息 ./rda.sh -S -p Rac_AdvancedAsm ./rda.sh -Sy -e SQL_SYSDBA=1,SQL_LOGIN=/,ASM_ORACLE_SID=+ASM1 -p Rac_AdvancedAsm Rac_Perf 收集RAC数据库性能信息 ./rda.sh -S -p Rac_Perf ./rda.sh -Sy -e SQL_SYSDBA=1,SQL_LOGIN=/ -p Rac_Perf ./rda.sh -Sy -e SQL_SYSDBA=1,SQL_LOGIN=/,PERF_START_TIME=11-Mar-2010_12:00,PERF_END_TIME=11-Mar-2010_13:00 -p Rac_Perf DirectNFS ./rda.sh -S -p DirectNFS ./rda.sh -Sy -e SQL_SYSDBA=1,SQL_LOGIN=/ -p DirectNFS AsmFileSystem ./rda.sh -S -p AsmFileSystem ./rda.sh -Sy -e SQL_SYSDBA=1,SQL_LOGIN=/ -p AsmFileSystem DB_Assessment ./rda.sh -S -p Rac_Assessment ./rda.sh -Sy -e SQL_SYSDBA=1,SQL_LOGIN=/ -p Rac_Assessment Rac_Assessment ./rda.sh -S -p Rac_Assessment ./rda.sh -Sy -e SQL_SYSDBA=1,SQL_LOGIN=/ -p Rac_Assessment ./rda.sh -Sy -e SQL_SYSDBA=1,SQL_LOGIN=/,ASM_ORACLE_SID=+ASM1 -p Rac_Assessment Maa_Assessment ./rda.sh -S -p Maa_Assessment ./rda.sh -Sy -e SQL_SYSDBA=1,SQL_LOGIN=/ -p Maa_Assessment ./rda.sh -Sy -e SQL_SYSDBA=1,SQL_LOGIN=/,ASM_ORACLE_SID=+ASM1 -p Maa_Assessment Exadata_Assessment ./rda.sh -S -p Exadata_Assessment ./rda.sh -Sy -e SQL_SYSDBA=1,SQL_LOGIN=/,ALERT_TEXT=1 -p Exadata_Assessment ./rda.sh -vSCRPfy -e SQL_SYSDBA=1,SQL_LOGIN=/,ALERT_TEXT=1,EXA_COLLECT_CELL=0 -p Exadata_Assessment ./rda.sh -vSCRPfy -e SQL_SYSDBA=1,SQL_LOGIN=/,ALERT_TEXT=1 -p Exadata_Assessment Maa_Exa_Assessment ./rda.sh -S -p Maa_Exa_Assessment ./rda.sh -Sy -e SQL_SYSDBA=1,SQL_LOGIN=/,ALERT_TEXT=1 -p Maa_Exa_Assessment ./rda.sh -Sy -e SQL_SYSDBA=1,SQL_LOGIN=/,ALERT_TEXT=1,EXA_COLLECT_CELL=0 -p Maa_Exa_Assessment ./rda.sh -vSCRPfy -e SQL_SYSDBA=1,SQL_LOGIN=/,ALERT_TEXT=1 -p Maa_Exa_Assessment
还可以利用rda对OS做数据库软件安装前的预检查，如将需要安装11.2g,则执行 ./rda.sh -T hcve：
[oracle@vrh8 rda]$ ./rda.sh -T hcve Processing HCVE tests ... Available Pre-Installation Rule Sets: 1. Oracle Database 10g R1 (10.1.0) Preinstall (Linux-x86) 2. Oracle Database 10g R1 (10.1.0) Preinstall (Linux AMD64) 3. Oracle Database 10g R1 (10.1.0) Preinstall (IA-64 Linux) 4. Oracle Database 10g R2 (10.2.0) Preinstall (Linux AMD64) 5. Oracle Database 10g R2 (10.2.0) Preinstall (IA-64 Linux) 6. Oracle Database 10g R2 (10.2.0) Preinstall (Linux-x86) 7. Oracle Database 11g R1 (11.1.0) Preinstall (Linux AMD64) 8. Oracle Database 11g R1 (11.1.0) Preinstall (Linux-x86) 9. Oracle Database 11g R2 (11.2.0) Preinstall (Linux-x86) ID NAME RESULT VALUE ====== ==================== ======= ========================================== A00010 OS Certified? PASSED Adequate A00050 Enter ORACLE_HOME RECORD /s01/oracle/product/10.2.0/db_1 A00060 ORACLE_HOME Valid? PASSED OHexists A00070 O_H Permissions OK? PASSED CorrectPerms A00080 oraInventory Permiss PASSED oraInventoryOK A00090 Got ld,nm,ar,make? PASSED ld_nm_ar_make_found A00100 Umask Set to 022? PASSED UmaskOK A00120 Limit Processes PASSED Adequate A00130 Limit Descriptors PASSED Adequate A00140 LDLIBRARYPATH Unset? PASSED UnSet A00180 JAVA_HOME Unset? PASSED UnSet A00190 Enter JDK Home RECORD A00200 JDK Version FAILED JDK home is missing A00210 Other O_Hs in PATH? FAILED OratabEntryInPath A00220 Other OUI Up? PASSED NoOtherOUI A00230 /tmp Adequate? PASSED TempSpaceOK A00240 Disk Space OK? PASSED DiskSpaceOK A00250 Swap (in MB) RECORD 5951 A00260 RAM (in MB) PASSED 3955 A00270 Swap OK? PASSED SwapToRAMOK A00280 Network PASSED Connected A00290 IP Address RECORD 192.168.1.191 A00300 Domain Name RECORD oracle.com A00310 DNS Lookup FAILED nslookup host.domain A00320 /etc/hosts Format FAILED Missing host.domain A00330 Kernel Parameters OK PASSED KernelOK A00380 Tainted Kernel? PASSED NotVerifiable A00400 ip_local_port_range PASSED RangeOK A00480 EL4 RPMs OK? SKIPPED NotEL4 A00490 EL5 RPMs OK? FAILED [kernel-headers(i386)] not installed ..> A00530 RHEL4 RPMs OK? SKIPPED NotRedHat A00540 RHEL5 RPMs OK? SKIPPED NotRedHat A00570 SUSE SLES10 RPMs OK? SKIPPED NotSuSE A00580 SUSE SLES11 RPMs OK? SKIPPED NotSuSE Result file: /home/oracle/rda/output/RDA_HCVE_A200DB11R2_lnx_res.htm
上例对OS做了Oracle Database 11g R2 (11.2.0) Preinstall的预安装检查 ，并给出了检查结果。
还可以使用./rda.sh命令对现有的RDA软件做完整性检测，保证RDA没有被修改过:
[oracle@vrh8 rda]$ ./rda.sh -cv Loading the file list ... Checking the directory '.' ... Checking the directory 'RDA' ... Checking the directory 'RDA/Handle' ... Checking the directory 'RDA/Library' ... Checking the directory 'RDA/Library/Remote' ... Checking the directory 'RDA/Local' ... Checking the directory 'RDA/Object' ... Checking the directory 'RDA/Operator' ... Checking the directory 'RDA/Value' ... Checking the directory 'hcve' ... Checking the directory 'modules' ... No issues found
内容总结
以上是互联网集市为您收集整理的利用Oracle RDA（ Remote Diagnostic Agent）快速收集Oracle产品分析数据全部内容，希望文章能够帮你解决利用Oracle RDA（ Remote Diagnostic Agent）快速收集Oracle产品分析数据所遇到的程序开发问题。 如果觉得互联网集市技术教程内容还不错，欢迎将互联网集市网站推荐给程序员好友。
内容备注
版权声明：本文内容由互联网用户自发贡献，该文观点与技术仅代表作者本人。本站仅提供信息存储空间服务，不拥有所有权，不承担相关法律责任。如发现本站有涉嫌侵权/违法违规的内容， 请发送邮件至 gblab@vip.qq.com 举报，一经查实，本站将立刻删除。
内容手机端
扫描二维码推送至手机访问。