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).
Joords is in-depth knowledge of Oracle database technology
To integrate with Active Directory we are going to use two database features
To integrate with Active Directory we are going to use two database features
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.
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;