Oracle diagnostic tool-RDA

Oracle diagnostic tool-RDA

RDA is short for Remote Diagnostic Agent. It is a tool used by oracle to collect and analyze databases. Running this tool does not change any system parameters. RDA collects comprehensive data, it can simplify our daily monitoring and analysis of databases. Oracle Support also recommends that we provide data collected by RDA when providing feedback on related issues, which can provide a powerful guarantee for quick problem solving.

1. 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 2000 Workstation and Server

Windows 2003 Server

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

Iii. Mainly used to diagnose the following problems of the database

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

Iv. RDA installation (version 4.12-080530)

Tool download: metalink (metalink account is required)

Installation instructions on Unix operating systems:

1. Do not decompress the tool in the window operating system after it is downloaded. The script file format will be damaged.

2. ftp upload is in binary mode.

3. Execute the decompression command

$ Gunzip rda.tar.gz

$ Tar xvf rda.tar

4. Check whether the test is normal.

$ Cd rda

$./Rda. sh-c

V. Use of RDA

In Unix operating systems, it is recommended that oracle be executed under database creation users (generally oracle users). An initial collection configuration is required for the first use.

Run the following command:

$./Rda. sh-S

After the command is executed, a wizard interface is displayed to allow you to complete initial configuration based on the product installed in the current database. After the configuration is complete, the configuration files setup. cfg and setup. bak will be generated in the rda directory. If you need to re-adjust the configuration parameters, you can directly modify the file.

The configuration process is generally the default value, or enter parameters as prompted. The special points are as follows:

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

Enter an Oracle User ID (userid only) to view DBA _ and V $ tables

If RDA will 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 (will connect as sysdba) (Y/N )?

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

> Y

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

To collect data after initial configuration, run the following command:

$./Rda. sh

To view the detailed collection process, run the following command:

$./Rda. sh-v

Enter sysman user password:

Please re-enter it to confirm:

You may need to enter the password of the database-related user during the collection process.

After the collection is complete, the report file in zip format and the collection log will be generated according to the initial configuration file in the rda directory. The default file location is./output/rda.w.machine_name.zip.

Decompress the file and access mongostart.htm to view the detailed information of the collected data.

$ Cd output

$ Ls-l * zip

-Rw-r -- 1 oracle oinstall 1911090 14:49 RDA.RDA_game.zip

$ Sz RDA.RDA_game.zip

Note:

1. Sometimes the report file in zip format cannot be generated, which is related to whether the client installs the compression tool. You need to decompress the report file on your own.

2. If you need to install the generated configuration for collection again, delete the generated report file and run the following command:

$./Rda. sh-Svf

Re-set and then execute the collection command:

$./Rda. sh-v

6. Collect data analysis

The report files mainly include the operating system software, hardware environment, user settings, and detailed database information (initial parameters, Operation events, and daily monitoring) of the corresponding database machine ).

In daily maintenance, we mainly focus on:

1. Pay attention to the statistics under RDBMS

Set Database-related initial Parameters in Database SPFile Parameters spfile

View the current memory Information in the global zone of the system using SGA Information

Sessions and Processes

V $ System_Event wait statistics view of all process events during the whole running period of the database instance

V $ Session_Wait session wait event and related positioning information data

Latch Information competition Information (translation is not very accurate)

Table space database tablespace information (table space type, corresponding data file usage, scalability, etc)

Database Files Database data file information (file location, usage, etc)

Invalid Objects database Objects. If any failures are detected in routine monitoring, the maintenance personnel must manually re-compile

All errors database errors that are routinely executed

In V $ System_Event, V $ Session_Wait focuses on (buffer busy waits, db file scattered read, db file sequential read, enqueue, free buffer waits, latch free, log file sync, log file paralle write events.

2. RDBMS Log/Trace Files information

Alert. log database system-level log

Last errors: The latest exception log of the database. You can view detailed error information based on the location of the trace file.