Remote Diagnostic Agent (RDA) - Main Man Page

会UI设计的dba 2025-02-14

189

RDA Manual Page (rda)

Interface Manual Page

rda - Oracle Remote Diagnostic Agent (RDA)

SYNOPSIS

rda.sh [-bcdfilnqvwy] [-SCRP|A|B|D|E|G|H|I|K|L|M|Q|V|T] [-e list] [-m dir] [-o out] [-p prof] [-s nam] [-t lvl] [mod ...]

rda.cmd [-bcdfilnqvwy] [-SCRP|A|B|D|E|G|H|I|K|L|M|Q|V|T] [-e list] [-m dir] [-o out] [-p prof] [-s nam] [-t lvl] [mod ...]

rda.pl [-bcdfilqtvwy] [-SCRP|A|B|D|E|G|H|I|K|L|M|Q|V|T] [-e list] [-m dir] [-o out] [-p prof] [-s nam] [-t lvl] [mod ...]

rda.sh [-bilnqvy] [-e list] [-s nam] [-t lvl] [-u lng] [-X pkg] [fct arg...]

rda.cmd [-bilnqvy] [-e list] [-s nam] [-t lvl] [-u lng] [-X pkg] [fct arg...]

rda.pl [-bilnqvy] [-e list] [-s nam] [-t lvl] [-u lng] [-X pkg] [fct arg...]

See the following sections for additional information about the switches.

DESCRIPTION

The purpose of RDA is to assist in problem analysis and troubleshooting of local and remote databases, file systems, and operating system environments in relation to Oracle products. This tool helps automate the task of gathering information about an Oracle environment for the Oracle Support and Development teams and customers to analyze the Oracle technology stacks quickly.

For example, if a customer has problems with SQL*NET, then Oracle Support may want to view the configuration files and the environment related to the problems. This can include information about the operating system, database, and file system. The RDA Development team adds content to the tool regularly to gather information about more products.

You can run RDA concurrently as long as each execution refers to a different setup file. You can share the same report directory if you specify different report groups during the setup phase. However, usually the compiled versions of the RDA engine do not allow concurrent executions.

For more information about this tool or to download the latest version, see My Oracle Support documents 314422.1 and 330363.1.

COMMAND VARIANTS

`rda.sh`	UNIX shell RDA launcher, which attempts to locate Perl in the Oracle home directory structure when it is not available in the `PATH` environment variable.
`rda.cmd`	Microsoft RDA launcher, which attempts to locate Perl in the Oracle home directory structure.
`rda.com`	VMS RDA launcher, which checks the user environment and locates Perl and Zip.
`rda.pl`	RDA main script, which can be used directly if Perl is available in the `PATH` environment variable (for UNIX) or if the `.pl` suffix is registered (for Windows).

OPTIONS

Mode Options

-A

Adds or deletes passwords in an Oracle Wallet to enable batch execution of data collections. The wallet file, cwallet.sso, is created in directory <result_set_name>_wallet, located in the same directory as the collector definition file. The supported account types are host, jdbc, odbc, oracle, pseudo, wls, and wsp. The default account type is oracle.
Authentication information is given in the following format:

<username>[/<password>][[@<account_type>]@<connect_info>]

For example you can provide:

`<username>/<password>`
`<username>/<password>@<sid>`
`<username>/<password>@oracle@<sid>`
`<username>`
`<username>@<sid>`
`<username>@oracle@<sid>`
`<username>@host@<hostname>`
`<username>@jdbc@<driver>\|<url>`
`<username>@odbc@<dsn>`
`<username>@pseudo@<id>`
`<username>@wls@<domain>`
`<username>@wsp@<domain>`

If the password is omitted on the command line when you add authentication, RDA prompts you to specify it interactively. When an asterisk (*) prefixes the user name (\* on Unix platforms), RDA deletes the entry instead of adding it. To amend a saved password repeat the add command using the new value.

-B Starts a background data collection process. When forking capability is available within the Perl implementation, RDA collects the information in a child process with a different session identifier. RDA uses an exclusive lock to prevent concurrent executions and redirects standard input and output to /dev/null by default. However, you can specify an output file with the -o option. If you specify the -f option, then RDA issues a halt request and the process performs the initial data collection and sample archiving tasks only.

-C Collects the diagnostic information for modules specified as arguments. When no modules are specified as arguments, the data is collected for all configured modules. Unless you specify the -f option, RDA collects the data that was previously uncollected only.
To set the trace mode at the module level, prefix the module name with t: or T:, respectively for tracing the execution or for tracing both the execution and the variable assignment.

-D Deletes the modules that are specified as arguments from the setup. It is possible only to delete modules that do not have reports. When you specify the -f option, RDA removes the associated reports first.
Note: You cannot delete the modules that are executed at each data collection run.

-E Displays an explanation of the error numbers that are specified as arguments.

-G Converts reports or a group of reports to XML format.

-H Sends a halt request to the current background data collection. The collection process stops when the current task is complete or at the next wake up.

-I Regenerates the report index. When you specify the -f option, RDA reloads the cascading style sheet in the output directory.

-K Kills the current background data collection process. This option is possible only in Perl versions with fork and signals implemented.

-L Lists the available profiles, modules, tools, tests, conversion groups, setting levels. You can restrict the list by specifying list types (modules, profiles, tools, etc) as arguments. The result list for the profiles, collections, tools list types can be further restricted by specifying the -g option followed by a collection group name. Collection group names match the sub directories found under RDA_HOME/collect (e.g. EM, DB, OFM, OS). Example:
-g OFM,OS -L modules profiles
Finally, when you specify the -f option, RDA displays the data collection modules that are always executed.

-M Displays the related manual pages associated with the arguments. You can replace the arguments by a -p option, to get profile manual pages. By default, RDA displays this manual page. The operating system "pager" mechanism must be configured to pause at the end of the page to support multiple arguments in interactive mode.

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

-Q Displays the setup questions for the modules that are specified as arguments. When you specify a higher setting level, you can list additional questions. To support multiple arguments in interactive mode, you must configure the pager to pause at the end of the file.

-R Generates the HTML reports. By default, RDA generates out-dated and missing 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 configured only.

-T Executes tools or test modules that are specified as arguments. When you do not specify any module, RDA runs the default modules.
To set the trace mode at the module level, prefix the module name with t: or T:, respectively for tracing the execution or for tracing both the execution and the variable assignment.

-V Displays the version of the RDA components and previously loaded Perl modules. The Perl module list is not exhaustive as additional packages can be loaded dynamically during the execution of other functions.

Modifiers

`-b`	Does not back up the setup file. By default, RDA renames the setup file with a `.bak` suffix before rewriting the file.
`-c`	Verifies that RDA was installed correctly and still exists. When you do not specify any arguments, RDA verifies file permissions and check sums. Otherwise, RDA checks the syntax of the configuration and definition files that are specified as arguments. RDA skips all other files. RDA returns a 0 (zero) exit status when no errors are detected. Otherwise, it returns a nonzero exit status.
`-e key=value[,...]`	Specifies a temporary value for one or more settings. RDA converts the setting names automatically to upper case and separates the different assignments by commas. For example, the following value enables some ping tests and allows a maximum of 120 seconds for executing each SQL request. `-e OS.NET.B_PING_TESTS=1,DFT/N_SQL_TIMEOUT=120` You can use this mechanism also to alter the default setting values when making non-interactive setups.
`-f`	Sets the force mode, which influences the Background, Collect, Delete, Index, List, Report, and Setup modes. For more information about these modes, see the Mode Options section.
`-g grp`	Specify the group for list or XML conversion features.
`-h`	Displays the command usage and exits.
`-i`	Reads settings from the standard input. Therefore, this option suppresses all interactive dialogues in setup and all user acknowledge requests in the data collection or tests.
`-l`	Uses a lock file to prevent concurrent usage of a setup file. RDA derives the name of the lock file from the setup file name. RDA generates an error if the lock cannot be acquired immediately.
`-m dir`	Specifies the module directory (`modules` by default).
`-n`	Ignores the content of any existing setup file. This option enables you to start a new collection without any manual operation on existing setup files.
`-o out`	Specifies an output file for a background data collection.
`-p prof`	Specifies the setting level and/or the setup profiles to use during the setup operations. When you specify both, use a hyphen (-) to separate them. 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 setup of the corresponding modules.
`-q`	Sets the quiet mode.
`-s nam`	Specifies the name of the setup file (`output` by default). You can maintain multiple setup configurations in the same directory structure. The name of the setup file must start with a letter followed by alphanumeric characters or underscores and cannot exceed 32 characters. It can also include a directory part. That directory must exist and will be used as the default location for other files (such as lock files and the report directory).
`-u lng`	Specifies the language and the character set to use for the engine error messages and texts. For example, `-l es.88591` gives the preference to Spanish when available. SDCI will encode them with the ISO 8859-P1 character set.
`-v`	Sets the verbose mode.
`-w`	Prevents the current RDA job from running when the background collection daemon is active. The process waits until the current daemon task is complete. RDA does not update the setup file when you specify this option.
`-x`	Produces a cross reference for the specified arguments or profiles.
`-y`	Accepts all setting defaults in the module configuration. This option suppresses all interactive dialogues in setup and all user acknowledge requests in the data collection or tests.

Debugging Options

-t lvl Enables RDA tracing and specifies the global trace level. The trace level is an integer number between 0 and 99. The upper digit is dedicated to the agent operations, while the lower digit is more used by the functional layers.
Specialized dump and trace mechanisms requires the presence of this option, regardless its value.

SPECIAL USAGE

You can combine the -S, -C, -R, and -P mode flags. Other modes are exclusive. Regroup the module names by using a hyphen (-) as separator when -C, -D, -Q, or -S mode flags are used.

When you execute the RDA command without specifying any mode or module, RDA performs the complete data collection, report generation, and report packaging. RDA sets up the data collection at its first execution.

The setup step must be done explicitly for profile based data collection.

By default, RDA creates collector definition files and their corresponding diagnostic data directories in the current working directory. The name of the diagnostic data directory is derived from the collector name. Use the -s option or the RDA_SETUP environment variable to store them in another directory.

ENVIRONMENT

The following environment variables influence the execution of RDA:

COLUMNS	Used to adjust the page width when displaying manual pages (78 by default).
HOME	User home directory.
ORACLE_BASE	Oracle base directory.
ORACLE_HOME	Oracle home directory.
ORACLE_SID	Oracle system identifier.
PAGER	Pager that RDA uses to display the manual pages. RDA uses `more` by default.
PATH	Command execution path.
RDA_BUNDLE	Path of a complementary XML conversion bundle definition file (none by default). RDA ignores the environment variable when the corresponding file does not exist or cannot be read.
RDA_CHARSET	Character set to use when displaying engine message (`utf8` by default)
RDA_CONVERT	Alternative location for the XML conversion plug-in directory structure (`Convert` by default).
RDA_CWD	Alternative working directory for the setup files or for relative paths to setup files. When you do not specify this variable, RDA uses the current working directory.
RDA_DOMAIN	Default domain name used to bypass the domain detection. RDA performs this detection at setup when the domain name is not available from the setup file and not included in the host name.
RDA_EDIT	Specifies a temporary value for one or more settings as for the `-e` option.
RDA_FILTER	Specifies a filter definition file to load when creating a new setup file.
RDA_LANG	Preferred language to use by the engine (`en` by default).
RDA_LEVEL	Sets the global trace level.
RDA_LOCK	Directory where the RDA lock files are stored. By default, they are stored in the directory that contains the setup file.
RDA_MAN	When specified, it does not use `Pod::Text` to display manual pages.
RDA_MRC	Path of a complementary multi-run collection definition file. RDA ignores the environment variable when the corresponding file does not exist or cannot be read.
RDA_NO_7ZIP	When specified, it disables the search and the use of the `7zip` command.
RDA_NO_COMPRESS	When specified, it disables the search and the use of the `compress` command.
RDA_NO_DBD_ORACLE	When set to a nonzero value, disables the usage of `DBD::Oracle`. The command wrappers do not verify that Perl can load this package without errors when a value is set.
RDA_NO_GZIP	When specified, it disables the search and the use of the `gzip` command.
RDA_NO_JAR	When specified, it disables the search and the use of the `jar` command.
RDA_NO_PAX	When specified, it disables the search and the use of the `pax` command.
RDA_NO_TAR	When specified, it disables the search and the use of the `tar` command.
RDA_NO_XZ	When specified, it disables the search and the use of the `xz` command.
RDA_NO_ZIP	When specified, it disables the search and the use of the `zip` command.
RDA_PID	Directory where the control files for the background collection are stored. By default, they are stored in the directory that contains the setup file.
RDA_PROFILE	Specifies the path of an alternative profile definition file. RDA ignores the environment variable when the corresponding file does not exist or cannot be read.
RDA_SETUP	Specifies the setup name to be used when the `-s` option is not specified. The name can contain a directory part. That directory must exist and is used as a default location for other files (such as the lock files and the report directory).
SHELL	For UNIX, the command interpreter (shell) to use.
TERM	Terminal name. When supported by the platform, it identifies the escape sequences used for controlling the display.

FILES

For UNIX, rda.sh creates a .config file to cache where Perl is located in the Oracle home directory structure.

RDA collects execution events and statistics in an RDA.log file in the report directory. Use this file to retrieve the execution history. For security reasons, it does not contain any setting or command arguments. The report packages contain the RDA.log file to identify further product improvements.

The RDA engine can create three lock files. The names are derived from the setup file name:

`<setup>.lck`	To avoid concurrent usage of a setup file (see options `-B` and `-l`)
`-B-<setup>.lck`	To serialize file manipulation tasks between foreground and background RDA processes.
`-T-<setup>.lck`	To monitor thread execution completion.

The RDA_LOCK environment variable influences the location of the lock files.

PERL PACKAGES USED

An RDA data collection explicitly calls the following Perl packages:

·	`strict`
·	`vars`
·	`Cwd`
·	`Exporter`
·	`File::Basename`
·	`File::Copy`
·	`File::Spec`
·	`Getopt::Std`
·	`IO::File`
·	`IO::Handle`
·	`POSIX`
·	`Socket`
·	`Symbol`
·	`Time::Local`

The following packages are used but they are not required for the data collection:

·	`Compress::Zlib` (used for accessing archives)
·	`DBD::ODBC` (used for alternative ODBC accesses)
·	`DBD::Oracle` (used for alternative accesses to Oracle databases)
·	`DBI` (used for alternative database accesses)
·	`Digest::MD5` (used for check sums)
·	`Fcntl` (used in locking context)
·	`Sys::Hostname` (used as help for determining the domain name)
·	`Term::Cap` (used to enhance the display)
·	`Time::HiRes` (used for clock checks)
·	`Win32` (used for spawning processes)
·	`Win32::Console` (used for disabling echo)
·	`Win32::ODBC` (used for ODBC accesses)
·	`Win32::Process` (used for spawning processes)

Back to Main Menu

RDA Manual Page (sdci)

Interface Manual Page

sdci - Support Diagnostic Command-line Interface (SDCI)

SYNOPSIS

sdci.sh [-bilnqvy] [-X pkg|-M|-V] [-e edt] [-s nam] [-t lvl] [-u lng] [fct arg...]

sdci.cmd [-bilnqvy] [-X pkg|-M|-V] [-e edt] [-s nam] [-t lvl] [-u lng] [fct arg...]

sdci.pl [-bilnqvy] [-X pkg|-M|-V] [-e edt] [-s nam] [-t lvl] [-u lng] [fct arg...]

See the following sections for additional information about the switches.

DESCRIPTION

SDCI is a command-line tool to manage Oracle diagnostic data collectors and, more particularly, the Remote Diagnostic Agent (RDA).

For example, if a customer has problems with Oracle Net, then Oracle Support may want to view the configuration files and the environment related to the problems. This can include information about the operating system, database, and file system. The RDA Development team adds content to the tool regularly to gather information about more products.

For more information about this tool, or to download the latest version, see My Oracle Support documents 314422.1 and 330363.1.

COMMAND VARIANTS

`sdci.sh`	UNIX shell SDCI launcher, which attempts to locate Perl in the Oracle home directory structure when it is not available in the `PATH` environment variable.
`sdci.cmd`	Microsoft SDCI launcher, which attempts to locate Perl in the Oracle home directory structure.
`sdci.com`	VMS SDCI launcher, which checks the user environment and locates Perl and Zip.
`sdci.pl`	SDCI main script, which can be used directly if Perl is available in the `PATH` environment variable (for UNIX) or if the `.pl` suffix is registered (for Windows).

OPTIONS

Mode Options

`-M`	Displays the command manual pages.
`-V`	Displays the software and engine builds.
`-X pkg`	Invokes the specified user interface. The default user interface is `Rda`.

Modifiers

`-b`	Does not back up the setup file. By default, SDCI renames the setup file with a `.bak` suffix before rewriting the file.
`-e key=value[,...]`	Specifies a temporary value for one or more settings. SDCI converts the setting names automatically to upper case and separates the different assignments by commas. For example, the following value enables some ping tests and allows a maximum of 120 seconds for executing each SQL request. `-e OS.NET.B_PING_TESTS=1,DFT/N_SQL_TIMEOUT=120` You can use this mechanism also to alter the default setting values when making non-interactive setups.
`-h`	Displays the command usage and exits.
`-i`	Reads settings from the standard input. Therefore, this option suppresses all interactive dialogues in setup and all user acknowledge requests in the data collection or tests.
`-l`	Uses a lock file to prevent concurrent usage of a setup file. RDA derives the name of the lock file from the setup file name. RDA generates an error if the lock cannot be acquired immediately.
`-n`	Ignores the content of any existing setup file. This option enables you to start a new collection without any manual operation on existing setup files.
`-q`	Sets the quiet mode.
`-s nam`	Specifies the name of the setup file (`output` by default). You can maintain multiple setup configurations in the same directory structure. The name of the setup file must start with a letter followed by alphanumeric characters or underscores and cannot exceed 32 characters. It can also include a directory part. That directory must exist and will be used as the default location for other files (such as lock files and the report directory).
`-u lng`	Specifies the language and the character set to use for the engine error messages and texts. For example, `-l es.88591` gives the preference to Spanish when available. SDCI will encode them with the ISO 8859-P1 character set.
`-v`	Sets the verbose mode.
`-y`	Accepts all setting defaults in the module configuration. This option suppresses all interactive dialogues in setup and all user acknowledge requests in the data collection or tests.

Debugging Options

SPECIAL USAGE

The mode flags are exclusive.

By default, SDCI creates collector definition files and their corresponding diagnostic data directories in the current working directory. The name of the diagnostic data directory is derived from the collector name. Use the -s option or the RDA_SETUP environment variable to store them in another directory.

ENVIRONMENT

The following environment variables influence the execution of RDA:

COLUMNS	Used to adjust the page width when displaying manual pages (78 by default).
HOME	User home directory.
ORACLE_BASE	Oracle base directory.
ORACLE_HOME	Oracle home directory.
ORACLE_SID	Oracle system identifier.
PAGER	Pager that RDA uses to display the manual pages. RDA uses `more` by default.
PATH	Command execution path.
RDA_BUNDLE	Path of a complementary XML conversion bundle definition file (none by default). SDCI ignores the environment variable when the corresponding file does not exist or cannot be read.
RDA_CHARSET	Character set to use when displaying engine message (`utf8` by default)
RDA_CONVERT	Alternative location for the XML conversion plug-in directory structure (`Convert` by default).
RDA_CWD	Alternative working directory for the setup files or for relative paths to setup files. When you do not specify this variable, RDA uses the current working directory.
RDA_DOMAIN	Default domain name used to bypass the domain detection. RDA performs this detection at setup when the domain name is not available from the setup file and not included in the host name.
RDA_EDIT	Specifies a temporary value for one or more settings as for the `-e` option.
RDA_FILTER	Filter definition file to load when creating a new setup file.
RDA_LANG	Preferred language to use by the engine (`en` by default).
RDA_LEVEL	Sets the global trace level.
RDA_LOCK	Directory where the RDA lock files are stored. By default, they are stored in the directory that contains the setup file.
RDA_MAN	When specified, it does not use `Pod::Text` to display manual pages.
RDA_MRC	Path of a complementary multi-run collection definition file. RDA ignores the environment variable when the corresponding file does not exist or cannot be read.
RDA_NO_7ZIP	When specified, it disables the search and the use of the `7zip` command.
RDA_NO_COMPRESS	When specified, it disables the search and the use of the `compress` command.
RDA_NO_DBD_ORACLE	When set to a nonzero value, disables the usage of `DBD::Oracle`. The command wrappers do not verify that Perl can load this package without errors when a value is set.
RDA_NO_GZIP	When specified, it disables the search and the use of the `gzip` command.
RDA_NO_JAR	When specified, it disables the search and the use of the `jar` command.
RDA_NO_PAX	When specified, it disables the search and the use of the `pax` command.
RDA_NO_TAR	When specified, it disables the search and the use of the `tar` command.
RDA_NO_ZIP	When specified, it disables the search and the use of the `zip` command.
RDA_PID	Directory where the control files for the background collection are stored. By default, they are stored in the directory that contains the setup file.
RDA_PROFILE	Path of a complementary profile definition file. RDA ignores the environment variable when the corresponding file does not exist or cannot be read.
RDA_SETUP	Specifies the setup name to be used when the `-s` option is not specified. The name can contain a directory part. That directory must exist and is used as a default location for other files (such as the lock files and the report directory).
SHELL	For UNIX, the command interpreter (shell) to use.
TERM	Terminal name. When supported by the platform, it identifies the escape sequences used for controlling the display.

FILES

For UNIX, sdci.sh or rda.sh creates a .config file to cache where Perl is located in the Oracle home directory structure.

RDA collects execution events and statistics in an RDA.log file in the data diagnostic data directory. Use this file to retrieve the execution history. For security reasons, it does not contain any setting or command arguments. The report packages contain the RDA.log file to identify further product improvements.

The RDA engine can create three lock files. The names are derived from the setup file name:

`<setup>.lck`	To avoid concurrent usage of a setup file (see options `-B` and `-l`)
`-B-<setup>.lck`	To serialize file manipulation tasks between foreground and background RDA processes.
`-T-<setup>.lck`	To monitor thread execution completion.

The RDA_LOCK environment variable influences the location of the lock files.

PERL PACKAGES USED

An RDA data collection explicitly calls the following Perl packages:

·	`strict`
·	`vars`
·	`Cwd`
·	`Exporter`
·	`File::Basename`
·	`File::Copy`
·	`File::Spec`
·	`Getopt::Std`
·	`IO::File`
·	`IO::Handle`
·	`POSIX`
·	`Socket`
·	`Symbol`
·	`Time::Local`

The following packages are used but they are not required for the data collection:

·	`Compress::Zlib` (used for accessing archives)
·	`DBD::ODBC` (used for alternative ODBC accesses)
·	`DBD::Oracle` (used for alternative accesses to Oracle databases)
·	`DBI` (used for alternative database accesses)
·	`Digest::MD5` (used for check sums)
·	`Fcntl` (used in locking context)
·	`Sys::Hostname` (used as help for determining the domain name)
·	`Term::Cap` (used to enhance the display)
·	`Time::HiRes` (used for clock checks)
·	`Win32` (used for spawning processes)
·	`Win32::Console` (used for disabling echo)
·	`Win32::ODBC` (used for ODBC accesses)
·	`Win32::Process` (used for spawning processes)

Back to Main Menu

COPYRIGHT NOTICE

TRADEMARK NOTICE

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

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 to all users, including users that are disabled. 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. Accessibility 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 more information, visit the Oracle Accessibility Program Web site at
https://www.oracle.com/corporate/accessibility/

Accessibility of Code Examples in Documentation

Screen readers 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, some screen readers 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.

Deaf/Hard of Hearing Access to Oracle Support Services

To reach Oracle Support Services, use a telecommunications relay service (TRS) to call Oracle Support at 1.800.223.1711. An Oracle Support Services engineer will handle technical issues and provide customer support according to the Oracle service request process. Information about TRS is available at https://www.fcc.gov/trs.

oracle

「喜欢这篇文章，您的关注和赞赏是给作者最好的鼓励」

关注作者

Remote Diagnostic Agent (RDA) - Main Man Page

RDA Manual Page (rda)

Interface Manual Page

SYNOPSIS

DESCRIPTION

COMMAND VARIANTS

OPTIONS

Mode Options

Modifiers

Debugging Options

SPECIAL USAGE

ENVIRONMENT

FILES

PERL PACKAGES USED

RDA Manual Page (sdci)

Interface Manual Page

SYNOPSIS

DESCRIPTION

COMMAND VARIANTS

OPTIONS

Mode Options

Modifiers

Debugging Options

SPECIAL USAGE

ENVIRONMENT

FILES

PERL PACKAGES USED

COPYRIGHT NOTICE

TRADEMARK NOTICE

LEGAL NOTICES AND TERMS OF USE

DOCUMENTATION ACCESSIBILITY

评论