oracle的RDA诊断工具

Subject:	Remote Diagnostic Agent (RDA) 4 - Download
	Doc ID:	330472.1	Type:	DIAGNOSTIC TOOLS
	Modified Date:	09-DEC-2008	Status:	PUBLISHED

<!--20-SEP-2007 - hspatel.us - Added RDA 4.11 release content -->

RDA 4 Download

RDA Documentation Links

Getting Started	Download RDA You Are Here	FAQ	Man Pages	Troubleshooting Guide	Training	RDA Documentation Index

Download

Choose the RDA packaging format you wish to download and click on the related link. Each package contains all of the files you need, so only choose one package to download.

<!-- Generated rda_base.html by mk_webiv for notes :314422.1 --> Available RDA standalone packages for download Download Link Instructions Package Size

Tar format: rda.tar	Change the filename torda.tar when saving	size: 6,072,320 Bytes
UNIX Tar and gzipped format: rda.tar.gz	Change the filename torda.tar.gz when saving (IE5+ users please use "Right-Click"+ "Save target as ..." or "Save link as ..." option. Otherwise the file will automatically uncompressed by your browser.)	size: 1,121,583 Bytes
Zip format: rda.zip	Change the filename torda.zip when saving	size: 1,494,419 Bytes

<!-- End of Generation by mk_webiv -->

NOTE: RDA 4 is written in Perl and is a command line script. It uses only basic Perl libraries so the customer should never have to install anything additional, this includes Windows Platforms. RDA is designed to use the Perl libraries that are shipped with Oracle and/or shipped with most Unix platforms. If for some reason Perl 5.005 or above is not available or is inaccessible on the customer environment, then a binary version is available for download on major platforms.

For additional information please read the RDA FAQ - Knowledge Article 330362.1.

Subject:	Remote Diagnostic Agent (RDA) 4 - Getting Started
	Doc ID:	314422.1	Type:	DIAGNOSTIC TOOLS
	Modified Date:	11-FEB-2009	Status:	PUBLISHED

RDA 4 Getting Started

RDA Documentation Links

Getting Started You are here	FAQ	Man Pages	Troubleshooting Guide	Training	RDA Documentation Index

In This Document

Overview What new in this RDA Release Platforms Supported Products Supported Versions Supported Why Use RDA? Oracle Configuration Manager Download RDA Installation Instructions Running RDA - Unix

Running RDA - Windows Running RDA - RAC Cluster Running RDA - VMS Upgrading RDA Password Security View RDA Output Security Filters Report Feedback Terms of Use

RDA 4.x 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 (see Knowledge Article 330760.1). 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 New in this RDA Release

See the RDA 4 Release Notes for information about new features. The next release in RDA 4.x series is scheduled for release in Mid-March.

Platforms Supported

At this time, RDA has been successfully tested to run on the following Supported platforms:

• IBM AIX
• Intel Linux (Oracle Enterprise, RedHat, and SuSE)
• HP-UX (10.* and 11.*)
• HP Tru64 (OSF)
• Linux Itanium
• Linux PPC
• Mac OS X/Darwin
• Sequent Dynix/Ptx
• Sun Solaris (2.6 - 2.10)
• Windows XP Professional
• Windows 2000 Workstation and Server
• Windows 2003 Server
• HP OpenVMS Alpha 7.3-2 and above
• HP OpenVMS Itanium
• ZLinux

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

• Oracle RDBMS Server (Standard and Enterprise Editions)
• Oracle RAC Cluster (Single/Multiple Nodes, Automatic Storage Management, Oracle Cluster File System, Data Guard)
• Oracle Application Server (iAS 1.0.2.x/9.0.x/10.1.2.x/10.1.3.x,10.1.4.x, HTTP Server,WebCache,J2EE/OC4J)
• Oracle Oracle Data Integrator
• Oracle Management Server and Intelligent Agent (Grid Server, Agent Server, DB Control)
• OLAP Products (Express Server, Financial Analyzer, and Demand Planning Server)
• Oracle Developer (Forms and Reports)
• Oracle JDBC/PRO *C/ODBC and other development client related information
• Oracle Collaboration Suites (Email Server,Calendar,Discussions,Content Services,Workspaces,WebClient, and Wireless)
• Oracle Identity Management
• Oracle Networking products
• Oracle Ebusiness Suite 11i and 12
• Oracle Portal Software 7.0, 7.2, and 7.3
• Oracle Retail (Retek)

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!

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 tars:

· Performance issues

· Installation/configuration issues

· ORA-600, ORA-7445, and ORA-3113 errors

· Upgrade, migration, and linking issues

· Database and Development API issues

· Forms and reports issues

· Development / Discoverer Server issues

· Oracle Application Server / Fusion Middleware issues

· Other corrective issues

Oracle Configuration Manager

The Oracle Configuration Manager 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, OCM optimizes the customer benefits of OCM by automating the configuration collections. OCM simplifies your ability to automate your configuration and diagnostics uploads to Oracle. To learn more about Oracle Configuration Manager see the following Oracle Knowledge Article: 250434.1.

For your benefit, Oracle created an RDA/OCM bundle . Such a bundle contains both RDA and OCM software and it allows customers to install OCM as part of the RDA data collection process. Customers, who prefer to install OCM and RDA separately, are able to do this as well.

Download

To run RDA with the Oracle Configuration Manager bundle, choose the RDA/OCM bundle for your specific Operating System to download and click the related link. Each package contains all of the files you require, so only choose one package to download. If you need troubleshooting information for the OCM product, see Oracle Knowledge Article 250434.1 for assistance.

<!-- Generated rda_ocm.html by mk_webiv for notes :314422.1,372331.1 -->

1. RDA 4.14 Package with OCM Kit(Unix and Windows 32bit) - Also available from Knowledge Article: 372331.1
   
   Platform Specific RDA bundled with Oracle Configuration Manager Collector (Released Dec, 9 2008) ARU Download Link Instructions OCM Package Size

   For IBM AIX PPC CPU:p7563988_414_AIX.zip	Change the filename to rda.zip when saving	v10.3.0	size: 30,177,688 Bytes
   For HP-UX IA64 CPU:p7563988_414_HPUX-IA64.zip	Change the filename to rda.zip when saving	v10.3.0	size: 36,901,170 Bytes
   For HP-UX PA CPU:p7563988_414_HP64.zip	Change the filename to rda.zip when saving	v10.3.0	size: 31,342,360 Bytes
   For Linux x86/x86-64/AMD64/EM64T CPU:p7563988_414_LINUX.zip	Change the filename to rda.zip when saving	v10.3.0	size: 27,453,272 Bytes
   For Linux IA64 CPU:p7563988_414_Linux-IA64.zip	Change the filename to rda.zip when saving	v10.3.0	size: 32,798,731 Bytes
   For Linux PPC CPU:p7563988_414_LinuxPower.zip	Change the filename to rda.zip when saving	v10.3.0	size: 28,051,635 Bytes
   For IBM zSeries Based Linux CPU:p7563988_414_Linux-zSer.zip	Change the filename to rda.zip when saving	v10.3.0	size: 26,970,407 Bytes
   For SunOS Sparc CPU:p7563988_414_SOLARIS64.zip	Change the filename to rda.zip when saving	v10.3.0	size: 28,908,800 Bytes
   For MS Windows 32bit x86 CPU:p7563988_414_WINNT.zip	Change the filename to rda.zip when saving	v10.3.0	size: 26,326,231 Bytes
   For MS Windows 64bit	Use RDA standalone	N/A
   For MacOS X	Use RDA standalone	N/A
   For ZLinux	Use RDA standalone	N/A
   For VMS	Use RDA standalone	N/A

   <!-- End of Generation by mk_webiv -->
   
   
2. Standalone Multi-platform ( Windows 64bit,MacOS,HP Tru64,VMS (7.3-2 and above), ZLinux) RDA 4.14 Only Package (Released December 9, 2008)
   Choose an RDA packaging format you wish to download from either section and click the related link. Each package contains all of the files you require, so only choose one package to download. All packages contain the same version of RDA and works with all Oracle certified platforms.
   
   

   Note: Select RDA from the table below if your OS is not available from the list in step 1 or its against your security policy. Oracle encourages you to download the RDA-OCM bundle if available, for the following added support benefit

   • Secure, automated configuration collection
   • Simplified Service Request logging, tracking and reporting
   • Pro-active configuration-specific notification of Security and General Alerts
   • HealthCheck recommendations based on Support best practices when using configuration auto-collection
   • Personalized access to best practices and the Oracle Knowledge base
   • Project cataloging of key milestones and contacts associated with your configurations
   • Improves Oracle's understanding of your business needs

<!-- Generated rda_base.html by mk_webiv for notes :314422.1 -->

Available RDA standalone packages for download Download Link Instructions Package Size

Tar format: rda.tar	Change the filename torda.tar when saving	size: 6,072,320 Bytes
UNIX Tar and gzipped format: rda.tar.gz	Change the filename torda.tar.gz when saving (IE5+ users please use "Right-Click"+ "Save target as ..." or "Save link as ..." option. Otherwise the file will automatically uncompressed by your browser.)	size: 1,121,583 Bytes
Zip format: rda.zip	Change the filename torda.zip when saving	size: 1,494,419 Bytes

<!-- End of Generation by mk_webiv -->

Note: RDA 4 is written in Perl and is a command-line script. It uses basic Perl libraries so you do not have to install any additional software. This includes Windows platforms. RDA is designed to use the Perl libraries that are shipped with Oracle and/or shipped with most UNIX platforms. 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.

Installation Instructions

Instructions for UNIX/ZLinux Type Operating Systems

1. Choose or create a directory or area that is used exclusively for RDA 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: Each rda package (.zip, .tar, and, .tar.gz) creates a directory named "rda" containing all the required files when you extract it..

2. FTP the downloaded rda.tar, rda.tar.gz, or rda.zip file to your UNIX server in binary mode and place it in the directory chosen in step 1.
3. Extract the tar or .tar.gz archive contents into a new directory (do not create a directory called "rda"), preserving the directory structure of the archive. Do not extract the file into a directory that contains an older RDA version.

   For example:
   tar xvf rda.tar or
   gunzip rda.tar.gz or
   tar xvf rda.tar or
   unzip rda.zip

   Note: Each rda package (.zip, .tar, and, .tar.gz) creates a directory named " rda" containing all the required files when you extract it.

   Do not extract the contents of the RDA archive (rda.tar and rda.tar.gz) 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.

4. Make sure the RDA command (rda.sh and rda.pl) is executable. To verify, enter the following command:

   chmod +x <rda>

5. You can verify the RDA installation using the following command:

   rda.sh -cv

Instructions for Microsoft Windows Based Operating Systems

1. Create a new directory or area that will be used exclusively for RDA 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 not use a directory that contains an older version of RDA unless you have deleted the previous version of RDA first.

   Note: Each RDA package (.zip, .tar, and, .tar.gz) creates a directory named " rda " containing all the required files when you extract it.

2. Transfer the downloaded rda.zip file to your Windows server and place it in the directory chosen in step 1. If transferring the zip file from one system to another using FTP, remember to transfer it in binary mode.
3. 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

4. You can verify the RDA installation using the following command:

   rda.cmd -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 4 - OpenVMS Users Guide: Knowledge Article 171748.1.

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):

1. 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 tar, 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.

2. 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 libaries in current directory) is present in @INC section. Notice the last entry "." in the example below:

   @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
   .

3. Note: The RDA command you selected above is represented as <rda> in the rest of this procedure. Therefore substitute rda.sh, rda.pl, or perl rda.pl in place of <rda>.

4. The data collection requires an initial setup to determine which information should be collected. Enter the following command to initiate the set up:

   ./<rda> -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.

5. 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.
6. 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:

   ./<rda> [-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, ./rda.sh -fv. For additional information read the RDA FAQ.

7. A more targeted way of executing RDA and a way to limit the number of setup questions asked is the use of Diagnostic profiles (<rda> -p <profile_name>), see RDA Profiles for list of various profiles or run <rda> -L profiles. e.g:. ./rda.sh -p DB10g
8. 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:

   <output_directory>/<report_group>__start.htm

9. The final output is also packaged in an archive located in the <output_directory> 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 not rename 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 directory may not contain an archive file (.zip, .tar, .tar.gz, or .tar.Z). If the archive is missing, please archive all of the files in the <output_directory> 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

1. 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 tar, 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.
2. 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 <rda> in the rest of this procedure.

3. 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: <rda> means use either rda.cmd or rda.pl.

   <rda> -S

   After setup completes, you can review the setup file setup.cfg by opening it a text editor like wordpad.

   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.

4. 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.
5. 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:

   <rda> [-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 ./rda.cmd -fv. For additional information, read the RDA FAQ.

6. A more targeted way of executing RDA and a way to limit the number of setup questions asked is the use of Diagnostic profiles (<rda> -p <profile_name>), see RDA Profiles for list of various profiles . e.g:. ./rda.cmd -p DB10g
7. 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:

   <output_directory>/<report_group>__start.htm

8. The final output is also packaged in an archive located in the <output_directory> 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.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 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 <output_directory> manually and send them to Oracle Support. You can use a packaging/archive utility program such as http://www.info-zip.org/Zip.html

9. 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 it is named with 'RDA' in the filename; 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 notbundle 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 4 - RAC Cluster/Multi-Node Users Guide - Knowledge Article 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 4 - OpenVMS Users Guide - Knowledge Article 171748.1.

Upgrading RDA

Use the following procedure to upgrade the Standalone RDA:

1. Delete the rda directory and all it's contents. If you want to use the same setup.cfg file again, move it to another location first. Also, move any output files you wish to save.
2. Download the new version of RDA from this Knowledge Article.
3. 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.

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:

<rda> -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 <rda_directory><output_directory>/<report_group>__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 <host> 5.6 Generic 105181-29 sun4u
Fully qualified host name	<host><domain>
Platform	32 - bit Sun O/S Version 2.6
Logged in as	<user>
Last run as	uid=52279 (<user>)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/<user>/home/rda2/security/output
RDA install directory	/emea/oracle/<user>/home/rda2

The host names (machine names), are substituted by '<host>'. Similarly, user names are substituted by '<user>' 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 '<user>' 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 <user> 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:

<rda> -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:

<rda> -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 SR by selecting OSS Support Tools from the product list of values on the Create a SR screen. Click on "Expand the Product List" button to see the full set of products. Select the "Remote Diagnostic Agent (RDA) Issue" type 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.

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, with good usability, to the disabled community. 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. 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 additional information, visit the Oracle Accessibility Program Web site at

http://www.oracle.com/accessibility/

Accessibility of Code Examples in Documentation JAWS, a Windows screen reader, 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, JAWS 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.