================================================================================

===========
D) RDA output
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
+++++++++++
================================================================================
===========
Collect an RDA report from the ASM ORACLE_HOME.
Use the collection script with following options: 'rda.sh -p advanced ASM'.For
details, see Note 314422.1
Also, please, do the following to provide a global view of the situation:
Download the latest version 4.18 or 4.19 of RDA based on the note 314422.1 named
"Remote Diagnostic Agent (RDA) 4 - Getting Started'
Then connect to the OS user owning the ASM ORACLE_HOME (ie: grid) and then use t
he following syntax:
./rda.sh -vSCRP ASM RAC OS INST
-C
Collects the diagnostic information for modules specified as arguments.
When no modules are specified as arguments, the data is collected for all config
ured modules.
Unless you specify the -f option, RDA collects the data that was previously unco
llected only.
-P
Packages all reports that belong to the report group using zip, pax, tar
or jar. When several commands are available, preference is first given to zip,
then to pax, and then to tar.
When possible, it uses compress or gzip to compress tar files.
-R
Generates the HTML reports. By default, RDA generates out-dated and miss
ing reports only. When you specify the -f option, RDA generates all reports. RDA
regenerates the index automatically when reports are produced.
-S
Configures all modules that are specified as arguments. When you do not
specify any module, then RDA configures all available modules.
Unless you specify the -f option, RDA considers modules that are not yet configu
red only
-p prof
Specifies the setting level and/or the setup profiles to use dur
ing the setup operations. When you specify both, use a hyphen (-) to separate th
em. By default, RDA considers the basic setting level and all existing modules.
Use the advanced setting level to specify more settings interactively.
When you specify a new profile at collection time, RDA performs an implicit setu
p of the corresponding modules.
================================================================================
===========
Please take care to answer the questions (Y) in order to collect all the possibl
e information (DO NOT USE SYSTEMATICALLY THE DEFAULT ANSWER).
------------Please run the Remote Diagnostic Agent (RDA) on the instance where you are
experiencing the issue and upload the output file to MetaLink. Remember: You
can review the RDA output using a web browser. Instructions for RDA are
available via Metalink:
Note 314422.1 "Remote Diagnostic Agent (RDA) 4.0 - Overview"
Note 330363.1 "Remote Diagnostic Agent (RDA) 4 - FAQ"
Note 330344.1 "Remote Diagnostic Agent (RDA) 4.0 - Training"
Note 330362.1 "Remote Diagnostic Agent (RDA) 4 - Troubleshooting Guide"

PLEASE USE THE FOLLOWING SYNTAX TO GENERATE THE RDA OUTPUT:

Delete the "setup.cfg" file in the directory of RDA.
then:
./Rda.sh -vSRCP OS INST ASM
./Rda.sh -vSRCP OS INST ASM
./rda.sh -vCRP OS DB ===> this force collection
===========================================
ADRCI
adrci> show homes
ADR Homes:
diag/asm/+asm/+ASM4
diag/tnslsnr/exa104/listener
diag/rdbms/testdb/TESTDB4
diag/rdbms/fsdb/FSDB4
diag/rdbms/edwprd/EDWPRD4
diag/rdbms/edwsgprd/EDWSGPRD4
diag/rdbms/edwreprd/EDWREPRD4
diag/rdbms/mdbp/MDBP4
adrci> set home diag/tnslsnr/exa104/listener purge -age 1440 set home
adrci> diag/rdbms/edwprd/EDWPRD4 purge -age 1440