Oracle 10g - switch off archive logs

Hi,
I understand in oracle 10g, the following parameter is not longer available:
LOG_ARCHIVE_START=FALSE
Can i confirm that for now, only way to disable archive log is to execute the following command when in mount stage:
alter database noarchivelog;
There's not other parameter we can specify in pfile to disable it permantely?
thanks

You are correct. No other parameters.

Similar Messages

  • How can I turn off archive logs are being generated by system? (ugrent)

    Dear all,
    How can I turn off archive logs are being generated by system?
    Best Regards,
    Amy

    Sorry not to you @kamran its to OP.accidently it reply button pressed for you
    SQL> shutdown immediate
    Database closed.
    Database dismounted.
    ORACLE instance shut down.
    SQL> startup mount
    ORACLE instance started.
    Total System Global Area  171966464 bytes
    Fixed Size                   787988 bytes
    Variable Size             145750508 bytes
    Database Buffers           25165824 bytes
    Redo Buffers                 262144 bytes
    Database mounted.
    SQL> alter database noarchivelog
      2  /
    Database altered.
    SQL> Khurram

  • 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

  • Oracle 9i request wrong archive log name during recovery

    Hello all,
    I am facing a problem with a database 9i Enterprise Edition running on Windows 2003 Enterprise Edition environment. According to the customer, when he takes the database offline using MSCS to take an offline backup, the database crashes when he tries to put it back online... But here a strange thing happens... when the command RECOVER DATABASE is issued, it asks for the wrong archive log... for example:
    The actual sequence is 14322, but Oracle asks for the archive log SID_4322... (in this case we have to rename the original file SID_14322 to SID_4322). I don't understand why it asks for the archive incorrectly... I issued the command ARCHIVE LOG LIST and it says that the current thread is 14322 (which is correct)... every new archive is created with the correct name (SID_143XX)... why is it asking for an archive without the number 1 in this case? Rename all the files to recover a database is not very pleasent job... creating an script to do so is not a solution in my opinion, hehe. Thanks for your help in advance.
    Best regards,
    Bruno Carvalho
    Edited by: Bruno Carvalho on Jul 5, 2010 10:08 AM

    Hello Damorgan,
    MSCS = Microsoft Cluster Services (it's an MMC console). The backup strategy is very old, and they use BR*Tools script to create a job on ArcServe Brigstor, and then the backup is performed via backint. (It's an SAP ERP system, which should be backed up using BR*Tools). I checked the alert log and I think that the problem is the length of the archive log name (in the alert log it gives me the error below):
    ARCH: Warning. Log sequence in archive filename wrapped
    to fix length as indicated by %S in LOG_ARCHIVE_FORMAT.
    Old log archive with same name might be overwritten.
    Media Recovery Log E:\ORACLE\SID\SAPARCH\SIDARCH\SIDARCH_43454.DBF <- this should be SIDARCH_143454.DBF
    Now I'm looking for a parameter where I can set the length of the archives, your help would be very appreciated (and please let me know if I'm not going the right way).
    Best regards,
    Bruno Carvalho

  • Oracle recommended location for archive logs in  oracle 10g rac

    Hello All,
    We would like to know the oracle recommended location for the archive logs in oracle10g RAC .we are using ASM.
    Thanks...

    user4487322 wrote:
    thanks. Is it the recommended setting ,if we go for a DR setup?I mean archive logs in ASM.If you can use dataguard, the archivelog copy to the standby system would be handled by Oracle and it supports ASM.
    Just remember, what ever your strategy, the archivelogs must be in a SHARED location (where all nodes can read/write to this location.)

  • Oracle 10g R2 Database Redo Log Files

    I had 3 redo log files, each of size 50 MB. i added 3 more redo log files, each of size 250 MB.
    Database is running in archive mode, files are generating with different sizes like 44 MB and 240 MB, i need to know is this harm for database or not?
    to make all archive redo log files generation of equal size what should i do?
    Please guide

    Waheed,
    When the redo log switch willbe happening,oracle would be asking archiver to log that into the archive file.So in case you have any parameters set to make the switch happen at certain time,depending on the activity of teh database,the archive file size may vary.There is no harm wit the different sizes of the files.What matters is the transaction informaiton contained in them not their size.
    to make all archive redo log files generation of equal size what should i do?
    As mentioned by Syed, you can make the switch happen at a defined interval which will not ensure but still will be a step to make the archive files of the same size.But I shall say you should bother more about making sure that the files are available rather than their size.
    Aman....

  • Switching to Archive Log Mode

    If I have an application that hooks into an Oracle 8.1.7 database running in noarchive mode, would it be transparent to that application if I were to switch oracle to archive log mode? I can't think of anything that would require configuration changes for an application that connects via Net8 but just want to be somewhat sure.
    Stu

    I agree. However, if you have a problem with the archive like archive dest running out of space, or you forgetting to turn on auto archiving, the application will hang on a log switch. But, these are not problems caused by archivelog mode itself, but rather by improper configuration/administration.

  • Putting a Oracle RAC in  to archive log mode??

    Our RAC is a 10gR2 Three(3) node RAC with a SAN as the shared storage. cluster is installed on linux. at the moment the RAC is in noarchieve log mode.
    SQL> archive log list;
    Database log mode No Archive Mode
    Automatic archival Disabled
    Archive destination /u01/app/oracle/product/10.2.
    0/db_1/dbs/arch
    Oldest online log sequence 665
    Current log sequence 666
    we created raw partitions in SAN and use ASM to manage shared storage.
    when running DBCA at "specify locations for the database files to be created" step we selected "use oracle managed files" and gave database area = +DATA/
    then at choose the recovery options for the database" step we ticked specify flash recovery area and gave Flash Recovery AREA = +BACKUP/ and flash recovery area = 10240 MB. we didnt click "enable archiving" option. hence the RAC DB is in NOARCHIEVELOG mode.
    i found some guide to put RAC in archive log mode which i have given below....
    ALTER SYSTEM SET log_archive_start=TRUE SCOPE=spfile;
    ALTER SYSTEM SET log_archive_dest_1='location=/u01/oradata/MYSID/archive/' SCOPE=spfile;
    ALTER SYSTEM SET log_archive_format='arch_%t_%s.arc' SCOPE=spfile;
    Since we need to mount the database in exclusive mode we must also alter the following parameter:
    ALTER SYSTEM SET cluster_database=FALSE SCOPE=spfile;
    From the command line we can stop the entire cluster using:
    srvctl stop database -d MYSID
    With the cluster down we can connect to a single node and issue the following commands:
    STARTUP MOUNT;
    ARCHIVE LOG START;
    ALTER DATABASE ARCHIVELOG;
    ALTER SYSTEM SET cluster_database=TRUE SCOPE=spfile;
    SHUTDOWN IMMEDIATE;
    Notice that the CLUSTER_DATABASE parameter has been reset to it's original value. Since the datafiles and spfile are shared between all instances this operation only has to be done from a single node.
    From the command line we can now start the cluster again using:
    srvctl start database -d MYSID
    my main question is about the setting of
    ALTER SYSTEM SET log_archive_dest_1='location= ????? ' SCOPE=spfile;
    since i have set +BACKUP/ as the FRA during installation how should i define the location of log_archive_dest_1???
    many thanks in advance.
    regards
    Dilan

    many thanks for the replies
    will the command you posted send the archive logs to the "+BACKUP/" location in my SAN.
    if yes how does oracle know that USE_DB_RECOVERY_FILE_DEST = BACKUP/ in my SAN. or how do i set oracle to use BACKUP/ as the USE_DB_RECOVERY_FILE_DEST??
    im a newbie to RAC so pls bear with me. also at the moment i get the following outputs from my database.... pls note the bold part below, is the archive destination pointing to a location in my local server?
    SQL> archive log list;
    Database log mode No Archive Mode
    Automatic archival Disabled
    Archive destination            /u01/app/oracle/product/10.2.0/db_1/dbs/arch
    Oldest online log sequence 665
    Current log sequence 666
    SQL> show parameter db_recovery;
    NAME TYPE VALUE
    db_recovery_file_dest string
    db_recovery_file_dest_size big integer 0
    SQL> show parameter archive
    NAME TYPE VALUE
    archive_lag_target integer 0
    log_archive_config string
    log_archive_dest string
    log_archive_dest_1 string
    log_archive_dest_10 string
    log_archive_dest_2 string
    log_archive_dest_3 string
    log_archive_dest_4 string
    log_archive_dest_5 string
    log_archive_dest_6 string
    log_archive_dest_7 string
    NAME TYPE VALUE
    log_archive_dest_8 string
    log_archive_dest_9 string
    log_archive_dest_state_1 string enable
    log_archive_dest_state_10 string enable
    log_archive_dest_state_2 string enable
    log_archive_dest_state_3 string enable
    log_archive_dest_state_4 string enable
    log_archive_dest_state_5 string enable
    log_archive_dest_state_6 string enable
    log_archive_dest_state_7 string enable
    log_archive_dest_state_8 string enable
    NAME TYPE VALUE
    log_archive_dest_state_9 string enable
    log_archive_duplex_dest string
    log_archive_format string %t_%s_%r.dbf
    log_archive_local_first boolean TRUE
    log_archive_max_processes integer 2
    log_archive_min_succeed_dest integer 1
    log_archive_start boolean FALSE
    log_archive_trace integer 0
    remote_archive_enable string true
    standby_archive_dest string ?/dbs/arch

  • Oracle 10g ASM converting noarchive log to archive log

    DATABASE Details
    Oracle Database 10g Release 10.2.0.4.0 - 64bit Production
    PL/SQL Release 10.2.0.4.0 - Production
    CORE 10.2.0.4.0 Production
    TNS for 64-bit Windows: Version 10.2.0.4.0 - Production
    NLSRTL Version 10.2.0.4.0 - Production
    Mode
    Database log mode No Archive Mode
    Automatic archival Disabled
    Archive destination USE_DB_RECOVERY_FILE_DEST
    Oldest online log sequence 26269
    Current log sequence 26274
    SQL>
    TYPE :
    DW Batch Process
    Redo log groups
    6 groups with 2 files size each 2GB Aprx. 400gb redo log generates per day
    OS : WINDOWS 2008 SERVER
    Current Size
    SQL> select sum(bytes)/(1024*1024*1024) from v$datafile;
    SUM(BYTES)/(1024*1024*1024)
    1003.86945
    ASM Details
    SELECT GROUP_NUMBER,NAME FROM V$ASM_DISKGROUP;
    GROUP_NUMBER NAME
    1 KK_DATA
    SQL> SELECT dg.name AS diskgroup, SUBSTR(c.instance_name,1,12) AS instance,
    2 SUBSTR(c.db_name,1,12) AS dbname, SUBSTR(c.SOFTWARE_VERSION,1,12) AS software,
    3 SUBSTR(c.COMPATIBLE_VERSION,1,12) AS compatible
    4 FROM V$ASM_DISKGROUP dg, V$ASM_CLIENT c
    5 WHERE dg.group_number = c.group_number;
    DISKGROUP INSTANCE DBNAME SOFTWARE COMPATIBLE
    KK_DATA +asm         KK   10.2.0.4.0   10.2.0.0.0
    Currently DB in noarchive mode, Need to put in archive Mode
    What are additional precautions need to take in case of ASM for managing archive mode

    I would recommend creating a new ASM diskgroup and assign Flash recovery area to this group. This is part of ASM best practices as in case your Data diskgroup goes, you can use RMAN backups/archivelogs for recovery purpose.
    -Amit
    http://askdba.org/weblog/

  • Log Directories in Oracle 10g RAC environment

    Hi all,
    Would you please tell me in which directories, the following log files will be created, in a Oracle 10g RAC enviroment.
    evmd.log
    crsd.log
    ocssd.log
    Best Regards,
    Narayan

    U should try login as root and then type:
    find / -name nameoffileyouaresearchingfor
    This command will show You location of those files.

  • Firewall - switch off logging

    Hi
    Does anyone know how to switch off firewall logging now in Snow Leopard?
    I can't seem to find the setting in the security pane anymore.
    My system profiler is showing up logging as "no". But it's also saying no stealth mode either, but that is set to yes on my firewall settings pane.
    Firewall Logging: No
    Stealth Mode: No
    So I think the system profiler is displaying the wrong info... I would like to switch firewall logging off though!
    Cheers

    If you wish to turn off firewall logging while still enabling stealth mode, here is the file and key that must be changed:
    /Library/Preferences/com.apple.alf.plist
    <key>loggingenabled</key>
    <integer>0</integer>
    You can change it manually after converting the plist to text using plutil, and then change it back to binary. However, it's much easier to use the Property List Editor application, installed with xcode.
    See this thread [http://discussions.apple.com/message.jspa?messageID=10239354&tstart=0] for more details.
    Apparently the System Profiler misreports firewall status. There's an older dormant plist in /usr/libexec/ApplicationFirewall but that proved to not be the culprit. The console app will quickly confirm that the above change has taken effect, in spite of what system profiler says.

  • Tidying the list of archive logs in Oracle

    We have been using Archive Logging for a while but manually handle the purging of them. Since we restart our 9.2 Oracle DBs daily and perform backups (cold) daily, the archive logs are currently suitable for a day.
    However, in Oracle Enterprise Manager > Storage > Archive Logs, we see the entire list (history) of archive logs.
    Can this be tidied and how?
    Thanks

    my mistake
    Problem Description:
    ====================
    When querying "v$loghist," the number of rows displayed is less than the total
    number of Redo Logs created by the database.
    Solution Description:
    =====================
    The quantity of Log History is driven by the internal parameter "maxloghistory".
    When creating a database you have the option to specify the "maxloghistory"
    parameter. The default value is OS dependent.
    In order to alter this parameter you need to re-create the controlfile and
    specify the "maxloghistory" parameter.
    Explanation:
    ============
    The setting for log history in the control file is set very low.
    The Log history is stored in the controlfile. When a database is created we
    specify how much Log history to store. Often, this setting is ignored or made
    small so the controlfile is not too large.
    References:
    ===========
    Oracle Server SQL Reference
    Note: there are some bugs about maxloghistory being ignored if you try to recreate your database.

  • Flashback Recovery area Full in Oracle 10g

    Before the flashback recovery area is full our
    Archive destination is USE_DB_RECOVERY_FILE_DEST
    Our DB_RECOVERY_FILE_DEST =/S01/app/oracle/flash_recovery_area/
    We got the Error:- ORA-00257
    Inorder to resolve the error we changed the log_archive_dest_1='/S01/app/oracle/db/archive'
    now the archive destination is changed to /S01/app/oracle/db/archive
    Archive logs getting generated in the above directory from now onwards.
    In the mean time i moved all the files from /S01/app/oracle/flash_recovery_area/
    to diff directory.
    But the below query gives still the space used is 3935.27 MB, where physically there are no files in /S01/app/oracle/flash_recovery_area/
    When will these values in the query update. Is there anything i have to do to reclaim the space 3935.27 MB (in the query below). Now after reclaiming the space, i want to use the Flash Back Recovery area (/S01/app/oracle/flash_recovery_area/) for the archive logs, like a switchback to where we are initially. How to reclaim the space ? How to switch back archive logs to Flash Back Recovery Area (/S01/app/oracle/flash_recovery_area/).
    Please the below report for the above conversation.
    Sat May 20 page 1
    Flash Recovery Area Status
    Space Space Reclm
    Limit Used Space
    File Name (MB) (MB) (MB) Files
    /S01/app/oracle/flash_recovery_a 4000.00 3935.27 3935.27 90
    rea
    Experts share your experience. Appreciate your reply in this regard..........
    Thanks

    In UNIX style environments you often don't see reclaimed space until the database is restarted. Backup the database and archivelogs and the flashback area shoudl take care of itself in future. If not, you can always delete obsolete archivelogs manually by using the DELETE command in RMAN.
    To cleanup now, first you must tell RMAN that the files you've moved are no longer available:
    crosscheck archivelog all;
    You can then delete the obsolete archivelogs using the following RMAN command:
    delete obsolete;
    I'm assuming you use RMAN for all your backups :)
    Cheers
    Tim...

  • Archive logs cutting early

    Hello, I have a 11g 11.1.0.7 database running on Windows Server 2003 64bit. This is a new server and database that will be replacing our 10g 32bit system. Everything is running fine on it, the only weird thing I have noticed is that the Redo logs cut early. I have them set to 50mb and they seem to always cut at 25mb. Once in a while I will get one that is around 44mb. I do not have the ARCHIVE_LAG_TARGET parameter set. I am confused as to why I can only get 25mb into an Archive log. I have Automatic Memory Management enabled and the Maximum Memory size is set to 15gb. I also have Large Page support enabled.
    On my current 10g server, the archive logs are being cut about every 5 minutes and I am trying to set this new server to cut 1 or 2 an hour. Having these logs cut early is making it difficult to determine what size Redo logs I need. I guess I could set them to a much larger size and then set the ARCHIVE_LAG_TARGET parameter to cut every 60 minutes but I want to make sure something isn't set incorrectly to cause the early cut of the Redo log. My Redo Buffer size is 61665280 bytes when I check "Show SGA". Any help with this would be appreciated.

    I checked the Archive_Lag_target parameter again and it is set to '0'. There is not much activity on the database right now since people don't start training on it until next week so it looks like it cuts an archive log just under 4 hours apart. When I was upgrading the database with our 10g data I had it in archive mode and it was cutting 25mb logs every few minutes since I was putting a pretty heavy load on it. I have never seen this behavior before, I am hoping my vendor who we get our Oracle support through puts in a SR with Oracle. Unfortunately I can't get direct support from Oracle.
    Could Automatic Memory Management have anything to do with it? This is the only real difference between my 10g and 11g databases that I can think of. I also have set a much larger SGA/PGA than my 10g database.

  • Two copies archive logs with only one defined

    Hi,
    On a 11g database, I have only got flash_recovery_area defined. When switched into archive log mode, I have expected only one copy of archive logs produced in the defined USE_DB_RECOVERY_FILE_DEST location, but there is another copy generated as well under $ORACLE_HOME/dbs directory. How to explain that? and how to DISABLE the second copy to be produced?
    Thanks for any help
    Zhuang Li
    PS: more info
    In spfile:
    orcl.__java_pool_size=50331648
    orcl.__large_pool_size=16777216
    orcl.__oracle_base='/usr/oracle11g'#ORACLE_BASE set from environment
    orcl.__pga_aggregate_target=1828716544
    orcl.__sga_target=1056964608
    orcl.__shared_io_pool_size=0
    orcl.__shared_pool_size=654311424
    orcl.__streams_pool_size=0
    *.audit_file_dest='/usr/oracle11g/admin/orcl/adump'
    *.audit_trail='db'
    *.compatible='11.1.0.0.0'
    *.control_file_record_keep_time=30
    *.control_files='/db/orcl1/control0^@^@C^AC"^@^@^@^@^@^C^@^@^@^@^@^@^A^D{^S^@^@1.ctl','/db/orcl1/control02.ctl',
    '/db/orcl1/control03.ctl'
    *.db_block_size=8192
    *.db_domain=''
    *.db_name='orcl'
    *.db_recovery_file_dest='/usr/oracle11g/flash_recovery_area'
    *.db_recovery_file_dest_size=6442450944
    *.diagnostic_dest='/usr/oracle11g'
    *.dispatchers='(PROTOCOL=TCP) (SERVICE=orclXDB)'
    *.job_queue_processes=5
    *.open_cursors=300
    *.pga_aggregate_target=1824522240
    *.processes=150
    *.remote_login_passwordfile='EXCLUSIVE'
    *.sga_max_size=1258291200#internally adjusted
    *.sga_target^@^@C^AC"^@^@^@^@^@^D^@^@^@^@^@^@^A^DCS^@^@=1056964608
    *.undo_tablespace='UNDOTBS1'
    ==============================
    SQL> select destination from V$ARCHIVE_DEST;
    DESTINATION
    /usr/oracle11g/R1/dbs/arch
    USE_DB_RECOVERY_FILE_DEST
    10 rows selected.
    SQL> SQL> archive log lis
    SP2-0718: illegal ARCHIVE LOG option
    SQL> archive log list
    Database log mode Archive Mode
    Automatic archival Enabled
    Archive destination USE_DB_RECOVERY_FILE_DEST
    Oldest online log sequence 2549
    Next log sequence to archive 2551
    Current log sequence 2551
    SQL>
    ===================
    SQL> show parameter archive
    NAME TYPE VALUE
    archive_lag_target integer 0
    log_archive_config string
    log_archive_dest string
    log_archive_dest_1 string
    log_archive_dest_10 string
    log_archive_dest_2 string
    log_archive_dest_3 string
    log_archive_dest_4 string
    log_archive_dest_5 string
    log_archive_dest_6 string
    log_archive_dest_7 string
    log_archive_dest_8 string
    log_archive_dest_9 string
    log_archive_dest_state_1 string enable
    log_archive_dest_state_10 string enable
    log_archive_dest_state_2 string enable
    log_archive_dest_state_3 string enable
    log_archive_dest_state_4 string enable
    log_archive_dest_state_5 string enable
    log_archive_dest_state_6 string enable
    log_archive_dest_state_7 string enable
    log_archive_dest_state_8 string enable
    log_archive_dest_state_9 string enable
    log_archive_duplex_dest string
    log_archive_format string %t_%s_%r.dbf
    log_archive_local_first boolean TRUE
    log_archive_max_processes integer 4
    log_archive_min_succeed_dest integer 1
    log_archive_start boolean FALSE
    log_archive_trace integer 0
    standby_archive_dest string ?/dbs/arch

    This is the way 11g install sets up the archive destination intially after creating the database using DBA.
    What you can do is to go to the Recovery Settings in Enterprise Manager. You would notice that Archive Log Destination number 1 is set to usr/oracle11g/R1/dbs/arch while number 10 is set to USE_DB_RECOVERY_FILE_DEST
    Remove the entry for Number 1 (leave it blank). Apply the settings. This will force Oracle to only log to flash_recovery_area.
    <br>
    Oracle Database FAQs
    </br>

Maybe you are looking for