the first week when the problem starts i would look at the ora_i process. we had the excact same problem with ora_i being hung and oracle spawing more ora_i processes until the backusp became real slow and used to crawl to a halt. killing the previous ora_i processes immediately solved the issues. ----- Original Message ---- From: Terry Sutton <terrysutton@xxxxxxx> To: oracle-l@xxxxxxxxxxxxx Sent: Friday, July 7, 2006 2:01:16 PM Subject: Re: Lengthening backup SQL> SELECT DISTINCT(incremental_level) FROM rc_backup_set WHERE db_id = 435051864 AND start_time > SYSDATE -10; INCREMENTAL_LEVEL ----------------- So the incremental level is null. --Terry ----- Original Message ----- From: Allen, Brandon To: terrysutton@xxxxxxx ; oracle-l@xxxxxxxxxxxxx Sent: Friday, July 07, 2006 11:43 AM Subject: RE: Lengthening backup The only thing I can think of that would cause such behaviour is if for some reason you were actually running a cumulative incremental backup. From the script you've shown, that doesn't appear to be the case, but could you check the incremental_level of the rc_backup_set view in your recovery catalog and verify? From: oracle-l-bounce@xxxxxxxxxxxxx [mailto:oracle-l-bounce@xxxxxxxxxxxxx] On Behalf Of Terry Sutton I'm having some issues with a client's RMAN backup. They're on Oracle 184.108.40.206, Solaris 8. It's a weekly full backup, and they're backing up ~1.5TB to disk, and the longer the instance is up, the longer the backup takes. Privileged/Confidential Information may be contained in this message or attachments hereto. Please advise immediately if you or your employer do not consent to Internet email for messages of this kind. Opinions, conclusions and other information in this message that do not relate to the official business of this company shall be understood as neither given nor endorsed by it.