ORA-01455 :CONVERTING VOLUMN OVERFLOWS

[liv176]

HI,
CAN YOU HELP ME? Oracle 10g
I have tried to make 'RESTORE DATABASE' but the result was :
RMAN-03002;failure of recover command at 03/1272009 14:08:40
ORA-1455:converting column overflows integer datatype
RMAN-06031;could not translate database keyword.

Can you help me?
Thanks
n.b. I already make a restore dei controlfile.

 

[Turkbear]

Hi,
This was posted on a French tech forum ( By a Marc Musette )and may be what is happening to you.

reported as bug on metalink 

Problem: Problem: 
~~~~~~~~ ~~~~~~~~ 
Issuing List Backup set or Report Obsolete against the Recovery Catalog Database Issuing List Backup Report set or Obsolete against the Recovery Catalog Database 
returns the following: returns the following: 
RMAN-6004: ORACLE error from recovery catalog database: ORA-1455: converting column overflows integer datatype RMAN-6004: ORACLE error from recovery catalog database: ORA-1455: converting column overflows integer datatype 

You are hitting this bug only if RMAN_SEQ in the recovery catalog is bigger than UB4MAXVAL (usually 2^32 - 1, or 4,294,967,295) You are hitting this bug only if RMAN_SEQ in the recovery catalog is bigger than UB4MAXVAL (usually 2 ^ 32 - 1, or 4294967295) 
SQL> select rman_seq.nextval from dual ; SQL> select rman_seq.nextval from dual; 
. . 
NEXTVAL Nextval 
---------- ---------- 
6000000179 6000000179 


Workarounds: Workarounds: 
~~~~~~~~~~~~ ~~~~~~~~~~~~ 
Start over by creating a brand-new recovery catalog, and register all of your target databases again. Start over by creating a brand-new recovery catalog, and register all of your target databases again. 
That will capture whatever recovery metadata is still in the controlfiles of those target databases. That will capture whatever recovery metadata is still in the target controlfile of those databases. 
In the meantime, you may be able to use the "nocatalog" option, assuming that the metadata you need In the meantime, you may be able to use the "nocatalog" option, assuming that the metadata you need 
is still in the controlfile, and within the keep time that is set by the init.ora parameter called is still in the controlfile, and keep within the time that is set by the parameter called INIT.ORA 
CONTROL_FILE_RECORD_KEEP_TIME. CONTROL_FILE_RECORD_KEEP_TIME. 
__________________ __________________ 
*** Oracle RAC Certified Expert *** *** Oracle RAC Certified Expert *** 
*** OCP DBA 9i-10g-11g *** *** OCP DBA 9i-10g-11g *** 
*** OCA iAS 10g *** OCA 10g iAS *** ***

This is the URL from the Translated Google result (

http://translate.google.com/transla...+%22+RMAN&hl=en&lr=&safe=off&sa=G&as_qdr=all)

To Paraphrase:"The Help you get is proportional to the Help you give.."

 

[karluk]

I also see some references that this error can be caused by rman trying to manage a datafile that is bigger than some upper limit, usually 4GB. The suggested workaround is to try restoring individual datafiles, instead of the entire database, and only doing the recovery after all files are restored. I guess the idea is that you are breaking the restore into smaller pieces, which rman may be able to handle without exceeding a limit.

So, your recovery script would look something like

restore datafile 1;
restore datafile 2;
restore datafile 3;
.
.
.
recover database;

There's no guarantee it will work, but I would give it a try. If it doesn't work, you should contact Oracle support for advice. They are really good with database recoveries - I've seen them do successful recoveries on databases that seemed irretrievably lost.