Noarchivelog mode in oracle

Hello,
When I try to set my database in noarchivelog mode, it asks me to mount it and make sure its not open in any instance.
I have mounted it and this is the only oracle instance on the server, still it doesn't go in noarchivelog mode.
Please advise.
SQL> alter database mount;
alter database mount
ERROR at line 1:
ORA-01100: database already mounted
SQL> ALTER DATABASE NOARCHIVELOG;
ALTER DATABASE NOARCHIVELOG
ERROR at line 1:
ORA-01126: database must be mounted in this instance and not open in any
instance

Hi,
Try to use Brtools - 1. Instance Management - 3. Alter Database Instance - c- continue - 4. Set noarchivelog mode - 3. Force -
Database instance DBE will be remounted now with mode 'IMMEDIATE'
Now your database will be shut down and restart with noarchive log mode

Similar Messages

How to change the ARCHIVELOG / NOARCHIVELOG mode in Oracle 10g

Hi
how How to change the ARCHIVELOG / NOARCHIVELOG mode in Oracle10g in SQLPLUS ?
Many thanks.

Steps :
0 - change SPFILE
ALTER SYSTEM SET log_archive_dest = '/oracle9i/archive/tmpr' SCOPE =SPFILE;
ALTER SYSTEM SET log_archive_start = TRUE SCOPE =SPFILE;
ALTER SYSTEM SET log_archive_format = 'tmpr_%s.arc' SCOPE =SPFILE;
1 - shutdown immediate
2 - startup mount
3 - alter database archivelog;
4 - alter database open
Note : to verify if is ok type :
SQL> archive log list;

Oracle recovery in noarchivelog mode

Hello,
SAP Release : ECC6
Oracle 10G
Solaris 10g
Our SAP system is in noarchivelog mode (formation environnement, with frequent client copies).
We frequently perform an offline backup.
The solaris server that is hosting our Sap system, has been brutally shutdown this morning,
due to a network issue.
Afterwards, we had to restart the sap system.
A fisrt error occured ; inconsistency between the control files ...
ORA-00205: error in identifying control file, check alert log for more info
In alert log :
ORA-00202: control file: '/oracle/ZMA/origlogA/cntrl/cntlrZMA.dbf'
ORA-27037: unable to obtain file status
We regenerated a new control file and replaced it.
The error was solved.
Then a second error occured :
SQL> startup
ORACLE instance started.
Total System Global Area 1660944384 bytes
Fixed Size                  2268216 bytes
Variable Size             851207112 bytes
Database Buffers          805306368 bytes
Redo Buffers                2162688 bytes
Database mounted.
ORA-01589: must use RESETLOGS or NORESETLOGS option for database open
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/ZMA/sapdata1/system_1/system.data1'
SQL> recover database using backup controlfile until cancel ;
ORA-00279: change 647063400 generated at 04/28/2008 11:10:01 needed for thread
1
ORA-00289: suggestion : /oracle/ZMA/oraarch/ZMAarch1_76005_618576658.dbf
ORA-00280: change 647063400 for thread 1 is in sequence #76005
The redo log #76005 is no more available; I tried to apply the online redo logs, but it didn't help.
We had to restore the whole database from the offline backup.
1/ I still have problems understanding why Oracle is asking for a recovery, when we tried to reopen the database ? The database was consistent this morning, how is it that the file '/oracle/ZMA/sapdata1/system_1/system.data1' became inconsistent ?
2/ In sap note 863417 "If the database operates in NOARCHIVELOG mode, the database can ONLY be completely recovered from instance failure but not from media failure. "
What is exactly the difference between media failure and instance failure ?
Does a network problem and then a reboot of the host is considered a media failure ?
Best Regards.
thank you for your help .

> 1/ I still have problems understanding why Oracle is asking for a recovery, when we tried to reopen the database ? The database was consistent this morning, how is it that the file '/oracle/ZMA/sapdata1/system_1/system.data1' became inconsistent ?
Because the database was not shut down cleanly. An open database is by definition "inconsistent" without the proper logfiles.
> 2/ In sap note 863417 "If the database operates in NOARCHIVELOG mode, the database can ONLY be completely recovered from instance failure but not from media failure. "
> What is exactly the difference between media failure and instance failure ?
Media = File/Raw-Device. If you database is crashing due to a software error it can be recovered, if a file is corrupt it can't be (since you have no redo logs).
> Does a network problem and then a reboot of the host is considered a media failure ?
A corrupt control file (e. g.) is a media failure.
Markus

Anyone running Portal with NOARCHIVELOG mode in the Oracle DB?

Although we have several high-volume SQL Server customers running their DB in simple recovery mode (no transaction logging) with success, I am trying to determine if anyone is doing the equivalent with Oracle DB.
Even if you aren't using NOARCHIVELOG mode, please let me know your thoughts on performance, especially since the perception exists that the Portal is less performant on Oracle DB than on SQL Server. If that perception has any basis in reality, there should be an even greater potential for performance gain using Oracle DB, through intelligent tuning.
The cons of NOARCHIVELOG were pointed out to me by an excellent DBA:
1. Lose the ability to do hot online physically backup, (both RMAN and Manual)
2. Lose the ability to do point in time recovery of your database (irrelevant to the Portal)
3. When something bad happens to your DB, you are guaranteed to lose some data, because you can only recover to last good backup. (This is either acceptable to the business or not. Usually it is.)
Thanks for your thoughts!

There are no dumb questions. 'Better' or 'worse' can mean different things from different angles. I won't recommend something to a customer that I saw in an article somewhere, or gained knowledge via hearsay. I have to have tried it successfully with a customer, usually though iterative tuning, testing and monitoring cycles.
With that said, I see nothing wrong with using NOARCHIVELOG mode for the portal, and am looking to find someone with experience using it with the portal; and I don't mean a portal with four communities and a scant thousand users. I am looking for something more on the scale of our mutual customer who had about 15 front end portal servers, and about 15,000 hits per hour. Who, incidentally, is happily using SQL Server in simple recovery mode, and was game to try it out in the first place.

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

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

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

How to recover a PDB in noarchivelog mode?

Hi all,
Urgent! We have a PDB currently in mount stage after restoring and recovering from backup. Whenever I tried to open it or recover data file, I keep getting this error message:
Errors in file C:\ORACLE\diag\rdbms\us022348\us022348\trace\us022348_p000_8788.trc:
ORA-01113: file 9 needs media recovery
ORA-01110: data file 9: 'D:\ORADATA\12C\US022348\0FB7D663771D443E8DE2229B76E0DCA7\DATAFILE\O1_MF_USERS_B2TVTBL1_.DBF'
The CDB and PDB both are in noarchivelog modes.
Which command should I use to bring the database back?
Thanks!!

I tried these but no luck.
RMAN> alter pluggable database PDBNAME open;
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of sql statement command at 12/15/2014 14:10:49
ORA-01113: file 9 needs media recovery
ORA-01110: data file 9: 'D:\ORADATA\12C\US022348\0FB7D663771D443E8DE2229B76E0DCA7\DATAFILE\O1_MF_USERS_B2TVTBL1_.DBF'
RMAN> alter pluggable database PDBNAME open resetlogs;
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of sql statement command at 12/15/2014 14:11:05
ORA-39862: RESETLOGS option only valid after a Pluggable Database incomplete recovery

ORA-00258: manual archiving in NOARCHIVELOG mode must identify log

Hi I am new to oracle streams. I am trying to setup a one way replication from one database to another using Oracle 10g (10.2.0.1.0) on Windows XP SP3 (32 bit).
I ran the following proc as the streams admin schema:
begin
dbms_streams_adm.maintain_schemas(
schema_names => 'XXCOW',
source_directory_object => 'repl_exp_dir',
destination_directory_object => 'repl_imp_dir',
source_database => 'PWBSD',
destination_database => 'PDVSD',
perform_actions => true,
dump_file_name => 'exp_app23.dmp',
capture_queue_table => 'rep_capt_table',
capture_queue_name => 'rep_capt_queue',
capture_queue_user => NULL,
apply_queue_table => 'rep_dest_table',
apply_queue_name => 'rep_dest_queue',
apply_queue_user => NULL,
capture_name => 'capture_pubs',
propagation_name => 'prop_pubs',
apply_name => 'apply_pubs',
log_file => 'exp_app23.log',
bi_directional => false,
include_ddl => true,
instantiation => dbms_streams_adm.instantiation_schema);
end;
The script failed the first time because i forgot to configure the source database in archive log mode.
The steps i followed to change to archivelog mode:
SQL> select name from v$database;
NAME
PWBSD
SQL> alter system set LOG_ARCHIVE_DEST = 'D:\data\oracle\oradata\PWBSD\archive' scope=both;
System altered.
SQL> conn sys/sys@pwbsd as sysdba
Connected.
SQL> shutdown immediate
Database closed.
Database dismounted.
ORACLE instance shut down.
SQL> startup mount
ORACLE instance started.
Total System Global Area 612368384 bytes
Fixed Size 1250428 bytes
Variable Size 197135236 bytes
Database Buffers 406847488 bytes
Redo Buffers 7135232 bytes
Database mounted.
SQL> alter database archivelog;
Database altered.
SQL> alter database open;
Database altered.
SQL>
I configured it in archive log mode and ran the proc above again.
I got the following output this time:
job finished
begin
ERROR at line 1:
ORA-23616: Failure in executing block 90 for script
959ECF1D1159402A8C16687AE5E3B5CD
ORA-06512: at "SYS.DBMS_RECOVERABLE_SCRIPT", line 457
ORA-06512: at "SYS.DBMS_STREAMS_MT", line 2201
ORA-06512: at "SYS.DBMS_STREAMS_MT", line 7486
ORA-06512: at "SYS.DBMS_STREAMS_ADM", line 2624
ORA-06512: at "SYS.DBMS_STREAMS_ADM", line 2685
ORA-06512: at line 2
I ran the following to check the error:
select * from dba_recoverable_script_errors;
The output is:
SCRIPT ID: 959ECF1D1159402A8C16687AE5E3B5CD
BLOCK NUM: 90
ERROR_NUMBER: -258
ERROR_MESSAGE: ORA-00258: manual archiving in NOARCHIVELOG mode must identify log
ORA-06512: at "SYS.DBMS_RECO_SCRIPT_INVOK", line 129
ORA-06512: at "SYS.DBMS_STREAMS_RPC", line 358
It seemed like it was still complaining about archive log mode,
I verified that the PWBSD db is in archivelog mode by running the following:
select name, log_mode from v$database;
NAME: PWBSD
LOG_MODE: ARCHIVELOG
What could be the problem and how do i proceed to fix it?

Hi Parthiv,
The steps given by you is not clear.
please try to fallow the steps given in the below link. It may be helpful to you to setup schema level streams:
http://gssdba.wordpress.com/2011/04/20/steps-to-implement-schema-level-oracle-streams/
Thanks and Regards,
Satish.G.S
gssdba.wordpress.com

Recover a deleted record in NOARCHIVELOG mode?

Hello,
I'm running 10gR2 in NOARCHIVELOG mode and we do not take backups (please, let's not get into a discussion about this!).
I need to know if there is any possible way to recover a record once it has been deleted and a COMMIT has been issued? A user inserted two records in the database that they should not have, and I need to verify there is no possible way to recover those once they have been deleted.
Thank you,
Mimi

Mimi Miami wrote:
Ok so my UNDO_RETENTION parameter is set to 900...so 15 minutes after I delete the records they should not be querable using Flashback Query any longer, right?No,
UNDO_RETENTION is low threshold value of undo retention. Meaning, Oracle will try to keep at least that time before overwritten.
However, it's not gurranteed if not enough undo tablespace available, meaning it can be overwritten before the value is up if not enough undo tablespace to serve new transaction.
On the other-hand, it will not remove the undo record until it's overwritten, meaning the record could stay there for considerable amount of time if your database is not busy and undo tablespace is big.
http://download.oracle.com/docs/cd/B19306_01/server.102/b14237/initparams222.htm#REFRN10225
Not sure what's the intention to make your delete irreversible,
you could actually create table newtable as select .. from old_table where <except the two records>.
Drop the old table and rename new table.
purge the recycle bin of your database

Noarchivelog mode in oracle

Similar Messages

Maybe you are looking for