ORA-16789: standby redo logs configured incorrectly

Creating standby redo log files is a recommended way of configuring dataguard in Oracle database environment. If there is any discrepancy found in standby redo log configuration, you might face ORA-16789 warning. While checking status of dataguard configuration through DGMGRL command, following is that you might see as an example, in a dataguard broker configuration.

ORA-12578: TNS:wallet open failed

 

[oracle]$ sqlplus   SQL*Plus: Release 12.1.0.2.0 Production on Fri Apr 14 08:50:59 2023   Copyright (c) 1982, 2014, Oracle.  All rights reserved.   Enter user-name: sys as sysdba Enter password:

ORA-16000: database or pluggable database open for read-only access

 I faced this error message when I tried to drop a table from my PDB which was opened in read-write mode without any restriction.

SQL> drop table test; drop table test            * ERROR at line 1: ORA-00604: error occurred at recursive SQL level 1 ORA-16000: database or pluggable database open for read-only access    SQL> show pdbs   CON_ID    CON_NAME         OPEN MODE        RESTRICTED ---------- ------------------------------ ---------- ---------------------------  3                PDB1                      READ WRITE      NO

ORA-65179: cannot keep datafiles for a pluggable database that is not unplugged

You should use “including datafiles” clause while dropping a pluggable database otherwise ORA-65179 would be returned

SQL> drop pluggable database testpdb; drop pluggable database testpdb * ERROR at line 1: ORA-65179: cannot keep datafiles for a pluggable database that is not unplugged

ORA-65342: source pluggable database has unrecovered transaction

Starting 12.2, if you are planning to clone a PDB locally or remotely, you can do that while source PDB is open in read-write mode (hot cloning). In 12.1, if you start your CREATE PLUGGABLE DATABASE command while a transaction is already active in the source PB, you will be returned ORA-65342. Therefore, the better option is to close the source PDB, and then start it as read-only so that no transactions could hinder the cloning process

ORA-65040: operation not allowed from within a pluggable database

 Starting 12c, after introduction of pluggable databases, there are certain operations that can be performed only at the root container level. If you try to execute that operation/SQL within the PDB, you will receive ORA-65040. In this case you must ensure that the command you are executing is being executed at the root container level. Following is only one example of such operations that can only be performed from the root container.

Listener log file is empty and logging not happening

If listener log file is empty and no logging records are being logged in the log file, this probably means that someone truncate listener log file on the fly without following proper process. In Windows OS, you can not modify or truncate a file (listener log file in this case) that is in use by another proceess, however, Linux based OS would let you do this. After that, logging would no longer continue. Here I have explained the proper way of rotating listener log file. These instructions can be used for listener log file rotation as well as solving the issue of empty listener log file discussed here.

TNS-12508: TNS:listener could not resolve the COMMAND given

If you are in process of rotating listener log file  and you receive TNS-12508 while disabling log_status, this means you have imposed admin restrictions in listener log file for this listener. Same error would be returned for any other settings you would want to change using “set” command from lsnrctl utility. In the following I have reproduced this error and explained how to set and unset admin restrictions in listner log file.

Rotating Listener Log File

Rotating database log files is a common and day-to-day practice for DBAs. Rotation of logs is a process whereby we rename (and archive/compress) current log files so that new log files get created. Listener’s log file is also part of this practice because size of listener log file increases very fast, and it may increase beyond several GBs within a couple of months. If listener log file is not rotated, this may sometimes cause initial connection to database become slow. Therefore, this is very important to rotate listener log file. In the following I will explain how we rotate listener log file.

ORA-46697: Keystore password required

SQL> show pdbs       CON_ID CON_NAME                       OPEN MODE  RESTRICTED ---------- ------------------------------ ---------- ----------          2 PDB$SEED                       READ ONLY  NO          3 MYPDB1                           READ WRITE NO   SQL> create pluggable database testpdb from MYPDB1; create pluggable database testpdb from MYPDB1 * ERROR at line 1: ORA-46697: Keystore password required.