Applies to:
OSS Support Tools - Version 4.29 and laterInformation in this document applies to any platform.
Main Content
RDA 4 Getting Started
RDA Documentation Links | |||||
---|---|---|---|---|---|
Getting Started You are here |
In This Document
RDA 4.x Overview
Note: Please review installation and execution instructions below. If you experience difficulties or receive errors please follow theRDA Troubleshooting Guide and RDA FAQ for instructions on reporting problems. |
Overview
What's New in this RDA Release
Platforms Supported
- 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)
Following Platforms are NOT Supported:
- IBM Z/OS (OS/390)
Products Supported
- 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
Versions Supported
Why use RDA?
- Acquired company product issues
- Developer issues
- Installation/configuration issues
- ORA-600, ORA-7445, ORA-3113, and ORA-4031 errors
- Oracle Database issues
- Oracle Application Server/Fusion Middleware issues
- Oracle Collaboration products (Oracle Collaboration Suite and Oracle Beehive) issues
- Oracle Application issues
- Other corrective issues
- Performance issues
- Upgrade, migration, and linking issues
Oracle Configuration Manager
- 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
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/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
Note:If your platform is certified for OCM, the RDA zip file below is conveniently bundled with OCM.
RDA bundle (Released MON, D YYYY) | |||||||
---|---|---|---|---|---|---|---|
Platform | Download File | ||||||
Apple Mac OS X | |||||||
HP OpenVMS | |||||||
HP Tru64 | |||||||
HP-UX Itanium | |||||||
HP-UX PA-RISC (32-bit) | |||||||
HP-UX PA-RISC (64-bit) | |||||||
IBM AIX on POWER Systems (32-bit) | |||||||
IBM AIX on POWER Systems (64-bit) | |||||||
IBM Dynix/Ptx | |||||||
IBM Linux on POWER | |||||||
IBM zSeries Based Linux | |||||||
Linux Itanium | |||||||
Linux x86 (32-bit) | |||||||
Linux x86 (64-bit) | |||||||
Microsoft Windows (32-bit) | |||||||
Microsoft Windows (64-bit) | |||||||
Sun Solaris Intel (32-bit) | |||||||
Sun Solaris Intel (64-bit) | |||||||
Sun Solaris SPARC (32-bit) | |||||||
Sun Solaris SPARC (64-bit) |
Note: RDA 4 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 abinary version is available for download on major platforms. |
Note: In this document <rda> 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 <rda>. |
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 notuse 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 <rda>
- You can verify the RDA installation using the following command:./<rda> -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 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.
- 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
- You can verify the RDA installation using the following command:<rda> -cv
Instructions for HP OpenVMS Based Operating Systems
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 -VInspect 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 . |
- The data collection requires an initial setup to determine which information should be collected. Enter the following command to initiate the set up:./<rda> -SIncluding 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.
- 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:./<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> -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 (<rda> -p <profile_name>), see RDA Profiles for list of various profiles or run <rda> -L profiles. e.g:. ./<rda> -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:<output_directory>/<report_group>__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 <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 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 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.
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 scriptthat 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 -VIn 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.
- 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> -SAfter 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.
- 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:<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> -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 (<rda> -p), see RDA Profiles for list of various profiles. e.g: <rda> -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:<output_directory>/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 <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
- 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.)
Instructions for Oracle RAC Cluster or Multi-Node Environment
Instructions for HP OpenVMS Based Operating Systems:
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 setup.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
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
Special Note on the Output Directory
Viewing RDA Report Output Files
Special Note on Security Filters
Machine and Version | SunOS 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 |
- Domain names
- Group names
- Host names
- IPv4 and IPv6 addresses
- LDAP domain components
- Network masks
- User names
Using Security Filters
Reporting Problems or Feedback
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 |