Eve redo question

We do not have Oracle Database 11 g Enterprise Edition Release 11.2.0.1.0 - 64 bit Production Linux on Red Hat 5

Databases has 2 newspapers of recovery sleep

redo04.log
redo05.log
redo06.log

They were not created in the Flash recovery area.

First question:

They should have and how is it important?

Second question: (guess Yes to the first Question)

Is there a safe method to move or drop them and recreate them in the Flash recovery area?

Hello

++ Connects FRA not much of impact if you watch again or not.
++ If you want to move the standby redo logs FIU you can add new ones and drop the old no - FRA.

Concerning
Nathalie

Tags: Database

Similar Questions

Eve redo particular journal for thread group
Hi master,

I actually play experience to create the database physical standbyt on the same machine as my primary database.

I have my past according to "data guard admin guide". even if the article for the newspaper group waiting for redo ading, it says you need to add the newspaper group pending roll forward to 'wire '...

What is this thread? and how can I foind thread that I have to give the next group of redo log?

How to find the current thread?

What happens if I add "thread"clause in my statement:-".

ALTER DATABASE ADD LOGFILE ENSURES WIRE 5
2 > ('/ oracle/dbs/log1c.rdo','/oracle/dbs/log2c.rdo') SIZE 500 M;

Thanks and greetings
VD
Vikrant,

First a question: you have a RAC instance? If so, the same paragraph does not apply to you and I don't know why you are questioning it.

Second

"The THREAD clause is required only if you want to add one or more standby redo log.
groups of files to a specific primary database thread. If you do not include the WIRE
clause and the configuration uses Real Application Clusters (RAC), Data Guard will be
automatically assign standby redo log threads file groups when running because they are
required by the various RAC instances. »

This means that you don't have to specify the thread for CARS, it will affect one according to the current thread.

Your conclusion is incorrect.
Where did you read the word "current"?
Oracle will probably simply ensure that each instance has enough sleep redolog groups, it takes 1 day before redolog group-by-Group + 1 extra.

--
Sybrand Bakker
Senior Oracle DBA

question re redologs ensures

Oracle 10.2.0.4 on OEL 5.4

Work on an exercise to create a DG configuration. After the success of the creation of Eve with

RMAN> run {
2> set until sequence = ?? thread = 1;
3> duplicate target database for standby dorecover;}

I connect to the wait (which was left in Mount by rman) and run

alter database recover managed standby database cancel;
--
ALTER DATABASE ADD standby logfile group 4 (
   '/ora01/oradata/mydb/sbyredo04a.rdo',
   '/ora02/oradata/mydb/sbyredo04b.rdo') SIZE 51200K;

change the database returns

SQL> alter database recover managed standby database cancel;
alter database recover managed standby database cancel
*
ERROR at line 1:
ORA-16136: Managed Standby Recovery not active


SQL> --
SQL> ALTER DATABASE ADD standby logfile group 4 (
  2     '/ora01/oradata/mydb/sbyredo04a.rdo',
  3     '/ora02/oradata/mydb/sbyredo04b.rdo') SIZE 51200K;
ALTER DATABASE ADD standby logfile group 4 (
*
ERROR at line 1:
ORA-01184: logfile group 4 already exists

Shows alerts log

Mon May  2 14:13:41 2011
ALTER DATABASE ADD standby logfile group 4 (
   '/ora01/oradata/mydb/sbyredo04a.rdo',
   '/ora02/oradata/mydb/sbyredo04b.rdo') SIZE 51200K
ORA-1184 signalled during: ALTER DATABASE ADD standby logfile group 4 (
   '/ora01/oradata/mydb/sbyredo04a.rdo',
   '/ora02/oradata/mydb/sbyredo04b.rdo') SIZE 51200K...

but then

SQL> select group#,
  2         thread#,
  3         sequence#,
  4         status
  5  from v$standby_log;

    GROUP#    THREAD#  SEQUENCE# STATUS
---------- ---------- ---------- ----------
         4          0          0 UNASSIGNED
         5          0          0 UNASSIGNED
         6          0          0 UNASSIGNED
         7          0          0 UNASSIGNED

4 rows selected.

but then...

[oracle@vmlnx02 dgsetup]$ cd /ora01/oradata/mydb
[oracle@vmlnx02 mydb]$ ls -l
total 1011508
-rw-r----- 1 oracle oinstall   5251072 May  2 14:13 audit_ts_01.dbf
-rw-r----- 1 oracle oinstall   7061504 May  2 14:14 control01.ctl
-rw-r----- 1 oracle oinstall  52429312 May  2 14:13 redo01a.rdo
-rw-r----- 1 oracle oinstall  52429312 May  2 14:14 redo02a.rdo
-rw-r----- 1 oracle oinstall  52429312 May  2 14:14 redo03a.rdo
-rw-r----- 1 oracle oinstall 199237632 May  2 14:13 sysaux01.dbf
-rw-r----- 1 oracle oinstall 450895872 May  2 14:13 system01.dbf
-rw-r----- 1 oracle oinstall 209723392 May  2 14:13 undotbs01.dbf
-rw-r----- 1 oracle oinstall   5251072 May  2 14:13 users01.dbf

To summarize
-the command Add STANDBY REDO fails, saying the group already exists - but...
-v$ standby_log reportss groups exist
-directory listing which files exist shows that they do not exist.

Will I have a blatent DSA, or am I just overlooking a subtlety?

As a (probably) side while listening to the eve alerts log, I noticed that at first, he complained the redo log files online (not the eve redo logs) did not exist, but which finally cleared itself.

Published by: EdStevens on May 2, 2011 15:29

If you watch redologs created on your database, then it will get spread to your control file sleep too, that's why you see them during the selection of v$ standby_log. You will just need to clear the newspapers awaiting inorder to create them on the file system before using.

try to clear the logs.

change the Group of claire database log file.

11 g it is supported automatically when you start managed recovery.

See you soon... Serrano.

automatic failover - failover unable

Hi gurus,
I have expirienced strange behavior of automatic failover of data guard.
According to the Observer newspaper failover failed:
Observer began
[W000 15:57:01.46 02/20] Observer began.
16:00:07.44 Thursday, February 20, 2014
Opening of failover accelerated to database 'ipcblna2 '...
Perform the failover NOW, please wait...
Error:
ORA-03113: end of file on communication channel
Process-ID: 2785
Session ID: 162 Seriennummer: 5
Unable to failover
16:02:08.55 Thursday, February 20, 2014
[W000 16:02:08.55 02/20] Failover failed. Leave the observer.
Observer stopped
However according to primary alerts of new ipcblna2 journal:
Successful failover. Primary database is now IPCBLNA2.
Primary alerts of new ipcblna2 journal:
Thu Feb 20 15:59:35 2014
RFS [7]: network Possible disconnect with primary database
Thu Feb 20 15:59:35 2014
RFS [2]: network Possible disconnect with primary database
Thu Feb 20 15:59:35 2014
RFS [6]: network Possible disconnect with primary database
Fri 20 Feb 16:00:07 2014
An attempt to failover accelerated because the threshold of 30 seconds is up.
Fri 20 Feb 16:00:07 2014
MICHAEL: Failover beginning
Fri 20 Feb 16:00:07 2014
ALTER DATABASE RECOVER MANAGED STANDBY DATABASE FINISH FORCE
Terminal recovery: real-time decision applies
Fri 20 Feb 16:00:07 2014
MRP0: Background Media Recovery cancelled with status 16037
Errors in the /u01/app/oracle/diag/rdbms/ipcblna2/ipcdb/trace/ipcdb_pr00_2892.trc file:
ORA-16037: Benutzer Hat Abbruch von managed recovery-procedure statement
Managed Standby recovery not using real time applies
Recovery interrupted!
Data files recovered in a consistent state to change 262827045900
Waiting for pid MRP0 2870 to terminate
Errors in the /u01/app/oracle/diag/rdbms/ipcblna2/ipcdb/trace/ipcdb_pr00_2892.trc file:
ORA-16037: Benutzer Hat Abbruch von managed recovery-procedure statement
Fri 20 Feb 16:00:07 2014
MRP0: Stopping the process background Media Recovery (ipcdb)
Terminal recovery: real time apply
Waiting for "D000" dispatcher stopped
Fri 20 16:00:23 Feb 2014
ARC2: Waiting for example near full
Fri 20 Feb 16:02:10 2014
Waiting for Server shared "S000" to die
Fri 20 Feb 16:02:23 2014
ARC2: Waiting for example close has expired
ARC2: Waiting for example near full
Fri 20 Feb 16:04:23 2014
ARC2: Waiting for example close has expired
Logging of 1034 errors received on the eve
Errors in the /u01/app/oracle/diag/rdbms/ipcblna2/ipcdb/trace/ipcdb_arc2_2827.trc file:
ORA-01034: ORACLE non available
Heartbeat PING [ARC2]: Unable to connect to the day before "ipcblna". The error is 1034.
ARC2: Waiting for example near full
Fri 20 Feb 16:05:07 2014
Renounce wait dispatchers/dispatchers and shared servers to die
CLOSING: kill the server sessions.
CLOSED: all the closing of sessions successfully.
Fri 20 Feb 16:05:07 2014
SMON: disabling of cache recovery
Try to perform a Terminal recovery (ipcdb)
Start of recovery media: Managed Standby Recovery (ipcdb)
has started the process of logmerger
Fri 20 Feb 16:05:07 2014
Managed Standby recovery not using real time applies
Fri 20 Feb 16:05:07 2014
ARC2: Waiting for example close over
Parallel Media Recovery started with 8 slaves
To start: Eve redo Logfile to check-in
End: Standby redo Logfile to check-in
"Terminal recovery Timestamp is February 20, 2014 16:05:08.
Terminal recovery: application standby redo logs.
Terminal recovery: thread 1 seq # 12 again required
Recovery of terminal:
Online Redo Log recovery: thread 1 mem Group 6 Seq 12 reading 0
Mem # 0: /u01/app/oracle/oradata/IPCBLNA2/stdbyredo01.log
Identified end-of-Redo for thread 1 sequence 12
Incomplete recovery applied to change 262827045901 20/02/2014 time 15:59:35
Media recovery complete (ipcdb)
Terminal recovery: success of
Fri 20 Feb 16:05:08 2014
Identified end-of-Redo for thread 1 sequence 12
Activation reset sleep ID 652569681 (0x26e56c51)
ARCH: Stopped archiving, error occurred. Will continue to retry
ORACLE Instance ipcdb - check-in error
ORA-16014: Log sequence 6-Nr. 12 non archiviert, keine Energiepflanzen vision
ORA-00312: line-6, 1-wire Journal: ' / u01/app/oracle/oradata/IPCBLNA2/stdbyredo01.log'
Errors in the /u01/app/oracle/diag/rdbms/ipcblna2/ipcdb/trace/ipcdb_arc0_2823.trc file:
ORA-16014: Log sequence 6-Nr. 12 non archiviert, keine Energiepflanzen vision
ORA-00312: line-6, 1-wire Journal: ' / u01/app/oracle/oradata/IPCBLNA2/stdbyredo01.log'
Completed: ALTER DATABASE RECOVER MANAGED FORCE STANDBY DATABASE FINISH
ALTER DATABASE COMMIT TO SWITCHING TO THE MAIN WAITING WITH THE STOP OF THE SESSION
DATABASE ALTER CROSSING elementary SCHOOL (ipcdb)
Waiting for the transition from role maximum is 15 minutes.
Backup controlfile written to trace the file /u01/app/oracle/diag/rdbms/ipcblna2/ipcdb/trace/ipcdb_rsm0_2844.trc
Terminal standby recovery start SCN: 262827045900
RESETLOGS after complete through change 262827045901
Log in online /u01/app/oracle/oradata/IPCBLNA2/redo01.log: thread 1 Group 1 had been previously authorized
Log in online /u01/app/oracle/oradata/IPCBLNA2/redo02.log: thread 1 group 2 was previously disabled
Log in online /u01/app/oracle/oradata/IPCBLNA2/redo03.log: thread 1 Group 3 has been previously authorized
Log in online /u01/app/oracle/oradata/IPCBLNA2/redo04.log: thread 1 Group 4 has been previously authorized
Log in online /u01/app/oracle/oradata/IPCBLNA2/redo05.log: thread 1 Group 5 has been previously authorized
Standby became primary YVERT: 262827045899
Fri 20 Feb 16:05:09 2014
Assessment target incarnation to 20
The digital switchover: completed - mounted as primary database
Completed: ALTER DATABASE COMMIT to SWITCHING to the MAIN WAITING WITH the STOP of the SESSION
Fri 20 Feb 16:05:09 2014
Arc1: become the "no SRL" ARCH
ALTER DATABASE OPEN
Initializing data Guard Broker...
Fri 20 Feb 16:05:09 2014
Assigning activation ID 652556989 (0x26e53abd)
Thread 1 Advanced to record the sequence 2 (open thread)
Thread 1 is open to the sequence of log 2
Currently Journal # 2 seq # 2 mem # 0: /u01/app/oracle/oradata/IPCBLNA2/redo02.log
Opening of redo thread 1
View MTTR is disabled, because FAST_START_MTTR_TARGET is not defined
SMON: enabling cache recovery
Fri 20 Feb 16:05:10 2014
ARC3: LGWR is scheduled for archive destination LOG_ARCHIVE_DEST_2 after log command
Fri 20 Feb 16:05:10 2014
NSA2 started with pid = 29, OS id = 5464
Successfully online 2 undo Tablespace.
Dictionary check start
Logging of 1034 errors received on the eve
Errors in the /u01/app/oracle/diag/rdbms/ipcblna2/ipcdb/trace/ipcdb_arc2_2827.trc file:
ORA-01034: ORACLE non available
Heartbeat PING [ARC2]: Unable to connect to the day before "ipcblna". The error is 1034.
Logging of 1034 errors received on the eve
Errors in the /u01/app/oracle/diag/rdbms/ipcblna2/ipcdb/trace/ipcdb_arc3_2829.trc file:
ORA-01034: ORACLE non available
ARC3: Error 1034 creation log file from archive for "ipcblna."
Archived journal 254 extra for each sequence 1 1 0x26e53abd dest ID thread entry 1:
Archiver released errors process. Is more interrupted
Verification of the complete dictionary
Check the compatibility of the header files for tablespace 11g encryption...
Compatibility check header files 11g for tablespace encryption completed
SMON: enabling the recovery of tx
From OCMS background process
Fri 20 Feb 16:05:10 2014
OCMS started with pid = 30, OS id = 5466
Database character set is AL32UTF8
Fri 20 Feb 16:05:10 2014
found dead shared server "S000", pid = (18: 1)
idle dispatcher "D000" completed, pid = (17: 1)
No Resource Manager plan active
From QMNC background process
Fri 20 Feb 16:05:11 2014
QMNC started with pid = 40, OS id = 5472
LOGSTDBY: Validation controlfile with logical metadata
LOGSTDBY: Validation complete
ALTER SYSTEM SET service_names = 'IPCBLNA2.idealo.de' SCOPE = MEMORY SID = "ipcdb";
ALTER SYSTEM SET service_names = 'IPCBLNA2.idealo.de', 'RESIN_READ1' SCOPE = MEMORY SID = "ipcdb";
ALTER SYSTEM SET service_names = 'RESIN_READ1', 'IPCBLNA2.idealo.de', 'RESIN_WRITE' SCOPE = MEMORY SID = "ipcdb";
Completed: ALTER DATABASE OPEN
ALTER SYSTEM SET log_archive_trace = 0 SCOPE = BOTH SID = "ipcdb";
ALTER SYSTEM SET log_archive_format='%t_%s_%r.dbf' SCOPE = SPFILE SID = 'ipcdb ';
ALTER SYSTEM SET standby_file_management = 'AUTO' SCOPE = BOTH SID ='* ';
ALTER SYSTEM SET archive_lag_target = 0 SCOPE = BOTH SID ='* ';
ALTER SYSTEM SET log_archive_max_processes = 5 SCOPE = BOTH SID ='* ';
ALTER SYSTEM SET log_archive_min_succeed_dest = 1 SCOPE = BOTH SID ='* ';
ALTER SYSTEM SET db_file_name_convert = ' / IPCBLNA / ', ' / IPCBLNA2 / ' SCOPE = SPFILE;
ALTER SYSTEM SET log_file_name_convert = ' / IPCBLNA / ', ' / IPCBLNA2 / ' SCOPE = SPFILE;
Fri 20 Feb 16:05:11 2014
Using the default for the STANDBY_ARCHIVE_DEST as USE_DB_RECOVERY_FILE_DEST parameter value
ARC3: FROM PROCESS ARCH
ALTER SYSTEM SET log_archive_dest_state_2 = 'RESET' SCOPE = BOTH;
Fri 20 Feb 16:05:11 2014
ARC5 started with pid = 43, OS id = 5478
Successful failover. Primary database is now IPCBLNA2.
Thread 1 Advanced to save sequence 3 (switch LGWR)
Currently Journal # 3 seq # 3 mem # 0: /u01/app/oracle/oradata/IPCBLNA2/redo03.log
Fri 20 Feb 16:05:12 2014
Archived journal 255 extra for each sequence 1 2 0x26e53abd dest ID thread entry 1:
ARC5: Started archiving
ARC3: FROM PROCESS ARCH COMPLETE
krsk_srl_archive_int: enabling archiving delayed physical standby SRls
Identified end-of-Redo for thread 1 sequence 12
Archived journal 256 additional for each sequence 1 12 0x26e56c51 dest ID thread entry 1:
From CJQ0 background process
Fri 20 Feb 16:05:14 2014
CJQ0 started with pid = 42, OS id = 5490
Fri 20 Feb 16:05:18 2014
Safety started with pid = 50, OS id = 5504
steps to reproduce:
the judgment on the primary
configuration:
DGMGRL > show fast_start failover;
Fast-Start Failover: ENABLED
Threshold: 30 seconds
Target: ipcblna2
Observer: s146
Offset limit: 7200 seconds
Primary closure: TRUE
Auto-Rétablir: TRUE
Configurable failover conditions
Animal health conditions:
Corrupt Controlfile YES
Corrupt YES dictionary
Inaccessible logfile No.
Stuck archive ONLY
YES offline data file
Oracle error conditions:
(none)
primary news after failover:
Database - ipcblna2
Role: PRIMARY
State of destination: TRANSPORT-WE
Occurrence (s):
ipcdb
Database error (s):
ORA-16820: accelerated failover observer observes is no longer this database
Warning (s) of database:
ORA-16829: accelerated failover configuration is trolling
Properties:
DGConnectIdentifier = "ipcblna2".
ObserverConnectIdentifier = "
LogXptMode = "async".
DelayMins = '0'
Binding = "optional."
MaxFailure = '0'
MaxConnections = '1'
ReopenSecs = "300"
NetTimeout = "30"
RedoCompression = "DISABLE."
LogShipping = 'ON '.
PreferredApplyInstance = "
ApplyInstanceTimeout = '0'
ApplyParallel = 'AUTO '.
StandbyFileManagement = 'AUTO '.
ArchiveLagTarget = '0'
LogArchiveMaxProcesses = '5'
LogArchiveMinSucceedDest = '1'
DbFileNameConvert = ' / IPCBLNA /, / IPCBLNA2 / '.
LogFileNameConvert = ' / IPCBLNA /, / IPCBLNA2 / '.
FastStartFailoverTarget = "ipcblna".
StatusReport = "(monitor).
InconsistentProperties = "(monitor).
InconsistentLogXptProps = "(monitor).
SendQEntries = "(monitor).
LogXptStatus = "(monitor).
RecvQEntries = "(monitor).
HostName = "rac4.lvl.bln."
Nom_sid = "ipcdb".
StaticConnectIdentifier = ' (DESCRIPTION = (ADDRESS = (PROTOCOL = tcp)(HOST=rac4.lvl.bln) (PORT = 1521)) (CONNECT_DATA = (SID = ipcdb)))'
StandbyArchiveLocation = "USE_DB_RECOVERY_FILE_DEST".
AlternateLocation = "
LogArchiveTrace = '0'
LogArchiveFormat = '% t_%s_%r.dbf '.
TopWaitEvents = "(monitor).
config after failover:
Configuration - dg_newtest
Protection mode: MaxPerformance
Databases:
ipcblna2 - primary database
Error: ORA-16825: multiple errors or warnings, including failover quick start or warnings, errors detected for the database
ipcblna - (*) physical standby database (disabled)
ORA-16661: database backup must be restored
Fast-Start Failover: ENABLED
The configuration status:
ERROR
Perhaps a clue:
strange behaviour occurred after the configuration of the shared server connections. before automatic failover worked very well.
relevant parameter:
* .shared_servers = 10
* Once = 445
* .session_cached_cursors = 300
* runoff = 400
* .open_cursors = 500
* .log_archive_dest_2 = "service = db_unique_name VALID_FOR = (ALL_LOGFILES, ALL_ROLES)"ipcblna2"="ipcblna2"net_timeout = 30', ' valid_for = (all_logfiles, primary_role)"
* .job_queue_processes = 1000
* .dispatchers ='(protocol=tcp) (dispatchers = 1)(sessions=400) '
* .log_archive_dest_state_2 = 'ENABLE '.
11 GR 2 on rhel5
Thank you

Hi oraman,

You can check the broker for this config. Connect to the database with dgmgrl and get the config database:

See the verbose XXX database;

The parameter 'StaticConnectIdentifier' will tell you what data Guard Broker expects to find when it needs to restart a database. You must create a static entry to the listener with the service_name in this setting.

Make sure you have the "SERVER = DEDICATED" in the connection string. If you set this explicit, default oracle shared a connection via the server connection, which could cause your question.

Concerning

Thomas

Questions about the parameters of database using a fast recovery area and the writing of two copies of archived redo logs.

My databases are 11.2.0.3.7 Enterprise Edition. My OS is AIX 7.1.
I am to convert databases to use individual zones of rapid recovery and have two questions about what values to assign to database settings related to archived redo logs. This example refers to a database.
I read that if I specify
Log_archive_dest_1 =' LOCATION = USE_DB_RECOVERY_FILE_DEST'
the names of newspapers archived redo written in the default quick recovery area is '% t_%S_%r.dbf '.
In the past my archived redo logs have been appointed based on the parameter
log_archive_format='GPAIDT_archive_log_%t_%s_%r.arc'
I think log_archive_format will be ignored for logs archived redo written in the fast recovery area.
I am planning to write a second copy of the archived redo logs based on the parameter
ALTER system set log_archive_dest_2 = ' LOCATION = / t07/admin/GPAIDT/arch.
If I do this, the copy of logs placed in /t07 will be called '% t_%S_%r.dbf' or 'GPAIDT_archive_log_%t_%s_%r.arc '?
Before my use of a fast recovery area, I used the OEM 12 c Console to specify settings of backup of database that has been deleted and archived redo logs after 1 backup. Oracle manuals say rather specify a deletion of "none" policy and allow Oracle delete newspapers in the area of fast recovery if necessary. Since I got to keep a second copy of these log files in /t07 should I keep the policy that says to delete logs after 1 backup? If I don't do that, how will they removed from /t07?
Thank you
Bill

If I do this, the copy of logs placed in /t07 will be called '% t_%S_%r.dbf' or 'GPAIDT_archive_log_%t_%s_%r.arc '?

They will be "GPAIDT_archive_log_%t_%s_%r.arc". LOG_ARCHIVE_FORMAT is only ignored for directories under OMF.

Since I got to keep a second copy of these log files in /t07 should I keep the policy that says to delete logs after 1 backup? If I don't do that, how will they removed from /t07?

You can hold the deletion policy as it is. Oracle documentation, defining the STRATEGY of the ARCHIVELOG DELETION: "the deletion of archived newspaper policy applies to logs archive destinations, including the area of fast recovery."

ORA-02236: invalid filename when creating redo eve

I'm getting ora-02236 creating again Eve... Why is it so?
SQL > select * from v version $;
BANNER
----------------------------------------------------------------
Oracle Database 10g Enterprise Edition Release 10.2.0.1.0 - Prod
PL/SQL Release 10.2.0.1.0 - Production
CORE 10.2.0.1.0 Production
AMT for Linux: Version 10.2.0.1.0 - Production
NLSRTL Version 10.2.0.1.0 - Production
SQL > 300 fixed lines;
SQL > set 300 pages;
SQL > /.
GROUP # STATUS TYPE MEMBER IS_
---------- ------- ------- ------------------------------ ---
/ U01/oracle/oradata/HITHA/redo No. 3 online
03 journal
/ U01/oracle/oradata/HITHA/redo No. 2 online
02.Markus newspaper
1/u01/oracle/oradata/HITHA/redo STALE in LINE No.
01.intro newspaper
SQL > select bytes of the log v$.
BYTES
----------
52428800
52428800
52428800
SQL > ALTER DATABASE ADD STANDBY LOGFILE GROUP 4 SIZE 50 M;
ALTER DATABASE ADD STANDBY LOGFILE GROUP 4 SIZE 50 M
*
ERROR on line 1:
ORA-02236: invalid file name
SQL > ALTER DATABASE ADD STANDBY LOGFILE SIZE 50 M;
ALTER DATABASE ADD STANDBY LOGFILE SIZE 50 M
*
ERROR on line 1:
ORA-02236: invalid file name

Hi all

I just tried to give the path and he managed...

SQL > alter database add standby logfile ' / u01/oracle/oradata/EDWIGE redo04.log "size m 50;

Database altered.

SQL > alter database add standby logfile ' / u01/oracle/oradata/EDWIGE

Database altered.

SQL > alter database add standby logfile ' / u01/oracle/oradata/EDWIGE

Database altered.

SQL > select * from v$ logfile;

GROUP # STATUS TYPE MEMBER IS_

---------- ------- ------- ------------------------------ ---

/ U01/oracle/oradata/HITHA/redo No. 3 online

03 journal

/ U01/oracle/oradata/HITHA/redo No. 2 online

02.Markus newspaper

1/u01/oracle/oradata/HITHA/redo STALE in LINE No.

01.intro newspaper

4/u01/oracle/oradata/HITHA/redo of EVE No.

04.the newspaper

5/u01/oracle/oradata/HITHA/redo of EVE No.

05.Marco newspaper

6/u01/oracle/oradata/HITHA/redo of EVE No.

06.the newspaper

6 selected lines.

Question about the clause for the EVE of BACKUP command
Hello

I would like to know the exact difference between BACKUP CONTROLFILE CURRENT and BACKUP CONTROLFILE CURRENT for INTELLIGENCE in Oracle 11 g. I searched the docs and My Oracle Support OTN, but still I have not found an answer. I would be grateful for any explanation or references.

Thanks in advance.
Hello

Allows to consider from scratch,

What is a controlfile :--> its a small binary file that records the physical structure of the database.
The control file includes:
The name of the database
The names and locations of the partners of the data files and redo log files
The timestamp of the creation of the database
The current sequence number
Control point information

Now, down to backup controlfile--> will have the exact backup of the controlfile used by the database (including the role of the database) Please note that this controlfile cannot serve as a controlfile standby when you try to use it it will return the error

Backup controlfile as Eve--> will anything similar as for the previous command except for the role of database that are not primary indicator but would be pahysical Eve, all other information would be same.. like with it it will not be an exact replica of the primary database.

It is the only difference from what I understand concepts.

Regrads

Question about how Oracle manages the Redo logs
Hello

Assuming a configuration which consists of 2 redo log groups (groups A and B), each group of 2 disks (disks A1 and A2 for Group A) and B1 and B2 disks for Group B. Additionally, assume that each redo log file resides by itself in a disk storage device and that the device is dedicated to her. So in the situation described above, there are 4 discs, one for each redo log file, and each disc contains nothing other than a redo log file. Also, assume that the database is in ARCHIVELOG mode and the files from archive is stored on another different set of devices.

kind of graphically:
```
    GROUP A             GROUP B

      A1                  B1
      A2                  B2
```
The question is: when the disks that make up the Group A are filled and Oracle switches to the disks in the Group B, can the group drives to take offline, perhaps even physically removed from the system if necessary without affecting the functioning of the database? Can the archiver process temporarily delayed until the disks (which have been removed) are presented online or is the DBA have to wait until the end of the process to archive a copy of the redo log file creating in archive?

Thank you for your help,

John.
Hello
A journal of the groups fall

To remove a group of online redo logs, you must have the ALTER DATABASE system privilege. Before you delete a line redo log group, consider the following precautions and restrictions:

* An instance requires at least two groups of files logging online, regardless of the number of members in the groups. (A group is one or more members.)
* You can delete a group of newspapers online redo only if it is inactive. If you need to drop the current group, first force a log switch occurs.
* Make sure a group of online redo logs is archived (if archiving is enabled) before dropping. To see if this happens, use the view LOG V$.

SELECT GROUP #, ARCHIVED, STATUS FROM V$ LOG;

GROUP # ARC STATUS
--------- --- ----------------
1 ACTIVE YES
2. NO CURRENT
3 INACTIVE YES
4 INACTIVE YES

Delete a group of newspapers online redo with the SQL ALTER DATABASE statement with the DROP LOGFILE clause.

The following statement drops redo log group number 3:

ALTER DATABASE, DROP LOGFILE GROUP 3;

When a group of online redo logs is deleted from the database, and you do not use Oracle managed files, operating system files are not removed from the disk. Instead, control of the associated database files are updated to remove members of the Group of the database structure. After deleting a group of online redo logs, make sure the drop completed successfully and then use the command of operating system appropriate to delete the dropped online redo log files.

When you work with files managed by Oracle, the cleaning of operating system files is done automatically for you.
Your database will not be affected as you can work with 2 files, redo log in each group, as the minimum number of redo log in a database file is two because the process LGWR (newspaper writer) writes in the redo log in a circular way. If the process crashes because you have 2 groups only if you want to remove 1 Add a third and make that the current group and remove the one you want to be offline.

Please refer to:
http://download.Oracle.com/docs/CD/B10500_01/server.920/a96521/onlineredo.htm#7438
Kind regards
Mohamed
Oracle DBA

Question about REDO
I have a question about roll FORWARD.

We know that when changes to databases... online redo file change logs.

In books and various documents, it is mentioned that redo logs also store 'image' of the data before. Before the Images go to UNDO Tablespace and contributing to restoring

My question is why do the newspapers 'image' of the data before store? What is the main purpose of storage before the image of the data in the REDO logs?

Please explain.

Thanks in advance.
Here is the nice discussion.

Difference between newspapers redo and undo tablespace
Difference between newspapers redo and undo tablespace

HTH
-André

Redo log buffer question
Hi master,

This seems to be very basic, but I would like to know internal process.

We know all that LGWR writes redo entries to redo logs on the disk online. on validation SCN is generated and the tag to the transaction. and LGWR writes this to online redo log files.

but my question is, how these redo entries just redo log buffer? Look at all the necessary data are read from the cache of the server process buffers. It is modified it and committed. DBWR wrote this in files of data, but at what time, what process writes this committed transaction (I think again entry) in the log buffers cache?

LGWR do that? What exactly happens internally?

If you can please focus you some light on internals, I will be grateful...

Thanks and greetings
VD
Vikrant,
I will write less coz used pda. In general, this happens
1. a calculation because how much space is required in the log buffer.
2 server process acquires redo copy latch to mention some reco will be responsible.

Redo allocation latch is used to allocate space.

Redo allocation latch is provided after the space is released.

Redo copy latch is used copy redo contained in the log buffer.

Redo copy lock is released

HTH
Aman

question about sync of drain plug and Eve delay block
If a session in my primary database applies a large transaction, then it could cause to delay block drain plug, which is writing the changed blocks to the data files in the primary database will be delayed until an attempt is made to read them, now that they will be written to the data files. However redo generation for the big transacation is not delayed, nor is archiving, and so do it again is sent to the database Eve with a minimum of delay. It is not possible or even likely that the large transaction will have been written to pending data files then written to the primary data files? If so, is it important?

Thank you.

Two fundamental questions in physics eve
DB version: 10.2.0.5
Operating system: Solaris

Question1.
That's how we get a database from the previous day. Right?
```
$ sqlplus / as sysdba
 
SQL*Plus: Release 10.2.0.5.0 Production on Thu Dec 16 13:16:33 2011
 
Copyright (c) 1982, 2010, Oracle.  All rights reserved.
 
Connected to an idle instance.
 
SQL> startup nomount;
ORACLE instance started.
 
Total System Global Area 1436819456 bytes
Fixed Size                  2158344 bytes
Variable Size             855642360 bytes
Database Buffers          570425344 bytes
Redo Buffers                8593408 bytes

SQL> alter database mount standby database;
 
Database altered.
```
Question2.
Once MOUNTED (using the above command), the standby database in a consistent state of recovery will automatically be applying shipped archive logs. Right?
Or, we must issue explicitly below command on a regular basis to apply the embedded archived redo logs to sync with the primary DB?
```
recover standby database;
```
Question1.
That's how we get a database from the previous day. Right?

Yes even if you give "edit the editing of database" or "alter database mount standby database", there is no difference, because controlfile is the type of sleep.

Question2.
Once MOUNTED (using the above command), the standby database in a consistent state of recovery will automatically be applying shipped archive logs. Right?
Or, we must issue explicitly below command on a regular basis to apply the embedded archived redo logs to sync with the primary DB?

The command above just goes up, it doesn't start any recovery.
If you recover the database pending, it will apply only available archives.

you need to automate the process of recovery as

SQL > change database recovery managed standby database disconnect from the session.

Then recovery will be automated.

Question on create Redo log after restoring files and recover
Log files to rebuild RMAN backup? Below the blog describes the steps to restore and recover a RMAN backup in a new host.
http://blog.CSDN.NET/sweethouse1128/article/details/6948273

RMAN seems to have backed up and restored the redo log files

After the resumption, blogger issues
```
select * from v$logfile;
```
and the result obtained some log files. The rows returned are restored files redo log. right? Redo of RMAN backup and restore log files?
Redo of RMAN backup and restore log files?

N ° never. Even when you do a 'coherent' backup (i.e. with the database MOUNT but the mode is not OPEN).

When you restore a full RMAN on a new server backup, RMAN restore REDO LOG files in the respective directories

Does not apply because RMAN does not save logs in restoration online.

Isn't better to manually create redo log files after restoration

When you perform incomplete recovery, you must issue an ALTER DATABASE OPEN RESETLOGS.
The RESETLOGS creates log files remake it, if they are not present OR reset them if they are present.
In a scenario of complete restoration, the online redo log files are already present on the drive (i.e. they are not lost or destroyed and they are not restored a backup).

Hemant K Collette

question abount undo and Redo
Hello friends,

could you explain the work of UNDO and REDO, I have some confusion.
Well, cancel all of the user update and also on the Segment Undo update, both are stored in it again! The use of roll forward is for the recovery and cancellation for read consistency.

HTH
Aman...

Question about the size of the redo log buffer
Hello

I am a student in Oracle and the book I use says that having a bigger than the buffer log by default, the size is a bad idea.

It sets out the reasons for this are:

>
The problem is that when a statement COMMIT is issued, part of the batch validation means to write the contents of the buffer log for redo log to disk files. This entry occurs in real time, and if it is in progress, the session that issued the VALIDATION will be suspended.
>

I understand that if the redo log buffer is too large, memory is lost and in some cases could result in disk i/o.

What I'm not clear on is, the book makes it sound as if a log buffer would cause additional or IO work. I would have thought that the amount of work or IO would be substantially the same (if not identical) because writing the buffer log for redo log files is based on the postings show and not the size of the buffer itself (or its satiety).

Description of the book is misleading, or did I miss something important to have a larger than necessary log buffer?

Thank you for your help,

John.

Published by: 440bx - 11 GR 2 on August 1st, 2010 09:05 - edited for formatting of the citation
A commit evacuates everything that in the buffer redolog for redo log files.
A redo log buffer contains the modified data.
But this is not just commit who empty the redolog buffer to restore the log files.
LGWR active every time that:
(1) a validation occurs
(2) when the redo log is 1/3 full
(3) every 3 seconds
It is not always necessary that this redolog file will contain validated data.
If there is no commit after 3 seconds, redologfile would be bound to contain uncommitted data.

Best,
Wissem

Eve redo question

Similar Questions

Maybe you are looking for