“Oracle *daily* TidBits” (#oratidbit) published on Facebook &Twitter, during weekdays in April 2019. Hope you find these helpful to learn something new or to remind you of its existence and use.
|#oratidbit #db18c Automatically maintain standby databases when performing PDB plugins by using initialization parameter STANDBY_PDB_SOURCE_FILE_DIRECTORY (directory location where files of a PDB being used for repeated plugins are stored).
|#oratidbit #db18c Automatically maintain Active Data Guard standby databases when performing PDB remote clones by using initialization parameter STANDBY_PDB_SOURCE_FILE_DBLINK (name of the db link used to clone the PDB at the primary).
|#oratidbit #db19c The SET FAST_START FAILOVER TARGET command enables to dynamically change the fast-start failover target to the named standby database without disabling fast-start failover or modifying the fast start failover list.
|#oratidbit #db19c The High-Frequency Automatic Optimizer Statistics Collection feature collects statistics frequently (default 15 minutes) for tables where data changes frequently. The lightweight task gathers only stale statistics.
|#oratidbit #db19c Oracle Trace File Analyzer integrates with Oracle Cluster Health Advisor. When Oracle Cluster Health Advisor detects a problem event, Oracle Trace File Analyzer automatically triggers the relevant diagnostic collection and sends an email notification.
|#oratidbit #db19c Heard at #CTX19: #OracleEBS will support Oracle Database 19c container database architecture, with one PDB.
|#oratidbit Heard at #CTX19: #OracleEBS uses (deprecated) UTL_FILE_DIR parameter to read and write files. Starting Database 19c, UTL_FILE_DIR is desupported. When you upgrade EBS database to 19c, an equivalent directory object will be created for each UTL_FILE_DIR entry.
|#oratidbit #db19c You can use ADDM to analyze AWR data stored inside the PDB through an AWR snapshot taken inside the PDB. Automatic ADDM of a PDB is disabled by default. You can enable it for a PDB by enabling automatic AWR snapshots.
|#oratidbit #db19c In Oracle Grid Infrastructure, use Fleet Patching and Provisioning to automate relocation of a PDB from one CDB to another. Automated relocation enables individual PDBs to be patched more quickly without exposing other PDBs to the changes in the patch.
|#oratidbit #OracleCloud The Oracle Cloud Infrastructure Audit service automatically records calls to all supported OCI public API endpoints as log events. Each log event includes a header ID, target resources, time stamp of the recorded event, request parameters, and response parameters.
|#oratidbit #ADW #OracleCloud DATA_PUMP_DIR is the only directory you can specify as the directory argument for data pump jobs, and it is predefined. Move the dump files from the directory DATA_PUMP_DIR to Cloud Object Store by calling DBMS_CLOUD.PUT_OBJECT.
|#oratidbit #ADW #OracleCloud To ensure the security and the performance of Autonomous Data Warehouse, LONG and LONG RAW data types are not supported (also media types and spatial types).
|#oratidbit #db19c In a multitenant database, you can use Oracle Database Vault to block common users (infrastructure DBAs, for example) from accessing local data in pluggable databases (PDBs).
|#oratidbit #exadata Secure Eraser (V2 or higher) solution securely erases all data on both database servers and storage servers, and resets InfiniBand switches, Ethernet switches, and power distribution units back to factory default. Use when you are removing an Oracle Exadata Database Machine from your environment to securely erase all the information on the servers.
|#oratidbit #apex For testing and production instances, Oracle Application Express supports the ability to install a runtime version. This minimizes the installed footprint and privileges.
|#oratidbit #orcldb #db19c Real-Time SQL Monitoring for Developers: Database users without SELECT_CATALOG_ROLE can generate and view SQL Monitor reports for their own SQL statements, including the execution plans and performance metrics.
|#oratidbit #orcldb Trace File Analyzer (TFA) feature: Use “tfactl blackout” command to suppress automatic diagnostic collections. If you set blackout for a target, then TFA stops automatic diagnostic collections if it finds events in the alert logs while scanning.
|#oratidbit #orcldb Trace File Analyzer (TFA) feature: “tfactl blackout” command has several options to supress diagnostic collection at a granular level. Use -targettype, -target, -events, -local.