| Oracle FAQ | Your Portal to the Oracle Knowledge Grid | |
 |
 | |||
| Oracle FAQ | Your Portal to the Oracle Knowledge Grid | |
|
| |||
Home -> Community -> Usenet -> c.d.o.server -> RMAN-10039 on rman duplicate and metalink Note: 403214.1
I am hitting what seems like bug described in this note (note below)..
however, there are a few things that I don't get
Mar 29 13:58:31 my-db kernel: Node 0 HighMem per-cpu: empty Mar 29 13:58:31 my-db kernel: Mar 29 13:58:31 my-db kernel: Free pages: 9140kB (0kB HighMem) Mar 29 13:58:31 my-db kernel: Active:36757 inactive:1945578dirty:357966 writeback:0 unstable:0 free:2285 slab:35002 mapped:36721 pagetables:1419
Mar 29 13:58:31 my-db kernel: Free swap: 16639208kB Mar 29 13:58:31 my-db kernel: 2293760 pages of RAM Mar 29 13:58:31 my-db kernel: 252274 reserved pages Mar 29 13:58:31 my-db kernel: 1163936 pages shared Mar 29 13:58:31 my-db kernel: 0 pages swap cached Mar 29 13:58:31 my-db kernel: Out of Memory: Killed process 9591(oracle).
However,
a) the duplicated db sga is only 500M b) total ram is 8G c) sysctl settings are identical to production machine d) I have already successfully restored another db on the machine e) init.ora is identical to the db I restored f) db sizes of duplicated dbs are roughly the same (300g) g) there seems to be a lot of 'cached' memory used when this runs, butoracle should be able to reclaim it
Subject: Rman Database Clone Terminated Unsuccessful Ora-01667 Doc ID: Note:403214.1 Type: PROBLEM Last Revision Date: 14-DEC-2006 Status: MODERATED
In this Document
Symptoms
Cause
Solution
References
This document is being delivered to you via Oracle Support's Rapid Visibility (RaV) Rapid Visibility (RaV) process, and therefore has not been subject to an independent technical review.
Applies to: Oracle Server - Enterprise Edition - Version: Oracle to
9.2.0.6
This problem can occur on any platform.
SymptomsRMAN duplicate fails opening the clone database:
RMAN-00601: fatal error in recovery manager RMAN-03004: fatal error during execution of command RMAN-10039: error encountered while polling for RPC completion onchannel clone_default
RMAN-10006: error running SQL statement: select act from x$ksusex where sid=:1 and serial=:2 RMAN-10002: ORACLE error: ORA-03113: end-of-file on communicationchannel
RMAN-03002: failure of Duplicate Db command at 12/13/2006 13:03:25 RMAN-03015: error occurred in stored script Memory Script RMAN-06136: ORACLE error from auxiliary database: ORA-01092: ORACLEinstance terminated.
.
CauseBug 4771560 OPEN RESETLOGS TERMINATES WITH ORA-1667
From the bug:
This problem was discovered during RMAN DUPLICATE when MAXDATAFILES
was set
to the actual number of datafiles.
.
The database code will expand the controlfile during file add and
increase
MAXDATAFILES if DB_FILES parameter allows it, but the recovery/open
process
won't, and will raise an ORA-1667 trying to add a tablespace, and no
slots
are available.
.
SolutionRecreate the controlfile with a higher value for MAXDATAFILES
and follow Note 360962.1 (Manual Completion of a Failed RMAN
Duplicate)to complete the duplicate process.
.
Note 360962.1 (Manual Completion of a Failed RMAN Duplicate)to
complete the duplicate process.
.
ReferencesBug 4771560 - OPEN RESETLOGS TERMINATES WITH ORA-01667
Note 360962.1 - Manual Completion of a Failed RMAN Duplicate
ErrorsORA-1092 Oracle instance terminated.
ORA-1667 cannot add any more tablespaces: limit of %s exceeded / redo
log is incompatible with standby database
ORA-3113 "end-of-file on communication channel"
RMAN-3015
RMAN-10002 ORACLE error: %s
RMAN-3002 { Message text depends on version }
RMAN-601 fatal error in recovery manager
RMAN-6136 ORACLE error from auxiliary database: %s
RMAN-10006 error running sql statement: %s
RMAN-10039 error encountered while polling for RPC completion on
channel
 |
 |