Will the DB down if INACTIVE redo log group is deleted?

Platform: Oracle Linux 6.5

DB version: 11.2

If I delete one or all members of a Redo Log group online that is IDLE, manually (using the rm command) will be the DB crash?

Instead of everybody speculating, why not just run a test?

Oracle 11.2.0.1, Enterprise Edition, 64-bit on OL 5, running in archivelog mode

SQL> select group#,
  2 sequence#,
  3 archived,
  4 status
  5  from v$log
  6 order by group#
  7  ;
    GROUP# SEQUENCE# ARC STATUS
---------- ---------- --- ----------------
 1    1 YES INACTIVE
 2    2 YES INACTIVE
 3    3 NO  CURRENT
3 rows selected.
SQL> --
SQL> insert into scott.mytest values (sysdate);
1 row created.
SQL> commit;
Commit complete.
SQL> alter system switch logfile;
System altered.
SQL> select * from v$logfile;
    GROUP# STATUS  TYPE MEMBER  IS_
---------- ------- ------- ------------------------------ ---
 3 ONLINE /oradata/tulsa/redo03.rdo  NO
 2 ONLINE /oradata/tulsa/redo02.rdo  NO
 1 ONLINE /oradata/tulsa/redo01.rdo  NO
3 rows selected.
SQL>
SQL> select group#,
  2 sequence#,
  3 archived,
  4 status
  5  from v$log
  6 order by group#
  7  ;
    GROUP# SEQUENCE# ARC STATUS
---------- ---------- --- ----------------
 1    4 NO  CURRENT
 2    2 YES INACTIVE
 3    3 NO  ACTIVE
3 rows selected.

Group 2 is inactive, so delete the

SQL> !rm /oradata/tulsa/redo02.rdo
SQL> !ls -l /oradata/tulsa/redo02.rdo
ls: /oradata/tulsa/redo02.rdo: No such file or directory

And continue the activity of db.  Keep an eye on the #2 group

SQL> select group#,
  2 sequence#,
  3 archived,
  4 status
  5  from v$log
  6 order by group#
  7  ;
    GROUP# SEQUENCE# ARC STATUS
---------- ---------- --- ----------------
 1    4 NO  CURRENT
 2    2 YES INACTIVE
 3    3 YES ACTIVE
3 rows selected.
SQL> insert into scott.mytest values (sysdate);
1 row created.
SQL> commit;
Commit complete.
SQL> alter system switch logfile;
System altered.
SQL> --
SQL> select group#,
  2 sequence#,
  3 archived,
  4 status
  5  from v$log
  6 order by group#
  7  ;
    GROUP# SEQUENCE# ARC STATUS
---------- ---------- --- ----------------
 1    4 NO  ACTIVE
 2    5 NO  CURRENT
 3    3 YES ACTIVE
3 rows selected.
SQL> insert into scott.mytest values (sysdate);
1 row created.
SQL> commit;
Commit complete.
SQL> alter system switch logfile;
System altered.
SQL> --
SQL> select group#,
  2 sequence#,
  3 archived,
  4 status
  5  from v$log
  6 order by group#
  7  ;
    GROUP# SEQUENCE# ARC STATUS
---------- ---------- --- ----------------
 1    4 YES INACTIVE
 2    5 NO  ACTIVE
 3    6 NO  CURRENT
3 rows selected.
SQL> insert into scott.mytest values (sysdate);
1 row created.
SQL> commit;
Commit complete.
SQL> alter system switch logfile;
System altered.
SQL> --
SQL> select group#,
  2 sequence#,
  3 archived,
  4 status
  5  from v$log
  6 order by group#
  7  ;
    GROUP# SEQUENCE# ARC STATUS
---------- ---------- --- ----------------
 1    7 NO  CURRENT
 2    5 NO  ACTIVE
 3    6 NO  ACTIVE
3 rows selected.
SQL> insert into scott.mytest values (sysdate);
1 row created.
SQL> commit;
Commit complete.
SQL> alter system switch logfile;

At this point, the SWTICH LOGFILE command has been attached, and in the alerts log, we see this:

CJQ0 started with pid=26, OS id=4817
Sat Sep 19 10:48:11 2015
Thread 1 advanced to log sequence 4 (LGWR switch)
  Current log# 1 seq# 4 mem# 0: /oradata/tulsa/redo01.rdo
Sat Sep 19 10:48:11 2015
Archived Log entry 1 added for thread 1 sequence 3 ID 0xdaf1e381 dest 1:
Sat Sep 19 10:48:44 2015
Thread 1 advanced to log sequence 5 (LGWR switch)
  Current log# 2 seq# 5 mem# 0: /oradata/tulsa/redo02.rdo
Sat Sep 19 10:48:44 2015
Archived Log entry 2 added for thread 1 sequence 4 ID 0xdaf1e381 dest 1:
Thread 1 cannot allocate new log, sequence 6
Checkpoint not complete
  Current log# 2 seq# 5 mem# 0: /oradata/tulsa/redo02.rdo
Thread 1 advanced to log sequence 6 (LGWR switch)
  Current log# 3 seq# 6 mem# 0: /oradata/tulsa/redo03.rdo
Sat Sep 19 10:48:48 2015
Errors in file /u01/app/oracle/diag/rdbms/tulsa/tulsa/trace/tulsa_arc3_4789.trc:
ORA-00313: open failed for members of log group 2 of thread 1
ORA-00312: online log 2 thread 1: '/oradata/tulsa/redo02.rdo'
ORA-27037: unable to obtain file status
Linux-x86_64 Error: 2: No such file or directory
Additional information: 3
Errors in file /u01/app/oracle/diag/rdbms/tulsa/tulsa/trace/tulsa_arc3_4789.trc:
ORA-00313: open failed for members of log group 2 of thread 1
ORA-00312: online log 2 thread 1: '/oradata/tulsa/redo02.rdo'
ORA-27037: unable to obtain file status
Linux-x86_64 Error: 2: No such file or directory
Additional information: 3
Thread 1 advanced to log sequence 7 (LGWR switch)
  Current log# 1 seq# 7 mem# 0: /oradata/tulsa/redo01.rdo
ARCH: Archival stopped, error occurred. Will continue retrying
ORACLE Instance tulsa - Archival Error
Thread 1 cannot allocate new log, sequence 8
Checkpoint not complete
  Current log# 1 seq# 7 mem# 0: /oradata/tulsa/redo01.rdo
ORA-16038: log 2 sequence# 5 cannot be archived
ORA-00312: online log 2 thread 1: '/oradata/tulsa/redo02.rdo'
Errors in file /u01/app/oracle/diag/rdbms/tulsa/tulsa/trace/tulsa_arc3_4789.trc:
ORA-16038: log 2 sequence# 5 cannot be archived
ORA-00312: online log 2 thread 1: '/oradata/tulsa/redo02.rdo'
Sat Sep 19 10:48:48 2015
Errors in file /u01/app/oracle/diag/rdbms/tulsa/tulsa/trace/tulsa_arc0_4777.trc:
ORA-00313: open failed for members of log group 2 of thread 1
ORA-00312: online log 2 thread 1: '/oradata/tulsa/redo02.rdo'
ORA-27037: unable to obtain file status
Linux-x86_64 Error: 2: No such file or directory
Additional information: 3
Errors in file /u01/app/oracle/diag/rdbms/tulsa/tulsa/trace/tulsa_arc0_4777.trc:
ORA-00313: open failed for members of log group 2 of thread 1
ORA-00312: online log 2 thread 1: '/oradata/tulsa/redo02.rdo'
ORA-27037: unable to obtain file status
Linux-x86_64 Error: 2: No such file or directory
Additional information: 3
Sat Sep 19 10:48:48 2015
Errors in file /u01/app/oracle/diag/rdbms/tulsa/tulsa/trace/tulsa_m000_4864.trc:
ORA-00313: open failed for members of log group 2 of thread 1
ORA-00312: online log 2 thread 1: '/oradata/tulsa/redo02.rdo'
ORA-27037: unable to obtain file status
Linux-x86_64 Error: 2: No such file or directory
Additional information: 3
Checker run found 2 new persistent data failures
ORACLE Instance tulsa - Can not allocate log, archival required
Thread 1 cannot allocate new log, sequence 8
All online logs needed archiving
  Current log# 1 seq# 7 mem# 0: /oradata/tulsa/redo01.rdo
Sat Sep 19 10:48:59 2015
Errors in file /u01/app/oracle/diag/rdbms/tulsa/tulsa/trace/tulsa_arc2_4785.trc:
ORA-00313: open failed for members of log group 2 of thread 1
ORA-00312: online log 2 thread 1: '/oradata/tulsa/redo02.rdo'
ORA-27037: unable to obtain file status
Linux-x86_64 Error: 2: No such file or directory
Additional information: 3
Errors in file /u01/app/oracle/diag/rdbms/tulsa/tulsa/trace/tulsa_arc2_4785.trc:
ORA-00313: open failed for members of log group 2 of thread 1
ORA-00312: online log 2 thread 1: '/oradata/tulsa/redo02.rdo'
ORA-27037: unable to obtain file status
Linux-x86_64 Error: 2: No such file or directory
Additional information: 3
Sat Sep 19 10:48:59 2015
Errors in file /u01/app/oracle/diag/rdbms/tulsa/tulsa/trace/tulsa_arc1_4781.trc:
ORA-00313: open failed for members of log group 2 of thread 1
ORA-00312: online log 2 thread 1: '/oradata/tulsa/redo02.rdo'
ORA-27037: unable to obtain file status
Linux-x86_64 Error: 2: No such file or directory
Additional information: 3
Errors in file /u01/app/oracle/diag/rdbms/tulsa/tulsa/trace/tulsa_arc1_4781.trc:
ORA-00313: open failed for members of log group 2 of thread 1
ORA-00312: online log 2 thread 1: '/oradata/tulsa/redo02.rdo'
ORA-27037: unable to obtain file status
Linux-x86_64 Error: 2: No such file or directory
Additional information: 3
Sat Sep 19 10:49:59 2015
Errors in file /u01/app/oracle/diag/rdbms/tulsa/tulsa/trace/tulsa_arc2_4785.trc:
ORA-00313: open failed for members of log group 2 of thread 1
ORA-00312: online log 2 thread 1: '/oradata/tulsa/redo02.rdo'
ORA-27037: unable to obtain file status
Linux-x86_64 Error: 2: No such file or directory
Additional information: 3
Errors in file /u01/app/oracle/diag/rdbms/tulsa/tulsa/trace/tulsa_arc2_4785.trc:
ORA-00313: open failed for members of log group 2 of thread 1
ORA-00312: online log 2 thread 1: '/oradata/tulsa/redo02.rdo'
ORA-27037: unable to obtain file status
Linux-x86_64 Error: 2: No such file or directory
Additional information: 3
Sat Sep 19 10:49:59 2015
Errors in file /u01/app/oracle/diag/rdbms/tulsa/tulsa/trace/tulsa_arc3_4789.trc:
ORA-00313: open failed for members of log group 2 of thread 1
ORA-00312: online log 2 thread 1: '/oradata/tulsa/redo02.rdo'
ORA-27037: unable to obtain file status
Linux-x86_64 Error: 2: No such file or directory
Additional information: 3
Errors in file /u01/app/oracle/diag/rdbms/tulsa/tulsa/trace/tulsa_arc3_4789.trc:
ORA-00313: open failed for members of log group 2 of thread 1
ORA-00312: online log 2 thread 1: '/oradata/tulsa/redo02.rdo'
ORA-27037: unable to obtain file status
Linux-x86_64 Error: 2: No such file or directory
Additional information: 3
Sat Sep 19 10:49:59 2015
Errors in file /u01/app/oracle/diag/rdbms/tulsa/tulsa/trace/tulsa_m000_5163.trc:
ORA-00313: open failed for members of log group 2 of thread 1
ORA-00312: online log 2 thread 1: '/oradata/tulsa/redo02.rdo'
ORA-27037: unable to obtain file status
Linux-x86_64 Error: 2: No such file or directory
Additional information: 3

Tags: Database

Similar Questions

  • How to resize Redo log groups

    Windows Server 2008 64 bit - Oracle 11g (11.02.0)

    We have our first oracle database implementation.
    The go live is supposed to happen in March or April.
    Our Oracle courses will begin next week, but because of the performance, I need to change the size of redo log groups.
    Users are just load data of the year 2010 in the database, but the performance is terrible.
    I would like to know if it is possible to do using the Manager of the company.
    I was able to modify the storage spaces and their files, but I don't succeed with redo log groups.
    I have 3 groups with 50 MB each. I would change the 500 MB each.
    When I try to change groups, it does not open the possibility of change.
    Do I have to stop the database? do I have to clean the Group? How can I change the size of them?

    Eduardo

    Hello

    As vmalepati says, you can't resize redo log groups.
    Create three new newspaper groups, with the size you need.
    As the database is through the loggroups, you will be able to drop the 'old' (small ones).

    (1) find the instance in OEM
    2) enter the tab "Server".
    (3) with the 'storage', press 'Redo log groups'
    (4) connect the database with a strong user
    (5) use the "create as.
    (6) change the size and all the other things you need and press "ok".
    (7) repeat 5 & 6 until you have the number of new redo log groups you need
    (8) remove the old redologs. Choose those showing "inactive".

    To force a logswitch, newspaper in sqlplus as user hard (System, for example) and run the command
    alter system switch logfile;

    Best regards
    Anders.

  • [Account] redo logs groups and its members?

    Hello gurus,

    Well well, the theory written in the book may be different on the actual situation, different configuration of the different company...

    How we determine how many redo logs groups it is should be? And how many members each group better?

    What are the considerations?

    Kind regards

    NIA...

    What are the considerations?

    How journal frequent switches under the load of work 'normal' (time in minutes)?
    Can the archiver complete its work before this log file is required to be used again?

  • Adding more large size Redo log groups in RAC, ASM

    Hi people,

    Version of database - 10.1.0.4.0
    Version of the OS - AIX 5.3
    Node 2 RAC and ASM

    We had 4 groups of log roll forward of any size on the two nodes.yesterday, I added 4 new larger size groups using pl/sql developer tool and deleted the old 2 redolog groups. But I'm not able to remove the rest of the 2 groups of old.

    ORA-01567 a log2 fall would have less than 2 log files for example 1.

    Our redolog files are the SAN and the two points of the same storage node. When I pulled this command line query

    SELECT v$ logfile.member, v$ logfile.group #, v$ log.status, v$ log.bytes
    V $ log v$ logfile
    WHERE v$ log.group # v = $logfile.group #;

    I had the same result for both nodes.

    The problem that I think, is that all 4 new newspaper groups are added to instance 2 and its old 2 grouips are are also deleted.


    Now my question is that:

    1 should I I added groups of redo log separately on the two nodes of storage is the same for both nodes?
    2 redologs groups are defined separately for each node?

    How can I assign 2 new groups of newspapers to instantiate redo 1?

    Kind regards

    Redo log group should minus 2 groups each of the thread.
    But it is good to use 3 groups... each of the threads.

    and 2 members on each of the groups.

    all redo check journal... from v$ session, v$ logfile, v$ archvied_log

    If you mean the idea to determine approximately the size of the log to roll forward... you can check newspaper alerts.

    or

    ALTER session set nls_date_format = "YYYY/MM/DD HH24:MI:SS;
    Select INST_ID select, name, control gv completion_time $ archived_log by 3.1.

    Good luck

  • redo log groups

    How much max redo log groups we create and how many members max groups can created b

    Here are the most bone depenedent. They are defined during the creation of the database or the creation of control files are identified by the MAXLOGFILES and MAXLOGMEMBERS parameters respectively.

    They may have a value maximum 255 and 5 respectively

  • Connect the switch to Oracle 9iR2 - redo log size too small?

    Hi all!

    I just ran a report of Diagnostic Agent service RDA (Remote) and have found a lot of information on our company database system.

    Among the interesting findings is that newspaper that shows recovery logs archiving.

    It seems that it is quite often archiving. This means that our recovery logs is too small (they are 50 MB)? Please check the date and time stamp of the columns in the papers below for details.

    Also, sorry for the column headers and columns being not very well aligned. I hope that it is readable for you anyway.


    Information from V$ Logfile and V$ Log

    V$ Logfile
    Group # member status
    1 null value /prog26/ORACLE/X4450/redo_01.log
    2 null value /prog26/ORACLE/X4450/redo_02.log
    3 null value /prog26/ORACLE/X4450/redo_03.log

    V$ Log
    Group # Thread # sequence # bytes members archived first change state # first time
    1 1 19394 52428800 1 NO CURRENT 9944095405700 March 4, 2009 14:24:40
    YES 2 1 19392 52428800 1 INACTIVE 9944095397506 4 March 2009 14:23:49
    3 1 19393 52428800 1 YES ON 9944095402911 March 4, 2009 14:24:06




    Status of data protection
    Gravity installation Dest Id Message Num Code legend Timestamp Error Message
    Connect the control Services of carriage 40075 0 0 YES March 4, 2009 08:19:53 ARC0: complete archiving 3 thread 1 sequence 19339 journal
    Log of information Transport Services 0 0 40076 No. 4 March 2009 08:20:07 ARC0: Evaluating archive log 1 thread 1 sequence 19340
    Log Transport Services 0 40077 Control 0 YES March 4, 2009 08:20:07 ARC0: starts to archive log 1-wire 1 sequence 19340
    Log of information Transport Services 0 0 40078 No. 4 March 2009 08:20:07 destination creation of archive LOG_ARCHIVE_DEST_1: ' / prog26/oracle/admin/X4450/arch/archX4450.log1_19340.dbf'
    Log Transport Services 0 40079 Control 0 YES March 4, 2009 08:20:09 ARC0: completed archive connect 1 thread 1 sequence 19340
    Log of information Transport Services 0 0 40080 No. 4 March 2009 08:20:23 ARC0: Evaluating archive log 2 wire 1 sequence 19341
    Log Transport Services 0 40081 Control 0 YES March 4, 2009 08:20:23 ARC0: starts to archive log 2 wire 1 sequence 19341
    Log of information Transport Services 0 40082 0 no. 4 March 2009 08:20:23 destination archive creation LOG_ARCHIVE_DEST_1: ' / prog26/oracle/admin/X4450/arch/archX4450.log1_19341.dbf'
    Log Transport Services 0 40083 Control 0 YES March 4, 2009 08:20:25 ARC0: completed thread 1 archiving of Journal 2 sequence 19341
    Log of information Transport Services 0 0 40084 No. 4 March 2009 08:20:39 ARC0: Evaluating archive log 3 wire 1 sequence 19342
    Log Transport Services 0 40085 Control 0 YES March 4, 2009 08:20:39 ARC0: starts to archive log 3 wire 1 sequence 19342
    Log of information Transport Services 0 0 40086 No. 4 March 2009 08:20:39 destination creation of archive LOG_ARCHIVE_DEST_1: ' / prog26/oracle/admin/X4450/arch/archX4450.log1_19342.dbf'
    Connect the control Services of carriage 40087 0 0 YES March 4, 2009 08:20:41 ARC0: complete archiving 3 thread journal 1 sequence 19342
    Log of information Transport Services 0 0 40088 No. 4 March 2009 08:20:55 ARC0: Evaluating archive log 1 thread 1 sequence 19343
    Log Transport Services 0 40089 Control 0 YES March 4, 2009 08:20:55 ARC0: starts to archive log 1-wire 1 sequence 19343
    Log of information Transport Services 0 40090 0 no. 4 March 2009 08:20:55 destination archive creation LOG_ARCHIVE_DEST_1: ' / prog26/oracle/admin/X4450/arch/archX4450.log1_19343.dbf'
    Log Transport Services 0 40091 Control 0 YES March 4, 2009 08:20:57 ARC0: completed archive connect 1 thread 1 sequence 19343
    Log of information Transport Services 0 0 40092 No. 4 March 2009 08:21:11 ARC0: Evaluating archive log 2 wire 1 sequence 19344
    Log Transport Services 0 40093 Control 0 YES March 4, 2009 08:21:11 ARC0: starts to archive log 2 wire 1 sequence 19344
    Log of information Transport Services 0 40094 0 no. 4 March 2009 21:08:11 destination archive creation LOG_ARCHIVE_DEST_1: ' / prog26/oracle/admin/X4450/arch/archX4450.log1_19344.dbf'
    Log Transport Services 0 40095 Control 0 YES March 4, 2009 08:21:13 ARC0: completed thread 1 archiving of Journal 2 sequence 19344
    Log of information Transport Services 0 0 40096 No. 4 March 2009 08:21:27 ARC0: Evaluating archive log 3 wire 1 sequence 19345
    Log Transport Services 0 40097 Control 0 YES March 4, 2009 08:21:27 ARC0: starts to archive log 3 wire 1 sequence 19345
    Log of information Transport Services 0 40098 0 no. 4 March 2009 08:21:27 destination archive creation LOG_ARCHIVE_DEST_1: ' / prog26/oracle/admin/X4450/arch/archX4450.log1_19345.dbf'
    Log of information Transport Services 0 0 40099 No. 4 March 2009 08:21:43 ARC1: Evaluating archive log 3 wire 1 sequence 19345
    Log Transport Services WARNING 0 40100 1 No. 4 March 2009 08:21:43 ARC1: impossible to archive log 3 thread 1 sequence 19345
    Log of information Transport Services 0 40101 0 no. 4 March 2009 08:21:43 Log Archived actively by another process



    History of archives
    Stamp RecId name Dest Id Thread # sequence # Resetlogs change # Resetlogs time first change # Primo next change # next time blocks block size creator Registrar Dest applied archived standby status deleted end time dictionary dictionary tip tip of Redo Backup Begin archiving Thread # Activation County #.
    9408 674554239 /prog26/oracle/admin/X4450/arch/archX4450.log1_9408.dbf 1 1 9408 9085999921960 23 August 2008 21:12:37 9091063265490 December 27, 2008 08:10:23 9091063265585 December 27, 2008 08:10:37 102398 512 ARCH ARCH no YES NO a December 27, 2008 08:10:39 NO NO NO 0 1 3017662510
    9409 674554252 /prog26/oracle/admin/X4450/arch/archX4450.log1_9409.dbf 1 1 9409 9085999921960 23 August 2008 21:12:37 9091063265585 December 27, 2008 08:10:37 9091063265684 December 27, 2008 08:10:50 102398 512 ARCH ARCH no YES NO a December 27, 2008 08:10:52 0 1 3017662510 NO NO NO
    9410 674554266 /prog26/oracle/admin/X4450/arch/archX4450.log1_9410.dbf 1 1 9410 9085999921960 23 August 2008 21:12:37 9091063265684 December 27, 2008 08:10:50 9091063265783 December 27, 2008 08:11:03 102398 512 ARCH ARCH no YES NO a December 27, 2008 08:11:06 0 1 3017662510 NO NO NO
    9411 674554279 /prog26/oracle/admin/X4450/arch/archX4450.log1_9411.dbf 1 1 9411 9085999921960 23 August 2008 21:12:37 9091063265783 December 27, 2008 08:11:03 9091063265884 December 27, 2008 08:11:17 102398 512 ARCH ARCH no YES NO a December 27, 2008 08:11:19 0 1 3017662510 NO NO NO
    9412 674554293 /prog26/oracle/admin/X4450/arch/archX4450.log1_9412.dbf 1 1 9412 9085999921960 23 August 2008 21:12:37 9091063265884 December 27, 2008 08:11:17 9091063265980 December 27, 2008 08:11:31 102398 512 ARCH ARCH no YES NO a December 27, 2008 08:11:33 0 1 3017662510 NO NO NO
    9413 674554306 /prog26/oracle/admin/X4450/arch/archX4450.log1_9413.dbf 1 1 9413 9085999921960 23 August 2008 21:12:37 9091063265980 December 27, 2008 08:11:31 9091063266072 December 27, 2008 08:11:44 102398 512 ARCH ARCH no YES NO a December 27, 2008 08:11:46 0 1 3017662510 NO NO NO
    9414 674554506 /prog26/oracle/admin/X4450/arch/archX4450.log1_9414.dbf 1 1 9414 9085999921960 23 August 2008 21:12:37 9091063266072 December 27, 2008 08:11:44 9091063287590 27 December 2008 08:15:01 102398 512 ARCH ARCH no YES NO a 27 December 2008 08:15:06 0 1 3017662510 NO NO NO
    9415 674563077 /prog26/oracle/admin/X4450/arch/archX4450.log1_9415.dbf 1 1 9415 9085999921960 23 August 2008 21:12:37 9091063287590 December 27, 2008 08:15:01 9091063833538 December 27, 2008 10:37:54 102398 512 ARCH ARCH no YES NO a December 27, 2008 10:37:57 0 1 3017662510 NO NO NO
    9416 674570183 /prog26/oracle/admin/X4450/arch/archX4450.log1_9416.dbf 1 1 9416 9085999921960 23 August 2008 21:12:37 9091063833538 December 27, 2008 10:37:54 9091064440549 December 27, 2008 12:36:17 102398 512 ARCH ARCH no YES NO a December 27, 2008 12:36:23 0 1 3017662510 NO NO NO
    9417 674582409 /prog26/oracle/admin/X4450/arch/archX4450.log1_9417.dbf 1 1 9417 9085999921960 23 August 2008 21:12:37 9091064440549 December 27, 2008 12:36:17 9091065119444 December 27, 2008 16:00:03 102398 512 ARCH ARCH no YES NO a 27 December 2008 16:00:09 0 1 3017662510 NO NO NO
    9418 674585288 /prog26/oracle/admin/X4450/arch/archX4450.log1_9418.dbf 1 1 9418 9085999921960 23 August 2008 21:12:37 9091065119444 December 27, 2008 16:00:03 9091065291305 December 27, 2008 16:48:06 102398 512 ARCH ARCH no YES NO a 27 December 2008 16:48:08 0 1 3017662510 NO NO NO
    9419 674586049 /prog26/oracle/admin/X4450/arch/archX4450.log1_9419.dbf 1 1 9419 9085999921960 23 August 2008 21:12:37 9091065291305 December 27, 2008 16:48:06 9091065312654 27 December 2008 17:00:44 102398 512 ARCH ARCH no YES NO a 27 December 2008 17:00:49 0 1 3017662510 NO NO NO
    9420 674600023 /prog26/oracle/admin/X4450/arch/archX4450.log1_9420.dbf 1 1 9420 9085999921960 23 August 2008 21:12:37 9091065312654 December 27, 2008 17:00:44 9091068116124 27 December 2008 20:53:38 102386 512 ARCH ARCH no YES NO a 27 December 2008 20:53:43 0 1 3017662510 NO NO NO
    9421 674620207 /prog26/oracle/admin/X4450/arch/archX4450.log1_9421.dbf 1 1 9421 9085999921960 23 August 2008 21:12:37 9091068116124 December 27, 2008 20:53:38 9091068973106 December 28, 2008 02:30:02 102398 512 ARCH ARCH no YES NO a December 28, 2008 02:30:07 0 1 3017662510 NO NO NO
    9422 674632413 /prog26/oracle/admin/X4450/arch/archX4450.log1_9422.dbf 1 1 9422 9085999921960 23 August 2008 21:12:37 9091068973106 December 28, 2008 02:30:02 9091069195751 December 28, 2008 05:53:29 64635 512 ARCH ARCH no YES NO a December 28, 2008 05:53:33 0 1 3017662510 NO NO NO

    From what I can understand with so many archives (8) in the id space 3-5 minute too high. You need to think about increasing the size redolog say about 500 MB in your case. The rule says 1 switch journal every 20 minutes... It IS a statistic of rush hour?

    And in this mode, your Dataguard works?

    Protection maximum/availability/performance?

    Published by: Maran Viswarayar March 10, 2009 10:22

  • What is the purpose of waiting for redo log files

    Hello

    What is the purpose of the log files waiting for redo in the Dr?

    What happens if the standby redo log files are created? or else is not created?

    Please explain

    Thank you

    Re: what is the difference between onlinelog and standbylog

    I mentioned the goal of the eve of the redo log in RD files in above thread.

    Concerning
    Girish Sharma

  • Lack of redo log group

    10G.2 ORacle vErsion on HP - UX11.31 (archivelog mode)

    I have 3 redo group, each group of redo 1 Redo memmber; If my group again 3 become missing or corrupted (and I can't start my dabatase), how can I recover my database?

    RESETLOGS option requires one case when you lost all the group not an individual group

    SQL> shutdown immediate
    Database closed.
    Database dismounted.
    ORACLE instance shut down.
    SQL> startup
    ORACLE instance started.
    
    Total System Global Area  171966464 bytes
    Fixed Size                   787988 bytes
    Variable Size             145750508 bytes
    Database Buffers           25165824 bytes
    Redo Buffers                 262144 bytes
    Database mounted.
    ORA-00313: open failed for members of log group 3 of thread 1
    ORA-00312: online log 3 thread 1:
    'F:\ORACLE\PRODUCT\10.1.0\ORADATA\PROD\REDO03.LOG'
    
    SQL> shutdown immediate
    ORA-01109: database not open
    
    Database dismounted.
    ORACLE instance shut down.
    SQL> startup mount
    ORACLE instance started.
    
    Total System Global Area  171966464 bytes
    Fixed Size                   787988 bytes
    Variable Size             145750508 bytes
    Database Buffers           25165824 bytes
    Redo Buffers                 262144 bytes
    Database mounted.
    SQL> alter database open resetlogs
      2  /
    alter database open resetlogs
    *
    ERROR at line 1:
    ORA-01139: RESETLOGS option only valid after an incomplete database recovery
    

    To Op

    http://download.oracle.com/docs/cd/B19306_01/backup.102/b14191/recoscen.htm#i1006437
    

    Khurram

  • How to create Redo Log as a good way to avoid the problem of performance

    Hi Experts,

    I work in the following environment.

    OS - Windows server 2012

    version - 11.2.0.1.0

    Server: production server

    1 to 10 of each month, we have huge process. Like many DML and ddl involve.

    I've implemented the RMAN also.

    My Alerts log entry is as below,

    Kills Sep 08 17:05:34 2015

    Thread 1 cannot allot of new newspapers, 88278 sequence

    Private stream flush is not complete

    Currently journal # 1, seq # 88277 mem # 0: D:\APP\ADMINISTRATOR\ORADATA\AWSPROCESS\REDO01. JOURNAL

    Thread 1 Advanced to record the sequence 88278 (switch LGWR)

    Currently Journal # 2 seq # 88278 mem # 0: D:\APP\ADMINISTRATOR\ORADATA\AWSPROCESS\REDO02. JOURNAL

    Kills Sep 08 17:05:38 2015

    Archived journal 81073 extra for each sequence 1 88277 0x38b3fdf6 dest ID thread entry 1:

    Kills Sep 08 17:05:52 2015

    Thread 1 cannot allot of new newspapers, sequence 88279

    Checkpoint is not complete

    Currently Journal # 2 seq # 88278 mem # 0: D:\APP\ADMINISTRATOR\ORADATA\AWSPROCESS\REDO02. JOURNAL

    Thread 1 Advanced to record the sequence 88279 (switch LGWR)

    Currently Journal # 3 seq # 88279 mem # 0: D:\APP\ADMINISTRATOR\ORADATA\AWSPROCESS\REDO03. JOURNAL

    Kills Sep 08 17:05:58 2015

    Archived journal 81074 extra for each sequence 1 88278 0x38b3fdf6 dest ID thread entry 1:

    Kills Sep 08 17:06:16 2015

    Thread 1 cannot allot of new newspapers, sequence 88280

    Checkpoint is not complete

    When I check in the internet I found a few points and need clarity also by the following.

    -It is recommended that this switch Redo log 5 times maximum per hour, but I have this time of maximum peak about 100 redo log changes occur.

    -It is recommended to have the large size of the Redo log. But I have 3 Group of redo and each size is 50 MB by default.

    -My group of Redo log not multiplexed and it by default with each group have only a single Member

    Group 1 - D:\APP\ADMINISTRATOR\ORADATA\AWSPROCESS\REDO01. JOURNAL

    Group 2 - D:\APP\ADMINISTRATOR\ORADATA\AWSPROCESS\REDO02. JOURNAL

    Group 3 - D:\APP\ADMINISTRATOR\ORADATA\AWSPROCESS\REDO03. JOURNAL

    And advised by experts with add that again group will give more performance in the other location. Is it mean that I need to add the Redo log as a different group, player or Redo Log itself I need to replace the other location.

    Say in the end, My Live server works with the location and size of restore default. I'm trying to create a better way and get all confused

    How to do it perfectly.

    Experts, please share your comments to my environment to log redo instance as better through your comment or recommended weblink based on my above needs, or a document.

    Thanks in advance, if you need more information to help me, then ask me, I'll share you.

    Hello

    You can't resize an existing redo log group.

    You will need to create 3 new redo log groups and drop old log redo (with 200 MB size) groups.

    Here you can find a good explanation: DBA for Oracle tips Archives

  • Will be database Oracle 10 g / 11g run without redo logs?

    I was asked in an interview with tech:

    What is an Oracle Database 10 g / 11g continue to run if someone or something corrupt any of its redo logs?

    I believe that the answer is Yes.

    I tested the removal of all newspapers of redo of an Oracle 11.1.0.7 running database, and I was still able to create a new table, perform an insertion and validation.

    When I stop and restart the database however, of course, he complained lack of recovery logs.

    Assuming that never stop you the database, the database continues to function without error, without no redo logs?

    Is the database from functioning normally without redo logs? Are newspapers in recovery in the event of failure of the user, instance or media, and recover from these situations?

    The documentation I've read does not address what happens if corrupt you recovery logs but more data files in the case of media/disk failures.

    MetaLink notes or documents or first hand experience would be appreciated.

    Snake

    In fact, you are right, and the captain himself, Oracle Database 10 g / 11 g will not run if all is redo logs have been deleted or corrupted by all means. Play well!

  • 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

  • Recreate the Member lost/damaged redo log in a group

    DB version: 11.2.0.4

    OS: Oracle Linux 6.5

    In this particular PB we have multiplexes recovery logs (2 members from each group of redo).

    If one member of a group of Redo log is corrupted then, regardless of whether the Member belonged to the Group that is CURRENT, ACTIVE or INACTIVE, can we just let GO and CREATE the file journal lost this group member by following the steps below?

    -Find the corrupted Member

    SELECT GROUP #, STATUS, MEMBER OF V$ LOGFILE WHERE STATUS = 'INVALID ';

    1 back UP the DB

    2. CHANGE THE SYSTEM CHECKPOINT;

    3 ALTER DATABASE CLEAR LOGFILE GROUP 3;  - , This step should not be executed. Right?

    4. ALTER DATABASE DROP LOGFILE MEMBER ' / oracle/oradata/wms/redo02.log';

    (Apparently, this removes not the logfile at the OS level, only the control file is updated in the DB)

    5 ALTER DATABASE ADD LOGFILE MEMBER ' / oracle/oradata/wms/redo02b.log' to GROUP 3.

    When I googled for steps, I found the table below in the official documentation of the Oracle. This table is applicable only if the ENTIRE REDO LOG disappeared.

    http://docs.Oracle.com/CD/E25054_01/backup.1111/e10642/osadvsce.htm#CACFJDBG

    I want just the steps if only 1 member of a multiplex group is lost/damaged.

    3. ALTER DATABASE CLEAR LOGFILE GROUP 3;  -This step should not be executed. Right?

    Yes. It's true. You can refer to the section 'Recovery after losing a member of the a multiplex online Redo Log group' under recovery after the loss of online redo log files: scenarios

    HTH

    -Jonathan Rolland

  • Redo log size of the defect of EBS

    Hi all

    EBS R12.2.4

    11 GR 2

    Rhel6.5

    I noticed that the installation by dΘfaut of EBS has only two 1 GB size redo log groups.

    Is this acceptable to perform better?

    Your comment is very much appreciated.

    Thank you very much

    JC

    Protection for the primary database in three ways:

    Maximum availability: Transactions on the primary do not commit to redo information was written for the online redo log and newspapers awaiting restoration by progression of at least a place to sleep. If no location intelligence is available, it in the same way as the maximum performance mode until a standby is available again.
    Maximum performance: Transactions on the validation of primary as soon as redo information has been written for the online redo log. Transfer of information to roll forward to the standby server is asynchronous, so it has no impact on the performance of the primary.
    Maximum protection: the Transactions on the primary do not commit to redo information was written for the online redo log and newspapers awaiting restoration by progression of at least a place to sleep. If the standby not suitable location is available, the primary database stops.

    By default, a newly created Eve, the primary database is in maximum performance mode.

    I suggest to use the maximum performance with delay mode in the application of 15 minutes. You can drop the idea of delay if you are not comfortable with data loss

    concerning

    Pravin

  • Waiting for redo log file missing when restore main database using RMAN backup that was taken on the database physical standby

    Here's my question after tons of research and test without have the right solutions.

    Target:

    (1) I have a 12.1.0.2 database unique main enterprise 'testdb' as database instance running on the server "node1".

    (2) I created physical standby database "stbydb" on the server "node2".

    (3) DataGuard running on the mode of MaxAvailability (SYNC) with roll forward in real time 12 default c apply.

    (4) primary database has 3 groups of one-man redo. (/oraredo/testdb/redo01.log redo02.log redo03.log)

    (5) I've created 4 standby redo logfiles (/oraredo/testdb/stby01.log stby02.log stby03.log stby04.log)

    (6) I do RMAN backup (database and archivelog) on the site of relief only.

    (7) I want to use this backup for full restore of the database on the primary database.

    He is a DR test to simulate the scenario that has lost every primary & Eve total servers.

    Here is how to save, on the database pending:

    (1) performance 'alter database recover managed standby database Cancel' to ensure that compatible data files

    (2) RMAN > backup database;

    (3) RMAN > backup archivelog all;

    I got elements of backup and copied to primary db Server something like:

    /Home/Oracle/backupset/o1_mf_nnndf_TAG20151002T133329_c0xq099p_.BKP (data files)

    /Home/Oracle/backupset/o1_mf_ncsnf_TAG20151002T133329_c0xq0sgz_.BKP (spfile & controlfile)

    /Home/Oracle/backupset/o1_mf_annnn_TAG20151002T133357_c0xq15xf_.BKP (archivelogs)

    So here's how to restore, on the main site:

    I clean all the files (data files, controlfiles oder all gone).

    (1) restore spfile from pfile

    RMAN > startup nomount

    RMAN > restore spfile from pfile ' / home/oracle/pfile.txt' to ' / home/oracle/backupset/o1_mf_ncsnf_TAG20151002T133329_c0xq0sgz_.bkp';

    (2) modify pfile to convert to db primary content. pFile shows below

    *.audit_file_dest='/opt/Oracle/DB/admin/testdb/adump '

    * .audit_trail = "db".

    * full = '12.1.0.2.0'

    *.control_files='/oradata/testdb/control01.ctl','/orafra/testdb/control02.ctl'

    * .db_block_size = 8192

    * .db_domain = "

    *.db_file_name_convert='/testdb/','/testdb /'

    * .db_name = "testdb".

    * .db_recovery_file_dest ='/ orafra'

    * .db_recovery_file_dest_size = 10737418240

    * .db_unique_name = "testdb".

    *.diagnostic_dest='/opt/Oracle/DB '

    * .fal_server = "stbydb".

    * .log_archive_config = 'dg_config = (testdb, stbydb)'

    * .log_archive_dest_2 = "service = stbydb SYNC valid_for = (ONLINE_LOGFILE, PRIMARY_ROLE) db_unique_name = stbydb'"

    * .log_archive_dest_state_2 = 'ENABLE '.

    *.log_file_name_convert='/testdb/','/testdb /'

    * .memory_target = 1800 m

    * .open_cursors = 300

    * runoff = 300

    * .remote_login_passwordfile = "EXCLUSIVE."

    * .standby_file_management = "AUTO".

    * .undo_tablespace = "UNDOTBS1.

    (3) restart db with updated file pfile

    SQLPLUS > create spfile from pfile='/home/oracle/pfile.txt'

    SQLPLUS > the judgment

    SQLPLUS > startup nomount

    (4) restore controlfile

    RMAN > restore primary controlfile to ' / home/oracle/backupset/o1_mf_ncsnf_TAG20151002T133329_c0xq0sgz_.bkp';

    RMAN > change the editing of the database

    (5) all elements of backup catalog

    RMAN > catalog starts by ' / home/oracle/backupset / '.

    (6) restore and recover the database

    RMAN > restore database;

    RMAN > recover database until the SNA XXXXXX; (this YVERT is the maximum in archivelog backups that extends beyond the scn of the backup of the data file)

    (7) open resetlogs

    RMAN > alter database open resetlogs;

    Everything seems perfect, except one of the file log roll forward pending is not generated

    SQL > select * from v$ standby_log;

    ERROR:

    ORA-00308: cannot open archived log ' / oraredo/testdb/stby01.log'

    ORA-27037: unable to get file status

    Linux-x86_64 error: 2: no such file or directory

    Additional information: 3

    no selected line

    I intended to use the same backup to restore primary basic & helps record traffic and the downtime between them in the world of real output.

    So I have exactly the same steps (except STANDBY restore CONTROLFILE and not recover after database restore) to restore the database pending.

    And I got the same missing log file.

    The problem is:

    (1) complete alert.log filled with this error, not the concern here

    (2) now repeat it in real time apply won't work since the Party shall LGWR shows always "WAITING_FOR_LOG."

    (3) I can't delete and re-create this log file

    Then I tried several and found:

    The missing standby logfile was still 'ACTIVE' at present RMAN backup was made.

    For example, on db standby, under Group #4 (stby01.log) would be lost after the restoration.

    SQL > select GROUP #, SEQUENCE #, USE (s), the STATUS from v$ standby_log;

    GROUP # SEQUENCE # USED STATUS

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

    4 19 ACTIVE 133632

    5 0 0 UNASSIGNED

    6 0 0 not ASSIGNED

    7 0 0 UNASSIGNED

    So until I take the backup, I tried on the primary database:

    SQL > alter system set log_archive_dest_state_2 = delay;

    This was the Group of standby_log side Eve #4 was released:

    SQL > select GROUP #, SEQUENCE #, USE (s), the STATUS from v$ standby_log;

    GROUP # SEQUENCE # USED STATUS

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

    4 0 0 UNASSIGNED

    5 0 0 UNASSIGNED

    6 0 0 not ASSIGNED

    7 0 0 UNASSIGNED

    Then, the backup has been restored correctly without missing standby logfile.

    However, to change this primary database means break DataGuard protection when you perform the backup. It's not accept on the production environment.

    Finally, my real questions come:

    (1) what I do may not do on parameter change?

    (2) I know I can re-create the control file to redo before delete and then recreate after. Is there any simple/fast to avoid the standby logfile lost or recreate the lost one?

    I understand that there are a number of ways to circumvent this. Something to keep a copy of the log file waiting restoration progress and copy up one missing, etc, etc...

    And yes I always have done no real-time applies "to the aid of archived logfile" but is also not accept mode of protection of production.

    I just want proof that the design (which is displayed in a few oracle doc Doc ID 602299.1 is one of those) that backs up data backup works effectively and can be used to restore the two site. And it may be without spending more time to resume backups or put the load on the primary database to create the database before.

    Your idea is very much appreciated.

    Thank you!

    Hello

    1--> when I take via RMAN backup, RMAN does not redo log (ORL or SRL) file, so we cannot expect ORLs or SRL would be restored.

    2nd--> when we opened the ORL database should be deleted and created

    3rd--> Expecting, SRL should not be an issue.we should be able to do away with the fall.

    DR sys@cdb01 SQL > select THREAD #, SEQUENCE #, GROUP #, STATUS from v$ standby_log;

    THREAD # SEQUENCE # GROUP # STATUS

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

    1 233 4 ACTIVE

    1 238 5 ACTIVE

    DR sys@cdb01 SQL > select * from v$ logfile;

    GROUP # STATUS TYPE MEMBER IS_ CON_ID

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

    3 /u03/cdb01/cdb01/redo03.log no. 0 online

    /U03/cdb01/cdb01/redo02.log no. 0 2 online

    1 /u03/cdb01/cdb01/redo01.log no. 0 online

    4 /u03/cdb01/cdb01/stdredo01.log WATCH No. 0

    /U03/cdb01/cdb01/stdredo02.log EVE 5 No. 0

    DR sys@cdb01 SQL > ! ls - ltr /u03/cdb01/cdb01/stdredo01.log

    method: cannot access the /u03/cdb01/cdb01/stdredo01.log: no such file or directory

    DR sys@cdb01 SQL >! ls - ltr /u03/cdb01/cdb01/stdredo02.log

    -rw - r-. 1 oracle oinstall 52429312 17 Oct 15:32 /u03/cdb01/cdb01/stdredo02.log

    DR sys@cdb01 SQL > alter database force claire logfile 4;

    change the database group claire logfile 4

    *

    ERROR on line 1:

    ORA-01156: recovery or current flashback may need access to files

    DR sys@cdb01 SQL > alter database recover managed standby database cancel;

    Database altered.

    DR sys@cdb01 SQL > change the database group claire logfile 4;

    Database altered.

    DR sys@cdb01 SQL > ! ls - ltr /u03/cdb01/cdb01/stdredo01.log

    -rw - r-. 1 oracle oinstall 52429312 17 Oct 15:33 /u03/cdb01/cdb01/stdredo01.log

    DR sys@cdb01 SQL >

    If you do, you can recreate the controlfile without waiting for redo log entry...

    If you still think it's something is not acceptable, you must have SR with support to analyze why he does not abandon SRL when controlfile_type is "underway".

    Thank you

  • Loss/Corruption of a Redo Log multiplex group member

    Grid infrastructure: 11.2.0.4

    DB version: 11.2.0.4

    OS: RHEL 6.5

    All recovery logs are multiplexed IE once. Copy of a mirror

    I created a document on how to cope with the loss of a member of a group of Redo Log multiplex. It applies to DBs in ASM or Linux Filesystem.

    If a member of a multiplex redo logs group is lost/damaged is in State assets or CURRENT (v$ log.status), will be the following work?

    Assuming that the DB would not crash (well that's the whole point of multiplexing)

    Step 1. Switch redo log group and bring him to the INACTIVE State IE. LGWR is not written for her now


    Step 2. Remove the Member lost/damaged.

    ALTER DATABASE DROP LOGFILE MEMBER "+ DATA_DG1/mbhsprd/onlinelog/group_1.256.834497203";

    Apparently, this command does not actually remove the log file at the level of the ASM/OS; It updates only the control file

    Step 3. If it is a corrupt then log file physically remove the damaged location ASM/OS file

    Step 4. I hope the below will create a mirror copy of the survivor

    ALTER DATABASE ADD LOGFILE MEMBER '+ DATA_DG1/mbhsprd/onlinelog/group_1.256.834497203' to GROUP 3.

    The above steps won't work?

    There is no point in writing in the document if you do not actually test what you write

    It seems that you are working with Oracle managed files. In this case:

    You will find that your "apparently" in step 2 is not correct, and that your step 4 will throw an ora-01276.

Maybe you are looking for