Standby in Noarchivelog mode

Hello,
Standby Redo Log must be archived before the redo data can be applied to the standby database. If we put our standby database in noarchivelog mode, then standby database does not generate any archive.Because of this Redo data wont apply to the standby database. Right? Is this the reason why we put standby database in archivelog mode?
Thanks

Hello;
Standby Redo Log must be archived before the redo data can be applied to the standby database.That statement is not correct.
If we put our standby database in noarchivelog mode, then standby database does not generate any archive. Because of this Redo data wont apply to the standby database. Right?That statement is not correct either. While Standby can use a process which is like generating archive, archive is really being transported from the Primary database.
Is this the reason why we put standby database in archivelog mode?Yes. If you switch modes the standby becomes the primary and needs to be in archivelog mode.
Failover
If you do a failover there are two main methods for recovery, RMAN and Flashback. You want your Standby database to be ready for use as a Primary, otherwise why have it? So you need to have it ready for anything including recovery.
I debated the archive question with somebody here last year. They claim the Standby produces Archive because such and such a process does this. I disagree. In Standby mode the database is not doing what a Primary mode database does. Those Oracle processes don't create new archive, they complete the transfer of archive from a Primary. The Sequence number was created on the Primary.
From Oracle document
"If all databases in a distributed database operate in ARCHIVELOG mode, you can perform coordinated distributed database recovery. However, if any database in a distributed database is in NOARCHIVELOG mode, recovery of a global distributed database (to make all databases consistent) is limited by the last full backup of any database operating in NOARCHIVELOG mode."
If you search this document
Data Guard Concepts and Administration 11g Release 2 (11.2) E10700-02
For "ARCHIVELOG" you get several hits.
If you search for "NOARCHIVELOG" you get none.
I suppose in theory you could run a Standby in "NOARCHIVELOG" but you gain nothing. If you ever have a switchover or failover you need to fix this ASAP. I see no reason to add that item to my checklist. It just an extra step and in the event of a failover one I could be very unhappy about.
Best Regards
mseberg
Edited by: mseberg on Mar 15, 2013 1:25 PM

Similar Messages

Logical standby in noarchive mode

Hello,
does anybody know if it is possible to run a logical standby (10gR2) in noarchivelog mode?
For my understanding it should be possible, why not... But I can't find a piece of documentation which prove this.
Thanks in advance,
Boris...

I also was curious if setting up a Logical Standby in noarchivelog mode was possible. It looks like it is...
We use this simply as a reporting copy of our data. Our analysts do not change any of this data. They just need it to be fairly current (~3 days). At this point, there isn't any need to generate archivelogs so we want to disable the feature to minimize our maintenance and our storage requirements.
STANDBY DB:
SQL> select log_mode, open_mode from v$database;
LOG_MODE     OPEN_MODE
ARCHIVELOG   READ WRITE
SQL> ALTER DATABASE STOP LOGICAL STANDBY APPLY;
Database altered.
SQL> shutdown immediate;
Database closed.
Database dismounted.
ORACLE instance shut down.
SQL> startup mount;
ORACLE instance started.
Database mounted.
SQL> alter database noarchivelog;
Database altered.
SQL> alter database open;
Database altered.
SQL> ALTER DATABASE START LOGICAL STANDBY APPLY IMMEDIATE;
Database altered.Then I created an object on the production server:
SQL> create table testuser.noarchivelog_testing as select * from dba_objects;
Table created.
SQL> alter system switch logfile;
System altered.
Mon Jun 22 11:13:26 2009
Beginning log switch checkpoint up to RBA [0xe6.2.10], SCN: 1031235046
Mon Jun 22 11:13:26 2009Now I see it on the standby:
Mon Jun 22 11:13:43 2009
RFS LogMiner: RFS id [25920] assigned as thread [1] PING handler
RFS[1]: Archived Log: '/oracle/LH1/oraarch/LH1arch_1_229_680639127.arc'
Mon Jun 22 11:13:46 2009
RFS LogMiner: Registered logfile [/oracle/LH1/oraarch/LH1arch_1_229_680639127.arc] to LogMiner session id [1]
Mon Jun 22 11:13:48 2009
LOGSTDBY status: ORA-16204: DDL successfully applied
Mon Jun 22 11:13:51 2009
LOGMINER: End mining logfile: /oracle/LH1/oraarch/LH1arch_1_229_680639127.arc
SQL> select count(*) from testuser.noarchivelog_testing;
COUNT(*)
     24444

Running a physical standby database in noarchivelog mode

Primary Database: 2 node rac cluster, 11.2.0.2 GI and RDBMS
Standby Database: single instance 11.2.0.2
OS: AIX 7.1
Hello,
I'm in the process of implementing a data guard standby system. To make this system simpler to admin, I want to run the standby database in NOARCHIVELOG mode. This standby is used only as a mirror of production (to be copied to a 3rd site for separate user activity) and will never be switched to active mode. Maintaining another set of archive logs seems to be redundant to me and another point of failure, so I want to disable archiving. I wanted to ask if any of the DG experts on the forums have ever had experience with this? Does anyone know if this is recommended? I've searched the Oracle Data guard documentation online... it says that the primary obviously needs to be in archive mode, but I'm not seeing anything specific about the standby. Please let me know if anyone has experience with this.
Thanks

Hello again;
If this is the case, then I have nothing to worry about here. Does that sound right to you?Yes.
For this :
b) monthly, shutdown this system and copy it to a 3rd site to host a separate set of business activityI would consider RMAN Duplicate in which case you may avoid the shutdown.
And for this :
resync the "mirror" with productionAll you have to do if DEFER the primary to the standby, then ENABLE and Data Guard will catch up.
--- Will post a detailed example here in a moment.
Right at the first of the year they wanted to work on our Primary server room ( Power ). What I did was switchover to the Standby but I kept log_archive_dest_state_2 on the new primary set to DEFER. Then I shutdown
all the databases at the Primary site. At the end of work two days later I started the databases at the Primary site in standby mode. Switched log_archive_dest_state_2 to ENABLE. When the databases were back in SYNC
I did another switchover and it was done. I used TAF and none of the users even noticed.
Best Regards
mseberg

Database in noarchivelog mode, truncate command issued

Database in noarchivelog mode, truncate command has been issued how to restore the table?
FACTS:-
1. DB In noarchivelog Mode
2. Cannot enable flash back mode because of 1. above
3. No exports available
4. No backup's Available.
Any thoughts ?

Oracle Support/ Professional Services has a Data Unloader (DUL) and ORA-00600 has DUDE, both of which may be able to extract information from data files that are corrupted, where the control files are lost, etc.
These are not, however, cheap utilities. Unless the data itself is really valuable, it is generally not a viable option.
Justin

Can't backup database in NOarchivelog mode

Hi there,
I get this error when I run this command from rman:
backup database
Starting backup at 19-JAN-11
using channel ORA_DISK_1
channel ORA_DISK_1: starting full datafile backupset
channel ORA_DISK_1: specifying datafile(s) in backupset
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03009: failure of backup command on ORA_DISK_1 channel at 01/19/2011 17:18:10
ORA-19602: cannot backup or copy active file in NOARCHIVELOG mode
please help.
Thanks in advance!

user13286861 wrote:
ok it finally shutdown cleanly.
I altered it in archivelog mode.
Now I can run a backup database command from rman?What does it cost to try it and see? What would be the worst thing that could possibly happen? An error message saying you can't do that?
And please note, this forum is not a chat line. Operators are NOT standing by. Posting a new message every two minutes to give an update on the fact that the database hasn't shut down yet is not necessary and not productive.
If there are a lot of pending transactions when you issue SHUTDOWN IMMEDIATE, they will all have to be rolled back as part of the shutdown. That can take some time. And if you bypass that with SHUTDOWN ABORT, they will have to be rolled back as part of instance crash recovery on the next startup, which will also take some time. Five minutes may feel like an eternity when you are sitting there waiting for your command to complete, but is no reason to panic.

How to set the database in NOARCHIVELOG mode

hellow world,
I knewly joined this organization.
Our database is very small < 4GB data.
Database is running in ARCHIVELOG MODE.
since we are not keeping any physical backup, so I opted to run the datbase in NOARCHIVELOG mode.
For bringing the database in NOARCHIVE MODE, I simply changed the init.ora parameter LOG_ARCHIVE_START = FALSE and restart the database.
offcourse the archiving stopped, but to my strange after 30 to 40 minutes my all log files filled an error message is being displayed to the server, saying
log files are filled, waiting for the archiving, Oh my God, What has happened, All users came to my head, DATABASE HANGED, NOT RESPONSING.
SIR, MY QUESTION IS
WHAT FOR ALL LOG FILES WAITING?
when i am saying NOARCHIEVE than
please explain me, where i committed mistake. I am new to ADMINISTRATION.

1. Not keeping any physical backup is all the more reason to stay in archivelog mode.
2. You need to shutdown the database, startup mount, and issue 'alter database noarchivelog', the alter database open.

Remove Standby/Read only mode for a database in sql server 2005

Hi,
I have a problem in sql sever . my database is showing standby/read-only mode. i want to remove that mode.please help me for the issue.

HI
Did you assign any DB read only user?
check the administrator guide in your SAP Business one->Documntation->system setup->Administrator guide...
but removing DB read only user is impossible.....

Back-up in noarchivelog mode

If running in NOARCHIVELOG mode, the script displays the following output:
Warning: Log archiving (ARCHIVELOG mode) is currently disabled. If
you restore the database from this backup, any transactions that take
place between this backup and the next backup will be lost. It is
recommended that you enable ARCHIVELOG mode before proceeding so
that all transactions can be recovered upon restore. See the section
'Enabling ARCHIVELOG Mode...' in the online help for instructions.
Backup with log archiving disabled will shut down and restart the
database. Are you sure [Y/N]?
i was wondering why will it be lost when i am going to make a current backup? I will obviously stop all transactions isn't it?

Case of archive log mode online redo log files dumped into archives. So let suppose you have full backup at morning 6 am.
If your database crashes around 8 am, you can restore 6 am backup and you option of recovery until 8am. So there is no data loss until you have archives.
Now we talk of noarchivelog mode, here online redo log files are not dumped because of noarchivelog mode of database.
You have backup at 6 am
Now the time is 8 am , your database crashed. Now you have to restore 6 am backup. Later there is no concept of recovery. It's just restore. Because you don't have archives to perform recovery.
So again archivelog mode depends on your business requirements.
Overall you have two hours of data loss in noarchivelog mode.
HTH.

ORA-01242: data file suffered media failure: database in NOARCHIVELOG mode

Hi All,
Need help from the gurus.
Currently we are in state unable to do anything.
Was using a database and all of a sudden it crashed. Tried to mount the database, open it, it failed. Also tried the recover and alter database open, even that failed. Errors are as follows.
Errors in file e:\oracle\product\10.2.0 \admin\devrevdb\bdump\devrevdb_p000_2620.trc:
ORA-00603: ORACLE server session terminated by fatal error
ORA-01242: data file suffered media failure: database in NOARCHIVELOG mode
ORA-00449: background process 'DBW0' unexpectedly terminated with error 1242
ORA-01242: data file suffered media failure: database in NOARCHIVELOG mode
In my spfile, the administrator has set only two control files and there is no mirroring and hence do not have another control file that will help me boot the db.
Please let me know how I should go about it. I am only a timebeing person trying to carryout a db activity. Any help would be of great help.

Hemant,
thanks for the reply.
I tried the way you suggested and it threw an error.
ORA-01145: offline immediate disallowed unless media recovery enabled
I searched and found that an additional tag of drop needs to be added to the command which you suggested.
ALTER DATABASE DATAFILE '<filename>' OFFLINE DROP.
i don't know what will the drop command have an effect ?
i have copied the data file to another location. Since i don't know much, i just want to be sure of what im doing.
if the above command is successfull, will it drop the datafile or the tablespace and i can no more use it. How can i use the copied datafile.
Thanks,
Sachin
I

Start database in NOARCHIVELOG mode

Hi,
I would like to know if there is a way to set some oracle paramete so that each time database is restarted, it comes up in NOARCHIEVELOG mode.
Regards,
Andrija

your answer is completelly wrong.
Please check description of log_archive_start parameter in documentation:
LOG_ARCHIVE_START
Parameter type
Boolean
Default value
false
Parameter class
Static
Range of values
true | false
Real Application Clusters
Multiple instances can have different values.
LOG_ARCHIVE_START is applicable only when you use the redo log in ARCHIVELOG mode. It indicates whether archiving should be automatic or manual when the instance starts up.
Values:
true
Indicates that archiving is automatic
false
Indicates that the database administrator will archive filled redo log files manually
The SQL*Plus statements ARCHIVE LOG START or ARCHIVE LOG STOP override this parameter.
In ARCHIVELOG mode, if all online redo log files fill without being archived, Oracle issues an error and suspends instance operations until the necessary archiving is performed. This delay is more likely if you use manual archiving. You can reduce its likelihood by increasing the number of online redo log files.
To use ARCHIVELOG mode while creating a database, set this parameter to true. Normally, a database is created in NOARCHIVELOG mode and then altered to ARCHIVELOG mode after creation.

Recover database in NOarchivelog mode :)

Hi all. How to recover a database wich is in noarchivelog mode? B-)
Suppose,
I have 3 redolog groups (with two members in each, the second members are located on another drive ). When first redo log group was 1/2 full I took a full backup. Then there were 2 switches from first to second and from second to third. Now the currnet redolog group - 3 (just started). At this point we faced media failer. How to roll forward changes using backup + online redologs?
Edited by: Junior Oracle DBA on Oct 16, 2008 1:53 PM

Restore your database cold backup (excluding redo logs).
Then issue this command :
RECOVER DATABASE USING BACKUP CONTROLFILE
provide the names of the last ACTIVE / CURRENT Redo Logs in the database when Oracle prompts for an ArchiveLog.
When Oracle has finished recovery to a consistent point in time, it will return to the command prompt without any error.
Now issue this command :
ALTER DATABASE OPEN RESETLOGS
You would have a Complete Recovery.
This is provided that Oracle had NOT cycled through all the Online Redo Logs since the time when the Cold Backup was taken. (If Oracle had cycled through all the Online Redo Logs, it would have overwrriten the oldest log because it wasn't in ArchiveLog mode).
Hemant K Chitale
http://hemantoracledba.blogspot.com

Changing database to noarchivelog mode during impdp

Hi Guys,
I am using Oracle Database 10g Enterprise Edition Release 10.2.0.5.0 - 64bit Production on RHEL5.
I am in the middle on the impdp and I want my database to run on noarchivelog as it creates a lot of archivelogs.
Will it be proper if I stop the import:
e.g Import> STOP_JOB=IMMEDIATE
and shutdown the database put the database on noarchivelog mode.
then opne database and
impdp hr/hr@mydb ATTACH=myfulljob Will these work fine?
Or should I execute:
alter system archive log stop;
Please Help !!!!!!!!!!!

Vinod Dhandapani wrote:
Running the database in Noarchivelog mode means you should be ready to lose data incase there is any crash. I would recommend you to change the size of the redologs so that it will not create frequent archivelogs. Which does nothing about the space required for the archivelogs. If you are generating redo at the rate of 1gb/hour, you will consume archivelog dest space at the rate of 1gb/hour. Doesn't matter if those files are 10mb each or 100mb each.
If space is the problem then use a shell script to move the archivelog to another location (Tape)....And hopefully that shell script is invoking rman to do the work, so that in the event of recovery, rman will know that backups were taken and where they are located.
>
Incase you want to convert the database from archivelog to noarchivelog, follow the steps provided in the following link.
http://racadmin.blogspot.com/2011/06/convert-archivelog-mode-to-noarchivelog.html
Thanks

ORA-19602: cannot backup or copy active file in NOARCHIVELOG mode

Hi All
Its my first time to use RMAN in our ERP EBSR12
our database version is 11g
Please help how to resolv and make successfully backup
RMAN> backup database;
Starting backup at 24-JAN-11
using channel ORA_DISK_1
channel ORA_DISK_1: starting full datafile backup set
channel ORA_DISK_1: specifying datafile(s) in backup set
RMAN-03009: failure of backup command on ORA_DISK_1 channel at 01/24/2011 11:18: 25
ORA-19602: cannot backup or copy active file in NOARCHIVELOG mode
continuing other job steps, job failed will not be re-run
channel ORA_DISK_1: starting full datafile backup set
channel ORA_DISK_1: specifying datafile(s) in backup set
including current control file in backup set
channel ORA_DISK_1: starting piece 1 at 24-JAN-11
channel ORA_DISK_1: finished piece 1 at 24-JAN-11
piece handle=/oracle/mybackup_db/PROD2/backupset/2011_01_24/o1_mf_ncnnf_TAG20110 124T111824_6msvw4cv_.bkp tag=TAG20110124T111824 comment=NONE
channel ORA_DISK_1: backup set complete, elapsed time: 00:00:03
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03009: failure of backup command on ORA_DISK_1 channel at 01/24/2011 11:18: 25
ORA-19602: cannot backup or copy active file in NOARCHIVELOG mode
RMAN>
Thanks

ORA-19602: cannot backup or copy active file in NOARCHIVELOG modeIs your database in archivelog or noarchivelog mode?
How to Turn Archiving ON and OFF [ID 69739.1]
Please also see these docs/links.
ORA-19602 Using RMAN to Backup Database [ID 246183.1]
COLD RMAN backup fails: Ora-19602 even after SHUTDOWN IMMEDIATE and STARTUP MOUNT [ID 373828.1]
Backup & Recovery
http://www.oracle.com/pls/db112/portal.portal_db?selected=14&frame=#backup_and_recovery
Thanks,
Hussein

ORA-01152 when restoring from RMAN backupset in NOARCHIVELOG mode

Hi all,
I got the error ORA-01152 when I tried restoring an Oracle 10g R1 database from an RMAN backupset into a new server. The error returned when it reached to the level of opening the database in resetlogs.
The database runs on NOARCHIVELOG mode and on Windows 2003 Server SP2 32-bit.
Following is what I did in RMAN:
set ORACLE_HOME=D:\oracle\product\10.1.0\db_1
set ORACLE_SID=DAWA
set PATH=D:\oracle\product\10.1.0\db_1\bin;%PATH%
cd %ORACLE_HOME%\bin
rman target sys/mypassword
Recovery Manager: Release 10.2.0.1.0 - Production on Tue Feb 13 00:36:55 2007
Copyright (c) 1982, 2005, Oracle. All rights reserved.
connected to target database (not started)
RMAN> startup nomount pfile=X:\temp\DawaPFILE.ORA
connected to target database (not started)
Oracle instance started
Total System Global Area 1048576000 bytes
Fixed Size 792200 bytes
Variable Size 551807352 bytes
Database Buffers 494927872 bytes
Redo Buffers 1048576 bytes
RMAN> restore controlfile from
'X:\temp\Flash_Rec\DAWA\AUTOBACKUP\2011_07_16\O1_
MF_S_756655133_7226R018_.BKP';
Starting restore at 19-JUL-11
allocated channel: ORA_DISK_1
channel ORA_DISK_1: sid=270 devtype=DISK
channel ORA_DISK_1: restoring controlfile
channel ORA_DISK_1: restore complete
output filename=D:\ORACLE\ORADATA\DAWA\CONTROL01.CTL
output filename=D:\ORACLE\ORADATA\DAWA\CONTROL02.CTL
output filename=D:\ORACLE\ORADATA\DAWA\CONTROL03.CTL
Finished restore at 17-AUG-11
alter database mount;
database mounted
catalog backuppiece 'X:\temp\PUMHJATD_1_1';
catalog backuppiece 'X:\temp\PTMHJ91Q_1_1';
/* Rename the Redologfiles,so that they can be created in new locations
the database is opened in resetlogs */
SQL>conn sys as sysdba
-- get registered files from SELECT * FROM V$LOGFILE
SQL> alter database rename file
'D:\ORACLE\PRODUCT\10.1.0\ORADATA\DAWA\REDO01.LOG' to
'X:\oracle\oradata\dawa\REDO01.LOG';
alter database rename file 'D:\ORACLE\PRODUCT\10.1.0\ORADATA\DAWA\REDO02.LOG'
to 'X:\oracle\oradata\dawa\REDO02.LOG';
alter database rename file 'D:\ORACLE\PRODUCT\10.1.0\ORADATA\DAWA\REDO03.LOG'
to 'X:\oracle\oradata\dawa\REDO03.LOG';
alter database rename file 'D:\ORACLE\PRODUCT\10.1.0\ORADATA\DAWA\REDO04.LOG'
to 'X:\oracle\oradata\dawa\REDO04.LOG';
alter database rename file 'D:\ORACLE\PRODUCT\10.1.0\ORADATA\DAWA\REDO05.LOG'
to 'X:\oracle\oradata\dawa\REDO05.LOG';
alter database rename file 'D:\ORACLE\PRODUCT\10.1.0\ORADATA\DAWA\REDO06.LOG'
to 'X:\oracle\oradata\dawa\REDO06.LOG';
alter database rename file 'D:\ORACLE\PRODUCT\10.1.0\ORADATA\DAWA\REDO07.LOG'
to 'X:\oracle\oradata\dawa\REDO07.LOG';
/* Now in RMAN: restore the datafiles
    to new locations and recover. */
RMAN> run{
set newname for datafile
'E:\ORACLE\PRODUCT\10.1.0\ORADATA\DAWA\UNDOTBS201' TO
'D:\oracle\oradata\dawa\UNDOTBS201';
set newname for datafile
'E:\ORACLE\PRODUCT\10.1.0\ORADATA\DAWA\UNDOTBS202' TO
'D:\oracle\oradata\dawa\UNDOTBS202';
restore database;
switch datafile all;
alter database open resetlogs;
.../* alter database open resetlogs returned the errors: */
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of alter db command at 08/18/2011 08:44:45
ORA-01152: file 2 was not restored from a sufficiently old backup
ORA-01110: data file 2: 'D:\ORACLE\ORADATA\DAWA\UNDOTBS206'Thanks in advance.

SYS @ DAWA> shutdown immediate
ORA-01109: database not open
Database dismounted.
ORACLE instance shut down.
SYS @ DAWA> startup mount
ORACLE instance started.
Total System Global Area 1048576000 bytes
Fixed Size                   792200 bytes
Variable Size             551807352 bytes
Database Buffers          494927872 bytes
Redo Buffers                1048576 bytes
Database mounted.
SYS @ DAWA> recover database using backup controlfile until cancel;
ORA-00279: change 329012 generated at 03/08/2005 16:24:46 needed for thread 1
ORA-00289: suggestion :
X:\ORACLE\ORADATA\FLASH_REC\DAWA\ARCHIVELOG\2011_08_18\O1_MF_1_6_%U_.ARC
ORA-00280: change 329012 for thread 1 is in sequence #6
Specify log: {<RET>=suggested | filename | AUTO | CANCEL}
ORA-00308: cannot open archived log
'X:\ORACLE\ORADATA\FLASH_REC\DAWA\ARCHIVELOG\2011_08_18\O1_MF_1_6_%U_.ARC'
ORA-27041: unable to open file
OSD-04002: unable to open file
O/S-Error: (OS 2) The system cannot find the file specified.
ORA-01547: warning: RECOVER succeeded but OPEN RESETLOGS would get error below
ORA-01152: file 1 was not restored from a sufficiently old backup
ORA-01110: data file 1: 'X:\ORACLE\ORADATA\DAWA\SYSTEM01.DBF'You can download the alert log from here:
http://ahmedbaraka.com/temp/alertdawa.log

Change Data Capture on a db in NoArchivelog mode

I am trying to test an implementation of CDC on a database in noarchivelog mode, but I'm not having much success. All the documentation I've read does not make it sound like it is required, but there are no guides on doing it. I am attempting to use the Asynchronous HotLog method on a 10.2 instance. The (first) error I am running into occurs after trying to create a change set via DMBS_CDC_PUBLISH.CREATE_CHANGE_SET:
ERROR at line 1:
ORA-00258: manual archiving in NOARCHIVELOG mode must identify log
ORA-06512: at "SYS.DBMS_CAPTURE_ADM_INTERNAL", line 121
ORA-06512: at line 1
ORA-06512: at "SYS.DBMS_CDC_PUBLISH", line 560
ORA-06512: at line 2

I'm afraid this is not possible!!!!

Standby in Noarchivelog mode

Similar Messages

Maybe you are looking for