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 if you
are running RDA to assist in a performance related issue.
In this case,
we recommend that you log on as the Unix user that owns
the Oracle
software, then issue
su root or su privileged_user
Do not use su - as that will reset the
environment.
Run setup.sh to configure RDA for the options to be
collected
% ./setup.sh
Setup for the Oracle rda.sh Version 3.10 parameters
Enter the Prefix for all the Files Generated
Hit Return to Accept Default: RDA
============================>
[More prompts continue...]
At this time, you should be able to run the rda script
######################################################
1) Make sure it is executable: $ chmod +x rda.sh
2) At this point, $ORACLE_SID should be set and you
should be able to connect to sqlplus with the userid
you entered
3) The screen will indicate various iterations of
files being collected.
Once it has completed, you will be able to send the
resulting /rda309/RDA_Output/RDA.<pid>.rda.tar.Z
file
to Oracle.
<pid> will be the process id from the execution of
rda.sh that created the file.
4) If this file was generated to assist in resolving a
TAR, please send /rda309/RDA_Output/RDA.<pid>.rda.tar.Z
to Oracle Support using the 'upload to support' link in
the Tar Update section of Metalink.
will be the process id from the execution of rda.sh that
created the file.
#######################################################
Special notes on userids and passwords
Starting with version 3.03 of RDA, the default option is
not
to store the password in plain text in the setup.txt file, but to prompt the user for the password
when RDA is started. If you are currently executing RDA at regularly scheduled intervals via cron,
you may need to adjust your cron jobs accordingly. You still have the option of storing the password
as plain text in the setup.txt file, should you so desire.
Starting with version 3.03 of RDA, you may now indicate
if the userid provided is a SYSDBA user. However, RDA does not support specifying
/ as the
username.
Review setup.txt (optional)
After setup.sh completes you can optionally view the
setup.txt file and make any changes manually.
Run rda.sh (do not specify the shell when running
rda.sh or you will receive
various "is not an identifier" errors).
% ./rda.sh
RDA Started Sun Nov 12 12:11:08 EDT 2002
RDA Starting Version 3.10, please wait..
[More output is displayed...]
Review the output (start with RDA__START.htm)
The simplest way of reviewing the output files is to
launch a web browser on the same machine where rda.sh is
run and open the file RDA__START.htm located in the
RDA_Output directory.
Alternatively, you may ftp the <prefix>.<pid>.rda.tar.Z
output file, created in the RDA_Output directory, in binary mode to a Windows client machine.
Most Windows compression utilities, such as WinZip version 8.0+, can read Unix compressed files.
A third option would be to access the RDA__START.htm
file from a browser using the ftp (instead of http) protocol. The URL will look similar to
ftp://username@hostname.domain/home/rda_dir/RDA_Output//RDA__START.htm. Note that this option may
not work with all browsers or servers.
Upload the <prefix>.<pid>.rda.tar.Z file to
Oracle Support
RDA will produce a compressed tar file called
<prefix>.<pid>.rda.tar.Z. Please do not rename the file as it will help Oracle Support to quickly identify that RDA
output is attached to the iTAR After you log the iTAR, upload the file using
the 'upload to support' link when updating the iTAR via MetaLink. Remember to transfer this file in
binary
mode!