OEM 10g - Upgrade Recovery Catalog

Hello All,
I'm experiencing some difficulties when trying to upgrade my recovery catalog using Oracle's Enterprise Manager 10g and wanted to see if anyone could explain this error.
"+Error - Unable to retrieve the URL from repository. Check the specified target name and its corresponding target type. Other possible causes: remote EMD is not pointing to the web server, or remote target information has not bee loaded+."
What URL is the repository trying to use? Do I need to reinstall my repository using emca? Any assistance is appreciated.
Oracle DB Version: 10.2.0.3.0
Catalog DB Version: 10.2.0.1.0
OS: MS Windows Server 2003 SP2

I perform the following tasks:
<ol><li>Log in as sysdba</li>
<li>Click the Maintenance Tab</li>
<li>Click Recovery Catalog Settings (my recovery catalog is already registered)</li>
<li>Click on Recovery Catalogs (located under Related Links)</li>
<li>Select my recovery catalog and click Upgrade</li>
<li>Put in my OS user credentials and Recovery Cataloge credentials and click OK</li>
</ol>
The error occurs when after I click OK.

Similar Messages

Forgotten to upgrade recovery catalog

hi ,
i sucessfully upgraded from 11.2.0.1 to 11.2.0.3. BUt forgotten to upgrade the catalog.
which is the below steps..... (copy from a blogs, not mine)
lnx04ora.bai.com: FITSD>/opt/app/oracle/product/11.2.0.3/db_1/bin/rman target / catalog ......
Recovery Manager: Release 11.2.0.3.0 - Production on Fri Feb 10 04:33:40 2012
Copyright (c) 1982, 2011, Oracle and/or its affiliates. All rights reserved.
connected to target database: FITSD (DBID=3617642037)
connected to recovery catalog database
recovery catalog is partially upgraded to 11.02.00.03
RMAN> upgrade catalog;
recovery catalog owner is RMAN11GR2
enter UPGRADE CATALOG command again to confirm catalog upgrade
RMAN> upgrade catalog;
recovery catalog upgraded to version 11.02.00.03
DBMS_RCVMAN package upgraded to version 11.02.00.03
DBMS_RCVCAT package upgraded to version 11.02.00.03
RMAN>not too sure can it be done llive, meaning any need to shut the databse down?

damorgan wrote:
Then, by definition, you did not successfully upgrade anything.
Open an SR at MyOracleSupport and ask them to advise you as to how to safely fix the mess.
If you follow a blog post and something goes terribly wrong who is going to lose their job? You or the blogger?oh no no, not going to follow blindly. JUst copy the command out and paste here so that i can show the command.
I am clearifying whether is there any thing i need pre- task. NOt too sure i need to shutdown completely, backup the rman catalog schema, etc.

10g recovery catalog db dont support 11g db

Wondering 9i and 10g recovery catalogs dont support 11g db? and if i make 11g as recovery catalog it will support 9i and 10g right?

RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03009: failure of register command on default channel at 10/19/2010 12:19:5
8
RMAN-10015: error compiling PL/SQL program
RMAN-10033: error during compilation of job step 1: ORA-04023: Object RCAT.DBMS_
RCVCAT could not be validated or authorized
i'm having the issue below after upgrading 10.1.0 catalog database to 11g by running upgrade catalog twice....
but hitting the above error. Any idea why?

Oracle 10g express edition recovery catalog

whether oracle 10g express edition spoort recovery catalog?

Yes you can; the answer is in the manual.
>
In general, the rules of RMAN compatibility are as follows:
<li>You can create 8.X or 9.X RMAN catalog schema in any Oracle database release 8.1.X (or higher) and Release 10g RMAN catalog schema in any Oracle database release 9.0.1 (or higher).</li>
<li>The recovery catalog schema version must be greater than or equal to the RMAN client version.</li>
<li>Ideally, the versions of the RMAN client and the target database should be the same (although there are other legal combinations, listed in Table B-1).</li>
<li>While backing up a Release 10g database using the 9.X RMAN client, you cannot include a controlfile that was created using compatible=10.0.0 in a datafile backupset. The workaround is to turn controlfile autobackup ON.</li>
>
http://download.oracle.com/docs/cd/B12037_01/server.101/b10770/compat.htm
http://download.oracle.com/docs/cd/B25329_01/doc/admin.102/b25107/backrest.htm#i1004902
XE questions are best answered here {forum:id=251}
Regards,
Phiri
Edited by: phiri on 02-Apr-2010 01:36

Standby database - RMAN level 0 - Recovery catalog - OEM.

We have configured rman level 0 backup from standby database on OEM. Job is running fine, but rman is not getting connected to recovery catalog. RMAN is connecting to target control file instead of recovery catalog. I understand we need to have DG broker configured for primary and standby for RMAN to connect recovery catalog if you run from OEM. We have configured the DG broker also. DG broker configuration is woriing fine. but Still Standby is not connecting the rman recovery catalog database.
Can anyone tell me what i should check.

Catalog database is same for primary and standby. It is not working for both the version. What are all the basic check i need to do to debug the issue.
THIS IS LOG FROM OEM it is not connecting to target. instead of it is connecting to target control file.
Recovery Manager: Release 11.2.0.3.0 - Production on Thu Sep 6 22:40:28 2012
Copyright (c) 1982, 2011, Oracle and/or its affiliates. All rights reserved.
RMAN>
connected to target database: CAAPRD1 (DBID=524360237, not open)
using target database control file instead of recovery catalog
RMAN>
echo set on
RMAN> run {
2> allocate channel oem_backup_disk1 type disk MAXOPENFILES 1 format '/local/oracle/orabackups/CAASTB1/level0/%U';
3> allocate channel oem_backup_disk2 type disk MAXOPENFILES 1 format '/local/oracle/orabackups/CAASTB1/level0/%U';
4> allocate channel oem_backup_disk3 type disk MAXOPENFILES 1 format '/local/oracle/orabackups/CAASTB1/level0/%U';
5> allocate channel oem_backup_disk4 type disk MAXOPENFILES 1 format '/local/oracle/orabackups/CAASTB1/level0/%U';
6> allocate channel oem_backup_disk5 type disk MAXOPENFILES 1 format '/local/oracle/orabackups/CAASTB1/level0/%U';
7> allocate channel oem_backup_disk6 type disk MAXOPENFILES 1 format '/local/oracle/orabackups/CAASTB1/level0/%U';
8> allocate channel oem_backup_disk7 type disk MAXOPENFILES 1 format '/local/oracle/orabackups/CAASTB1/level0/%U';
9> allocate channel oem_backup_disk8 type disk MAXOPENFILES 1 format '/local/oracle/orabackups/CAATB1/level0/%U';
10> backup FILESPERSET 1 as BACKUPSET tag 'DAILY_LEVL0_DATA' database;
11> backup FILESPERSET 1 as BACKUPSET tag 'DAILY_LEVL0_ARCH' archivelog all not backed up;
12> release channel oem_backup_disk1;
13> release channel oem_backup_disk2;
14> release channel oem_backup_disk3;
15> release channel oem_backup_disk4;
16> release channel oem_backup_disk5;
17> release channel oem_backup_disk6;
18> release channel oem_backup_disk7;
19> release channel oem_backup_disk8;
20> }

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.

Best tactic to migrate recovery catalog

#Recovery Catalog
Oracle9i 9.2.0.1.0
Windows 2003 Server - 32 bit
Our recovery catalog is an old one, we will upgrade this to 11g, but we will need to make a new server for him as well.
Correct me if i am wrong but one way should be just to create a new server, install oracle and database, and re-connect all recovery catalog users to this one, and make new backups on them to get information about backup in the new catalog.
However, should'nt it be possible to export the data from old recovery catalog , to new recovery catalog?
Please guide me to the best tactic
Regards,

migrate catalog from 9i to 10g
Read the link.
Regards
Asif Kabir

V10.2.0.5 and Database Target Recovery Catalog Assignments

We recently upgraded to version from version 10.2.0.4 to 10.2.0.5. After, I started to continue where I left off with assigning recovery catalogs to our database targets. What was a simple process previously, is now becoming a headache. First, when adding an already registered recovery catalog I received this message "The specified username does not match the recovery catalog username configured for this database.". I was then told by support to update the back-end repository tables to make the recovery catalog username lowercase. This didn't work so I removed the registered catalog and attempted to add it back. Then I received this message which is rather frightening:
"In this version of Enterprise Manager, recovery catalog settings are now specific to each Enterprise Manager user. Existing recovery catalog settings made prior to upgrading Enterprise Manager have been preserved in order to allow existing backup jobs to continue to work. However, if you change the recovery catalog setting for this database, all non-user-specific settings will be removed, and each Enterprise Manager user that manages this database will have to individually reset their recovery catalog settings for this database. Do you want to continue?"
I can't find any mention of this change in any updated documentation, support page, or other. Essentially, this tells me that as of GC version 10.2.0.5, assignment of a recovery catalog to a given database target is no longer centralized but de-centralized. Each user with OEM GC now has to assign a recovery catalog to each database instance irregardless if their profile is setup as a Super Admin. Or, if you expect to run a manaul backup for a given database you have to log in under a shared account which has all the catalogs assigned which defeats the purpose of any SAS 70 auditing.
I have a ticket in with Oracle support at this time. If anyone has any insight to this I would love to know the reasoning behind it. Thanks.

Well, product development responded with this:
"The catalog management model has been changed in 10.2.0.5GC to
accommodate new database catalog features and enhance security.
Each team member would have to register the catalog separately for the
targets they manage, through their own EM account. This is a one-time
activity. Once that is done, the functionality is the same as before."
What a huge faux pas.

Recovery Catalog showing wrong Archive Destination

Hi All,
I am using Oracle 10g on Solaris 10.
The problem I am facing is this, while taking backup using recover catalog..............
Starting backup at 27-JUL-11
current log archived
released channel: ch00
released channel: ch01
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of backup command at 07/27/2011 11:16:47
RMAN-06059: expected archived log not found, lost of archived log compromises recoverability
ORA-19625: error identifying file /u01/oracle/product/10.2.0/db_1/dbs/arch1_56_757089402.dbf
ORA-27037: unable to obtain file status
SVR4 Error: 2: No such file or directory
Additional information: 3
This is because of the following reason
RMAN> list archivelog all;
List of Archived Log Copies
Key Thrd Seq S Low Time Name
39401 1 1567 A 26-JUL-11 /oradb2/Archive/HCSPRD91/1_1567_756523261.dbf
39402 1 1568 A 26-JUL-11 /oradb2/Archive/HCSPRD91/1_1568_756523261.dbf
39403 1 1569 A 26-JUL-11 /oradb2/Archive/HCSPRD91/1_1569_756523261.dbf
39404 1 1570 A 26-JUL-11 /oradb2/Archive/HCSPRD91/1_1570_756523261.dbf
39405 1 1571 A 26-JUL-11 /oradb2/Archive/HCSPRD91/1_1571_756523261.dbf
39406 1 1572 A 26-JUL-11 /oradb2/Archive/HCSPRD91/1_1572_756523261.dbf
39407 1 1573 A 26-JUL-11 /oradb2/Archive/HCSPRD91/1_1573_756523261.dbf
39408 1 1574 A 26-JUL-11 /oradb2/Archive/HCSPRD91/1_1574_756523261.dbf
39409 1 1575 A 26-JUL-11 /oradb2/Archive/HCSPRD91/1_1575_756523261.dbf
39410 1 1576 A 26-JUL-11 /oradb2/Archive/HCSPRD91/1_1576_756523261.dbf
39411 1 1577 A 26-JUL-11 /oradb2/Archive/HCSPRD91/1_1577_756523261.dbf
39412 1 1578 A 26-JUL-11 /oradb2/Archive/HCSPRD91/1_1578_756523261.dbf
39413 1 1579 A 26-JUL-11 /oradb2/Archive/HCSPRD91/1_1579_756523261.dbf
39414 1 1580 A 26-JUL-11 /oradb2/Archive/HCSPRD91/1_1580_756523261.dbf
39415 1 1581 A 26-JUL-11 /oradb2/Archive/HCSPRD91/1_1581_756523261.dbf
39416 1 1582 A 26-JUL-11 /oradb2/Archive/HCSPRD91/1_1582_756523261.dbf
39417 1 1583 A 26-JUL-11 /oradb2/Archive/HCSPRD91/1_1583_756523261.dbf
39418 1 1584 A 26-JUL-11 /oradb2/Archive/HCSPRD91/1_1584_756523261.dbf
39419 1 1585 A 26-JUL-11 /oradb2/Archive/HCSPRD91/1_1585_756523261.dbf
39420 1 1586 A 26-JUL-11 /oradb2/Archive/HCSPRD91/1_1586_756523261.dbf
39421 1 1587 A 26-JUL-11 /oradb2/Archive/HCSPRD91/1_1587_756523261.dbf
39422 1 1588 A 26-JUL-11 /oradb2/Archive/HCSPRD91/1_1588_756523261.dbf
39423 1 1589 A 26-JUL-11 /oradb2/Archive/HCSPRD91/1_1589_756523261.dbf
39424 1 1590 A 26-JUL-11 /oradb2/Archive/HCSPRD91/1_1590_756523261.dbf
39425 1 1591 A 26-JUL-11 /oradb2/Archive/HCSPRD91/1_1591_756523261.dbf
39426 1 1592 A 26-JUL-11 /oradb2/Archive/HCSPRD91/1_1592_756523261.dbf
39427 1 1593 A 26-JUL-11 /oradb2/Archive/HCSPRD91/1_1593_756523261.dbf
39428 1 1594 A 26-JUL-11 /oradb2/Archive/HCSPRD91/1_1594_756523261.dbf
39429 1 1595 A 26-JUL-11 /oradb2/Archive/HCSPRD91/1_1595_756523261.dbf
39430 1 1596 A 26-JUL-11 /oradb2/Archive/HCSPRD91/1_1596_756523261.dbf
39431 1 1597 A 26-JUL-11 /oradb2/Archive/HCSPRD91/1_1597_756523261.dbf
39432 1 1598 A 26-JUL-11 /oradb2/Archive/HCSPRD91/1_1598_756523261.dbf
39433 1 1599 A 26-JUL-11 /oradb2/Archive/HCSPRD91/1_1599_756523261.dbf
39434 1 1600 A 26-JUL-11 /oradb2/Archive/HCSPRD91/1_1600_756523261.dbf
39435 1 1601 A 26-JUL-11 /oradb2/Archive/HCSPRD91/1_1601_756523261.dbf
39436 1 1602 A 26-JUL-11 /oradb2/Archive/HCSPRD91/1_1602_756523261.dbf
39437 1 1603 A 26-JUL-11 /oradb2/Archive/HCSPRD91/1_1603_756523261.dbf
39438 1 1604 A 26-JUL-11 /oradb2/Archive/HCSPRD91/1_1604_756523261.dbf
39439 1 1605 A 26-JUL-11 /oradb2/Archive/HCSPRD91/1_1605_756523261.dbf
39440 1 1606 A 26-JUL-11 /oradb2/Archive/HCSPRD91/1_1606_756523261.dbf
39441 1 1607 A 26-JUL-11 /oradb2/Archive/HCSPRD91/1_1607_756523261.dbf
39442 1 1608 A 26-JUL-11 /oradb2/Archive/HCSPRD91/1_1608_756523261.dbf
39443 1 1609 A 26-JUL-11 /oradb2/Archive/HCSPRD91/1_1609_756523261.dbf
39444 1 1610 A 26-JUL-11 /oradb2/Archive/HCSPRD91/1_1610_756523261.dbf
39445 1 1611 A 26-JUL-11 /oradb2/Archive/HCSPRD91/1_1611_756523261.dbf
39446 1 1612 A 26-JUL-11 /oradb2/Archive/HCSPRD91/1_1612_756523261.dbf
39447 1 1613 A 26-JUL-11 /oradb2/Archive/HCSPRD91/1_1613_756523261.dbf
39448 1 1614 A 26-JUL-11 /oradb2/Archive/HCSPRD91/1_1614_756523261.dbf
39449 1 1615 A 26-JUL-11 /oradb2/Archive/HCSPRD91/1_1615_756523261.dbf
39450 1 1616 A 26-JUL-11 /oradb2/Archive/HCSPRD91/1_1616_756523261.dbf
39451 1 1617 A 26-JUL-11 /oradb2/Archive/HCSPRD91/1_1617_756523261.dbf
39452 1 1618 A 26-JUL-11 /oradb2/Archive/HCSPRD91/1_1618_756523261.dbf
39453 1 1619 A 26-JUL-11 /oradb2/Archive/HCSPRD91/1_1619_756523261.dbf
39454 1 1620 A 26-JUL-11 /oradb2/Archive/HCSPRD91/1_1620_756523261.dbf
39455 1 1621 A 26-JUL-11 /oradb2/Archive/HCSPRD91/1_1621_756523261.dbf
39456 1 1622 A 26-JUL-11 /oradb2/Archive/HCSPRD91/1_1622_756523261.dbf
39457 1 1623 A 26-JUL-11 /oradb2/Archive/HCSPRD91/1_1623_756523261.dbf
39458 1 1624 A 26-JUL-11 /oradb2/Archive/HCSPRD91/1_1624_756523261.dbf
39459 1 1625 A 26-JUL-11 /oradb2/Archive/HCSPRD91/1_1625_756523261.dbf
39460 1 1626 A 26-JUL-11 /oradb2/Archive/HCSPRD91/1_1626_756523261.dbf
39461 1 1627 A 26-JUL-11 /oradb2/Archive/HCSPRD91/1_1627_756523261.dbf
39462 1 1628 A 26-JUL-11 /oradb2/Archive/HCSPRD91/1_1628_756523261.dbf
39463 1 1629 A 26-JUL-11 /oradb2/Archive/HCSPRD91/1_1629_756523261.dbf
39464 1 1630 A 26-JUL-11 /oradb2/Archive/HCSPRD91/1_1630_756523261.dbf
39465 1 1631 A 26-JUL-11 /oradb2/Archive/HCSPRD91/1_1631_756523261.dbf
39466 1 1632 A 26-JUL-11 /oradb2/Archive/HCSPRD91/1_1632_756523261.dbf
39467 1 1633 A 26-JUL-11 /oradb2/Archive/HCSPRD91/1_1633_756523261.dbf
39468 1 1634 A 26-JUL-11 /oradb2/Archive/HCSPRD91/1_1634_756523261.dbf
39469 1 1635 A 26-JUL-11 /oradb2/Archive/HCSPRD91/1_1635_756523261.dbf
39470 1 1636 A 26-JUL-11 /oradb2/Archive/HCSPRD91/1_1636_756523261.dbf
39471 1 1637 A 26-JUL-11 /oradb2/Archive/HCSPRD91/1_1637_756523261.dbf
39682 1 1638 A 26-JUL-11 /oradb2/Archive/HCSPRD91/1_1638_756523261.dbf
39689 1 1639 A 26-JUL-11 /oradb2/Archive/HCSPRD91/1_1639_756523261.dbf
40642 1 1640 A 26-JUL-11 /oradb2/Archive/HCSPRD91/1_1640_756523261.dbf
40643 1 1641 A 27-JUL-11 /oradb2/Archive/HCSPRD91/1_1641_756523261.dbf
40644 1 1642 A 27-JUL-11 /oradb2/Archive/HCSPRD91/1_1642_756523261.dbf
40645 1 1643 A 27-JUL-11 /oradb2/Archive/HCSPRD91/1_1643_756523261.dbf
40646 1 1644 A 27-JUL-11 /oradb2/Archive/HCSPRD91/1_1644_756523261.dbf
40647 1 1645 A 27-JUL-11 /oradb2/Archive/HCSPRD91/1_1645_756523261.dbf
40648 1 1646 A 27-JUL-11 /oradb2/Archive/HCSPRD91/1_1646_756523261.dbf
41310 1 1647 A 27-JUL-11 /oradb2/Archive/HCSPRD91/1_1647_756523261.dbf
41317 1 1648 A 27-JUL-11 /oradb2/Archive/HCSPRD91/1_1648_756523261.dbf
41373 1 1649 A 27-JUL-11 /oradb2/Archive/HCSPRD91/1_1649_756523261.dbf
41374 1 1650 A 27-JUL-11 /oradb2/Archive/HCSPRD91/1_1650_756523261.dbf
41375 1 1651 A 27-JUL-11 /oradb2/Archive/HCSPRD91/1_1651_756523261.dbf
41383 1 1652 A 27-JUL-11 /oradb2/Archive/HCSPRD91/1_1652_756523261.dbf
*38725 1 56 A 26-JUL-11 /u01/oracle/product/10.2.0/db_1/dbs/arch1_56_757089402.dbf*
*38946 1 57 A 26-JUL-11 /u01/oracle/product/10.2.0/db_1/dbs/arch1_57_757089402.dbf*
*39000 1 58 A 26-JUL-11 /u01/oracle/product/10.2.0/db_1/dbs/arch1_58_757089402.dbf*
*39022 1 59 A 26-JUL-11 /u01/oracle/product/10.2.0/db_1/dbs/arch1_59_757089402.dbf*
*39243 1 60 A 26-JUL-11 /u01/oracle/product/10.2.0/db_1/dbs/arch1_60_757089402.dbf*
*39297 1 61 A 26-JUL-11 /u01/oracle/product/10.2.0/db_1/dbs/arch1_61_757089402.dbf*
*39703 1 62 A 26-JUL-11 /u01/oracle/product/10.2.0/db_1/dbs/arch1_62_757089402.dbf*
*39704 1 63 A 26-JUL-11 /u01/oracle/product/10.2.0/db_1/dbs/arch1_63_757089402.dbf*
*39705 1 64 A 26-JUL-11 /u01/oracle/product/10.2.0/db_1/dbs/arch1_64_757089402.dbf*
*39933 1 65 A 27-JUL-11 /u01/oracle/product/10.2.0/db_1/dbs/arch1_65_757089402.dbf*
*39991 1 66 A 27-JUL-11 /u01/oracle/product/10.2.0/db_1/dbs/arch1_66_757089402.dbf*
*40023 1 67 A 27-JUL-11 /u01/oracle/product/10.2.0/db_1/dbs/arch1_67_757089402.dbf*
*40024 1 68 A 27-JUL-11 /u01/oracle/product/10.2.0/db_1/dbs/arch1_68_757089402.dbf*
*40025 1 69 A 27-JUL-11 /u01/oracle/product/10.2.0/db_1/dbs/arch1_69_757089402.dbf*
*40254 1 70 A 27-JUL-11 /u01/oracle/product/10.2.0/db_1/dbs/arch1_70_757089402.dbf*
*40308 1 71 A 27-JUL-11 /u01/oracle/product/10.2.0/db_1/dbs/arch1_71_757089402.dbf*
*40345 1 72 A 27-JUL-11 /u01/oracle/product/10.2.0/db_1/dbs/arch1_72_757089402.dbf*
*40570 1 73 A 27-JUL-11 /u01/oracle/product/10.2.0/db_1/dbs/arch1_73_757089402.dbf*
*41329 1 74 A 27-JUL-11 /u01/oracle/product/10.2.0/db_1/dbs/arch1_74_757089402.dbf*
I dont know from where recovery catalog is getting the information in bold.
I have crosschecked and deleted archives and resynced the catalog several times. Immediatly after doing that the backup works fine, but the other day its the same thing all over again.
Can some one tell me from where the catalog is getting this wrong infomation about archivelogs???
By the way here is some more info about my target Database:
Connected to:
Oracle Database 10g Enterprise Edition Release 10.2.0.5.0 - 64bit Production
With the Partitioning, OLAP, Data Mining and Real Application Testing options
SQL> archive log list
Database log mode Archive Mode
Automatic archival Enabled
Archive destination /oradb2/Archive/HCSPRD91
Oldest online log sequence 1651
Next log sequence to archive 1653
Current log sequence 1653
NAME TYPE VALUE
archive_lag_target integer 0
log_archive_config string
log_archive_dest string
log_archive_dest_1 string LOCATION=/oradb2/Archive/HCSPR
D91
log_archive_dest_10 string
log_archive_dest_2 string
log_archive_dest_3 string
log_archive_dest_4 string
log_archive_dest_5 string
log_archive_dest_6 string
NAME TYPE VALUE
log_archive_dest_7 string
log_archive_dest_8 string
log_archive_dest_9 string
log_archive_dest_state_1 string enable
log_archive_dest_state_10 string enable
log_archive_dest_state_2 string enable
log_archive_dest_state_3 string enable
log_archive_dest_state_4 string enable
log_archive_dest_state_5 string enable
log_archive_dest_state_6 string enable
log_archive_dest_state_7 string enable
NAME TYPE VALUE
log_archive_dest_state_8 string enable
log_archive_dest_state_9 string enable
log_archive_duplex_dest string
log_archive_format string %t_%s_%r.dbf
log_archive_local_first boolean TRUE
log_archive_max_processes integer 2
log_archive_min_succeed_dest integer 1
log_archive_start boolean FALSE
log_archive_trace integer 0
remote_archive_enable string true
standby_archive_dest string ?/dbs/arch
Regards .....

Do you have any other DBs with the same DBID as the one you are backing up? Are they connect to the same RMAN catalog?
Iordan Iotzov
http://iiotzov.wordpress.com/

Installing OEM 10g (10.2.0.1) Grid Control on Linux86

Hi friends,
I have successfully installed OEM Grid in our RHEL 4.6 server (1st time).
At the end of the installation I got this message:
See below for information pertaining to your Enterprise Manager installation:
1. Use the following URL to access the Enterprise Manager Grid Control:
http://server01.ebiztech.biz:4889/em
2. The Enterprise Manager installation includes an Oracle Application Server instance, which is administered using a special "ias_admin" user account. The following information was defaulted for the embedded Application Server instance:
Instance Name:    EnterpriseManager0.server01.ebiztech.biz
ias_admin password: This password is the same the SYSMAN account.
3. The connection details for the Enterprise Manager Repository are:
Host: server01.ebiztech.biz
Port: 1521
SID: emrepI can do #1, and #3.
How do I access #2? what is the URL corresponding to it? Or is it done through SQLPlus?
Thanks a lot,
Ms K

Thanks Raj,
Of course I will upgrade it, but for now I am still cramming on how to complete my installation huhuhhu:(
Firstly....
How do you install management agent for linux86?
I have already installed OEM 10g Grid Control OMS on my linux sever which also has EBS R12.1.
Do I need to install a "management agent" on this server, to be able to manage my EBS R12.1?
Secondly....
I want to manage our EBS 11i which resides on another server (remote).
I downloaded the Linux_Grid_Control_agent_download_10_2_0_2_0.zip file from OTN,
and put it to the target server.
I unzip it following the readme.txt to the
1. Download the Linux_Grid_Control_agent_download_10_2_0_2_0.zip file from OTN.
2. Copy the downloaded file to <OMS_HOME>/sysman/agent_download/10.2.0.2.0 directory.(create <OMS_HOME>/sysman/agent_download/10.2.0.2.0 directory, if it doesn't exist.)
3. cd <OMS_HOME>/sysman/agent_download/10.2.0.2.0
4. <OMS_HOME>/bin/unzip Linux_Grid_Control_agent_download_10_2_0_2_0.zip
5. If agent_download.rsp doesn't exists at <OMS_HOME>/sysman/agent_download/10.2.0.2.0 directory then:
    a. mv agent_download.rsp.bak agent_download.rsp
    b. edit agent_download.rsp and modify s_OMSHost="%s_hostname%" and s_OMSPort="%s_OMSPort%" with the correct OMSHost and OMSPort values.(However, even if you are specifying a secure Management Service, you must still enter the non-secure port number here)
        eg. s_OMSHost="stadv26.us.oracle.com"
            s_OMSPort="4889"
6. Edit <OMS_HOME>/sysman/agent_download/10.2.0.2.0/linux/agentDownload.linux and modify OMShost=%s_OMSHost% and httpPort=%s_OMSPort% with the correct OMSHost and OMSPort.(However, even if you are specifying a secure Management Service, you must still enter the non-secure port number here)
   For eg. OMShost =stadv26.us.oracle.com
           httpPort=4889
7. Follow the agentDownload instructions from 5.4 section of Oracle Enterprise Manager Installation and Basic Configuration Guide.But when I got to #7 ....the documentation is not clear, as usual there are lots of injected unrelated topics which make the documentation "topsiturvy" and very hard to follow.
Can you just tell me, based on your experience how to install the agent? Someone told me to run OUI?
But I can not find it on the unzip >Linux_Grid_Control_agent_download_10_2_0_2_0.zip file
Thanks a lot.

OEM 10g (10.2.0.1) Grid Control for Linux86 part 2

Hi hussein/helios,
Firstly....
How do you install management agent for linux86?
I have already installed OEM 10g Grid Control OMS on my linux sever which also has EBS R12.1.
Do I need to install a "management agent" on this server, to be able to manage my EBS R12.1?
Secondly....
I want to manage our EBS 11i which resides on another server (remote).
I downloaded the Linux_Grid_Control_agent_download_10_2_0_2_0.zip file from OTN,
and put it to the target server.
I unzip it following the readme.txt to the
1. Download the Linux_Grid_Control_agent_download_10_2_0_2_0.zip file from OTN.
2. Copy the downloaded file to <OMS_HOME>/sysman/agent_download/10.2.0.2.0 directory.(create <OMS_HOME>/sysman/agent_download/10.2.0.2.0 directory, if it doesn't exist.)
3. cd <OMS_HOME>/sysman/agent_download/10.2.0.2.0
4. <OMS_HOME>/bin/unzip Linux_Grid_Control_agent_download_10_2_0_2_0.zip
5. If agent_download.rsp doesn't exists at <OMS_HOME>/sysman/agent_download/10.2.0.2.0 directory then:
    a. mv agent_download.rsp.bak agent_download.rsp
    b. edit agent_download.rsp and modify s_OMSHost="%s_hostname%" and s_OMSPort="%s_OMSPort%" with the correct OMSHost and OMSPort values.(However, even if you are specifying a secure Management Service, you must still enter the non-secure port number here)
        eg. s_OMSHost="stadv26.us.oracle.com"
            s_OMSPort="4889"
6. Edit <OMS_HOME>/sysman/agent_download/10.2.0.2.0/linux/agentDownload.linux and modify OMShost=%s_OMSHost% and httpPort=%s_OMSPort% with the correct OMSHost and OMSPort.(However, even if you are specifying a secure Management Service, you must still enter the non-secure port number here)
   For eg. OMShost =stadv26.us.oracle.com
           httpPort=4889
7. Follow the agentDownload instructions from 5.4 section of Oracle Enterprise Manager Installation and Basic Configuration Guide.But when I got to #7 ....the documentation is not clear, as usual there are lots of injected unrelated topics which make the documentation "topsiturvy" and very hard to follow.
Can you just tell me, based on your experience how to install the agent? Someone told me to run OUI?
But I can not find it on the unzip >Linux_Grid_Control_agent_download_10_2_0_2_0.zip file
Thanks a lot.
Ms K

hi dear,
I want to upgrade my OMS server 10.2.0.1 to 10.2.0.5
I downloaded the patch 10.2.0.5 and read the README.txt
Part of the README is:
1.2 Enter the following command to extract the installation files:
$ unzip GridControl_10.2.0.5_<platform name>.zip
This command extracts the following files and directory:
|- p3731593_10205_<platform name>.zip
|- 3731596.zip
|- 3822442.zip
|- README.txt
|- doc/
NOTE: <platform name> will be "LINUX" or "Win32" depending on the platform for which you are installing. For installing Enterprise Manager 10g Grid Control Release 5 (10.2.0.5), refer to the Release Notes available in the "doc" directory.
- p3731593_10205_<platform name>.zip is the ZIP file that contains 10.2.0.5 patch set software.
This zip can be used for:
- Upgrading Oracle Management Service Release 2 (10.2.0.x) or higher to Oracle Management Service Release 5 (10.2.0.5)
- Upgrading Oracle Management Repository (sysman schema)
- Upgrading Oracle Management Agent on the host where OMS is running.
NOTE: This will not upgrade the database in which the Management Repository (sysman schema) resides.
- 3731596.zip is for patching Management Agent by staging the patch set. To understand how you can apply the Management Agent 10.2.0.5 patch set, refer to method 2 described in section 4.3.3 "Upgrading Management Agent - Multiple Hosts at a Time" of the Release Notes. The Release Notes can be found in the "doc" directory.
- 3822442.zip is for patching Management Agent by distributing the full patch set. To understand how to apply the Management Agent 10.2.0.5 patch set, refer to method 1 described in section 4.3.3 "Upgrading Management Agent - Multiple Hosts at a Time" of the Release Notes. The Release Notes can be found in the "doc" directory.3731596.zip - by staging
3822442.zip - by distributing
Does the two above have the same function or purpose?
I can not understand the meaning of the two :( . which do you think is the right one for my setup?
Thanks a lot

Oracle 10g XE recovery failed

Hi, everyone:
I have re-install my linux which is rh5. I also have a backup directory - "flash_recovery_area" from another oracle 10g XE database.
When I installed the new oracle 10 XE, I try to restore the backup data from application menu, but the get result as below:
This operation will shut down and restore the database. Are you sure [Y/N]?y
Restore in progress...
Enter the flash recovery area location:/usr/lib/oracle
==================== ERROR =========================
Restore of the database failed
==================== ERROR =========================
RMAN error: See log for details.
Log file is at /home/tim/oxe_restore.log.
Press ENTER key to exit
I found the error lines in oxe_restore.log as below:
RMAN>
Oracle instance started
Total System Global Area 285212672 bytes
Fixed Size 1258464 bytes
Variable Size 92277792 bytes
Database Buffers 188743680 bytes
Redo Buffers 2932736 bytes
RMAN>
Recovery Manager complete.
Recovery Manager: Release 10.2.0.1.0 - Production on Tue Jul 29 01:05:53 2008
Copyright (c) 1982, 2005, Oracle. All rights reserved.
connected to target database: XE (not mounted)
RMAN>
echo set on
RMAN> restore spfile from autobackup db_recovery_file_dest='/usr/lib/oracle';
Starting restore at 29-JUL-08
using target database control file instead of recovery catalog
allocated channel: ORA_DISK_1
channel ORA_DISK_1: sid=36 devtype=DISK
recovery area destination: /usr/lib/oracle
database name (or database unique name) used for search: XE
channel ORA_DISK_1: no autobackups found in the recovery area
autobackup search outside recovery area not attempted because DBID was not set
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of restore command at 07/29/2008 01:05:54
RMAN-06172: no autobackup found or specified handle is not a valid copy or piece
RMAN> startup force nomount;
Oracle instance started
Total System Global Area 608174080 bytes
Fixed Size 1260316 bytes
Variable Size 226493668 bytes
Database Buffers 377487360 bytes
Redo Buffers 2932736 bytes
RMAN> restore controlfile from autobackup;
Starting restore at 29-JUL-08
allocated channel: ORA_DISK_1
And after that, the new oracle 10 XE can`t start anymore.
Thanks for any help!
OldTim

Thank you so much for reply!
Tried full path already, but still can`t work. But I found another solution below and made it working finally:
Oracle XE Recovery
1 Copy /usr/lib/oracle to Bakcup disk.
sudo cp /usr/lib/oracle /media/disk
2 Copy the directory oracle to new linux system
sudo cp /media/disk /usr/lib/oracle
3 install Oracle 10g XE
4 run command below:
/usr/lib/oracle/xe/app/oracle/product/10.2.0/server/config/scripts/restore.sh
Done.

Oracle 10.2.0.4 RMAN Duplicate without a Recovery Catalog

Production Backups are Tuesday - Sunday at 22:00:
RUN {
ALLOCATE CHANNEL c1 DEVICE TYPE DISK;
CROSSCHECK ARCHIVELOG ALL;
CROSSCHECK BACKUP;
DELETE NOPROMPT COPY OF ARCHIVELOG ALL COMPLETED BEFORE 'SYSDATE-2';
DELETE NOPROMPT BACKUP;
BACKUP DATABASE PLUS ARCHIVELOG;
CROSSCHECK BACKUP;
RELEASE CHANNEL c1;
LIST BACKUPSET;
EOF
I have these files sent over to the development server on Wednesday, RMANbackup (log), backupset and the controlfile:
rcp -rp /backup/$1/flash_recovery/$2/RMANbackup/* kacdb4:/backup/common/flash_recovery/$2/RMANbackup
rcp -rp /backup/$1/flash_recovery/$2/backupset/* kacdb4:/backup/common/flash_recovery/$2/backupset
rcp -rp /backup/$1/flash_recovery/$2/controlfile/* kacdb4:/backup/common/flash_recovery/$2/controlfile
I run the RMAN Duplicate and the database gets created with no problems!
The question is: If I wait unit Thursday, to run the duplicate script, I get the traditional RMAN errors: RMAN-03002, RMAN-03015, RMAN-06026, RMAN-06023:
Starting restore at 20-SEP-12
released channel: aux1
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of Duplicate Db command at 09/20/2012 10:05:36
RMAN-03015: error occurred in stored script Memory Script
RMAN-06026: some targets not found - aborting restore
RMAN-06023: no backup or copy of datafile 6 found to restore
RMAN-06023: no backup or copy of datafile 5 found to restore
RMAN-06023: no backup or copy of datafile 4 found to restore
RMAN-06023: no backup or copy of datafile 3 found to restore
RMAN-06023: no backup or copy of datafile 2 found to restore
RMAN-06023: no backup or copy of datafile 1 found to restore
Recovery Manager complete.
Is this because of the 'SYSDATE-2' in the RMAN runlist? Does RMAN connect back to the target and it does not find the logs, because they've been deleted, it aborts the duplicate? I've shipped over the backupset and controlfile of the scn I'm using in the duplicate runlist all is there? If I'm trying to cleanup the archive area, would'nt 'delete expired archivelog all' in my runlist, be better than using the 'SYSDATE-2'?
Or is it because of this database parameter:
control_file_record_keep_time= 7, should I set this to say 14?
Is it one of these RMAN configurations:
Retention Policy to Redundancy 1, should I set this to say 7?
Datafile Backup Copies for Device Type Disk to 1, to say 3, this takes up disk space which is precious
Archivelog Backup Copies for Device Type Disk to 1, to say 3, this takes up disk space too
Archive deletion policy to none change this to the other option?
I've tested this a few times now, and always fails if the dupicate is not done the next day.
If I have to create a development database on a Friday from Tuesday's copy FROM TAPE, I will get the error, because the files are no longer on disk.
What can I do to ensure that I can create an RMAN duplicate any day of the week from Tuesday to Sunday?
Look forward to your answer.
Please let me know if I left any details out that you may need.
Sincerely,
Elizabeth Burns

Hi Valentin,
Here is the good duplicate log from Monday 9/24:
oracle:dupdb@kacdb4:/u01/app/oracle/KAC_SCRIPTS/dupdb/logs-> more clone_database_from_common_20120924.log
SQL*Plus: Release 10.2.0.4.0 - Production on Mon Sep 24 18:07:32 2012
Copyright (c) 1982, 2007, Oracle. All Rights Reserved.
Connected.
SQL> spool /u01/app/oracle/KAC_SCRIPTS/dupdb/logs/DBShutdown.log
SQL> shutdown immediate
ORA-01507: database not mounted
ORACLE instance shut down.
SQL> spool off
SQL> exit;
Disconnected from Oracle Database 10g Release 10.2.0.4.0 - 64bit Production
SQL*Plus: Release 10.2.0.4.0 - Production on Mon Sep 24 18:07:41 2012
Copyright (c) 1982, 2007, Oracle. All Rights Reserved.
Connected to an idle instance.
File created.
ORACLE instance started.
Total System Global Area 134217728 bytes
Fixed Size 2054448 bytes
Variable Size 79693520 bytes
Database Buffers 50331648 bytes
Redo Buffers 2138112 bytes
Disconnected from Oracle Database 10g Release 10.2.0.4.0 - 64bit Production
Recovery Manager: Release 10.2.0.4.0 - Production on Mon Sep 24 18:07:43 2012
Copyright (c) 1982, 2007, Oracle. All rights reserved.
connected to target database: KEDSP (DBID=3370721566)
connected to auxiliary database: DUPDB (not mounted)
RMAN> RUN
2> {
3> ALLOCATE AUXILIARY CHANNEL aux1 DEVICE TYPE DISK;
4>
5> set until scn 211054288;
6> DUPLICATE TARGET DATABASE TO dupdb
7> PFILE=/u01/app/oracle/product/10.2.0/db_1/dbs/initdupdb.ora
8> DB_FILE_NAME_CONVERT=('/usr/local/OLlinks/kedsp/system/','/usr/local/OLlinks/dupdb/system/','/usr/local/OLlinks/kedsp/temp/','/us
r/local/OLlinks/dupdb/temp/','/usr/local/OLlinks/kedsp/data01/','/usr/local/OLlinks/dupdb/data01/','/usr/local/OLlinks/kedsp/index01
/','/usr/
9> local/OLlinks/dupdb/index01/')
10> LOGFILE
11> GROUP 1 (
12> '/usr/local/OLlinks/dupdb/redo01/redo0101.log',
13> '/usr/local/OLlinks/dupdb/redo02/redo0102.log',
14> '/usr/local/OLlinks/dupdb/redo03/redo0103.log'
15> ) SIZE 50M,
16> GROUP 2 (
17> '/usr/local/OLlinks/dupdb/redo01/redo0201.log',
18> '/usr/local/OLlinks/dupdb/redo02/redo0202.log',
19> '/usr/local/OLlinks/dupdb/redo03/redo0203.log'
20> ) SIZE 50M,
21> GROUP 3 (
22> '/usr/local/OLlinks/dupdb/redo01/redo0301.log',
23> '/usr/local/OLlinks/dupdb/redo02/redo0302.log',
24> '/usr/local/OLlinks/dupdb/redo03/redo0303.log'
25> ) SIZE 50M,
26> GROUP 4 (
27> '/usr/local/OLlinks/dupdb/redo01/redo0401.log',
28> '/usr/local/OLlinks/dupdb/redo02/redo0402.log',
29> '/usr/local/OLlinks/dupdb/redo03/redo0403.log'
30> ) SIZE 50M,
31> GROUP 5 (
32> '/usr/local/OLlinks/dupdb/redo01/redo0501.log',
33> '/usr/local/OLlinks/dupdb/redo02/redo0502.log',
34> '/usr/local/OLlinks/dupdb/redo03/redo0503.log'
35> ) SIZE 50M,
36> GROUP 6 (
37> '/usr/local/OLlinks/dupdb/redo01/redo0601.log',
38> '/usr/local/OLlinks/dupdb/redo02/redo0602.log',
39> '/usr/local/OLlinks/dupdb/redo03/redo0603.log'
40> ) SIZE 50M,
41> GROUP 7 (
42> '/usr/local/OLlinks/dupdb/redo01/redo0701.log',
43> '/usr/local/OLlinks/dupdb/redo02/redo0702.log',
44> '/usr/local/OLlinks/dupdb/redo03/redo0703.log'
45> ) SIZE 50M,
46> GROUP 8 (
47> '/usr/local/OLlinks/dupdb/redo01/redo0801.log',
48> '/usr/local/OLlinks/dupdb/redo02/redo0802.log',
49> '/usr/local/OLlinks/dupdb/redo03/redo0803.log'
50> ) SIZE 50M,
51> GROUP 9 (
52> '/usr/local/OLlinks/dupdb/redo01/redo0901.log',
53> '/usr/local/OLlinks/dupdb/redo02/redo0902.log',
54> '/usr/local/OLlinks/dupdb/redo03/redo0903.log'
55> ) SIZE 50M,
56> GROUP 10 (
57> '/usr/local/OLlinks/dupdb/redo01/redo1001.log',
58> '/usr/local/OLlinks/dupdb/redo02/redo1002.log',
59> '/usr/local/OLlinks/dupdb/redo03/redo1003.log'
60> ) SIZE 50M
61> ;
62> }
63>
using target database control file instead of recovery catalog
allocated channel: aux1
channel aux1: sid=242 devtype=DISK
executing command: SET until clause
Starting Duplicate Db at 24-SEP-12
contents of Memory Script:
set until scn 211054288;
set newname for datafile 1 to
"/usr/local/OLlinks/dupdb/system/system01.dbf";
set newname for datafile 2 to
"/usr/local/OLlinks/dupdb/system/undotbs01.dbf";
set newname for datafile 3 to
"/usr/local/OLlinks/dupdb/system/sysaux01.dbf";
set newname for datafile 4 to
"/usr/local/OLlinks/dupdb/system/users01.dbf";
set newname for datafile 5 to
"/usr/local/OLlinks/dupdb/data01/data1.dbf";
set newname for datafile 6 to
"/usr/local/OLlinks/dupdb/index01/index1.dbf";
restore
check readonly
clone database
executing Memory Script
executing command: SET until clause
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
Starting restore at 24-SEP-12
channel aux1: starting datafile backupset restore
channel aux1: specifying datafile(s) to restore from backup set
restoring datafile 00001 to /usr/local/OLlinks/dupdb/system/system01.dbf
restoring datafile 00002 to /usr/local/OLlinks/dupdb/system/undotbs01.dbf
restoring datafile 00003 to /usr/local/OLlinks/dupdb/system/sysaux01.dbf
restoring datafile 00004 to /usr/local/OLlinks/dupdb/system/users01.dbf
restoring datafile 00005 to /usr/local/OLlinks/dupdb/data01/data1.dbf
restoring datafile 00006 to /usr/local/OLlinks/dupdb/index01/index1.dbf
channel aux1: reading from backup piece /usr/local/OLlinks/kedsp/flash_recovery/KEDSP/backupset/2012_09_24/o1_mf_nnndf_TAG20120924T1
01837_860txxs8_.bkp
channel aux1: restored backup piece 1
piece handle=/usr/local/OLlinks/kedsp/flash_recovery/KEDSP/backupset/2012_09_24/o1_mf_nnndf_TAG20120924T101837_860txxs8_.bkp tag=TAG
20120924T101837
channel aux1: restore complete, elapsed time: 00:00:47
Finished restore at 24-SEP-12
sql statement: CREATE CONTROLFILE REUSE SET DATABASE "DUPDB" RESETLOGS ARCHIVELOG
MAXLOGFILES 16
MAXLOGMEMBERS 3
MAXDATAFILES 100
MAXINSTANCES 8
MAXLOGHISTORY 584
LOGFILE
GROUP 1 ( '/usr/local/OLlinks/dupdb/redo01/redo0101.log', '/usr/local/OLlinks/dupdb/redo02/redo0102.log', '/usr/local/OLlinks/dup
db/redo03/redo0103.log' ) SIZE 50 M ,
GROUP 2 ( '/usr/local/OLlinks/dupdb/redo01/redo0201.log', '/usr/local/OLlinks/dupdb/redo02/redo0202.log', '/usr/local/OLlinks/dup
db/redo03/redo0203.log' ) SIZE 50 M ,
GROUP 3 ( '/usr/local/OLlinks/dupdb/redo01/redo0301.log', '/usr/local/OLlinks/dupdb/redo02/redo0302.log', '/usr/local/OLlinks/dup
db/redo03/redo0303.log' ) SIZE 50 M ,
GROUP 4 ( '/usr/local/OLlinks/dupdb/redo01/redo0401.log', '/usr/local/OLlinks/dupdb/redo02/redo0402.log', '/usr/local/OLlinks/dup
db/redo03/redo0403.log' ) SIZE 50 M ,
GROUP 5 ( '/usr/local/OLlinks/dupdb/redo01/redo0501.log', '/usr/local/OLlinks/dupdb/redo02/redo0502.log', '/usr/local/OLlinks/dup
db/redo03/redo0503.log' ) SIZE 50 M ,
GROUP 6 ( '/usr/local/OLlinks/dupdb/redo01/redo0601.log', '/usr/local/OLlinks/dupdb/redo02/redo0602.log', '/usr/local/OLlinks/dup
db/redo03/redo0603.log' ) SIZE 50 M ,
GROUP 7 ( '/usr/local/OLlinks/dupdb/redo01/redo0701.log', '/usr/local/OLlinks/dupdb/redo02/redo0702.log', '/usr/local/OLlinks/dup
db/redo03/redo0703.log' ) SIZE 50 M ,
GROUP 8 ( '/usr/local/OLlinks/dupdb/redo01/redo0801.log', '/usr/local/OLlinks/dupdb/redo02/redo0802.log', '/usr/local/OLlinks/dup
db/redo03/redo0803.log' ) SIZE 50 M ,
GROUP 9 ( '/usr/local/OLlinks/dupdb/redo01/redo0901.log', '/usr/local/OLlinks/dupdb/redo02/redo0902.log', '/usr/local/OLlinks/dup
db/redo03/redo0903.log' ) SIZE 50 M ,
GROUP 10 ( '/usr/local/OLlinks/dupdb/redo01/redo1001.log', '/usr/local/OLlinks/dupdb/redo02/redo1002.log', '/usr/local/OLlinks/dup
db/redo03/redo1003.log' ) SIZE 50 M
DATAFILE
'/usr/local/OLlinks/dupdb/system/system01.dbf'
CHARACTER SET WE8ISO8859P1
contents of Memory Script:
switch clone datafile all;
executing Memory Script
datafile 2 switched to datafile copy
input datafile copy recid=1 stamp=794858918 filename=/usr/local/OLlinks/dupdb/system/undotbs01.dbf
datafile 3 switched to datafile copy
input datafile copy recid=2 stamp=794858918 filename=/usr/local/OLlinks/dupdb/system/sysaux01.dbf
datafile 4 switched to datafile copy
input datafile copy recid=3 stamp=794858918 filename=/usr/local/OLlinks/dupdb/system/users01.dbf
datafile 5 switched to datafile copy
input datafile copy recid=4 stamp=794858918 filename=/usr/local/OLlinks/dupdb/data01/data1.dbf
datafile 6 switched to datafile copy
input datafile copy recid=5 stamp=794858918 filename=/usr/local/OLlinks/dupdb/index01/index1.dbf
contents of Memory Script:
set until scn 211054288;
recover
clone database
delete archivelog
executing Memory Script
executing command: SET until clause
Starting recover at 24-SEP-12
starting media recovery
channel aux1: starting archive log restore to default destination
channel aux1: restoring archive log
archive log thread=1 sequence=1403
channel aux1: reading from backup piece /usr/local/OLlinks/kedsp/flash_recovery/KEDSP/backupset/2012_09_24/o1_mf_annnn_TAG20120924T1
01923_860tzfd7_.bkp
channel aux1: restored backup piece 1
piece handle=/usr/local/OLlinks/kedsp/flash_recovery/KEDSP/backupset/2012_09_24/o1_mf_annnn_TAG20120924T101923_860tzfd7_.bkp tag=TAG
20120924T101923
channel aux1: restore complete, elapsed time: 00:00:05
archive log filename=/usr/local/OLlinks/dupdb/flash_recovery/DUPDB/archivelog/2012_09_24/o1_mf_1_1403_861phcc3_.arc thread=1 sequenc
e=1403
channel clone_default: deleting archive log(s)
archive log filename=/usr/local/OLlinks/dupdb/flash_recovery/DUPDB/archivelog/2012_09_24/o1_mf_1_1403_861phcc3_.arc recid=1 stamp=79
4858923
media recovery complete, elapsed time: 00:00:02
Finished recover at 24-SEP-12
contents of Memory Script:
shutdown clone;
startup clone nomount pfile= '/u01/app/oracle/product/10.2.0/db_1/dbs/initdupdb.ora';
executing Memory Script
database dismounted
Oracle instance shut down
connected to auxiliary database (not started)
Oracle instance started
Total System Global Area 134217728 bytes
Fixed Size 2054448 bytes
Variable Size 79693520 bytes
Database Buffers 50331648 bytes
Redo Buffers 2138112 bytes
sql statement: CREATE CONTROLFILE REUSE SET DATABASE "DUPDB" RESETLOGS ARCHIVELOG
MAXLOGFILES 16
MAXLOGMEMBERS 3
MAXDATAFILES 100
MAXINSTANCES 8
MAXLOGHISTORY 584
LOGFILE
GROUP 1 ( '/usr/local/OLlinks/dupdb/redo01/redo0101.log', '/usr/local/OLlinks/dupdb/redo02/redo0102.log', '/usr/local/OLlinks/dup
db/redo03/redo0103.log' ) SIZE 50 M ,
GROUP 2 ( '/usr/local/OLlinks/dupdb/redo01/redo0201.log', '/usr/local/OLlinks/dupdb/redo02/redo0202.log', '/usr/local/OLlinks/dup
db/redo03/redo0203.log' ) SIZE 50 M ,
GROUP 3 ( '/usr/local/OLlinks/dupdb/redo01/redo0301.log', '/usr/local/OLlinks/dupdb/redo02/redo0302.log', '/usr/local/OLlinks/dup
db/redo03/redo0303.log' ) SIZE 50 M ,
GROUP 4 ( '/usr/local/OLlinks/dupdb/redo01/redo0401.log', '/usr/local/OLlinks/dupdb/redo02/redo0402.log', '/usr/local/OLlinks/dup
db/redo03/redo0403.log' ) SIZE 50 M ,
GROUP 5 ( '/usr/local/OLlinks/dupdb/redo01/redo0501.log', '/usr/local/OLlinks/dupdb/redo02/redo0502.log', '/usr/local/OLlinks/dup
db/redo03/redo0503.log' ) SIZE 50 M ,
GROUP 6 ( '/usr/local/OLlinks/dupdb/redo01/redo0601.log', '/usr/local/OLlinks/dupdb/redo02/redo0602.log', '/usr/local/OLlinks/dup
db/redo03/redo0603.log' ) SIZE 50 M ,
GROUP 7 ( '/usr/local/OLlinks/dupdb/redo01/redo0701.log', '/usr/local/OLlinks/dupdb/redo02/redo0702.log', '/usr/local/OLlinks/dup
db/redo03/redo0703.log' ) SIZE 50 M ,
GROUP 8 ( '/usr/local/OLlinks/dupdb/redo01/redo0801.log', '/usr/local/OLlinks/dupdb/redo02/redo0802.log', '/usr/local/OLlinks/dup
db/redo03/redo0803.log' ) SIZE 50 M ,
GROUP 9 ( '/usr/local/OLlinks/dupdb/redo01/redo0901.log', '/usr/local/OLlinks/dupdb/redo02/redo0902.log', '/usr/local/OLlinks/dup
db/redo03/redo0903.log' ) SIZE 50 M ,
GROUP 10 ( '/usr/local/OLlinks/dupdb/redo01/redo1001.log', '/usr/local/OLlinks/dupdb/redo02/redo1002.log', '/usr/local/OLlinks/dup
db/redo03/redo1003.log' ) SIZE 50 M
DATAFILE
'/usr/local/OLlinks/dupdb/system/system01.dbf'
CHARACTER SET WE8ISO8859P1
contents of Memory Script:
set newname for tempfile 1 to
"/usr/local/OLlinks/dupdb/temp/temp01.dbf";
switch clone tempfile all;
catalog clone datafilecopy "/usr/local/OLlinks/dupdb/system/undotbs01.dbf";
catalog clone datafilecopy "/usr/local/OLlinks/dupdb/system/sysaux01.dbf";
catalog clone datafilecopy "/usr/local/OLlinks/dupdb/system/users01.dbf";
catalog clone datafilecopy "/usr/local/OLlinks/dupdb/data01/data1.dbf";
catalog clone datafilecopy "/usr/local/OLlinks/dupdb/index01/index1.dbf";
switch clone datafile all;
executing Memory Script
executing command: SET NEWNAME
renamed temporary file 1 to /usr/local/OLlinks/dupdb/temp/temp01.dbf in control file
cataloged datafile copy
datafile copy filename=/usr/local/OLlinks/dupdb/system/undotbs01.dbf recid=1 stamp=794858932
cataloged datafile copy
datafile copy filename=/usr/local/OLlinks/dupdb/system/sysaux01.dbf recid=2 stamp=794858932
cataloged datafile copy
datafile copy filename=/usr/local/OLlinks/dupdb/system/users01.dbf recid=3 stamp=794858932
cataloged datafile copy
datafile copy filename=/usr/local/OLlinks/dupdb/data01/data1.dbf recid=4 stamp=794858932
cataloged datafile copy
datafile copy filename=/usr/local/OLlinks/dupdb/index01/index1.dbf recid=5 stamp=794858932
datafile 2 switched to datafile copy
input datafile copy recid=1 stamp=794858932 filename=/usr/local/OLlinks/dupdb/system/undotbs01.dbf
datafile 3 switched to datafile copy
input datafile copy recid=2 stamp=794858932 filename=/usr/local/OLlinks/dupdb/system/sysaux01.dbf
datafile 4 switched to datafile copy
input datafile copy recid=3 stamp=794858932 filename=/usr/local/OLlinks/dupdb/system/users01.dbf
datafile 5 switched to datafile copy
input datafile copy recid=4 stamp=794858932 filename=/usr/local/OLlinks/dupdb/data01/data1.dbf
datafile 6 switched to datafile copy
input datafile copy recid=5 stamp=794858932 filename=/usr/local/OLlinks/dupdb/index01/index1.dbf
contents of Memory Script:
Alter clone database open resetlogs;
executing Memory Script
database opened
Finished Duplicate Db at 24-SEP-12
Recovery Manager complete.
SQL*Plus: Release 10.2.0.4.0 - Production on Mon Sep 24 18:09:39 2012
Copyright (c) 1982, 2007, Oracle. All Rights Reserved.
Connected.
User altered.
User altered.
User altered.
User altered.
Database closed.
Database dismounted.
ORACLE instance shut down.
ORACLE instance started.
Total System Global Area 134217728 bytes
Fixed Size 2054448 bytes
Variable Size 79693520 bytes
Database Buffers 50331648 bytes
Redo Buffers 2138112 bytes
Database mounted.
Database altered.
Database altered.
Disconnected from Oracle Database 10g Release 10.2.0.4.0 - 64bit Production
oracle:dupdb@kacdb4:/u01/app/oracle/KAC_SCRIPTS/dupdb/logs->
Here is the duplicate log from this morning:
oracle:dupdb@kacdb4:/u01/app/oracle/KAC_SCRIPTS/dupdb/logs-> more clone_database_from_common_20120926.log
SQL*Plus: Release 10.2.0.4.0 - Production on Wed Sep 26 08:28:31 2012
Copyright (c) 1982, 2007, Oracle. All Rights Reserved.
Connected.
SQL> spool /u01/app/oracle/KAC_SCRIPTS/dupdb/logs/DBShutdown.log
SQL> shutdown immediate
Database closed.
Database dismounted.
ORACLE instance shut down.
SQL> spool off
SQL> exit;
Disconnected from Oracle Database 10g Release 10.2.0.4.0 - 64bit Production
SQL*Plus: Release 10.2.0.4.0 - Production on Wed Sep 26 08:28:42 2012
Copyright (c) 1982, 2007, Oracle. All Rights Reserved.
Connected to an idle instance.
File created.
ORACLE instance started.
Total System Global Area 134217728 bytes
Fixed Size 2054448 bytes
Variable Size 79693520 bytes
Database Buffers 50331648 bytes
Redo Buffers 2138112 bytes
Disconnected from Oracle Database 10g Release 10.2.0.4.0 - 64bit Production
Recovery Manager: Release 10.2.0.4.0 - Production on Wed Sep 26 08:28:45 2012
Copyright (c) 1982, 2007, Oracle. All rights reserved.
connected to target database: KEDSP (DBID=3370721566)
connected to auxiliary database: DUPDB (not mounted)
RMAN> RUN
2> {
3> ALLOCATE AUXILIARY CHANNEL aux1 DEVICE TYPE DISK;
4>
5> set until scn 211054288;
6> DUPLICATE TARGET DATABASE TO dupdb
7> PFILE=/u01/app/oracle/product/10.2.0/db_1/dbs/initdupdb.ora
8> DB_FILE_NAME_CONVERT=('/usr/local/OLlinks/kedsp/system/','/usr/local/OLlinks/dupdb/system/','/usr/local/OLlinks/kedsp/temp/','/us
r/local/OLlinks/dupdb/temp/','/usr/local/OLlinks/kedsp/data01/','/usr/local/OLlinks/dupdb/data01/','/usr/local/OLlinks/kedsp/index01
/','/usr/
9> local/OLlinks/dupdb/index01/')
10> LOGFILE
11> GROUP 1 (
12> '/usr/local/OLlinks/dupdb/redo01/redo0101.log',
13> '/usr/local/OLlinks/dupdb/redo02/redo0102.log',
14> '/usr/local/OLlinks/dupdb/redo03/redo0103.log'
15> ) SIZE 50M,
16> GROUP 2 (
17> '/usr/local/OLlinks/dupdb/redo01/redo0201.log',
18> '/usr/local/OLlinks/dupdb/redo02/redo0202.log',
19> '/usr/local/OLlinks/dupdb/redo03/redo0203.log'
20> ) SIZE 50M,
21> GROUP 3 (
22> '/usr/local/OLlinks/dupdb/redo01/redo0301.log',
23> '/usr/local/OLlinks/dupdb/redo02/redo0302.log',
24> '/usr/local/OLlinks/dupdb/redo03/redo0303.log'
25> ) SIZE 50M,
26> GROUP 4 (
27> '/usr/local/OLlinks/dupdb/redo01/redo0401.log',
28> '/usr/local/OLlinks/dupdb/redo02/redo0402.log',
29> '/usr/local/OLlinks/dupdb/redo03/redo0403.log'
30> ) SIZE 50M,
31> GROUP 5 (
32> '/usr/local/OLlinks/dupdb/redo01/redo0501.log',
33> '/usr/local/OLlinks/dupdb/redo02/redo0502.log',
34> '/usr/local/OLlinks/dupdb/redo03/redo0503.log'
35> ) SIZE 50M,
36> GROUP 6 (
37> '/usr/local/OLlinks/dupdb/redo01/redo0601.log',
38> '/usr/local/OLlinks/dupdb/redo02/redo0602.log',
39> '/usr/local/OLlinks/dupdb/redo03/redo0603.log'
40> ) SIZE 50M,
41> GROUP 7 (
42> '/usr/local/OLlinks/dupdb/redo01/redo0701.log',
43> '/usr/local/OLlinks/dupdb/redo02/redo0702.log',
44> '/usr/local/OLlinks/dupdb/redo03/redo0703.log'
45> ) SIZE 50M,
46> GROUP 8 (
47> '/usr/local/OLlinks/dupdb/redo01/redo0801.log',
48> '/usr/local/OLlinks/dupdb/redo02/redo0802.log',
49> '/usr/local/OLlinks/dupdb/redo03/redo0803.log'
50> ) SIZE 50M,
51> GROUP 9 (
52> '/usr/local/OLlinks/dupdb/redo01/redo0901.log',
53> '/usr/local/OLlinks/dupdb/redo02/redo0902.log',
54> '/usr/local/OLlinks/dupdb/redo03/redo0903.log'
55> ) SIZE 50M,
56> GROUP 10 (
57> '/usr/local/OLlinks/dupdb/redo01/redo1001.log',
58> '/usr/local/OLlinks/dupdb/redo02/redo1002.log',
59> '/usr/local/OLlinks/dupdb/redo03/redo1003.log'
60> ) SIZE 50M
61> ;
62> }
63>
using target database control file instead of recovery catalog
allocated channel: aux1
channel aux1: sid=242 devtype=DISK
executing command: SET until clause
Starting Duplicate Db at 26-SEP-12
contents of Memory Script:
set until scn 211054288;
set newname for datafile 1 to
"/usr/local/OLlinks/dupdb/system/system01.dbf";
set newname for datafile 2 to
"/usr/local/OLlinks/dupdb/system/undotbs01.dbf";
set newname for datafile 3 to
"/usr/local/OLlinks/dupdb/system/sysaux01.dbf";
set newname for datafile 4 to
"/usr/local/OLlinks/dupdb/system/users01.dbf";
set newname for datafile 5 to
"/usr/local/OLlinks/dupdb/data01/data1.dbf";
set newname for datafile 6 to
"/usr/local/OLlinks/dupdb/index01/index1.dbf";
restore
check readonly
clone database
executing Memory Script
executing command: SET until clause
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
Starting restore at 26-SEP-12
released channel: aux1
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of Duplicate Db command at 09/26/2012 08:28:53
RMAN-03015: error occurred in stored script Memory Script
RMAN-06026: some targets not found - aborting restore
RMAN-06023: no backup or copy of datafile 6 found to restore
RMAN-06023: no backup or copy of datafile 5 found to restore
RMAN-06023: no backup or copy of datafile 4 found to restore
RMAN-06023: no backup or copy of datafile 3 found to restore
RMAN-06023: no backup or copy of datafile 2 found to restore
RMAN-06023: no backup or copy of datafile 1 found to restore
Recovery Manager complete.
SQL*Plus: Release 10.2.0.4.0 - Production on Wed Sep 26 08:28:53 2012
Copyright (c) 1982, 2007, Oracle. All Rights Reserved.
Connected.
alter user sys identified by "Sco_tch!1"
ERROR at line 1:
ORA-01109: database not open
alter user system identified by "Sco_tch!1"
ERROR at line 1:
ORA-01109: database not open
alter user dbsnmp identified by "Sco_tch!1"
ERROR at line 1:
ORA-01109: database not open
alter user sysman identified by "Sco_tch!1"
ERROR at line 1:
ORA-01109: database not open
ORA-01507: database not mounted
ORACLE instance shut down.
ORACLE instance started.
Total System Global Area 134217728 bytes
Fixed Size 2054448 bytes
Variable Size 79693520 bytes
Database Buffers 50331648 bytes
Redo Buffers 2138112 bytes
ORA-00205: error in identifying control file, check alert log for more info
alter database noarchivelog
ERROR at line 1:
ORA-01507: database not mounted
alter database open
ERROR at line 1:
ORA-01507: database not mounted
Disconnected from Oracle Database 10g Release 10.2.0.4.0 - 64bit Production
oracle:dupdb@kacdb4:/u01/app/oracle/KAC_SCRIPTS/dupdb/logs->
Please let me know if you need anything else.
Sincerely,
Elizabeth

Creating Standby database in OEM 10g

DB = Oracle 10.2.0.4
OS = Solaris 10 Sparc
I am trying to create a physical standby database using the add standby database option within OEM 10g. This is something we have done numerous times before on 10g and 11g db's without a single issue, but for some reason, this time after selecting my RMAN backup location and staging area location , I am getting the following error when I click Next:
RMAN Backup Location - The specified RMAN backup is invalid. Could not identify controlfile from the backup
It is the latest backup (using RMAN catalog) from the previous evening and includes datafiles and control file.
Here is the output for List backup:
BS Key Size Device Type Elapsed Time Completion Time
1741586 7.70G DISK 00:03:26 06-DEC-12
BP Key: 1741590 Status: AVAILABLE Compressed: NO Tag: TAG20121206T220033
Piece Name: /carebackup/oradata/CARELIVE/carelive/backup/df_CARELIVE_4811_1.bus
List of Archived Logs in backup set 1741586
Thrd Seq Low SCN Low Time Next SCN Next Time
1 20013 7974703107 04-DEC-12 7974865046 04-DEC-12
1 20014 7974865046 04-DEC-12 7975209322 05-DEC-12
1 20015 7975209322 05-DEC-12 7975792781 05-DEC-12
1 20016 7975792781 05-DEC-12 7975841363 05-DEC-12
1 20017 7975841363 05-DEC-12 7976016507 05-DEC-12
1 20018 7976016507 05-DEC-12 7976577946 06-DEC-12
1 20019 7976577946 06-DEC-12 7976685352 06-DEC-12
1 20020 7976685352 06-DEC-12 7976816259 06-DEC-12
1 20021 7976816259 06-DEC-12 7976884597 06-DEC-12
1 20022 7976884597 06-DEC-12 7977236969 06-DEC-12
1 20023 7977236969 06-DEC-12 7978009499 06-DEC-12
1 20024 7978009499 06-DEC-12 7978784609 06-DEC-12
1 20025 7978784609 06-DEC-12 7979558556 06-DEC-12
1 20026 7979558556 06-DEC-12 7980614921 06-DEC-12
1 20027 7980614921 06-DEC-12 7981238045 06-DEC-12
1 20028 7981238045 06-DEC-12 7981890156 06-DEC-12
1 20029 7981890156 06-DEC-12 7982119933 06-DEC-12
1 20030 7982119933 06-DEC-12 7982775834 06-DEC-12
1 20031 7982775834 06-DEC-12 7983388279 06-DEC-12
BS Key Type LV Size Device Type Elapsed Time Completion Time
1741587 Full 214.09G DISK 01:15:15 06-DEC-12
List of Datafiles in backup set 1741587
File LV Type Ckp SCN Ckp Time Name
1 Full 7983402310 06-DEC-12 /oracle/oradata/care/carelive/data/system01.dbf
2 Full 7983402310 06-DEC-12 /oracle/oradata/care/carelive/data/undotbs01.dbf
3 Full 7983402310 06-DEC-12 /oracle/oradata/care/carelive/data/sysaux01.dbf
4 Full 7983402310 06-DEC-12 /oracle/oradata/care/carelive/data/large_indexes01.dbf
5 Full 7983402310 06-DEC-12 /oracle/oradata/care/carelive/data/large_indexes02.dbf
6 Full 7983402310 06-DEC-12 /oracle/oradata/care/carelive/data/large_indexes03.dbf
7 Full 7983402310 06-DEC-12 /oracle/oradata/care/carelive/data/large_tables01.dbf
8 Full 7983402310 06-DEC-12 /oracle/oradata/care/carelive/data/large_tables02.dbf
9 Full 7983402310 06-DEC-12 /oracle/oradata/care/carelive/data/large_tables03.dbf
10 Full 7983402310 06-DEC-12 /oracle/oradata/care/carelive/data/small_tables01.dbf
11 Full 7983402310 06-DEC-12 /oracle/oradata/care/carelive/data/small_tables02.dbf
12 Full 7983402310 06-DEC-12 /oracle/oradata/care/carelive/data/small_tables03.dbf
13 Full 7983402310 06-DEC-12 /oracle/oradata/care/carelive/data/small_tables04.dbf
14 Full 7983402310 06-DEC-12 /oracle/oradata/care/carelive/data/medium_tables01.dbf
15 Full 7983402310 06-DEC-12 /oracle/oradata/care/carelive/data/medium_tables02.dbf
16 Full 7983402310 06-DEC-12 /oracle/oradata/care/carelive/data/medium_tables03.dbf
17 Full 7983402310 06-DEC-12 /oracle/oradata/care/carelive/data/small_indexes01.dbf
18 Full 7983402310 06-DEC-12 /oracle/oradata/care/carelive/data/medium_indexes01.dbf
19 Full 7983402310 06-DEC-12 /oracle/oradata/care/carelive/data/tools01.dbf
20 Full 7983402310 06-DEC-12 /oracle/oradata/care/carelive/data/small_indexes02.dbf
Backup Set Copy #1 of backup set 1741587
Device Type Elapsed Time Completion Time Compressed Tag
DISK 01:15:15 06-DEC-12 NO TAG20121206T220415
List of Backup Pieces for backup set 1741587 Copy #1
BP Key Pc# Status Piece Name
1741591 1 AVAILABLE /carebackup/oradata/CARELIVE/carelive/backup/df_CARELIVE_4812_1.bus
1741592 2 AVAILABLE /carebackup/oradata/CARELIVE/carelive/backup/df_CARELIVE_4812_2.bus
1741593 3 AVAILABLE /carebackup/oradata/CARELIVE/carelive/backup/df_CARELIVE_4812_3.bus
1741594 4 AVAILABLE /carebackup/oradata/CARELIVE/carelive/backup/df_CARELIVE_4812_4.bus
1741595 5 AVAILABLE /carebackup/oradata/CARELIVE/carelive/backup/df_CARELIVE_4812_5.bus
1741596 6 AVAILABLE /carebackup/oradata/CARELIVE/carelive/backup/df_CARELIVE_4812_6.bus
1741597 7 AVAILABLE /carebackup/oradata/CARELIVE/carelive/backup/df_CARELIVE_4812_7.bus
1741598 8 AVAILABLE /carebackup/oradata/CARELIVE/carelive/backup/df_CARELIVE_4812_8.bus
1741599 9 AVAILABLE /carebackup/oradata/CARELIVE/carelive/backup/df_CARELIVE_4812_9.bus
1741600 10 AVAILABLE /carebackup/oradata/CARELIVE/carelive/backup/df_CARELIVE_4812_10.bus
1741601 11 AVAILABLE /carebackup/oradata/CARELIVE/carelive/backup/df_CARELIVE_4812_11.bus
1741602 12 AVAILABLE /carebackup/oradata/CARELIVE/carelive/backup/df_CARELIVE_4812_12.bus
1741603 13 AVAILABLE /carebackup/oradata/CARELIVE/carelive/backup/df_CARELIVE_4812_13.bus
1741604 14 AVAILABLE /carebackup/oradata/CARELIVE/carelive/backup/df_CARELIVE_4812_14.bus
1741605 15 AVAILABLE /carebackup/oradata/CARELIVE/carelive/backup/df_CARELIVE_4812_15.bus
1741606 16 AVAILABLE /carebackup/oradata/CARELIVE/carelive/backup/df_CARELIVE_4812_16.bus
1741607 17 AVAILABLE /carebackup/oradata/CARELIVE/carelive/backup/df_CARELIVE_4812_17.bus
1741608 18 AVAILABLE /carebackup/oradata/CARELIVE/carelive/backup/df_CARELIVE_4812_18.bus
1741609 19 AVAILABLE /carebackup/oradata/CARELIVE/carelive/backup/df_CARELIVE_4812_19.bus
1741610 20 AVAILABLE /carebackup/oradata/CARELIVE/carelive/backup/df_CARELIVE_4812_20.bus
1741611 21 AVAILABLE /carebackup/oradata/CARELIVE/carelive/backup/df_CARELIVE_4812_21.bus
1741612 22 AVAILABLE /carebackup/oradata/CARELIVE/carelive/backup/df_CARELIVE_4812_22.bus
BS Key Size Device Type Elapsed Time Completion Time
1741658 104.19M DISK 00:00:04 06-DEC-12
BP Key: 1741679 Status: AVAILABLE Compressed: NO Tag: TAG20121206T231939
Piece Name: /carebackup/oradata/CARELIVE/carelive/backup/df_CARELIVE_4813_1.bus
List of Archived Logs in backup set 1741658
Thrd Seq Low SCN Low Time Next SCN Next Time
1 20032 7983388279 06-DEC-12 7983637536 06-DEC-12
BS Key Type LV Size Device Type Elapsed Time Completion Time
1741702 Full 7.33M DISK 00:00:02 06-DEC-12
BP Key: 1741704 Status: AVAILABLE Compressed: NO Tag: TAG20121206T231950
Piece Name: /carebackup/oradata/CARELIVE/carelive/backup/ctlc-3640364239-20121206-00
Control File Included: Ckp SCN: 7983638867 Ckp time: 06-DEC-12
SPFILE Included: Modification time: 06-DEC-12
The only difference between creating a standby for this db and others we have created is that the file system the backups are stored on is on a non-global zone shared via nfs mount.
I know that when I try and share that filesystem with other servers I get the message:
share_nfs: Cannot share filesystems in non-global zones
If the /backup filesystem is not shared with any other servers would OEM be able to read from that NGZ? The filesystem is available to connect to using ssh from other locations, but not sure how OEM handles this part of the process.
Any advice would be great.
Regards,
JP

Thanks for the reply. I thought that is what I would need to do. However this link is very useful and could resolve the issue. I have yet to raise it with the system admin guys here yet but will do and will report back on outcome.
http://faizsulaiman.com/mount-nfs-solaris-non-global-zone/

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!

OEM 10g - Upgrade Recovery Catalog

Similar Messages

Maybe you are looking for