Tag: #oratidbit

Posted on

Oracle Tidbits – April 2020 #OraTidbit

“Oracle *daily* TidBits” (#oratidbit) published on Facebook &Twitter, during weekdays in April 2020. I hope you find these helpful to learn something new or to remind you of its existence and use.

#OraTidbit #db20c Oracle Data Guard Broker provides early detection of fast-start failover (FSFO) configuration issues and reports those misconfigurations allowing administrators to take action prior to a failover event.
#OraTidbit #db20c Oracle Data Guard broker utilizes a standardized directory structure to store client-side files. Use the DG_ADMIN environment variable to specify the default location.
#OraTidbit #db20c Two new #GoldenGate views, DBA_OGG_AUTO_CAPTURED_TABLES, and USER_OGG_AUTO_CAPTURED_TABLES, provide you with tools to query which tables are enabled for Oracle GoldenGate automatic capture.
#OraTidbit #db20c #db19c Init parameter MAX_IDLE_BLOCKER_TIME specifies the maximum number of minutes that a blocking session can be idle. After that point, the session is automatically terminated. This parameter differs from the MAX_IDLE_TIME parameter in that MAX_IDLE_TIME applies to all sessions (blocking and non-blocking), whereas MAX_IDLE_BLOCKING_TIME applies only to blocking sessions.
#OraTidbit #db20c In 20c, you must configure the Grid Infrastructure Management Repository (GIMR) in a separate Oracle home, instead of in the Grid home. A separate Oracle home for the GIMR ensures faster rolling upgrades, less errors, and fewer rollback situations.
#OraTidbit #db20c The remote Grid Infrastructure Management Repository (GIMR) feature for Oracle Standalone Cluster enables you to use a centralized GIMR. This feature does not require local cluster resources to host the GIMR.
#OraTidbit #db20c Init parameter DIAGNOSTICS_CONTROL helps to control and monitor the users who perform potentially unsafe database diagnostic operations. To modify this parameter with the ALTER SYSTEM command, you must be authenticated AS SYSDBA.
#OraTidbit #db20c Init parameter TABLESPACE_ENCRYPTION_DEFAULT_ALGORITHM specifies the default algorithm the database uses when encrypting a tablespace if an encryption algorithm is not specified when creating an encrypted tablespace or when encrypting an existing tablespace.
#OraTidbit #AutoUpgrade Oracle Database AutoUpgrade enables you to upgrade one or many databases without human intervention, all with one command, and with a single configuration file.
#OraTidbit #DBUpgrade Use the Oracle Database Parallel Upgrade Utility with the -T option to take schema-based tablespaces offline during upgrade. Oracle Database can read file headers created in earlier releases. The file headers of READ ONLY tablespaces are updated when they are changed to READ WRITE.
#OraTidbit #DBUpgrade If you plug in an earlier release PDB to a new release CDB, then the CDB detects on opening the PDB that the PDB is an earlier release than the CDB, and automatically starts a Replay Upgrade process. Upgrade on PDB Open automatically upgrades the PDB using the Replay Upgrade synchronization feature.
#OraTidbit #DBUpgrade By default, the Oracle Multitenant Replay Upgrade method is enabled for upgrades on PDBs and CDBs. To disable the Parallel Upgrade Utility (catctl.pl) default of performing a Replay Upgrade, run ALTER DATABASE UPGRADE SYNC OFF on either CDB$ROOT or a particular PDB.
#OraTidbit #db20c Traditional auditing is deprecated in 20c. Thus, AUDIT_FILE_DEST, AUDIT_SYS_OPERATIONS, AUDIT_SYSLOG_LEVEL, AUDIT_TRAIL init parameters are deprecated.
#OraTidbit #db20c The UNIFIED_AUDIT_SGA_QUEUE_SIZE initialization parameter is desupported in 20c database.
#OraTidbit #db20c #AutonomousDB Autonomous Database instance OCPU compute usage is now billed per-second with a one minute minimum. Previously Autonomous Database billed in one-hour minimum increments and partial usage of an hour was rounded up to a full hour.
#OraTidbit #AutonomousDB You can create Oracle Autonomous Database Dedicated Deployment on quarter-rack or half-rack Exadata Database Machine X7-2 or X8-2 systems.
#OraTidbit #VirtualBox Oracle VM VirtualBox 6.1 supports the importing of cloud instances from an Oracle Cloud Infrastructure service. When you import a cloud instance, Oracle VM VirtualBox creates and registers a new VM automatically on the localhost.
#OraTidbit #VirtualBox You can export a VirtualBox VM to Oracle Cloud Infrastructure account and save it as a custom image to create multiple cloud instances from the custom image, without having to reupload the image every time.
#OraTidbit #Linux The virt-v2v utility converts virtual machines from Oracle VM hypervisor, including their disk images and metadata, for use with Oracle Linux Virtualization Manager and Oracle Linux KVM.
#OraTidbit #AutonomousDB Autonomous Database supports loading and using Simple Oracle Document Architecture (#SODA) documents and collections. SODA allows us to store, search, and retrieve document collections, typically JSON documents, without using SQL.
Posted on

Oracle Tidbits – March 2020 #OraTidbit

“Oracle *daily* TidBits” (#oratidbit) published on Facebook &Twitter, during weekdays in March 2020. I hope you find these helpful to learn something new or to remind you of its existence and use.

#OraTidbit #Db20c Initialization parameters AUDIT_FILE_DEST, AUDIT_SYS_OPERATIONS, AUDIT_SYSLOG_LEVEL, AUDIT_TRAIL (Traditional auditing parameters) are deprecated in Oracle Database 20c.
#OraTidbit #db20c Traditional auditing is deprecated in Database 20c. DBA Views deprecated include DBA_AUDIT_TRAIL, DBA_COMMON_AUDIT_TRAIL, DBA_FGA_AUDIT_TRAIL and so on.
#OraTidbit #db20c Starting with Oracle Database 20c, an Oracle Database installation configures all Oracle Database homes in read-only mode by default (ORACLE_BASE_HOME and ORACLE_BASE_CONFIG are located separately from ORACLE_HOME).
#OraTidbit #db20c The option to use Oracle Data Guard with a logical standby Database is deprecated in Database 20c. The logical standby feature and the DBA_LOGSTDBY and DBMS_LOGSTDBY SQL statements and V$LOGSTDBY views can be desupported in a future release.
#OraTidbit #db20c Starting in Oracle Database 20c, the IGNORECASE parameter for the orapwd file is desupported. All newly created password files are case-sensitive.
#OraTidbit #ADW #ATP Depending on the region where you provision or clone your database, Autonomous Database supports 18c or 19c or both Oracle Database versions.
#OraTidbit #ADW #ATP By default the Autonomous database uses extended data types and the value of MAX_STRING_SIZE is set to EXTENDED. To support migration from older Oracle Databases or applications you can set MAX_STRING_SIZE to the value STANDARD by using DBMS_MAX_STRING_SIZE.MODIFY_MAX_STRING_SIZE.
#OraTidbit #ATP #ADW Oracle Database Vault is disabled by default on Autonomous Database. To configure and enable Oracle Database Vault on Autonomous Database, use DBMS_CLOUD_MACADM.CONFIGURE_DATABASE_VAULT and DBMS_CLOUD_MACADM.ENABLE_DATABASE_VAULT.
#OraTidbit #ATP #ADW You can create #OracleCloud Autonomous Database Dedicated Deployment on Exadata Infrastructure quarter-rack or half-rack Exadata Database Machine X7-2 or X8-2 systems.
#OraTidbit #ATP #ADW Autonomous Database with Oracle Database 19c includes automatic index management tasks, such as creating, rebuilding, and dropping indexes based on changes in the application workload.
#OraTidbit #db20cThe result cache in an Active Data Guard standby database is utilized to cache results of queries that were run on the physical standby database. In the case of a role transition to primary, the standby database result cache will be preserved ensuring performance for offloaded reporting and other queries continue without compromising the performance benefits of the standby result cache.
#OraTidbit #db20c Starting with 20c, the USER_APPLICATION_ROLES data dictionary view provides a subset of roles that are available in DBA_APPLICATION_ROLES that only apply to the current user.
#OraTidbit #db20c The SQL set operators support all keywords as defined in #ANSISQL. The new operator EXCEPT [ALL] is functionally equivalent to MINUS [ALL]. The operators MINUS and INTERSECT now support the keyword ALL.
#OraTidbit #db20c Starting with Oracle Database 20c Oracle Data Pump can include and exclude objects in the same export or import operation.
#OraTidbit #db20c Starting with Oracle Database 20c Oracle Data Pump can resume transportable tablespace export and import jobs that are stopped.
#OraTidbit #db20c DbNest provides operating system resource isolation and management, file system isolation, and secure computing for PDBs. The infrastructure is implemented as a Linux-specific package that provides hierarchical containers, called nests.
#OraTidbit #db20c The UNIFIED_AUDIT_SGA_QUEUE_SIZE initialization parameter is desupported in Oracle Database release 20c, version 20.2.
#OraTidbit #OracleCloud If your Autonomous Database instance is on Oracle Database 18c, Oracle will automatically upgrade your instance to Oracle Database 19c. If you want to upgrade at a time of your choosing, then you can manually upgrade your database to Oracle Database 19c.
#OraTidbit #OracleCloud The automatic upgrade of Autonomous Database 18 to 19c is a minimal downtime operation and requires up to ten (10) minutes of downtime during the maintenance window.
#OraTidbit #DB20c The Data Guard Broker in 20c enables users to create and add a Far Sync instance to a Data Guard Broker configuration using a single command. Zero Data loss over a long distance can be achieved by using the Data Guard Far Sync standby instances.
#OraTidbit #db20c Automatic zone maps are created and maintained for any user table without any customer intervention. Zone maps allow the pruning of blocks and partitions based on the predicates in the queries. Automatic zone maps improve the performance of any query transparently and automatically.
#OraTidbit #db20c Oracle ASM Flex Disk Group supports Cloning a PDB in one CDB to a new PDB in a different CDB. This feature enables you to use Oracle ASM cloning for test and development cloning.