|Source Database||Target Database|
GG Process Names
|Source Database||Target Database|
GG Process Names
Overview & Components
This post covers Overview & Components of Oracle GoldenGate (software for real-time data integration and replication in heterogeneous IT Systems). I also added several examples for a full Setup.Continue reading Oracle GoldenGate
Here we are going to convert a NON-CDB to PDB.
The process is simple , from the 12c Oracle Home start DBCA and create a CDB Instance with one PDB. Then you have all the necessary setup for the migration. Now with few simple steps one can migrate to the CDB instance.
In this demo my Non-CDB name is DIEGO and the newly created CDB instance name is GLOBALDB, it has one PDB named PDB001 and will later add DIEGO into the CDB as a PDB.
SQL*Plus includes support for the multitenant architecture.
SHOW command displays information about PDBs.
SQL> SHOW CON_ID CON_ID ------------------------------ 1 SQL> SHOW CON_NAME CON_NAME ------------------------------ CDB$ROOT SQL> SHOW PDBS CON_ID CON_NAME OPEN MODE RESTRICTED ---------- ------------------------------ ---------- ---------- 2 PDB$SEED READ ONLY NO 3 PDB1 READ WRITE NO
Before we can use the
HISTORY command we have to make sure it is turned on. In the example below we attempt to use the
HISTORY command with no options and we are told the
HISTORY command is not enabled, so we enable it as instructed. Continue reading SQL*Plus Enhancements
Rather than deleting data, some applications have a concept of “mark for delete”, so the data remains present in the table, but is not visible to the application. This is usually achieved by doing the following.
WHERE deleted = 'N'“, to exclude the deleted rows from the SQL and then create a view on that table to display only “active” records.
In-Database Archiving is a feature added to Oracle Database 12c to allow this type of “mark for delete” functionality out-of-the-box, with fewer changes to the existing application code.
There are quite a few useful additions, such as converting view into a table while exporting and turning off logging while import.
Multiple files are generated by parallel exports, so each file needs to have a unique name. This is achieved using substitution variables. In previous releases the only substitution variable available was “%U”, which generated a two digit number from 01-99.
Oracle 12.2 includes additional substitution variables.
The following substitution variables are only available for export operations.
The following substitution variables are available for both export and import operations.
The following example shows the usage of two of the new substitution variables in a parallel export. The output is edited to reduce its size.
$ expdp system@DB schemas=scott directory=TEST dumpfile=scott_%T_%L.dmp logfile=expdpscott.log parallel=4
Master table "SYSTEM"."SYS_EXPORT_SCHEMA_01" successfully loaded/unloaded
Dump file set for SYSTEM.SYS_EXPORT_SCHEMA_01 is:
Job "SYSTEM"."SYS_EXPORT_SCHEMA_01" completed with 1 error(s) at Wed Mar 22 16:05:41 2017 elapsed 0 00:01:07
In this post, I will demonstrate the conversion of a 220.127.116.11 non-CDB to a PDB. We will plug in 18.104.22.168 non-cdb named ncdb12c into a CDB called CDB2
Source = 22.214.171.124 non-cdb : ncdb12c
Target CDB : CDB2
Target PDB : ncdb12c
To get data from a Non-CDB to a PDB you have to do a convert of a Non-CDB to PDB. The conversion process is similar to unplug and plug of a pdb.
– Log into ncdb12c as sys
– Get the database in a consistent state by shutting it down cleanly.
– Open the database in read only mode
– Run DBMS_PDB.DESCRIBE to create an XML file describing the database.
– Shut down ncdb12c
– Connect to target CDB (CDB2)
– Check whether non-cdb (NCDB12c) can be plugged into CDB(CDB2)
– Plug-in Non-CDB (NCDB12c) as PDB(NCDB12c) into target CDB(CDB2).
– Access the PDB and run the noncdb_to_pdb.sql script.
– Open the new PDB in read/write mode.
Let’s see how to access EM express for various types of databases.
Oracle 12c has introduced multitenant architecture in which we can have different types of databases:
– Non CDB’s
Let’s see how to access EM express for various types of databases:
At the root container, data is displayed for the entire CDB, and all actions taken impact all containers. Data pertaining to a PDB, such as a user or a SQL statement, is qualified with the container name. The actions a user can perform at the root container include:
– viewing and setting initialization parameters;
– administering common users and privileges; and
– managing memory configuration, undo information and redo logs.
– Find out the port on which EM Express is configured:
Three methods are available:
I keep “playing'” with 12c, and this time I’d like to show you how easy is to install the Pre-Built VMs provided by Oracle.
As I mentioned, the process is very simple, these are the requirements to install it:
So now that you know the minimum requirements, let’s move to the installation process:
As you can see, the process is pretty simple right?
Have a nice day!!
I found a VERY interesting link at Oracle’s website showing a lot of information on 12c:
It contains information on: