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 …
Category Archive: RMAN
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. RMAN-08137: WARNING: archived log not deleted, needed for standby or upstream capture process archived log file name=+RECO/DBP1/ARCHIVELOG/2017_05_07/thread_1_seq_32041.11548.943352263 thread=1 sequence=32041 This database does not have any golden gate processes associated with it, so why doesn’t Oracle want to …
Aug 07
RMAN-20036: invalid record order
Trying to register a database with my rman catalog I was getting the following error $ rman target sys/xxx@DB01 catalog=RMAN_DB01/xxx@rmancat Recovery Manager: Release 11.2.0.4.0 – Production on Mon Aug 7 11:42:37 2017 Copyright (c) 1982, 2011, Oracle and/or its affiliates. All rights reserved. connected to target database: DB01 (DBID=114156133) connected to recovery catalog database RMAN> …
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 …
Recent Comments