Recover database with missing archivelog...

Oracle10gR2 RHEL 4
Hi,
I am having a problem. I'm trying to recover my database to an previous point in time but the archive logs that I need were accidentally removed. Is there anyway I can restore it to a previous point in time? None of the SCN's are working no matter how far I go back (note: I can created the database lastweek so it can't go further than that).
Thanks
RMAN> recover database until time "to_date('2008-04-08:17:47:00','YYYY-MM-DD:HH24:MI:SS')";
Starting recover at 14-APR-08
using channel ORA_DISK_1
starting media recovery
archive log thread 2 sequence 4 is already on disk as file +FLASH1/vmracdev/archivelog/2008_04_08/thread_2_seq_4.290.651538751
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of recover command at 04/14/2008 16:11:11
RMAN-06053: unable to perform media recovery because of missing log
RMAN-06025: no backup of log thread 1 seq 9 lowscn 153309685 found to restore
RMAN> recover database until SCN 153330712;
Starting recover at 14-APR-08
using channel ORA_DISK_1
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of recover command at 04/14/2008 16:12:40
RMAN-06556: datafile 1 must be restored from backup older than scn 153330712
RMAN> recover database until SCN 153266607;
Starting recover at 14-APR-08
using channel ORA_DISK_1
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of recover command at 04/14/2008 16:15:01
RMAN-06556: datafile 1 must be restored from backup older than scn 153266607

Ok, I am trying that but I get the following error:
RMAN> recover database until SCN 153219977;
Starting recover at 17-APR-08
using channel ORA_DISK_1
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of recover command at 04/17/2008 13:33:00
RMAN-06004: ORACLE error from recovery catalog database: RMAN-20208: UNTIL CHANGE is before RESETLOGS change
And this is the latest SCN I have.
Thanks

Similar Messages

  • Recover database with arc-file

    Hi,
    my database was in the archive-log and then we had a dataimport and the database crashed, because there was not enough space.
    So i brought the database now to the mount status and i want to recover my database.
    I take this:
    recover database using BACKUP CONTROLFILE
    and then it proposed me an archive-file but i must take an other one.
    How can i choose the file?
    Thanks in advance.
    Nicole

    And why on Earth are you throwing "using backup controlfile" in there?
    ARE you using a backed up copy of your controlfile? No. You haven't mentioned restoring an old copy of the controlfile at all. So if you haven't restored one from backup, why in Heaven's name are you telling Oracle that the control file is out of date? Because that's what that recovery command does.
    Once you say, "The control file you are using is not to be trusted regarding which logs have been generated because it's an old one I brought back from a backup made some time in the past", then it's no wonder that Oracle has a brain fit and starts proposing that archives be applied which don't actually exist yet. "Using backup controlfile" means "I will tell you when to stop applying redo, because this ancient controlfile can't do that for me reliably".
    It does actually get worse: the fact that your database crashes doesn't inevitably mean you have to recover a thing. Instance crashes are recovered from completely automatically just by restarting the database.
    So you probably didn't need to recover your database at all. You've used the wrong command to recover it even if it did. And by claiming your control file is out of date once, it is quite possible that you really do now need to perform a recovery that was originally completely unnecessary.
    Not bad for a day's work! :-)
    The golden rule of recoveries is: when you're in a hole, stop digging until you've worked out with near-complete certainty why you're in the hole in the first place. Diagnosis is king. Only then do you start planning recoveries.
    The second golden rule of any recovery process, once you've started is: only restore from backup those files which are actually damaged. If your control file isn't lost or damaged, it doesn't need restoring. Same goes for any datafile, too.
    And the third golden rule is: only recover that which you've restored. If you've restored file 4, you don't issue a "recover database" command. And if you haven't restored file 6, don't say 'recover datafile 6'. And if you haven't restored a binary copy of the controlfile made at some time in the past, don't say "using backup controlfile".
    The final, not so much rule as inevitable consequence, is that botched, mistaken, wrong or partial recoveries screw your database up much worse than it was before you did anything. I hope you have a good backup of this database, because you're going to need it.

  • Recover database with datafile and logfile

    Hi Export,
    we have one maxdb database. For some reasons, we have no backup and lost the programs binaries. Is it possble to recover the database with datafile and logfile? and how?
    thanks a lot.
    Rongfeng

    Hello Rongfeng,
    1. Please see document u201CHowTo - Creating a clone of a SAP MaxDB databaseu201D at
    http://wiki.sdn.sap.com/wiki/display/MaxDB/SAPMaxDBHowTo
    and review the section u201CCreating a clone manually via reusing volumes and parameters.u201D
    2. You wrote, that you u201Clost all dba passwords.u201D
    Please review the SAP note 25591. This note also has the brief description of the database user types.
    You are SAP customer, I recommend you to create the SAP message to the component u201CBC-DB-SDBu201D to clarify more details about the problem & find solution for you.
    Thank you and best regards, Natalia Khlopina

  • Archive logs and recovering database with no RMAN

    Hello,
    I inherited a database with no RMAN backup activated but archive redo logs are activated and generating at every moment.
    As there is no rman backup I always thought that those archive redo logs were useless and because of reduced disk space, regularly I delete all of them.
    Then I read that archive redo logs can be usefull even if there is no RMAN. Archive redo logs can be used in a recovery situation like this:
    set all tablespaces in backup mode
    alter tablespace tsp1..tsp100 begin backup;
    copy all datafiles
    alter tablespace tsp1..tsp100 end backup;
    alter database create standby controlfile as 'c:\temp\sbytemp.ctl';
    copy of archivelogs from start begin backup time till nowAs I delete my archive logs, I don't have all ones from the first time. My question is:
    How many archive redo log files would I need to have? Would I need to have all archive logs that were generated from the first time? Or would be enough to have the last three or four ones?
    Thanks
    Edited by: user521219 on 21-may-2012 7:50

    How many archive redo log files would I need to have?
    Would I need to have all archive logs that were generated from the first time?
    would be enough to have the last three or four ones?You need all archive redo log from the moment you have started taking full backup.
    If you take full backup every night at 1:00 AM, you will need all archive redo logs that have transactions finished at and after 1:00 AM.

  • Manual Standby Database not in sync with missing archivelogs

    Hello,
    OS: Solaris
    DB: Oracle 11.2.0.1 EE
    Not Using ASM or RAC
    I have a Production database that is in archivelog mode and a Standby DR server.
    Both servers (Prod, Standby) have exact same structure and db name/version.
    We manually scp archive logs and recover them to a manual standby database via SQL Scripts "cron". (I.E. set autorecovery on; recover standby database;)
    We recently got out of sync with our log files and have not been applying them to the standby. As part of Prod Maintenance, these log files were deleted and are not available anymore.
    I've tried several ways to "rebuild" our standby database. I have tried to Shutdown prod, backup all the db files and scp them to standby, re-create standby controlfile and startup mount and recover standby.
    Every time I try to apply a new archive log via recover standby, these are the errors:
    ORA-00279: change 211077622 generated at 1/27/2012 12:18:42 needed for thread 1
    ORA-00289: suggestion : /oradump/arch/PROD/PROD_arch_1_69486_736618850.arc
    ORA-00280: change 211077622 for thread 1 is in sequence #69486
    ORA-00308: cannot open archived log '/oradump/arch/PROD/PROD_arch_1_69486_736618850.arc'
    ORA-27037: unable to obtain file status
    SVR4 Error: 2: No such file or directory
    Additional information: 3
    ORA-10879: error signaled in parallel recovery slave
    ORA-01547: warning: RECOVER succeeded but OPEN RESETLOGS would get error below
    ORA-01152: file 1 was not restored from a sufficiently old backup
    ORA-01110: data file 1: '/oradevices/PROD/oraPRODsystem1.dbf'
    When I check v$log_history, the new logs have not been applied.
    I've also tried the "Restore from incremental backup via SCN" method with same results.
    Is there a way to re-create the standby clean and ensure that the log chain that is currently broken gets fixed or reset?
    I would eventually like to get DataGuard in here, but that's not the case at the moment.
    Thanks for your suggestions.
    -Dav

    if you are using the cold backup to create the standby database, Check that have you followed the following steps or not.
    1. remove
    all the datafiles and controlfiles from the standby database.
    2. Create a new standby controlfile of the production for standby using the following cmd
    'alter database create standby controlfile as 'Location';'
    3. move the new controlfile to standby database server location as specified in initialization parameter file.
    4. Restore all the datafiles to its appropriate loaction which was taken through cold backup.
    5. startup nomount
    6. alter database mount standby database;
    7. recover standby database.
    scp the archive log sequence that is asked by the database, from production.
    You can try this steps.

  • Recovery with missing archivelog

    I've got a client whose 10gR2 database has been running with the SYSAUX tablespace marked for "recovery" for 9 months. To properly bring SYSAUX online, they need an archivelog from 9 months ago and it no longer exists.
    They think they are in good shape, since they are in archivelog mode and are taking nightly RMAN backups.
    I contend that they are walking on very thin ice: while they can restore from last night's backup, media recovery is impossible and they risk losing up to 24 hours of data.
    Am I correct? Or is there some way to perform an RMAN "recover" operation that by-passes the SYSAUX tablespace, leaving it offline, but brings all the other datafiles up to date?
    I have performed a test using a sample database and my theory is confirmed. But I would like a reality check in case I am missing something.
    Thanks.

    SYSAUX offline and inaccessible for 9 months, really? As you probably already know, there are a ton of objects that exist in this tablespace and therefore, you are probably not able to use some database features.
    As far as recovery, you could use SKIP TABLESPACE to avoid recovery of this tablespace.

  • Recover database with corrupt datafile

    I have an Oracle 9.2.0.6.0 database which has crashed due to disk failure & there is no backup. on the disk that failed there is one rollback datafile so I was hoping to be able to just drop this datafile & the related tablespace & recreate on disk that is OK.
    I found the following instructions in a thread on this forum & managed the offline drop of the datafile & the alter database open. However when I tried to drop the rollback tablespace it couldn't find what I though the tablespace was. Now when I try & do anything with the DB is failed with the error -
    Error 376 happened during db open, shutting down database
    USER: terminating instance due to error 376
    Instance terminated by USER, pid = 47050
    ORA-1092 signalled during: ALTER DATABASE OPEN...
    the instructions I was following were :-
    Database was NOT cleanly shut down
    I.e. Datafile was accidentally dropped using operating system command, when the database was not cleanly shutdown using SHUTDOWN ABORT COMMAND.
    * Check the alert.log file for this instance.
    * Comment out the ROLLBACK_SEGMENTS parameter and add the following line: corruptedrollback_segments = ( ,...., ) i.e., the above list should contain all the rollbacks originally listed in the ROLLBACK_SEGMENTS parameter.
    * Mount the database in restricted mode. STARTUP RESTRICT MOUNT
    * Offline drop the lost datafile.
    ALTER DATABASE DATAFILE OFFLINE DROP;
    * Open the database.
    ALTER DATABASE OPEN.
    * Drop the rollback tablespace to which the datafile belonged.
    * Recreate the rollback tablespace with all its rollback segments. Remember to bring the rollbacks online after you create them.
    * Make the database available to all users.
    * ALTER SYSTEM DISABLE RESTRICTED SESSION;
    You should be able to see your database back at this step.
    Any ideas how to indentify the tablespace that I need to drop & how to get the database into a state that will let me attempt this?

    latest entries in alert.log ...
    Mon Jan 18 15:32:33 2010
    Errors in file /dwdb1/u01/oracle/app/oracle/admin/PLYDW/bdump/plydw_smon_33822.t
    rc:
    ORA-01595: error freeing extent (2) of rollback segment (13))
    ORA-00376: file 6 cannot be read at this time
    ORA-01110: data file 6: '/dip3/u07/oradata/PLYDW/dwrbs01.dbf'
    SMON: about to recover undo segment 2
    SMON: mark undo segment 2 as needs recovery
    SMON: about to recover undo segment 3
    SMON: mark undo segment 3 as needs recovery
    SMON: about to recover undo segment 4
    SMON: mark undo segment 4 as needs recovery
    SMON: about to recover undo segment 5
    SMON: mark undo segment 5 as needs recovery
    SMON: about to recover undo segment 6
    SMON: mark undo segment 6 as needs recovery
    SMON: about to recover undo segment 7
    SMON: mark undo segment 7 as needs recovery
    SMON: about to recover undo segment 8
    SMON: mark undo segment 8 as needs recovery
    SMON: about to recover undo segment 9
    SMON: mark undo segment 9 as needs recovery
    SMON: about to recover undo segment 10
    SMON: mark undo segment 10 as needs recovery
    SMON: about to recover undo segment 11
    SMON: mark undo segment 11 as needs recovery
    Mon Jan 18 15:32:46 2010
    Errors in file /dwdb1/u01/oracle/app/oracle/admin/PLYDW/udump/plydw_ora_52948.tr
    c:
    ORA-00376: file 6 cannot be read at this time
    ORA-01110: data file 6: '/dip3/u07/oradata/PLYDW/dwrbs01.dbf'
    Mon Jan 18 15:32:46 2010
    Error 376 happened during db open, shutting down database
    USER: terminating instance due to error 376
    Instance terminated by USER, pid = 52948
    ORA-1092 signalled during: alter database open...

  • Recover database with control and dbf files

    Dear all,
    How to recover a database whose registery was damaged but it's control and dbf files are still there
    Notes there is no dmp files to recover after reinstalling the oracle

    Hi,
    How to recover a database whose registery was damaged but it's control and dbf files
    are still thereWhat do you mean by "registry" damaged? Do you mean Windows Registry?
    If you have control files, data files, and online redo log files then you can simply reinstall Oracle Software, create a windows instance (assuming its on Windows) and start the database without any loss.
    Regards

  • How to recover a database with archive log

    how to recover database with archivle log

    Hi,
    With in information no one can tell the answer.
    Kindly post your qusetion in details information, you want to recover the database in archive log mode, what type of error you get, bcoz depending up on the errors you recover your database,
    please mention all about your database
    cheers
    Senthil Kumar

  • Recover database to new server problem

    Hi all,
    I'm running a production 10.2.0.4 DB in archivelog mode on Solaris 10.8. I used RMAN with a recovery catalog to execute the stored script:
    run{sql 'alter system archive log current';
    backup incremental level 0
    database archivelog all delete input;}
    I copied the rman files and spfile to a test server with the same directory structres. No Problem.
    Using "rman target /" I started the database in nomount and restored the controlfile from backup and mounted the database. No Problem.
    Still within the RMAN session, I restored the 1TB worth of datafiles. The restore completed, no problem.
    I then issued the command, "recover database;" PROBLEM, RMAN said datafile1 "System.dbf" needs more recovery to be in a consistent state.
    WHY? I issued the commands, "alter system archive log current;" and "archivelog all delete input" in my script.
    Why does it need the next archivelog to be consistent?
    I was under the impression that all I need to recover a database with rman was the output files from RMAN.
    I copied the next archivelog over and in SQLPLUS as SYS I issued the command, " recover database using backup controlfile until cancel;"
    I canceled the recovery when it asked for the next archivelog and opened database reset logs.
    If I didn't have access to the next archive log how would I solve this problem?

    Your BACKUP should be executed as BACKUP DATABASE PLUS ARCHIVELOG. The "PLUS ARCHIVELOG" causes Oracle to issue an ALTER SYSTEM SWITCH LOGFILE at the end of the database backup so that the ArchiveLog generated gets picked up by the subsequent Backup of the ArchiveLog as well.
    Your first RECOVER DATABASE command was attempting a Complete recovery. Had you specified an UNTIL clause, Oracle would know that you wanted an Incomplete recovery upto the last available archivelog. Your second RECOVER DATABASE with the UNTIL CANCEL was an Incomplete Recovery.
    Hemant K Chitale

  • Rman backup with a missing archivelog.

    hello,
    I backed my database up yesterday after you guys helped me fix few problems I had on it. I used RMAN with the following command in a run block:
    *run {*
    allocate channel t1 type disk;
    backup current controlfile ;
    backup database;
    backup archivelog all delete input;
    release channel c1;
    At the end of the operation, RMAN indicates that and archivelog is missing and it couldn't find it. As a result, recover operation can be compromised. Now am confused because I do not know whether the command executed successfully or not and how to fix the missing archivelog.
    Below is the entire output of the operation along with error message:
    canal affectÚ : t1
    canal t1 : sid=131 typedev=DISK
    DÚmarrage de backup dans 16/04/09
    canal t1 : dÚmarrage de l'ensemble de sauvegarde de tous les fichiers de donnÚes
    canal t1 : insertion du fichier de donnÚes dans l'ensemble de sauvegarde
    insertion du fichier de contr¶le en cours dans l'ensemble de sauvegarde
    canal t1 : dÚmarrage de l'ÚlÚment 1 dans 16/04/09
    canal t1 : ÚlÚment 1 terminÚ dans 16/04/09
    pointeur=+ASMTEST/meta4/backupset/2009_04_16/ncnnf0_tag20090416t211049_0.334.684
    *364257 Útiquette=TAG20090416T211049 commentaire=NONE*
    canal t1 : ensemble de sauvegarde terminÚ, temps ÚcoulÚ : 00:00:14
    Fin de backup dans 16/04/09
    DÚmarrage de backup dans 16/04/09
    canal t1 : dÚmarrage de l'ensemble de sauvegarde de tous les fichiers de donnÚes
    canal t1 : insertion du fichier de donnÚes dans l'ensemble de sauvegarde
    fichier de donnÚes en entrÚe fno=00008 nom=+ASMTEST/meta4/m4prod.dbf
    fichier de donnÚes en entrÚe fno=00010 nom=H:\ORADATA\M4REC.DBF
    fichier de donnÚes en entrÚe fno=00009 nom=E:\DATAFILEMETA4\M4PROD02.DBF
    fichier de donnÚes en entrÚe fno=00001 nom=+ASMTEST/meta4/system01.dbf
    fichier de donnÚes en entrÚe fno=00003 nom=+ASMTEST/meta4/sysaux01.dbf
    fichier de donnÚes en entrÚe fno=00006 nom=C:\TEST.DBF
    fichier de donnÚes en entrÚe fno=00007 nom=+ASMTEST/meta4/meta4.dbf
    fichier de donnÚes en entrÚe fno=00005 nom=+ASMTEST/meta4/example01.dbf
    fichier de donnÚes en entrÚe fno=00002 nom=+ASMTEST/meta4/undotbs01.dbf
    fichier de donnÚes en entrÚe fno=00004 nom=+ASMTEST/meta4/users01.dbf
    canal t1 : dÚmarrage de l'ÚlÚment 1 dans 16/04/09
    canal t1 : ÚlÚment 1 terminÚ dans 16/04/09
    pointeur=+ASMTEST/meta4/backupset/2009_04_16/nnndf0_tag20090416t211107_0.333.684
    *364271 Útiquette=TAG20090416T211107 commentaire=NONE*
    canal t1 : ensemble de sauvegarde terminÚ, temps ÚcoulÚ : 00:51:10
    canal t1 : dÚmarrage de l'ensemble de sauvegarde de tous les fichiers de donnÚes
    canal t1 : insertion du fichier de donnÚes dans l'ensemble de sauvegarde
    insertion du fichier de contr¶le en cours dans l'ensemble de sauvegarde
    inclusion du SPFILE en cours dans l'ensemble de sauvegarde
    canal t1 : dÚmarrage de l'ÚlÚment 1 dans 16/04/09
    canal t1 : ÚlÚment 1 terminÚ dans 16/04/09
    pointeur=+ASMTEST/meta4/backupset/2009_04_16/ncsnf0_tag20090416t211107_0.345.684
    *367351 Útiquette=TAG20090416T211107 commentaire=NONE*
    canal t1 : ensemble de sauvegarde terminÚ, temps ÚcoulÚ : 00:00:26
    Fin de backup dans 16/04/09
    DÚmarrage de backup dans 16/04/09
    journal en cours archivÚ
    canal libÚrÚ : t1
    RMAN-00571: ===========================================================
    RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
    RMAN-00571: ===========================================================
    RMAN-03002: Úchec de la commande backup Ó 04/16/2009 22:04:03
    RMAN-06059: journal d'archivage attendu introuvable ; la perte du journal d'arch
    ivage compromet la possibilitÚ de rÚcupÚration
    ORA-19625: erreur lors de l'identification du fichier H:\ARCHIVEMETA4\ARC00001_0
    *682674928.001*
    ORA-27041: ouverture du fichier impossible
    OSD-04002: ouverture impossible du fichier
    O/S-Error: (OS 2) Le fichier spÚcifiÚ est introuvable.
    Here's my nderstanding and please correct me if am wrong:
    The first 3 instructions of the run block executed successfully, but
    the last one didn't. Is that so?
    Whatever the understanding, do I have a backup? WHat can I do to have a consistent backup?
    Thanks in advance.

    Adomi,
    It is sad to see you are still running RMAN in 8i fashion where you are on 10g.
    The script is bs, sorry
    run {
    allocate channel t1 type disk; -- not required
    backup current controlfile ; -- not required, as this is already done by backup database
    backup database;
    backup archivelog all delete input;
    release channel c1; -- not required.
    If you have controlfile autobackup on, you could just
    backup database plus archivelog
    and be done with it.
    As you didn't make a RMAN backup from the start, your backup archivelog statement should have read
    backup archivelog all skip inaccessible delete input;
    Once that succeeds Oracle shouldn't need the archivelog anymore, and you should make a second backup without the skip inaccessible clause.
    Sybrand Bakker
    Senior Oracle DBA

  • Recover database until cancel using backup controlfile Fails with ORA-01547

    Hi
    First of all, I'm sorry for posting in this community as my issue doesn't have any thing to do with Rman, but I couldn't find any more relative Community to post in
    our System is Oracle EBS 11i and the OS on the production is AIX 5.2 / and the DR is 5.3 / DB version is 9i
    we have our Oracle ERP scheduled using crontab to take a database COLD backup daily using gtar -cvzf .
    yesterday I needed to clone the database only, so I used my usual method witch is
    1) on the source SQL> alter database backup controlfile to trace as '<dest>/makecntrlfil.sql'
    then you can delete the Commented header and change the first command from
    "CREATE CONTROLFILE REUSE DATABASE <SOURCE> NORESETLOGS ..."
    TO
    CREATE CONTROLFILE SET DATABASE <TARGET> RESETLOGS <NO>ARCHIVELOG
    2) de-compress the tgz files
    3) on the target edit the $ORACLE_HOME/dbs/init<source>.ora, $ORACLE_HOME/environment file
    4)run /ORACLE_HOME/appsutils/clone/bin/adcfgclone.prl
    5) delete old controlfiles
    6) on the database run the script you created on firs t step to create a new control fole
    7)recover database until cancel using backup controlfile
    8) alter database open resetlogs
    add new temp file system
    this way I used to do it
    but yesterday when trying to execute recover database it didn't work, and gave this error
    ORA-00279: change 6450277404 generated at 02/28/2013 02:47:56 needed for thread
    1
    ORA-00289: suggestion : /ERPDEV/DBASE/devdb/9.2.0/dbs/arch1_188462.dbf
    ORA-00280: change 6450277404 for thread 1 is in sequence #188462
    Specify log: {<RET>=suggested | filename | AUTO | CANCEL} >> I gave cancel >> so >>
    ORA-01547: warning: RECOVER succeeded but OPEN RESETLOGS would get error below
    ORA-01152: file 1 was not restored from a sufficiently old backup
    ORA-01110: data file 1: '/ERPDEV/DBASE/SYS/devdata/system01.dbf'
    nothing strange in the original alert log file in the time of taking the backup
    So can You please tell me what maybe wrong and why it used to work before and now it's not
    take in consideration that we are on archive log mode, but not using Rman or the archived Logs for backup and the sequence it needed ( 188462 ) is too old and already deleted on Production.

    the output of the sript
    Please Do not Forgot to run /usr/bin/runmwm as root Please Do not Forgot to run /usr/bin/runmwm as root Please Do not Forgot to run /usr/bin/runmwm as root Please Do not Forgot to run /usr/bin/runmwm as root ConcMgr will not work ConcMgr will not work ConcMgr will not work #####################################################
    172.16.10.10:1.0
    access control disabled, clients can connect from any host
    You are running adstpall.sh version 115.19
    Executing service control script:
    /ERPABP/APPL/abpcomn/admin/scripts/ABP_babtain-erp/adapcctl.sh stop script returned:
    adapcctl.sh version 115.54
    Apache Web Server Listener :httpd ( pid 765998 ) is running.
    Stopping Apache Web Server Listener (dedicated HTTP) ...
    Apache Web Server Listener (PLSQL) :httpd ( pid 2830390 ) is running.
    Stopping Apache Web Server Listener (dedicated PLSQL) ...
    adapcctl.sh: exiting with status 0
    .end std out.
    .end err out.
    Executing service control script:
    /ERPABP/APPL/abpcomn/admin/scripts/ABP_babtain-erp/adalnctl.sh stop script returned:
    adalnctl.sh version
    Shutting down listener process APPS_ABP.
    adalnctl.sh: exiting with status 0
    .end std out.
    .end err out.
    Executing service control script:
    /ERPABP/APPL/abpcomn/admin/scripts/ABP_babtain-erp/adtcfctl.sh stop script returned:
    You are running adtcfctl.sh version 115.14
    Shutting down TCF SocketServer for ABP on port -1.
    adtcfctl.sh: exiting with status 0
    .end std out.
    .end err out.
    Executing service control script:
    /ERPABP/APPL/abpcomn/admin/scripts/ABP_babtain-erp/adcmctl.sh stop script returned:
    You are running adcmctl.sh version 115.28
    Shutting down concurrent managers for ABP ...
    Submitted request 7481224 for CONCURRENT FND SHUTDOWN
    adcmctl.sh: exiting with status 0
    .end std out.
    .end err out.
    Executing service control script:
    /ERPABP/APPL/abpcomn/admin/scripts/ABP_babtain-erp/adfrmctl.sh stop script returned:
    You are running adfrmctl.sh version 115.37
    Stopping forms server for ABP on port 9003.
    adfrmctl.sh: exiting with status 0
    .end std out.
    .end err out.
    Executing service control script:
    /ERPABP/APPL/abpcomn/admin/scripts/ABP_babtain-erp/adrepctl.sh stop script returned:
    You are running adrepctl.sh version 115.32
    stopping Reports Server for ABP on port 7003.
    kill -9 827420
    Reports Server for ABP successfully stopped.
    adrepctl.sh: exiting with status 0
    .end std out.
    .end err out.
    Executing service control script:
    /ERPABP/APPL/abpcomn/admin/scripts/ABP_babtain-erp/adfmcctl.sh stop script returned:
    You are running adfmcctl.sh version 115.19
    Stopping forms load balancing client for ABP.
    adfmcctl.sh: exiting with status 0
    .end std out.
    .end err out.
    Executing service control script:
    /ERPABP/APPL/abpcomn/admin/scripts/ABP_babtain-erp/adfmsctl.sh stop script returned:
    You are running adfmsctl.sh version 115.15
    Stopping forms metrics server for ABP on port 9203.
    adfmsctl.sh: exiting with status 0
    .end std out.
    .end err out.
    Executing service control script:
    /ERPABP/APPL/abpcomn/admin/scripts/ABP_babtain-erp/jtffmctl.sh stop script returned:
    You are running jtffmctl.sh version 115.16
    Shutting down Fulfillment Server for ABP on port 9303 ...
    jtffmctl.sh: exiting with status 0
    .end std out.
    .end err out.
    All enabled services on this node are stopped.
    Check logfile /ERPABP/APPL/abpcomn/admin/log/ABP_babtain-erp/04010130.log for details
    Exiting with status 0
    You are running addlnctl.sh version 115.7
    Logfile: /ERPABP/DBASE/abpdb/9.2.0/appsutil/log/ABP_babtain-erp/addlnctl.txt
    Shutting down listener process ABP ...
    addlnctl.sh: exiting with status 0
    You are running addbctl.sh version 115.10
    Shutting down database ABP ...
    SQL*Plus: Release 9.2.0.8.0 - Production on Mon Apr 1 01:36:25 2013
    Copyright (c) 1982, 2002, Oracle Corporation. All rights reserved.
    Connected.
    Database closed.
    Database dismounted.
    ORACLE instance shut down.
    Disconnected from Oracle9i Enterprise Edition Release 9.2.0.8.0 - 64bit Production With the Partitioning, OLAP and Oracle Data Mining options JServer Release 9.2.0.8.0 - Production
    addbctl.sh: exiting with status 0
    You are running addbctl.sh version 115.10
    Starting the database ABP ...
    SQL*Plus: Release 9.2.0.8.0 - Production on Mon Apr 1 01:38:48 2013
    Copyright (c) 1982, 2002, Oracle Corporation. All rights reserved.
    Connected to an idle instance.
    ORACLE instance started.
    Total System Global Area 6829474752 bytes
    Fixed Size          742336 bytes
    Variable Size          1493172224 bytes
    Database Buffers     5324800000 bytes
    Redo Buffers          10760192 bytes
    Database mounted.
    Database opened.
    Disconnected from Oracle9i Enterprise Edition Release 9.2.0.8.0 - 64bit Production With the Partitioning, OLAP and Oracle Data Mining options JServer Release 9.2.0.8.0 - Production
    addbctl.sh: exiting with status 0
    You are running addbctl.sh version 115.10
    Shutting down database ABP ...
    SQL*Plus: Release 9.2.0.8.0 - Production on Mon Apr 1 01:39:08 2013
    Copyright (c) 1982, 2002, Oracle Corporation. All rights reserved.
    Connected.
    Database closed.
    Database dismounted.
    ORACLE instance shut down.
    Disconnected from Oracle9i Enterprise Edition Release 9.2.0.8.0 - 64bit Production With the Partitioning, OLAP and Oracle Data Mining options JServer Release 9.2.0.8.0 - Production
    addbctl.sh: exiting with status 0
    root 2883784 2097278 0 01:39:54 - 0:00 grep abpappl
    root 1425530 2097278 1 01:39:54 - 0:00 grep abpora
    Taring /ERPABP/DBASE/SYS/abpdata
    Mon Apr 1 01:39:54 SAUST 2013
    Mon Apr 1 03:00:16 SAUST 2013
    Taring /ERPDEV/DBASE/SYS/abpdata
    Mon Apr 1 03:00:16 SAUST 2013
    Mon Apr 1 03:10:18 SAUST 2013
    Taring /ERPABP/DBASE/DATA/abpdata
    Mon Apr 1 03:10:18 SAUST 2013
    Mon Apr 1 04:51:04 SAUST 2013
    Taring /ERPDEV/APPL/DATA/abpdata
    Mon Apr 1 04:51:04 SAUST 2013
    Mon Apr 1 05:02:58 SAUST 2013
    You are running addbctl.sh version 115.10
    Starting the database ABP ...
    SQL*Plus: Release 9.2.0.8.0 - Production on Mon Apr 1 05:04:46 2013
    Copyright (c) 1982, 2002, Oracle Corporation. All rights reserved.
    Connected to an idle instance.
    ORACLE instance started.
    Total System Global Area 6829474752 bytes
    Fixed Size          742336 bytes
    Variable Size          1493172224 bytes
    Database Buffers     5324800000 bytes
    Redo Buffers          10760192 bytes
    Database mounted.
    Database opened.
    Disconnected from Oracle9i Enterprise Edition Release 9.2.0.8.0 - 64bit Production With the Partitioning, OLAP and Oracle Data Mining options JServer Release 9.2.0.8.0 - Production
    addbctl.sh: exiting with status 0
    You are running addlnctl.sh version 115.7
    Logfile: /ERPABP/DBASE/abpdb/9.2.0/appsutil/log/ABP_babtain-erp/addlnctl.txt
    Starting listener process ABP ...
    addlnctl.sh: exiting with status 0
    Please Do not Forgot to run /usr/bin/runmwm as root Please Do not Forgot to run /usr/bin/runmwm as root Please Do not Forgot to run /usr/bin/runmwm as root Please Do not Forgot to run /usr/bin/runmwm as root ConcMgr will not work ConcMgr will not work ConcMgr will not work #####################################################
    172.16.10.10:1.0
    access control disabled, clients can connect from any host
    You are running adstrtal.sh version 115.16
    Executing service control script:
    /ERPABP/APPL/abpcomn/admin/scripts/ABP_babtain-erp/adapcctl.sh start script returned:
    adapcctl.sh version 115.54
    Apache Web Server Listener is not running.
    Starting Apache Web Server Listener (dedicated HTTP) ...
    Apache Web Server Listener (PLSQL) is not running.
    Starting Apache Web Server Listener (dedicated PLSQL) ...
    adapcctl.sh: exiting with status 0
    .end std out.
    .end err out.
    Executing service control script:
    /ERPABP/APPL/abpcomn/admin/scripts/ABP_babtain-erp/adalnctl.sh start script returned:
    adalnctl.sh version
    Checking for FNDFS executable.
    Starting listener process APPS_ABP.
    adalnctl.sh: exiting with status 0
    .end std out.
    .end err out.
    Executing service control script:
    /ERPABP/APPL/abpcomn/admin/scripts/ABP_babtain-erp/adtcfctl.sh start script returned:
    You are running adtcfctl.sh version 115.14
    TCF SocketServer for ABP on port -1 is already started.
    adtcfctl.sh: exiting with status 2
    .end std out.
    .end err out.
    Executing service control script:
    /ERPABP/APPL/abpcomn/admin/scripts/ABP_babtain-erp/adcmctl.sh start script returned:
    You are running adcmctl.sh version 115.28
    Starting concurrent manager for ABP ...
    Starting ABP_0401@ABP Internal Concurrent Manager Default printer is noprint
    adcmctl.sh: exiting with status 0
    .end std out.
    .end err out.
    Executing service control script:
    /ERPABP/APPL/abpcomn/admin/scripts/ABP_babtain-erp/adfrmctl.sh start script returned:
    You are running adfrmctl.sh version 115.37
    Starting forms server for ABP on port 9003.
    adfrmctl.sh: exiting with status 0
    .end std out.
    .end err out.
    Executing service control script:
    /ERPABP/APPL/abpcomn/admin/scripts/ABP_babtain-erp/adrepctl.sh start script returned:
    You are running adrepctl.sh version 115.32
    starting Reports Server for ABP on port 7003.
    adrepctl.sh: exiting with status 0
    .end std out.
    .end err out.
    Executing service control script:
    /ERPABP/APPL/abpcomn/admin/scripts/ABP_babtain-erp/adfmcctl.sh start script returned:
    You are running adfmcctl.sh version 115.19
    Starting forms load balancing client for ABP.
    adfmcctl.sh: exiting with status 0
    .end std out.
    .end err out.
    Executing service control script:
    /ERPABP/APPL/abpcomn/admin/scripts/ABP_babtain-erp/adfmsctl.sh start script returned:
    You are running adfmsctl.sh version 115.15
    starting forms metrics server for ABP.
    adfmsctl.sh: exiting with status 0
    .end std out.
    .end err out.
    Executing service control script:
    /ERPABP/APPL/abpcomn/admin/scripts/ABP_babtain-erp/jtffmctl.sh start script returned:
    You are running jtffmctl.sh version 115.16
    Validating Fulfillment patch level via /ERPABP/APPL/abpcomn/java Fulfillment patch level validated.
    Starting Fulfillment Server for ABP on port 9303 ...
    jtffmctl.sh: exiting with status 0
    .end std out.
    .end err out.
    All enabled services for this node are started.
    Check logfile /ERPABP/APPL/abpcomn/admin/log/ABP_babtain-erp/04010505.log for details
    Exiting with status 0
    MWA Telnet Server Release: 1.0.8.4 [December 12th 2002] Mon Apr 1 05:06:01 SAUST 2013
    9653.50     /store/abp/data/data_abpdata_010413.tgz
    1089.50     /store/abp/data/datadev_abpdata_010413.tgz
    0.04     /store/abp/data/mkctrl.sql
    13309.38     /store/abp/data/sys_abpdata_010413.tgz
    1000.25     /store/abp/data/sysdev_abpdata_010413.tgz
    Mon Apr 1 05:06:01 SAUST 2013
    #######################################################################################################################

  • RMAN-06067: RECOVER DATABASE required with a backup or created controlfile

    Hi,
    DB:9.2.0.8
    OS: AIX 5.3
    I am restoring DB with until time(12/06/2012) for needed tablespaces.
    I restored the 12th date controlfile ,which is backed up with archivedlogs. I also have one more controlfile which backed up with full DB..
    Restore of tablespaces are completed..
    When recovery is going , failed with following error..
    allocated channel: c7
    channel c7: sid=22 devtype=SBT_TAPE
    channel c7: VERITAS NetBackup for Oracle - Release 5.1 (2006040520)
    allocated channel: c8
    channel c8: sid=21 devtype=SBT_TAPE
    channel c8: VERITAS NetBackup for Oracle - Release 5.1 (2006040520)
    executing command: SET until clause
    Starting recover at 23-06-2012 02:00:15
    released channel: c1
    released channel: c2
    released channel: c3
    released channel: c4
    released channel: c5
    released channel: c6
    released channel: c7
    released channel: c8
    RMAN-00571: ===========================================================
    RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
    RMAN-00571: ===========================================================
    RMAN-03002: failure of recover command at 06/23/2012 03:36:57
    RMAN-06067: RECOVER DATABASE required with a backup or created controlfile
    RMAN>
    Restore Script:
    connect target /
    connect catalog rmanc/recom@lgn_rmanc
    run {
    allocate channel c1 type 'SBT_TAPE';
    allocate channel c2 type 'SBT_TAPE';
    allocate channel c3 type 'SBT_TAPE';
    allocate channel c4 type 'SBT_TAPE';
    allocate channel c5 type 'SBT_TAPE';
    allocate channel c6 type 'SBT_TAPE';
    allocate channel c7 type 'SBT_TAPE';
    allocate channel c8 type 'SBT_TAPE';
    allocate channel c9 type 'SBT_TAPE';
    allocate channel c10 type 'SBT_TAPE';
    allocate channel c11 type 'SBT_TAPE';
    allocate channel c12 type 'SBT_TAPE';
    set until time '12-06-2012 00:01:26';
    restore tablespace SYSTEM,UNDO_GEN01,UNDO_GEN02,TAB_80K_GENCON,TAB_25M_GENCON;
    release channel c1;
    release channel c2;
    release channel c3;
    release channel c4;
    release channel c5;
    release channel c6;
    release channel c7;
    release channel c8;
    release channel c9;
    release channel c10;
    release channel c11;
    release channel c12;
    Recover Script:
    connect catalog rmanc/recom@lgn_rmanc
    connect target /
    run {
    allocate channel c1 type 'SBT_TAPE';
    allocate channel c2 type 'SBT_TAPE';
    allocate channel c3 type 'SBT_TAPE';
    allocate channel c4 type 'SBT_TAPE';
    allocate channel c5 type 'SBT_TAPE';
    allocate channel c6 type 'SBT_TAPE';
    allocate channel c7 type 'SBT_TAPE';
    allocate channel c8 type 'SBT_TAPE';
    set until time '12-06-2012 00:01:26';
    recover tablespace SYSTEM,UNDO_GEN01,UNDO_GEN02,TAB_80K_GENCON,TAB_25M_GENCON;
    release channel c1;
    release channel c2;
    release channel c3;
    release channel c4;
    release channel c5;
    release channel c6;
    release channel c7;
    release channel c8;
    Any suggestion in this is helpful to me..
    Thanks in advance,

    Hello;
    I read your post and here's the thoughts that came to mind : ( my largest concern is you might restore something that damages your current system )
    1. So you want to restore the whole DB back to 12/06/2012 to get some tablespaces from then right?
    2. Are you restoring to a different system?
    3. How did you start the database ( NOMOUNT, MOUNT )
    4. If you are restoring the whole DB back to 12/06/2012 how did you restore the control file?
    5. Your command shows :
    restore tablespace SYSTEM,UNDO_GEN01,UNDO_GEN02,TAB_80K_GENCON,TAB_25M_GENCON;
    COMMENT : Generally I use recover tablespace for point in time recovery and use an auxilary destination.
    Meaning I don't use restore at all, in fact using restore may cause an issue.
    SUMMARY : I don't see how this will work as is.
    It seems you want data from five tablespaces from about six months ago including the SYSTEM tablespace.
    This is an Incomplete Recovery. I believe I would rethink this completely.
    Give the time that has past I would consider restoring the whole database to a different server where cannot damage anything.
    Once this is done I would decide how to get the data I need.
    Or I would check for a daily export file and recover the tablespace data that way.
    So you have some good details on your question but it seems the plan is either missing something or you need to add a few more details.
    Example
    I'm recovering old tablespaces into a test system.
    Here's how I'm not damaging my current production system.
    I don't have an export from that date.
    So take a step back and either rethink or give a few more details on how this is safe.
    Best Regards
    mseberg

  • Recover database from cold backup and add ol archivelogs....

    Hello!
    Scenarion : I have create in 1 january cold backup of my database. I have from 1 to 4 January all archive logs generated by my database. My database gone in 4 January.
    Solution question : How can i restore database using cold backup a than add info from archivelogs to recovered database to do database consist from disaster day.
    Regards... Marcin

    1. Kill current instance with SHUTDOWN ABORT.
    2. Copy all control files and data files from your cold backup to original destination.
    3. Make sure all archived redo logs from 01-JAN to 04-JAN are available in the database archive destination (LOG_ARCHIVE_DEST or LOG_ARCHIVE_DEST_x).
    4. Run as SYSDBA:
    startup mount
    recover database using backup controlfile until cancel;When prompted for something like
    ORA-00279: change 864868 generated at 01/14/2010 09:30:10 needed for thread 1
    ORA-00289: suggestion :
    C:\ORACLEXE\APP\ORACLE\FLASH_RECOVERY_AREA\XE\ARCHIVELOG\2010_01_15\O1_MF_1_22_%
    U_.ARC
    ORA-00280: change 864868 for thread 1 is in sequence #22enter:
    AUTOWhen you get something like:
    ORA-00308: cannot open archived log
    'C:\ORACLEXE\APP\ORACLE\FLASH_RECOVERY_AREA\XE\ARCHIVELOG\2010_01_15\O1_MF_1_29_
    %U_.ARC'
    ORA-27041: unable to open file
    OSD-04002: ouverture impossible du fichier
    O/S-Error: (OS 2) Le fichier spécifié est introuvable.run
    alter database open resetlogs;

  • Recover controlfile with database in NOMOUNT state

    Hi,
    I'm doing some tests, destroying my test envinroment. At this time i was trying to recover a "missing" controlfile both via RMAN and ALTER DATABASE command, but they all have failed because i cannot mount my database and as my researches show, i am only able to recover a controlfile if my instance is in MOUNT, but i cannot mount it because of the missing controlfile. I saw that via RMAN, i can recover the controlfile from a backup if i use static service registration. This is the only manner?
    Thanks for your attention
    Version: 10.2.0.4
    OS: Win 2003

    Fabricio_Jorge wrote:
    Hi,
    I'm doing some tests, destroying my test envinroment. At this time i was trying to recover a "missing" controlfile both via RMAN and ALTER DATABASE command, but they all have failed because i cannot mount my database and as my researches show, i am only able to recover a controlfile if my instance is in MOUNT, but i cannot mount it because of the missing controlfile. I saw that via RMAN, i can recover the controlfile from a backup if i use static service registration. This is the only manner?
    Thanks for your attention
    Version: 10.2.0.4
    OS: Win 2003I make new CONTROLFILE from SQL below
    bcm@bcm-laptop:~$ cat restart.sql
    STARTUP NOMOUNT
    CREATE CONTROLFILE REUSE DATABASE "V112" NORESETLOGS  NOARCHIVELOG
        MAXLOGFILES 16
        MAXLOGMEMBERS 3
        MAXDATAFILES 100
        MAXINSTANCES 8
        MAXLOGHISTORY 1168
    LOGFILE
      GROUP 1 '/u01/app/oracle/oradata/v112/redo01.log'  SIZE 50M BLOCKSIZE 512,
      GROUP 2 '/u01/app/oracle/oradata/v112/redo02.log'  SIZE 50M BLOCKSIZE 512,
      GROUP 3 '/u01/app/oracle/oradata/v112/redo03.log'  SIZE 50M BLOCKSIZE 512
    -- STANDBY LOGFILE
    DATAFILE
      '/u01/app/oracle/oradata/v112/system01.dbf',
      '/u01/app/oracle/oradata/v112/sysaux01.dbf',
      '/u01/app/oracle/oradata/v112/undotbs01.dbf',
      '/u01/app/oracle/oradata/v112/users01.dbf',
      '/u01/app/oracle/oradata/v112/example01.dbf'
    CHARACTER SET AL32UTF8
    -- Commands to re-create incarnation table
    -- Below log names MUST be changed to existing filenames on
    -- disk. Any one log file from each branch can be used to
    -- re-create incarnation records.
    -- ALTER DATABASE REGISTER LOGFILE '/u01/app/oracle/flash_recovery_area/V112/archivelog/2011_10_20/o1_mf_1_1_%u_.arc';
    -- ALTER DATABASE REGISTER LOGFILE '/u01/app/oracle/flash_recovery_area/V112/archivelog/2011_10_20/o1_mf_1_1_%u_.arc';
    -- Recovery is required if any of the datafiles are restored backups,
    -- or if the last shutdown was not normal or immediate.
    RECOVER DATABASE
    -- Set Database Guard and/or Supplemental Logging
    ALTER DATABASE ADD SUPPLEMENTAL LOG DATA;
    -- Database can now be opened normally.
    ALTER DATABASE OPEN;
    -- Commands to add tempfiles to temporary tablespaces.
    -- Online tempfiles have complete space information.
    -- Other tempfiles may require adjustment.
    ALTER TABLESPACE TEMP ADD TEMPFILE '/u01/app/oracle/oradata/v112/temp01.dbf'
         SIZE 39845888  REUSE AUTOEXTEND ON NEXT 655360  MAXSIZE 32767M;
    -- End of tempfile additions.
    bcm@bcm-laptop:~$

Maybe you are looking for