Oracle Database RMAN Defaults List

Oracle database RMAN (Recovery Manager) has some default settings. To get to know details of RMAN defaults, use show all command. Connect to target database and issue the command
$rman target /
RMAN> show all;
using target database control file instead of recovery catalog
RMAN configuration parameters for database with db_unique_name onlinetutelage are:
CONFIGURE RETENTION POLICY TO REDUNDANCY 1; # default
CONFIGURE BACKUP OPTIMIZATION OFF; # default
CONFIGURE DEFAULT DEVICE TYPE TO DISK; # default
CONFIGURE CONTROLFILE AUTOBACKUP OFF; # default
CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO ‘%F’; # default
CONFIGURE DEVICE TYPE DISK PARALLELISM 1 BACKUP TYPE TO BACKUPSET; # default
CONFIGURE DATAFILE BACKUP COPIES FOR DEVICE TYPE DISK TO 1; # default
CONFIGURE ARCHIVELOG BACKUP COPIES FOR DEVICE TYPE DISK TO 1; # default
CONFIGURE MAXSETSIZE TO UNLIMITED; # default
CONFIGURE ENCRYPTION FOR DATABASE OFF; # default
CONFIGURE ENCRYPTION ALGORITHM ‘AES128’; # default
CONFIGURE COMPRESSION ALGORITHM ‘BASIC’ AS OF RELEASE ‘DEFAULT’ OPTIMIZE FOR LOA
D TRUE ; # default
CONFIGURE ARCHIVELOG DELETION POLICY TO NONE; # default
CONFIGURE SNAPSHOT CONTROLFILE NAME TO ‘C:APPUSERPRODUCT11.2.0DBHOM
E_3DATABASESNCFlr.ORA’; # default
RMAN>
The output shows that control file of the target database is used instead of recovery catalog.

Oracle database startup stages enterprise manager

Oracle database instance can be started in stages. This sequence can be viewed from Oracle Enterprise Manager Database Control 11g. Here are the sequence of steps and corresponding screen shots. I’ve logged into OEM as SYSMAN user with NORMAL Privilege (NORMAL in Drop-Down menu)
1) When database is in normal state
2) Shutdown the instance using SHUTDOWN IMMEDIATE command. This throws an error in OEM Database Control
3) Issue STARTUP command with NOMOUNT option. In Database Control Click OK.Instance status shows no mount
4) Mount the database by issuing ALTER DATABASE MOUNT; command. Click on refresh button at top right corner of database control and status changes to mounted
5) Open the database using ALTER DATABASE OPEN; command. This will show the status as open now

ORA-01688: unable to extend ASH tables in sysaux tablespace fix


I got a call from client stating that they have ORA-1688 messages recorded in alert.log file. Upon investigation I found that there has been storage problems in SYSAUX tablespace causing storage problems. The error happened to be ORA-01688 related to extending ASH tables that demanded more extents the basic storage structure needed for tablespace to grow bigger and better
As a side effect, active session history tables that get created, did throw ORA-1688 error owing to unable to extend tablespace.
As a fix, we need to look for free space in sysaux tablespace and address it in one of the following two ways:
1) Add more space to existing tablespace using alter database command
2) Add additional datafile to SYSAUX tablespace to address the space issue
As a side effect indexes belonging to SYS tables became unuable. To fix this issue we need to rebuild index online
select * from dba_indexes where status=’UNUSABLE’;
alter index index_name rebuild online;
It is to be taken care of from capacity planning perspective and more space need to be added to SYSAUX tablespace

Free Oracle Database Articles, Tips, Jobs :

Delivered by FeedBurner

Oracle DBA Packages,Display Package specification and Package Body



Display Package specification and Package Body can be accomplished as follows:
For package specification details issue the command:
select line,text from user_source where name = ‘package_name’ and type = ‘PACKAGE’ order by line;
desc ;
For Package Body issue the command:
select line,textfrom user_source where name = ‘package_name’and type = ‘PACKAGE BODY’order by line;

Free Oracle Database Articles, Tips, Jobs :

Delivered by FeedBurner