Oracle Error From Recovery Catalog Database Ora-06550
Answered by: Tom Kyte � Last updated: February 08, 2007 - 11:20 am UTC Category: Database � Version: 8.0.6/8.1.5 Whilst you are here, check out some content from the AskTom team: Problematic SQL ? PL/SQL is your friend. Latest Followup You Asked Dear Tom, Sorry for asking again about RMAN. I have 2 questions: 1.Can we create a catalog for a 8i version database in another oracle 8.0.x or 7.3.x database ? i-e I have a 8.1.5 database and 7.3.2 database. I want to backup 8.1.5 database using RMAN. Can I use Oracle 7.3 database to create recovery catalog for oracle 8i? (Is there any restrictions about oracle versions ?) 2.Suppose my datafile is of size 2 GB. Can I break this 2GB file in the backup pieces as (1GB+1GB)and store using RMAN in the backup form? (Since oracle8i supports exporting into multiple files, is it possible to break-up big file into small pieces using RMAN ? and we said... RMAN's recovery catalog should be in the release of the database that RMAN ships with. Since RMAN did not exist with 7.3 -- you would not be creating an RMAN catalog in 7.3. If you are using the 8.0 RMAN, it would be in an 8.0 database. If you are using the 8i RMAN, it would be in an 8.1 instance. This is the supported configuration. Part of recovery manager is a DBMS_* package and this package is stored only in the appropriate versioned database. for #2, not that I am aware of. It does image copies. You can use incremental backups which will result in smaller backup sets and files but eventually you need do a full. Reviews Write a Review catalog February 18, 2004 - 9:46 am UTC Reviewer: reader (1) I was under the impression that if i created a catalog in 8i then, i could manage version 8 databases using 8i catalog. Is it possible? Along the same line, If i created a catalog in 9i database can i store rman information for prior 9i databases in 9i catalog? Thanks. (2) Can I use 9i RMAN executable to backup 8i and 8 databases? Thanks. catalog February 23, 2004 - 9:34 pm UTC Reviewer: David I wanted to ask questions in line with the ones asked above. Could you answer those questions? Thanks. Followup February 24, 2004 - 6:31 am UTC rman is backwards compatible, yes. Any reason to use a 10g catalog versus a 9i catalog? May 28, 2004 - 5:53 pm UTC Reviewer: A reader I have a bunch of databases (both production and develop
CommunityOracle User Group CommunityTopliners CommunityOTN Speaker BureauJava CommunityError: You don't have JavaScript enabled. This tool uses JavaScript and much of it will not work correctly without it enabled. Please turn JavaScript back on and reload this page. Please enter a title. You can not post a blank message. Please type your message and try again. More discussions in Recovery Manager (RMAN) All PlacesDatabasePerformance & AvailabilityRecovery Manager (RMAN) This discussion is archived 5 Replies Latest reply on Sep 26, https://asktom.oracle.com/pls/asktom/f?p=100:11:0::::P11_QUESTION_ID:518622203320 2008 12:54 PM by 662120 Trying to register 10.2.0.3 db in Rec Catalog using OEM, getting errors 489554 Jan 30, 2008 10:19 PM Hi all, I didn't know whether to post this here in the RMAN forum or in the OEM Grid Control forum, but the issue is more related https://community.oracle.com/thread/614393 to RMAN, so I'll post it here, and hope someone can help me out! I have a new 10.2.0.3 database that I am getting configured to manage using OEM Grid Control. Through the OEM interface, I am trying to register this database with my recovery catalog - the recovery catalog is version 10.02.00.02. When I try to register this new db with the recovery catalog, I am getting this lengthy collection of errors: ------------------------------------------------------------------------------- Recovery Manager: Release 10.2.0.3.0 - Production on Wed Jan 30 14:58:36 2008 Copyright (c) 1982, 2005, Oracle. All rights reserved. RMAN> connected to target database: INSIGHT (DBID=4016731035) RMAN> connected to recovery catalog database PL/SQL package RMAN.DBMS_RCVCAT version 10.02.00.02 in RCVCAT database is not current PL/SQL package RMAN.DBMS_RCVMAN version 10.02.00.02 in RCVCAT database is not current RMAN> echo set on RMAN> register database; RMAN-00571: =========================================================== RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS =============== RMAN-00571: =========================================================== RMAN
I'm responsible for maintaining database systems mostly based on Real Application Clusters technology. My http://ivan.kartik.sk/index.php?controller=blog&action=view&tag=RMAN specialization is administration, design and consolidation of database platforms and other products running on Unix and Linux operating systems and during last years exploring the world of unstructured data. Became first Oracle certified RAC Expert in Slovakia. I've been an Oracle ACE since 2006.CategoriesOracle DatabaseLinuxSolarisHadoop and Big oracle error DataUncategorisedLatest postsACFS issue with latest UEK3 kernels on OEL 7/RHEL 7New package dependency for OPatch utilityUpgrade to 12c: Put a spotlight on Database clientA misleading error message...Oracle EM Cloud Control 12c: Oracle Agent Error UploadMaxDiskUsedPct: 98Redhat Enterprise Linux 7.2 and Oracle Enteprise Linux 7.2 releasedConfiguring automatic startup of oracle error from Oracle Database under systemd on RHEL 7/OEL 7/CentOS 7Be(a)ware of Licensing policy changes regarding Infrastructure Repository DatabasesJuly 2015 CPUs and PSUs releasedVirtualBox 5.0 released!PagesHomeChristian AntogniniFrits HooglandHector Rivera MadridHans ForbrichHarald van BreederodeJonathan LewisLuca CanaliMohamed HouriNicolas Gasparotto ACFS issue with latest UEK3 kernels on OEL 7/RHEL 7 02 June, 2016 One of my colleagues has been facing to weird behaviour of ACFS during installation of two nodes RAC on RHEL 7 and OEL7 (started on RHEL, then tried OEL). ACFS volume creation (during mkfs execution) one of the nodes has either hung or thrown error like this: mkfs.acfs: version = 12.1.0.2.0 mkfs.acfs: on-disk version = 39.0 mkfs.acfs: volume = /dev/asm/goldengate-32 mkfs.acfs: CLSU-00100: operating system function: ioctl failed with error data: 1 mkfs.acfs: CLSU-00101: operating system error message: Operation not permitted mkfs.acfs: CLSU-00103: error location: OI_0 mkfs.acfs: ACFS-00546: failed to change on-disk signature mkf