What is the most important part in an execution plan? It's probably the predicate section. It helps to see implicit conversions. It helps to understand why an index is used or not. Or to see additional predicates coming from constraints. When you get an execution plan from shared pool, the dbms_xplan.display_cursor() shows the predicates. But when you retrieve a plan from the past, dbms_xplan.display_awr() don't show them.
In most environments one set of GoldenGate process (1 Extract & 1 Replicat process) is sufficient for change data synchronization. But if your source database generates a huge volume of data then a single process may not be sufficient to handle the data volume. In such a scenario there may be need to split the […]
The post GoldenGate Not Keeping Up? Split the Process Using GoldenGate Range Function appeared first on VitalSoftTech.
I've blogged about multitenant internals at the time when 22.214.171.124 was just released. Something has changed in 126.96.36.199 and blogging about it was in my todo list for a long time. Now the occasion to do it has been triggered by a question on Oracle Forums about CDB_DATA_FILES not showing PDB$SEED datafiles because there is an important change we must be aware of.
With Basic Compression, you cannot drop a column.
Oracle 12c came up with one nice new feature: Opatch, the tool known to all database administrators is now integrated into the database in the form of DBMS_QOPATCH package. If the database contains pluggable databases, the package must be executed from the root (CDB$ROOT) level, as user sys.
Also, a minor inconvenience is that there are no tabular results, results are returned as XML. It is a bit cumbersome to work with and I do prefer the traditional Opatch for now. So, let’s make an example:
With the INMEMORY clause you can specify 4 sub-clauses: