May 2021

ORA-19527: physical standby redo log must be renamed

Posted on May 27, 2021 by Dataguard Oracle 12c Oracle Database 0

On standby side, you may encountered the Error “ORA-19527: physical standby redo log must be renamed” in the alert log. 

ORA-19527: physical standby redo log must be renamed
ORA-00312: online log 10 thread 1: '/u01/oradata/dev12c/std_redo03.log'

Though this didn’t stop the data guard replication, we need to get rid of this error message. It seems to be false alarm in DR alert log.

Solution: If there is no difference in the directory structure in Primary and standby, you can get rid of this message by modifying the log_file_name_convert parameter to a dummy Value 

ALTER SYSTEM SET log_file_name_convert='dummy','dummy';

After the parameter was set, the ORA message was no longer seen in the alert.log

Reference: ORA-19527: Physical Standby Redo Log Must Be Renamed…during switchover (Doc ID 2194825.1)

ORA-65093: multitenant container database not set up properly

Posted on May 15, 2021 by CDB Oracle Database 0

While starting a container database or mounting a standby container database you may encountered Error: ORA-65093: multitenant container database not set up properly

RMAN-11003: failure during parse/execution of SQL statement: alter database mount standby database
ORA-65093: multitenant container database not set up properly

Solution is add the parameter enable_pluggable_database=true and restart the instance,

enable_pluggable_database=true

Hope this helps…

Enable Flashback Database on Oracle 12c

Posted on May 6, 2021 by Oracle 12c Oracle Database 0

In this article we will describe the step by step instructions on how to enable flashback on Oracle 12c database

  1. Enable ARCHIVELOG mode:
SQL> select log_mode from v$database;

LOG_MODE
------------
NOARCHIVELOG

If the database is in NOARCHIVELOG mode, Enable it

alter system set log_archive_dest_1='LOCATION=/u01/app/oracle/arch';
SHUTDOWN IMMEDIATE;
STARTUP MOUNT;
ALTER DATABASE ARCHIVELOG;
ALTER DATABASE OPEN;

Check the Database ARCHIVELOG status

SQL> select log_mode from v$database;

LOG_MODE
------------
ARCHIVELOG

2. Set the DB_RECOVERY_FILE_DEST_SIZE and DB_RECOVERY_FILE_DEST

alter system set DB_RECOVERY_FILE_DEST_SIZE=10G;
alter system set DB_RECOVERY_FILE_DEST='/u01/app/oracle/fra';

3. Enable FLASHBACK database

ALTER DATABASE FLASHBACK ON;

4. Check the FLASHBACK database status

SQL> select flashback_on from v$database;

FLASHBACK_ON
------------------
YES

Hope this helps..

Categories

Visitor Count

0375138
Visit Today : 159
Total Visit : 375138
Total Hits : 776668
Who's Online : 4