Category Archive: RMAN

May 14

ORA-01422: exact fetch returns more than requested number of rows

The other night on of my databases started throwing the following error. From the RMAN trace The solution here is actually quite simple, the rout table, which stores previous rman output from previous runs so that it can displayed in OEM had excessive rows in it. Since we don’t really use OEM to track our …

Continue reading »

Aug 31

RMAN-08137: WARNING: archived log not deleted, needed for standby or upstream capture process

On a non-production database I was getting the following error when trying to delete archive logs with RMAN.

This database does not have any golden gate processes associated with it, so why doesn’t Oracle want to delete the ¬†archive log? The database was rebuilt with a copy of a production database that did have …

Continue reading »

Aug 07

RMAN-20036: invalid record order

Trying to register a database with my rman catalog I was getting the following error

Poking around metalink I found note¬†113325.1 Basicly it says there is a mismatch in the number of standby redo logs, but this database does not have a standby. However it was cloned from a database that had a standby, …

Continue reading »

Jun 08

Rushing = Stupid Mistakes

I am currently being asked to refresh a database. The end users are pissed because they asked for the database to be refreshed at noon yesterday, this was the first they had asked for it, and they were doing “really important things” and by 3pm were pissed that I hadn’t responded to them, let alone …

Continue reading »