RMAN dump script giving ORA-01220 error [message #52725] |
Thu, 08 August 2002 05:50 ![Go to next message Go to next message](/forum/theme/orafaq/images/down.png) |
James Briar
Messages: 72 Registered: January 2002 Location: Morden (South London)
|
Member |
|
|
Our RMAN backup script is failing with "ORA-01220: file based sort illegal before database is open" ?
When logged into RMAN i get the following messages/error when i do "run { execute script Backuptest; }" :-
RMAN-01005: resync got ORA-1220, retrying with sort_area_size = 3MB
RMAN-08003: starting partial resync of recovery catalog
RMAN-01005: resync got ORA-1220, retrying with sort_area_size = 4MB
RMAN-08003: starting partial resync of recovery catalog
RMAN-01005: resync got ORA-1220, retrying with sort_area_size = 5MB
RMAN-08003: starting partial resync of recovery catalog
RMAN-01005: resync got ORA--1220, giving up
RMAN-03026: error recovery releasing channel resources
RMAN-08031: released channel: c1
RMAN-08031: released channel: c2
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03015: error occurred in stored script Backuptest
RMAN-03002: failure during compilation of command
RMAN-03013: command type: backup
RMAN-03014: implicit resync of recovery catalog failed
RMAN-03006: non-retryable error occurred during execution of command: partial re
sync
RMAN-07004: unhandled exception during command execution on channel default
RMAN-10032: unhandled exception during execution of job step 1: ORA-01220: file
based sort illegal before database is open
I'm connected to a target database called test and a RMAN database called rmandb. I've tried changing the SORT_AREA_SIZE values in both database param files but this made no difference (changed the value from 65536 in both to 10485760, i assume this is in bytes). I've not tried changing SORT_AREA_RETAINED_SIZE in each param file (currently set to 65536).
We're using Oracle 8i on a Sun Solaris 8 unix platform.
P.S - Low priority (no urgency on this).
|
|
|
|
|
Re: RMAN dump script giving ORA-01220 error [message #53585 is a reply to message #52725] |
Mon, 30 September 2002 13:35 ![Go to previous message Go to previous message](/forum/theme/orafaq/images/up.png) ![Go to next message Go to next message](/forum/theme/orafaq/images/down.png) |
Hamdy
Messages: 1 Registered: September 2002
|
Junior Member |
|
|
Hi James,
Just try one of the following solutions,may be it will help
This is an Oracle/RMAN issue. RMAN is failing when trying to perform a partial resync of the recovery catalog.
When trying to restore a whole database, the database must be mounted (but not open), so Oracle is unable to use the temporary tablespace to perform some operations, and it must use previously allocated memory. This memory allocation is done through the variables SORT_AREA_SIZE and SORT_AREA_RETAINED_SIZE in the init.ora file (initORACLE_SID.ora in fact).
you need to increase the value for SORT_AREA_RETAINED_SIZE on the TARGET database, shut it down and mount it again, then retry the restore.
Another solution is to try commenting out the SORT_AREA_RETAINED_SIZE and then retry the restore. In this case, the customer had SORT_AREA_SIZE=10M and SORT_AREA_RETAINED_SIZE=400k. When they commented out SORT_AREA_RETAINED_SIZE the catalog resync ran just fine. This caused the SORT_AREA_RETAINED_SIZE to default to the same value as SORT_AREA_SIZE, which allowed enough resources for the resync to process without any problems.
|
|
|
|