Oracle doubt...backup/recovery

Hi all,
1.Can anyone help me understand the significance of checkpoint_change# parameter in v$datafile,v$datafile_header and v$database in the context of recovery? And various situations explaining their values?
2.If anyone give me some link for practising some test cases on this I will be grateful and hope by doing the concept will be clear.
2.When do we fire "recover database using backup controlfile until cancel"?
Regards,
Saikat

v$database---checkpoint_change#,current_scn
checkpoint_change# is the scn number written to control file during checkppoint and current_scn is the SCN in the database at the current time.
current_scn will be ahead of checkpoint_change# as the background process do the work continuously and gets incremented. Once checkpoint occurs
both checkpoint_change#=current_scn
V$DATAFILE --checkpoint_change#  is the last SCN   recorded for each datafile when last checkpoint occured.
V$DATAFILE_HEADER---This view displays datafile information from the datafile headers.
When your db is in open mode, checkpoint_change# form v$database,v$datafile,v$datafile_header are same.
sql> select name, CHECKPOINT_CHANGE# dbcheckpoint,current_scn dbcurrscn,a.*,b.* from (select checkpoint_change# datafilechkpt, count(*) from v$datafile group by checkpoint_change#) a, (select checkpoint_change# datafilehdrckpt, count(*) from v$datafile_header group by checkpoint_change#) b,v$database;
NAME DBCHECKPOINT DBCURRSCN DATAFILECHKPT COUNT(*) DATAFILEHDRCKPT COUNT(*)
REPO 232905378354 232905387977 232905378354 5 232905378354 5
From mount to open mode of database, if checkpoint_change# in v$datafile_header and v$database does not match your database does not come to OPEN mode.
2) When you loose your current controlfile , and restore the control file from backup. In this case your checkpoint_change# from v$datafile_header would be greater than checkpoint_change# from v$database(since it is old control file) and hence it asks for recovery
Edited by: vreddy on Aug 13, 2012 10:19 AM
Edited by: vreddy on Aug 13, 2012 10:22 AM
Edited by: vreddy on Aug 13, 2012 10:22 AM
Edited by: vreddy on Aug 13, 2012 10:23 AM

Similar Messages

  • Oracle 10g backup and recovery

    Hi
    Can you guys give me some resource of oracle 10g backup and recovery. I want to learn about oracle 10g backup+recovery. Plz help

    Best resource is Backup and Recovery guide from Oracle document site.
    Backup and Recovery Advanced User's Guide
    http://download-west.oracle.com/docs/cd/B19306_01/backup.102/b14191/toc.htm

  • ORACLE8 OPS BACKUP & RECOVERY

    제품 : ORACLE SERVER
    작성날짜 : 2004-08-16
    ORACLE8 OPS BACKUP & RECOVERY
    =============================
    SCOPE
    Standard Edition 에서는 Real Application Clusters 기능이 10g(10.1.0) 이상 부터 지원이 됩니다.
    Explanation
    OPS에서의 database backup & recovery 방법은 single instance의 backup 방법과
    비슷하다. 즉, Single instance에서의 모든 backup 방법은 ops에서도 지원된다.
    1. Backup 방법
    다음의 backup 방법 모두 사용이 가능하다. 여기서는 2)의 os 명령을 이용한
    backup 방법에 대해 기술합니다.
    1) Recovery Manager (RMAN) : <Bulletin 11451> 참고
    2) OS 명령을 활용한 백업
    Noarchive log mode : full offline backup only
    Archive log mode : full or partial, offline or online backup
    3) export : <Bulletin 10080> 참고 : ORACLE 7 BACKUP 및 RECOVERY 방법
    2. backup 정책 수립 시 고려 사항
    1) disk crash나 user error 등으로 말미암은 손실을 허용하지 않는다면 ARCHIVE
    LOG MODE를 사용해야 한다.
    2) 대부분 모든 instance는 자동 archiving을 사용한다.
    3) 모든 data backup 작업이 어떤 instance 건 가능하다.
    4) media recovery 시 모든 thread의 archive file이 사용된다.
    5) Instance recovery 시 살아있는 instance의 smon에 의해 자동으로 recovery된다.
    3. Noarchive log mode : Full offline backup
    1) 다음의 view들을 query하여 backup이 필요한 file을 알아낸다.
    V$DATAFILE or DBA_DATA_FILES
    V$LOGFILE
    V$CONTROLFILE
    2) 모든 instance를 shutdown한다.
    3) 확인된 file을 backup destination으로 copy한다.
    4. Archive log mode : Partial or Full Online Backup
    1) 백업을 수행하기 전에 ALTER SYSTEM ARCHIVE LOG CURRENT 명령 실행(이 명령을
    실행하여 현재 운영되지 않는 데이터베이스를 포함한 모든 노드의 current redo
    log에 대한 로그 스위치와 그에 따른 아카이브를 모든 인스턴스에서 실행시킨다.)
    2) ALTER TABLESPACE tablespace BEGIN BACKUP 명령 실행
    3) ALTER TABLESPACE 명령이 성공적을 실행될 때까지 대기
    4) OS에서 적절한 명령어를 활용하여 테이블스페이스에 속하는 데이터파일들을 백업
    (tar, cpio, cp 등)
    5) OS 명령을 활용한 백업이 다 끝날 때까지 대기
    6) ALTER TABLESPACE tablespace END BACKUP 명령 수행
    7) ALTER DATABASE BACKUP CONTROLFILE TO filename 이나
    ALTER DATABASE BACKUP CONTROLFILE TO TRACE
    명령을 수행시켜 컨트롤 파일을 백업.
    만약 아카이브 로그 파일을 백업받는다면 END BACKUP 명령을 실행시킨 이후
    ALTER SYSTEM ARCHIVE LOG CURRENT 명령을 실행시켜 END BACKUP 시점까지의
    모든 리두 로그 파일들을 확보한다.
    5. Import Parameter
    1) Controlfile 내의 Redo Log History (MAXLOGHISTORY )
    CREATE DATABASE 명령이나 CREATE CONTROLFILE 명령에서 MAXLOGHISTORY 값을
    지정하여 parallel server에서 다 채워진 리두 로그 파일에 대한 history를
    컨트롤 파일이 저장하도록 할 수 있다. 이미 데이터베이스를 생성한 후라면
    log history 값을 증가시키거나 감소시키기 위해서는 컨트롤 파일을 재생성
    하여야만 한다.
    MAXLOGHISTORY는 컨트롤 파일 내의 archive history를 얼마나 저장할 수
    있는지를 지정하며, 기본값은 플랫폼 별로 다르다. 이 값이 0이 아닌 다른
    값으로 지정된다면 log switch가 발생할 때마다 LGWR 프로세스에서는 컨트롤
    파일에 다음 정보를 기록한다.
    thread number, log sequence number, low SCN, low SCN timestamp, next SCN
    (next log의 가장 낮은 SCN값)
    (이 정보는 리두 로그 파일이 archive된 후가 아니라 log switch가 발생할 때
    컨트롤 파일에 저장된다.)
    MAXLOGHISTORY 값에서 지정한 값을 넘어서 log history가 저장되어야 할 경우
    가장 오래된 history를 overwrite하는 방식으로 저장된다. Log history 정보는
    OPS에서 자동 media recovery 시 SCN, thread number를 기준으로 적절한
    아카이브 로그 파일을 찾아 재구성하는 데 사용된다. 데이터베이스를 exclusive
    모드에서 한개의 쓰레드만 사용하는 환경에서는 log history 정보가 필요하지 않다.
    Log history 관련 정보는 V$LOG_HISTORY를 이용해 조회해 볼 수 있다.
    서버 관리자에서 V$RECOVERY_LOG를 조회하면 media recovery에 필요한 아카이브
    로그에 대한 정보를 얻을 수 있다.
    Multiplex된 리두 로그 파일에 대해서, log history 내에서 여러개의 entry가
    사용되지 않는다. 각각의 entry는 개개의 파일에 대한 정보가 아니라, multiplex
    된 log 파일의 그룹에 대한 정보를 가지고 있다.
    2) Archive Log Mode 시 Parameter
    OPS에서 archive log mode로 변경 시 exclusive mode로 db mount 후에 변경한다.
    a. LOG_ARCHIVE_FORMAT
    파라미터     설명     예
    %T     thread number, left-zero-padded     arch0000000001
    %t     thread number, not padded     arch1
    %S     log sequence number, left-zero-padded     arch0000000251
    %s     log sequence number, not padded     arch251
    이 가운데 %T와 %t는 OPS에서만 유효한 파라미터이다.
    모든 instance의 format은 같아야 하며 OPS 환경에서는 반드시 thread 번호를
    포함시켜야 한다.
    예) log_archive_format = %t_%s.arc
    b. LOG_ARCHIVE_START
    - 자동 archiving : TRUE로 지정한 후 인스턴스를 구동시키면 background process
    인 ARCH에서 자동 archiving을 수행한다. Closed Thread의 경우에는 실행 중인
    thread에서 closed thread를 대신해 log switch와 archiving을 수행한다.
    이것은 모든 노드에서 비슷한 SCN을 유지하도록 하기 위해 강제적으로 log switch
    가 발생할 때 일어난다
    - 수동 Archiving : FALSE이면 archive를 시작하도록 지시하는 명령을 명시적으로
    내리지 않는 이상 동작을 멈추고 대기한다. OPS에서는 각각의 인스턴스에서 서로
    다른 LOG_ARCHIVE_START 값을 사용할 수 있다.
    다음과 같은 방법으로 수동 archiving을 수행할 수 있다.
    ALTER SYSTEM ARCHIVE LOG SQL 명령을 실행
    ALTER SYSTEM ARCHIVE LOG START 명령을 실행하여 자동 archiving을 실행하도록
    지정.
    수동 archiving은 명령을 실행시킨 노드에서만 실행 되며, 이 때 archiving
    작업을 ARCH 프로세스가 처리하지 않는다.
    c. LOG_ARCHIVE_DEST
    archive log file이 만들어질 directory를 지정한다.
    예) log_archive_dest = /arch2/arc
    6. OPS Recovery
    1) Instance Failure 시
    Instance failure는 S/W나 H/W 상의 문제, 정전이나 background process에서
    fail이 발생하거나, shutdown abort를 시키거나 OS crash 등 여러가지 이유로
    인해 instance가 더 이상 작업을 진행할 수 없을 때 발생할 수 있다.
    Single instance 환경에서는 instance failure는 instance를 restart 시키고
    database를 open하여 해결된다. Mount 상태에서 open 되는 중간 단계에서 SMON은
    online redo log 파일을 읽어 instance recovery 작업을 수행한다.
    OPS에서는 instance failure가 발생 했을 경우 다른 방식으로 instance
    recovery가 수행된다. OPS에서는 한 노드에서 fail이 발생했다고 하더라도
    다른 노드의 인스턴스는 계속 운영될 수 있기 때문에 instance failure는
    database가 가용하지 않다는 것을 의미하지는 않는다.
    Instance recovery는 dead instance를 처음으로 발견한 SMON 프로세스에서
    수행한다. Recovery가 수행되는 동안 다음과 같은 작업이 일어난다.
    - Fail이 발생하지 않은 다른 인스턴스에서는 fail이 발생한 인스턴스의
    redo log 파일을 읽어 들여 데이터파일에 그 내용을 적용시킨다.
    - 이 기간 동안 fail이 발생하지 않은 다른 노드에서도 buffer cache 영역의
    내용을 write 하지는 못한다.
    - DBWR disk I/O가 일어나지 못한다.
    - DML 사용자에 의해 lock request를 할 수 없다.
    a. Single-node Failure
    한 인스턴스에서 fail이 난 다른 인스턴스에 대한 recovery를 수행하는 동안,
    정상적으로 운영 중인 인스턴스는 fail이 난 인스턴스의 redo log entry를
    읽어 들어 commit이 된 트랜잭션의 결과치를 데이터베이스에 반영시킨다.
    따라서 commit 된 데이터에 대한 손실은 일어나지 않으며, fail이 난
    인스턴스에서 commit 시키지 않은 트랜잭션에 대해서는 rollback을 수행하고,
    트랜잭션에서 사용 중이던 자원을 release시킨다.
    b. Multiple-node Failure
    만약 OPS의 모든 인스턴스에서 fail이 발생했을 경우, 인스턴스 recovery는
    어느 한 인스턴스라도 open이 될 때 자동으로 수행된다. 이 때 open되는 인스턴스는
    fail이 발생한 인스턴스가 아니라도 상관 없으며, OPS에서 shared 모드
    혹은 execlusive 모드에서 데이터베이스를 mount 하더라도 상관 없이 수행된다.
    오라클이 shared 모드에서 수행되던, execlusive 모드에서 수행되건,
    recovery 절차는 하나의 인스턴스에서, fail이 난 모든 인스턴스에 대한
    recovery를 수행하는지 여부를 제외하고는 동일하다.
    2) Media Failure 시
    Oracle에서 사용하는 file을 저장하는 storage media에 문제가 발생했을 경우
    발생한다. 이와 같은 상황에서는 일반적으로 data에 대한 read/write가 불가능하다.
    Media failure가 발생했을 경우 recovery는 single instance의 경우와
    마찬가지로 recovery가 수행되어야 한다. 두 경우 모드 archive log 파일을
    이용해서 transaction recovery를 수행하여야 한다.
    3) Node Failure 시
    OPS 환경에서, 한 노드 전체에 fail이 발생했을 때, 해당 노드에서 동작하던
    instance와 IDLM 컴포넌트에서도 fail이 발생한다. 이 경우 instance recovery를
    하기 위해서는 IDLM은 lock에 대한 remaster를 시키기 위해 그 자신을
    reconfigure시켜야 한다.
    한 노드에서 fail이 발생했을 때 Cluster Manager 또는 다른 GMS product에서는
    failure를 알리고, reconfiguration을 수행하여야만 한다. 이 작업이 수행되어야만
    다른 노드에서 운영 중인 LMD0 프로세스와의 통신이 가능하다.
    오라클에서는 fail이 발생한 노드에서 잡고 있는 lock 정보를 access할 경우나,
    LMON 프로세스에서 heartbeat을 이용해서 fail이 발생한 노드가 더 이상
    가용하지 않다는 것을 감지할 때 failure가 발생한 것을 알게 된다.
    IDLM에서 reconfigure가 일어나면 instance recovery가 수행된다.
    Instance recovery는 recovery를 수행하는 동안 자원에 대한 contention을
    피하기 위해 전체 데이터베이스의 작업을 일시 중지시킬 수 있다.
    FREEZE_DB_FOR_FAST_INSTANCE_RECOVERY initialization parameter 값을
    TRUE로 지정하며 전체 데이터베이스가 일시적으로 작업을 멈추게 된다.
    데이터 화일에서 fine-grain lock을 사용할 경우 기본값은 TRUE이다.
    이 값을 FALSE로 지정할 경우 recovery가 필요한 데이터만이 일시적으로 작업이
    멈춰진다. 데이터 화일이 hash lock을 사용할 경우 FALSE가 기본 값이다.
    4) IDLM failure 시
    한 노드에서 다른 연관된 프로세스의 fail이나 memory fault 등의 이유로 인해
    IDLM 프로세스만 fail이 발생했다면 다른 노드의 LMON에서는 이 문제를 감지하여
    lock reconfiguration process를 시작한다.
    이 작업이 진행 중인 동안 lock 관련 작업은 처리가 정지되고 PCM lock 또는
    다른 resource를 획득하기 위해 일부 사용자들은 대기 상태로 들어간다.
    5) Interconnect Failure ( GMS failure ) 시
    노드 간의 interconnect에서 fail이 발생하면 각각의 노드에서는 서로 다른
    노드의 IDLM과 GMS에서 fail 이 발생했다고 간주하게 된다. GMS에서는 quorum
    disk나 node에 pinging 등을 수행하는 다른 방법을 통해 시스템의 상태를 확인한다.
    이 경우 Fail이 발생한 connection에 대해 두 노드 혹은 한쪽 노드에서
    shutdown 이 일어난다.
    Oracle 8 recovery mechanism에서는 노드 혹은 인스턴스에서 강제로 fail이
    발생했을 경우 IDLM이나 instance가 startup 될 수 없게 된다. 경우에 따라서는
    노드 간의 IDLM communication이 가용한지 여부를 확인하기 위해 cluster
    validation code를 직접 작성하여 사용할 수도 있다. 이 방법을 사용하여
    GMS에서 제공하지는 않지만, 문제를 진단한 후 shutdown을 수행하도록 할 수 있다.
    이같은 code를 작성하기 위해서는 단일 PCM lock에서 처리되는 단일 data block에
    대해 계속해서 update 를 수행해 보는 루틴이 들어가면 된다. 서로 연결된
    두 노드에서 이 프로그램을 실행시키게 될 경우 interconnect에서 fail이
    난 상황을 진단할 수 있게 된다.
    만약 여러개의 노드가 cluster를 구성할 경우에는 매 interconnect 마다
    다른 PCM lock에 의해 처리되는 data block을 update 함으로써, 어떤 노드와의
    interconnect에 문제가 발생했는지를 알아낼 수 있다.
    7. Parallel Recovery
    Parallel Recovery의 목표는 compute와 I/O parallelism을 사용해서 crash
    recovery, single-instance recovery, media recovery 시 소요되는 시간을 줄이는
    데 있다.
    Parallel recovery는 여러 디스크에 걸쳐 몇 개의 데이터파일에 대해 동시에
    recovery를 수행할 때 가장 효율적이다
    다음과 같이 2가지 방식으로 병렬화시킬 수 있다.
    - RECOVERY_PARALLELISM 파라미터 지정
    - RECOVER 명령의 옵션에 지정
    오라클 서버는 하나의 프로세스에서 log file을 순차적으로 읽어들이고, redo
    정보를 여러 개의 recovery 프로세스에 전달해, log file에 기록된 변동 사항을
    데이터파일에 적용시킬 수 있다.
    Recovery Process는 오라클에서 자동적으로 구동되므로, recovery를 수행할 경우
    한 개 이상의 session을 사용할 필요가 없다.
    RECOVERY_PARALLELISM의 최대값은 PARALLEL_MAX_SERVERS 파라미터에 지정된 값을
    초과할 수 없다.
    Reference Ducumment
    Oracle8 ops manual

    Configuration files of the Oracle Application server can be backed up by "Backup and Recovery Tool"
    Pls refer to the documentation,
    http://download.oracle.com/docs/cd/B32110_01/core.1013/b32196/part5.htm#i436649
    Also "backup to tapes feature" is not yet supported by this tool
    thanks,
    Murugesh
    Message was edited by:
    Murugesan Appukuttty

  • Concepts : Backup&Recovery

    Hello Experts
    I want to know the real concepts about Oracle Backup and Recovery process, please tell me where ?. I have a lots of books and pdf's, but they are only just like syllabus or exam preparation material.
    Regards
    Sunil Kumar(India)

    >> I have a lots of books and pdf's,
    Have you read the books on Backup & Recovery wirtten by Rama Velpuri?
    There are many good and real time Backup & Recovery scenarios available in his books. "Oracle 8i Backup & Recovery Handbook"
    By the way, I have worked with Rama Velpuri team for sometime a couple of years back :)
    Regards,
    Sabdar Syed.

  • From where can I buy this book?  Oracle Backup & Recovery

    Oracle Backup & Recovery:
    Expert secrets for using RMAN and Data Pump
    http://www.rampant-books.com/book_1002_rman_backup_recovery.htm
    No answers on Google or Amazon

    user10735952 wrote:
    Oracle Backup & Recovery:
    Expert secrets for using RMAN and Data Pump
    http://www.rampant-books.com/book_1002_rman_backup_recovery.htm
    No answers on Google or AmazonDear OP
    Me and Aman Sharma currently working on this book and there're only two chapters left. We've two strongest reviewers - Hemant K. Chitale and Syed Sabdar who help us a lot.
    This book will be available for the 03/2011

  • Need help on Oracle manual Backup and Recovery?

    Dear Gurus,
    I want to study Oracle manual Backup and Recovery(without RMAN) in detail.
    Is there any book or site, which describes more scenarios and explanation on manual backup and Recovery(without RMAN)
    Regards
    Sanjeev

    user12868781 wrote:
    Dear Gurus,
    I want to study Oracle manual Backup and Recovery(without RMAN) in detail.Why?
    My car has a flat tire. The manufacturer packed a spare tire, jack, and lug wrench in the trunk of the car at no additional cost, and described the process in the owners manual. I want to replace the flat tire without using any method other than the one involving the use of the tools designed for and provided for the job.
    Is there any book or site, which describes more scenarios and explanation on manual backup and Recovery(without RMAN)
    Regards
    Sanjeev

  • Error using Oracle Suggested Backup

    Hi, I am a first time DBA. A new 10g database has just been installed and I have just set up Oracle Suggested Backup in Enterprise Manager for the first time. The first run failed and this is the output log:
    Any help or suggestion is sincerely appreciated.
    Thanks.
    Output Log
    SQL*Plus: Release 10.2.0.1.0 - Production on Fri Jan 5 02:00:19 2007
    Copyright (c) 1982, 2005, Oracle. All rights reserved.
    SQL> SQL> Connected.
    SQL> SQL> SQL> Database closed.
    Database dismounted.
    ORACLE instance shut down.
    SQL> SQL> Disconnected from Oracle Database 10g Enterprise Edition Release 10.2.0.1.0 - Production
    With the Partitioning, OLAP and Data Mining options
    SQL*Plus: Release 10.2.0.1.0 - Production on Fri Jan 5 02:00:37 2007
    Copyright (c) 1982, 2005, Oracle. All rights reserved.
    SQL> SQL> Connected to an idle instance.
    SQL> SQL> ORACLE instance started.
    Total System Global Area 293601280 bytes
    Fixed Size          1248600 bytes
    Variable Size          100663976 bytes
    Database Buffers     184549376 bytes
    Redo Buffers          7139328 bytes
    Database mounted.
    SQL> Disconnected from Oracle Database 10g Enterprise Edition Release 10.2.0.1.0 - Production
    With the Partitioning, OLAP and Data Mining options
    Recovery Manager: Release 10.2.0.1.0 - Production on Fri Jan 5 02:00:42 2007
    Copyright (c) 1982, 2005, Oracle. All rights reserved.
    RMAN>
    connected to target database: ATCFGENP (DBID=36478235, not open)
    using target database control file instead of recovery catalog
    RMAN>
    echo set on
    RMAN> run {
    2> allocate channel oem_disk_backup device type disk;
    3> recover copy of database with tag 'ORA$OEM_LEVEL_0';
    4> backup incremental level 1 cumulative copies=1 for recover of copy with tag 'ORA$OEM_LEVEL_0' database;
    5> }
    allocated channel: oem_disk_backup
    channel oem_disk_backup: sid=156 devtype=DISK
    Starting recover at 05-JAN-07
    no copy of datafile 1 found to recover
    no copy of datafile 2 found to recover
    no copy of datafile 3 found to recover
    no copy of datafile 4 found to recover
    no copy of datafile 5 found to recover
    no copy of datafile 6 found to recover
    no copy of datafile 7 found to recover
    no copy of datafile 8 found to recover
    no copy of datafile 9 found to recover
    R_DAT1.DBF
    output filename=D:\ORACLE\PRODUCT\10.2.0\FLASH_RECOVERY_AREA\ATCFGENP\DATAFILE\O1_MF_WAIVER_D_2SVY0K24_.DBF tag=ORA$OEM_LEVEL_0 recid=8 stamp=611028161
    channel oem_disk_backup: datafile copy complete, elapsed time: 00:00:01
    channel oem_disk_backup: starting incremental level 1 datafile backupset
    channel oem_disk_backup: specifying datafile(s) in backupset
    including current control file in backupset
    including current SPFILE in backupset
    channel oem_disk_backup: starting piece 1 at 05-JAN-07
    released channel: oem_disk_backup
    RMAN-00571: ===========================================================
    RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ==============
    RMAN-00571: ===========================================================
    RMAN-03009: failure of backup command on oem_disk_backup channel at 01/05/2007 02:02:46
    ORA-19809: limit exceeded for recovery files
    ORA-19804: cannot reclaim 7127040 bytes disk space from 2147483648 limit
    RMAN> exit;
    Recovery Manager complete.
    SQL*Plus: Release 10.2.0.1.0 - Production on Fri Jan 5 02:02:47 2007
    Copyright (c) 1982, 2005, Oracle. All rights reserved.
    SQL> SQL> Connected.
    SQL> SQL>
    Database altered.
    SQL> Disconnected from Oracle Database 10g Enterprise Edition Release 10.2.0.1.0 - Production
    With the Partitioning, OLAP and Data Mining options

    Your Flashback Recovery Area is not sized properly, follow the suggestions as given by the error message:
    Error:     ORA-19804 (ORA-19804)
    Text:     cannot reclaim %s bytes disk space from %s limit
    Cause:     Oracle cannot reclaim disk space of specified bytes from the
         DB_RECOVERY_FILE_DEST_SIZE limit.
    Action:     There are five possible solutions: 1) Take frequent backup of
         recovery area using RMAN. 2) Consider changing RMAN retention
         policy. 3) Consider changing RMAN archivelog deletion policy. 4)
         Add disk space and increase DB_RECOVERY_FILE_DEST_SIZE. 5) Delete
         files from recovery area using RMAN.
    Werner

  • Error during Backup/Recovery settings configuration

    Hi all,
    Using the Oracle Enterprise Manager 10g Application Server control,
    i am configuring backup/recovery settings for my infrastructure tier in a 10g Rel 2 application server environment. however after specifying the various locations for Log Files, Configuration files, Metadata repository database backup etc i get the following error after clicking the 'Ok' button.
    An Internal Error has occurred while performing the operation.
    Performing configuration ...
    oracle_sid: cinfra
    The command /oracle/appn/oracle/infra/perl/bin/perl /oracle/appn/oracle/infra/backup_restore/bkp_restore.pl -m configure -h /oracle/appn/oracle/infra -f > /infrahome/backups/log_files/2009-12-06_17-13-38_output.log failed with return code 255
    i am at a loss as to why i am having this error and how to fix it.
    I examined the log file and saw an error snippet saying
    *"Unable to get dbid from the database. Please ensure that ORACLE_HOME and ORACLE_SID are set to the same values used when starting up the database and that the database is open.... Failure: Configure failed"*
    Also examined another file generated at the same time as the output log file and in there i saw the following
    *"ld,so.1: oracle: fatal: relocation error: file /oracle/appn/oracle/product/10.2.0/cm2t/lib/libjox10.so: symbol kgestKguard_: referenced symbol not found*
    *ERROR:*
    *ORA-12547: TNS: lost contact*
    *SP2-0751: Unable to connect to oracle. exiting SQL*Plus"*
    Apart from the infrastructure database, i have another database with SID 'cm2t' on the same machine and i am suspecting that OEM Application server control is referencing the wrong file while it's doing it's work. How do i tell it to look in the right place if indeed that is the cause of my problem?
    In my config.inp file all the right parameter values are in place.
    Thanks.
    Steve.

    Hi AMN,
    Thanks for your reply. I managed to solve it by taking the following steps.
    I use the runstartupconsole.sh script to start up my infrastructure tier. At startup it was using an LD_LIBRARY_PATH pointing to that used by an existing Oracle database instance on the same machine.
    I set ORACLE_HOME, ORACLE_SID, LD_LIBRARY_PATH etc correctly before running the runstartupconsole.sh script and after that i was able to setup my backup/recovery settings properly.
    I hope this will be useful to others.
    Steve.

  • RMAN-06004:ORACLE error from recovery catalog ... ORA-00904: : invalid ...

    Good Morning All,
    One of our RMAN backups is failing with the following error message. Any suggestions would be greatly appreciated.
    ==================================================================================================
    Starting backup at 12/30/2008 22:03:47
    using channel ORA_DISK_1
    RMAN-00571: ===========================================================
    RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
    RMAN-00571: ===========================================================
    RMAN-03002: failure of backup command at 12/30/2008 22:03:47
    RMAN-06004: ORACLE error from recovery catalog database: ORA-00904: : invalid identifier
    RMAN>
    RMAN> ##BACKUP ARCHIVELOG ALL FORMAT '%d_bkp_al_%t_Set%s_Piece%p' delete input;
    2>
    3> # DELETE ARCHIVELOG UNTIL TIME 'SYSDATE-7';
    4>
    5> # check if database can be restored
    6> # RESTORE DATABASE VALIDATE;
    7>
    8> # check if controlfile can be restored
    9> ##RESTORE CONTROLFILE to '/backups/admin/custpr/custpr_bkp_cntlfile.ctl' VALIDATE;
    10>
    11> # check if archivelogs for the past two weeks can be restored
    12> # RESTORE ARCHIVELOG FROM TIME 'SYSDATE-7' VALIDATE;
    13>
    14> # - Verify all backups on backup media are intact
    15> # CROSSCHECK BACKUP OF DATABASE;
    16>
    17> # - Display a list of files that need to be backed up based on the retention
    18> # policy. For this case study, files that don't have at least 1 backups
    19> # will be reported.
    20> REPORT NEED BACKUP;
    RMAN retention policy will be applied to the command
    RMAN retention policy is set to recovery window of 7 days
    Report of files whose recovery needs more than 7 days of archived logs
    File Days Name
    RMAN-00571: ===========================================================
    RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
    RMAN-00571: ===========================================================
    RMAN-03002: failure of report command at 12/30/2008 22:03:48
    RMAN-06004: ORACLE error from recovery catalog database: ORA-00904: : invalid identifier
    RMAN>
    RMAN> # - delete un-necessary backups. This command deletes backups based on the
    2> # retention policy.
    3> ######### commented out DELETE OBSOLETE - TSM not configured to delete on 68
    4> #########DELETE OBSOLETE;
    5>
    6> # - get complete list of existing backups
    7> LIST BACKUP;
    RMAN-00571: ===========================================================
    RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
    RMAN-00571: ===========================================================
    RMAN-03002: failure of list command at 12/30/2008 22:03:49
    RMAN-06004: ORACLE error from recovery catalog database: ORA-00904: : invalid identifier
    RMAN>
    RMAN> #-end of file-
    2> **end-of-file**
    RMAN>
    Edited by: ORA_UMAIR on Dec 31, 2008 7:51 AM

    This Oracle Database is 9.2.0.6.0. Here is the complete log file. The RMAN script that I am using ran successfully many times before.
    ====================================================================================================
    Recovery Manager: Release 9.2.0.6.0 - 64bit Production
    Copyright (c) 1995, 2002, Oracle Corporation. All rights reserved.
    RMAN>
    connected to recovery catalog database
    RMAN>
    connected to target database: CUSTPR (DBID=525071053)
    RMAN>
    RMAN> #########################################################################
    2> # LEVEL 0 BACKUP #
    3> #########################################################################
    4>
    5> # Configure backups to be written to disk.
    6> CONFIGURE DEFAULT DEVICE TYPE TO DISK;
    old RMAN configuration parameters:
    CONFIGURE DEFAULT DEVICE TYPE TO DISK;
    new RMAN configuration parameters:
    CONFIGURE DEFAULT DEVICE TYPE TO DISK;
    new RMAN configuration parameters are successfully stored
    starting full resync of recovery catalog
    full resync complete
    RMAN>
    RMAN> # Set the retention policy to a recovery window of 7 days. This ensures that
    2> # RMAN retains all backups needed to recover the database to any point in time
    3> # in the last 7 days. You can use the DELETE OBSOLETE command to delete
    4> # backups that are no longer required by the retention policy. To exclude a
    5> # backup from consideration by the policy, you can use KEEP option with the
    6> # BACKUP command.
    7> CONFIGURE RETENTION POLICY TO RECOVERY WINDOW OF 7 DAYS;
    old RMAN configuration parameters:
    CONFIGURE RETENTION POLICY TO RECOVERY WINDOW OF 7 DAYS;
    new RMAN configuration parameters:
    CONFIGURE RETENTION POLICY TO RECOVERY WINDOW OF 7 DAYS;
    new RMAN configuration parameters are successfully stored
    starting full resync of recovery catalog
    full resync complete
    RMAN>
    RMAN> # Configure RMAN to use two disk channels for backup, restore, recovery, and
    2> # maintenance operations.
    3> CONFIGURE DEVICE TYPE DISK PARALLELISM 1;
    old RMAN configuration parameters:
    CONFIGURE DEVICE TYPE DISK PARALLELISM 1;
    new RMAN configuration parameters:
    CONFIGURE DEVICE TYPE DISK PARALLELISM 1;
    new RMAN configuration parameters are successfully stored
    starting full resync of recovery catalog
    full resync complete
    RMAN>
    RMAN> # Configure RMAN to write disk backups to the /backup directory.
    2> # The format specifier %t is replaced with a 4-byte timestamp, %s with the
    3> # backup set number, and %p with the backup piece number.
    4> CONFIGURE CHANNEL DEVICE TYPE DISK FORMAT '/backups/admin/custpr/%d_bkp_df%t_Set%s_Piece%p';
    old RMAN configuration parameters:
    CONFIGURE CHANNEL DEVICE TYPE DISK FORMAT '/backups/admin/custpr/%d_bkp_df%t_Set%s_Piece%p';
    new RMAN configuration parameters:
    CONFIGURE CHANNEL DEVICE TYPE DISK FORMAT '/backups/admin/custpr/%d_bkp_df%t_Set%s_Piece%p';
    new RMAN configuration parameters are successfully stored
    starting full resync of recovery catalog
    full resync complete
    RMAN>
    RMAN> # Configure RMAN to back up the control file after each backup.
    2> CONFIGURE CONTROLFILE AUTOBACKUP ON;
    old RMAN configuration parameters:
    CONFIGURE CONTROLFILE AUTOBACKUP ON;
    new RMAN configuration parameters:
    CONFIGURE CONTROLFILE AUTOBACKUP ON;
    new RMAN configuration parameters are successfully stored
    starting full resync of recovery catalog
    full resync complete
    RMAN>
    RMAN> # Configure RMAN to write controlfile autobackups to the /backup directory.
    2> CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO '/backups/admin/custpr/%d_bkp_cf%F';
    old RMAN configuration parameters:
    CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO '/backups/admin/custpr/%d_bkp_cf%F';
    new RMAN configuration parameters:
    CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO '/backups/admin/custpr/%d_bkp_cf%F';
    new RMAN configuration parameters are successfully stored
    starting full resync of recovery catalog
    full resync complete
    RMAN>
    RMAN> # Enable the backup optimization feature introduced in 9i to make sure that
    2> # RMAN won't backup an archivelog or datafile if there already exists a backup
    3> # of that file. The FORCE option can be used to override optimization on a
    4> # specific BACKUP command.
    5> CONFIGURE BACKUP OPTIMIZATION ON;
    old RMAN configuration parameters:
    CONFIGURE BACKUP OPTIMIZATION ON;
    new RMAN configuration parameters:
    CONFIGURE BACKUP OPTIMIZATION ON;
    new RMAN configuration parameters are successfully stored
    starting full resync of recovery catalog
    full resync complete
    RMAN>
    RMAN> # Use the SHOW ALL command to see the current configuration settings.
    2> SHOW ALL ;
    RMAN configuration parameters are:
    CONFIGURE RETENTION POLICY TO RECOVERY WINDOW OF 7 DAYS;
    CONFIGURE BACKUP OPTIMIZATION ON;
    CONFIGURE DEFAULT DEVICE TYPE TO DISK;
    CONFIGURE CONTROLFILE AUTOBACKUP ON;
    CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE 'SBT_TAPE' TO '%d_bkp_cf%F';
    CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO '/backups/admin/custpr/%d_bkp_cf%F';
    CONFIGURE DEVICE TYPE 'SBT_TAPE' PARALLELISM 1;
    CONFIGURE DEVICE TYPE DISK PARALLELISM 1;
    CONFIGURE DATAFILE BACKUP COPIES FOR DEVICE TYPE SBT_TAPE TO 1; # default
    CONFIGURE DATAFILE BACKUP COPIES FOR DEVICE TYPE DISK TO 1; # default
    CONFIGURE ARCHIVELOG BACKUP COPIES FOR DEVICE TYPE SBT_TAPE TO 1; # default
    CONFIGURE ARCHIVELOG BACKUP COPIES FOR DEVICE TYPE DISK TO 1; # default
    CONFIGURE CHANNEL DEVICE TYPE 'SBT_TAPE' FORMAT '%d_bkp_df%t_Set%s_Piece%p';
    CONFIGURE CHANNEL DEVICE TYPE DISK FORMAT '/backups/admin/custpr/%d_bkp_df%t_Set%s_Piece%p';
    CONFIGURE MAXSETSIZE TO UNLIMITED; # default
    CONFIGURE SNAPSHOT CONTROLFILE NAME TO '/orahome2/custprdb/9.2.0/dbs/snapcf_custpr.f'; # default
    RMAN>
    RMAN> # The following commands are run each day to start the backup cycle.
    2> # The steps are:
    3> # - Take an incremental level 0 backup of the database. A level 0 backup is
    4> # a complete backup of the entire file which can be used as the basis
    5> # for a subsequent incremental backup.
    6> # - Backup all archivelogs that have not already been backed up.
    7> # - Delete on-disk archivelogs older than seven days.
    8>
    9> BACKUP INCREMENTAL LEVEL 0 FORMAT '/backups/admin/custpr/%d_bkp_df%t_Set%s_Piece%p'
    10> DATABASE maxsetsize 33G
    11> PLUS ARCHIVELOG FORMAT '/backups/admin/custpr/%d_bkp_al%t_Set%s_Piece%p'
    12> delete all input;
    Starting backup at 12/30/2008 22:01:40
    current log archived
    allocated channel: ORA_DISK_1
    channel ORA_DISK_1: sid=11 devtype=DISK
    channel ORA_DISK_1: starting archive log backupset
    channel ORA_DISK_1: specifying archive log(s) in backup set
    input archive log thread=1 sequence=8008 recid=7910 stamp=674638862
    input archive log thread=1 sequence=8009 recid=7911 stamp=674671207
    input archive log thread=1 sequence=8010 recid=7912 stamp=674697380
    input archive log thread=1 sequence=8011 recid=7913 stamp=674780433
    input archive log thread=1 sequence=8012 recid=7914 stamp=674784211
    input archive log thread=1 sequence=8013 recid=7915 stamp=674863288
    input archive log thread=1 sequence=8014 recid=7916 stamp=674863300
    channel ORA_DISK_1: starting piece 1 at 12/30/2008 22:01:41
    channel ORA_DISK_1: finished piece 1 at 12/30/2008 22:03:47
    piece handle=/backups/admin/custpr/CUSTPR_bkp_al674863300_Set3083_Piece1 comment=NONE
    channel ORA_DISK_1: backup set complete, elapsed time: 00:02:07
    channel ORA_DISK_1: deleting archive log(s)
    archive log filename=/custpr/arch/arch_custpr_8008.log recid=7910 stamp=674638862
    archive log filename=/custpr/arch/arch_custpr_8009.log recid=7911 stamp=674671207
    archive log filename=/custpr/arch/arch_custpr_8010.log recid=7912 stamp=674697380
    archive log filename=/custpr/arch/arch_custpr_8011.log recid=7913 stamp=674780433
    archive log filename=/custpr/arch/arch_custpr_8012.log recid=7914 stamp=674784211
    archive log filename=/custpr/arch/arch_custpr_8013.log recid=7915 stamp=674863288
    archive log filename=/custpr/arch/arch_custpr_8014.log recid=7916 stamp=674863300
    Finished backup at 12/30/2008 22:03:47
    Starting backup at 12/30/2008 22:03:47
    using channel ORA_DISK_1
    RMAN-00571: ===========================================================
    RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
    RMAN-00571: ===========================================================
    RMAN-03002: failure of backup command at 12/30/2008 22:03:47
    RMAN-06004: ORACLE error from recovery catalog database: ORA-00904: : invalid identifier
    RMAN>
    RMAN> ##BACKUP ARCHIVELOG ALL FORMAT '%d_bkp_al_%t_Set%s_Piece%p' delete input;
    2>
    3> # DELETE ARCHIVELOG UNTIL TIME 'SYSDATE-7';
    4>
    5> # check if database can be restored
    6> # RESTORE DATABASE VALIDATE;
    7>
    8> # check if controlfile can be restored
    9> ##RESTORE CONTROLFILE to '/backups/admin/custpr/custpr_bkp_cntlfile.ctl' VALIDATE;
    10>
    11> # check if archivelogs for the past two weeks can be restored
    12> # RESTORE ARCHIVELOG FROM TIME 'SYSDATE-7' VALIDATE;
    13>
    14> # - Verify all backups on backup media are intact
    15> # CROSSCHECK BACKUP OF DATABASE;
    16>
    17> # - Display a list of files that need to be backed up based on the retention
    18> # policy. For this case study, files that don't have at least 1 backups
    19> # will be reported.
    20> REPORT NEED BACKUP;
    RMAN retention policy will be applied to the command
    RMAN retention policy is set to recovery window of 7 days
    Report of files whose recovery needs more than 7 days of archived logs
    File Days Name
    RMAN-00571: ===========================================================
    RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
    RMAN-00571: ===========================================================
    RMAN-03002: failure of report command at 12/30/2008 22:03:48
    RMAN-06004: ORACLE error from recovery catalog database: ORA-00904: : invalid identifier
    RMAN>
    RMAN> # - delete un-necessary backups. This command deletes backups based on the
    2> # retention policy.
    3> ######### commented out DELETE OBSOLETE - TSM not configured to delete on 68
    4> #########DELETE OBSOLETE;
    5>
    6> # - get complete list of existing backups
    7> LIST BACKUP;
    RMAN-00571: ===========================================================
    RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
    RMAN-00571: ===========================================================
    RMAN-03002: failure of list command at 12/30/2008 22:03:49
    RMAN-06004: ORACLE error from recovery catalog database: ORA-00904: : invalid identifier
    RMAN>
    RMAN> #-end of file-
    2> **end-of-file**
    RMAN>
    Recovery Manager complete.

  • INCREMENTAL MERGE BACKUP & RECOVERY

    INCREMENTAL MERGE BACKUP & RECOVERY
    =====================================
    1) 개요
    RMAN을 이용하여 database의 Image copy를 Backup하고 그 Backup에 retention policy만큼의 Incremental Backup을 적용하여서 복구의 시간을 단축한 Backup의 방법입니다.
    즉 retention policy에 설정되어있는 시간 전의 최후의 시간까지 Image Copy를 보장하는 방법이며 Disk Space는 Incremental Backup만 사용하는 방법보다는 Image Copy를 사용하는 것임으로 많이 소요됩니다.
    물론 Backup & Recovery 정책에 따라서 Retention Policy를 Recovery Window나 Redundancy 2이상으로 설정할 수 있으나, Incremental Merge Backup & Recovery의 장점을 극대화 하기 위해서는 Redundancy 1 (Default)로 설정하는 것을 권해드립니다.
    2) 장점
    - Recovery 시에 최근 Incremental Backup의 정보들이 적용이 되어있기 때문에 최소한의 시간으로 Recovery 작업을 진행하실 수 있습니다. 물론 장점을 극대화 하시기 위해서는 Retention Policy를 redundancy 1로 설정해 주시길 권해드립니다.
    - Datafile들의 Destination을 Backup된 Image Copy가 있는 곳으로 Switch 하여 Restore하는 시간을 단축하셔서 Recovery를 진행하실 수도 있으나 Recovery 후의 관리의 용이성을 위해 부득히한 경우를 재외하고는 권장하지 않습니다.
    3) Syntax
    - Backup
    RMAN> BACKUP INCREMENTAL LEVEL 1
    FOR RECOVER OF COPY
    WITH TAG WEEKLY DATABASE;
    위 명령어를 사용하시면 WEEKLY라는 Tag로 생성된 Copy가 없을 시에는 Image Copy를 Weekly라는 Tag로 구분하여 Backup을 받게 됩니다.
    * 여기서 Copy라 함은 FOR RECOVER OF COPY라는 구문을 사용하여서 만든 Image Copy를 뜻합니다.
    RMAN> RECOVER COPY OF DATABASE WITH TAG WEEKLY;
    위 명령어를 사용하시면 현재 받았던 Incremental Backup을 Weekly라는 Tag를 가지고 있는 Database Copy에 적용을 하게 됩니다.
    RMAN> Delete Obsolete;
    위 명령어를 사용하시면 현재의 Image Copy에 적용된 Incremental Backup을 재외한 나머지 Incremental Backup들이 Delete됩니다.
    -Recovery
    RMAN> switch database to copy;
    문제가 발생하셨을 때 위 명령어를 사용하시면 모든 datafile의 pointer들은 image backup copy를 바라보게 됨으로 Restore의 시간을 절약할 수 있습니다.
    4) Retention Policy에 따른 Syntax 변화
    * 기본적으로 INCREMENTAL MERGE BACKUP & RECOVERY의 장점인 Recovery 시간을 극대화 하기 위해서는 Retention Policy를 redundancy 1(Default)로 설정하시는 것을 권장해드립니다.
    하지만 User가 Backup & Recovery 계획을 변경하여 retention policy를 recovery window 또는 redundancy 1 이상으로 설정해 주시면 Obsolete한 Backupset을 Delete하는 부분과 Backupset을 적용시키는 부분을 수정해 주셔야합니다.
    - Recovery Window of 2
    Recovery Window를 2일로 설정해 놓으시면 Backup시에는 똑같은 Syntax를 사용하실 수 있으나 Recover copy of database 명령어는 아래와 같이 바뀌어야 합니다.
    RMAN> BACKUP INCREMENTAL LEVEL 1
    FOR RECOVER OF COPY
    WITH TAG WEEKLY DATABASE;
    RMAN> RECOVER COPY OF DATABASE WITH TAG WEEKLY until time 'sysdate-2';
    왜냐하면 retention policy에 마춰서 image copy도 2일전의 상태로 보관되어야하며 그에 따라서 2일동안의 Backupset들도 보관되어야하기 때문입니다. 만약 until time을 사용하지 않으시면 incremental backup들이 obsolete 상태로 안변하게 됩니다.
    - Redundancy 2 이상
    Redundancy 2이상으로 설정해 주시면 2개 이상의 Tag를 보관하는 효과로서 역시 예상대로 Obsolete로 안 변하는 현상이 발생됩니다.
    DAY 1)
    RMAN> BACKUP INCREMENTAL LEVEL 1 FOR RECOVER OF COPY WITH TAG DAILY DATABASE;
    -위와 같이 실행하시면 한개의 Database Copy (Tag DAILY)가 생성됩니다.
    DAY 2)
    RMAN> BACKUP INCREMENTAL LEVEL 1 FOR RECOVER OF COPY WITH TAG DAILY DATABASE;
    RMAN> BACKUP INCREMENTAL LEVEL 1 FOR RECOVER OF COPY WITH TAG WEEKLY DATABASE;
    -위와 같이 실행하시면 한개의 Database Copy (Tag WEEKLY)와 한개의 Backupset (Tag DAILY)가 생성됩니다.
    DAY 3)
    RMAN> BACKUP INCREMENTAL LEVEL 1 FOR RECOVER OF COPY WITH TAG DAILY DATABASE;
    RMAN> BACKUP INCREMENTAL LEVEL 1 FOR RECOVER OF COPY WITH TAG WEEKLY DATABASE;
    RMAN> BACKUP INCREMENTAL LEVEL 1 FOR RECOVER OF COPY WITH TAG MONTHLY DATABASE;
    -위와 같이 실행하시면 한개의 Database Copy (Tag MONTHLY)와 두개의 Backupset (Tag DAILY, Tag WEEKLY)가 생성됩니다.
    DAY 4)
    RMAN> Delete Obsolete;
    - 위와 같이 실행하시면 DAILY Tag와 관련된 부분이 Delete 됩니다. (최신 2개의 Tag관련 Backup만 보관)
    RMAN> Delete Obsolete redundancy 1
    - 위와 같이 실행하시면 DAYLY Tag와 WEEKLY Tag 관련된 부분이 Delete 됩니다. (Redundancy 1로 설정한 것과 똑같은 효과)
    Reference:
    Article-ID: Note 351455.1
    Title: Oracle Suggested Strategy & Backup Retention
    Article-ID: Note 303861.1
    Title: Incrementally Updated Backup In 10G
    글 수정:
    hunlee

    I would always include an archivelog backup:
    ... with tag 'fullbackup’ database plus archivelog delete all input;
    And at the end:
    delete obsolete noprompt;
    That delete incrmental backups already applied to the basic image copies.
    Your configuration allows only limited point in time recoveries. As soon as an incremental backup is applied to the image copies, you cannot go back in time. To change this you can add a 'until time' clause, for example:
    recover
    copy of database
    with tag 'fullbackup until time 'sysdate-11';
    This creates a recovery window of 10 days, only image copies older than 10 days will be changed.
    Werner

  • Cold Oracle EBS backup and restore doesn't work

    Hi,
    I did a backup using tar while the database was open and not in archive mode ( archivelog disabled ) and restored it on another machine.
    OS = AIX 5.3
    Oracle EBS 11.5.9
    Database 9i
    When i started the database I got errors.
    Is there a metalink document which will help me recover the database ?
    I followed the following metalinks:
    Database Startup Fails with ORA-01113, ORA-01110 errors [ID 146039.1]
    Common Causes and Solutions on ORA-1113 Error Found in Backup & Recovery [ID 183367.1]
    However, I would like to point out that the above is applicable in case of archivelogs = enabled
    My case: archivelogs = disabled
    SQL> startup mount pfile=/oracle/proddb/9.2.0/dbs/initPROD.ora
    ORACLE instance started.
    Total System Global Area 615482512 bytes
    Fixed Size 742544 bytes
    Variable Size 436207616 bytes
    Database Buffers 167772160 bytes
    Redo Buffers 10760192 bytes
    Database mounted.
    SQL> SELECT V1.FILE#, NAME
    FROM V$BACKUP V1, V$DATAFILE V2
    WHERE V1.STATUS = 'ACTIVE' AND V1.FILE# = V2.FILE# ; 2 3
    no rows selected
    SQL> recover database using backup controlfile until cancel;
    ORA-00279: change 3368247542 generated at 02/10/2013 03:07:21 needed for thread
    1
    ORA-00289: suggestion : /oracle/proddb/9.2.0/dbs/arch1_637.dbf
    ORA-00280: change 3368247542 for thread 1 is in sequence #637
    Specify log: {<RET>=suggested | filename | AUTO | CANCEL}
    cancel
    ORA-01547: warning: RECOVER succeeded but OPEN RESETLOGS would get error below
    ORA-01194: file 1 needs more recovery to be consistent
    ORA-01110: data file 1: '/oracle/proddata/system01.dbf'
    ORA-01112: media recovery not started
    SQL> recover database using backup controlfile until cancel;
    ORA-00279: change 3368247542 generated at 02/10/2013 03:07:21 needed for thread
    1
    ORA-00289: suggestion : /oracle/proddb/9.2.0/dbs/arch1_637.dbf
    ORA-00280: change 3368247542 for thread 1 is in sequence #637
    Specify log: {<RET>=suggested | filename | AUTO | CANCEL}
    ORA-00308: cannot open archived log '/oracle/proddb/9.2.0/dbs/arch1_637.dbf'
    ORA-27037: unable to obtain file status
    IBM AIX RISC System/6000 Error: 2: No such file or directory
    Additional information: 3
    ORA-01547: warning: RECOVER succeeded but OPEN RESETLOGS would get error below
    ORA-01194: file 1 needs more recovery to be consistent
    ORA-01110: data file 1: '/oracle/proddata/system01.dbf'
    SQL> alter database open resetlogs;
    alter database open resetlogs
    ERROR at line 1:
    ORA-01194: file 1 needs more recovery to be consistent
    ORA-01110: data file 1: '/oracle/proddata/system01.dbf'
    SQL> select HXFIL File_num,substr(HXFNM,1,40) File_name,FHTYP Type,HXERR Validity,
    FHSCN SCN, FHTNM TABLESPACE_NAME,FHSTA status ,FHRBA_SEQ Sequence
    from X$KCVFH;
    419 rows selected.

    981553 wrote:
    I understand that Hot backups cannot be done with noarchivelog and data will be inconsistent.
    However, shouldn't the Database be able to recover whatever data is in there in the datafiles and startup normally. From where should it be recoverd, only if we store the data changes in a separate files. These files are called archive logs. The archive logs will be generated when you enable archive log.
    This is my question and concern. I searched for Metalink and couldn't find anything on it.
    I want to startup the database with whatever Data is present there after the backup. Any solutions for such a scenario ?
    ORA-00279: change 3368247542 generated at 02/10/2013 03:07:21 needed for thread
    1
    ORA-00289: suggestion : /oracle/proddb/9.2.0/dbs/arch1_637.dbf
    ORA-00280: change 3368247542 for thread 1 is in sequence #637
    Specify log: {<RET>=suggested | filename | AUTO | CANCEL}When it asks for change number "637" and if you are lucky enough that the redo log file with this sequence is not over written then that redo log file can be given as input when it asks as above.
    But again, all these tries are for nothing. At the end of the day if your database is in no archive log mode the reliable backup is only the one taken using cold backup method. i.e. by shutting down the database.
    Thanks

  • Oracle secure  backup "lsbackup " not showing in obtool

    hi!
    i am using oracle secure backup with virtual tape drive....
    lsdev -lvlib:
    Device type: library (virtual)
    Model: [none]
    Serial number: 82206a7c
    In service: yes
    Debug mode: no
    Barcode reader: default (hardware-selected)
    Barcodes required: no
    Auto clean: no
    Clean interval: (not set)
    Clean using emptiest: no
    Ejection type: auto
    Min writable volumes: 0
    UUID: d9916f34-cdec-102c-a9cf-000c2912137c
    Attachment 1:
    Host: osb
    Raw device: /vlib
    vt:
    Device type: tape (virtual)
    Model: [none]
    Serial number: 96627110
    In service: yes
    Library: vlib
    DTE: 1
    Automount: yes
    Error rate: 8
    Query frequency: [undetermined]
    Debug mode: no
    Blocking factor: (default)
    Max blocking factor: (default)
    Current tape: [unknown]
    Use list: all
    Drive usage: 1 minute, 9 seconds
    Cleaning required: no
    UUID: f2efc426-cdec-102c-a9cf-000c2912137c
    Attachment 1:
    Host: osb
    Raw device: /vt
    its working fine i use rman and took two backups....but i dont know where are they....on os i have two directory vlib(library) and one more was created 'vt'(tape drive).i know backups are in vlib but how to check them..through obtool ...it shows nothing..
    please help.......
    BACKUP 1:
    RMAN> run
    2> {
    3> allocate channel ch1 device type sbt;
    4> backup datafile 4;
    5> release channel ch1;
    6> }
    using target database control file instead of recovery catalog
    allocated channel: ch1
    channel ch1: sid=130 devtype=SBT_TAPE
    channel ch1: Oracle Secure Backup
    Starting backup at 22-DEC-09
    channel ch1: starting full datafile backupset
    channel ch1: specifying datafile(s) in backupset
    input datafile fno=00004 name=/u01/app/oracle/product/10.2.0/oradata/orcl/users01.dbf
    channel ch1: starting piece 1 at 22-DEC-09
    channel ch1: finished piece 1 at 22-DEC-09
    piece handle=0nl1h7ao_1_1 tag=TAG20091222T061656 comment=API Version 2.0,MMS Version 10.3.0.1
    channel ch1: backup set complete, elapsed time: 00:00:25
    Finished backup at 22-DEC-09
    released channel: ch1
    BACKUP 2 .......
    RMAN> run
    2> {
    3> allocate channel ch1 device type 'SBT_TAPE';
    4> backup datafile 3;
    5> backup datafile 2;
    6> release channel ch1;
    7> }
    allocated channel: ch1
    channel ch1: sid=130 devtype=SBT_TAPE
    channel ch1: Oracle Secure Backup
    Starting backup at 22-DEC-09
    channel ch1: starting full datafile backupset
    channel ch1: specifying datafile(s) in backupset
    input datafile fno=00003 name=/u01/app/oracle/product/10.2.0/oradata/orcl/sysaux01.dbf
    channel ch1: starting piece 1 at 22-DEC-09
    channel ch1: finished piece 1 at 22-DEC-09
    piece handle=0ol1h7nq_1_1 tag=TAG20091222T062354 comment=API Version 2.0,MMS Version 10.3.0.1
    channel ch1: backup set complete, elapsed time: 00:00:45
    Finished backup at 22-DEC-09
    Starting backup at 22-DEC-09
    channel ch1: starting full datafile backupset
    channel ch1: specifying datafile(s) in backupset
    input datafile fno=00002 name=/u01/app/oracle/product/10.2.0/oradata/orcl/undotbs01.dbf
    channel ch1: starting piece 1 at 22-DEC-09
    channel ch1: finished piece 1 at 22-DEC-09
    piece handle=0pl1h7p7_1_1 tag=TAG20091222T062439 comment=API Version 2.0,MMS Version 10.3.0.1
    channel ch1: backup set complete, elapsed time: 00:00:25
    Finished backup at 22-DEC-09
    released channel: ch1
    Edited by: Muhammad.Usman on Dec 22, 2009 8:51 PM

    The configuration you have described is not supported. If you want to use a VTL you will need to purchase one from a supported VTL supplier.
    OSB does not provide its own VTL.
    Rich

  • Unable to see Oracle Secure Backup Selections in EM (10g-10.2.0.1)

    I cannot see the Oracle Secure Backup choices on the maintenance tab page.
    I see Backup/Recovery and Backup/Recovery Settings but no third column Oracle Secure Backup.
    I logon to EM as SYS.
    Any ideas ?
    Thanks

    If you go to the maintenance tab on your EM, are there a couple of links under "Oracle Secure Backup" heading. I don't have this showing on my page. If I look at any of the Oracle demo pages I see it.
    Like I said it is a feature of 10gR2....which I have.

  • Oracle 11g flash recovery keeps growing

    Oracle 11g flash recovery (E:\ partition in a Windows 2003 server) keeps growing. It already used 200GB of disk space and only 46GB of disk space is left in that partition. Can we tell how often Oracle 11g delete the old backups?
    Thanks.
    Andy

    andychow wrote:
    SQL> set linesize 1000
    SQL> select substr(name,1,30) name,
    2         space_limit,
    3         space_used,
    4         space_reclaimable,
    5         number_of_files
    6  from V$RECOVERY_FILE_DEST
    7  ;
    NAME                           SPACE_LIMIT SPACE_USED SPACE_RECLAIMABLE NUMBER_OF_FILES
    E:\flash_recovery_area_11       1.0486E+11 1.6752E+10                 0               5
    SQL> select *
    2  from V$FLASH_RECOVERY_AREA_USAGE
    3  ;
    FILE_TYPE            PERCENT_SPACE_USED PERCENT_SPACE_RECLAIMABLE NUMBER_OF_FILES
    CONTROL FILE                          0                         0               0
    REDO LOG                              0                         0               0
    ARCHIVED LOG                        .09                         0               2
    BACKUP PIECE                      15.88                         0               3
    IMAGE COPY                            0                         0               0
    FLASHBACK LOG                         0                         0               0
    FOREIGN ARCHIVED LOG                  0                         0               0
    7 rows selected.
    SQL>
    It shows only 5 files in E:\flash_recovery_area_11. Can you verify ?

  • Oracle Secure Backup error: 'No such file or directory'

    Hi,
    could you help me to fix the following issue?
    RMAN> run {   ALLOCATE CHANNEL c1 DEVICE TYPE sbt PARMS='SBT_LIBRARY=C:\windows\
    system32\orasbt.dll' ; backup database format 'CF_%d_%T_s%sp%pt%t'; }
    using target database control file instead of recovery catalog
    allocated channel: c1
    channel c1: SID=8 device type=SBT_TAPE
    channel c1: Oracle Secure BackupStarting backup at 26-OCT-09
    channel c1: starting full datafile backup set
    channel c1: specifying datafile(s) in backup set
    input datafile file number=00001 name=C:\APP\AIME\ORADATA\ORCL\SYSTEM01.DBF
    input datafile file number=00002 name=C:\APP\AIME\ORADATA\ORCL\SYSAUX01.DBF
    input datafile file number=00003 name=C:\APP\AIME\ORADATA\ORCL\UNDOTBS01.DBF
    input datafile file number=00004 name=C:\APP\AIME\ORADATA\ORCL\USERS01.DBF
    input datafile file number=00005 name=C:\APP\AIME\PRODUCT\11.2.0\DBHOME_1\DATABA
    SE\TBS_5.F
    channel c1: starting piece 1 at 26-OCT-09
    released channel: c1
    RMAN-00571: ===========================================================
    RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
    RMAN-00571: ===========================================================
    RMAN-03009: failure of backup command on c1 channel at 10/26/2009 00:20:54
    ORA-19506: failed to create sequential file, name="CF_ORCL_20091026_s10p1t701223
    652", parms=""
    ORA-27028: skgfqcre: sbtbackup returned error
    ORA-19511: Error received from media manager layer, error text:
    sbt__rpc_cat_query: Query for piece CF_ORCL_20091026_s10p1t701223652 failed.
    (Oracle Secure Backup error: 'No such file or directory').
    Thanks,
    jun

    You can work entirely in Xcode by using the command-line tool template in C. Xcode > File > New > Project > Command-Line Tool > Next > Language: C > Next > Create.
    If you do want to work on the command line, you may as well just use the "clang" program instead. The "gcc" tool is just a compatibility tool for existing scripts that are expecting the actual "gcc" program. Apple hasn't used the real "gcc" for years. (Read up on the GPLv3 for more information.)
    The gcc/clang arguments are the same. The "-c" flag instructs the compiler to only compile a single .c file into a .o object file. It won't create an executable. If you are only compiling a single source file, just omit the "-c" flag and the compiler will create an executable named "a.out" that you can run by typing "./a.out". You can specify "-o <executable name>" if you want to specify a name. Once you get more than a handful of source files, using the terminal starts to become a hassle. At that point, you definitely want to start using Xcode.
    I'm not sure why you would try to compile "helloworlddot1.c" and then get an error message about "filename.c". Something else is wrong.
    If you are working in the Terminal, it is easiest to use the "cd" command to move into the same directory as your source files. Then you don't have to keep typing the full path.
    It is hard to say what the "best" community is. There are many to choose from.

  • Best Practises for Backup & Recovery windows

    Hi All,
    Could you please let me know the following .
    1. Best Practises to be followed for backup & recovery on windows server 2008
    2. how to plan for the DR on windows
    Regards
    Mohammed. Abdul Muqeet

    Mohammed Abdul Muqeet wrote:
    Hi All,
    Could you please let me know the following .
    1. Best Practises to be followed for backup & recovery on windows server 2008
    As far as the Oracle database is concerned, best practices on Windows server 2008 are exactly the same as for any other OS.
    http://docs.oracle.com/cd/E11882_01/backup.112/e10642/toc.htm
    (and my own prejudice, developed over 30+ years in this industry and working with Oracle on Windows beginning with Oracle 7.3 on windows 3.11, is that best practice is to stay as far away from Windows as possible)
    2. how to plan for the DR on windowsAs far as the Oracle database is concerned, best practices on Windows server 2008 are exactly the same as for any other OS.
    Backup everything. Get the backups off site. Perform regular DR drills. Document everything. Keep a copy of the documentation off site. (Doesn't do any good to have the DR manual located such that it gets destroyed in the same disaster that takes out your data center. ) Have an off-site DR site.
    While it isn't in your lane as a DBA, you need to keep reminding managment that DR is about more than just the database, and even more than just the data center itself. If there is a physical disaster (ask the people in Oklahoma City about that ... over the years - multiple F5 tornadoes, plus a truck bomb) all kinds of infrastructure and documentation issues. What about important records (like the DR manual) that exist only in someone's desk drawer? Where are the business units going to set up shop and how are they going to connect to the restored database at the DR site?
    I've seen DR manuals that got down to the detail of temporary housing for employees and how to get coffee at the DR site.
    >
    >
    Regards
    Mohammed. Abdul MuqeetEdited by: EdStevens on May 23, 2013 7:44 AM

Maybe you are looking for

  • Lenovo Yoga 2 13 - Screen going back to windows 8 Start page every 5 seconds

    Hello ! I've had for a few months this weird problem I find no solution for. In laptop mode, my screen randomly go back to the windows 8 start page while the laptop loudly vibrates. Even when I'm not touching the laptop it does so. I've searched for

  • IPhoto Library upgrade version won't import previous library

    So I have been reading past posts and have figured out how to locate my iphoto library. I have my originals & I can view them in Preview. However, I can't get them into iphoto, I get an error message. I also tried to re-import the whole library and I

  • Partitions on raid-array not recognized on boot

    Hey there, I already had my share of problems with my raid setup and kernel/udev updates, but this one is new: I have a raid1 setup with several partitions on the array which get recognized as /dev/md0p1, /dev/md0p2, etc. My root-device is on /dev/md

  • Data storage and aggregation levels

    Hi, I want to know, in facts and dimensions, where is data stored? Is it on multiple levels of aggregation? Or it does not depend from aggregation and it is stored at the lowest level? Thank you.

  • PB G4 17" doesn't recognize it is plugged in or charge battery

    My Powerbook G4 17" doesn't recognize it is plugged in (battery icon doesn't show "plugged in" icon) nor will it charge battery (down to 42%!). I live far from an Apple dealer and know no one else who has a Powerbook so I can borrow their cord. I hav