RMAN incompatibility issue

Hi All,
Working on DB v10.2.0.3.0 and 10.1.0.5 .0
OS:AIX 64 bits
We used to get the output when connecting from 10.2.0.3.0 to RMAN 10.2.0.3.0 as below:
SQL> select distinct object_type from rc_rman_status;
OBJECT_TYPE
ARCHIVELOG
DB FULL
But the same query doesn't work when connecting from 10.1.0.5 .0 to RMAN v10.2.0.3.0:
SQL> select distinct object_type from rc_rman_status;
OBJECT_TYPE
The above output is blank.
Also on doing some research,OBJECT_TYPE column doesn't exist in rc_rman_status for 10.1.0.5.0.
Oracle® Database Recovery Manager Reference
10g Release 1 (10.1)
Part Number B10770-02
RC_RMAN_STATUS
URL: http://download.oracle.com/docs/cd/B14117_01/server.101/b10770/rcviews28.htm#RCMRF381
So is there any other table or view apart from rc_rman_status where from we can extract this information - DB Full or Archivelog since Object_type column is not present in rc_rman_status in v10.1.0.5.
Thanks for your time!
Regards,

Please configure RMAN settings and try to run full backup again.
RMAN> show all; --> will display current settings.
Arun wrote:
Hi,
I have registered the database and fired the full backup and getting the following message
channel ORA_DISK_1: starting piece 1 at 06-OCT-11
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03009: failure of backup command on ORA_DISK_1 channel at 10/06/2011 01:41:22
ORA-19502: write error on file "/u01/app/oracle/product/dbname/dbs/df1c.dbname.t763781956.s6.p1", blockno 610433 (blocksize=8192)See, the backup pieces are going to $ORACLE_HOME/dbs directory.
Arun wrote:
ORA-27072: File I/O error
SVR4 Error: 25: Inappropriate ioctl for device
Additional information: 4
Additional information: 610433
Additional information: 841728
Do I need to reset the incarnation ? Please help me in this
Regards
ArunRegards,
Suresh.GV
Edited by: sureshgali on Oct 6, 2011 1:22 AM

Similar Messages

  • Version incompatibility issue with Interop.SAPbobsCOM.dll in SBO 2004

    Hi,
    I have encountered an incompatibility issue in DI API 2004 across different patch level-versions. Originally, I developed an application in SBO 2004 pl4 environment. Now, some of the customers who were installing the application, notified me that the application has a login problem. It turned out that the CompanyClass.connect() method returns an error message "object reference not set to an instance of an object", when the DI API version installed in the production environment is higher (in this case, pl7) than the DI API version which was used in the development environment.
    I figured out that the problem can be fixed by replacing the Interop.SAPbobsCOM.dll file in the application directory by a newer version that reflects the DI API that is installed in the system. However, it seems a rather lousy workaround, if the customer needs to manually replace the dll. Maybe the installer could be customized to "sniff" the correct DI API level, but this too would be a pretty kludgy solution.
    Does anyone know a better solution to this problem ?
    Regards,
    Henry

    normally this is not a problem as long as they don't change the signatures on the DI-API (which they said they wouldn't) but it appears in P5 they changed that signature... we noticed some enums that got added and a few minor changes.

  • Incompatibility issue - WLC 5508 and ACS 5.4

    Hi,
    This is my scenario:
    Cisco WLC 5508 firmware 7.4.110.20 and ACS 5.4, two WLAN eap/tls, many client  can't connect to WLAN and on ACS i receive the following error:
    Authentication failed : 11051 RADIUS packet contains invalid state attribute
    workaround:
    1 -Check the network device or AAA Client for hardware problems.
    2-known RADIUS compatibility issues.
    3-Check the network that connects the device to ACS for hardware problems
    there are some incompatibility issue between WLC and ACS ? the compatibility matrix document for wireless imposes the 7.5 firmware for WLC.
    What do you think is possibile ?

    Are there any other errors shown in the details of the failed authentication?
    We may need to look at service logs in debug mode, opening a TAC case would be the best way to go about this.
    Javier Henderson
    Cisco Systems

  • Incompatibility issues with the new flash pplayer

    Ever since I installed the new version of flash 11.5 I have had major issues with watching video etc. I am also into astronomy. Myself and many others have paid a lot of money to use Sloohs robotic telescopes in their canary islands observatory.
    I now cannot enjoy this because the flash player has compatibility issues with your browser. Me and quite a lot of others are getting rather annyoed this opportunity is being ruined because adobe have released a version of flash without checking it's compatibility with all browsers first.
    May I suggest that you contact them and ask that you are notified about new versions and release dates to ensure that you can make necessary amendments to prevent incompatibility issues.
    That way lots of angry people like me will not be complaning.

    At work, symantec endpoint. At home, norton. Ever since firefox 15, no flash version works except for 11.2. Now that ff18 was pushed out, it "forces" the upgrade to 11.5, and absolutely will not accept anything less. But as with any version of flash that was not 11.2, it just causes firefox to freeze up completely.

  • Incompatibility issues when saving BW workbook in early excel versions

    When saving a BW workbooks to my desktop for example so that I can then send it to a user to view the report I get incompatibility issues when saving workbook to earlier excel versions.  I am currently using 2007 and when I save the workbook to Excel 97 - 2003 then I get incompatibility messages.  If I ignore these and just save then no one is able to open the workbook.  This means that I cannot also save workbooks on the reporting system as those users not using 2007 cannot view them. The message that I get is that 'the features of this workbook are not supported by the earlier features of Excel.'

    Hi,
    Please refer to this note,
    Note 1152092 - Error opening MS Excel 2007 workbook in MS Excel 2003
    Usually when you do any formatting feature available in Excel 2007 to the workbook it would throw you the error, not sure if you are formatting the workbook.
    Regards,
    Mani

  • AEBS hard drive incompatibility issues

    Is there an updated list of incompatible hard drives for the AEBS? I have an external 300GB Seagate that is formatted FAT32 and does not mount. It shows up partially under the DISKS menu in Airport Utility, meaning it shows that there is storage connected but doesn't show a volume. I thought the new 5.2.1 update was going to do the trick since it dealt with incompatibility issues but not so. I have tried everything except reformatting because I cannot lose all the info that's on the drive currently. Any help would be appreciated.

    I've checked out your list and posted my experiences.
    From the tests that I've run over the last week or so, the Macally PHR-100AC 3.5" HDD enclosure should work. Failures 'seems' to point specifically to the hard drive used.
    I have now used 4 different drives (different sizes, manufacturers etc..) in 2 Macally cases (both with updated firmware) and the only failure - via USB but not FireWire - was the Western Digital Caviar SE WD1600. Reformatting it with WD's utility is Windows XP via Bootcamp cleared up the issue with the drive and is now fully functional and consistent under Mac OS X and through the AEBS. I still have one more WD1600 to look at.
    Aug 23 09:43:06 Patricks-iMac-Core-Duo-2 kernel[0]: USBF: 459.963 AppleUSBUHCI[0x39ce000]::DoControlTransfer sync request on workloop thread. Use async!
    Aug 23 09:43:06 Patricks-iMac-Core-Duo-2 kernel[0]: USBF: 460.271 AppleUSBUHCI[0x39ce000]::DeviceRequest - buffer dmaCommand (0x3b76900) already had memory descriptor (0x39a6100) - clearing

  • RMAN Backup Issue when Full backup file was missing

    Hi,
    On : 11.2.0.2 version, Recovery Manager
    RMAN Backup issue
    Last week we had the NFS Issue where we backup the files onto NFS.
    The problem occurred in the below sequence
    Saturday the backup was successful
    Saturday before deleting the backup files they are copied to tape
    Deleting the backup files via OS command
    Sunday Full backup started but due the NFS issue backup failed(Killed the instance and restarted)
    Did the RMAN Incremental backup which worked on Monday
    On Tuesday RMAN started complaining and started doing the Full backup.
    no parent backup or copy of datafile 1 found
    no parent backup or copy of datafile 3 found
    no parent backup or copy of datafile 24 foundSony any idea why the Incremental backup worked on Monday but not on Tuesday
    Regards
    NM

    Ok here is why I would like exact filenames..
    1) to speed the time of recovery. I am much more familiar with traditional recovery methods than RMAN, and while I myself installed and suggested RMAN for backups, our other (11i) database does not use RMAN and so I am more familiar with traditional recovery. So to be able to recover quickly I want to have these files as close as possible to the original names so that I can use my standard script (from a trace file) to recreate the control fiile. If I can get RMAN to spit out the filies with original names but keep RMAN for making the backup, I may ditch the rman bacjup script in chron and write a traditional hot backup script which copies the files the old fashioned way.
    2) to reduce cloning time. The RMAN duplicate command is not as good as I thought. I was actually easier for me to restore RMAN backups first to a box that has all the same paths, and THEN shutdown (cold) these files and copy them cold to another server, and restore from there. Agaiin if I can get the original file names, I could choose to do recovery either way (RMAN or traditional) in a real emergency instead of being forced to use rman.
    3) to be able to switch to a backup file in the FRA without having to rename it. Seems logical if it is already named correctly.
    thanks ! Marvi

  • RMAN  script issue ....

    Oracle Server - Enterprise Edition - Version: 10.2.0.3
    RMAN Catalog : 10.2.0.4
    I am using the follwoing script for backup :
    4> run
    5> {
    6>     allocate channel dev1 type disk format 'Z:\Rbackup\DMP\db_t%t_s%s_p%p';
    7>     allocate channel dev2 type disk format 'Z:\Rbackup\DMP\db_t%t_s%s_p%p';
    8>     backup database FILESPERSET 20 ;
    9>     backup archivelog all archivelog until time 'sysdate-1' delete all input ;
    10>     release channel dev1 ;   
    11>     release channel dev2 ;   
    12> }The issue is with backup archivelog all archivelog until time 'sysdate-1' delete all input ;
    This command gives error
    ORA-19588: Archived Log Recid Stamp Is No Longer Valid
    even after doing crosscheck .
    Referred Metalink ID : 1189883.1
    which clearly indicates that the statement
    backup archivelog all archivelog until time 'sysdate-1' delete all input ;
    is wrong by logic and is the reason for the issue .
    And suggests to use
    backup archivelog until time 'sysdate-1' delete all input ;
    or
    backup archivelog all delete input ;
    which definitely do not serve the purpose .
    The logic that needs to be implemented is
    I need to backup all archivelogs and delete archivelogs until sysdate-1  .....
    How can I do this ? Please help ....
    Regards
    Renjith Madhavan

    Of course. You have asked Oracle to backup files as of 1 day old. Your command is explicitly stating that it is not to backup files newer than 1 day old.
    Read and understand "archivelogRecordSpecifier" at
    http://download.oracle.com/docs/cd/B19306_01/backup.102/b14194/rcmsynta008.htm#sthref121
    UNTIL TIME "Specifies the end date for a sequence of archived redo log files"
    It is actually used when doing RECOVER and RESTORE so as to do Point In Time Recovery.
    Backups are not done with UNTIL TIME. The only scenario where someone would backup until TIME is when he is writing separate sets of backups deliberately to different backupsets (e.g. one backupset representing 01-Dec will subsequently be copied to another location or to Tape-1, the next backupset representing 02-Dec will be copied to a different location or to Tape-2 etc).
    However, when you do a BACKUP DATABASE today, you have to ensure that you BACKUP ARCHIVELOG upto the latest archivelog else, you will NOT be able to use today's database backup for restore and recovery.
    Hemant K Chitale
    Edited by: Hemant K Chitale on Dec 6, 2010 2:57 PM

  • RMAN backup issue

    Oracle 11.2.0.1
    Windows 7 Home Premium
    RMAN> backup database;
    Starting backup at 05-MAR-12
    using channel ORA_DISK_1
    channel ORA_DISK_1: starting full datafile backup set
    channel ORA_DISK_1: specifying datafile(s) in backup set
    RMAN-03009: failure of backup command on ORA_DISK_1 channel at 03/05/2012 12:25:05
    ORA-19602: cannot backup or copy active file in NOARCHIVELOG mode
    continuing other job steps, job failed will not be re-run
    channel ORA_DISK_1: starting full datafile backup set
    channel ORA_DISK_1: specifying datafile(s) in backup set
    including current control file in backup set
    including current SPFILE in backup set
    channel ORA_DISK_1: starting piece 1 at 05-MAR-12
    channel ORA_DISK_1: finished piece 1 at 05-MAR-12
    piece handle=E:\APP\NISHA\FLASH_RECOVERY_AREA\ORCL\BACKUPSET\2012_03_05\O1_MF_NCSNF_TAG20120305T122505_7O8RTBXJ_.BKP tag=TAG20120305T122505 comment=NONE
    channel ORA_DISK_1: backup set complete, elapsed time: 00:00:01
    RMAN-00571: ===========================================================
    RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
    RMAN-00571: ===========================================================
    RMAN-03009: failure of backup command on ORA_DISK_1 channel at 03/05/2012 12:25:05
    ORA-19602: cannot backup or copy active file in NOARCHIVELOG mode
    RMAN> 1.What is the problem in above scnerio ?
    2.How to take RMAN backup when db is down ?
    3.How to take RMAN backup when db is noarchivelog mode ?
    Please help me. Thank you.

    I am trying to do a full RMAN cold backup and am getting the following :
    ORA-19602: cannot backup or copy active file in NOARCHIVELOG mode
    What’s the cause ?
    Here’s the example
    connected to target database (not started)
    Oracle instance started
    database mounted Total System Global Area 1610612736 bytes Fixed Size 2056504 bytes
    Variable Size 603983560 bytes
    Database Buffers 989855744 bytes
    Redo Buffers 14716928 bytes using target database control file instead of recovery catalog
    allocated channel: backup_disk1
    channel backup_disk1: sid=4977 instance=TEST1 devtype=DISK Starting backup at 31-OCT-13
    channel backup_disk1: starting full datafile backupset
    channel backup_disk1: specifying datafile(s) in backupset
    RMAN-03009: failure of backup command on backup_disk1 channel at 31/10/2013 20:18:45
    ORA-19602: cannot backup or copy active file in NOARCHIVELOG mode
    continuing other job steps, job failed will not be re-run
    channel backup_disk1: starting full datafile backupset
    channel backup_disk1: specifying datafile(s) in backupset
    RMAN-03009: failure of backup command on backup_disk1 channel at 13/10/2013 20:18:45
    ORA-19602: cannot backup or copy active file in NOARCHIVELOG mode
    continuing other job steps, job failed will not be re-run
    channel backup_disk1: starting full datafile backupset
    channel backup_disk1: specifying datafile(s) in backupset
    RMAN-03009: failure of backup command on backup_disk1 channel at 13/10/2013 20:18:46
    ORA-19602: cannot backup or copy active file in NOARCHIVELOG mode
    continuing other job steps, job failed will not be re-run
    channel backup_disk1: starting full datafile backupset
    channel backup_disk1: specifying datafile(s) in backupset
    released channel: backup_disk1
    RMAN-00571: ===========================================================
    RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
    RMAN-00571: ===========================================================
    RMAN-03009: failure of backup command on backup_disk1 channel at 13/10/2013 20:18:47
    ORA-19602: cannot backup or copy active file in NOARCHIVELOG mode
    RMAN>
    The cause is simple, the database has not been shutdown cleanly. You will require to restart the database and shutdown again, if in a RAC you will have to shutdown all instances cleanly.
    Disabing archive log and attempting to backup the database will demonstrate the cause.
    SQL> startup force;
    ORACLE instance started.
    Total System Global Area 1235959808 bytes
    Fixed Size 2175288 bytes
    Variable Size 620760776 bytes
    Database Buffers 603979776 bytes
    Redo Buffers 9043968 bytes
    Database mounted.
    Database opened.
    SQL> shutdown abort;
    ORACLE instance shut down.
    SQL> startup mount;
    ORACLE instance started.
    Total System Global Area 1235959808 bytes
    Fixed Size 2175288 bytes
    Variable Size 620760776 bytes
    Database Buffers 603979776 bytes
    Redo Buffers 9043968 bytes
    Database mounted.
    SQL>
    Now we’ll try again to backup datafile 1.
    RMAN> backup datafile 1;
    Starting backup at 31-OCT-13
    using target database control file instead of recovery catalog
    allocated channel: ORA_DISK_1
    channel ORA_DISK_1: SID=133 device type=DISK
    channel ORA_DISK_1: starting compressed full datafile backup set
    channel ORA_DISK_1: specifying datafile(s) in backup set
    RMAN-00571: ===========================================================
    RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
    RMAN-00571: ===========================================================
    RMAN-03009: failure of backup command on ORA_DISK_1 channel at 13/10/2013 20:43:34
    ORA-19602: cannot backup or copy active file in NOARCHIVELOG mode
    This is simply because we issue a shutdown abort on the instance. However, just preforming a recovery will allow you to backup as required.
    SQL> recover database;
    Media recovery complete.
    SQL> exit
    Disconnected from Oracle Database 11g Enterprise Edition Release 11.2.0.1.0 – 64bit Production
    With the Partitioning, OLAP, Data Mining and Real Application Testing options
    C:UsersGary>rman target sys/passwd@db11g
    Recovery Manager: Release 11.2.0.1.0 – Production on Thu  Oct 31 20:44:15 2010
    Copyright (c) 1982, 2009, Oracle and/or its affiliates. All rights reserved.
    connected to target database: DB10G (DBID=3002158372, not open)
    RMAN> backup datafile 1;
    Starting backup at 06-DEC-10using target database control file instead of recovery catalog
    allocated channel: ORA_DISK_1channel ORA_DISK_1: SID=125 device type=DISK
    channel ORA_DISK_1: starting compressed full datafile backup set
    channel ORA_DISK_1: specifying datafile(s) in backup set
    input datafile file number=00001 name=C:APPGARYORACLEPRODUCT10.2.0DB_1ORADATADB10GSYSTEM01.DBF
    channel ORA_DISK_1: starting piece 1 at 31-OCT-13
    channel ORA_DISK_1: finished piece 1 at 31-OCT-13
    piece handle=C:APPGARYORACLEPRODUCT10.2.0DB_1FLASH_RECOVERY_AREADB10GBACKUPSET2010_12_06O1_MF_NNNDF_TAG20101206T204423_6HTCR810_.BKP tag=TAG20101206T204423 comment=NONE
    channel ORA_DISK_1: backup set complete, elapsed time: 00:00:45
    Finished backup at 31-OCT-13
    Starting Control File and SPFILE Autobackup at 31-OCT-13
    piece handle=C:APPGARYORACLEPRODUCT10.2.0DB_1FLASH_RECOVERY_AREADB10GAUTOBACKUP2010_12_06O1_MF_S_737066556_6HTCSQVF_.BKP comment=NONE
    Finished Control File and SPFILE Autobackup at 31-OCT-13
    RMAN> exit
    Interestingly, even with the recovery performed, we cannot switch back to archivelog mode without a clean shutdown.
    SQL> alter database archivelog;
    alter database archivelog*
    ERROR at line 1:ORA-00265: instance recovery required, cannot set ARCHIVELOG mode
    SQL> recover database;
    ORA-00283: recovery session canceled due to errors
    ORA-00264: no recovery required
    SQL> alter database archivelog;
    alter database archivelog*
    ERROR at line 1:ORA-00265: instance recovery required, cannot set ARCHIVELOG mode
    So we’ll startup and shutdown again. You cannot use the force option since that still does not perform a normal shutdown and you’ll get the same error.
    SQL> alter database open;
    Database altered.
    SQL> shutdown immediate;
    Database closed.
    Database dismounted.
    ORACLE instance shut down.
    SQL> startup mount;
    ORACLE instance started.
    Total System Global Area 1235959808 bytes
    Fixed Size 2175288 bytes
    Variable Size 620760776 bytes
    Database Buffers 603979776 bytes
    Redo Buffers 9043968 bytes
    Database mounted.
    SQL> alter database archivelog;
    Database altered.
    SQL> alter database open;
    Database altered.

  • RMAN Duplicate issue

    hi,
    I have taken fresh rman backup of the source which is on ASM.
    RMAN>List backup;
    1 Full 1619742 28-SEP-11 +DATA/devdb/datafile/system.256.705775043
    4 Full 1619742 28-SEP-11 +DATA/devdb/datafile/users.259.705775045
    2 Full 1619875 28-SEP-11 +DATA/devdb/datafile/sysaux.257.705775043
    3 Full 1619875 28-SEP-11 +DATA/devdb/datafile/undotbs1.258.705775045
    5 Full 1619875 28-SEP-11 +DATA/devdb/datafile/undotbs2.264.705775347
    I have ASM Configured and also creted the +DATA diskgrounp and the system is in no-mount.
    Auxiliary and Target path is same. ie., DATA.  Also, on auxiliary i have specified     db_create_file_dest='DATA'
    When I run teh below duplicate command, It is trying to restore it to a different path on Auxiliary.
    run {
    allocate auxiliary channel ch1 type disk;
    duplicate target database to ORCL;
    ORA-19504: failed to create file "/u02/app/oradata/rman/system01.dbf"
    ORA-27040: file create error, unable to create file
    Linux Error: 2: No such file or directory
    Ideally, it should get the info about the PATH / file system from the SOURCE controlfile.
    But no idea from where it is getting this.

    Thanks for your repply !
    I can get the point of the ORA-279, that can be a normal error.
    But why about the performance issue ?
    Of course it is depence what I have in the archive log.
    Some body can help me to monitor what is take match times ?
    I have get a look at : Alert.log, rman.log, ASM alert.log et SAN disk load with out information !
    Is it posible to start more detail log at RMAN level ?
    Thanks for your advice !!
    Best Regards

  • Rman restore issue

    Hi friend;
    I have 11.2.0.1 RAC+ASM system on IAX6. My db size almost 3 Tb. In a day i take 2 full backup via rman,evert 20 min archivelog taken
    My question is:
    1. When i use list backup i have very long list which its hard to understad for me,is there any easy method?
    2. If i want to see my lastest backup details how i can achive this
    3. If i want to restore just one of my tabespace to sysdate-1, which syntax i should use(There are different tags for backup,what syntax should be) for this issue
    Thanks

    user12203572 wrote:
    Hi friend;
    I have 11.2.0.1 RAC+ASM system on IAX6. My db size almost 3 Tb. In a day i take 2 full backup via rman,evert 20 min archivelog taken
    My question is:
    1. When i use list backup i have very long list which its hard to understad for me,is there any easy method?
    2. If i want to see my lastest backup details how i can achive thisI do not understand what is exactly problem.But if this is performance problem then you have to take AWR/STATSPACK report and investigate exact problem.In additionally you can use views like v$backup_files,v$backup_set,v$backup_datafile and according COMPLATION TIME you can get last and any time backup.
    3. If i want to restore just one of my tabespace to sysdate-1, which syntax i should use(There are different tags for backup,what syntax should be) for this issue
    In this case you have use SET UNTIL TIME clause through rman then RESTORE DATABASE ,RECOVER DATABASE.

  • RMAN channel issue

    Hi friends;
    I need one advice,Before start my rman backup i allocate channel like
    run
    ALLOCATE CHANNEL C1 device type 'sbt_tape' ;
    ALLOCATE CHANNEL C2 device type 'sbt_tape' ;
    ALLOCATE CHANNEL C3 device type 'sbt_tape' ;
    ALLOCATE CHANNEL C4 device type 'sbt_tape' ;
    ALLOCATE CHANNEL C5 device type 'sbt_tape' ;
    ALLOCATE CHANNEL C6 device type 'sbt_tape' ;
    ALLOCATE CHANNEL C7 device type 'sbt_tape' ;
    BACKUP SCRIPT HERE
    RELEASE CHANNEL C1;
    RELEASE CHANNEL C2;
    RELEASE CHANNEL C3;
    RELEASE CHANNEL C4;
    RELEASE CHANNEL C5;
    RELEASE CHANNEL C6;
    RELEASE CHANNEL C7;
    Backup is very slow db size almost 5 Tb and almost it takes 4-5 hours.We use virtaul disk library(AIX TSM) My question is there any way to run this process more faster, or is there any comment which i cant find to direct each channel different disk in rman script?
    Thanks
    Helios

    Hi,
    I have this kind of issues quite a few times. Restarting the master backup server (where backup software runs, TSM server in your case), or restarting tape library resolved the problem (I never found problem or resolved at ORacle/RMAN side).
    Currently i have a Linux server where backup speed is very very low and this is because of slow read from the file system which is on my storage for which my vendor asks to install latest storage firmware. So, if your file system IO is OK, you can try resolving efforts to be ishifted at tape library or backup server side.
    Thanks

  • RMAN recovery Issue

    Hi Expert,
    I having a issue when do db recovery with following error. My db is not in archivelog mode. Kindly advise Tks
    channel dev1: restore complete
    Finished restore at 20-AUG-10
    Starting recover at 20-AUG-10
    starting media recovery
    unable to find archive log
    archive log thread=1 sequence=1
    Oracle Error:
    ORA-01547: warning: RECOVER succeeded but OPEN RESETLOGS would get error below
    ORA-01190: controlfile or data file 1 is from before the last RESETLOGS
    ORA-01110: data file 1: '/export/home/oracleas/oradata/orcl/system01.dbf'
    released channel: dev1
    RMAN-00571: ===========================================================
    RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
    RMAN-00571: ===========================================================
    RMAN-03002: failure of recover command at 08/20/2010 15:12:34
    RMAN-06054: media recovery requesting unknown log: thread 1 seq 1 lowscn 8165752
    Recovery Manager complete.

    Hi,
    Information as per below:
    RMAN> list incarnation of database;
    using target database controlfile instead of recovery catalog
    List of Database Incarnations
    DB Key Inc Key DB Name DB ID STATUS Reset SCN Reset Time
    1 1 ORCL 1236121495 PARENT 1 20-JUN-06
    2 2 ORCL 1236121495 CURRENT 743480 15-JAN-10
    3 3 ORCL 1236121495 ORPHAN 8165752 20-AUG-10
    RMAN> list backup;
    List of Backup Sets
    ===================
    BS Key Type LV Size Device Type Elapsed Time Completion Time
    1 Full 1G DISK 00:01:58 20-AUG-10
    BP Key: 1 Status: AVAILABLE Compressed: NO Tag: TAG20100820T122103
    Piece Name: /export/home/oracleas/infra/backup/01llqgtf_1_1
    List of Datafiles in backup set 1
    File LV Type Ckp SCN Ckp Time Name
    1 Full 8165751 20-AUG-10 /export/home/oracleas/oradata/orcl/system01.dbf
    2 Full 8165751 20-AUG-10 /export/home/oracleas/oradata/orcl/undotbs01.dbf
    3 Full 8165751 20-AUG-10 /export/home/oracleas/oradata/orcl/sysaux01.dbf
    4 Full 8165751 20-AUG-10 /export/home/oracleas/oradata/orcl/users01.dbf
    5 Full 8165751 20-AUG-10 /export/home/oracleas/oradata/orcl/portal.dbf
    6 Full 8165751 20-AUG-10 /export/home/oracleas/oradata/orcl/ptldoc.dbf
    7 Full 8165751 20-AUG-10 /export/home/oracleas/oradata/orcl/ptlidx.dbf
    8 Full 8165751 20-AUG-10 /export/home/oracleas/oradata/orcl/ptllog.dbf
    9 Full 8165751 20-AUG-10 /export/home/oracleas/oradata/orcl/ias_meta01.dbf
    10 Full 8165751 20-AUG-10 /export/home/oracleas/oradata/orcl/discopltm1.dbf
    11 Full 8165751 20-AUG-10 /export/home/oracleas/oradata/orcl/discopltc1.dbf
    12 Full 8165751 20-AUG-10 /export/home/oracleas/oradata/orcl/dcm.dbf
    13 Full 8165751 20-AUG-10 /export/home/oracleas/oradata/orcl/oss_sys01.dbf
    14 Full 8165751 20-AUG-10 /export/home/oracleas/oradata/orcl/wcrsys01.dbf
    15 Full 8165751 20-AUG-10 /export/home/oracleas/oradata/orcl/b2b_rt.dbf
    16 Full 8165751 20-AUG-10 /export/home/oracleas/oradata/orcl/b2b_dt.dbf
    17 Full 8165751 20-AUG-10 /export/home/oracleas/oradata/orcl/b2b_idx.dbf
    18 Full 8165751 20-AUG-10 /export/home/oracleas/oradata/orcl/b2b_lob.dbf
    19 Full 8165751 20-AUG-10 /export/home/oracleas/oradata/orcl/orabpel.dbf
    20 Full 8165751 20-AUG-10 /export/home/oracleas/oradata/orcl/bam.dbf
    21 Full 8165751 20-AUG-10 /export/home/oracleas/oradata/orcl/oca.dbf
    22 Full 8165751 20-AUG-10 /export/home/oracleas/oradata/orcl/uddisys01.dbf
    23 Full 8165751 20-AUG-10 /export/home/oracleas/oradata/orcl/attrs1_oid.dbf
    24 Full 8165751 20-AUG-10 /export/home/oracleas/oradata/orcl/battrs1_oid.dbf
    25 Full 8165751 20-AUG-10 /export/home/oracleas/oradata/orcl/gcats1_oid.dbf
    26 Full 8165751 20-AUG-10 /export/home/oracleas/oradata/orcl/gdefault1_oid.dbf
    27 Full 8165751 20-AUG-10 /export/home/oracleas/oradata/orcl/svrmg1_oid.dbf
    28 Full 8165751 20-AUG-10 /export/home/oracleas/oradata_mygst/very_large_data.dbf
    29 Full 8165751 20-AUG-10 /export/home/oracleas/oradata_mygst/very_large_indexes. dbf
    30 Full 8165751 20-AUG-10 /export/home/oracleas/oradata_mygst/large_indexes.dbf
    31 Full 8165751 20-AUG-10 /export/home/oracleas/oradata_mygst/medium_data.dbf
    32 Full 8165751 20-AUG-10 /export/home/oracleas/oradata_mygst/medium_indexes.dbf
    33 Full 8165751 20-AUG-10 /export/home/oracleas/oradata_mygst/small_data.dbf
    34 Full 8165751 20-AUG-10 /export/home/oracleas/oradata_mygst/small_indexes.dbf
    35 Full 8165751 20-AUG-10 /export/home/oracleas/oradata_mygst/TBS_MYGST.DBF
    36 Full 8165751 20-AUG-10 /export/home/oracleas/oradata_mykbgst/very_large_data_k b.dbf
    37 Full 8165751 20-AUG-10 /export/home/oracleas/oradata_mykbgst/very_large_indexe s_kb.dbf
    38 Full 8165751 20-AUG-10 /export/home/oracleas/oradata_mykbgst/large_data_kb.dbf
    39 Full 8165751 20-AUG-10 /export/home/oracleas/oradata_mykbgst/large_indexes_kb. dbf
    40 Full 8165751 20-AUG-10 /export/home/oracleas/oradata_mykbgst/medium_data_kb.db f
    41 Full 8165751 20-AUG-10 /export/home/oracleas/oradata_mykbgst/medium_indexes_kb .dbf
    42 Full 8165751 20-AUG-10 /export/home/oracleas/oradata_mykbgst/small_data_kb.dbf
    43 Full 8165751 20-AUG-10 /export/home/oracleas/oradata_mykbgst/small_indexes_kb. dbf
    44 Full 8165751 20-AUG-10 /export/home/oracleas/oradata_mykbgst/TBS_MYKBGST.DBF

  • Rman recovery issue in oracle database 10g

    hi all,
    i have two backups of database one is full and of 3 days previous than sysdate and one is incremental level 1 of sysdate.i have recover database successfully upto 3 days previous and open database with resetlogs but recovering the incremental backup i got the following error
    RMAN> restore database until time "to_date('06/10/09 13:09:00','MM/DD/YY HH24:MI
    *:SS')";*
    *Starting restore at 10-JUN-09*
    *using channel ORA_DISK_1*
    *RMAN-00571: ===========================================================*
    *RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============*
    *RMAN-00571: ===========================================================*
    *RMAN-03002: failure of restore command at 06/10/2009 14:23:13*
    *RMAN-20207: UNTIL TIME or RECOVERY WINDOW is before RESETLOGS time*
    what should i do in this regard to recover upto sysdate with rman

    RMAN> reset database to incarnation 2;
    using target database control file instead of recovery catalog
    database reset to incarnation 2
    RMAN> restore database until time "to_date('06/10/09 01:09:00','MM/DD/YY HH24:MI
    *:SS')";*
    *Starting restore at 11-JUN-09*
    *allocated channel: ORA_DISK_1*
    *channel ORA_DISK_1: sid=155 devtype=DISK*
    *RMAN-00571: ===========================================================*
    *RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============*
    *RMAN-00571: ===========================================================*
    *RMAN-03002: failure of restore command at 06/11/2009 10:28:42*
    *RMAN-06026: some targets not found - aborting 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*
    *RMAN> restore database until time "to_date('06/10/09 13:09:00','MM/DD/YY HH24:MI*
    *:SS')";*
    *Starting restore at 11-JUN-09*
    *using channel ORA_DISK_1*
    *channel ORA_DISK_1: starting datafile backupset restore*
    *channel ORA_DISK_1: specifying datafile(s) to restore from backup set*
    *restoring datafile 00001 to C:\ORACLE\PRODUCT\10.2.0\ORADATA\WINDB\SYSTEM01.DBF*
    *restoring datafile 00002 to C:\ORACLE\PRODUCT\10.2.0\ORADATA\WINDB\UNDOTBS01.DBF*
    *restoring datafile 00003 to C:\ORACLE\PRODUCT\10.2.0\ORADATA\WINDB\SYSAUX01.DBF*
    *restoring datafile 00004 to C:\ORACLE\PRODUCT\10.2.0\ORADATA\WINDB\USERS01.DBF*
    *restoring datafile 00005 to C:\ORACLE\PRODUCT\10.2.0\ORADATA\WINDB\PROJECT1.DBF*
    *restoring datafile 00006 to C:\ORACLE\PRODUCT\10.2.0\ORADATA\WINDB\LIMS1.DBF*
    *restoring datafile 00007 to C:\ORACLE\PRODUCT\10.2.0\ORADATA\WINDB\FMADATA01.DBF*
    *channel ORA_DISK_1: reading from backup piece C:\ORACLE\PRODUCT\10.2.0\FLASH_REC*
    *OVERY_AREA\WINDB\BACKUPSET\2009_06_10\O1_MF_NNND1_TAG20090610T130709_52YTFH6T_.B*
    *KP*
    *channel ORA_DISK_1: restored backup piece 1*
    *piece handle=C:\ORACLE\PRODUCT\10.2.0\FLASH_RECOVERY_AREA\WINDB\BACKUPSET\2009_0*
    *6_10\O1_MF_NNND1_TAG20090610T130709_52YTFH6T_.BKP tag=TAG20090610T130709*
    *channel ORA_DISK_1: restore complete, elapsed time: 00:01:26*
    *Finished restore at 11-JUN-09*
    *RMAN> recover database until time "to_date('06/10/09 13:09:00','MM/DD/YY HH24:MI*
    *:SS')";*
    *Starting recover at 11-JUN-09*
    *using channel ORA_DISK_1*
    *starting media recovery*
    *archive log thread 1 sequence 59 is already on disk as file C:\ORACLE\PRODUCT\10*
    *.2.0\FLASH_RECOVERY_AREA\WINDB\ARCHIVELOG\2009_06_10\O1_MF_1_59_52YVW5X9_.ARC*
    *archive log filename=C:\ORACLE\PRODUCT\10.2.0\FLASH_RECOVERY_AREA\WINDB\ARCHIVEL*
    *OG\2009_06_10\O1_MF_1_59_52YVW5X9_.ARC thread=1 sequence=59*
    *media recovery complete, elapsed time: 00:00:02*
    *Finished recover at 11-JUN-09*
    *RMAN>*
    then after performing the recovery when i tried to open the database
    SQL> alter database open;
    alter database open
    ERROR at line 1:
    ORA-01092: ORACLE instance terminated. Disconnection forced
    i have also tried to open it with resetlogs
    any suggestion to open it now ?

  • Has the recent Itunes upgrade caused incompatibility issue with APPLE TV 1st gen?

    after recent upgrade to itunes, itunes no longer recognizes data on my apple tv 1st gen....but the Apple TV still has them loaded.  additonally this new itunes does not let me resync new songs or movies, etc.  thoughts? thanks!

    I'm having the exact same issue. Nothing in the "Music" menu except "My Music". I Noticed it this afternoon when I woke my Apple TV from standby. The disappearance, in my case, was not related to a reset. My Apple TV has not been reset since the power went out here several weeks ago. Though I obviously don't know for sure, I'm guessing that it's some kind of store problem and we most likely won't be able to correct it from our end.

Maybe you are looking for