Joords Oracle DBA blog

The DBMS_DICTIONARY_CHECK is a read-only and lightweight PL/SQL package procedure that helps you identify Oracle Database dictionary inconsistencies that are manifested in unexpected entries in the Oracle Database dictionary tables or invalid references between dictionary tables. Oracle Database dictionary inconsistencies can cause process failures and, in some cases, instance crash.

Oracle has engineered a new method to execute a Transportable Tablespaces to the Extreme. See the recording on Oracle's YouTube channel . You can read the Q&A and the slides  .

  Separation of Duty Ensuring that backup data is validated is key to being prepared for a future recovery, which means that all data, including TDE databases, must be validated for recoverability at each step of the workflow into the Cyber Vault. Multi-layer anomaly detection in the architecture ensures that data is valid at all points in the Oracle ecosystem. Each zone indicated above will perform independent checks to prevent invalid or compromised data from entering or exiting the zone and ultimately the Cyber Vault. Zone 1 RMAN will do consistency checks at the database to ensure the backup data is valid before being sent to the Recovery Appliance in the production data center Zone 2 The Recovery Appliance in the production data center performs checks to ensure that the data is valid and complete. Data is validated when the RMAN database backup arrives on the Recovery Appliance in the production data center.  Data replicated from the Recovery Appliance in the production d...

Oracle Connection Manager (CMAN) serves as a proxy for database connections within Oracle deployments. It facilitates the transmission of client requests to the Oracle Database and seamlessly transmits the database responses back to the client, whether it be an application, middle-tier, or other components. CMAN operates as a versatile networking solution, providing features such as TLS security, protocol switching/routing, and session multiplexing to enhance the accessibility of both local and remote Oracle databases. Traffic Director Mode (TDM) is an intelligent layer introduced in Oracle Client 18c and beyond, designed to enhance CMAN. TDM introduces additional dimensions to the system, including transparent High Availability (HA) with outage support , advanced security features for cloud environments (protection against DoS and fuzzing attacks, tenant isolation, etc.), and capabilities for optimizing performance. In summary, CMAN-TDM allows any client application to establish a ...

The COLOCATION_TAG parameter is an alphanumeric string that you can use with the CONNECT_DATA parameter of the TNS connect string. When you set the colocation_tag within the CONNECT_DATA parameter, load balancing is ignored.

Oracle has started from Oracle version 18c to use Oracle read-only software trees. See my blog Configuring Read Only OracleHome - 18c   From Oracle version 21c there are no distinctions between software trees in read-only and read-write modes. As of now, the default configuration is set to utilize the read-only mode introduced in Oracle 18c. When installing a CDB through DBCA on Oracle Database 21c, you will observe the presence of TNSNAMES.ORA .  The question then arises: where is it located?

 To integrate with Active Directory we are going to use two database features  Kerberos authentication (Part 1), Centrally Managed Users (Part 2)  (note: Centrally Managed Users is an Enterprise Edition feature). Centrally Managed Users (Part 2) 

To integrate with Active Directory we are going to use two database features  Kerberos authentication (Part 1), Centrally Managed Users (Part 2)  (note: Centrally Managed Users is an Enterprise Edition feature) Kerberos authentication (Part 1)

 The parameter FORWARD_LISTENER is useful when it is difficult to change an existing client connect string, for example, after an offsite database has been moved into the Oracle Cloud. With the FORWARD_LISTENER parameter, clients can continue to connect to their offsite listener, and the offsite listener forwards the connection to the Oracle Cloud listener.  Once a forward listener has been configured through the FORWARD_LISTENER parameter, the LOCAL_LISTENER parameter can be cleared by setting its value to "-oracle-none-" so that all the connections coming to an existing set of remote listeners configured through the REMOTE_LISTENER parameter are forwarded only to listeners configured through FORWARD_LISTENER . The FORWARD_LISTENER parameter can also be specified in the LISTENER_NETWORKS parameter. Lets play and test it, information of the environment

A PDB relocation executes an online block level copy of the source PDB data files, redo, and undo while the source PDB is open with active sessions. When the target PDB comes online because of an ALTER PLUGGABLE DATABASE OPEN statement, Oracle Database terminates the active sessions and closes the source PDB.  The AVAILABILITY MAX clause in CREATE PLUGGABLE DATABASE ... RELOCATE implicitly instructs the SQL*Net layer to reconfigure the original listener. This situation may be common when relocating a PDB between data centers. This configuration is intended to be temporary while the Oracle Internet Directory (OID) or LDAP server is updated or the client connections are modified. Overview image Relocate PDB

Dynamic CPU Scaling in Oracle Database   Prior to this new feature, DBAs had to allocate resources for peak loads to a database to ensure scale up was possible, and to ensure needed resources weren’t taken by other applications, commonly known as "Noisy Neighbors". Oracle offers the ability to configure " shares " and " limits " for each Pluggable Database within a Container Database.

When you encrypt your databases, you will often end up needing the keystore password to perform certain operations. For instance, cloning an encrypted PDB will require the keystore password: CREATE PLUGGABLE DATABASE ... KEYSTORE IDENTIFIED BY S3cr3t;

You can use Oracle wallet as a secure external password store for authenticating database users in DBCA silent mode commands. Oracle wallet is a secure software container external to Oracle Database, which can be used to store authentication credentials of Oracle Database users. The configuration of the Oracle wallet as a secure external password store will be done by the mkstore command-line utility. Database User Authentication in DBCA Commands Using Oracle Wallet useWalletForDBCredentials Specify true to use Oracle wallet for database user authentication, else specify false. Default is false. dbCredentialsWalletLocation Directory in which the Oracle wallet files are stored (Optional) dbCredentialsWalletPassword Password for the Oracle wallet account user. If the Oracle wallet is auto-login enabled, then you need not specify this password

Oracle Database 19c introduces a significantly enhanced connection string syntax called Easy Connect Plus. By reducing the need for external configuration files, Easy Connect Plus makes it easier to use features such as TLS connections, wallets, load balancing, connection timeouts, and to tune network buffer sizes. Easy Connect Plus can be used in JDBC and .NET applications. It is also usable in applications and drivers built on the C language Oracle Call Interface (OCI) such as the Oracle Database drivers for Python, Node.js, PHP, Ruby, and Go. Easy connect background An Easy Connect string includes a host name, an optional port, and the database service name: database_host[:port][/[service_name] Easy connect plus syntax The Oracle Database 19c enhanced Easy Connect Plus syntax is a superset of Easy Connect that supports more connection options. The syntax is available in Oracle Database drivers (JDBC, ODP.Net, cx_Oracle, node-oracledb etc) that use Oracle Client 19c and c...

Can you connect as SYSDBA without password into a PDB directly? Of course with the usual way of “ sqlplus / as sysdba ”. Yes you can, even without no bequeath connection available. There is a 19c EBS notes . In one of the most important EBS MOS Notes: 2552181.1 – Interoperability Notes: Oracle E-Business Suite MOS Notes: 2552181.1 – Interoperability Notes: Oracle E-Business Suite Release 12.2 with Oracle Database 19c under section 2.5 you can read:

How do you get the information Database? Go to My Oracle Support and hit the “Certification” tab. Then choose “Oracle Database“, “19.0.0.0.0” and either “Linux x86-64 Oracle Linux 8.x” or “Linux x86-64 Red Hat Enterprise Linux 8“.

Starting with Oracle Database 18c, you can configure an Oracle home in read-only mode. In a read-only Oracle home, all the configuration data and log files reside outside of the read-only Oracle home. This feature allows you to use the read-only Oracle home as a software image that can be distributed across multiple servers. The concept of a read-only Oracle home, Oracle has committed to to separate configuration files from binaries. The Configuring Read Only OracleHome 18c have impact on the following methods / DBCA / Patching / Upgrade / Key stores

From Mike Dietrich tweet on :  Different MOS Notes for xTTS PERL scripts . Question is which should I use?

Migration of a single PDB or executing of a single PDB into another container database with minimal downtime. This method has zero impact to any remaining primary PDBs.  To use this method  the process takes advantage of a new functionality added to the Data Guard broker command line interface DGMGRL. Important: The process are steps involve changes being made to 2 independent CDBs and is supported in Oracle RDBMS versions older than 12.1.0.2 The migration process overview

Bug 27693713 - PDB PITR Does Not Apply Incrementals When Local Undo Is Enabled DB PITR does not apply incremental backup when PDB is configured with local undo  (select * from database_properties where property_name = 'LOCAL_UNDO_ENABLED' and PROPERTY_VALUE = 'TRUE'); When restore pluggable database noredo is executed, it is supposed to apply incremental backups. Instead, media recovery is being performed when PDB local undo is enabled. this can take a long time. Bug info 27693713