RMAN  catalog/controlfile

Gurus ,
please clarify me below things
thanks for great help .. .
1) can rman backup information will be stored in both controlfile and catalog db at a time ? ( if target db is registered in catalog db)
2) how to know if db is only using controlfile for storing rman backup operations.
3) how to check if database is configured to use catalog db for rman operations ?
4) rman backup database plus archivelog;
will this command backups only archivelogs after start of backup operation (or) backup older files also which exists in archive destination.
Thanks
raj

1. RMAN Backup information is always written to the controlfile. If you are using a catalog, it will be written to the catalog in addition to the controlfile --- i.e. to both locations. However, retention of information in the controlfile is generally subject to the lower of controlfile_record_keep_time or the number of slots available in the controlfile while retention of information in the catalog can be and is generally much larger.
2. You can't know, from the database itself, whether it is writing to catalog schema or not. You can query the database's V$ views for information that is in the controlfile.
3. The database doesn't store information about whether a catalog is being used or not -- it doesn't know. You have to connect to the catalog to query for information about the target database's backups.
Remember : When you start RMAN, you must explicitly provide the CATALOG location (username/password@catalog_instance) otherwise, the default is NOCATALOG.
4. BACKUP DATABASE PLUS ARCHIVELOG will also backup Archivelogs that are present and were generated before the database backup began.
Hemant K Chitale

Similar Messages

  • Controlfile vs. RMAN Catalog

    Hey, my controlfile is increasing really fast. So I have to recreate the the controlfile on a regular basis. Its growing nearly 150 MB in one month.
    Therefore the backups are getting slow, also a logswitch is impacting my database performance. I am using a physical standby so the db parameter archive_lag_target is set to 600 (sec), so every 10 minutes a logswitch occurs.
    v$controlfile_record_section is showing archivelogs are the most space consuming part.
    Now the question:
    Is it an appriopate way to switch from controlfile to rman catalog ? Will this help me to keep the controlfile tiny ?
    Chris

    Hi Christian,
    Why is the size of the controlfile a problem for you?
    There are other points to keep in mind if you use controlfile or rman catalog.
    For example if you would like to use standby databases so Oracle recommend to use an rman catalog.
    For me it is not a problem of the size it is your decision to make a matrix and look about the pros and cons
    between controlfile and rman catalog.
    But if it is a production environment it is a good idea to use a rman catalog.
    regards
    SPA2

  • Query RMAN catalog to view my controlfile backup in backup piece

    version: 11.1.0.7
    We need to restore an year old database and its backup is availble in TAPE, RMAN directly takes backup to TAPE.
    we have dropped the database, Now there is a requirement to restore the database.
    we Know DBID, I can restore the db once i can restore the contolfile.
    However we did not have controlfile auto backup. whenever there is FULL/incremental backup cotnrolfile is included in that backup. now we have the rman catalog for that database. so How I can query rman catalog to find which backup piece containing the latest controlfile? once we know the backuppiece info, we can restore controlfile from that piece
    any help on this?

    user8860934 wrote:
    version: 11.1.0.7
    We need to restore an year old database and its backup is availble in TAPE, RMAN directly takes backup to TAPE.
    we have dropped the database, Now there is a requirement to restore the database.
    we Know DBID, I can restore the db once i can restore the contolfile.
    However we did not have controlfile auto backup. whenever there is FULL/incremental backup cotnrolfile is included in that backup. now we have the rman catalog for that database. so How I can query rman catalog to find which backup piece containing the latest controlfile? once we know the backuppiece info, we can restore controlfile from that piece
    any help on this?Connect with recovery catalog through rman and
    set dbid <yourdbid>
    list backup of controlfile;In this case you will see all backups of controlfile.And according time this backup you can restore database using
    rman>restore controlfile from 'backupset_location';

  • New RMAN catalog in existing EMREP database - new user and tablespace?

    Hi all,
    I am FINALLY getting "with the times" and trying to get my databases to back up with RMAN. I already have a dedicated server that is running Oracle Enterprise Manager 10g Grid Control, so it already has the OMS database on it, called EMREP. I was hoping to just use this database as my RMAN catalog, is that considered good practice or not?
    So assuming this practice is considered OK, I know that I need to create a new user (which I'll just call RMAN) in this database. Would it be best to also create a separate tablespace for this user? I have no idea how big I should expect this RMAN schema to get. I'm sure it all depends on the number of databases I'm backing up, but can anyone give me some realistic size expectations that I could start with?
    Any advice/info is greatly appreciated!

    I think that the catalog is only applicable if you will have several databases to manage.
    If you he will have only one, I dont see necessity to use the catalog, therefore with backups of controlfiles only, you can to execute the tasks of backup/restore/recovery.
    But, for catalog creation information, see
    RMAN CATALOG CREATION STEP BY STEP by Joel Pérez
    RMAN ( CATALOG CREATION ) STEP BY STEP by Joel Pérez
    Message was edited by:
    ARF

  • Need a create db script to manually create a 10g rman catalog db on unix

    Hi, Gurus:
    I would like to manually create a rman catalog database (Oracle 10g) on a HP-UX environment. Could anyone share a sql script to do that?
    It is going to be used to backup about 15 databases directly to tape and the retention policy is going to be 35 days. How big the database should be?
    Thanks in advance.

    I can't find any documentation supporting Oracle support's theory.And who writes the Oracle documentation? People in this forum?
    You got the "Best Practice" advise.
    If you have rman catalog on the same server or on the same database, it is like storing your backup on the same server you took it from.
    So, the idea od RMAN catalog is to have your catalog available for any recovery. If you cannot recover your recovery catalog, then you are better off using the controlfile as the repository.

  • Set RMAN catalog default setting for all databases

    Hi,
    I am running a 11gR1 RMAN catalog.
    I am wondering if is it possible to change a default configuration setting in the RMAN catalog  so that all the new databases will inherit it.
    For example, I would like all the new databases registered to the catalog to have:
    BACKUP OPTIMIZATION ON
    RETENTION POLICY TO REDUNDANCY 7
    Thanks,
    massi

    No, the catalog cannot "dictate" configurations for databases.  Each database retains configuration in the controlfile and this can be updated only by an rman connection (i.e. rman connecting to the database as a target). The CONFIGURE command in rman is used to set a "permanent" configuration parameter for a database but must be issued for each database individually.
    Hemant K Chitale

  • Rman catalog files

    We have 11g rac one node implemented on windows 2008, i took complete backup using rman from the production database and I copied the files to the test server and when am doing
    restore database validate it is still pointing to production backup location :
    c:\rman\ (test location)
    e:rman (production location)
    Am getting the error :
    channel ORA_DISK_1: reading from backup piece E:\RMAN\DATA_80_1_2GN1OG02_1_1.BAK
    channel ORA_DISK_2: reading from backup piece E:\RMAN\DATA_81_1_2HN1OG03_1_1.BAK
    Wondering why am getting the above error as I didn't catalog any backup piece on that location and the location is taken from production.
    test worklog
    RMAN> restore controlfile from 'C:\rman\DATA_82_1_2IN1OG3N_1_1.BAK';
    Starting restore at 26-JAN-12
    using channel ORA_DISK_1
    channel ORA_DISK_1: restoring control file
    channel ORA_DISK_1: restore complete, elapsed time: 00:00:03
    output file name=C:\APP\ADMINISTRATOR\ORADATA\medt\CONTROL\CONTROL01.CTL
    output file name=C:\APP\ADMINISTRATOR\ORADATA\medt\CONTROL\CONTROL02.CTL
    Finished restore at 26-JAN-12
    RMAN> catalog backuppiece 'C:\rman\DATA_73_1_29N1OG00_1_1.BAK';
    released channel: ORA_DISK_1
    cataloged backup piece
    backup piece handle=C:\RMAN\DATA_73_1_29N1OG00_1_1.BAK RECID=34 STAMP=773622357
    RMAN> catalog backuppiece 'C:\rman\'DATA_74_1_2AN1OG00_1_1.BAK';
    RMAN-00571: ===========================================================
    RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
    RMAN-00571: ===========================================================
    RMAN-00558: error encountered while parsing input commands
    RMAN-01009: syntax error: found "identifier": expecting one of: "comma, ;"
    RMAN-01008: the bad identifier was: DATA_74_1_2AN1OG00_1_1
    RMAN-01007: at line 1 column 31 file: standard input
    RMAN> catalog backuppiece 'C:\rman\DATA_74_1_2AN1OG00_1_1.BAK';
    cataloged backup piece
    backup piece handle=C:\RMAN\DATA_74_1_2AN1OG00_1_1.BAK RECID=35 STAMP=773622388
    RMAN> catalog backuppiece 'C:\rman\DATA_75_1_2BN1OG00_1_1.BAK';
    cataloged backup piece
    backup piece handle=C:\RMAN\DATA_75_1_2BN1OG00_1_1.BAK RECID=36 STAMP=773622401
    RMAN> catalog backuppiece 'C:\rman\DATA_76_1_2CN1OG01_1_1.BAK';
    cataloged backup piece
    backup piece handle=C:\RMAN\DATA_76_1_2CN1OG01_1_1.BAK RECID=37 STAMP=773622413
    RMAN> catalog backuppiece 'C:\rman\DATA_77_1_2DN1OG02_1_1.BAK';
    cataloged backup piece
    backup piece handle=C:\RMAN\DATA_77_1_2DN1OG02_1_1.BAK RECID=38 STAMP=773622427
    RMAN> catalog backuppiece 'C:\rman\DATA_78_1_2EN1OG02_1_1.BAK';
    cataloged backup piece
    backup piece handle=C:\RMAN\DATA_78_1_2EN1OG02_1_1.BAK RECID=39 STAMP=773622439
    RMAN> catalog backuppiece 'C:\rman\DATA_79_1_2FN1OG02_1_1.BAK';
    cataloged backup piece
    backup piece handle=C:\RMAN\DATA_79_1_2FN1OG02_1_1.BAK RECID=40 STAMP=773622501
    RMAN> catalog backuppiece 'C:\rman\DATA_80_1_2GN1OG02_1_1.BAK';
    cataloged backup piece
    backup piece handle=C:\RMAN\DATA_80_1_2GN1OG02_1_1.BAK RECID=41 STAMP=773622513
    RMAN> catalog backuppiece 'C:\rman\DATA_81_1_2HN1OG03_1_1.BAK';
    cataloged backup piece
    backup piece handle=C:\RMAN\DATA_81_1_2HN1OG03_1_1.BAK RECID=42 STAMP=773622525
    RMAN> catalog backuppiece 'C:\rman\DATA_82_1_2IN1OG3N_1_1.BAK';
    cataloged backup piece
    backup piece handle=C:\RMAN\DATA_82_1_2IN1OG3N_1_1.BAK RECID=43 STAMP=773622546
    RMAN> catalog backuppiece 'C:\rman\DATA_83_1_2JN1OG3N_1_1.BAK';
    cataloged backup piece
    backup piece handle=C:\RMAN\DATA_83_1_2JN1OG3N_1_1.BAK RECID=44 STAMP=773622560
    RMAN> catalog backuppiece 'C:\rman\DATA_84_1_2KN1OG75_1_1.BAK';
    cataloged backup piece
    backup piece handle=C:\RMAN\DATA_84_1_2KN1OG75_1_1.BAK RECID=45 STAMP=773622574
    RMAN> restore database validate;
    Starting restore at 26-JAN-12
    allocated channel: ORA_DISK_1
    channel ORA_DISK_1: SID=350 device type=DISK
    allocated channel: ORA_DISK_2
    channel ORA_DISK_2: SID=407 device type=DISK
    allocated channel: ORA_DISK_3
    channel ORA_DISK_3: SID=466 device type=DISK
    allocated channel: ORA_DISK_4
    channel ORA_DISK_4: SID=524 device type=DISK
    allocated channel: ORA_DISK_5
    channel ORA_DISK_5: SID=582 device type=DISK
    allocated channel: ORA_DISK_6
    channel ORA_DISK_6: SID=640 device type=DISK
    channel ORA_DISK_1: starting validation of datafile backup set
    channel ORA_DISK_2: starting validation of datafile backup set
    channel ORA_DISK_3: starting validation of datafile backup set
    channel ORA_DISK_4: starting validation of datafile backup set
    channel ORA_DISK_5: starting validation of datafile backup set
    channel ORA_DISK_6: starting validation of datafile backup set
    channel ORA_DISK_1: reading from backup piece E:\RMAN\DATA_80_1_2GN1OG02_1_1.BAK
    channel ORA_DISK_2: reading from backup piece E:\RMAN\DATA_81_1_2HN1OG03_1_1.BAK
    channel ORA_DISK_3: reading from backup piece C:\RMAN\DATA_76_1_2CN1OG01_1_1.BAK
    channel ORA_DISK_4: reading from backup piece C:\RMAN\DATA_77_1_2DN1OG02_1_1.BAK
    channel ORA_DISK_5: reading from backup piece C:\RMAN\DATA_78_1_2EN1OG02_1_1.BAK
    channel ORA_DISK_6: reading from backup piece C:\RMAN\DATA_79_1_2FN1OG02_1_1.BAK
    channel ORA_DISK_1: errors found reading piece handle=E:\RMAN\DATA_80_1_2GN1OG02
    _1_1.BAK
    channel ORA_DISK_1: failover to piece handle=C:\RMAN\DATA_80_1_2GN1OG02_1_1.BAK
    tag=TAG20120126T174849
    channel ORA_DISK_1: restored backup piece 1
    channel ORA_DISK_1: validation complete, elapsed time: 00:00:46
    channel ORA_DISK_2: errors found reading piece handle=E:\RMAN\DATA_81_1_2HN1OG03
    _1_1.BAK
    channel ORA_DISK_2: failover to piece handle=C:\RMAN\DATA_81_1_2HN1OG03_1_1.BAK
    tag=TAG20120126T174849
    channel ORA_DISK_2: restored backup piece 1
    channel ORA_DISK_2: validation complete, elapsed time: 00:00:56
    channel ORA_DISK_6: piece handle=C:\RMAN\DATA_79_1_2FN1OG02_1_1.BAK tag=TAG20120
    126T174849
    channel ORA_DISK_6: restored backup piece 1
    channel ORA_DISK_6: validation complete, elapsed time: 00:01:26
    channel ORA_DISK_3: piece handle=C:\RMAN\DATA_76_1_2CN1OG01_1_1.BAK tag=TAG20120
    126T174849
    channel ORA_DISK_3: restored backup piece 1
    channel ORA_DISK_3: validation complete, elapsed time: 00:01:36
    channel ORA_DISK_5: piece handle=C:\RMAN\DATA_78_1_2EN1OG02_1_1.BAK tag=TAG20120
    126T174849
    channel ORA_DISK_5: restored backup piece 1
    channel ORA_DISK_5: validation complete, elapsed time: 00:01:36
    channel ORA_DISK_4: piece handle=C:\RMAN\DATA_77_1_2DN1OG02_1_1.BAK tag=TAG20120
    126T174849
    channel ORA_DISK_4: restored backup piece 1
    channel ORA_DISK_4: validation complete, elapsed time: 00:02:07
    Finished restore at 26-JAN-12Kai

    Those "prod" locations are found in the backup controlfile:
    >
    RMAN> restore controlfile from 'C:\rman\DATA_82_1_2IN1OG3N_1_1.BAK';
    >
    >
    channel ORA_DISK_1: errors found reading piece handle=E:\RMAN\DATA_80_1_2GN1OG02
    _1_1.BAK
    channel ORA_DISK_1: failover to piece handle=C:\RMAN\DATA_80_1_2GN1OG02_1_1.BAK
    tag=TAG20120126T174849
    >
    You can see how RMAN noticed it couldn't find that piece and then found one that you had previously cataloged. Looks good to me.

  • RMAN Backup using Rman Catalog

    Hi
    can we take backup of oracle9i database using oracle10g RMAN Catalog?
    Thanks
    With Regards
    OH

    I guess this is related to backward compatibility support principle. Target database's controlfile and RMAN catalog is synchronized and different version may have different structure and feature. When we need to completely restore an Oracle instance from backup, RMAN catalog must be able to support target database, and it may not be possible if RMAN catalog version is lower than target database. I hope I get the message across.
    Pls anybody correct me if I am wrong

  • Backup rman catalog

    Hi
    my RMAN catalog db is is non archive log mode
    and we never back it up
    for better protection , i will convert it to archive mode and hotbackup it and use controlfile as catalog
    am i in the right way to backup my rman catalog db?
    Thanks

    user9145417 wrote:
    Hi
    my RMAN catalog db is is non archive log mode
    and we never back it up
    for better protection , i will convert it to archive mode and hotbackup it and use controlfile as catalog
    am i in the right way to backup my rman catalog db?
    Yes , you should take a hot backup of catalog DB and also configure controlfile auto backup.
    Regards
    Rajesh

  • How to restore the control fie? without having RMAN catalog.

    Hi ,
    can anyone help me out here.???
    How can i restore the control file.if i dont have the RMAN catalog.
    Please provide me steps that'll be helpful. I am frsher in oracle DBA
    Please mail me: [email protected]
    Regards
    Vikas Singh

    Hi Vikas,
    You can restore the control if you have the full backup of your database in some location.
    Lets assume you have the full backup piecs in loc "/u02/backup/..bkp"
    steps:
    shut abort;
    startup nomount;
    catalog start with "/u02/backup/..bkp"
    restore spfile from '/u02/backup/..bkp";
    restore controlfile from "/u02/backup/..bkp"
    shut immediate;
    startup mount;
    alter database open;
    Once the db is up with controlfile immediately take the full database backup of your database.
    Let me know having issue after following this.
    -- rohit
    http://dbarohit.blogspot.in/

  • Unregister from rman catalog

    Dear All,
    Currently our production backup is done by rman with catalog database. But I want to decommission it. I want to use the target database controlfile only for rman backup.
    what is the right approach to configure it?

    Currently our production backup is done by rman with catalog database. But I want to decommission it. I want to use the target database controlfile only for rman backup.
    what is the right approach to configure it?No ned to confiugre, while connecting to RMAN or in backupjob scripts just do not mention catalog connectivity.
    If any old backups available then register them with controlfile..
    in case of catalog :-
    rman target sys/****@prod catalog rman/rman@catlog
    in case of no-catalog:
    rman target sys/****@prod
    to register old backups:-
    RMAN> catalog start with 'location of backups';

  • SQL Reports Bad Idea Against RMAN Catalog?

    11.2.0.1 SPARC 64
    We use OEM to manage/execute our backups. The MML is NetBackup. One downside to this is that the "job" within OEM executes the backup for 20+ databases. In a serial fashion the backups occur in NetBackup...but most are queued - they throttle through and over time they complete. To this end, we have no way of seeing the true backup duration. We know the rman start and completion times, but they're not "actual."
    I started looking at creating a sql statement/report/[pl/sql] block that would give us the granular informatin on the true timings of the backup "pieces" as they relate to a "set."
    Research out on the wire shows a number of high level solutions, but nothing to which a report shows the data files, etc. Usually when I see this I start to question..."hey, is this even a good approach?"
    I do realize that through the RMAN utility there are a number of reports which are available...this post, however, is focused on the idea of sql reports against the rman catalog.
    Any advice would be welcome.
    Conceptual report:
    -> INCREMENTAL LEVEL 0
    --> BACKUP SET
    ---> BACKUP PIECE
    ----> HANDLE, TAG, DATAFILE, START, COMPLETION
    I'm NOT looking for the sql...I can work that out, I just want to know if this is a smart approach or best to stay out of the catalog.
    -abe
    Boulder, Colorado
    Edited by: user10863631 on Mar 10, 2011 7:43 AM
    Edited by: user10863631 on Mar 10, 2011 7:56 AM

    I think this is the wrong forum for such a question. The Database - General (General Database Discussions might be better suited. Or maybe the RMAN forum (Recovery Manager (RMAN)

  • How to upgrade RMAN catalog from 10.2.0.4 to 11?

    Hi, we are on Oracle 10.2.0.4, Solaris 5.10. Our RMAN catalog is 10.2.0.4 version and we have several 11g databases that need to connect to the catalog and obviously cannot. So we need to upgrade the catalog to 11. Does anyone have any docs on how to do it. Do I need to upgrade RMAN database to 11 via conventional upgrade and then do UPGRADE CATALOG? Really confusing, any help would be very appreciated.
    Thank you!

    You need to:
    1 - upgrade the recovery catalog database
    2 - upgrade the recovery catalog Schema
    Please check the details on note *452529.1 Recovery catalog for RMAN backup*.
    Normally newer databases (target) can be cataloged on previous version catalog database, but with 11g there is the bug 6756872 (RMAN REGISTER OF 11G TARGET INTO 10G CATALOG FAILS WITH ORA-04028) which force you to upgrade the catalog.
    You can also review RMAN Compatibility Matrix (Note 73431.1) which has all valid version combinations.
    If your scenario is simple enough, another option could be create a new 11g RMAN catalog and register there your databases, without importing data from the 10.2 catalog.
    Regards.

  • Can't register a database in RMAN catalog (PL/SQL package not current)

    Hi RMAN experts. I'm trying to register a 10.2.0.1.0 database into a 10.2.0.5.0 RMAN catalog but I get the following error (Note: following was done on the rman server machine, ORACLE_SID=rman, target database is remote)
    $ rman catalog rman/rman target sys@MPOWER
    Recovery Manager: Release 10.2.0.5.0 - Production on Sat Apr 30 12:54:16 2011
    Copyright (c) 1982, 2007, Oracle. All rights reserved.
    PL/SQL package SYS.DBMS_BACKUP_RESTORE version 10.02.00.00 in TARGET database is not current
    PL/SQL package SYS.DBMS_RCVMAN version 10.02.00.00 in TARGET database is not current
    connected to target database: MPOWER (DBID=**********)
    connected to recovery catalog database
    RMAN> register database;
    database registered in recovery catalog
    starting full resync of recovery catalog
    RMAN-00571: ===============
    RMAN-00569: =========ERROR MESSAGE STACK FOLLOWS
    RMAN-00571: =================
    RMAN-03008: error while performing automatic resync of recovery catalog
    ORA-00904: : invalid identifier
    Basically the error says that there are two packages in the TARGET database (SYS.DBMS_BACKUP_RESTORE and SYS.DBMS_RCVMAN) which are not compatible with the RMAN catalog.
    I cannot register the target database into the RMAN catalog.
    I highly appretiate if you give me an advice on this.
    Regards

    user13064912 wrote:
    Hi RMAN experts. I'm trying to register a 10.2.0.1.0 database into a 10.2.0.5.0 RMAN catalog but I get the following error (Note: following was done on the rman server machine, ORACLE_SID=rman, target database is remote)
    $ rman catalog rman/rman target sys@MPOWER
    Recovery Manager: Release 10.2.0.5.0 - Production on Sat Apr 30 12:54:16 2011
    Copyright (c) 1982, 2007, Oracle. All rights reserved.
    PL/SQL package SYS.DBMS_BACKUP_RESTORE version 10.02.00.00 in TARGET database is not current
    PL/SQL package SYS.DBMS_RCVMAN version 10.02.00.00 in TARGET database is not current
    connected to target database: MPOWER (DBID=**********)
    connected to recovery catalog database
    RMAN> register database;
    database registered in recovery catalog
    starting full resync of recovery catalog
    RMAN-00571: ===============
    RMAN-00569: =========ERROR MESSAGE STACK FOLLOWS
    RMAN-00571: =================
    RMAN-03008: error while performing automatic resync of recovery catalog
    ORA-00904: : invalid identifier
    Basically the error says that there are two packages in the TARGET database (SYS.DBMS_BACKUP_RESTORE and SYS.DBMS_RCVMAN) which are not compatible with the RMAN catalog.
    I cannot register the target database into the RMAN catalog.
    I highly appretiate if you give me an advice on this.
    RegardsCould you try to run the rman at the target database server (MPOWER), instead of rman catalog server ant try to register your database?
    Your rman client is higher than your target server. That could be the problem.
    Best Regards,
    Gokhan
    If this question is answered, please mark appropriate posts as correct/helpful and the thread as closed. Thanks

  • Question: Which is better and why....RMAN catalog or Flashback Recovery

    Hey All,
    Newly testing and reading up on 10g. I am on information overload and would appreciate pro's advice on which to choose and why.
    Thanks,
    d.

    Different things, not necessarily alternative. That is, RMAN catalog is normally (at least should be) on another machine, and does not contain physical backups, but only information about them : physical backups are normally stored on external devices, like tapes.
    Flashback Recovery technique is based on Flashback logs in Flash Recovery Area, which is a disk area on local machine, and so cannot be unlimited.
    Therefore, Flashback Recovery is much faster than Media Recovery, since you don't need to restore anything, but you have limits in using that : your disks size.
    On the other hand, RMAN backups are safer, being physically elsewhere.
    See http://download-uk.oracle.com/docs/cd/B19306_01/server.102/b14220/backrec.htm#g1023042

Maybe you are looking for