0% found this document useful (0 votes)
4 views

(Checkpoint Not Completed) Solve It by Resizing Redo Logs

The document details steps to add new redo log groups and drop unneeded redo log groups from an Oracle database. It reviews existing redo logs, adds 3 new groups, verifies the status of all groups, and provides instructions for dropping inactive redo log groups no longer needed.

Uploaded by

Sudhir Kushwaha
Copyright
© © All Rights Reserved
Available Formats
Download as PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
4 views

(Checkpoint Not Completed) Solve It by Resizing Redo Logs

The document details steps to add new redo log groups and drop unneeded redo log groups from an Oracle database. It reviews existing redo logs, adds 3 new groups, verifies the status of all groups, and provides instructions for dropping inactive redo log groups no longer needed.

Uploaded by

Sudhir Kushwaha
Copyright
© © All Rights Reserved
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 3

*********************** ADD Drop Redo logs **************************************

********************** **************************************

Step#01:
------

Review information on existing redo logs.

SELECT a.group#, b.member, a.status, a.bytes/1024/1024 FROM v$log a, v$logfile b WHERE


a.group#=b.group# ;

SQL> SELECT a.group#, b.member, a.status, a.bytes FROM v$log a, v$logfile b WHERE
a.group#=b.group#
2 ;

GROUP# MEMBER STATUS BYTES


------ ---------------------------------------------------------------------- ---------- ----------
2 /u02/oradata/afic/REDO02.LOG INACTIVE 52428800
1 /u02/oradata/afic/REDO01.LOG CURRENT 52428800
3 /u02/oradata/afic/REDO03.LOG ACTIVE 52428800
1 /u01/app/oracle/oradata/redo01a.log CURRENT 52428800
2 /u01/app/oracle/oradata/redo02a.log INACTIVE 52428800
3 /u01/app/oracle/oradata/redo03a.log ACTIVE 52428800
SQL>

****************************************************************************************************

Step#02:
------

2. Add new groups :


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

ALTER DATABASE ADD LOGFILE group 8 (’/u02/oradata/afic/redo08.log’,


’/u01/app/oracle/oradata/redo08a.log ’) SIZE 512M;

ALTER DATABASE ADD LOGFILE group 9 (’/u02/oradata/afic/redo09.log’,


’/u01/app/oracle/oradata/redo09a.log ’) SIZE 512M;

ALTER DATABASE ADD LOGFILE group 10 (’/u02/oradata/afic/redo10.log’,


’/u01/app/oracle/oradata/redo10a.log ’) SIZE 512M;

****************************************************************************************************

Step#03:
------
3. Check the status on all redo logs again.

SELECT a.group#, b.member, a.status, a.bytes FROM v$log a, v$logfile b WHERE a.group#=b.group# ;

SQL> SELECT a.group#, b.member, a.status, a.bytes FROM v$log a, v$logfile b WHERE
a.group#=b.group# ;

GROUP# MEMBER STATUS BYTES


------ ---------------------------------------------------------------------- ---------- ----------
2 /u02/oradata/afic/REDO02.LOG CURRENT 52428800
1 /u02/oradata/afic/REDO01.LOG INACTIVE 52428800
3 /u02/oradata/afic/REDO03.LOG INACTIVE 52428800
1 /u01/app/oracle/oradata/redo01a.log INACTIVE 52428800
2 /u01/app/oracle/oradata/redo02a.log CURRENT 52428800
3 /u01/app/oracle/oradata/redo03a.log INACTIVE 52428800
8 /u02/oradata/afic/redo08.log UNUSED 536870912
8 /u01/app/oracle/oradata/redo08a.log UNUSED 536870912
9 /u02/oradata/afic/redo09.log UNUSED 536870912
9 /u01/app/oracle/oradata/redo09a.log UNUSED 536870912
10 /u02/oradata/afic/redo10.log UNUSED 536870912
10 /u01/app/oracle/oradata/redo10a.log UNUSED 536870912

****************************************************************************************************

Step#04:
------

4. Drop the online redo log groups that are not needed. You must have the ALTER DATABASE system
privilege.

a. An instance requires at least two groups of online redo log files, regardless of the number of members
in the groups. (A group is one or more members.)

b. You can drop an online redo log group only if it is INACTIVE. If you need to drop the current group, first
force a log switch to occur.

By using this command :

ALTER SYSTEM SWITCH LOGFILE;

c. Make sure an online redo log group is archived (if archiving is enabled) before dropping it. This can be
determined by:
d. Check that the group is inactive and archived before dropping it .

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

ALTER DATABASE DROP LOGFILE GROUP 2;

You might also like