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.
Oracle Installation guides, Linux Administration tips for DBAs, Performance Tuning tips, Disaster Recovery, RMAN, Dataguard and ORA errors solutions.
No contents from my website can be published anywhere else without my permission. Test every solution before implementing in the production environment.
Friday, May 26, 2023
Friday, May 19, 2023
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.
Tuesday, May 9, 2023
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.
Popular Posts - All Times
-
This error means that you are trying to perform some operation in the database which requires encryption wallet to be open, but wallet is ...
-
Finding space usage of tablespaces and database is what many DBAs want to find. In this article I will explain how to find out space usage ...
-
ORA-01653: unable to extend table <SCHEMA_NAME>.<SEGMENT_NAME> by 8192 in tablespace <TABLESPACE_NAME> This error is q...
-
You may also want to see this article about the ORA-12899 which is returned if a value larger than column’s width is inserted in the col...
-
This document explains how to start and stop an Oracle cluster. To start and stop Grid Infrastructure services for a standalone installatio...
-
If database server CPU usage is showing 100%, or high 90%, DBA needs to find out which session is hogging the CPU(s) and take appropriate ...
-
If you want to know how we upgrade an 11g database to 12c using DBUA, click here . For upgrading 12.1.0.1 to 12.1.0.2 using DBUA, ...
-
By default AWR snapshot interval is set to 60 minutes and retention of snapshots is set to 8 days. For better and precise investigation of...
-
SWAP space recommendation from Oracle corp. for Oracle 11g Release 2 If RAM is between 1 GB and 2 GB, SAWP should be 1.5 times the s...
-
This article explains how to install a 2 nodes Oracle 12cR1 Real Application Cluster (RAC) on Oracle Linux 7. I did this installation on O...