Oracle Diagnostics Tool-rda use

RDA is the short name of the remote diagnostic Agent, the tool Oracle uses to collect and analyze databases, and running the tool does not change any of the parameters of the system, and RDA collects data that is comprehensive and simplifies our day-to-day monitoring and analysis of databases. Oracle Support also recommends that we provide RDA-collected data when feedback is relevant, providing a strong guarantee for quick resolution of the problem.

One, supported operating systems

IBM AIX

Intel Linux (RedHat and SuSE)

HP-UX (10.* and 11.*)

HP Tru64

Sequent dynix/ptx

Sun Solaris (2.6-2.10)

Windows XP Professional

Windows Workstation and Server

Windows 2003 Server

Second, supported Oracle products

Oracle RDBMS Server (Standard and Enterprise Editions)

Oracle RAC Cluster (single Node Collection)

Oracle Application Server (IAS 1.0.2.x/9.0.x/10.1.2.x, HTTP server)

Oracle Management Server and intelligent agent (Grid server, Agent Server, DB control)

OLAP Products (Express server, Financial Analyzer, and Demand Planning Server)

Oracle Developer (Forms and Reports)

Oracle Collaboration Suites (Email Server and Internet Directory)

Oracle Networking Products

Three, mainly for the diagnosis of the database of the following aspects of the problem

Performance, installation, configuration, upgrades, porting, and internal error issues.

Iv. installation of RDA (version 4.12-080530)

Tools Download: Metalink (need Metalink account)

Installation instructions for the UNIX operating system:

1, the tool download after the window operating system do not do decompression, the script file format will be destroyed.

2, FTP upload is the use of binary mode.

3. Perform decompression command

$ gunzip rda.tar.gz

$ tar xvf Rda.tar

4, the test is normal

$ CD RDA

$./rda.sh-c

V. Use of RDA

In UNIX operating systems, Oracle recommends execution under the database creation user (typically Oracle users), and the first use requires a collection of initial configuration.

To execute a command:

$./rda.sh-s

After the command is executed, a wizard interface allows you to complete the initial configuration based on the actual installed product of the current database. Configuration files Setup.cfg, Setup.bak are generated in the RDA directory after the configuration is completed, and can be modified directly if the configuration parameters need to be readjusted.

The configuration process is typically a default value, or if you are prompted to enter parameters, special places are as follows:

-------------------------------------------------------------------------------

Enter an Oracle User ID (userid only) to view Dba_ and v$ tables

If RDA would be run under the Oracle software owner ' s ID, enter a '/' here,

and select Y at the SYSDBA prompt to avoid being prompted for the database

Password at runtime.

Hit ' return ' to accept the default (System):/

Is '/' a SYSDBA user (would connect as SYSDBA) (y/n)?

Hit ' return ' to accept the default (N):

> Y

-------------------------------------------------------------------------------

After the initial configuration is completed to collect data, execute the command:

$./rda.sh

If you want to see a detailed collection process, you can execute the command:

$./rda.sh-v

Enter Sysman User password:

Please re-enter it to confirm:

You may need to enter the password for the database-related user during the acquisition process.

After the acquisition is completed, the initial configuration file is generated in the RDA directory based on the format Zip report file and acquisition log, default file location./output/rda $machine _name.zip.

By decompressing the file and accessing the __start.htm, you can see the details of the data collected this time.

$ CD Output

$ ls-l *zip

-rw-r--r--1 Oracle oinstall 1911090 November 14:49 RDA. Rda_game.zip

$ sz RDA. Rda_game.zip

Points to note when using:

1, sometimes can not generate a Zip format report file, which is related to whether the client installation of compression tools, the need to extract the relevant report files.

2. If you need to install the generated configuration to collect again, delete the generated report file, and then execute the command:

$./RDA.SH-SVF

Reset and then execute the capture command:

$./rda.sh-v

VI. Data Acquisition and analysis

The report file mainly includes the database corresponding machine operating system software, hardware environment, user settings and database detailed information (initial parameters, running events, day-to-day monitoring, etc.).

In the daily maintenance, we mainly focus on:

1, attention to the RDBMS under the several statistical information

setting of database-related initial parameters in db SPFile Parameters SPFile

SGA Information View the current memory information in the system global area

Database session-related information in Sessions and processes acquisition time

V$system_event waiting statistics view for all process events during the entire run of a database instance

v$session_wait session wait events and related positioning information data

Latch Information Competition-related information (translation is not very accurate)

Tablespaces database table space Information (table space type, corresponding data file usage, scalability, etc.)

database files databases corresponding data file information (file location, usage, etc.)

Invalid Objects failed database objects, daily monitoring if found to be ineffective, need maintenance personnel to manually recompile

All errors database errors performed on a daily basis

Main concerns in V$system_event, v$session_wait (buffer busy waits, db file scattered read, DB file sequential read, enqueue, free buffer Waits, latch free, log file sync, log file Paralle write these events.

2, the RDBMS log/trace Files information

Alert.log database System-level logs

Last errors database's most recent Exception log, depending on trace file location, you can view detailed error information