# profiles.pod: Oracle Remote Diagnostic Agent Setup Profiles
# $Id: profiles.pod,v 1.4 2015/09/24 23:38:58 RDA Exp $
# ARCS: $Header: /home/cvs/cvs/RDA_8/src/scripting/lib/Pod/en/profiles.pod,v 1.4 2015/09/24 23:38:58 RDA Exp $

=head1 NAME

profiles - Oracle Remote Diagnostic Agent Setup Profiles

=head1 PROFILE DEFINITION

A setup profile consists of a list of data collection modules and predefined
settings. Therefore, the data collected using a profile can be slightly
different than using the module separately. Profiles are typically used to
set up all modules required to diagnose a specific class of problems.

Profile names are case sensitive and are group specific. For example,

 DB.Exadata_Assessment

However you can omit the group when a profile is name is used in a single
group.

=head1 USING A PROFILE

In this page, E<lt>rdaE<gt> represents the command you selected to run RDA (for
example, F<rda.pl>, F<rda.cmd>, F<rda.sh>, and C<perl rda.pl>).

When profiles are not used, RDA considers all existing modules by default. To
set up the data collection with a profile, use the following command:

 <rda> -S -p <profile_name>

Run the data collection as usual. If you want to perform all steps in a single
run, then use a command such as the following:

 <rda> -vdSCRP -p <profile_name>

You can combine profiles with other options. For example, specify an
alternative setup file location as follows:

 <rda> -vdSCRP -s $HOME/rda/system1 -p <profile_name>

Note: The F<$HOME/rda> directory must exist and it is used as the default
location for the report directory also.

While a profile remains the current profile, its setting values can
override other default values each time the setup is performed. To avoid this
behavior, you can switch to the C<Default> profile, by using a command similar
to the following:

 <rda> -S -p Default

To obtain a list of available profile names and their applicability, use the
following command:

 <rda> -L profiles

To view this manual page, enter the following:

 <rda> -M profiles

To view the manual page of a profile, enter the following:

 <rda> -M -p <profile_name>

Add the B<-f> option to include the list of settings assigned by the profile.

 <rda> -fM -p <profile_name>

To obtain the modules and profiles cross reference, enter the following:

 <rda> -x profiles

=head2 Setting Level Definitions

Only a minimum set of settings are prompted by default. To fine-tune the data
collection, run the profile with the C<advanced> setting level. For
example:

 <rda> -S -p advanced DB

This setting level is stored in the setup file. Therefore, if you have to
change the setting level, then run the profile again as follows:

 <rda> -S -p basic CFG

To obtain the list of all setting levels, enter the following:

 <rda> -L levels

=head2 Combining Setting Level and Profile

You can combine setting levels and profiles by concatenating them with
a hyphen (-) sign. You can specify them in any order.

 <rda> -S -p OFM.AS10g-advanced

As mentioned above, the setting level is saved in the setup file and is reused
by default in the next setup operations, including when configuring extra
modules.

=head2 Custom Profiles Definitions

These explanations assume that you are using the default profile definition
file. You can define the location of a custom profile definition with an
C<RDA_PROFILE> environment variable.

=head1 COPYRIGHT NOTICE

Copyright (c) 2002, 2016, Oracle and/or its affiliates. All rights reserved.

=head1 TRADEMARK NOTICE

Oracle and Java are registered trademarks of Oracle and/or its
affiliates. Other names may be trademarks of their respective owners.

=cut