In Oracle 12.1 and below, the maximum
length for the name of an object (Table, View, Procedure, Package, Function,
Materialized View etc.) is 30 bytes (or 30 characters, if each character is of 1 byte as per character set used). Starting 12.2, name length has been increased to 128 bytes/characters. Likewise, the name of a column of a
table or view should also not exceed the allowed length. In the following I am
providing a few examples where we will see ORA-00972 error returned in 12.1 database
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.
Saturday, March 28, 2020
Friday, March 20, 2020
SQL Plan Management and SQL Baseline
Before you read this
article, I would suggest you to read my articles about bind variable peeking and adaptive cursor sharing.
Starting 11g release, adaptive cursor sharing makes optimizer to
generate and select multiple execution plans based on the bind variable values
passed during the execution. Oracle also introduced SQL Plan Management feature
starting 11g whereby the history of plans of an SQL is maintained in SQL
Baseline and out of which one or more plans can become “accepted” and can be
used for that SQL. This is our choice to make plan(s) “accepted” if think that
plan is optimal. We may ignore sub-optimal plans. In this will explain SQL Plan
Management using an example.Friday, March 6, 2020
gc buffer busy acquire and gc buffer busy release
These two wait events are
similar to ”buffer busy wait” that you might have observed which is recorded
when a session tries to access a data block/buffer which is already being
accessed by another session that is connected to the same instance and buffer
is also in the current instance’s buffer cache. In RAC environment, if a session
tries to read a buffer from a remote instance’s buffer cache but the buffer is
already being read by a different session, a “gc buffer busy acquire” wait
event is recorded. If a session tries to read a buffer from the buffer cache of
local instance, but buffer is already being read into remote instance’s buffer
cache from local cache by a session connected to that remote instance, a “gc
buffer busy release” wait event is recorded.
Subscribe to:
Posts (Atom)
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...