XE Failed Backup - Unknown log mode : SP2-0640:.

All,
When attempting to backup my Oracle XE db using the shortcut in the Programs menu, I am getting the following error:
==================== ERROR =============================
Backup of the database failed.
Unknown log mode : SP2-0640:.
Log file is at SP2-0640:.
==================== ERROR =============================
Press any key to continue . . .
...I tried looking at the OXE_BACKUP_CURRENT.LOG to see if there was a current error thrown. However, there was not.
....By looking at other posts regarding this error, one person suggesting changing the backup.bat for every line that states "echo connect / as sysdba;"...
to "echo connect sys/password as sysdba;"
When I do that, I get the following dump in the OXE_BACKUP_CURRENT.LOG file...
Recovery Manager: Release 10.2.0.1.0 - Production on Fri Sep 28 09:27:18 2007
Copyright (c) 1982, 2005, Oracle. All rights reserved.
Windows Server 2003 Version V5.2 Service Pack 2
CPU : 2 - type 586, 1 Physical Cores
Process Affinity : 0x00000000
Memory (Avail/Total): Ph:1417M/3071M, Ph+PgF:1856M/4219M, VA:2000M/2047M
Starting with debugging turned off
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-00554: initialization of internal recovery manager package failed
RMAN-04005: error from target database:
ORA-01031: insufficient privileges
More info....
I am logged in as an administrator in the ORA_DBA group.
{PR}

I am logged in as an administrator in the ORA_DBA group.With this you mean: user is member of the ORA_DBA group, or?

Similar Messages

  • Backup of the database failed Showing: Unknown log mode : SP2-0640:.

    In Oracle Express Edition 10g:
    When I try to create a backup I get the following:
    ==================== ERROR =============================
    Backup of the database failed.
    Unknown log mode : SP2-0640:.
    Log file is at SP2-0640:.
    ==================== ERROR =============================
    Press any key to continue . . .
    What may be the reason and whats the solution
    Thanks,
    Vishal.

    Hi all,
    I had the exact same problem
    the backup menu item runs :
    C:\oraclexe\app\oracle\product\10.2.0\server\BIN\backup.bat
    when you look at this batchfile you will see the following :
    The script assumes that user can connect using "/ as sysdba"when you have OS authentication disabled the batchfile will give the formentioned error
    turn OS authentication back on by changing C:\oraclexe\app\oracle\product\10.2.0\server\NETWORK\ADMIN\sqlnet.ora
    (you could turn it back off after your backup succeeded)
    grtz
    Martin

  • COLD BACKUP을 받은 후 ARCHIVE LOG로 변환하여 사용한 경우 INCOMPLETE RECOVERY.

    제품 : ORACLE SERVER
    작성날짜 : 2002-04-09
    COLD BACKUP을 받은 후 ARCHIVE LOG로 변환하여 사용한 경우 INCOMPLETE RECOVERY.
    ======================================================================
    PURPOSE
    COLD BACKUP을 받은 후 ARCHIVE LOG MODE로 변환하여 사용한 경우의 RECOVERY
    과정을 TEST로 확인하여 본다.
    Examples
    No Archive log mode.
    SQL> select * from tab ;
    TNAME TABTYPE CLUSTERID
    EMP TABLE
    EMP1 TABLE
    EMP2 TABLE
    EMP3 TABLE
    EMP4 TABLE
    10 rows selected.
    SQL> select count(*) from emp3 ;
    COUNT(*)
    0
    SQL> select count(*) from emp4 ;
    COUNT(*)
    0
    Cold backup을 받은후 Archive log mode 변경한 경우
    SVRMGR> startup mount
    SVRMGR> archive log list
    Database log mode No Archive Mode
    Automatic archival Enabled
    Archive destination D:\Oracle\oradata\SNAP\archive
    Oldest online log sequence 26
    Current log sequence 28
    SVRMGR> alter database archivelog ;
    SVRMGR> alter database open ; => archive log mode 변경.
    SQL> select * from tab ;
    TNAME TABTYPE CLUSTERID
    EMP TABLE
    EMP1 TABLE
    EMP2 TABLE
    EMP3 TABLE
    EMP4 TABLE
    10 rows selected.
    SQL> insert into emp3 select * from emp ;
    14 rows created.
    SQL> commit ;
    Commit complete.
    SQL> insert into emp4 select * from emp1 ;
    71680 rows created.
    SQL> commit ;
    Commit complete.
    SQL> select count(*) from emp3 ;
    COUNT(*)
    14
    SQL> select count(*) from emp4 ;
    COUNT(*)
    71680
    ## log switch 발생.
    SVRMGR> alter system switch logfile ;
    SQL> insert into emp3 select * from emp ; -- current log에 반영.
    14 rows created.
    SQL> commit ;
    SQL> select count(*) from emp3 ;
    COUNT(*)
    28
    SQL> select count(*) from emp4 ;
    COUNT(*)
    71680
    # ALL DATABASE CRASH #
    # recover 과정... #
    1. Restore Cold-backup
    2. modify initSID.ora
    log_archive_start = true
    log_archive_dest_1 = "location=D:\Oracle\oradata\SNAP\archive"
    log_archive_format = %%ORACLE_SID%%T%TS%S.ARC
    3. svrmgrl
    Statement processed.
    SVRMGR> startup mount
    ORACLE instance started.
    Total System Global Area 40703244 bytes
    Fixed Size 70924 bytes
    Variable Size 23777280 bytes
    Database Buffers 16777216 bytes
    Redo Buffers 77824 bytes
    Database mounted.
    SVRMGR> archive log list
    Database log mode No Archive Mode
    Automatic archival Enabled
    Archive destination D:\Oracle\oradata\SNAP\archive
    Oldest online log sequence 26
    Current log sequence 28
    SVRMGR> alter database archivelog ;
    Statement processed.
    SVRMGR> recover database using backup controlfile until cancel ;
    ORA-00279: change 340421 generated at 04/29/2001 23:42:20 needed for thread 1
    ORA-00289: suggestion : D:\ORACLE\ORADATA\SNAP\ARCHIVE\SNAPT001S00028.ARC
    ORA-00280: change 340421 for thread 1 is in sequence #28
    Specify log: {<RET>=suggested | filename | AUTO | CANCEL}
    Log applied.
    ORA-00279: change 340561 generated at 04/29/2001 23:47:29 needed for thread 1
    ORA-00289: suggestion : D:\ORACLE\ORADATA\SNAP\ARCHIVE\SNAPT001S00029.ARC
    ORA-00280: change 340561 for thread 1 is in sequence #29
    ORA-00278: log file 'D:\ORACLE\ORADATA\SNAP\ARCHIVE\SNAPT001S00028.ARC' no longe
    r needed for this recovery
    Specify log: {<RET>=suggested | filename | AUTO | CANCEL}
    Log applied.
    ORA-00279: change 340642 generated at 04/29/2001 23:47:35 needed for thread 1
    ORA-00289: suggestion : D:\ORACLE\ORADATA\SNAP\ARCHIVE\SNAPT001S00030.ARC
    ORA-00280: change 340642 for thread 1 is in sequence #30
    ORA-00278: log file 'D:\ORACLE\ORADATA\SNAP\ARCHIVE\SNAPT001S00029.ARC' no longe
    r needed for this recovery
    Specify log: {<RET>=suggested | filename | AUTO | CANCEL}
    Log applied.
    ORA-00279: change 340723 generated at 04/29/2001 23:47:40 needed for thread 1
    ORA-00289: suggestion : D:\ORACLE\ORADATA\SNAP\ARCHIVE\SNAPT001S00031.ARC
    ORA-00280: change 340723 for thread 1 is in sequence #31
    ORA-00278: log file 'D:\ORACLE\ORADATA\SNAP\ARCHIVE\SNAPT001S00030.ARC' no longe
    r needed for this recovery
    Specify log: {<RET>=suggested | filename | AUTO | CANCEL}
    Log applied.
    ORA-00279: change 340797 generated at 04/29/2001 23:48:01 needed for thread 1
    ORA-00289: suggestion : D:\ORACLE\ORADATA\SNAP\ARCHIVE\SNAPT001S00032.ARC
    ORA-00280: change 340797 for thread 1 is in sequence #32
    ORA-00278: log file 'D:\ORACLE\ORADATA\SNAP\ARCHIVE\SNAPT001S00031.ARC' no longe
    r needed for this recovery
    Specify log: {<RET>=suggested | filename | AUTO | CANCEL}
    cancel
    Media recovery cancelled.
    SVRMGR> alter database open resetlogs ;
    Statement processed.
    SVRMGR>
    SQL> connect scott/tiger
    SQL> select count(*) from emp3 ;
    COUNT(*)
    14
    SQL> select count(*) from emp4 ;
    COUNT(*)
    71680
    # 결론...... #
    따라서 current log file에 기록된 14 row에 대한 부분은 recover가 될수
    없지만 archive log file에 적용된 log에 대한 data는 정상적으로 복구가
    가능하다.
    # 주의 사항 #
    cold backup을 restore한 후 database open후 shutdown 한 다음 archive
    log mode로 변경하여 recover를 진행하는 경우 SCN number가 변경되기
    때문에 ora-600 error가 발생하며 media recovery를 필요로 하기 때문에
    주의하여야 한다.
    SVRMGR> startup
    ORACLE instance started.
    Total System Global Area 40703244 bytes
    Fixed Size 70924 bytes
    Variable Size 23777280 bytes
    Database Buffers 16777216 bytes
    Redo Buffers 77824 bytes
    Database mounted.
    Database opened.
    SVRMGR> shutdown
    Database closed.
    Database dismounted.
    ORACLE instance shut down.
    SVRMGR> startup mount
    ORACLE instance started.
    Total System Global Area 40703244 bytes
    Fixed Size 70924 bytes
    Variable Size 23777280 bytes
    Database Buffers 16777216 bytes
    Redo Buffers 77824 bytes
    Database mounted.
    SVRMGR> alter database archivelog ;
    Statement processed.
    SVRMGR> recover database using backup controlfile until cancel ;
    ORA-00279: change 339542 generated at 04/29/2001 23:30:57 needed for thread 1
    ORA-00289: suggestion : D:\ORACLE\ORADATA\SNAP\ARCHIVE\SNAPT001S00003.ARC
    ORA-00280: change 339542 for thread 1 is in sequence #3
    Specify log: {<RET>=suggested | filename | AUTO | CANCEL}
    ORA-00283: recovery session canceled due to errors
    ORA-00600: internal error code, arguments: [3020], [8390146], [1], [3], [143], [
    240], [], []
    SVRMGR> exit
    Server Manager complete.
    Rederence Documents
    ---------------------

  • BACKUP failed to complete the command BACKUP DATABASE. Check the backup application log for detailed messages.

    Hi,
    We have a back up that is failing.
    The error is "BACKUP failed to complete the command BACKUP DATABASE RPS. Check the backup application log for detailed messages.".
    As I understand it the backup application log is at C:\Program Files\Microsoft SQL Server\MSSQL.2\MSSQL\LOG. From that all I get is
    2014-03-05 14:49:29.41 Backup      Error: 3041, Severity: 16, State: 1.
    2014-03-05 14:49:29.41 Backup      BACKUP failed to complete the command BACKUP DATABASE myDb. Check the backup application log for detailed messages.
    The command I am using is
    BACKUP DATABASE [MyDb]
    TO  DISK = N'D:\Domains\SQL_Backup\DB\myDb\Mydb_FullBackup_20140305_1100.bak'
    WITH NOFORMAT, NOINIT,  NAME = N'mydb-Full Database Backup', SKIP, NOREWIND, NOUNLOAD,  STATS = 10
    GO
    The database is Microsoft SQL Server Standard Edition (64-bit) Version 9.00.1399.06.
    The computer is Windows server 2003 R2 Standard Edition SP2
    The Db is 191 Gb and there is 227 Gb available on the D drive where it's being backed up to.
    Any thoughts as to how I can track down the problem.
    Is the 227Gb of spare disk space big enough to back up a 191 Gb database?
    If not how much is needed?
    Thanks

    Hello,
    Can you apply latest service pack .I dont know but guess that can be issue.Once faced ,not quite sure.Also can you just make your command like
    BACKUP DATABASE [MyDb]
    TO DISK = 'D:\Domains\SQL_Backup\DB\myDb\Mydb_FullBackup_20140305_1100.bak'
    WITH NOFORMAT, NOINIT, STATS = 10
    GO
    Just a simple one .Is backup failing immediately or after some time .Error is not so helpful as it does not shows any information
    Please mark this reply as the answer or vote as helpful, as appropriate, to make it useful for other readers

  • Transaction failed for unknown reason (100) Unable to complete backup at this time. Does anyone know how to solve this issue?

    Transaction failed for unknown reason (100) Unable to complete backup at this time. Does anyone know how to solve this issue?
    Thanks.

    The system is set up to backup files to the iCloud at the end of the day. This has ot happen for sometime now and the mesaage I get is the back up error.

  • HT201263 my ipad 2 3G crashed while playing an HD movie on iOS 7.1, then it enter into rcovery mode, i tried itunes restore and it fails showing unknown error (27), i retried for about 100 times with no benefit.... any ideas or help please

    my ipad 2 3G crashed while playing an HD movie on iOS 7.1, then it enter into recovery mode, i tried itunes restore and it fails showing unknown error (27), i retried for about 100 times with no benefit.... any ideas or help please???

    By the way, i am using Windows 7 x64 and updated itunes

  • Trying to log in using sqlplus /nolog and getting SP2-0640

    Hello, I searched for this problem but not having much luck. I have Oracle 9iR2 running on Solaris 9 workstation. I can log on giving sys/passwd as sysdba and log on using any other user accounts. What I can't do is get into sqlplus using /nolog. I am setting up a dataguard physical clone. The clone is another 9iR2 workstation and i just installed the RDBMS software without creating a database. I can go into this database with sqlplus /nolog. I cannot do this on my intended primary database. I remember being able to get into the database when i first set it up using sqlplus /nolog but have since changed the unix account password and i believe this caused it but when i change the password back to the same one when I created the database, it still does not work. The error I get is SP2-0640: Not connected. Is there a log I can look up that will give me more information? thanks,
    Jim

    Normally this errors occurs, if you have in glogin.sql (located in $ORACLE_HOME/sqlplus/admin) or login.sql statements,which require a working connection.
    Werner

  • RMAN backup in noarchived log mode

    Hi,
    can we take RMAN backup in noarchived log mode?
    If yes, how? just run backup database command or ?
    thanks

    You can use RMAN to backup a database in noarchivelog mode but you need to shutdown and mount the database. e.g.:
    rman target /
    RMAN> shutdown immediate
    RMAN> startup mount
    RMAN> backup database

  • Why we cannot take hot backup if database is in noarchive log mode

    Hi,
    I am aware that if database is in noarchive log mode, we cannot take hot backups and only cold backup is possible.
    I would like to know the technical reason behind this restriction?
    Thank You
    Sarayu

    Hot backups are fuzzy backups, inconsistent, in other words, since something is always happening in the database.  When you recover, you restore data files and then apply redo to make the transactions consistent.  You can do a complete recovery or recover to a point in time.  So where does the redo come from?  That's what we call archiving redo logs.  When the online redo gets full, it gets archived.
    In the case of an instance crash, the redo is there in the online redo logs, so Oracle can recover automatically.  Anything beyond that, having to do with storage media, is a media recovery, and requires those archived logs.  So unless you have some other way to get your data back, always run in archivelog mode.
    It is really important to understand the concepts.  Please read the docs.
    http://docs.oracle.com/cd/E11882_01/server.112/e25789/cncptdba.htm#CNCPT031
    http://docs.oracle.com/cd/E11882_01/backup.112/e10642/rcmintro.htm#i1005488
    It may be worth your while to get a third party backup and recovery book too.

  • Backup with Exp,  Can  It used in DB with Archive Log Mode ??

    I need information about if When I activate Archive log mode in my database ,after This I will use all before backups with Exp in full,Table,user ...recovery mode .
    any advice are welcome
    thanks
    Jimmy

    If you are using archive log mode, you should back up your database by regularly backing up
    your data files. If you lose a tablespace due to a defecitve disk or need to do a point-in-time recovery due to a user error, you restore your latest copy (if doing point-in-time the latest copy before the
    user error) of the relevant data files an then roll forward using the archived log.
    You can not restore your database from an export and then roll forward using the archived
    logs.
    HTH
    Marcus Geselle

  • RMAN Restore Error - media recovery requesting unknown log: thread 1 seq 7

    Im using RMAN to copy a database to another server. The new server is IDENTICAL to the old one. By identical I mean it has the same sever name, ip address, operating system, Oracle version and directory structure.
    The new server already has the instance created, (same name as the old server instance, paths etc)
    The backup files have been manually restored to the new server, same locations as they were on the old one. ( RMAN did an automatic controlfile backup and also the archivelogs on the old server ).
    Ive restored the control file on the new server from the RMAN backup pieces.
    Ive catalogued the RMAN backup pieces on the new server.
    I know the last sequence available in the archivelogs backup by running on the new server :
    list backup of archivelog all;
    List of Backup Sets
    ===================
    BS Key Size Device Type Elapsed Time Completion Time
    5 14.43M DISK 00:00:03 11-MAY-11
    BP Key: 9 Status: AVAILABLE Compressed: NO Tag: TAG20110511T163502
    Piece Name: C:\ORACLE\PRODUCT\10.2.0\FLASH_RECOVERY_AREA\SAT\BACKUPSET\
    011_05_11\O1_MF_ANNNN_TAG20110511T163502_6WOC5833_.BKP
    List of Archived Logs in backup set 5
    Thrd Seq Low SCN Low Time Next SCN Next Time
    1 2 550217 10-MAY-11 556559 11-MAY-11
    1 3 556559 11-MAY-11 559776 11-MAY-11
    1 4 559776 11-MAY-11 560093 11-MAY-11
    1 5 560093 11-MAY-11 560794 11-MAY-11
    BS Key Size Device Type Elapsed Time Completion Time
    7 15.50K DISK 00:00:01 11-MAY-11
    BP Key: 10 Status: AVAILABLE Compressed: NO Tag: TAG20110511T163653
    Piece Name: C:\ORACLE\PRODUCT\10.2.0\FLASH_RECOVERY_AREA\SAT\BACKUPSET\
    011_05_11\O1_MF_ANNNN_TAG20110511T163653_6WOC8PMP_.BKP
    List of Archived Logs in backup set 7
    Thrd Seq Low SCN Low Time Next SCN Next Time
    1 6 560794 11-MAY-11 560851 11-MAY-11
    So far its all going swimmingly well.
    Now I want to restore the datafiles and recover. So I ran :
    RMAN run { restore database; recover database; alter database open resetlogs; }
    This gave me the output below which goes great but I get a final error, I think the error is because its looking for an archive log thats not in the backup set, but it should be. However, I think SCN 560851 is for a log that hadnt been created yet on the old server when the backup was ran ?
    How do I address resolving the error ? Its worth pointing out log, "archive log filename=C:\ORACLE\PRODUCT\10.2.0\FLASH_RECOVERY_AREA\SAT\ARCHIVELOG
    \2011_05_11\O1_MF_1_6_6WOK1X4W_.ARC recid=10 stamp=750881741" isnt on the old server either which is why its not in the backup set.
    I can do a alter database open reset logs but Id prefer to know why its failing.
    Any help would be much appreciated.
    RMAN> run { restore database; recover database; alter database open resetlogs; }
    Starting restore at 11-MAY-11
    using channel ORA_DISK_1
    channel ORA_DISK_1: starting datafile backupset restore
    channel ORA_DISK_1: specifying datafile(s) to restore from backup set
    restoring datafile 00001 to C:\ORACLE\PRODUCT\10.2.0\ORADATA\SAT\SYSTEM01.DBF
    restoring datafile 00002 to C:\ORACLE\PRODUCT\10.2.0\ORADATA\SAT\UNDOTBS01.DBF
    restoring datafile 00003 to C:\ORACLE\PRODUCT\10.2.0\ORADATA\SAT\SYSAUX01.DBF
    restoring datafile 00004 to C:\ORACLE\PRODUCT\10.2.0\ORADATA\SAT\USERS01.DBF
    channel ORA_DISK_1: reading from backup piece C:\ORACLE\PRODUCT\10.2.0\FLASH_REC
    OVERY_AREA\SAT\BACKUPSET\2011_05_11\O1_MF_NNNDF_TAG20110511T163507_6WOC5CM7_.BKP
    channel ORA_DISK_1: restored backup piece 1
    piece handle=C:\ORACLE\PRODUCT\10.2.0\FLASH_RECOVERY_AREA\SAT\BACKUPSET\2011_05_
    11\O1_MF_NNNDF_TAG20110511T163507_6WOC5CM7_.BKP tag=TAG20110511T163507
    channel ORA_DISK_1: restore complete, elapsed time: 00:00:55
    Finished restore at 11-MAY-11
    Starting recover at 11-MAY-11
    using channel ORA_DISK_1
    starting media recovery
    channel ORA_DISK_1: starting archive log restore to default destination
    channel ORA_DISK_1: restoring archive log
    archive log thread=1 sequence=6
    channel ORA_DISK_1: reading from backup piece C:\ORACLE\PRODUCT\10.2.0\FLASH_REC
    OVERY_AREA\SAT\BACKUPSET\2011_05_11\O1_MF_ANNNN_TAG20110511T163653_6WOC8PMP_.BKP
    channel ORA_DISK_1: restored backup piece 1
    piece handle=C:\ORACLE\PRODUCT\10.2.0\FLASH_RECOVERY_AREA\SAT\BACKUPSET\2011_05_
    11\O1_MF_ANNNN_TAG20110511T163653_6WOC8PMP_.BKP tag=TAG20110511T163653
    channel ORA_DISK_1: restore complete, elapsed time: 00:00:01
    archive log filename=C:\ORACLE\PRODUCT\10.2.0\FLASH_RECOVERY_AREA\SAT\ARCHIVELOG
    \2011_05_11\O1_MF_1_6_6WOK1X4W_.ARC thread=1 sequence=6
    channel default: deleting archive log(s)
    archive log filename=C:\ORACLE\PRODUCT\10.2.0\FLASH_RECOVERY_AREA\SAT\ARCHIVELOG
    \2011_05_11\O1_MF_1_6_6WOK1X4W_.ARC recid=10 stamp=750881741
    unable to find archive log
    archive log thread=1 sequence=7
    RMAN-00571: ===========================================================
    RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
    RMAN-00571: ===========================================================
    RMAN-03002: failure of recover command at 05/11/2011 18:15:42
    RMAN-06054: media recovery requesting unknown log: thread 1 seq 7 lowscn 560851
    RMAN>
    Edited by: user12173666 on 11-May-2011 10:28

    You need to do incomplete recovery i.e. to ask RMAN to restore/recover to some specific point in time. This is usually done with some UNTIL clause or SET UNTIL statement. Example in your case:
    SET UNTIL SEQUENCE 7;See http://download.oracle.com/docs/cd/B19306_01/backup.102/b14194/rcmsynta065.htm#RCMRF160.

  • Archive log mode in oracle 10g

    Hi,
    I would like to know the archive log mode in oracle 10g and I use this code in SQLPlus
    select log_mode from v$database
    But it displayed: "2" not : NOARCHIVELOG or ARCHIVELOG
    It displayed a number, not a String.
    How could I know this?
    Thanks

    Hi Paul
    Because I am a newbie in DBA Oracle so I got many difficulties.
    You are very kind to help me.
    So I have some more questions:
    1. when I executed this code, it always reported error:
    $ tmp=`${ORACLE_HOME}/bin/sqlplus -s / as sysdba << EOF
    set heading off feedback off;
    exit
    EOF`
    tmp='ERROR:
    ORA-01031: insufficient privileges
    SP2-0306: Invalid option.
    Usage: CONN[ECT] [logon] [AS {SYSDBA|SYSOPER}]
    where <logon> ::= <username>[<password>][@<connect_identifier>] | /
    SP2-0306: Invalid option.
    Usage: CONN[ECT] [logon] [AS {SYSDBA|SYSOPER}]
    where <logon> ::= <username>[<password>][@<connect_identifier>] | /
    SP2-0157: unable to CONNECT to ORACLE after 3 attempts, exiting SQL*Plus'
    so when I updated like this:
    tmp=`${ORACLE_HOME}/bin/sqlplus -s sys/syspass@db02 as sysdba <<EOF     
                   set heading off feedback off;
                   exit
                   EOF`
    It run correctly.
    2. With Paul's guide:
    Do not execute Oracle commands from root, execute them as oracle user. This works to me :
    $ tmp=`${ORACLE_HOME}/bin/sqlplus -s / as sysdba << EOF
    set heading off feedback off
    alter database backup controlfile to '${CONTROLFILE_DIR}/<file name>';
    alter database backup controlfile to trace;
    exit
    EOF`
    Of course CONTROLFILE_DIR must be set to a directory with write permission for oracle user.
    For ex: I have an Unix account: unix/unix
    and a Sys Oracle account: oracle/oracle
    I login with Unix acount (unix/unix) and call script file that contains above code.
    tmp=`${ORACLE_HOME}/bin/sqlplus -s oracle/oracle@db02 as sysdba <<EOF     
                   set heading off feedback off
                   alter database backup controlfile to '${CONTROLFILE_DIR}/backup_control.ctl';
                   alter database backup controlfile to trace;
                   exit
                   EOF`
    Unix report as following: Linux error: 13: Permission denied.
    CONTROLFILE_DIR directory is read,write,execute for account unix/unix.
    Of course CONTROLFILE_DIR must be set to a directory with write permission for oracle user. You mean I have to create a Unix user is the same to Oracle user so that Oracle user can have permission to write.
    Please guilde more detail.
    Thanks for your attention.
    Message was edited by:
    user481034

  • RECOVERY IN NOARCHIVE LOG MODE

    Dear all,
    Please help me in solving this recovery issue :
    My database is : oracle 8i server ent.edition
    database runs on windows 2000
    db confgiured in no archive logmode
    when I start the database today :
    am getting the following error :
    O/S-Error: (OS 23) Data error (cyclic redundancy check).'
    error 1242 detected in background process
    ORA-01242: data file suffered media failure: database in NOARCHIVELOG mode
    ORA-01114: IO error writing block to file 2 (block # 1936)
    ORA-01110: data file 2: 'c:\ORACLE\ORADATA\ORACLE\RBS01.DBF'
    ORA-27072: skgfdisp: I/O error
    OSD-04008: WriteFile() failure, unable to write to file
    O/S-Error: (OS 23) Data error (cyclic redundancy check).
    this tablespace rbs is defined only for rollback segments..
    since db in noarhicve log mode, I cant able to take the datafile offline.. I tried doing
    ALTER DATABASE RECOVER
    which resulted in the above error .
    I have valid 1 month old cold backup..
    when I try to drop the tablespace, it fails with the above error.. .
    Please guide me as this is the production database..
    Thanks in advance
    Please help me
    Kai

    Were you able to achieve a NORMAL or IMMEDIATE shutdown of the database ?
    In that case the Rollback segments are not required at startup.
    So,
    1 comment out the entry "rollback_segments=...(namesofrollbacksegments)"
    from the init.ora
    2. connect / as sysdba and STARTUP MOUNT;
    3. ALTER DATABASE DATAFILE '<filenameforRBS>' OFFLINE DROP ;
    4. ALTER DATABASE OPEN;
    Additional steps : CREATE ROLLBACK SEGMENT SYS_RBS01
    TABLESPACE SYSTEM;
    ALTER ROLLBACK SEGMENT SYS_RBS01 ONLINE;
    5. DROP TABLESPACE RBS ; (check the name of the tablespace)
    6. CREATE TABLESPACE RBS (or NEWRBS) DATAFILE ....
    7. CREATE ROLLBACK SEGMENT ........ and create multiple segments in
    the new RBS tablespace
    8. SHUTDOWN
    9. Edit init.ora to set the rollback segment names again
    10. STARTUP
    HOWEVER if your database shutdown was not normal or immediate but an
    abort, Oracle would try to do an Instance Recovery. In that case, you would
    need to use "_corrupted_rollback_segments" and may lose data consistency.
    Check MetaLink for notes on that. But first check your shutdown and see if
    you can follow the steps suggested by Sybrand and me.
    Added additional steps for SYS_RBS01 in the SYSTEM
    tablespace for any actions on the RBS tablespace.
    Message was edited by:
    Hemant K Chitale

  • Maxdb log mode

    hello experts,
          I need to change the log mode which is in "overwrite mode"
        currently. and increase LOG_IO_QUEUE size.
       how can i do it.
       our maxdb version is 7.6 and O/S linux 2.6.16
       plz suggest steps .
    thanks and regards

    Dear Kavitha,
    -> Please review the SAP notes::
                    869267        FAQ: MaxDB LOG area
         <  "35. Can the log area be overwritten cyclically without having to make a log backup?"
            "52. How large should the LOG_IO_QUEUE be when configured? " >
                 719652     Setting initial parameters for liveCache 7.5 or 7.6
                 819641     FAQ: MaxDB Performance
         If you are SAP customer, you are able to read the SAP notes.
    -> The MAXDB documentation also give you answers on the reported questions::
                http://maxdb.sap.com/documentation/ -> Open the SAP MaxDB 7.6 Library
                 ->  Glossary
              "Changing the Values of Database Parameters" at
                      http://maxdb.sap.com/doc/7_6/9b/e6dc41765b6024e10000000a1550b0/content.htm
              "Log Queue"
                    http://maxdb.sap.com/doc/7_6/23/c806c81e20f946a59a421e01c42c3b/content.htm
             < The new value of the LOG_IO_QUEUE parameter will be activated only after
                the database will be restarted from offline mode. >
              "Displaying and Changing Database Parameters" using DBMGUI tool at
                    http://maxdb.sap.com/doc/7_6/84/d8d198570411d4aa82006094b92fad/content.htm
    -> Please pay attention ::
          "Automatic overwrite of the log area without log backups is NOT    
               recommended for production operation. Since no backup history exists 
               for the following changes in the database, you cannot track transactions
               in the case of recovery. "    
          Run dbm command 'param_getexplain LOG_IO_QUEUE'.
              May be the log devspaces can be moved to a faster disk, to accelerate the physical log I/O.
    -> What is the version of the database? < Please also give the patch and build number >
         Why do you need to change the log mode which is in "overwrite mode"
          and increase the value of the database parameter LOG_IO_QUEUE?
    Thank you and best regards, Natalia Khlopina

  • Is the only way to import large amount of data and database objects into a primary database is to shutdown the standby, turn off archive log mode, do the import, then rebuild the standby?

    I have a primary database that need to import large amount of data and database objects. 1.) Do I shutdown the standby? 2.) Turn off archive log mode? 3.) Perform the import? 4.) Rebuild the standby? or is there a better way or best practice?

    Instead of rebuilding the (whole) standby, you take an incremental (from SCN) backup from the Primary and restore it on the Standby.  That way, if, for example
    a. Only two out of 12 tablespaces are affected by the import, the incremental backup would effectively be only the blocks changed in those two tablespaces (and some other changes in system and undo) {provided that there are no other changes in the other ten tablespaces}
    b. if the size of the import is only 15% of the database, the incremental backup to restore to the standby is small
    Hemant K Chitale

Maybe you are looking for