RMAN-06428 recovery catalog is not installed

RDBMS Version: 8.1.6
Operating System and Version: sun sparc 5.8
Error : RMAN-06428 RMAN-06428 recovery catalog is not installed
Product (i.e. SQL*Loader, Import, etc.): RMAN
Product Version: 8.1.6
Hi,
I hv a database running in unix box 1 (say 'FAST')
and Im trying to install a recovery catalog database in unix box
2
(Rcat)
1) in unixbox2..I hv created a new database, and I hv created a
tablespace rcvcat and user rman .granted catalog_recovery_owner
to rman.
also I hv created a catalogue using this command
create catalogue tablespace rcvcat;
(no error logs generated)
2)now when I try to connect to the catalogue I am getting an
error
what I did is, I tried connecting to rman of target database
(FAST database)
% rman target /catalog rman/rman@rcat
Recovery Manager: Release 8.1.6.0.0 - Production
RMAN-06005: connected to target database: FAST (DBID=3819569154)
RMAN-06008: connected to recovery catalog database
RMAN-06428: recovery catalog is not installed
also I tried like this,
% rman target system/manager@fast catalog rman/rman@rcat
Recovery Manager: Release 8.1.6.0.0 - Production
RMAN-06005: connected to target database: FAST (DBID=3819569154)
RMAN-06008: connected to recovery catalog database
RMAN-06428: recovery catalog is not installed
I dont understand why it says recovery catalog not installed ,
when I hv created one in rcat database.
Can anyone help me how to connect to catalog and register my
database (I mean from which machine I need to run the commands)
Thanks
Venkat

You do have a problem. It seems your "Shift" key is stuck.
Anyway, please read: [ID 188682.1],
Have a nice day.

Similar Messages

Backup policy on Grid, using RMAN and Recovery Catalog.

Hello Gurus,
I'm trying to move ahead the new features of Oracle 10g in my company. So I've already created Grid Control and will deploy Agents/Targets during the next week. I also want to switch the backup process from the archaic exp/imp to RMAN with the Recovery Catalog.
My question is such: could anybody suggest the best book or text with solutions and descriptions of backup policy, using the Grid, RMAN and Catalog? What I want to do is to create eventually the powerful and centralized storage of every database in a company and do all daily routine from there. But as long as I'm only in the very beginning I want to gain some knowledge before the bad experience, like crashed recovery catalog and no backups for all databases :-)))
Definitely I'll keep existing imp/exp and hotbackup for a long time. I'm not going to substitute all our backup strategy with one catalog. I just want to understand what will be the best practice in the backup perspective.
And at all, I wonder if you please could give me very brief answer to this question: Let's say I have a huge monster with 5 disks by 500Gb RAD0+1. Is it a bad idea to store all of them in one physical machine before they will tape to backup or it could make sense? For me it sounds a bit scary, but probably if all made with the brain it's not a bad idea?
Please, send me to some valuable and good source (like Tom Kyte or Don Burleson) Unfortunately, I didn't find anything regard the backups itself. Only pretty much general thought.
Thanks a lot in advance.
M.

great!
thanks a lot!
this is definitely valuable info and I'll read right away. but as far as understand they suggest to use Data Guard, Standby and RAC which are the best ways to prevent your environment from crash. But in reality (I mean in my company) nobody is going to move to RAC at this point and I'm not sure, that they will have a chance to do in the next year. they just aren't up to it.
what I'm looking for is probably some tips and hints about backups in more or less big environment, but not as big as Oracle itself :-) unfortunately, i'm the only DBA in my surrounding. i mean, i have no friends or mentors DBAs that could seat with me in a pub and pass theirs knowledge from generation to generation :-)))
but anyway, I'll devote this week-end to this link.
thanks a lot!

Switching RMAN from Recovery Catalog DB to target db controlfile

I have a doubt.
Is it possible to make RMAN to use controlfile, from using Recovery Catalog(RC) DB ?
The scenario is like this:
I have a target db and a RC db. The RMAN presently uses RC db for backup and recovery.
Due to some reasons, I want the RMAN to use target db controlfile, instead of RC.
Is there anyway to perform this?
If yes, I need the RMAN to understand and use backup sets, which are taken before switching to controlfile based backup (That is, controlfile should understand backup sets, which have backed-up using RC )
Is there a way to perform these tasks?

Hi,
The rman backup information in the controlfile has a limitation due to space constraints in the controlfile.
Oracle uses the parameter "control_file_record_keep_time" which defaults to 7 days to purge rman backup information from the controlfile. (So if you run rman backups the backup information in the controlfile will be automaticly purged.)
If you run rman using a catalog the controlfile will synchronize new informaton to the catalog at the start of every backup but it won't actively purge information from the catalog. So the catalog (next to other features) has the ability to store information longer than the controlfile. (Delete commands will be needed to purge information from the catalog.)
Due to some reasons, I want the RMAN to use target db controlfile, instead of RC.
Is there anyway to perform this?Just skip the connect to the catalog in your script.
If yes, I need the RMAN to understand and use backup sets, which are taken before switching to controlfile based backup > (That is, controlfile should understand backup sets, which have backed-up using RC )This is not easy to answer, your restore might work if the backup information is still available in the controlfile (younger than control_file_record_keep_time). Success is not related to the fact the backup was taken with the controlfile and RC at the same time.
Regards,
Tycho

Palm pixi plus app catalog will not install

I just actived my verizon pixi plus last week and I am not able to download and/or install apps from my app catalog, really would like a solution.

Try the instructions here for updating the App Catalog:
http://h30434.www3.hp.com/t5/webOS-Hardware-and-Software/App-Catalog-not-working-Missed-the-update-T...
smkranz
I am a volunteer, and not an HP employee.
Palm OS ∙ webOS ∙ Android

RMAN is not installed error although it's been already installed

Hi everyone,
My OS: Win 2008 x64 R2 Enterprise
Oracle; 11.2.0.2.0 64bit Enterprise
When I try to backup through Symantec Backup Exec , it returns the following error;
Recovery Manager: Release 11.2.0.2.0 - Production on Tue Feb 26 23:03:49 2013
Copyright (c) 1982, 2009, Oracle and/or its affiliates. All rights reserved.
connected to target database: KP0 (DBID=4283758981)
connected to recovery catalog database
*# RMAN command section*
*RUN {*
ALLOCATE CHANNEL ch0
TYPE 'SBT_TAPE';
*SEND 'BSA_SERVICE_HOST=BCKPSRVR00,NBBSA_TOTAL_STREAMS=1,NBBSA_JOB_COOKIE={D3774FE4-845A-4FD2-9BD9-4D98086B9BCA},NBBSA_DB_DEVICE_NAME=Oracle-Win::\\saperpprd0\KP0';*
BACKUP
INCREMENTAL LEVEL=0
FORMAT 'BE_U'
DATABASE FORCE PLUS ARCHIVELOG FORCE;
BACKUP CURRENT CONTROLFILE
FORMAT 'BE_U';
RELEASE CHANNEL ch0;
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of allocate command at 02/26/2013 23:03:51
RMAN-06428: recovery catalog is not installed
EXIT
Recovery Manager complete.
But I have already installed the recovery catalog by the following procedure and every command in the procedure altered successfully;
SQL>CREATE TABLESPACE RMAN
DATAFILE 'E:\oracle\KP0\sapdata1\rman\RMAN01.DATA1'
SIZE 200M REUSE AUTOEXTEND ON EXTENT MANAGEMENT LOCAL SEGMENT SPACE MANAGEMENT AUTO;
SQL>CREATE USER RMAN IDENTIFIED BY RMAN TEMPORARY TABLESPACE PSAPTEMP DEFAULT TABLESPACE RMAN QUOTA UNLIMITED ON RMAN;
SQL>GRANT RECOVERY_CATALOG_OWNER TO RMAN;
SQL>GRANT CONNECT, RESOURCE TO RMAN;
C:\USERS\KP0ADM>RMAN
RMAN>CONNECT CATALOG RMAN/RMAN@KP0
RMAN>CREATE CATALOG TABLESPACE 'RMAN';
C:\USERS\KP0ADM>RMAN TARGET System@KP0 CATALOG RMAN/RMAN@KP0
RMAN>REGISTER DATABASE;
RMAN>SQL "ALTER SYSTEM ARCHIVE LOG CURRENT";
RMAN>RESYNC CATALOG;
RMAN>CROSSCHECK COPY OF ARCHIVELOG ALL;
By the way, this database has been opened with RESETLOGS option in Feb 2012 and the incarnation list is like below;
RMAN> list incarnation;
List of Database Incarnations
DB Key Inc Key DB Name DB ID STATUS Reset SCN Reset Time
*1 129 KP0 4283758981 PARENT 1 05-OCT-11*
*1 2 KP0 4283758981 CURRENT 125827000 01-FEB-12*
I've already shut the database down and open it again after installing the recovery catalog , also related oracle services as well...
Could it be a bug with the version 11.2.0.2.0 which I currently use ?
Or what could be the solution ?
Thanks in advance...

Hi,
Here is the result of the select;
SQL> SELECT TABLE_NAME FROM USER_TABLES;
TABLE_NAME
UNDO$
USER$
TSQ$
UET$
SEG$
CCOL$
CDEF$
TS$
FET$
BOOTSTRAP$
ICOL$
TABLE_NAME
IND$
COL$
CLU$
TAB$
LOB$
COLTYPE$
SUBCOLTYPE$
NTAB$
REFCON$
OPQTYPE$
ICOLDEP$
TABLE_NAME
VIEWTRCOL$
LIBRARY$
ASSEMBLY$
ATTRCOL$
TYPE_MISC$
PROXY_DATA$
PROXY_ROLE_DATA$
CON$
FILE$
OBJ$
OBJERROR$
TABLE_NAME
OBJAUTH$
UGROUP$
SYN$
VIEW$
TYPED_VIEW$
SUPEROBJ$
SEQ$
PROPS$
EDITION$
FIXED_OBJ$
MIGRATE$
TABLE_NAME
DEPENDENCY$
ACCESS$
VIEWCON$
DUAL
SYSAUTH$
OBJPRIV$
DEFROLE$
ECOL$
EV$
EVCOL$
DEFERRED_STG$
TABLE_NAME
SQLERROR$
LINK$
TRUSTED_LIST$
COM$
DUC$
RECYCLEBIN$
IND_ONLINE$
CONTEXT$
SQL_VERSION$
JIJOIN$
JIREFRESHSQL$
TABLE_NAME
TRIGGER$
TRIGGERCOL$
TRIGGERJAVAF$
TRIGGERJAVAS$
TRIGGERJAVAC$
TRIGGERJAVAM$
TRIGGERDEP$
INDREBUILD$
COMPRESSION$
TRANSIENT_IOT$
SMB$CONFIG
TABLE_NAME
SQL$
SQL$TEXT
SQLOBJ$AUXDATA
OBJECT_USAGE
PROCEDURE$
PROCEDUREINFO$
ARGUMENT$
SOURCE$
IDL_UB1$
IDL_CHAR$
IDL_UB2$
TABLE_NAME
IDL_SB4$
ERROR$
SETTINGS$
NCOMP_DLL$
PROCEDUREJAVA$
PROCEDUREC$
PROCEDUREPLSQL$
WARNING_SETTINGS$
DIANA_VERSION$
PLSCOPE_IDENTIFIER$
PLSCOPE_ACTION$
TABLE_NAME
PENDING_TRANS$
PENDING_SESSIONS$
PENDING_SUB_SESSIONS$
SMON_SCN_TIME
MAP_FILE$
MAP_FILE_EXTENT$
MAP_SUBELEMENT$
MAP_ELEMENT$
MAP_EXTELEMENT$
MAP_COMPLIST$
PROFILE$
TABLE_NAME
PROFNAME$
RESOURCE_COST$
JOB$
RESOURCE_MAP
USER_ASTATUS_MAP
RESOURCE_PLAN$
RESOURCE_CONSUMER_GROUP$
RESOURCE_CATEGORY$
RESOURCE_PLAN_DIRECTIVE$
RESOURCE_GROUP_MAPPING$
RESOURCE_MAPPING_PRIORITY$
TABLE_NAME
RESOURCE_STORAGE_POOL_MAPPING$
RESOURCE_CAPABILITY$
RESOURCE_INSTANCE_CAPABILITY$
RESOURCE_IO_CALIBRATE$
TSM_SRC$
TSM_DST$
SERVICE$
DIR$MIGRATE_OPERATIONS
DIR$SERVICE_OPERATIONS
DIR$ESCALATE_OPERATIONS
DIR$QUIESCE_OPERATIONS
TABLE_NAME
DIR$INSTANCE_ACTIONS
DIR$RESONATE_OPERATIONS
DIR$ALERT_HISTORY
DIR$REASON_STRINGS
DIR$DATABASE_ATTRIBUTES
DIR$VICTIM_POLICY
DIR$NODE_ATTRIBUTES
DIR$SERVICE_ATTRIBUTES
defaultauditing_options_*
AUDIT$
SYSTEM_PRIVILEGE_MAP
TABLE_NAME
TABLE_PRIVILEGE_MAP
STMT_AUDIT_OPTION_MAP
USER_HISTORY$
RLS$
RLS_SC$
RLS_GRP$
RLS_CTX$
AUD$
FGA$
FGACOL$
FGA_LOG$
TABLE_NAME
APPROLE$
ENC$
PROXY_INFO$
PROXY_ROLE_INFO$
XS$VERIFIERS
XS$SESSIONS
XS$SESSION_ROLES
XS$SESSION_APPNS
XS$PARAMETERS
DEFAULT_PWD$
HISTGRM$
TABLE_NAME
HIST_HEAD$
AUX_STATS$
TAB_STATS$
IND_STATS$
CACHE_STATS_1$
CACHE_STATS_0$
ASSOCIATION$
USTATS$
STATS_TARGET$
COL_USAGE$
MON_MODS$
TABLE_NAME
MON_MODS_ALL$
WRI$_OPTSTAT_TAB_HISTORY
WRI$_OPTSTAT_IND_HISTORY
WRI$_OPTSTAT_HISTHEAD_HISTORY
WRI$_OPTSTAT_HISTGRM_HISTORY
WRI$_OPTSTAT_AUX_HISTORY
WRI$_OPTSTAT_OPR
OPTSTAT_HIST_CONTROL$
OPTSTAT_USER_PREFS$
DIR$
ID_GENS$
TABLE_NAME
OID$
TYPE$
COLLECTION$
ATTRIBUTE$
METHOD$
PARAMETER$
RESULT$
TYPEHIERARCHY$
KOPM$
VTABLE$
OPBINDING$
TABLE_NAME
OPANCILLARY$
OPARG$
OPERATOR$
INDTYPES$
INDOP$
INDARRAYTYPE$
SECOBJ$
JAVAOBJ$
JAVASNM$
PARTOBJ$
PARTCOL$
TABLE_NAME
TABPART$
INDPART$
SUBPARTCOL$
TABSUBPART$
INDSUBPART$
TABCOMPART$
INDCOMPART$
PARTLOB$
LOBFRAG$
LOBCOMPPART$
DEFSUBPART$
TABLE_NAME
DEFSUBPARTLOB$
INDPART_PARAM$
INSERT_TSN_LIST$
SUMPARTLOG$
SUMDELTA$
SNAP_LOGDEP$
SNAP_LOADERTIME$
MLOG$
SLOG$
SNAP_XCMT$
SNAP$
TABLE_NAME
SNAP_REFTIME$
MLOG_REFCOL$
SNAP_REFOP$
SNAP_COLMAP$
SNAP_OBJCOL$
REG_SNAP$
SNAP_SITE$
RGROUP$
RGCHILD$
CDC_SYSTEM$
CDC_CHANGE_SOURCES$
TABLE_NAME
CDC_CHANGE_SETS$
CDC_CHANGE_TABLES$
CDC_SUBSCRIBERS$
CDC_SUBSCRIBED_TABLES$
CDC_SUBSCRIBED_COLUMNS$
CDC_CHANGE_COLUMNS$
CDC_PROPAGATIONS$
CDC_PROPAGATED_SETS$
STREAMS$_SPLIT_MERGE
STREAMS$_CAPTURE_SERVER
STREAMS$_CAPTURE_PROCESS
TABLE_NAME
STREAMS$_APPLY_PROCESS
STREAMS$_PROPAGATION_PROCESS
STREAMS$_PROCESS_PARAMS
STREAMS$_EXTRA_ATTRS
STREAMS$_PREPARE_OBJECT
STREAMS$_PREPARE_DDL
STREAMS$_APPLY_MILESTONE
STREAMS$_APPLY_PROGRESS
STREAMS$_KEY_COLUMNS
STREAMS$_DEF_PROC
STREAMS$_RULES
TABLE_NAME
APPLY$_SOURCE_OBJ
APPLY$_SOURCE_SCHEMA
APPLY$_VIRTUAL_OBJ_CONS
APPLY$_CONSTRAINT_COLUMNS
APPLY$_DEST_OBJ
APPLY$_DEST_OBJ_CMAP
APPLY$_DEST_OBJ_OPS
STREAMS$_STMT_HANDLERS
STREAMS$_STMT_HANDLER_STMTS
APPLY$_CHANGE_HANDLERS
APPLY$_ERROR
TABLE_NAME
APPLY$_ERROR_TXN
APPLY$_ERROR_HANDLER
APPLY$_CONF_HDLR_COLUMNS
STREAMS$_DEST_OBJS
STREAMS$_DEST_OBJ_COLS
STREAMS$_PRIVILEGED_USER
STREAMS$_MESSAGE_RULES
STREAMS$_MESSAGE_CONSUMERS
STREAMS$_APPLY_SPILL_TXN
STREAMS$_APPLY_SPILL_TXN_LIST
FGR$_FILE_GROUPS
TABLE_NAME
FGR$_FILE_GROUP_VERSIONS
FGR$_FILE_GROUP_EXPORT_INFO
FGR$_FILE_GROUP_FILES
FGR$_TABLESPACE_INFO
FGR$_TABLE_INFO
REDEF$
REDEF_OBJECT$
REDEF_DEP_ERROR$
RULESET$
LOG$
RECO_SCRIPT$
TABLE_NAME
RECO_SCRIPT_PARAMS$
RECO_SCRIPT_BLOCK$
RECO_SCRIPT_ERROR$
COMPARISON$
COMPARISON_COL$
COMPARISON_SCAN$
COMPARISON_SCAN_VAL$
COMPARISON_ROW_DIF$
STREAMS$_COMPONENT
STREAMS$_COMPONENT_LINK
STREAMS$_COMPONENT_PROP
TABLE_NAME
STREAMS$_DATABASE
XSTREAM$_SERVER
XSTREAM$_SUBSET_RULES
XSTREAM$_SYSGEN_OBJS
XSTREAM$_PARAMETERS
XSTREAM$_DML_CONFLICT_HANDLER
XSTREAM$_SERVER_CONNECTION
XSTREAM$_DDL_CONFLICT_HANDLER
XSTREAM$_MAP
GOLDENGATE$_PRIVILEGES
AW$
TABLE_NAME
PS$
AW_OBJ$
AW_PROP$
AW_TRACK$
AW_PRG$
OLAP_MAPPINGS$
OLAP_MODELS$
OLAP_MODEL_PARENTS$
OLAP_MODEL_ASSIGNMENTS$
OLAP_CALCULATED_MEMBERS$
OLAP_SYNTAX$
TABLE_NAME
OLAP_DESCRIPTIONS$
OLAP_CUBE_BUILD_PROCESSES$
OLAP_AW_VIEWS$
OLAP_AW_VIEW_COLUMNS$
OLAP_MEASURE_FOLDERS$
OLAP_MEAS_FOLDER_CONTENTS$
OLAP_AW_DEPLOYMENT_CONTROLS$
OLAP_IMPL_OPTIONS$
OLAP_MULTI_OPTIONS$
OLAP_CUBE_DIMENSIONS$
OLAP_DIM_LEVELS$
TABLE_NAME
OLAP_ATTRIBUTES$
OLAP_ATTRIBUTE_VISIBILITY$
OLAP_HIERARCHIES$
OLAP_HIER_LEVELS$
OLAP_CUBES$
OLAP_MEASURES$
OLAP_DIMENSIONALITY$
OLAP_TAB$
OLAP_TAB_COL$
OLAP_TAB_HIER$
SUM$
TABLE_NAME
SUMDETAIL$
SUMINLINE$
SUMKEY$
SUMAGG$
SUMJOIN$
SUMDEP$
SUMPRED$
SUMQB$
HIER$
HIERLEVEL$
DIM$
TABLE_NAME
DIMLEVEL$
DIMLEVELKEY$
DIMJOINKEY$
DIMATTR$
INCEXP
INCVID
INCFIL
EXPACT$
NOEXP$
EXPPKGOBJ$
EXPPKGACT$
TABLE_NAME
EXPDEPOBJ$
EXPDEPACT$
EXPIMP_TTS_CT$
METAVIEW$
METAFILTER$
METAXSL$
METAXSLPARAM$
METASTYLESHEET
METASCRIPT$
METASCRIPTFILTER$
METANAMETRANS$
TABLE_NAME
METAPATHMAP$
EXTERNAL_TAB$
EXTERNAL_LOCATION$
MODEL$
MODELTAB$
MODELATT$
MODELSET$
LOGMNR_BUILDLOG
LOGMNRG_SEED$
LOGMNRG_DICTIONARY$
LOGMNRG_OBJ$
TABLE_NAME
LOGMNRG_TAB$
LOGMNRG_COL$
LOGMNRG_ATTRCOL$
LOGMNRG_TS$
LOGMNRG_IND$
LOGMNRG_USER$
LOGMNRG_TABPART$
LOGMNRG_TABSUBPART$
LOGMNRG_TABCOMPART$
LOGMNRG_TYPE$
LOGMNRG_COLTYPE$
TABLE_NAME
LOGMNRG_ATTRIBUTE$
LOGMNRG_LOB$
LOGMNRG_CDEF$
LOGMNRG_CCOL$
LOGMNRG_ICOL$
LOGMNRG_LOBFRAG$
LOGMNRG_INDPART$
LOGMNRG_INDSUBPART$
LOGMNRG_INDCOMPART$
LOGMNRG_LOGMNR_BUILDLOG
LOGMNRG_NTAB$
TABLE_NAME
LOGMNRG_OPQTYPE$
LOGMNRG_SUBCOLTYPE$
LOGMNRG_KOPM$
LOGMNRG_PROPS$
LOGMNRG_ENC$
LOGMNRG_REFCON$
LOGMNRG_PARTOBJ$
DST$AFFECTED_TABLES
DST$ERROR_TABLE
DST$TRIGGER_TABLE
SYS_FBA_FA
TABLE_NAME
SYS_FBA_TSFA
SYS_FBA_BARRIERSCN
SYS_FBA_TRACKEDTABLES
SYS_FBA_PARTITIONS
SYS_FBA_USERS
SYS_FBA_DL
REGISTRY$
REGISTRY$SCHEMAS
REGISTRY$LOG
REGISTRY$ERROR
REGISTRY$HISTORY
TABLE_NAME
REGISTRY$PROGRESS
REGISTRY$DEPENDENCIES
REGISTRY$DATABASE
AUDIT_ACTIONS
WRI$_SEGADV_OBJLIST
WRI$_SEGADV_CNTRLTAB
WRI$_REPT_COMPONENTS
WRI$_REPT_REPORTS
WRI$_REPT_FILES
WRI$_REPT_FORMATS
TRANSACTION_BACKOUT_STATE$
TABLE_NAME
TRANSACTION_BACKOUT_REPORT$
UTL_RECOMP_SORTED
UTL_RECOMP_COMPILED
UTL_RECOMP_ERRORS
TRANSFORMATIONS$
ATTRIBUTE_TRANSFORMATIONS$
RULE_SET_IEUAC$
RULE_SET$
RULE$
RULE_MAP$
RULE_EC$
TABLE_NAME
REC_TAB$
REC_VAR$
RULE_SET_EE$
RULE_SET_TE$
RULE_SET_VE$
RULE_SET_RE$
RULE_SET_ROR$
RULE_SET_FOB$
RULE_SET_NL$
SYS_IOT_OVER_5229
RULE_SET_RDEP$
TABLE_NAME
SYS_IOT_OVER_5235
SYS_IOT_OVER_5239
DAM_PARAM_TAB$
DAM_CONFIG_PARAM$
DAM_LAST_ARCH_TS$
DAM_CLEANUP_JOBS$
DAM_CLEANUP_EVENTS$
INVALIDATION_REGISTRY$
SYS_IOT_OVER_5476
CHNF$_CLAUSE_DEPENDENTS
CHNF$_QUERY_OBJECT
TABLE_NAME
CHNF$_REG_QUERIES
CHNF$_QUERIES
CHNF$_QUERY_BINDS
SYS_IOT_OVER_5511
CHNF$_QUERY_DEPENDENCIES
CHNFDIRECTLOAD$
CPOOL$
SSCR_CAP$
SSCR_RES$
REG$
LOC$
TABLE_NAME
AQ$_REPLAY_INFO
AQ$_QUEUE_TABLE_AFFINITIES
AQ$_SUBSCRIBER_TABLE
AQ$_SCHEDULES
AQ$_MESSAGE_TYPES
AQ$_PROPAGATION_STATUS
AQ$_PENDING_MESSAGES
AQ$_QUEUE_STATISTICS
AQ$_PUBLISHER
SYS_IOT_OVER_5779
WRI$_ADV_DEFINITIONS
TABLE_NAME
WRI$_ADV_DEF_PARAMETERS
WRI$_ADV_DEF_EXEC_TYPES
WRI$_ADV_TASKS
WRI$_ADV_PARAMETERS
WRI$_ADV_EXECUTIONS
WRI$_ADV_EXEC_PARAMETERS
WRI$_ADV_OBJECTS
WRI$_ADV_FINDINGS
WRI$_ADV_INST_FDG
WRI$_ADV_RECOMMENDATIONS
WRI$_ADV_ACTIONS
TABLE_NAME
WRI$_ADV_RATIONALE
WRI$_ADV_REC_ACTIONS
WRI$_ADV_DIRECTIVE_DEFS
WRI$_ADV_DIRECTIVE_META
WRI$_ADV_DIRECTIVE_INSTANCES
WRI$_ADV_JOURNAL
WRI$_ADV_MESSAGE_GROUPS
WRI$_ADV_SQLT_PLAN_HASH
WRI$_ADV_SQLT_PLAN_STATS
WRI$_ADV_SQLT_PLANS
WRI$_ADV_USAGE
TABLE_NAME
WRI$_ADV_ADDM_TASKS
WRI$_ADV_ADDM_INST
WRI$_ADV_ADDM_FDG
SCHEDULER$_PROGRAM
SCHEDULER$_CLASS
SCHEDULER$_JOB
SCHEDULER$_SAVED_OIDS
SCHEDULER$_LWJOB_OBJ
SCHEDULER$_LIGHTWEIGHT_JOB
SCHEDULER$_JOB_ARGUMENT
SCHEDULER$_WINDOW
TABLE_NAME
SCHEDULER$_PROGRAM_ARGUMENT
SCHEDULER$_SRCQ_INFO
SCHEDULER$_SRCQ_MAP
SCHEDULER$_EVTQ_SUB
SCHEDULER$_EVENT_LOG
SCHEDULER$_JOB_RUN_DETAILS
SCHEDULER$_WINDOW_DETAILS
SCHEDULER$_WINDOW_GROUP
SCHEDULER$_WINGRP_MEMBER
SCHEDULER$_SCHEDULE
SCHEDULER$_CHAIN
TABLE_NAME
SCHEDULER$_STEP
SCHEDULER$_STEP_STATE
SCHEDULER$_GLOBAL_ATTRIBUTE
SCHEDULER$_CREDENTIAL
SCHEDULER$_RJOB_SRC_DB_INFO
SCHEDULER$_REMOTE_DBS
SCHEDULER$_REMOTE_JOB_STATE
SCHEDULER$_FILE_WATCHER
SCHEDULER$_FILEWATCHER_HISTORY
SCHEDULER$_FILEWATCHER_RESEND
SCHEDULER$_NOTIFICATION
TABLE_NAME
SCHEDULER$_DESTINATIONS
SCHEDULER$_JOB_DESTINATIONS
KU_NOEXP_TAB
KU_UTLUSE
CRC$_RESULT_CACHE_STATS
WRI$_DBU_FEATURE_USAGE
WRI$_DBU_FEATURE_METADATA
WRI$_DBU_HIGH_WATER_MARK
WRI$_DBU_HWM_METADATA
WRI$_DBU_USAGE_SAMPLE
WRI$_DBU_CPU_USAGE
TABLE_NAME
WRI$_DBU_CPU_USAGE_SAMPLE
WRI$_ALERT_OUTSTANDING
WRI$_ALERT_HISTORY
WRI$_ALERT_THRESHOLD
WRI$_ALERT_THRESHOLD_LOG
KET$_AUTOTASK_STATUS
KET$_CLIENT_CONFIG
KET$_CLIENT_TASKS
WRI$_TRACING_ENABLED
WRI$_AGGREGATION_ENABLED
WRI$_ADV_SQLT_BINDS
TABLE_NAME
WRI$_ADV_SQLT_STATISTICS
WRI$_ADV_SQLT_RTN_PLAN
WRI$_SQLSET_DEFINITIONS
WRI$_SQLSET_REFERENCES
WRI$_SQLSET_STATEMENTS
WRI$_SQLSET_PLANS
WRI$_SQLSET_STATISTICS
WRI$_SQLSET_MASK
WRI$_SQLSET_PLAN_LINES
WRI$_SQLSET_BINDS
WRI$_SQLSET_WORKSPACE
TABLE_NAME
WRI$_SQLSET_WORKSPACE_PLANS
WRI$_SQLMON_USAGE
WRH$_FILESTATXS_BL
WRH$_TEMPSTATXS
WRH$_DATAFILE
WRH$_TEMPFILE
WRH$_COMP_IOSTAT
WRH$_IOSTAT_FUNCTION
WRH$_IOSTAT_FUNCTION_NAME
WRH$_IOSTAT_FILETYPE
WRH$_IOSTAT_FILETYPE_NAME
TABLE_NAME
WRH$_IOSTAT_DETAIL
WRH$_SQLSTAT_BL
WRH$_SQLTEXT
WRI$_SQLTEXT_REFCOUNT
WRH$_SQL_SUMMARY
WRH$_SQL_PLAN
WRH$_SQL_BIND_METADATA
WRH$_OPTIMIZER_ENV
WRH$_SYSTEM_EVENT_BL
WRH$_EVENT_NAME
WRH$_LATCH_NAME
TABLE_NAME
WRH$_BG_EVENT_SUMMARY
WRH$_WAITSTAT_BL
WRH$_ENQUEUE_STAT
WRH$_LATCH_BL
WRH$_LATCH_CHILDREN_BL
WRH$_LATCH_PARENT_BL
WRH$_LATCH_MISSES_SUMMARY_BL
WRH$_EVENT_HISTOGRAM_BL
WRH$_MUTEX_SLEEP
WRH$_LIBRARYCACHE
WRH$_DB_CACHE_ADVICE_BL
TABLE_NAME
WRH$_BUFFER_POOL_STATISTICS
WRH$_ROWCACHE_SUMMARY_BL
WRH$_SGA
WRH$_SGASTAT_BL
WRH$_PGASTAT
WRH$_PROCESS_MEMORY_SUMMARY
WRH$_RESOURCE_LIMIT
WRH$_SHARED_POOL_ADVICE
WRH$_STREAMS_POOL_ADVICE
WRH$_SQL_WORKAREA_HISTOGRAM
WRH$_PGA_TARGET_ADVICE
TABLE_NAME
WRH$_SGA_TARGET_ADVICE
WRH$_MEMORY_TARGET_ADVICE
WRH$_MEMORY_RESIZE_OPS
WRH$_INSTANCE_RECOVERY
WRH$_JAVA_POOL_ADVICE
WRH$_THREAD
WRH$_SYSSTAT_BL
WRH$_SYS_TIME_MODEL_BL
WRH$_OSSTAT_BL
WRH$_PARAMETER_BL
WRH$_MVPARAMETER_BL
TABLE_NAME
WRH$_STAT_NAME
WRH$_OSSTAT_NAME
WRH$_PARAMETER_NAME
WRH$_PLAN_OPERATION_NAME
WRH$_PLAN_OPTION_NAME
WRH$_SQLCOMMAND_NAME
WRH$_TOPLEVELCALL_NAME
WRH$_UNDOSTAT
WRH$_SEG_STAT_BL
WRH$_SEG_STAT_OBJ
WRH$_METRIC_NAME
TABLE_NAME
WRH$_SYSMETRIC_HISTORY
WRH$_SYSMETRIC_SUMMARY
WRH$_SESSMETRIC_HISTORY
WRH$_FILEMETRIC_HISTORY
WRH$_WAITCLASSMETRIC_HISTORY
WRH$_DLM_MISC_BL
WRH$_CR_BLOCK_SERVER
WRH$_CURRENT_BLOCK_SERVER
WRH$_INST_CACHE_TRANSFER_BL
WRH$_ACTIVE_SESSION_HISTORY_BL
WRH$_TABLESPACE_STAT_BL
TABLE_NAME
WRH$_LOG
WRH$_MTTR_TARGET_ADVICE
WRH$_TABLESPACE
WRH$_TABLESPACE_SPACE_USAGE
WRH$_SERVICE_NAME
WRH$_SERVICE_STAT_BL
WRH$_SERVICE_WAIT_CLASS_BL
WRH$_SESS_TIME_STATS
WRH$_STREAMS_CAPTURE
WRH$_STREAMS_APPLY_SUM
WRH$_BUFFERED_QUEUES
TABLE_NAME
WRH$_BUFFERED_SUBSCRIBERS
WRH$_PERSISTENT_QUEUES
WRH$_PERSISTENT_SUBSCRIBERS
WRH$_RULE_SET
WRI$_SCH_CONTROL
WRI$_SCH_VOTES
WRH$_RSRC_CONSUMER_GROUP
WRH$_RSRC_PLAN
WRH$_CLUSTER_INTERCON
WRH$_IC_DEVICE_STATS
WRH$_IC_CLIENT_STATS
TABLE_NAME
WRH$_MEM_DYNAMIC_COMP
WRH$_INTERCONNECT_PINGS_BL
WRH$_DISPATCHER
WRH$_SHARED_SERVER_SUMMARY
WRH$_DYN_REMASTER_STATS
WRH$_PERSISTENT_QMN_CACHE
WRM$_WR_USAGE
WRM$_DATABASE_INSTANCE
WRM$_SNAPSHOT
WRM$_SNAPSHOT_DETAILS
WRM$_SNAP_ERROR
TABLE_NAME
WRM$_BASELINE
WRM$_COLORED_SQL
WRM$_BASELINE_DETAILS
WRM$_BASELINE_TEMPLATE
WRM$_WR_CONTROL
WRR$_FILTERS
WRR$_CAPTURES
WRR$_CAPTURE_STATS
WRR$_CAPTURE_UC_GRAPH
WRR$_REPLAYS
WRR$_REPLAY_STATS
TABLE_NAME
WRR$_REPLAY_DIVERGENCE
WRR$_REPLAY_UC_GRAPH
WRR$_CONNECTION_MAP
WRR$_REPLAY_SQL_TEXT
WRR$_REPLAY_SQL_BINDS
WRR$_SEQUENCE_EXCEPTIONS
WRR$_REPLAY_CALL_FILTER
WRR$_REPLAY_FILTER_SET
WRR$_REPLAY_DEP_GRAPH
WRR$_REPLAY_COMMITS
WRR$_REPLAY_REFERENCES
TABLE_NAME
WRI$_ADV_SQLW_SUM
WRI$_ADV_SQLW_STMTS
WRI$_ADV_SQLW_TABLES
WRI$_ADV_SQLW_TABVOL
WRI$_ADV_SQLW_COLVOL
WRI$_ADV_SQLA_MAP
WRI$_ADV_SQLA_SUM
WRI$_ADV_SQLA_STMTS
WRI$_ADV_SQLA_TABLES
WRI$_ADV_SQLA_TABVOL
WRI$_ADV_SQLA_COLVOL
TABLE_NAME
WRI$_ADV_SQLA_TMP
WRI$_ADV_SQLA_FAKE_REG
DBMS_PARALLEL_EXECUTE_TASK$
DBMS_PARALLEL_EXECUTE_CHUNKS$
DBFS$_STORES
DBFS$_MOUNTS
DBFS$_STATS
DBFS_SFS$_TAB
DBFS_SFS$_VOL
DBFS_SFS$_SNAP
DBFS_SFS$_FS
TABLE_NAME
DBFS_SFS$_FST
DBFS_SFS$_FSTP
DBFS_SFS$_FSTO
DBFS_HS$_FS
DBFS_HS$_PROPERTY
DBFS_HS$_SFLOCATORTABLE
DBFS_HS$_BACKUPFILETABLE
DBFS_HS$_CONTENTFNMAPTBL
DBFS_HS$_STORECOMMANDS
DBFS_HS$_STOREID2POLICYCTX
DBFS_HS$_STOREPROPERTIES
TABLE_NAME
DBFS_HS$_STOREIDTABLE
SQL_TK_COLL_CHK$
SQL_TK_ROW_CHK$
SQL_TK_REF_CHK$
SQL_TK_TAB_DESC$
WRI$_OPTSTAT_SYNOPSIS_PARTGRP
WRI$_OPTSTAT_SYNOPSIS_HEAD$
STREAMS$_APPLY_SPILL_MESSAGES
STREAMS$_INTERNAL_TRANSFORM
DBMS_LOCK_ALLOCATED
DBMS_ALERT_INFO
TABLE_NAME
SCHEDULER$_EVENT_QTAB
AQ$_SCHEDULER$_EVENT_QTAB_S
AQ$_SCHEDULER$_EVENT_QTAB_L
SYS_IOT_OVER_12473
SCHEDULER$_REMDB_JOBQTAB
AQ$_SCHEDULER$_REMDB_JOBQTAB_S
AQ$_SCHEDULER$_REMDB_JOBQTAB_L
SYS_IOT_OVER_12508
SCHEDULER_FILEWATCHER_QT
AQ$_SCHEDULER_FILEWATCHER_QT_S
AQ$_SCHEDULER_FILEWATCHER_QT_L
TABLE_NAME
SYS_IOT_OVER_12538
ALERT_QT
AQ$_ALERT_QT_S
AQ$_ALERT_QT_L
SYS_IOT_OVER_12594
HS$_FDS_CLASS
HS$_FDS_INST
HS$_BASE_CAPS
HS$_CLASS_CAPS
HS$_INST_CAPS
HS$_BASE_DD
TABLE_NAME
HS$_CLASS_DD
HS$_INST_DD
HS$_CLASS_INIT
HS$_INST_INIT
HS$_FDS_CLASS_DATE
HS_BULKLOAD_VIEW_OBJ
HS_PARTITION_COL_NAME
HS_PARTITION_COL_TYPE
HS$_PARALLEL_METADATA
HS$_PARALLEL_PARTITION_DATA
HS$_PARALLEL_HISTOGRAM_DATA
TABLE_NAME
HS$_PARALLEL_SAMPLE_DATA
AQ$_MEM_MC
AQ$_AQ$_MEM_MC_S
AQ$_AQ$_MEM_MC_L
SYS_IOT_OVER_12797
AQ_EVENT_TABLE
AQ_PROP_TABLE
AQ$_AQ_PROP_TABLE_S
AQ$_AQ_PROP_TABLE_L
SYS_IOT_OVER_12833
KUPC$DATAPUMP_QUETAB
TABLE_NAME
AQ$_KUPC$DATAPUMP_QUETAB_S
AQ$_KUPC$DATAPUMP_QUETAB_L
SYS_IOT_OVER_13016
SYS$SERVICE_METRICS_TAB
AQ$_SYS$SERVICE_METRICS_TAB_S
AQ$_SYS$SERVICE_METRICS_TAB_L
SYS_IOT_OVER_13141
ATEMPTAB$
SQLLOG$
SQLOBJ$
SQLOBJ$DATA
TABLE_NAME
MAP_OBJECT
CLUSTER_DATABASES
CLUSTER_NODES
CLUSTER_INSTANCES
COL_GROUP_USAGE$
FINALHIST$
PSTUBTBL
WRI$_ADV_ASA_RECO_DATA
PLAN_TABLE$
RULE_SET_PR$
RULE_SET_IOT$
TABLE_NAME
RULE_SET_ROP$
CHNF$_CLAUSES
CHNF$_GROUP_FILTER_IOT
CHNF$_QUERY_DELTAS
RECENT_RESOURCE_INCARNATIONS$
KU$NOEXP_TAB
KU$_LIST_FILTER_TEMP
KU$_LIST_FILTER_TEMP_2
WRI$_SQLSET_PLANS_TOCAP
WRI$_SQLSET_STS_TOPACK
WRH$_FILESTATXS
TABLE_NAME
WRH$_SQLSTAT
WRH$_SYSTEM_EVENT
WRH$_WAITSTAT
WRH$_LATCH
WRH$_LATCH_CHILDREN
WRH$_LATCH_PARENT
WRH$_LATCH_MISSES_SUMMARY
WRH$_EVENT_HISTOGRAM
WRH$_DB_CACHE_ADVICE
WRH$_ROWCACHE_SUMMARY
WRH$_SGASTAT
TABLE_NAME
WRH$_SYSSTAT
WRH$_SYS_TIME_MODEL
WRH$_OSSTAT
WRH$_PARAMETER
WRH$_MVPARAMETER
WRH$_SEG_STAT
WRH$_DLM_MISC
WRH$_INST_CACHE_TRANSFER
WRH$_ACTIVE_SESSION_HISTORY
WRH$_TABLESPACE_STAT
WRH$_SERVICE_STAT
TABLE_NAME
WRH$_SERVICE_WAIT_CLASS
WRH$_INTERCONNECT_PINGS
WRR$_REPLAY_SCN_ORDER
WRR$_REPLAY_SEQ_DATA
WRR$_REPLAY_DATA
WRR$_WORKLOAD_ATTRIBUTES
ODCI_SECOBJ$
ODCI_WARNINGS$
ODCI_PMO_ROWIDS$
TTS_TBS$
TTS_USR$
TABLE_NAME
TTS_ERROR$
WRI$_OPTSTAT_SYNOPSIS$
STREAMS$_APPLY_SPILL_MSGS_PART
STREAMS$_COMPONENT_IN
STREAMS$_COMPONENT_LINK_IN
STREAMS$_COMPONENT_PROP_IN
STREAMS$_COMPONENT_STAT_IN
STREAMS$_COMPONENT_EVENT_IN
STREAMS$_LOCAL_FINDINGS_IN
STREAMS$_LOCAL_RECS_IN
STREAMS$_LOCAL_ACTIONS_IN
TABLE_NAME
STREAMS$_COMPONENT_STAT_OUT
STREAMS$_PATH_STAT_OUT
STREAMS$_PATH_BOTTLENECK_OUT
AQ$_SCHEDULER$_EVENT_QTAB_T
AQ$_SCHEDULER$_EVENT_QTAB_H
AQ$_SCHEDULER$_EVENT_QTAB_G
AQ$_SCHEDULER$_EVENT_QTAB_I
AQ$_SCHEDULER$_REMDB_JOBQTAB_T
AQ$_SCHEDULER$_REMDB_JOBQTAB_H
AQ$_SCHEDULER$_REMDB_JOBQTAB_G
AQ$_SCHEDULER$_REMDB_JOBQTAB_I
TABLE_NAME
AQ$_SCHEDULER_FILEWATCHER_QT_T
AQ$_SCHEDULER_FILEWATCHER_QT_H
AQ$_SCHEDULER_FILEWATCHER_QT_G
AQ$_SCHEDULER_FILEWATCHER_QT_I
AQ$_ALERT_QT_T
AQ$_ALERT_QT_H
AQ$_ALERT_QT_G
AQ$_ALERT_QT_I
AQ$_AQ$_MEM_MC_T
AQ$_AQ$_MEM_MC_H
AQ$_AQ$_MEM_MC_G
TABLE_NAME
AQ$_AQ$_MEM_MC_I
AQ$_AQ_PROP_TABLE_T
AQ$_AQ_PROP_TABLE_H
AQ$_AQ_PROP_TABLE_G
AQ$_AQ_PROP_TABLE_I
IMPDP_STATS
KU$_DATAPUMP_MASTER_11_2
KU$_DATAPUMP_MASTER_11_1_0_7
KU$_DATAPUMP_MASTER_11_1
KU$_DATAPUMP_MASTER_10_1
AQ$_KUPC$DATAPUMP_QUETAB_T
TABLE_NAME
AQ$_KUPC$DATAPUMP_QUETAB_H
AQ$_KUPC$DATAPUMP_QUETAB_G
AQ$_KUPC$DATAPUMP_QUETAB_I
AQ$_SYS$SERVICE_METRICS_TAB_T
AQ$_SYS$SERVICE_METRICS_TAB_H
AQ$_SYS$SERVICE_METRICS_TAB_G
AQ$_SYS$SERVICE_METRICS_TAB_I
WRI$_ADV_OBJSPACE_TREND_DATA
WRI$_ADV_OBJSPACE_CHROW_DATA
*933 rows selected.*
SQL>

Connecting rman and creating recovery catalog

I'm using oracle8i with Window/Nt
i have two database U10 and U20.
Using recovery manager, target db is U10 and recovery catalog of U10 is saved in U20.
i followed method in oracle8i manual(Rman Part)
when i attempt to connect rman, following message bothers me..
C:\WINDOWS>RMAN CATALOG RMAN/RMAN@U20
Recovery Manager: Release 8.1.6.0.0 - Production
RMAN-06008: connected to recovery catalog database
RMAN-06428: recovery catalog is not installed
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-00554: initialization of internal recovery manager package failed
RMAN-06004: ORACLE error from recovery catalog database: ORA-02112: PCC: SELECT.
.INTO returns too many rows
RMAN-06097: text of failing SQL statement: select user into :b1 from dual
RMAN-06099: error occurred in source file: krmk.pc, line: 3842
and when i attempt to create recovery catalog, i got a bunch of message
RMAN> CREATE CATALOG TABLESPACE "RCVCAT"
RMAN-06099: error occurred in source file: krmk.pc, line: 6549
RMAN-06097: text of failing SQL statement: CREATE TABLE db
db_key NUMBER NOT NULL, -- sequence generated primary key
db_id NUMBER NOT NULL, -- kccfhdbi from controlfile
-- updatable columns
curr_dbinc_key NUMBER, -- current incarnation
CONSTRAINT db_p PRIMARY KEY (db_key),
CONSTRAINT db_u1 UNIQUE(db_id) -- ensure that db_id is unique
tablespace "RCVCAT"
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-06433: error installing recovery catalog
i'm so hectic... plz help me....

Based on the following errors:
RMAN-06004: ORACLE error from recovery catalog database: ORA-02112: PCC: SELECT..INTO returns too many rows
RMAN-06097: text of failing SQL statement: select user into :b1 from dual
It looks like the table dual has more than 1 row.
select * from dual;
What do you get?
It should look like this:
D
X
1 row selected.
Your recovery catalog database may have a problem. You may need to start over and recreate the recovery catalog.
null

RMAN-06428:

hi,
I am configuring recovery catalog on 11.2.0.1.0 on different database . Facing RMAN-06428 error when register database command is executed , kindly confirm exactly what i am doing wrong below is the code
Catalog database name=rman
Target database name=orcl
CONNECT SYS/oracle@rman AS SYSDBA // From catalog db i have created catalog
CREATE USER rman IDENTIFIED BY cat
TEMPORARY TABLESPACE temp
DEFAULT TABLESPACE tools
QUOTA UNLIMITED ON tools;
GRANT RECOVERY_CATALOG_OWNER TO rman;
rman) CONNECT CATALOG rman/cat@rman
CREATE CATALOG;
rman TARGET sys@orcl as sysdba CATALOG rman/cat@rman
REGISTER DATABASE;
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of register command at 05/23/2013 15:43:49
RMAN-06428: recovery catalog is not installed

925701 wrote:
hi,
I am configuring recovery catalog on 11.2.0.1.0 on different database . Facing RMAN-06428 error when register database command is executed , kindly confirm exactly what i am doing wrong below is the code
Catalog database name=rman
Target database name=orcl
CONNECT SYS/oracle@rman AS SYSDBA // From catalog db i have created catalog
CREATE USER rman IDENTIFIED BY cat
TEMPORARY TABLESPACE temp
DEFAULT TABLESPACE tools
QUOTA UNLIMITED ON tools;
GRANT RECOVERY_CATALOG_OWNER TO rman;
rman) CONNECT CATALOG rman/cat@rman
CREATE CATALOG;What message did you get after this command.I guess we get catalog created message.
GRANT connect, resource, recovery_catalog_owner TO rman; Did you execute this?
Edited by: swapnil kambli on May 23, 2013 4:23 AM

Config recovery catalog database

dear all.
i had read several documents about "create recovery catalog", but all of that start with statement
CREATE TABLESPACE
...and continue with CREATE USER, etc.
I want to create a NEW database for recovery catalog, this database what characteristics must to have ?? Anyone have a link or document where explain me how to create a database (only i need database creation) for recovery catalog.???
thanks
The version is ORacle 10gr2

hi,
the recovery catalog is just a normal database with a schema called rman or whatever you choose.
it should ideally be on a separate server to your target database. The RMAN database as with any other database should have multiplexed control files and redo files.
schema creation assumming windows O/S
-- Create tablepsace to hold repository
CREATE TABLESPACE "RMAN"
DATAFILE 'C:\ORACLE\ORADATA\W2K1\RMAN01.DBF' SIZE 6208K REUSE
AUTOEXTEND ON NEXT 64K MAXSIZE 32767M
EXTENT MANAGEMENT LOCAL
SEGMENT SPACE MANAGEMENT AUTO;
-- Create rman schema owner
CREATE USER rman IDENTIFIED BY rman
TEMPORARY TABLESPACE temp
DEFAULT TABLESPACE rman
QUOTA UNLIMITED ON rman;
GRANT connect, resource, recovery_catalog_owner TO rman;
then create the recovery catalog
C:>rman catalog=rman/rman@w2k1
Recovery Manager: Release 9.2.0.1.0 - Production
Copyright (c) 1995, 2002, Oracle Corporation. All rights reserved.
connected to recovery catalog database
recovery catalog is not installed
RMAN> create catalog tablespace "RMAN";
recovery catalog created
RMAN> exit
Recovery Manager complete.
C:>
then register your database
C:>rman catalog=rman/rman@w2k1 target=sys/password@w2k2
Recovery Manager: Release 9.2.0.1.0 - Production
Copyright (c) 1995, 2002, Oracle Corporation. All rights reserved.
connected to target database: W2K2 (DBID=1371963417)
connected to recovery catalog database
RMAN> register database;
database registered in recovery catalog
starting full resync of recovery catalog
full resync complete
RMAN>
let us know how you get on.
rgds
alan

RMAN-06429: RCVCAT database is not compatible with this version of RMAN

Hi There,
I just want to confirm there is no work around for the issue I am having. Here is my situation:
I have four Oracle 8i databases that can not be removed because of client requirements. These 8i databases have there own RMAN catalog which is 10G (Originally there were Oracle 8i, 9i and 10g databases using it but are now moved to 11g catalog). Databases are backing up fine. However, all the other databases are using the RMAN 11g Catalog. I want to point the Oracle 8i databases to point to the RMAN 11g recovery catalog. I created an 8i schema, however, i'm getting the following error message: RMAN-06429: RCVCAT database is not compatible with this version of RMAN. It's pretty straight forward, however, I wanted to put the question out there to see if there are any work arounds. I would prefer to have only one RMAN recovery catalog.
Thanks in advance.
J

Hello;
I know of no way around the RMAN Compatibility Matrix. I would keep a second catalog DB for these older databases. Or go NOCATALOG. I checked all my sources and if there's a better option I sure did not find it. What breaks if these go to Oracle 9?
http://arjudba.blogspot.com/2010/03/about-rman-compatibility-matrix.html
Ask Tom
http://asktom.oracle.com/pls/asktom/f?p=100:11:0::::P11_QUESTION_ID:518622203320
Additional Information :
OERR: RMAN 6429 %s database is not compatible with this version of RMAN [ID 70776.1]
RMAN-06439: Compatibility Between 8.1.5 RMAN Executable and 8.1.6 Catalog [ID 104728.1]
Best Regards
mseberg
Edited by: mseberg on Sep 7, 2012 8:27 AM
Edited by: mseberg on Sep 7, 2012 10:53 AM

Maintenance Recovery Catalog

How can I remove the recovery catalog (registration of the metadata) made a backup on a tape that no longer exists on the host?
RMAN> list backupset 65045;
List of Backup Sets
===================
BS Key Type LV Size Device Type Elapsed Time Completion Time
=========================================================
65045 Full 122M SBT_TAPE 00:13:52 26-MAR-07
BP Key: 65047 Status: UNAVAILABLE Tag: TAG20070326T112147
Piece Name: g3idiv2b_1_1
List of Datafiles in backup set 65045
File LV Type Ckp SCN Ckp Time Name
=========================================================
4 Full 15154846192 26-MAR-07 /DATA/oradata/momina/example01.dbf
RMAN> delete backupset 65045;
allocated channel: ORA_DISK_1
channel ORA_DISK_1: sid=285 devtype=DISK
allocated channel: ORA_DISK_2
channel ORA_DISK_2: sid=295 devtype=DISK
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of delete command at 11/19/2008 08:40:09
RMAN-06160: no backup pieces found for backup set key: 65045
This error is obvious, I can not delete a backup tape to have a channel to disk.
But implementing this
RMAN> show all;
RMAN configuration parameters are:
CONFIGURE DEFAULT DEVICE TYPE TO DISK;
RMAN> CONFIGURE DEFAULT DEVICE TYPE TO sbt;
old RMAN configuration parameters:
CONFIGURE DEFAULT DEVICE TYPE TO DISK;
new RMAN configuration parameters:
CONFIGURE DEFAULT DEVICE TYPE TO 'SBT_TAPE';
new RMAN configuration parameters are successfully stored
starting full resync of recovery catalog
full resync complete
released channel: ORA_DISK_1
released channel: ORA_DISK_2
RMAN> show all;
RMAN configuration parameters are:
CONFIGURE DEFAULT DEVICE TYPE TO 'SBT_TAPE';
RMAN> delete backupset 65045;
allocated channel: ORA_DISK_1
channel ORA_DISK_1: sid=285 devtype=DISK
allocated channel: ORA_DISK_2
channel ORA_DISK_2: sid=295 devtype=DISK
released channel: ORA_DISK_1
released channel: ORA_DISK_2
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of delete command at 11/19/2008 08:47:31
ORA-19554: error allocating device, device type: SBT_TAPE, device name:
ORA-27211: Failed to load Media Management Library
Additional information: 2
If possible delete the backupset of recovery catalog despite not having media managemnet library (dont have hardware or sofware tape)?
Juan

Thank, but....
With the channel disk:
#> rman target / catalog rman/rman@database1
RMAN> crosscheck backupset;
Recovery Manager: Release 9.2.0.6.0 - 64bit Production
RMAN>
allocated channel: ORA_DISK_1
channel ORA_DISK_1: sid=175 devtype=DISK
allocated channel: ORA_DISK_2
channel ORA_DISK_2: sid=285 devtype=DISK
crosschecked backup piece: found to be 'AVAILABLE'
backup piece handle=/DATA/backups/momia/3491_1_MOMIA_17_11_2008 recid=5524 stamp=671060706
crosschecked backup piece: found to be 'AVAILABLE'
Crosschecked 14 objects
The backupset i need delete (of the recovery catalog) is register on tape.
With the channel sbt:
Recovery Manager complete.
#> rman target / catalog rman/rman@database1
RMAN> CONFIGURE DEFAULT DEVICE TYPE TO sbt;
RMAN> crosscheck backupset;
RMAN>
allocated channel: ORA_DISK_1
channel ORA_DISK_1: sid=179 devtype=DISK
allocated channel: ORA_DISK_2
channel ORA_DISK_2: sid=272 devtype=DISK
released channel: ORA_DISK_1
released channel: ORA_DISK_2
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of crosscheck command at 11/19/2008 10:32:37
ORA-19554: error allocating device, device type: SBT_TAPE, device name:
**ORA-27211: Failed to load Media Management Library**
Additional information: 2
The problem is the same.

Recommendations for recovery catalog database backup

Hi
We are using IBM Tivoli Storage Manager for our 9i db on AIX 5.2.
I would like us to consider using rman but I am not sure of the best way we would go about backing up the database we would use for our recovery catalog.
This database that hold all the metadata would need to be backed up after every rman backup. The rman backup would go to tape, so I am assuming that the recovery catalog would be backed up on tape also.
What are the common procedures for this in other shops ?

Dan A wrote:
Aman. That doc does help, and indeed it does explain
Back up the recovery catalog with the same frequency that you back up the target database.
We would be doing nightly backups, so we would have to back up the catalog with the same frequency.
The doc explains that we would use rman for these backups also, but that it would be in NOCATALOG mode so that the repository is in the control file.
And then what? Just copy this to tape? Seems that with rman there is then a need to do two backups - one of the target db and one of the recovery catalog.
Thanks.I shall suggest to take an export of the underlying schema which is holding the info in the recovery catalog. That's all which is basically required to be safe. In case , everything gets burnt regarding the catalog db,you can immediately create another db, import the user back there and things are in place. This should be a quick and easy way out of the backup of recovery catalog.
Yes if you are going to take backups every night than backup of recovery catalog schema/db nightly will be a good option. Docs are meant to promote people for RMAN so indeed they would talk about it. But its not at all a compulstion to use RMAN for recovery catalog schema's backup. If its a big catalog maintaining lots of database's info than using RMAN with all its features is a good option. If a single db is a part of it than it may not be that much big and export of teh schema alone may serve the purpose too.
HTH
Aman....

Help needed on RMAN backup/recovery

Hi All,
I planning to implement the following backup strategy..
Online hotbackup is taking using RMAN without Recovery Catalog, Instead using controlfile autobackup to the repository. We the following backup schedules
1. Weekly full backup of database.
2. Daily Incremental backup with archive logs
And the backupset files created by the above schedule are stored in tape.
My Assumption:
As we are using control file autobackup, whenever i take full/incremental backup. the backup information will be stored in control file and the control files/spfile also will be backed up.
I did the following:
1. I have taken full backup(incr level=0) of database in the morning.
2. After taking the full backup, i did some transactions in one of the table.
3. Again, i have taken the incremental backup of the database.
4. All the backup pieces are stored in a tape.
My Doubt:
1. Now, controlfile will have information of full backup and incremental backup right?
2. If i restore the database in a new machine with these backups, both full backup files and incremental backup files are considered?
Thanks,
Praveen.

To answer your questions:
1. Now, controlfile will have information of full backup and incremental backup right?Yes.
2. If i restore the database in a new machine with these backups, both full backup files and incremental backup files are considered?YES.
HTH
Thanks
Chandra

RMAN-20001: target database not found in recovery catalog

I am practicing loss off all control files. I have rman catalog backups which are set to autobackup controlfile. So far I did this.
RMAN> startup nomount;
Oracle instance started
Total System Global Area 209715200 bytes
Fixed Size 1272864 bytes
Variable Size 155190240 bytes
Database Buffers 50331648 bytes
Redo Buffers 2920448 bytes
RMAN> restore controlfile from autobackup;
Starting restore at 08-SEP-10
allocated channel: ORA_DISK_1
channel ORA_DISK_1: sid=156 devtype=DISK
recovery area destination: /u02/flash_recovery
database name (or database unique name) used for search: TEST
channel ORA_DISK_1: autobackup found in the recovery area
channel ORA_DISK_1: autobackup found: /u02/flash_recovery/TEST/autobackup/2009_12_09/o1_mf_s_705171034_5l0kgv4o_.bkp
channel ORA_DISK_1: control file restore from autobackup complete
output filename=/u02/control_files/TEST/control02.ctl
output filename=/u03/oradata/TEST/control03.ctl
Finished restore at 08-SEP-10
RMAN> alter database mount;
database mounted
released channel: ORA_DISK_1
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of alter db command at 09/08/2010 14:54:50
RMAN-06004: ORACLE error from recovery catalog database: RMAN-20001: target database not found in recovery catalog
I am assuming this has something to do with DBID but ... I don't have it and I don't know how to find it.

Hi BelMan,
Here is output
BS Key Type LV Size Device Type Elapsed Time Completion Time
56869 Full 11.20M DISK 00:00:00 08-SEP-10
BP Key: 56871 Status: AVAILABLE Compressed: NO Tag: TAG20100908T135312
Piece Name: /u01/oracle/product/10.2.0/db_1/dbs/cf_c-549414289-20100908-00
Control File Included: Ckp SCN: 125665520 Ckp time: 08-SEP-10
BS Key Type LV Size Device Type Elapsed Time Completion Time
56993 Full 11.20M DISK 00:00:00 08-SEP-10
BP Key: 56995 Status: AVAILABLE Compressed: NO Tag: TAG20100908T142547
Piece Name: /u01/oracle/product/10.2.0/db_1/dbs/cf_c-549414289-20100908-01
Control File Included: Ckp SCN: 125668490 Ckp time: 08-SEP-10

Installing recovery catalog!!

hello,
can anybody tell that how to install recovery
catalog on oracle8i?

Hi,
Here is the procedure for creating RMAN catalog:
Installing RMAN Catalog:
Install the recovery catalog schema in a different database (say RCAT) from the target database you will be backing up.
Assume the following for the examples below:
User SYS with password CHANGE_ON_INSTALL has SYSDBA privileges on the recovery catalog database RCAT.
There is a tablespace called CATTBS on the recovery catalog database RCAT that stores the recovery catalog.
There is a tablespace called TEMP in the recovery catalog database.
To set up the recovery catalog schema:
Start SQL*Plus and then connect with administrator privileges to the database containing the recovery catalog (RCAT). For example, enter:
SQL> CONNECT sys/change_on_install@rcat
Create a log file that you can use to check for errors. For example, enter:
SQL> SPOOL create_rman.log
Create a user and schema for the recovery catalog. For example, enter:
SQL> CREATE USER rman IDENTIFIED BY rman
2> TEMPORARY TABLESPACE temp
3> DEFAULT TABLESPACE cattbs
4> QUOTA UNLIMITED ON cattbs;
Grant the RECOVERY_CATALOG_OWNER role to the schema owner. This role provides the user with privileges to maintain and query the recovery catalog.
SQL> GRANT recovery_catalog_owner TO rman;
Grant other desired privileges to the RMAN user.
SQL> GRANT connect, resource TO rman;
Host out to the operating system to check the create_rman.log file for any errors before continuing. For example, a UNIX user can issue:
SQL> host
% vi create_rman.log
To create the recovery catalog:
Connect to the database that will contain the catalog as the catalog owner. For example, from the operating system command line enter:
% rman catalog rman/rman@rcat
You can also connect from the RMAN prompt:
% rman
RMAN> connect catalog rman/rman@rcat
Issue the create catalog command to create the catalog, specifying the CATTBS tablespace:
RMAN> create catalog tablespace cattbs;
Note that the creation of the catalog can take several minutes.
Host out to the operating system to check the create_rman.log file for any errors before continuing. For example, a UNIX user can issue:
RMAN> host;
% vi create_rman.log
Optionally, query the recovery catalog to see which tables were created:
SQL> SELECT table_name FROM user_tables;
Note: Database name, SYS password, tablespace names are for examples only. You can name change them.
You all set!!!! Good luck.
-Rama
null

RMAN-06004:ORACLE error from recovery catalog ... ORA-00904: : invalid ...

Good Morning All,
One of our RMAN backups is failing with the following error message. Any suggestions would be greatly appreciated.
==================================================================================================
Starting backup at 12/30/2008 22:03:47
using channel ORA_DISK_1
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of backup command at 12/30/2008 22:03:47
RMAN-06004: ORACLE error from recovery catalog database: ORA-00904: : invalid identifier
RMAN>
RMAN> ##BACKUP ARCHIVELOG ALL FORMAT '%d_bkp_al_%t_Set%s_Piece%p' delete input;
2>
3> # DELETE ARCHIVELOG UNTIL TIME 'SYSDATE-7';
4>
5> # check if database can be restored
6> # RESTORE DATABASE VALIDATE;
7>
8> # check if controlfile can be restored
9> ##RESTORE CONTROLFILE to '/backups/admin/custpr/custpr_bkp_cntlfile.ctl' VALIDATE;
10>
11> # check if archivelogs for the past two weeks can be restored
12> # RESTORE ARCHIVELOG FROM TIME 'SYSDATE-7' VALIDATE;
13>
14> # - Verify all backups on backup media are intact
15> # CROSSCHECK BACKUP OF DATABASE;
16>
17> # - Display a list of files that need to be backed up based on the retention
18> # policy. For this case study, files that don't have at least 1 backups
19> # will be reported.
20> REPORT NEED BACKUP;
RMAN retention policy will be applied to the command
RMAN retention policy is set to recovery window of 7 days
Report of files whose recovery needs more than 7 days of archived logs
File Days Name
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of report command at 12/30/2008 22:03:48
RMAN-06004: ORACLE error from recovery catalog database: ORA-00904: : invalid identifier
RMAN>
RMAN> # - delete un-necessary backups. This command deletes backups based on the
2> # retention policy.
3> ######### commented out DELETE OBSOLETE - TSM not configured to delete on 68
4> #########DELETE OBSOLETE;
5>
6> # - get complete list of existing backups
7> LIST BACKUP;
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of list command at 12/30/2008 22:03:49
RMAN-06004: ORACLE error from recovery catalog database: ORA-00904: : invalid identifier
RMAN>
RMAN> #-end of file-
2> **end-of-file**
RMAN>
Edited by: ORA_UMAIR on Dec 31, 2008 7:51 AM

This Oracle Database is 9.2.0.6.0. Here is the complete log file. The RMAN script that I am using ran successfully many times before.
====================================================================================================
Recovery Manager: Release 9.2.0.6.0 - 64bit Production
Copyright (c) 1995, 2002, Oracle Corporation. All rights reserved.
RMAN>
connected to recovery catalog database
RMAN>
connected to target database: CUSTPR (DBID=525071053)
RMAN>
RMAN> #########################################################################
2> # LEVEL 0 BACKUP #
3> #########################################################################
4>
5> # Configure backups to be written to disk.
6> CONFIGURE DEFAULT DEVICE TYPE TO DISK;
old RMAN configuration parameters:
CONFIGURE DEFAULT DEVICE TYPE TO DISK;
new RMAN configuration parameters:
CONFIGURE DEFAULT DEVICE TYPE TO DISK;
new RMAN configuration parameters are successfully stored
starting full resync of recovery catalog
full resync complete
RMAN>
RMAN> # Set the retention policy to a recovery window of 7 days. This ensures that
2> # RMAN retains all backups needed to recover the database to any point in time
3> # in the last 7 days. You can use the DELETE OBSOLETE command to delete
4> # backups that are no longer required by the retention policy. To exclude a
5> # backup from consideration by the policy, you can use KEEP option with the
6> # BACKUP command.
7> CONFIGURE RETENTION POLICY TO RECOVERY WINDOW OF 7 DAYS;
old RMAN configuration parameters:
CONFIGURE RETENTION POLICY TO RECOVERY WINDOW OF 7 DAYS;
new RMAN configuration parameters:
CONFIGURE RETENTION POLICY TO RECOVERY WINDOW OF 7 DAYS;
new RMAN configuration parameters are successfully stored
starting full resync of recovery catalog
full resync complete
RMAN>
RMAN> # Configure RMAN to use two disk channels for backup, restore, recovery, and
2> # maintenance operations.
3> CONFIGURE DEVICE TYPE DISK PARALLELISM 1;
old RMAN configuration parameters:
CONFIGURE DEVICE TYPE DISK PARALLELISM 1;
new RMAN configuration parameters:
CONFIGURE DEVICE TYPE DISK PARALLELISM 1;
new RMAN configuration parameters are successfully stored
starting full resync of recovery catalog
full resync complete
RMAN>
RMAN> # Configure RMAN to write disk backups to the /backup directory.
2> # The format specifier %t is replaced with a 4-byte timestamp, %s with the
3> # backup set number, and %p with the backup piece number.
4> CONFIGURE CHANNEL DEVICE TYPE DISK FORMAT '/backups/admin/custpr/%d_bkp_df%t_Set%s_Piece%p';
old RMAN configuration parameters:
CONFIGURE CHANNEL DEVICE TYPE DISK FORMAT '/backups/admin/custpr/%d_bkp_df%t_Set%s_Piece%p';
new RMAN configuration parameters:
CONFIGURE CHANNEL DEVICE TYPE DISK FORMAT '/backups/admin/custpr/%d_bkp_df%t_Set%s_Piece%p';
new RMAN configuration parameters are successfully stored
starting full resync of recovery catalog
full resync complete
RMAN>
RMAN> # Configure RMAN to back up the control file after each backup.
2> CONFIGURE CONTROLFILE AUTOBACKUP ON;
old RMAN configuration parameters:
CONFIGURE CONTROLFILE AUTOBACKUP ON;
new RMAN configuration parameters:
CONFIGURE CONTROLFILE AUTOBACKUP ON;
new RMAN configuration parameters are successfully stored
starting full resync of recovery catalog
full resync complete
RMAN>
RMAN> # Configure RMAN to write controlfile autobackups to the /backup directory.
2> CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO '/backups/admin/custpr/%d_bkp_cf%F';
old RMAN configuration parameters:
CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO '/backups/admin/custpr/%d_bkp_cf%F';
new RMAN configuration parameters:
CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO '/backups/admin/custpr/%d_bkp_cf%F';
new RMAN configuration parameters are successfully stored
starting full resync of recovery catalog
full resync complete
RMAN>
RMAN> # Enable the backup optimization feature introduced in 9i to make sure that
2> # RMAN won't backup an archivelog or datafile if there already exists a backup
3> # of that file. The FORCE option can be used to override optimization on a
4> # specific BACKUP command.
5> CONFIGURE BACKUP OPTIMIZATION ON;
old RMAN configuration parameters:
CONFIGURE BACKUP OPTIMIZATION ON;
new RMAN configuration parameters:
CONFIGURE BACKUP OPTIMIZATION ON;
new RMAN configuration parameters are successfully stored
starting full resync of recovery catalog
full resync complete
RMAN>
RMAN> # Use the SHOW ALL command to see the current configuration settings.
2> SHOW ALL ;
RMAN configuration parameters are:
CONFIGURE RETENTION POLICY TO RECOVERY WINDOW OF 7 DAYS;
CONFIGURE BACKUP OPTIMIZATION ON;
CONFIGURE DEFAULT DEVICE TYPE TO DISK;
CONFIGURE CONTROLFILE AUTOBACKUP ON;
CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE 'SBT_TAPE' TO '%d_bkp_cf%F';
CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO '/backups/admin/custpr/%d_bkp_cf%F';
CONFIGURE DEVICE TYPE 'SBT_TAPE' PARALLELISM 1;
CONFIGURE DEVICE TYPE DISK PARALLELISM 1;
CONFIGURE DATAFILE BACKUP COPIES FOR DEVICE TYPE SBT_TAPE TO 1; # default
CONFIGURE DATAFILE BACKUP COPIES FOR DEVICE TYPE DISK TO 1; # default
CONFIGURE ARCHIVELOG BACKUP COPIES FOR DEVICE TYPE SBT_TAPE TO 1; # default
CONFIGURE ARCHIVELOG BACKUP COPIES FOR DEVICE TYPE DISK TO 1; # default
CONFIGURE CHANNEL DEVICE TYPE 'SBT_TAPE' FORMAT '%d_bkp_df%t_Set%s_Piece%p';
CONFIGURE CHANNEL DEVICE TYPE DISK FORMAT '/backups/admin/custpr/%d_bkp_df%t_Set%s_Piece%p';
CONFIGURE MAXSETSIZE TO UNLIMITED; # default
CONFIGURE SNAPSHOT CONTROLFILE NAME TO '/orahome2/custprdb/9.2.0/dbs/snapcf_custpr.f'; # default
RMAN>
RMAN> # The following commands are run each day to start the backup cycle.
2> # The steps are:
3> # - Take an incremental level 0 backup of the database. A level 0 backup is
4> # a complete backup of the entire file which can be used as the basis
5> # for a subsequent incremental backup.
6> # - Backup all archivelogs that have not already been backed up.
7> # - Delete on-disk archivelogs older than seven days.
8>
9> BACKUP INCREMENTAL LEVEL 0 FORMAT '/backups/admin/custpr/%d_bkp_df%t_Set%s_Piece%p'
10> DATABASE maxsetsize 33G
11> PLUS ARCHIVELOG FORMAT '/backups/admin/custpr/%d_bkp_al%t_Set%s_Piece%p'
12> delete all input;
Starting backup at 12/30/2008 22:01:40
current log archived
allocated channel: ORA_DISK_1
channel ORA_DISK_1: sid=11 devtype=DISK
channel ORA_DISK_1: starting archive log backupset
channel ORA_DISK_1: specifying archive log(s) in backup set
input archive log thread=1 sequence=8008 recid=7910 stamp=674638862
input archive log thread=1 sequence=8009 recid=7911 stamp=674671207
input archive log thread=1 sequence=8010 recid=7912 stamp=674697380
input archive log thread=1 sequence=8011 recid=7913 stamp=674780433
input archive log thread=1 sequence=8012 recid=7914 stamp=674784211
input archive log thread=1 sequence=8013 recid=7915 stamp=674863288
input archive log thread=1 sequence=8014 recid=7916 stamp=674863300
channel ORA_DISK_1: starting piece 1 at 12/30/2008 22:01:41
channel ORA_DISK_1: finished piece 1 at 12/30/2008 22:03:47
piece handle=/backups/admin/custpr/CUSTPR_bkp_al674863300_Set3083_Piece1 comment=NONE
channel ORA_DISK_1: backup set complete, elapsed time: 00:02:07
channel ORA_DISK_1: deleting archive log(s)
archive log filename=/custpr/arch/arch_custpr_8008.log recid=7910 stamp=674638862
archive log filename=/custpr/arch/arch_custpr_8009.log recid=7911 stamp=674671207
archive log filename=/custpr/arch/arch_custpr_8010.log recid=7912 stamp=674697380
archive log filename=/custpr/arch/arch_custpr_8011.log recid=7913 stamp=674780433
archive log filename=/custpr/arch/arch_custpr_8012.log recid=7914 stamp=674784211
archive log filename=/custpr/arch/arch_custpr_8013.log recid=7915 stamp=674863288
archive log filename=/custpr/arch/arch_custpr_8014.log recid=7916 stamp=674863300
Finished backup at 12/30/2008 22:03:47
Starting backup at 12/30/2008 22:03:47
using channel ORA_DISK_1
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of backup command at 12/30/2008 22:03:47
RMAN-06004: ORACLE error from recovery catalog database: ORA-00904: : invalid identifier
RMAN>
RMAN> ##BACKUP ARCHIVELOG ALL FORMAT '%d_bkp_al_%t_Set%s_Piece%p' delete input;
2>
3> # DELETE ARCHIVELOG UNTIL TIME 'SYSDATE-7';
4>
5> # check if database can be restored
6> # RESTORE DATABASE VALIDATE;
7>
8> # check if controlfile can be restored
9> ##RESTORE CONTROLFILE to '/backups/admin/custpr/custpr_bkp_cntlfile.ctl' VALIDATE;
10>
11> # check if archivelogs for the past two weeks can be restored
12> # RESTORE ARCHIVELOG FROM TIME 'SYSDATE-7' VALIDATE;
13>
14> # - Verify all backups on backup media are intact
15> # CROSSCHECK BACKUP OF DATABASE;
16>
17> # - Display a list of files that need to be backed up based on the retention
18> # policy. For this case study, files that don't have at least 1 backups
19> # will be reported.
20> REPORT NEED BACKUP;
RMAN retention policy will be applied to the command
RMAN retention policy is set to recovery window of 7 days
Report of files whose recovery needs more than 7 days of archived logs
File Days Name
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of report command at 12/30/2008 22:03:48
RMAN-06004: ORACLE error from recovery catalog database: ORA-00904: : invalid identifier
RMAN>
RMAN> # - delete un-necessary backups. This command deletes backups based on the
2> # retention policy.
3> ######### commented out DELETE OBSOLETE - TSM not configured to delete on 68
4> #########DELETE OBSOLETE;
5>
6> # - get complete list of existing backups
7> LIST BACKUP;
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of list command at 12/30/2008 22:03:49
RMAN-06004: ORACLE error from recovery catalog database: ORA-00904: : invalid identifier
RMAN>
RMAN> #-end of file-
2> **end-of-file**
RMAN>
Recovery Manager complete.

RMAN-06428 recovery catalog is not installed

Similar Messages

Maybe you are looking for