This morning a user came to me because they were getting what appeared to be a Permission error FLASHBACK automatically enabled to preserve database integrity. Starting “myschema”.”SYS_EXPORT_SCHEMA_06″: Estimate in progress using BLOCKS method… Processing object type SCHEMA_EXPORT/TABLE/TABLE_DATA Total estimation using BLOCKS method: 252.1 GB ORA-31693: Table data object “myschema”.”mytable” failed to load/unload and is being …
Monthly Archive: August 2017
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 31
ORA-02396: exceeded maximum idle time, please connect again
I was doing a schema import last night, over a database link. Lack of sleep had set in and I was getting the following error Processing object type SCHEMA_EXPORT/TABLE/INDEX/INDEX ORA-39126: Worker unexpected fatal error in KUPW$WORKER.FETCH_XML_OBJECTS [INDEX:”SCHEMA_OWNER”.”TABLE2″] ORA-02396: exceeded maximum idle time, please connect again ORA-06512: at “SYS.DBMS_SYS_ERROR”, line 95 ORA-06512: at “SYS.KUPW$WORKER”, line 11259 …
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> …
Recent Comments