MADHU ORACLE APPS & RAC DBA: October 2013

ASM Healthchecks :

ASM Healthchecks and Scripts:
===================================

To find the free space in an ASM disk :
select group_number, disk_number, name, failgroup, create_date, path, total_mb,free_mb from v$asm_disk;

To find the free space in an ASM diskgroup :
select name, group_number, name, type, state, total_mb, free_mb from v$asm_diskgroup;

To see the current ASM operations in Progress :
select group_number, operation, state, power, actual, sofar, est_work, est_rate, est_minutes from v$asm_operation;

ASM Healthchecks :
=================
[oracle@madhu21 ~]$ ps -ef | grep css
root 18864 1 0 Dec09 ? 00:02:25 /app/base/GRID/11.2.0/bin/cssdmonitor
root 18881 1 0 Dec09 ? 00:02:50 /app/base/GRID/11.2.0/bin/cssdagent
oracle 18895 1 1 Dec09 ? 06:27:07 /app/base/GRID/11.2.0/bin/ocssd.bin
oracle 23285 14709 0 23:28 pts/4 00:00:00 grep css
[oracle@madhu21 ~]$

[oracle@madhu21 ~]$ crsctl check crs
CRS-4638: Oracle High Availability Services is online
CRS-4537: Cluster Ready Services is online
CRS-4529: Cluster Synchronization Services is online
CRS-4533: Event Manager is online

[oracle@bgadbs21 ~]$ ps -ef | grep asm

ASM_Disk groups
---------------------
SQL> SELECT
2 name group_name
, sector_size sector_size
3 4 , block_size block_size
5 , allocation_unit_size allocation_unit_size
6 , state state
7 , type type
8 , total_mb total_mb
9 , (total_mb - free_mb) used_mb
10 , ROUND((1- (free_mb / total_mb))*100, 2) pct_used
FROM
11 12 v$asm_diskgroup
13 WHERE
14 total_mb != 0
15 ORDER BY
name
16 17 /

Find diskgroup sizes:
======================
SET LINESIZE 145
SET PAGESIZE 9999
SET VERIFY off

COLUMN group_name FORMAT a20 HEAD 'Disk Group|Name'
COLUMN sector_size FORMAT 99,999 HEAD 'Sector|Size'
COLUMN block_size FORMAT 99,999 HEAD 'Block|Size'
COLUMN allocation_unit_size FORMAT 999,999,999 HEAD 'Allocation|Unit Size'
COLUMN state FORMAT a11 HEAD 'State'
COLUMN type FORMAT a6 HEAD 'Type'
COLUMN total_mb FORMAT 999,999,999 HEAD 'Total Size (MB)'
COLUMN used_mb FORMAT 999,999,999 HEAD 'Used Size (MB)'
COLUMN pct_used FORMAT 999.99 HEAD 'Pct. Used'

break on report on disk_group_name skip 1

compute sum label "Grand Total: " of total_mb used_mb on report

SELECT
name group_name
, sector_size sector_size
, block_size block_size
, allocation_unit_size allocation_unit_size
, state state
, type type
, total_mb total_mb
, (total_mb - free_mb) used_mb
, ROUND((1- (free_mb / total_mb))*100, 2) pct_used
FROM
v$asm_diskgroup
WHERE
state = 'MOUNTED'
ORDER BY name;

Find ASM-components sizes:
=============================
SET ECHO OFF
SET FEEDBACK 6
SET HEADING ON
SET LINESIZE 180
SET PAGESIZE 50000
SET TERMOUT ON
SET TIMING OFF
SET TRIMOUT ON
SET TRIMSPOOL ON
SET VERIFY OFF

CLEAR COLUMNS
CLEAR BREAKS
CLEAR COMPUTES

COLUMN component FORMAT a25 HEAD 'Component Name'
COLUMN current_size FORMAT 9,999,999,999 HEAD 'Current Size'
COLUMN min_size FORMAT 9,999,999,999 HEAD 'Min Size'
COLUMN max_size FORMAT 9,999,999,999 HEAD 'Max Size'
COLUMN user_specified_size FORMAT 9,999,999,999 HEAD 'User Specified|Size'
COLUMN oper_count FORMAT 9,999 HEAD 'Oper.|Count'
COLUMN last_oper_type FORMAT a10 HEAD 'Last Oper.|Type'
COLUMN last_oper_mode FORMAT a10 HEAD 'Last Oper.|Mode'
COLUMN last_oper_time FORMAT a20 HEAD 'Last Oper.|Time'
COLUMN granule_size FORMAT 999,999,999 HEAD 'Granule Size'

SELECT
component
, current_size
, min_size
, max_size
, user_specified_size
, oper_count
, last_oper_type
, last_oper_mode
, TO_CHAR(last_oper_time, 'DD-MON-YYYY HH24:MI:SS') last_oper_time
, granule_size
FROM
v$sga_dynamic_components
ORDER BY
component DESC

SOME IMP NOTE-ID'S:

SOME IMP NOTE-ID'S:
=====================

1025288.6 --- How to Diagnose and Resolve ORA-01650,ORA-01652,ORA-01653,ORA-01654,ORA-01688 : Unable to Extend < OBJECT > by %S in Tablespace %S

1035935.6 --- Example of How To Resize the Online Redo Logfiles

133062.1 --- ORA-25150 Altering Of Extent Parameters Not Permitted While Applying Patch

139516.1 --- Discoverer 4i with Oracle Applications 11i

15476.1 --- FAQ about Detecting and Resolving Locking Conflicts

177240.1 --- Supported 11i Login URLs - using Dev60cgi / f60cgi to Access Applications is Unsupported

207959.1 --- All About Security: User, Privilege, Role, SYSDBA, O/S Authentication, Audit, Encryption, OLS

216205.1 --- Database Initialization Parameters for Oracle Applications 11i

216550.1 --- Oracle Applications Release 11i with Oracle9i Release 2 (9.2.0)

218089.1 --- Autoconfig FAQ

230672.1 --- Cloning Oracle Applications Release 11i with Rapid Clone

233428.1 --- Sharing the Application Tier File System in Oracle Applications 11i

236247.1 --- Transferring Archive Logs to the Standby Database Disconnects

242941.1 --- How To Troubleshoot Java-based Workflow Notification Mailer In 11.5.9 and OWF.G

260676.1 --- When Applying Patch 2644375 Worker Is Prompting For Parameter 5 In The Worker Log

277710.1 --- Ora-00600: Internal Error Code, Arguments: [1236], [], ... Ora-600

282234.1 --- Error "java.lang.NullPointerException" In Step 3 Of Configuring WF Java Mailer In Applications 11i

ORA-04030: out of process memory when trying to allocate 48 bytes (TCHK^93bb9d5b,idndef : qcuAllocIdn)

a)ORA-04030: out of process memory when trying to allocate 16328 bytes (koh-kghu call ,pmucalm coll)

b)ORA-04030: out of process memory when trying to allocate 16328 bytes (koh-kghu call ,pmucalm coll)~Incident details in:

Solution:

The problem related to Memory allocation at OS level:

I have gone through the Note ID:

PLSQL Procedure Causing ORA-04030: (pga heap,control file i/o buffer) And ORA-04030: (koh-kghu sessi,pmuccst: adt/record) or ORA-04030: (koh-kghucall ,pmucalm coll) Errors (Doc ID 1325100.1)

Any Queries reach me kotturi.madhu@gmail.com

PSU(PATCH SET UPDATE) FROM 11.2.0.1.7 to 11.2.0.3.0

PSU(PATCH SET UPDATE):

§ Per –request is satisfied on DBGALE instance Oracle home

o Opatch Version should be 11.2.0.3.0

§ This is not satisfied we need to upgrade the OPATCH version from 11.2.0.1.7 to 11.2.0.3.0

§ Download the OPatch utility (Patch 6880880) to a temporary directory.

§ For each Oracle RAC database home and the GI home that are being patched, run the following commands as the home owner to extract the OPatch utility.

· zip <OPATCH-ZIP> -d <ORACLE_HOME>

· $ <ORACLE_HOME>/OPatch/opatch version

o Validation of Oracle Inventory

§ <ORACLE_HOME>/OPatch/opatch lsinventory -detail -oh <ORACLE_HOME>

o Unzipping the Patch

o Check Inventory on Both Nodes -

§ ./opatch lsinventory -bugs_fixed | egrep 'PSU|PATCH SET UPDATE'

o Loading Modified SQL Files into the Database

§ cd $ORACLE_HOME/rdbms/admin

§ sqlplus /nolog

§ SQL> CONNECT / AS SYSDBA

§ SQL> STARTUP

§ SQL> @catbundle.sql psu apply

§ SQL> QUIT

o Check the following log files in $ORACLE_BASE/cfgtoollogs/catbundle for any errors:

§ catbundle_PSU_<database SID>_APPLY_<TIMESTAMP>.log

§ catbundle_PSU_<database SID>_GENERATE_<TIMESTAMP>.log

Scheduling Gather Schema Statistics

Scheduling Gather Schema Statistics For “ALL” Schemas.

================================================

To run concurrent program Gather Schema Statistics:

Log on to Oracle Applications withSysadmin

Select System Administrator à Concurrent à Requests

Select Single Request option as shown in the below picture ….

Click ok to continue ….

Query for “Gather Schema Statistics” concurrent program …

Select “Gather Schema Statistics” concurrent program and click ok ..

It will Request for the “Parameters” Enter the appropriate parameters. This can be run for specific schemas by specifying the schema name or entering ‘ALL’ to gather statistics for every schema in the database..

Click Ok to continue ….

Click Schedule button to schedule the gather schema statistics program as per the requirement …

Select Periodically Option for running weekly once …

Scheduled Time (Every week Friday at 20.00 Perth Time)..

Click OK …

And Submit the Concurrent Request …

Note down the Concurrent Request ID …

To Check the Concurrent Request ID status:

Checking the Concurrent Request ID status from database …..

Detailed Information about Parameters

Parameters

Schema Name: Schema for which statistics are to be gathered. Specify ALL for all Oracle Applications schemas

Percent: The sampling percentage. If left blank, the default value of10 is used. The valid range is from 0 to 100

Degree: The degree of parallelism to be used for gathering statistics. If a Degree is not provided, it defaults to the minimum ofparallel_max_servers and cpu_count.

Backup Flag: NOBACKUP isused, then the GATHER_SCHEMA_STATS procedure will not backup the current statistics. This way the GATHER_SCHEMA_STATS procedure will run faster.

Restart Request ID: In the case where the Gather Schema Statistics run fails due to whatever reasons, the concurrent request can be re-submitted and it will pick up where the failed run left off, if you provide the concurrent request_id of the failed run.

History Mode: Last Run – History records for each object are maintained only for the last gather statistics run. Each subsequent run will overwrite the previous history record for the object. This is the default behavior

Gather Options: GATHER: All tables and indexes of the schema schema name are selected for stats gathering. This is the default

Modifications Threshold: Applicable only to GATHER AUTO and LIST AUTO Options

Invalidate Dependent Cursors: This flag indicates whether cursors dependent on the table being analyzed should be invalidated or not. By default, dependent cursors are invalidated

APPS SHORTCUT KEYS

RMAN Duplicate from RAC backup fails ORA-38856 [ID 334899.1]

RMAN Duplicate from RAC backup fails ORA-38856 [ID 334899.1]:

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

In this Document

Symptoms

Changes

Cause

Solution

Applies to:

Oracle Database - Enterprise Edition - Version 10G/11G [Release 10.2]

Information in this document applies to any platform.

***Checked for relevance on 28-May-2013***

Symptoms:

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

RMAN duplicate using a backup taken from a RAC installation fails on opening the clone instance with

RMAN-06136: ORACLE error from auxiliary database:

ORA-38856: cannot mark instance UNNAMED_INSTANCE_2 (redo thread 2) as enabled

The target database is a RAC two node database being duplicated to a single instance database.

Changes:

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

RMAN is being used to clone from a source backup taken from a RAC database.

Cause:

---------

Unpublished Bug 4355382 ORA-38856: FAILED TO OPEN DATABASE WITH RESETLOGS WHEN USING RAC BACKUP

ORA-38856 is the expected error during open database resetlogs when the set of enabled instances (redo threads) in the controlfile does not match the set of enabled instances (redo threads) in datafile checkpoint. This is expected behavior in a normal RAC restore/recover/open resetlogs situation.

However, in a cloning scenario where, once the clone database is opened with resetlogs you would never expect to restore the old (RAC) backup , this check doesnt matter.

Solution:

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

As a workaround you could do the following:

1.Set the following parameter in the auxiliary init.ora file:

_no_recovery_through_resetlogs=TRUE

Then open with resetlogs;

Once the auxiliary has opened, remove this hidden parameter.

Temporary Tablespace Enhancements in Oracle Database 11g

Temporary Tablespace Enhancements in Oracle Database 11g:
===========================================

Oracle 11g has a new view called DBA_TEMP_FREE_SPACE that displays information about temporary tablespace usage.
SQL> SELECT * FROM dba_temp_free_space;

TABLESPACE_NAME TABLESPACE_SIZE ALLOCATED_SPACE FREE_SPACE
------------------------------ --------------- --------------- ----------
TEMP 56623104 56623104 55574528

1 row selected.

SQL>
Armed with this information, you can perform an online shrink of a temporary tablespace using the ALTER TABLESPACE command.
SQL> ALTER TABLESPACE temp SHRINK SPACE KEEP 40M;

Tablespace altered.

SQL> SELECT * FROM dba_temp_free_space;

TABLESPACE_NAME TABLESPACE_SIZE ALLOCATED_SPACE FREE_SPACE
------------------------------ --------------- --------------- ----------
TEMP 42991616 1048576 41943040

1 row selected.

SQL>
The shrink can also be directed to a specific tempfile using the TEMPFILE clause.
SQL> ALTER TABLESPACE temp SHRINK TEMPFILE '+OBIDATA/<SID>/tempfile/temp01.dbf' KEEP 10240M;

Tablespace altered.

SQL> SELECT * FROM dba_temp_free_space;

TABLESPACE_NAME TABLESPACE_SIZE ALLOCATED_SPACE FREE_SPACE
------------------------------ --------------- --------------- ----------
TEMP 31522816 65536 31457280

1 row selected.

SQL>

The KEEP clause specifies the minimum size of the tablespace or tempfile. If this is omitted, the database will shrink the tablespace or tempfile to the smallest possible size.
SQL> ALTER TABLESPACE temp SHRINK SPACE;

Tablespace altered.

SQL> SELECT * FROM dba_temp_free_space;

TABLESPACE_NAME TABLESPACE_SIZE ALLOCATED_SPACE FREE_SPACE
------------------------------ --------------- --------------- ----------
TEMP 1114112 65536 1048576

1 row selected.

CONTROLF FILE BACKUP FAILING IN Database.

======================================

Control File Backup has been failing with below error with the following error:

PROBLEM:

==========

RMAN-00571: ===========================================================

RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============

RMAN-00571: ===========================================================

RMAN-03009: failure of Control File and SPFILE Autobackup command on CH01 channel at 02/20/2013 19:07:31

ORA-00245: control file backup failed; target is likely on a local file system

SOLUTION:

When checked the RMAN settings the snap shot controlfile is being stored in local mount point where as in 11.2.0.3. it should be stored in shared location or in ASM disk. In RAC environment any form of controlfile backup may fail with ORA-0245 if the location of the Snapshot Controlfile is not a shared location.

The backup of the controlfile actualy makes a backup of the SNAPSHOT controlfile. The Snapshot controlfile is created when the controlfile is about to be backed up.

Change the RMAN configuration as shown below :

RMAN> show all;

using target database control file instead of recovery catalog

RMAN configuration parameters for database with db_unique_name <SID> are:

CONFIGURE RETENTION POLICY TO RECOVERY WINDOW OF 7 DAYS;

CONFIGURE BACKUP OPTIMIZATION ON;

CONFIGURE DEFAULT DEVICE TYPE TO DISK;

CONFIGURE CONTROLFILE AUTOBACKUP ON;

CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO "/dbbackup/<SID>/20022013/%F";

CONFIGURE DEVICE TYPE DISK PARALLELISM 8 BACKUP TYPE TO COMPRESSED BACKUPSET;

CONFIGURE DATAFILE BACKUP COPIES FOR DEVICE TYPE DISK TO 1; # default

CONFIGURE ARCHIVELOG BACKUP COPIES FOR DEVICE TYPE DISK TO 1; # default

CONFIGURE CHANNEL DEVICE TYPE DISK FORMAT 'CLEAR';

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 LOAD TRUE ; # default

CONFIGURE ARCHIVELOG DELETION POLICY TO SHIPPED TO ALL STANDBY BACKED UP 1 TIMES TO DISK;

CONFIGURE SNAPSHOT CONTROLFILE NAME TO '/home/oracle/snapcf_<SID>.f';

RMAN> CONFIGURE SNAPSHOT CONTROLFILE NAME TO '+EBSDATA/<SID>/snapcf_<SID>.f';

old RMAN configuration parameters:

CONFIGURE SNAPSHOT CONTROLFILE NAME TO '/home/oracle/snapcf_<SID>.f';

new RMAN configuration parameters:

CONFIGURE SNAPSHOT CONTROLFILE NAME TO '+EBSDATA/<SID>/snapcf_<SID>.f';

new RMAN configuration parameters are successfully stored

RMAN> show all;

RMAN configuration parameters for database with db_unique_name <SID> are:

CONFIGURE RETENTION POLICY TO RECOVERY WINDOW OF 7 DAYS;

CONFIGURE BACKUP OPTIMIZATION ON;

CONFIGURE DEFAULT DEVICE TYPE TO DISK;

CONFIGURE CONTROLFILE AUTOBACKUP ON;

CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO "/dbbackup/<SID>/20022013/%F";

CONFIGURE DEVICE TYPE DISK PARALLELISM 8 BACKUP TYPE TO COMPRESSED BACKUPSET;

CONFIGURE DATAFILE BACKUP COPIES FOR DEVICE TYPE DISK TO 1; # default

CONFIGURE ARCHIVELOG BACKUP COPIES FOR DEVICE TYPE DISK TO 1; # default

CONFIGURE CHANNEL DEVICE TYPE DISK FORMAT 'CLEAR';

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 LOAD TRUE ; # default

CONFIGURE ARCHIVELOG DELETION POLICY TO SHIPPED TO ALL STANDBY BACKED UP 1 TIMES TO DISK;

CONFIGURE SNAPSHOT CONTROLFILE NAME TO '+EBSDATA/<SID>/snapcf_<SID>.f';

Relocating Datafiles from one ASM Disk to Another using RMAN:

Relocating Datafiles from one ASM Disk to Another using RMAN:

Relocating Datafiles from one ASM Disk to Another using RMAN

1. Place the datafile to be moved in offline

SQL> alter database datafile '+<DGNAME>/<SID>/datafile/ebsdata.287.790435127' offline;

Database altered.

2. Copy the datafile to target ASM disk and don’t mention any directory structure.

RMAN> copy datafile '+<DGNAME>/<SID>/datafile/ebsdata.287.790435127' to '+PPRDATA';

Starting backup at 03-JAN-13

using channel ORA_DISK_1

channel ORA_DISK_1: starting datafile copy

input datafile file number=00013 name=+<DGNAME>/<SID>/datafile/ebsdata.287.790435127

output file name=+PPRDATA/<SID>/datafile/ebsdata.286.803747693 tag=TAG20130103T151453 RECID=20 STAMP=803749077

channel ORA_DISK_1: datafile copy complete, elapsed time: 00:23:05

Finished backup at 03-JAN-13

Starting Control File and SPFILE Autobackup at 03-JAN-13

piece handle=/dbbackup/<SID>/c-2626060668-20130103-04 comment=NONE

Finished Control File and SPFILE Autobackup at 03-JAN-13

3. Make note of input and outfile name run the following command.

RMAN> run {

2> set newname for datafile '+<DGNAME>/<SID>/datafile/ebsdata.287.790435127' to '+PPRDATA/<SID>/datafile/ebsdata.286.803747693'; ?Output file name here from step 2.

3> switch datafile all;

4> }

executing command: SET NEWNAME

datafile 13 switched to datafile copy

input datafile copy RECID=20 STAMP=803749077 file name=+PPRDATA/<SID>/datafile/ebsdata.286.803747693

4. Once done recover the new datafile

SQL> recover datafile '+PPRDATA/<SID>/datafile/ebsdata.286.803747693';

Media recovery complete.

5. Make the datafile online.

SQL> alter database datafile '+PPRDATA/<SID>/datafile/ebsdata.286.803747693' online;

Database altered.

We can’t use the same method for SYSTEM and SYSAUX datafiles as we can’t put the datafiles of system and sysaux in offline. Use the following method to move the datafiles of system and sysaux.

6. Take backup as copy for system tablespace.

RMAN> backup as copy tablespace system format '+PPRDATA';

Starting backup at 03-JAN-13

using channel ORA_DISK_1

channel ORA_DISK_1: starting datafile copy

input datafile file number=00019 name=+PPRDATA/<SID>/datafile/system01.dbf

output file name=+PPRDATA/<SID>/datafile/system.293.803756671 tag=TAG20130103T174431 RECID=34 STAMP=803756736

channel ORA_DISK_1: datafile copy complete, elapsed time: 00:01:05

channel ORA_DISK_1: starting datafile copy

input datafile file number=00001 name=+<DGNAME>/<SID>/datafile/system.297.790435247

output file name=+PPRDATA/<SID>/datafile/system.294.803756737 tag=TAG20130103T174431 RECID=35 STAMP=803756774

channel ORA_DISK_1: datafile copy complete, elapsed time: 00:00:45

Finished backup at 03-JAN-13

Starting Control File and SPFILE Autobackup at 03-JAN-13

piece handle=/dbbackup/<SID>/c-2626060668-20130103-0f comment=NONE

Finished Control File and SPFILE Autobackup at 03-JAN-13

7. Take backup as copy for sysaux tablespace.

RMAN> backup as copy tablespace sysaux format '+PPRDATA';

Starting backup at 03-JAN-13

using channel ORA_DISK_1

channel ORA_DISK_1: starting datafile copy

input datafile file number=00002 name=+<DGNAME>/<SID>/datafile/sysaux.293.790435173

output file name=+PPRDATA/<SID>/datafile/sysaux.295.803756811 tag=TAG20130103T174650 RECID=36 STAMP=803756930

channel ORA_DISK_1: datafile copy complete, elapsed time: 00:02:05

channel ORA_DISK_1: starting datafile copy

input datafile file number=00020 name=+PPRDATA/<SID>/datafile/sysaux01.dbf

output file name=+PPRDATA/<SID>/datafile/sysaux.296.803756935 tag=TAG20130103T174650 RECID=37 STAMP=803756994

channel ORA_DISK_1: datafile copy complete, elapsed time: 00:01:05

Finished backup at 03-JAN-13

Starting Control File and SPFILE Autobackup at 03-JAN-13

piece handle=/dbbackup/<SID>/c-2626060668-20130103-10 comment=NONE

Finished Control File and SPFILE Autobackup at 03-JAN-13

8. Once backup of system and sysaux is completed stop the database.

[oracle@bgaodb21 ~]$ srvctl stop database -d <SID>

[oracle@bgaodb21 ~]$ ps -ef|grep pmon

oracle 7617 1 0 2012 ? 00:18:31 asm_pmon_+ASM1

oracle 32162 22710 0 18:06 pts/1 00:00:00 grep pmon

9. Start the database in mount on one node if this is RAC database.

SQL> startup mount;

ORACLE instance started.

Total System Global Area 8551575552 bytes

Fixed Size 2230472 bytes

Variable Size 3942647608 bytes

Database Buffers 4596957184 bytes

Redo Buffers 9740288 bytes

Database mounted.

SQL> exit

10. Connect to RMAN and switch both system and sysaux tablespaces by issues the following command.

[oracle@bgaodb21 ~]$ rman

Recovery Manager: Release 11.2.0.1.0 - Production on Thu Jan 3 18:07:04 2013

RMAN> connect target /

connected to target database: <SID> (DBID=2626060668, not open)

RMAN> switch tablespace system to copy;

using target database control file instead of recovery catalog

datafile 1 switched to datafile copy "+PPRDATA/<SID>/datafile/system.294.803756737"

datafile 19 switched to datafile copy "+PPRDATA/<SID>/datafile/system.293.803756671"

RMAN> switch tablespace sysaux to copy;

datafile 2 switched to datafile copy "+PPRDATA/<SID>/datafile/sysaux.295.803756811"

datafile 20 switched to datafile copy "+PPRDATA/<SID>/datafile/sysaux.296.803756935"

11. Recover the database.

Rman>Recover database.

12. Once recovery is completed shutdown the database and start the database.

Srvctl start database –d <SID>.