Skip to main content

Adding or Dropping of Redo and StandBy Redo file in Dataguard Standby Environment

 

Adding or Dropping Redo and StandBy Redo files in Dataguard Standby Environment

On Standby Server


Redo Log File

1.0.
ALTER DATABASE RECOVER MANAGED STANDBY DATABASE CANCEL;

1.1.

Show parameter STANDBY_FILE_MANAGEMENT
ALTER SYSTEM SET STANDBY_FILE_MANAGEMENT = MANUAL;

1.2.

set line 400 pages 150
col GROUP# for 99
col THREAD# for 99
col STATUS for a9
col MEMBERS for 999999
col member for a64
select l.GROUP#,l.THREAD#,l.STATUS,l.MEMBERS,f.member from v$log l inner join v$logfile f on (l.GROUP#=f.GROUP#);

1.3.

ALTER DATABASE ADD LOGFILE '/u01/app/oracle/oradata/cbsdgdb1/redo01.log' SIZE 1024M;
ALTER DATABASE ADD LOGFILE '/u01/app/oracle/oradata/cbsdgdb1/redo02.log' SIZE 1024M;
ALTER DATABASE ADD LOGFILE '/u01/app/oracle/oradata/cbsdgdb1/redo03.log' SIZE 1024M;

1.4.

alter system switch logfile;

1.5.

ALTER DATABASE DROP LOGFILE '/u01/app/oracle/oradata/oradbcdb/redo01.log';
ALTER DATABASE DROP LOGFILE '/u01/app/oracle/oradata/oradbcdb/redo02.log';
ALTER DATABASE DROP LOGFILE '/u01/app/oracle/oradata/oradbcdb/redo03.log';

standby redo log file

2.0.
set line 400 pages 150
col GROUP# for 99
col THREAD# for 99
col STATUS for a12
col MEMBERS for 999999
col member for a64
select l.GROUP#,l.THREAD#,l.STATUS,f.member from v$STANDBY_LOG l inner join v$logfile f on (l.GROUP#=f.GROUP#);

2.1.

alter database add standby logfile '/u01/app/oracle/oradata/cbsdgdb1/standbyredo01.log' size 1024m;
alter database add standby logfile '/u01/app/oracle/oradata/cbsdgdb1/standbyredo02.log' size 1024m;
alter database add standby logfile '/u01/app/oracle/oradata/cbsdgdb1/standbyredo03.log' size 1024m;
alter database add standby logfile '/u01/app/oracle/oradata/cbsdgdb1/standbyredo04.log' size 1024m;
alter database add standby logfile '/u01/app/oracle/oradata/cbsdgdb1/standbyredo05.log' size 1024m;

2.2.

ALTER DATABASE DROP STANDBY LOGFILE '/u01/app/oracle/oradata/cbsdgdb2/standby1.log';
ALTER DATABASE DROP STANDBY LOGFILE '/u01/app/oracle/oradata/cbsdgdb2/standby2.log';
ALTER DATABASE DROP STANDBY LOGFILE '/u01/app/oracle/oradata/cbsdgdb2/standby3.log';
ALTER DATABASE DROP STANDBY LOGFILE '/u01/app/oracle/oradata/cbsdgdb2/standby4.log';
ALTER DATABASE DROP STANDBY LOGFILE '/u01/app/oracle/oradata/cbsdgdb2/standby5.log';

2.3.

alter database drop standby logfile group 5;
alter database clear logfile group 5;

2.4.

ALTER SYSTEM SET STANDBY_FILE_MANAGEMENT=AUTO;
ALTER DATABASE RECOVER MANAGED STANDBY DATABASE DISCONNECT;

Labels:

Comments

Post a Comment

Popular posts from this blog

Upgrading Issue for RHEL 7 to 8 With Leapp

Overview The Leapp utility is a framework for updating and upgrading operating systems as well as applications. The operations of this utility consist of two phases 1. the preupgrade Phase – that chack the upgrade possibilities and 2. the actual upgrade phase – that map packages between previous and current versions of the software packages. Issue – 01: After running ‘ sudo leapp preupgrade ‘ sometimes you find the below issue in ‘ /var/log/leapp/leapp-report.txt ‘. Detail: Risk Factor: high (inhibitor) Title: Leapp detected loaded kernel drivers which have been removed in RHEL 8. Upgrade cannot proceed. Summary: Support for the following RHEL 7 device drivers has been removed in RHEL 8: – pata_acpi Key: f08a07da902958defa4f5c2699fae9ec2eb67c5b Remediation: 1. Disable detected kernel drivers in order to proceed with the upgrade process using the rmmod or modprobe -r . rmmod – Simple program to remove a module from the Linux Kernel modprobe – Add and remove modules from the Linux Ke...
Post a Comment
Read more

ORA-00800: soft external error arguments

The problem as stated: After upgrading the Oracle Database from 12c to 19c the following error generated in the alert log file. Actual Oracle Error Code: ORA-00800 After Upgrading from 12c to 19c ORA-00800: soft external error, arguments occured Oracle Database Enterprise 19c fails to start with error: ORA-00800: soft external error, arguments: [Set Priority Failed], [VKTM] Why does Insights prevent Oracle grid services from starting How to configure the User slice to allow Real-Time Scheduling for user processes In Alert Log: Errors in file /u01/app/oracle/diag/rdbms/orclproddbone/orclprod/trace/psbcdb_vktm_3529.trc (incident=1200048) (PDBNAME=CDB$ROOT): ORA-00800: soft external error, arguments: [Set Priority Failed], [VKTM], [Check traces and OS configuration], [Check Oracle document and MOS notes], [] Incident details in: /u01/app/oracle/diag/rdbms/orclproddbone/orclprod/incident/incdir_1200048/psbcdb_vktm_3529_i1200048.trc 2023-10-30T10:04:53.536165+06:00 Error attempting to elev...
Post a Comment
Read more

The Oracle Management Server (OMS) host and port specified via OMS_HOST and EM_UPLOAD_PORT is not available

The Oracle Management Server (OMS) host and port specified via OMS_HOST and EM_UPLOAD_PORT is not available. 1.0. error message: Error Message: The Oracle Management Server (OMS) host and port specified via OMS_HOST and EM_UPLOAD_PORT is not available. Pass in a valid hostname and port number for the OMS to successfully deploy the agent. 1.1. deploy log: Log: /opt/gc_inst/em/EMGC_OMS1/sysman/agentpush/2023-11-07_16-09-23-PM/applogs/dblivesrv_deploy.log Execution of command cd /opt/agent/ADATMP_2023-11-07_16-09-23-PM;/opt/agent/ADATMP_2023-11-07_16-09-23-PM/agentDeploy.sh -ignorePrereqs ORACLE_HOSTNAME=dblivesrv AGENT_BASE_DIR=/opt/agent OMS_HOST=oemsrv.localdomain EM_UPLOAD_PORT=4903 AGENT_INSTANCE_HOME=/opt/agent/agent_inst b_doDiscovery=false START_AGENT=false b_forceInstCheck=true -force AGENT_PORT=3872 on host dblivesrv Failed 1.2. oms details: [oracle@oemsrv ~]$ $OMS_HOME/bin/emctl status oms -details Oracle Enterprise Manager Cloud Control 13c Release 5 Copyright (c) 1996, 2...
Post a Comment
Read more