Online logs needed archiving

we have 10.2.0.4 on solaris 5.10
Instance hanged coz of this reason:
MED1 - Can not allocate log, archival required
Tue Aug 18 09:46:05 2009
Thread 1 cannot allocate new log, sequence 53164
All online logs needed archiving
so,we made the below change in the environment :
increased log_archive_max_process=10
increased redlogs form 300Mb to 500Mb with additional groups..
Please advise if this is the correct solution ?
Kai

MED1 - Can not allocate log, archival requiredIt seems that all the online redo logs are full and you need to empty them. This can happeen due to two reasons
1) archivelog destination is full
2)archiving is disabled although the database is in archive log mode
increased log_archive_max_process=10
increased redlogs form 300Mb to 500Mb with additional groups..
Please advise if this is the correct solution ?These solution will not help you. See if the sufficient empty space is there at log_archive_destination. If it is there it may happen that archive log files were removed by OS commands and database has no knowledge about the removal. In this case connect to RMAN and crosscheck archivelogs, delete the expired. This will let the database archive all redo logs once you execute the command 'ALTER SYSTEM SWITCH LOGFILE' . If enough space is not there backup the old archivelog and delete them as described above. If archiving is disabled the enable them executing the command 'ALTER SYSTEM set log_archive_dest_state_1=enable'
Rgds.

Similar Messages

All online logs needed archiving

"All online logs needed archiving"
I have the database in "archivelog" mode
alert file ..All online logs needed archiving
When adding a new schema should the archivelog be NO?
What am I to do here?

Check to make sure that you aren't running out of space in the archive log destination. Make sure that you have not sopped archiving because this will backup on you unless you take the database out of archive log mode.
What happens when you do archive log start?
archive log stop should only be used for a temporary stop.

Getting time when online log switches; archiver start, ends

Hi
I am using "Oracle Database 10g Release 10.2.0.2.0 - 64bit Production"
Is there a possibility to check the exact time
-when do online redo log switch
-when does Archiver start and finish his archiving online logs
I would like to tune archiver performance.
Thanks for answers
Groxy

In my current configuration I am getting a lot of "waits" (processes waiting form commit)
I would like to see if there is any relation of archiving process with "waits" in my application. Redo logs currently siwtch upto 6 times /hour. My ideas is to increase redo log size from 150MB to e.g 300MB and give archiver less priority, so there are no peaks, which consumes significant amount of disk I/O and the process of archiving will be spreaded.
Groxy

PMON process and ORACLE Instance - Cannot allocate log. Archival required

Hello there,
We are running Oracle RAC (9i) database with two nodes and Oracle Applications 11i.The operatiing system is solaris 5.8.
1.Recently while bouncing the db, i happen to see many PMON process get started up? is it a normal thing to see those process? what is actually happening?
oracle 14125 1 1 05:02:36 ? 18:46 ora_p007_CMWPROD1
oracle 14123 1 1 05:02:36 ? 21:33 ora_p006_CMWPROD1
oracle 14117 1 3 05:02:34 ? 30:58 ora_p003_CMWPROD1
oracle 14121 1 1 05:02:35 ? 18:56 ora_p005_CMWPROD1
oracle 5230 1 0 21:45:54 ? 0:11 ora_qmn0_CMWPROD1
oracle 5192 1 0 21:45:09 ? 0:07 ora_pmon_CMWPROD1
oracle 5194 1 0 21:45:09 ? 1:37 ora_diag_CMWPROD1
oracle 5196 1 0 21:45:09 ? 0:48 ora_lmon_CMWPROD1
oracle 5198 1 0 21:45:09 ? 2:15 ora_lmd0_CMWPROD1
oracle 5200 1 0 21:45:12 ? 7:51 ora_lms0_CMWPROD1
oracle 5202 1 0 21:45:13 ? 7:59 ora_lms1_CMWPROD1
oracle 5204 1 0 21:45:13 ? 0:06 ora_dbw0_CMWPROD1
oracle 5206 1 0 21:45:13 ? 0:17 ora_lgwr_CMWPROD1
oracle 5208 1 0 21:45:13 ? 0:53 ora_ckpt_CMWPROD1
oracle 5210 1 0 21:45:13 ? 0:11 ora_smon_CMWPROD1
oracle 5212 1 0 21:45:13 ? 0:00 ora_reco_CMWPROD1
oracle 5214 1 0 21:45:13 ? 0:06 ora_cjq0_CMWPROD1
oracle 5218 1 0 21:45:13 ? 0:00 ora_arc0_CMWPROD1
oracle 5220 1 0 21:45:13 ? 0:05 ora_arc1_CMWPROD1
oracle 5223 1 0 21:45:17 ? 0:17 ora_lck0_CMWPROD1
oracle 14113 1 1 05:02:33 ? 5:30 ora_p002_CMWPROD1
oracle 14109 1 0 05:02:33 ? 5:14 ora_p000_CMWPROD1
oracle 14119 1 1 05:02:34 ? 21:03 ora_p004_CMWPROD1
oracle 14111 1 1 05:02:33 ? 6:12 ora_p001_CMWPROD1
2.We happen to see some notifications like
"Oracle instance <xxx> - cannot allocate log -Archival required" in the alert log file and could see many log switches in a second in archival destination.
we have three members of log groups (two in each group) in one node and same on the other. Should we have to increase log_buffer_size or addition of redo log files is required?
the error messages:
ORACLE Instance xxxx - Can not allocate log, archival required
ARCH: Connecting to console port...
Thread 2 cannot allocate new log, sequence 55487
All online logs needed archiving
Current log# 12 seq# 55486 mem# 0: /dev/vx/rdsk/racdg/log12a
Current log# 12 seq# 55486 mem# 1: /dev/vx/rdsk/racdg/log12b
Fri Oct 10 21:47:45 2008
Completed checkpoint up to RBA [0xd8be.2.10], SCN: 0x0000.e6dcbc2a
Fri Oct 10 21:47:49 2008
ARC0: Completed archiving log 7 thread 2 sequence 55482
ARC0: Evaluating archive log 10 thread 2 sequence 55480
ARC0: Unable to archive log 10 thread 2 sequence 55480
Log actively being archived by another process
ARC0: Evaluating archive log 9 thread 2 sequence 55483
ARC0: Beginning to archive log 9 thread 2 sequence 55483
Any suggestions to overcome these errors would be helpful.
Thanks,
Balu.

Tux Dueñas wrote:
Bueno.
A nosotros nos apasado el error de que no se puede guardar los archive logs por falta de espacio en Disco. Eso pasa cuando algun proceso genera demasiadas ransacciones que necesitan ser escritas en los logs. Por esa razon se genera mucho archive log y se llena el espacio en disco.
Borra los archivelog mas viejos, y que ya los tengas en un backup y asi no habra problema te recomiendo tener un espacio en disco minimo de 50%I hope this is what you meant,
>
We apas the error that you can not save the archive logs for lack of space on disk. That happens when any process that generates too many ransacciones need to be written in the logs. For that reason much archive log is generated and fills the space.
Removes archivelog older, and those who already have a backup and there will be no problem so I recommend you have a disk space minimum of 50%
>
This is an international forum so to spread your message as far as possible, use a more universal language, English for example can be a good choice.
Cheers
Aman....

When occurs crash recovery,why use active online redo log not archived log?

If current redo log had archived, but it's still 'ACTIVE'. As we all know, archived log is just an archived copy of the current redo log which is still 'ACTIVE', they have the same data. But why use active online redo log not archived log for crash recovery?(I think, if crash recovery can use archived log, then whether the online redo log is 'ACTIVE' or not, it can be overwritten)
Quote:
Re: v$log : How redo log file can have a status ACTIVE and be already archived?
Hemant K Chitale
If your instance crashes, Oracle attempts Instance Recovery -- reading from the Online Redo Logs. It doesn't need ArchiveLogs for Instance Recovery.
TanelPoder
Whether the log is already archived or not doesn't matter here, when the instance crashes, Oracle needs some blocks from that redolog. Archivelog is just an archived copy of the redolog, so you could use either the online or achive log for the recovery, it's the same data in there (Oracle reads the log/archivelog file header when it tries to use it for recovery and validates whether it contains the changes (RBA range) in it what it needs).

Aman.... wrote:
John,
Are you sure that the instance recovery (not the media recovery) would be using the archived redo logs? Since the only thing that would be lost is the isntance, there wouldn't be any archived redo log generated from the Current redo log and the previous archived redo logs, would be already checkpointed to the data file, IMHO archived redo logs won't participate in the instance recovery process. Yep, shall watch the video but tomorrow .
Regards
Aman....
That's what I said. Or meant to say. If Oracle used archivelogs for instance recovery, it would not be possible to recover in noarchive log mode. So recovery relies exclusively on the online log.
Sorry I wasted your time, I'll try to be less ambiguous in future

Clone from standby ended in ARC: Cannot archive online log based on backup

Hi
I m into scenario where my prod db is in one data center and standby is in other data center.
Both are geographically separated. I have to get a copy of prod on to standby data center side.
Sending data over the network is taking long time either with duplicate db from active db or take backup and copy over standby side and restore it.
so i thought of duplicate db from standby db which is in same data center, using 11g RMAN duplicate from active standby command.
I have simulated scenario which is as below
oracle version 11.2.0.1
os version REHL 5.4
My procedure & parameter are as below.
on standby side from where i m copying (TARGET)
1) on standby
alter database recover managed standby db cancel;
2)alter database convert to snapshot standby;
which gave me
/u01/data/DGSTD/archive/1_152_750425930.dbf
/u01/data/DGSTD/archive/1_153_750425930.dbf
*/u01/data/DGSTD/archive/1_1_752604441.dbf*
*/u01/data/DGSTD/archive/1_2_752604441.dbf*
3) alter database open;
4) alter system switch logfile;
now from rman
RMAN> connect target sys/system@DGSTD
connect auxiliary sys/system@GGR
connected to target database: DGPRM (DBID=578436102)
RMAN>
connected to auxiliary database: NOTREAL (not mounted)
RMAN>
run{
allocate channel prmy1 type disk;
allocate channel prmy2 type disk;
allocate channel prmy3 type disk;
allocate channel prmy4 type disk;
allocate channel prmy5 type disk;
allocate auxiliary channel stby1 type disk;
duplicate target database to ggr from active database
spfile
parameter_value_convert='DGSTD','GGR','/u01/data/DGSTD/','/u01/data/ggr/'
set db_file_name_convert='/u01/oradata/DGSTD/','/u01/data/ggr/'
set log_file_name_convert='/u01/oradata/DGSTD/','/u01/data/ggr/'
set 'db_unique_name'='ggr'
set 'audit_file_dest'='/u00/app/oracle/admin/ggr/adump'
set 'sga_max_size'='140m'
set 'pga_aggregate_target'='28940697'
nofilenamecheck;
and when output of rman reaches up below
Starting backup at 31-MAY-11
channel prmy1: starting datafile copy
input datafile file number=00001 name=/u01/data/DGSTD/datafile/system01.dbf
channel prmy2: starting datafile copy
input datafile file number=00002 name=/u01/data/DGSTD/datafile/sysaux01.dbf
in alert log of clone db it gives massive error saying
ARC3: Cannot archive online log based on backup controlfile
ARC2: Cannot archive online log based on backup controlfile
ARC3: Cannot archive online log based on backup controlfile
ARC2: Cannot archive online log based on backup controlfile
and it fill up whole fs. and finally duplicate command throws error.
not sure what i m missing of inside duplicate command or is it valid to duplicate database from snapshot standby.
can somebody light on it please
Edited by: user12281508 on Jun 1, 2011 10:26 AM
Edited by: user12281508 on Jun 1, 2011 10:28 AM

duplicate target database to ggr from active database
spfile
parameter_value_convert='DGSTD','GGR','/u01/data/DGSTD/','/u01/data/ggr/'
set db_file_name_convert='/u01/oradata/DGSTD/','/u01/data/ggr/'
set log_file_name_convert='/u01/oradata/DGSTD/','/u01/data/ggr/'
set 'db_unique_name'='ggr'
set 'audit_file_dest'='/u00/app/oracle/admin/ggr/adump'
set 'sga_max_size'='140m'
set 'pga_aggregate_target'='28940697'
nofilenamecheck;
}I think you should use standby cluase as
DUPLICATE TARGET DATABASE TO dup1 FOR STANDBY FROM ACTIVE DATABASE;

Local capture only seems to process archived logs - not online logs

In Oracle 10g R2 I have set up a local capture and apply on a logical standby database. I am configured to capture table level changes with LOGFILE_ASSIGNMENT = IMPLICIT, but the capture process only seems to find changes when the local redo logs are archived. I read that local capture will try to read the online redo if it can and then resort to the archive log. I don't see anything on why the online redo couldn't be used (except if LOGFILE_ASSIGNMENT = EXPLICIT). I want the capture to read the online redo rather than waiting for an archive. Can you help me? The status of the capture shows "WAITING FOR REDO" until archive time.
-Nick

Anybody else ever experience this?

Cloning of database to same host give error, unable to re-create online log

clone the database to same host
oracle version: 9.2.0.5
os HP
target db: tardb
catlog catlog
auxiliary: auxbr
After running this script, I am getting error unable to re-create online log.
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of Duplicate Db command at 06/08/2009 23:17:38
RMAN-03015: error occurred in stored script Memory Script
RMAN-06136: ORACLE error from auxiliary database: ORA-00344: unable to re-create online log '/db/app/oracle/product/9.2.0.5/dbs/ /db
/redolog.001/catalog1/catalog1_log1.rdo'
ORA-27040: skgfrcre: create error, unable to create file
HP-UX Error: 2: No such file or directory
I tried to shutdown, and mount, recover with backup contorlfile until cancel. and open with reset logs ,
I am not able to make the copy of the database on same host.
Help is appreciated.
complete error log
oracle@dimondz{auxbr}/db/app/oracle/dba/sql> sqlplus '/as sysdba'
SQL*Plus: Release 9.2.0.5.0 - Production on Mon Jun 8 23:11:23 2009
Copyright (c) 1982, 2002, Oracle Corporation. All rights reserved.
Connected to an idle instance.
SQL> startup nomount pfile='/db/app/oracle/admin/catlog/pfile/initauxbr.ora';
ORACLE instance started.
Total System Global Area 219115512 bytes
Fixed Size 737272 bytes
Variable Size 83886080 bytes
Database Buffers 134217728 bytes
Redo Buffers 274432 bytes
SQL> create spfile from pfile='/db/app/oracle/admin/catlog/pfile/initauxbr.ora';
File created.
SQL> exit
Disconnected from Oracle9i Enterprise Edition Release 9.2.0.5.0 - 64bit Production
With the Partitioning option
JServer Release 9.2.0.5.0 - Production
oracle@dimondz{auxbr}/db/app/oracle/dba/sql>
oracle@dimondz{auxbr}/db/app/oracle/dba/sql> rman
Recovery Manager: Release 9.2.0.5.0 - 64bit Production
Copyright (c) 1995, 2002, Oracle Corporation. All rights reserved.
RMAN> connect catalog rman/rman@catlog
connected to recovery catalog database
RMAN> connect target sys/dimondz@tardb
connected to target database: tardb (DBID=3063303886)
RMAN> connect auxiliary sys/dimondz@auxbr
connected to auxiliary database: auxbr (not mounted)
RMAN>
RMAN> RUN
2> {
3> SET NEWNAME FOR DATAFILE 1 TO '/db/catalog1.001/oradata/system01.dbf';
4>
5> SET NEWNAME FOR DATAFILE 2 TO '/db/catalog1.001/oradata/undotbs01.dbf';
6>
SET NEWNAME FOR DATAFILE 3 TO '/db/catalog1.001/oradata/ptest01.dbf';
7> 8>
9> SET NEWNAME FOR DATAFILE 4 TO '/db/catalog1.001/oradata/users_01.dbf';
10>
11> SET NEWNAME FOR DATAFILE 5 TO '/db/catalog1.001/oradata/drsys_01.dbf';
12>
13> SET NEWNAME FOR DATAFILE 6 TO '/db/catalog1.001/oradata/qms_dat_01.dbf';
14>
15> SET NEWNAME FOR DATAFILE 7 TO '/db/catalog1.001/oradata/ultradat_01.dbf';
16>
17> SET NEWNAME FOR DATAFILE 11 TO '/db/catalog1.001/oradata/xmltbs_01.dbf';
18>
19> DUPLICATE TARGET DATABASE TO auxbr
20>
21> pfile=/db/app/oracle/admin/catlog/pfile/initauxbr.ora
22> logfile
23> ' /db/redolog.001/catalog1/catalog1_log1.rdo' size 5m,
24> ' /db/redolog.003/catalog1/catalog1_log2.rdo' size 5m,
25> ' /db/redolog.002/catalog1/catalog1_log3.rdo' size 5m;
26> }
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
Starting Duplicate Db at 08-JUN-09
allocated channel: ORA_AUX_DISK_1
channel ORA_AUX_DISK_1: sid=11 devtype=DISK
printing stored script: Memory Script
set until scn 229907626;
set newname for datafile 1 to
"/db/catalog1.001/oradata/system01.dbf";
set newname for datafile 2 to
"/db/catalog1.001/oradata/undotbs01.dbf";
set newname for datafile 3 to
"/db/catalog1.001/oradata/ptest01.dbf";
set newname for datafile 4 to
"/db/catalog1.001/oradata/users_01.dbf";
set newname for datafile 5 to
"/db/catalog1.001/oradata/drsys_01.dbf";
set newname for datafile 6 to
"/db/catalog1.001/oradata/qms_dat_01.dbf";
set newname for datafile 7 to
"/db/catalog1.001/oradata/ultradat_01.dbf";
set newname for datafile 11 to
"/db/catalog1.001/oradata/xmltbs_01.dbf";
restore
check readonly
clone database
executing script: Memory Script
executing command: SET until clause
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
Starting restore at 08-JUN-09
using channel ORA_AUX_DISK_1
channel ORA_AUX_DISK_1: starting datafile backupset restore
channel ORA_AUX_DISK_1: specifying datafile(s) to restore from backup set
restoring datafile 00001 to /db/catalog1.001/oradata/system01.dbf
restoring datafile 00002 to /db/catalog1.001/oradata/undotbs01.dbf
restoring datafile 00003 to /db/catalog1.001/oradata/ptest01.dbf
restoring datafile 00004 to /db/catalog1.001/oradata/users_01.dbf
restoring datafile 00005 to /db/catalog1.001/oradata/drsys_01.dbf
restoring datafile 00006 to /db/catalog1.001/oradata/qms_dat_01.dbf
restoring datafile 00007 to /db/catalog1.001/oradata/ultradat_01.dbf
restoring datafile 00011 to /db/catalog1.001/oradata/xmltbs_01.dbf
channel ORA_AUX_DISK_1: restored backup piece 1
piece handle=/dump/DBA/RMAN/tardb_bkup/db_tardb_f_04kgt77h tag=WHOLE_DATABASE_tardb params=NULL
channel ORA_AUX_DISK_1: restore complete
Finished restore at 08-JUN-09
sql statement: CREATE CONTROLFILE REUSE SET DATABASE "auxbr" RESETLOGS ARCHIVELOG
MAXLOGFILES 5
MAXLOGMEMBERS 5
MAXDATAFILES 100
MAXINSTANCES 1
MAXLOGHISTORY 907
LOGFILE
GROUP 1 ' /db/redolog.001/catalog1/catalog1_log1.rdo' SIZE 5242880 ,
GROUP 2 ' /db/redolog.003/catalog1/catalog1_log2.rdo' SIZE 5242880 ,
GROUP 3 ' /db/redolog.002/catalog1/catalog1_log3.rdo' SIZE 5242880
DATAFILE
'/db/catalog1.001/oradata/system01.dbf'
CHARACTER SET UTF8
printing stored script: Memory Script
switch clone datafile all;
executing script: Memory Script
datafile 2 switched to datafile copy
input datafilecopy recid=1 stamp=689037446 filename=/db/catalog1.001/oradata/undotbs01.dbf
datafile 3 switched to datafile copy
input datafilecopy recid=2 stamp=689037446 filename=/db/catalog1.001/oradata/ptest01.dbf
datafile 4 switched to datafile copy
input datafilecopy recid=3 stamp=689037446 filename=/db/catalog1.001/oradata/users_01.dbf
datafile 5 switched to datafile copy
input datafilecopy recid=4 stamp=689037446 filename=/db/catalog1.001/oradata/drsys_01.dbf
datafile 6 switched to datafile copy
input datafilecopy recid=5 stamp=689037446 filename=/db/catalog1.001/oradata/qms_dat_01.dbf
datafile 7 switched to datafile copy
input datafilecopy recid=6 stamp=689037446 filename=/db/catalog1.001/oradata/ultradat_01.dbf
datafile 11 switched to datafile copy
input datafilecopy recid=7 stamp=689037446 filename=/db/catalog1.001/oradata/xmltbs_01.dbf
printing stored script: Memory Script
set until scn 229907626;
recover
clone database
delete archivelog
executing script: Memory Script
executing command: SET until clause
Starting recover at 08-JUN-09
using channel ORA_AUX_DISK_1
starting media recovery
channel ORA_AUX_DISK_1: starting archive log restore to default destination
channel ORA_AUX_DISK_1: restoring archive log
archive log thread=1 sequence=3
channel ORA_AUX_DISK_1: restoring archive log
archive log thread=1 sequence=4
channel ORA_AUX_DISK_1: restored backup piece 1
piece handle=/dump/DBA/RMAN/tardb_bkup/db_arch_tardb_f_06kgt7ih tag=ARCHIVE_LOG_tardb_BACKUP params=NULL
channel ORA_AUX_DISK_1: restore complete
archive log filename=/oradump/oradata/catlog/arch/catlog-1231663410_1_3.arc thread=1 sequence=3
channel clone_default: deleting archive log(s)
archive log filename=/oradump/oradata/catlog/arch/catlog-1231663410_1_3.arc recid=1 stamp=689037447
archive log filename=/oradump/oradata/catlog/arch/catlog-1231663410_1_4.arc thread=1 sequence=4
channel clone_default: deleting archive log(s)
archive log filename=/oradump/oradata/catlog/arch/catlog-1231663410_1_4.arc recid=2 stamp=689037447
media recovery complete
Finished recover at 08-JUN-09
printing stored script: Memory Script
shutdown clone;
startup clone nomount pfile= '/db/app/oracle/admin/catlog/pfile/initauxbr.ora';
executing script: Memory Script
database dismounted
Oracle instance shut down
connected to auxiliary database (not started)
Oracle instance started
Total System Global Area 219115512 bytes
Fixed Size 737272 bytes
Variable Size 83886080 bytes
Database Buffers 134217728 bytes
Redo Buffers 274432 bytes
sql statement: CREATE CONTROLFILE REUSE SET DATABASE "auxbr" RESETLOGS ARCHIVELOG
MAXLOGFILES 5
MAXLOGMEMBERS 5
MAXDATAFILES 100
MAXINSTANCES 1
MAXLOGHISTORY 907
LOGFILE
GROUP 1 ' /db/redolog.001/catalog1/catalog1_log1.rdo' SIZE 5242880 ,
GROUP 2 ' /db/redolog.003/catalog1/catalog1_log2.rdo' SIZE 5242880 ,
GROUP 3 ' /db/redolog.002/catalog1/catalog1_log3.rdo' SIZE 5242880
DATAFILE
'/db/catalog1.001/oradata/system01.dbf'
CHARACTER SET UTF8
printing stored script: Memory Script
catalog clone datafilecopy "/db/catalog1.001/oradata/undotbs01.dbf";
catalog clone datafilecopy "/db/catalog1.001/oradata/ptest01.dbf";
catalog clone datafilecopy "/db/catalog1.001/oradata/users_01.dbf";
catalog clone datafilecopy "/db/catalog1.001/oradata/drsys_01.dbf";
catalog clone datafilecopy "/db/catalog1.001/oradata/qms_dat_01.dbf";
catalog clone datafilecopy "/db/catalog1.001/oradata/ultradat_01.dbf";
catalog clone datafilecopy "/db/catalog1.001/oradata/xmltbs_01.dbf";
switch clone datafile all;
executing script: Memory Script
cataloged datafile copy
datafile copy filename=/db/catalog1.001/oradata/undotbs01.dbf recid=1 stamp=689037456
cataloged datafile copy
datafile copy filename=/db/catalog1.001/oradata/ptest01.dbf recid=2 stamp=689037456
cataloged datafile copy
datafile copy filename=/db/catalog1.001/oradata/users_01.dbf recid=3 stamp=689037456
cataloged datafile copy
datafile copy filename=/db/catalog1.001/oradata/drsys_01.dbf recid=4 stamp=689037457
cataloged datafile copy
datafile copy filename=/db/catalog1.001/oradata/qms_dat_01.dbf recid=5 stamp=689037457
cataloged datafile copy
datafile copy filename=/db/catalog1.001/oradata/ultradat_01.dbf recid=6 stamp=689037457
cataloged datafile copy
datafile copy filename=/db/catalog1.001/oradata/xmltbs_01.dbf recid=7 stamp=689037457
datafile 2 switched to datafile copy
input datafilecopy recid=1 stamp=689037456 filename=/db/catalog1.001/oradata/undotbs01.dbf
datafile 3 switched to datafile copy
input datafilecopy recid=2 stamp=689037456 filename=/db/catalog1.001/oradata/ptest01.dbf
datafile 4 switched to datafile copy
input datafilecopy recid=3 stamp=689037456 filename=/db/catalog1.001/oradata/users_01.dbf
datafile 5 switched to datafile copy
input datafilecopy recid=4 stamp=689037457 filename=/db/catalog1.001/oradata/drsys_01.dbf
datafile 6 switched to datafile copy
input datafilecopy recid=5 stamp=689037457 filename=/db/catalog1.001/oradata/qms_dat_01.dbf
datafile 7 switched to datafile copy
input datafilecopy recid=6 stamp=689037457 filename=/db/catalog1.001/oradata/ultradat_01.dbf
datafile 11 switched to datafile copy
input datafilecopy recid=7 stamp=689037457 filename=/db/catalog1.001/oradata/xmltbs_01.dbf
printing stored script: Memory Script
Alter clone database open resetlogs;
executing script: Memory Script
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of Duplicate Db command at 06/08/2009 23:17:38
RMAN-03015: error occurred in stored script Memory Script
RMAN-06136: ORACLE error from auxiliary database: ORA-00344: unable to re-create online log '/db/app/oracle/product/9.2.0.5/dbs/ /db
/redolog.001/catalog1/catalog1_log1.rdo'
ORA-27040: skgfrcre: create error, unable to create file
HP-UX Error: 2: No such file or directory
RMAN>
I tried to shutdown and open with resetlogs , it still error
oracle@dimondz{auxbr}/db/app/oracle/dba/sql> sqlplus '/as sysdba'
SQL*Plus: Release 9.2.0.5.0 - Production on Mon Jun 8 23:27:05 2009
Copyright (c) 1982, 2002, Oracle Corporation. All rights reserved.
Connected to:
Oracle9i Enterprise Edition Release 9.2.0.5.0 - 64bit Production
With the Partitioning option
JServer Release 9.2.0.5.0 - Production
SQL> shutdown immediate;
ORA-01109: database not open
Database dismounted.
ORACLE instance shut down.
SQL> startup mount;
ORACLE instance started.
Total System Global Area 219115512 bytes
Fixed Size 737272 bytes
Variable Size 83886080 bytes
Database Buffers 134217728 bytes
Redo Buffers 274432 bytes
Database mounted.
SQL> recover database until cancel using backup controlfile;
ORA-00279: change 229907626 generated at 06/06/2009 11:58:09 needed for thread
1
ORA-00289: suggestion : /oradump/oradata/catlog/arch/catlog-1814470384_1_5.arc
ORA-00280: change 229907626 for thread 1 is in sequence #5
Specify log: {<RET>=suggested | filename | AUTO | CANCEL}
CANCEL
Media recovery cancelled.
SQL> alter database open resetlogs;
alter database open resetlogs
ERROR at line 1:
ORA-00344: unable to re-create online log '/db/app/oracle/product/9.2.0.5/dbs/
/db/redolog.001/catalog1/catalog1_log1.rdo'
ORA-27040: skgfrcre: create error, unable to create file
HP-UX Error: 2: No such file or directory
SQL>
Thanks, Your help and guide will appreciated very much.

Hello,
The directory for the creation of the logfiles does not exist, from the error:
RMAN-06136: ORACLE error from auxiliary database: ORA-00344: unable to re-create online log '/db/app/oracle/product/9.2.0.5/dbs/ /db
/redolog.001/catalog1/catalog1_log1.rdo'
ORA-27040: skgfrcre: create error, unable to create file
HP-UX Error: 2: No such file or directoryI.e., there is no such directory as *'/db/app/oracle/product/9.2.0.5/dbs/ /db/redolog.001/catalog1/catalog1_log1.rdo'*
Your db_recovery_file_dest parameter may be set here, therefore change this:
'/db/redolog.001/catalog1/catalog1_log1.rdo' size 5m,
' /db/redolog.003/catalog1/catalog1_log2.rdo' size 5m,
' /db/redolog.002/catalog1/catalog1_log3.rdo' size 5m;To this:
'catalog1_log1.rdo' size 5m,
'catalog1_log2.rdo' size 5m,
'catalog1_log3.rdo' size 5m;And try again.

How to restore an Oracle XE Database without online logs and SPFILE?

Hi there,
My laptop was crashed last week and I was able to get only current datafiles without two online logs files and SPFILEXE.ORA from my old hard drive. I've installed with the same version of Oracle Database 10g Express Edition Release 10.2.0.1.0* software on Windows XP Pro.
I have DATAFILEs from my old db instance XE which have my thesis data.
*'C:\ORACLEXE\ORADATA\XE\SYSTEM.DBF',*
*'C:\ORACLEXE\ORADATA\XE\UNDO.DBF',*
*'C:\ORACLEXE\ORADATA\XE\SYSAUX.DBF',*
*'C:\ORACLEXE\ORADATA\XE\USERS.DBF',*
*'C:\ORACLEXE\ORADATA\XE\TEMP.DBF',*
*'C:\ORACLEXE\ORADATA\XE\USERS.DBF'*
Even though I am not 100% percent sure about If I've set the NOARCHIVELOG mode previously but neither I have the redo log files are backed up i.e. two redo log files are in C:\oraclexe\app\oracle\flash_recovery_area\XE\ONLINELOG nor have SPFILE<<SID>>.ORA. Thus, this is not really typical "+Cold backup+" when you stop the database and zip up all those 9 files (in NOARCHIVELOG mode).
I've tried the RMAN utility but it seems it requires redo log files too.
I wonder if I can restore somehow by copying all 6 datafiles to the same folder 'C:\ORACLEXE\ORADATA\XE\' or not. If so, how can I do so?
Will appreciate any advice.
Thanks in advance,

Recovering an SPfile is trivial if you have the alert log, locate the last startup- there will be a section with all the non-default parameters. Copy/paste those items to create a pfile, use it for a startup mount, check the catalog views to see if recovery is needed. Without the online redo logs it will probably need an incomplete recovery.
So in the old alertlog, [drive:]\oraclexe\app\oracle\admin\xe\bdump\alert_xe.log, grab the lines after "System parameters with non-default values:" its maybe 15 or 20 items for an "out of the box" XE install, save those to a file someplace like [drive:]\oraclexe\app\oracle\admin\xe\init\initXE.ora, fire up sqlplus and connect as sysdba, startup with the pfile ...
$ sqlplus /nolog
> connect /as sysdba;
startup mount pfile='[drive:]\oraclexe\app\oracle\admin\xe\init\initXE.ora';
If the database makes it to mount mode, check the recovery view ...
select * from v$recover_file;
If that view is clean, open 'er up should be good to go ... and create a new spfile:
alter database open;
create spfile from pfile='[drive:]\oraclexe\app\oracle\admin\xe\init\initXE.ora';
If the instance was in archivelog mode and the archive destination wasn't specified it uses flash_recovery_area for storing archivelog files, check if there are any files in the flash_recovery_area/XE/ARCHIVELOG/[yyyy-mm-dd] (?) directories. Or when connected as sysdba a command will tell you if archivelog mode is enabled:
archive log list;

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/

Recovering online log group

I am wondering how to recovery online redo log which is not multiplexed?

or you can use the flashback feature if using oracle 10g.
You can flashback your database before the time you discover the error.
you not need archived log files for that, only flashback logs, see below steps to enable the flashback feature:
ENABLE DATABASE IN ARCHIVE MODE
Step 1: verify the database is not in archiving mode
SQL> ARCHIVE LOG LIST;
Database log mode No Archive Mode
Automatic archival Disabled
Archive destination C:\local_destination1_orcl
Oldest online log sequence 1
Current log sequence 3
Step 2
SQL> SHUTDOWN IMMEDIATE;
ORACLE instance shut down.
SQL> STARTUP MOUNT;
Database mounted.
SQL> ALTER DATABASE ARCHIVELOG;
Database altered.
SQL> ARCHIVE LOG LIST;
Database log mode Archive Mode
Automatic archival Enabled
Archive destination C:\local_destination1_orcl
Oldest online log sequence 1
Next log sequence to archive 3
Current log sequence 3
SQL> ALTER DATABASE OPEN;
Database altered.
ENABLE THE FLASHRECOVERY AREA
Step 1: updating the spfile with the flash recovery area directory
SQL> ALTER SYSTEM SET DB_RECOVERY_FILE_DEST='C:\FLASHRECOVERYAREA_ORCL' SCOPE=SPFILE;
System altered.
Step 2: finding the whole database size
SQL> SELECT SUM(BYTES)/1024/1024 "TOTAL DATABASE SIZE IN MB" FROM V$TEMPFILE UNION SELECT SUM(BYTES)/1024/1204 FROM DBA_DATA_FILES;
TOTAL DATABASE SIZE IN MB
20
620.863787
Step 3: in our case the database size is 640M.Oracle recommends to size the flash recovery area at lest 3 times the database size
SQL> ALTER SYSTEM SET DB_RECOVERY_FILE_DEST_SIZE =650M SCOPE=SPFILE;
System altered.
ENABLE THE FLAHBACK DATABASE
Step 1
SQL> SHUTDOWN IMMEDIATE;
ORACLE instance shut down.
Step 2
SQL> STARTUP MOUNT EXCLUSIVE;
Database mounted.
Step 3: set up the retention policy in minutes:2880 is two days(24*60*60)
SQL> ALTER SYSTEM SET DB_FLASHBACK_RETENTION_TARGET=2880 SCOPE=BOTH;
System altered.
SQL> ALTER DATABASE FLASHBACK ON;
Database altered.
Step 4: verify that the flashback feature is enabled
SQL> SELECT FLASHBACK_ON FROM V$DATABASE;
FLASHBACK_ON
YES
Step 5: open the database
SQL> ALTER DATABASE OPEN;
Database altered.
FLASHING BACK YOUR DATABASE
SQL> SHUTDOWN IMMEDIATE;
SQL> STARTUP MOUNT;
SQL> FLASHBACK DATABASE TO SCN or TIMESTAMP before redolog file get corrupted;
SQL> ALTER DATABASE OPEN RESETLOGS
Thanks

Standby database SRL & Online logs

Hi,
I have just tried my hand at building a Physical standby database in Oracle 10gR2 using RMAN. I will detail out the steps that i have performed before asking my question.
I configured every pre-requisite and i did not create any SRL's on primary before building a standby database. I am using LGWR ASYNC for redo transmission. I have configured FAL_CLIENT and FAL_SERVER. Protection mode is MAX PERFORMANCE and it is on Solaris 10 x86_64
1. Took a RMAN full backup
and created a standby control file as
SQL> alter database create standby controlfile as '/tmp/standby.ctl';
2. On another server, I copied the pfile, standby controlfile (renamed it) from primary and mounted the database.
sqlplus /as sysdba'
SQL> startup mount pfile='...';
rman target /
RMAN> restore database;
SQL> alter database recover managed standby database disconnect from session;
Everything worked and MRP was applying the archived logs as they were received from the primary. But, i have seen the SRL's created with default names on the primary database & standby database by Oracle even though i did not explicitly create them. Is this a normal behaviour? I saw them using v$standby_log.
As a Physical standby database will not use any ONLINE REDO LOGS and i haven't created any with the procedure i have used. i have performed a SWITCHOVER, which has worked with out any problem. My question here is
1. How did Oracle open the database database when there were no redo logs physically present on the standby site? Is this a normal behavior in a standby environment where Oracle creates ONLINE REDO LOG files for a Standby database being transitioned to Primary whenever a SWITCHOVER or FAILOVER occurs? If this is the case, it is obvious that Oracle will take the LOG SEQUENCE from the last applied ARCHIVED LOG and will start the ONLINE LOG from that sequence?
Please correct me if i have understood anything wrong here or if i have configured anything wrong. But with the above configuration the Standby database worked perfectly well and switchover was successful too.
Thanks,
Harris.

Correction: I have not created the Standby Database using RMAN but only performed a FULL backup, which i have restored before starting the MRP.

Capture Proccess offen abend when online log is switching

enviroment:
Red Hat Enterprise Linux Server release 5.8 (X64)
Oracle Database 11.2.0.3.0
Oracle Golden Gate 11.1.1.1.2
Problome:
Capture Proccess offen abend when online log is switching.（Not every time）
I find errors in ggserr.log:
2013-05-01 22:10:53 ERROR OGG-01028 Oracle GoldenGate Capture for Oracle, cap.prm: error reading redo log file,
'+DATA/orcl/onlinelog/group_2.265.803917775' for sequence 1021: Reading ASM file +DATA/orcl/onlinelog/group_2.265.803917775
in DBLOGREADER mode: (333) ORA-00333: redo log read error block 42395 count 4081.
2013-05-01 22:10:53 ERROR OGG-01668 Oracle GoldenGate Capture for Oracle, cap.prm: PROCESS ABENDING.
Vut I can't find any error in database's log.xml but 'Incomplete read from log member
'+DATA/orcl/onlinelog/group_2.265.803917775'. Trying next member.'.
I find that when this error happened ,the database is switching it's online log.It is not happened in a specific online
log.And when Database switch online log to the 'error' online log back,capture proccess will work correctly.
Here is my configure:
GGSCI (TIKUDB) 1> view params cap
EXTRACT cap
SETENV (ORACLE_SID = orcl)
USERID ogg, PASSWORD ogg
TRANLOGOPTIONS DBLOGREADER
TRANLOGOPTIONS LOGRETENTION ENABLED
EXTTRAIL dirdat/lt
TABLE TQMS.TEST;
Please help me ！

xyz_hh wrote:
enviroment:
Red Hat Enterprise Linux Server release 5.8 (X64)
Oracle Database 11.2.0.3.0
Oracle Golden Gate 11.1.1.1.2Would it be possible to try upgrading to OGG 11.2.1, and see if the problem persists?

How can more than one online log file be CURRENT?

SQL> select * from v$log;
    GROUP#    THREAD# SEQUENCE#      BYTES BLOCKSIZE    MEMBERS ARC STATUS           FIRST_CHANGE# FIRST_TIM NEXT_CHANGE# NEXT_TIME
         1          1      73393   52428800        512          2 YES INACTIVE            1.2618E+13 09-SEP-13   1.2618E+13 09-SEP-13
         2          1      73394   52428800        512          2 YES INACTIVE            1.2618E+13 09-SEP-13   1.2618E+13 09-SEP-13
         3          2      64918   52428800        512          2 NO CURRENT             1.2618E+13 09-SEP-13   2.8147E+14
         4          2      64917   52428800        512          2 YES INACTIVE            1.2618E+13 09-SEP-13   1.2618E+13 09-SEP-13
         5          1      73395   52428800        512          2 NO CURRENT             1.2618E+13 09-SEP-13   2.8147E+14
         6          2      64916   52428800        512          2 YES INACTIVE            1.2618E+13 09-SEP-13   1.2618E+13 09-SEP-13
6 rows selected.
I found this in the oracle docs:
"Oracle Database uses only one redo log files at a time to store redo records written from the redo log buffer. The redo log file that LGWR is actively writing to is called the current redo log file."

this is where it confuses me actually. I also thought about 2 nodes writing to 2 online log. But when I was querying gv$log, I saw 4 CURRENT entries.
SQL> select * from gv$log;
   INST_ID     GROUP#    THREAD# SEQUENCE#      BYTES BLOCKSIZE    MEMBERS ARC STATUS           FIRST_CHANGE# FIRST_TIM NEXT_CHANGE# NEXT_TIME
         2          1          1      73393   52428800        512          2 YES INACTIVE            1.2618E+13 09-SEP-13   1.2618E+13 09-SEP-13
         2          2          1      73394   52428800        512          2 YES INACTIVE            1.2618E+13 09-SEP-13   1.2618E+13 09-SEP-13
         2          3          2      64918   52428800        512          2 NO CURRENT             1.2618E+13 09-SEP-13   2.8147E+14
         2          4          2      64917   52428800        512          2 YES INACTIVE            1.2618E+13 09-SEP-13   1.2618E+13 09-SEP-13
         2          5          1      73395   52428800        512          2 NO CURRENT             1.2618E+13 09-SEP-13   2.8147E+14
         2          6          2      64916   52428800        512          2 YES INACTIVE            1.2618E+13 09-SEP-13   1.2618E+13 09-SEP-13
         1          1          1      73393   52428800        512          2 YES INACTIVE            1.2618E+13 09-SEP-13   1.2618E+13 09-SEP-13
         1          2          1      73394   52428800        512          2 YES INACTIVE            1.2618E+13 09-SEP-13   1.2618E+13 09-SEP-13
         1          3          2      64918   52428800        512          2 NO CURRENT             1.2618E+13 09-SEP-13   2.8147E+14
         1          4          2      64917   52428800        512          2 YES INACTIVE            1.2618E+13 09-SEP-13   1.2618E+13 09-SEP-13
         1          5          1      73395   52428800        512          2 NO CURRENT             1.2618E+13 09-SEP-13   2.8147E+14
         1          6          2      64916   52428800        512          2 YES INACTIVE            1.2618E+13 09-SEP-13   1.2618E+13 09-SEP-13
12 rows selected.
SQL>
Maybe the thread# is the key? What does thread# mean here. Oracle doc of thread# doesn't describe much:   -> V$LOG

ORA-00313: cannot open online log

Hi All !!!
Please Help
% sqldba startup
SQL*DBA: Version 6.0.33.1.1 - Production on Wed Jul 11 15:40:37 2013
Copyright (c) Oracle Corporation 1979, 1989. All rights reserved.
ORACLE RDBMS V6.0.33.1.1, transaction processing option - Production
ORACLE instance started.
Database mounted.
ORA-00313: cannot open online log '/u1/oradata/orac/log2orac.dbf' (log # 2, log)
ORA-00320: cannot read log file header
ORA-07362: sfifi: open error, unable to open file.
UNIX System V 386/486 Error: 13: Permission denied
Attempting to dismount database........Database dismounted.
Attempting to shutdown instance........ORACLE instance shut down.
SQL*DBA complete.
Idea ?

987301 wrote:
Hi All !!!
Please Help
% sqldba startup
SQL*DBA: Version 6.0.33.1.1 - Production on Wed Jul 11 15:40:37 2013
Copyright (c) Oracle Corporation 1979, 1989. All rights reserved.
ORACLE RDBMS V6.0.33.1.1, transaction processing option - Production
ORACLE instance started.
Database mounted.
ORA-00313: cannot open online log '/u1/oradata/orac/log2orac.dbf' (log # 2, log)
ORA-00320: cannot read log file header
ORA-07362: sfifi: open error, unable to open file.
UNIX System V 386/486 Error: 13: Permission denied
Attempting to dismount database........Database dismounted.
Attempting to shutdown instance........ORACLE instance shut down.
SQL*DBA complete.
Idea ?
ANCIENT Oracle (V6?)!
does file /u1/oradata/orac/log2orac.dbf' really exist now?
when was last time Oracle started without error/
What happened since then?

Online logs needed archiving

Similar Messages

Maybe you are looking for