Professional Documents
Culture Documents
El multiplexar es una opcin que nos ayuda a reducir el riesgo de falla en la base de
datos Oracle.
Para multiplexar los redo logs se debe proceder de la siguiente manera:
Paso 1: Realizamos un select a la siguiente vista para determinar la configuracin
actual de los redo logs de la base de datos:
SELECT * FROM V$LOGFILE;
Paso 2: Ejecutamos el comando ALTER DATABASE para generar miembros en cada
grupo de redo logs:
ALTER DATABASE ADD LOGFILE MEMBER /oracle/dbs/log2b.log TO GROUP 2;
Nota: Cuando adicionamos un miembro a un redo log group no es necesario especificar
el tamao, por consiguiente, todos los redo log files en el grupo sern del mismo
tamao.
Paso 3: Verificamos otra vez la vista V$LOGFILE para verificar que se ha aadido el
nuevo miembro al grupo:
SELECT * FROM V$LOGFILE;
$ rman nocatalog;
RMAN> CONNECT TARGET;
RMAN> RESTORE CONTROLFILE TO +DISCO_FLASH FROM
+DISCO_DATOS/ruta/nombre_ctl;
Se identifica en este momento el nombre del controlfile en la flash; teniendo en cuenta que estamos
haciendo uso de OMF, no sabemos qu nombre le va a poner Oracle al segundo controlfile, por eso
es imprescindible este paso. sto se pude hacer desde SQLPLUS (como se puede observar ms
arriba) o con la nueva herramienta proporcionada por Oracle 10.2, ASMCMD:
$ asmcmd
ASMCMD> CD +DISCO_FLASH
ASMCMD> FIND -t controlfile*
Modificar ahora el SPFILE. Esto se puede hacer desde cualquier nodo cuando estamos en un
entorno Oracle RAC:
SQL> ALTER SYSTEM SET CONTROL_FILES =
+DISCO_DATOS/ruta/nombre_ctl,'+DISCO_FLASH/ruta/nombre_ctl;
SQL> SHUTDOWN IMMEDIATE;
SQL> CONN / AS SYSDBA
SQL> STARTUP;
PUBLICADO POR RODOLFO CNDIDO EN 11:3
GROUP# STATUS
TYPE
MEMBER
IS_
GROUP#
THREAD# SEQUENCE#
FIRST_CHANGE# FIRST_TIM
BYTES
1
799976 01-MAY-12
11
52428800
1 YES INACTIVE
2
800427 01-MAY-12
12
52428800
1 NO
3
779491 29-APR-12
10
52428800
1 YES INACTIVE
CURRENT
As shown above, Group 2 was the CURRENT one and Group 3 becomes CURRENT one after switching log.
System altered.
GROUP#
THREAD# SEQUENCE#
FIRST_CHANGE# FIRST_TIM
BYTES
11
52428800
1 YES INACTIVE
2
800427 01-MAY-12
12
52428800
1 YES ACTIVE
3
802153 01-MAY-12
13
52428800
1 NO
CURRENT
System altered.
GROUP#
THREAD# SEQUENCE#
FIRST_CHANGE# FIRST_TIM
BYTES
11
52428800
1 YES INACTIVE
2
800427 01-MAY-12
12
52428800
1 YES INACTIVE
3
802153 01-MAY-12
13
52428800
1 NO
CURRENT
Database altered.
GROUP#
THREAD# SEQUENCE#
FIRST_CHANGE# FIRST_TIM
BYTES
11
52428800
1 YES INACTIVE
2
800427 01-MAY-12
12
52428800
1 YES INACTIVE
3
802153 01-MAY-12
13
52428800
2 NO
CURRENT
Database altered.
GROUP#
THREAD# SEQUENCE#
FIRST_CHANGE# FIRST_TIM
BYTES
1
799976 01-MAY-12
11
52428800
1 YES INACTIVE
2
800427 01-MAY-12
12
52428800
1 YES INACTIVE
3
802153 01-MAY-12
13
52428800
3 NO
CURRENT
MEMBER
-----------------------------------------------------G:\ORACLE\PRODUCT\10.2.0\ORADATA\ORCL1\REDO03.LOG
G:\ORACLE\PRODUCT\10.2.0\ORADATA\ORCL1\REDO03A.LOG
G:\ORACLE\PRODUCT\10.2.0\ORADATA\ORCL1\REDO03B.LOG
It is not possible to drop CURRENT Group but we can drop any other GROUP.
group 3;
group 3
*
ERROR at line 1:
ORA-01623: log 3 is current log for instance orcl1 (thread 1) - cannot
drop
group 1;
Database altered.
GROUP#
THREAD# SEQUENCE#
FIRST_CHANGE# FIRST_TIM
BYTES
12
52428800
1 YES INACTIVE
3
802153 01-MAY-12
13
52428800
3 NO
CURRENT
While adding Group again, you may consider all the groups to be of same size (better practice).
Database altered.
GROUP#
THREAD# SEQUENCE#
FIRST_CHANGE# FIRST_TIM
BYTES
52428800
1 YES UNUSED
2
800427 01-MAY-12
12
52428800
1 YES INACTIVE
3
802153 01-MAY-12
13
52428800
3 NO
CURRENT
MEMBER
---------------------------------------------------------------------------------------------------G:\ORACLE\PRODUCT\10.2.0\FLASH_RECOVERY_AREA\ORCL1\ONLINELOG\O1_MF_1_7T01
969R_.LOG
While trying to add member for GROUP 1, it will generate error for same file name. we need to delete it
physically as it's not an OMF FILE.
Database altered.
Database altered.
Database altered.
GROUP#
THREAD# SEQUENCE#
FIRST_CHANGE# FIRST_TIM
BYTES
52428800
4 YES UNUSED
2
805988 01-MAY-12
17
52428800
1 YES INACTIVE
3
806007 01-MAY-12
18
52428800
3 NO
CURRENT
Now, let's try to drop this OMF redo file, will encounter error eventually as it is still unused. switch log file to
avoid this error.
System altered.
GROUP#
THREAD# SEQUENCE#
FIRST_CHANGE# FIRST_TIM
BYTES
19
52428800
4 NO
2
805988 01-MAY-12
17
52428800
3 YES INACTIVE
3
806007 01-MAY-12
18
52428800
3 YES ACTIVE
System altered.
CURRENT
GROUP#
THREAD# SEQUENCE#
FIRST_CHANGE# FIRST_TIM
BYTES
19
52428800
4 YES ACTIVE
2
806404 01-MAY-12
20
52428800
3 NO
3
806007 01-MAY-12
18
52428800
3 YES ACTIVE
CURRENT
Database altered.
GROUP#
THREAD# SEQUENCE#
FIRST_CHANGE# FIRST_TIM
BYTES
19
52428800
3 YES ACTIVE
2
806404 01-MAY-12
20
52428800
1 NO
CURRENT
3
806007 01-MAY-12
18
52428800
3 YES ACTIVE
Let's Multiplex Members for Group 2. Here, all members are placed in same location but it's just a demo.
Multiplexing must be done on different disk or disk controllers.
Database altered.
Database altered.
GROUP#
THREAD# SEQUENCE#
FIRST_CHANGE# FIRST_TIM
BYTES
1
806398 01-MAY-12
19
52428800
3 YES ACTIVE
2
806404 01-MAY-12
20
52428800
3 NO
3
806007 01-MAY-12
18
52428800
3 YES ACTIVE
MEMBER
--------------------------------------------------------G:\ORACLE\PRODUCT\10.2.0\ORADATA\ORCL1\REDO01.LOG
G:\ORACLE\PRODUCT\10.2.0\ORADATA\ORCL1\REDO01A.LOG
G:\ORACLE\PRODUCT\10.2.0\ORADATA\ORCL1\REDO01B.LOG
G:\ORACLE\PRODUCT\10.2.0\ORADATA\ORCL1\REDO02.LOG
G:\ORACLE\PRODUCT\10.2.0\ORADATA\ORCL1\REDO02A.LOG
G:\ORACLE\PRODUCT\10.2.0\ORADATA\ORCL1\REDO02B.LOG
G:\ORACLE\PRODUCT\10.2.0\ORADATA\ORCL1\REDO03.LOG
G:\ORACLE\PRODUCT\10.2.0\ORADATA\ORCL1\REDO03A.LOG
G:\ORACLE\PRODUCT\10.2.0\ORADATA\ORCL1\REDO03B.LOG
CURRENT