RMAN 10g/9i Compatibility

Hi,
I'm considering creating an RMAN repository on one of my 10g databases, but I would like to know if I will be able to use this same repository to manage RMAN backups for my 9i databases too?
In essence, is 10g RMAN backward compatible with 9i?
Thanks in advance.

This is the schema for 9i/10g (columns are target database,rman executable,catalog database,catalog schema):
9.2.0 | >=9.0.1.3 and <= Target database | > =8.1.7 | >= RMAN executable
10.1.0 | >=9.0.1.3 and <= Target database | > =9.0.1 | >= RMAN executable

Similar Messages

  • How to update host username/password in RMAN - 10g Enterprise manager bkp

    Hi,
    We have RMAN - 10g Enterprise manager scheduled.
    Last week we changed OS - Oracle password.
    Now backups are failing.
    Please let me know where to update Host username/password details in 10g Enterprise manager...

    it is showing sys credentials only.
    I see the following tips in Enterprise manager.
    "Normal credentials are used by Enterprise Manager functions that need operating system access but do not require administrator privileges. Privileged credentials are used by functions that do need administrator privileges. Database functions and jobs that require host credentials do not use the credentials set on this page; they instead use database-specific host credentials set on the Database Preferred Credentials page."
    Please let me know where can i set database-specific host credentials ?
    Message was edited by:
    user589334

  • RMAN 10G script examples

    Hi all,
    I plan to start using RMAN soon. After doing a lot of reading, I have a pretty good feel for how it works and the syntax.
    I'd appreciate getting some good example scripts that I can compare with mine. I realize I can compare with the DBA manual, but I'd rather see something that someone has been using successfully. Perhaps I'll use them as a starting point for my on RMAN scripts.
    If it makes a difference, we are at RMAN 10G and our server is Windows 2003.
    Thanks a bunch.

    Full Database backup
    rman
    connect rcvcat username/password@rmancat
    connect target username/password@target
    run {
    set command id to 'rman 10g database';
    allocate channel tape1 type 'SBT_TAPE' format '%d_full_%U';
    allocate channel tape2 type 'SBT_TAPE' format '%d_full_%U';
    allocate channel tape3 type 'SBT_TAPE' format '%d_full_%U';
    backup incremental level=0 tag="target_Level0_full" (database filesperset=25 include current controlfile);
    sql 'alter system archive log current';
    change archivelog all validate;
    backup filesperset 5 archivelog all;
    backup current controlfile format '%d_cf_%U';
    release channel tape1;
    release channel tape2;
    release channel tape3;
    Archive log backup and delete
    rman
    connect rcvcat username/password@rmancat
    connect target username/password@target
    run {
    set command id to 'rman 10g archive backup';
    allocate channel tape1 type 'SBT_TAPE' format '%d_full_%U';
    allocate channel tape2 type 'SBT_TAPE' format '%d_full_%U';
    allocate channel tape3 type 'SBT_TAPE' format '%d_full_%U';
    sql "alter system archive log current";
    backup tag="target_Level0_arch" filesperset 10 archivelog until time 'sysdate - 1/24' delete input;
    release channel tape1;
    release channel tape2;
    release channel tape3;
    }

  • Oracle 9i lite & 10g lite compatibility issue

    Hi,
    Can anyone tell me if there is a compatibility issue between oracle lite 9i and 10g lite. We are currently developing a window mobile 5.0 application in C# and our client is using a 9i oracle database. We want to directly connect to the database but based on what I search on the forums that CF oracle DtaAdapter only available in the 10g lite version. based on this link:
    http://blog.opennetcf.org/ncowburn/OracleLite10gADONETProviderForWindowsCEPocketPC.aspx
    Can anyone shead some ligth here, any help will be highly appreciated....
    Thank you,

    I connect to the database through the same user that created those tables. Do I still need a public synonym ?

  • Can RMAN 10g Keep Log of Backup History?

    hi experts,
    I use RMAN to backup my 10g database on a Windows Server.
    Not using Recovery Catalog.
    Database IS in Archivelog mode.
    I have the settings configured so that backups become obsolete after 10 days.
    ** But the auditors want to be able to see evidence that we were doing daily backups - so we need to keep 180 days of "history" even though the actual backup files have long since been deleted.
    ??How can I accomplish this? Is setting CONTROL_FILE_RECORD_KEEP_TIME = 180 a good optiion?
    Thanks, John

    Steve, not sure what may have prompted some of your questions but I will answer those that I can.
    No, the idea of a log is not new to me.
    Sure I keep the backups for the control file in the FRA. I also have the control file on 2 different physical disks so that if a disk fails or if I accidentally delete one, the other is still available. Yes I have AUTOBACKUP enabled. Any type of backup triggers a backup of the control file as well. I was able to restore the control file as recently as 2 weeks ago.
    I don't use a Recovery catalog because I dont yet fully understand them. At this time, I'm more comfortable not using one.
    I'm sure there are bettter backup strategies for 10g. But I've been able to restore when I needed to..... so far.
    That said... I'm always ready to learn and make improveemnts.
    Thanks, John

  • Ora 10g client compatibility

    Accessing Oracle 8.1.7.3 databases with a 10.1. Client produces an ORA-03134 error - access to a server version not supported any more.
    Where can I find which versions are supported - the documentation that comes with the client says nothing about it.
    Michael

    This compatibility matrix:
    https://support.oracle.com/CSP/main/article?cmd=show&type=NOT&id=207303.1
    "#2 - An ORA-3134 error is incorrectly reported if a 10g client tries to connect to an 8.1.7.3 or lower server. See Note:3437884.8 . "
    Yes, we're still migrating things from 8i - I know it's 2010, but we weren't in any hurry...

  • 10g Backup Compatibility

    I have a RMAN backup of 10g R2 database and using this backup I want the database to be duplicated in 11g on a different system. But RMAN 11g refuses to connect to 10g Database and error is that it is not compatible. I have a cold backup and tried to manually recover database in 11g but when I tried to mount the database it says that control file is of older version and is not compatible. As for as I knew Oracle is backward compatible and I have done manual recovery of 8i into 9i and 9i to 10g. Can anyone tell what's wrong here?

    Upon running the script above I got the following.
    SQL> @C:\app\imran.haider\product\11.1.0\db_1\RDBMS\ADMIN\catupgrd.sql
    DOC>#######################################################################
    DOC>#######################################################################
    DOC>
    DOC> The first time this script is run, there should be no error messages
    DOC> generated; all normal upgrade error messages are suppressed.
    DOC>
    DOC> If this script is being re-run after correcting some problem, then
    DOC> expect the following error which is not automatically suppressed:
    DOC>
    DOC> ORA-00001: unique constraint (<constraint_name>) violated
    DOC> possibly in conjunction with
    DOC> ORA-06512: at "<procedure/function name>", line NN
    DOC>
    DOC> These errors will automatically be suppressed by the Database Upgrade
    DOC> Assistant (DBUA) when it re-runs an upgrade.
    DOC>
    DOC>#######################################################################
    DOC>#######################################################################
    DOC>#
    DOC>######################################################################
    DOC>######################################################################
    DOC> The following statement will cause an "ORA-01722: invalid number"
    DOC> error if the user running this script is not SYS. Disconnect
    DOC> and reconnect with AS SYSDBA.
    DOC>######################################################################
    DOC>######################################################################
    DOC>#
    no rows selected
    DOC>######################################################################
    DOC>######################################################################
    DOC> The following statement will cause an "ORA-01722: invalid number"
    DOC> error if the database server version is not correct for this script.
    DOC> Shutdown ABORT and use a different script or a different server.
    DOC>######################################################################
    DOC>######################################################################
    DOC>#
    no rows selected
    DOC>#######################################################################
    DOC>#######################################################################
    DOC> The following statement will cause an "ORA-01722: invalid number"
    DOC> error if the database has not been opened for UPGRADE.
    DOC>
    DOC> Perform a "SHUTDOWN ABORT" and
    DOC> restart using UPGRADE.
    DOC>#######################################################################
    DOC>#######################################################################
    DOC>#
    no rows selected
    DOC>#######################################################################
    DOC>#######################################################################
    DOC> The following statement will cause an "ORA-01722: invalid number"
    DOC> error if the Oracle Database Vault option is TRUE. Upgrades cannot
    DOC> be run with the Oracle Database Vault option set to TRUE since AS
    DOC> SYSDBA connections are restricted.
    DOC>
    DOC> Perform a "SHUTDOWN ABORT", relink the server without the Database
    DOC> Vault option (but with the OLS option), and restart the server using
    DOC> UPGRADE.
    DOC>#######################################################################
    DOC>#######################################################################
    DOC>#
    no rows selected
    DOC>#######################################################################
    DOC>#######################################################################
    DOC> The following statement will cause an "ORA-01722: invalid number"
    DOC> error if Database Vault is installed in the database but the Oracle
    DOC> Label Security option is FALSE. To successfully upgrade Oracle
    DOC> Database Vault, the Oracle Label Security option must be TRUE.
    DOC>
    DOC> Perform a "SHUTDOWN ABORT", relink the server with the OLS option
    DOC> (but without the Oracle Database Vault option) and restart the server
    DOC> using UPGRADE.
    DOC>#######################################################################
    DOC>#######################################################################
    DOC>#
    no rows selected
    DOC>#######################################################################
    DOC>#######################################################################
    DOC> The following statement will cause an "ORA-01722: invalid number"
    DOC> error if bootstrap migration is in progress and logminer clients
    DOC> require utlmmig.sql to be run next to support this redo stream.
    DOC>
    DOC> Run utlmmig.sql
    DOC> then (if needed)
    DOC> restart the database using UPGRADE and
    DOC> rerun the upgrade script.
    DOC>#######################################################################
    DOC>#######################################################################
    DOC>#
    no rows selected
    DOC>#######################################################################
    DOC>#######################################################################
    DOC> The following statement will cause an "ORA-01722: invalid number"
    DOC> error if the current timezone version file is not the same as the
    DOC> version in the database to be upgraded. The statement will cause an
    DOC> ORA-00942 or ORA-00904 error if the pre-upgrade utility (utlu111i.sql)
    DOC> has not be run to update registry$database table to include the existing
    DOC> database timezone file version.
    DOC>
    DOC> Shutdown ABORT and revert to the original ORACLE_HOME. Then apply
    DOC> the required timezone version patch to the original ORACLE_HOME
    DOC> prior to attempting to upgrade. Re-run utlu111i.sql after applying
    DOC> the patch to record the new timzone file version in the
    DOC> registry$database table.
    DOC>
    DOC>#######################################################################
    DOC>#######################################################################
    DOC>#
    FROM registry$database
    ERROR at line 2:
    ORA-00942: table or view does not exist
    Disconnected from Oracle Database 11g Enterprise Edition Release 11.1.0.6.0 - Production
    With the Partitioning, OLAP, Data Mining and Real Application Testing options

  • 10g - 9i Compatibility

    Hi,
    New to oracle and had a question regarding compatibility between 9i and 10g;
    If I create an export file from Oracle 10g and send this file to a client; can the client import the file if he is running Oracle 9i. Would there be issues?
    Thanks in advance

    What if you do not have the 9i install? Only 10g
    install.
    Client has 9i onlyYou can download and install 9i client software on one of your machines and do export using it. Also check the exact version of your Client's 9i. For example, if he's on 9.1.0.4 you can't use 9.2.0.1 to do export. You need to use version lower than his.

  • X2-10GB-LRM to SFP-10G-SR= Compatibility

    Hi,
    Can you help me in this ?
    I have two 10Gig modules.
    On 6500, i have X2-10GB-LRM  and on 3750-x i have SFP-10G-SR= .
    you can use it with fiber cable and patch cord to connect the two devices?
    thanks

    Hello,
    SFP-10G-SR is a MMF and it uses a LC duplex connector.
    X2-10GB-LRM is also a MMF and it uses LC duplex connector.
    so they are compatible.
    Link
    Under 6xxx series switches you will both transceivers as part of the supported devices.
    http://www.cisco.com/en/US/docs/interfaces_modules/transceiver_modules/compatibility/matri/OL_6974.html#wp99798
    Under 3xxx series switches:
    http://www.cisco.com/en/US/docs/interfaces_modules/transceiver_modules/compatibility/matri/OL_6974.html#wp48759
    Link for 10GBASE X2 modules:
    http://www.cisco.com/en/US/prod/collateral/modules/ps5455/ps6574/product_data_sheet0900aecd801f92aa.html
    10 transceiver modules compatibility matrix:
    http://www.cisco.com/en/US/docs/interfaces_modules/transceiver_modules/compatibility/matrix/OL_6974.html
    Look for Table 1 10-Gigabit Ethernet Transceiver Module Models
    Thank,
    Haihua

  • 9i and 10g backward compatibility

    We are thinking of trying out Oracle 10g. We are currently using 9i and have written Java apps that work against 9i using the JDBC drivers provided by Oracle. We would like to know if these apps will work perfectly against 10g without any changes if we use the new 10g JDBC drivers.
    Thanks.

    We are thinking of trying out Oracle 10g. We are
    currently using 9i and have written Java apps that
    work against 9i using the JDBC drivers provided by
    Oracle. We would like to know if these apps will
    work perfectly against 10g without any changes if we
    use the new 10g JDBC drivers.
    Thanks.We make OrindaBuild, a JDBC access code generator for PL/SQL. We found a series of minor behaviour changes when we ported it to 10g, such as:
    * In oracle 9i retrieving a NULL value for any of the datatypes TIMESTAMP, TIMESTAMP WITH TIME ZONE or TIMESTAMP WITH LOCAL TIME ZONE would result in a matching but empty java object being returned. In 10g null is returned instead, which means that existing code may suddenly start to generate java.lang.NullPointerException Exceptions when the driver is upgraded.
    * Prior to Oracle 10.1.0 DATE columns were returned as java.sql.TimeStamp objects. In Oracle 10G they come back as java.sql.Date objects.
    * Get Cursor Closed message when attempting to retrieve a cursor a second time. Prior to 10.1.0 Oracle returned a zero-length cursor.
    None of the above are bugs but you are going to have to test your app and possibly make minor code changes. Do not assume the new driver will work 'out of the box'.
    David Rolfe
    Orinda Software
    Dublin, Ireland
    www.orindasoft.com

  • RMAN Catalog Version compatibility

    Hi,
    I have 11.1.0.7 database and RMAn repository version is 10.2.0.4 and i am receiving following error
    PL/SQL package RMAN.DBMS_RCVCAT version 10.02.00.04 in RCVCAT database is too old
    RMAN-00571: ===========================================================
    RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
    RMAN-00571: ===========================================================
    RMAN-03002: failure of resync command at 02/01/2010 14:04:02
    RMAN-06429: RCVCAT database is not compatible with this version of RMAN
    So does it means i need to have RMAN repository at least 11.2.0.7? Is there a work around to resolve this issue so that i can use my current 10.2.0.4 repository for backing up my 11 g databases.
    Thanks

    If you have another database which is using 10.2.0.4 then using the rman executable for this database connect to your 11.1.0.7 database and recovery catalog. Then run the backup.
    Regards
    Asif Kabir

  • Extracting Backups Sets from ASM with RMAN (10g)

    If I backup my database to my flash recovery area in ASM using RMAN, can I then extract those backup sets from ASM and turn them into normal file system files?
    I think I read that you can do this but I just wanted to be sure. I don't need super detail on this, just get me pointed in the right direction.
    I've certainly read about extracting a database from ASM, but I'm just not sure how I'd migrate an individual, arbitrary file.

    http://www.oracle.com/technology/oramag/oracle/04-nov/o64rman.html#T2 describes something like this, in the "Adding ASM" section. Here's the excerpt:
    Files inside an ASM location are not accessible as operating system files. To get the backups and archived logs from the ASM disk group to regular disks and tapes, John will use RMAN to back up the recovery area from ASM to tape (at the network backup server) through the following command:
    BACKUP RECOVERY AREA;
    This backs up the entire recovery area, including data file backups, archived logs, and control file backups from the ASM disk group to the tape.
    So, this would lead us to believe that what we want can be done. However, I read somewhere in the RMAN doc that BACKUP RECOVERY AREA will only create a backup to an sbt (i.e. tape) device. That is, it would appear that RMAN cannot store backups in ASM, and also allow you to "export" them to disk. You can export to tape, but not to disk.
    This is disconcerting. I'd like to store all Oracle-related files under ASM, but I'd also like to allow our tape backup procedures (which I am not in control of, and which do more than just backup Oracle) to easily just grab OS files that I put out there.

  • SFP-10G-LR and SFP-10G-LRM Compatibility

    Hello,
    Has anyone had success/experience running across OS2 SM with a SFP-10G-LR at one end and a SFP-10G-LRM at the other, where the total link length is <300m?
    Thanks,
    Andrew

    Dear Dima L,
    I will check this tomorrow... but expect the same error.
    Regards,
    Manuel

  • RMAN 10g new incremental features compression issue

    Hi,
    I'm testing block change tracking and fast incremental but, come to an issue with compressed level 0 backupsets and uncompressed level 1.
    I've run:
    connect target;
    backup as compressed backupset INCREMENTAL LEVEL 0 TAG = WEEKLY DATABASE;
    exit;
    on 500GB database ,and the backupset was about 90GB.
    But now I'm trying :
    RMAN> BACKUP INCREMENTAL LEVEL 1 FOR RECOVER OF COPY WITH TAG WEEKLY DATABASE;
    Starting backup at 2008-02-20 22:27:34
    allocated channel: ORA_DISK_1
    channel ORA_DISK_1: sid=367 devtype=DISK
    no parent backup or copy of datafile 7 found
    no parent backup or copy of datafile 29 found
    no parent backup or copy of datafile 42 found
    no parent backup or copy of datafile 56 found
    no parent backup or copy of datafile 19 found
    no parent backup or copy of datafile 61 found
    no parent backup or copy of datafile 83 found
    no parent backup or copy of datafile 77 found
    no parent backup or copy of datafile 92 found
    no parent backup or copy of datafile 105 found
    and don't know how oracle manage to 'merge' level 0 compressed backup and level 1 uncompressed backup. For me it looks like the level 1 is equal to level 0 .
    BTW that database was not used at all so I was expecting to almost 0 size incrementals.
    The next step should be :
    RECOVER COPY OF DATABASE
    WITH TAG WEEKLY;
    but I've give up as totaly confused :).
    Any explanation would be great.
    There is a lot of myth about new features behaviour.
    Best Regards.
    Grzegorz

    You are mixing 2 independent features , compression and incrementally updated backups. Talking about incrementally updated backups,this is a working script:
    run {
    recover copy of database with tag 'incr_update'';
    backup incremental level 1 for recover of copy with tag 'incr_update' database;
    You don't start the process with 'backup database ..'. How it works:
    In the first run 'recover copy...' does anything,because there's no backup to recover.
    'backup incremental...' creates image copies (not a backupset) of all datafiles,image copies are never compressed.
    In the second run 'recover copy...' still does nothing,because we still have no backup. 'backup incremental...' now creates an incremental backup , that may be compressed or not compressed. I've set 'compressed' as permanent parameter,so it's not included in the command.
    In the third (and all following) run 'recover copy...' now applies the incremental backups taken in the previous run to the image copies. 'backup incremental...' creates a new incremental backup, again this can be compressed or not.
    Werner

  • Document for upgrading 8i to 10g using RMAN backup

    hi
    I need to restore a 8i database on a server and then wanted to upgrade it to 10g.
    Is there any good documentation available ?

    RMAN won't perfom upgrade. You'll have to resotore your database using the Recovery Manager reference manual 8i: http://download-west.oracle.com/docs/cd/A87860_01/doc/server.817/a76990/toc.htm . (Watch out, the above mentioned reference is for RMAN 10g, there were many differences between 8i and 10g, if you try to use 10g syntax on an 8i rman it will partially work or won't work at all)
    Install 8i on your target OS.
    Restore/Recover with rman 8i your 8i rman backup.
    Your rman backup must be located at the same path where it was when you obtained it on your source OS.
    Once you have made sure it opens, proceed with upgrade.
    Read upgrade guide for an specific upgrade procedure for 8i->10g.

Maybe you are looking for