The document outlines procedures for managing online redo logs in a database, including increasing log sizes, enabling multiplexing, and recovering from various log loss scenarios. It provides SQL commands for verifying existing logs, adding new log files, resizing logs, and recovering databases not in archive log mode. Additionally, it details steps for database recovery using backup control files when archive logs are unavailable.
The document outlines procedures for managing online redo logs in a database, including increasing log sizes, enabling multiplexing, and recovering from various log loss scenarios. It provides SQL commands for verifying existing logs, adding new log files, resizing logs, and recovering databases not in archive log mode. Additionally, it details steps for database recovery using backup control files when archive logs are unavailable.
The document outlines procedures for managing online redo logs in a database, including increasing log sizes, enabling multiplexing, and recovering from various log loss scenarios. It provides SQL commands for verifying existing logs, adding new log files, resizing logs, and recovering databases not in archive log mode. Additionally, it details steps for database recovery using backup control files when archive logs are unavailable.
The document outlines procedures for managing online redo logs in a database, including increasing log sizes, enabling multiplexing, and recovering from various log loss scenarios. It provides SQL commands for verifying existing logs, adding new log files, resizing logs, and recovering databases not in archive log mode. Additionally, it details steps for database recovery using backup control files when archive logs are unavailable.
Download as TXT, PDF, TXT or read online from Scribd
Download as txt, pdf, or txt
You are on page 1/ 4
onlineredo log management
CHG000021 Increase the Redo log size for all listeddatabases.
CHG000022 Enable multiplexing of redo log files CHG000023 Recovering After Losing a Member of a Multiplexed Online Redo Log Group CHG000024 Losing an Inactive Online Redo Log group CHG000025 Losing an Active Online Redo Log Group CHG000026 Losing an Current Online Redo Log Group CHG000027 Database recovery if database is not running archive log mode
ALTER DATABASE ADD LOGFILE group 5 ('/u02/oradata/vdscp/redo05a.log',
'/u02/oradata/vdscp/redo05b.log','/u02/oradata/vdscp/redo05c.log') SIZE 512M; ALTER DATABASE ADD LOGFILE group 6 ('/u02/oradata/vdscp/redo06a.log', '/u02/oradata/vdscp/redo06b.log','/u02/oradata/vdscp/redo06c.log') SIZE 512M;
alter database add logfile group 4 ('+AP_DATA','+AP_FRA') size 512M;
alter database add logfile group 5 ('+AP_DATA','+AP_FRA') size 512M;
alter database add logfile group 6 ('+AP_DATA','+AP_FRA') size 512M;
--------------------------------------- HOW TO RESIZE THE ONLINE REDO LOGS: --------------------------------------- CHG000021 Increase the Redo log size for all listeddatabases. no we can't resize the redolog files we can add the new groups with new size and drop the old groups
a) first see the size of current group
select group# bytes status from v$log;
b)retrieve the all member names for all groups
select group member from v$logfile;
c) now create the new log group
alter database add log file group 4 '/u02/oradata/vdscp/log4vdscp.dbf' size 10m;
d) now verify the status of groups
select group# status from v$log;
c) switch ontill group 4 into current ,
alter system switch logfile;
verify the status
d) now drop the old groups
alter database drop logfile group 1;
%rm /u02/oradata/vdscp/log1vdscp.dbf'
************************************************* How to do database recovery if database is not running archive log mode or Archvie logs are not available for complete recovery. ----------------------------------------------------------------------------------- ------------------------------------------------
We can recover database even if database is not running archive log mode OR archive logs are not available for recovery. Please find the below steps --------- Step 1 : ---------
SQL> startup mount
SQL> recover automatic database using backup controlfile;
------- Step2 : -------
Open a new terminal and find CURRENT online redologfile.
set lines 900
set pages 900 col member for a55;
select group#,member from v$logfile;
select group#,members,status from v$log;
--------- Step 3 : --------- NOTE : If Log applied and Media recovery complete Then open the database with reset logs
alter database open resetlogs;
----------------------------- Please find the below logs : ----------------------------- SQL> startup mount
ORACLE instance started.
Total System Global Area 2538893312 bytes
Fixed Size 2283824 bytes
Variable Size 671090384 bytes
Database Buffers 1845493760 bytes
Redo Buffers 20025344 bytes
Database mounted.
SQL> recover automatic database using backup controlfile;
ORA-00279: change 72197053 generated at 07/19/2019 19:17:24 needed for thread 1
