creating common user # db12c ##

creating common user on container databases

SQL> create user c##nikhil identified by oracle;

User created.

SQL> grant sysdba to c##nikhil;

Grant succeeded.

SQL> grant create session to c##nikhil;

Grant succeeded.

SQL> select * from v$pwfile_users;

USERNAME       SYSDB SYSOP SYSAS SYSBA SYSDG SYSKM     CON_ID

------------------------------ ----- ----- ----- ----- ----- ----- ----------

SYS                       TRUE  FALSE FALSE FALSE FALSE FALSE          1

SYSDG                 FALSE FALSE FALSE FALSE TRUE  FALSE          1

SYSBACKUP       FALSE FALSE FALSE TRUE  FALSE FALSE          1

SYSKM                 FALSE FALSE FALSE FALSE FALSE TRUE           1

SYSTEM               TRUE  FALSE FALSE FALSE TRUE  FALSE          1

DBSNMP              TRUE  FALSE FALSE FALSE TRUE  FALSE          1

C##NIKHIL          TRUE  FALSE FALSE FALSE FALSE FALSE          1

7 rows selected.

connecting using common user as sysdba#

[oracle@kansas ~]$ sqlplus c##nikhil/oracle as sysdba

SQL*Plus: Release 12.1.0.1.0 Production on Mon Apr 24 01:17:06 2017

Copyright (c) 1982, 2013, Oracle.  All rights reserved.

Connected to:

Oracle Database 12c Enterprise Edition Release 12.1.0.1.0 - 64bit Production

With the Partitioning, OLAP, Advanced Analytics and Real Application Testing options

SQL> 

SQL> show user;

USER is "SYS"

Connecting as common User “c##nikhil# to manage container database # 

[oracle@kansas ~]$ sqlplus

SQL*Plus: Release 12.1.0.1.0 Production on Mon Apr 24 01:18:04 2017

Copyright (c) 1982, 2013, Oracle.  All rights reserved.

Enter user-name: c##nikhil

Enter password: 

Connected to:

Oracle Database 12c Enterprise Edition Release 12.1.0.1.0 - 64bit Production

With the Partitioning, OLAP, Advanced Analytics and Real Application Testing options

SQL> 

SQL> 

SQL> show user;

USER is "C##NIKHIL"

>> >> >>>

---Nikhil Tatineni---

---Oracle Database---

Encrypted tables # TDE with goldengate #

In previous releases (up to OGG 11.1.1.0.x) OGG does not support TDE completely.

TDE tablespace encryption is not supported in OGG 10.4 and 11.1.1.0.x

Starting with OGG 11.1.1.1 the behaviour is changed and TDE is supported.  

TDE columns are encrypted in the data files and in the redo log, so Extract must be

configured to fetch the clear-text values from the database. To trigger this fetch, use the fetch parameters fetchcols and fetchmodcols.
FETCHCOLS forces a fetch of values that are not in the redo log, and FETCHMODCOLS or FETCHMODCOLS[EXCEPT] forces a fetch of values that are in the logs. Used together, these parameters ensure that the TDE columns are always fetched from the database. The following is an example of how to configure Extract to support TDE. In this example, the TDE column is credit_card_number.


USERID ggs, password ggs
RMTHOST sysb, mgrport 4261
RMTTRAIL C:\ggs\oracle\v8100\dirdat\td
TABLE ab.payment_info, FETCHCOLS (credit_card_number), &
FETCHMODCOLS (credit_card_number);

GoldenGate limitations with TDE:
The table that contains the TDE columns must have a primary or unique key.
Columns that use TDE cannot be part of the primary key.
If there is no primary or unique key defined in the source database, it might be added in the extract. 

for more details # please see following note #

See KM 1341598.1 for detail of full TDE support. The basic setup is described in the Oracle GoldenGate 10.4 documentation:

http://download.oracle.com/docs/cd/E15881_01/doc.104/gg_ora_inst_v104.pdf

Replicating Oracle TDE data

If any tables have columns that use Transparent Data Encryption (TDE), check them

Still it is mandatory to have a non-TDE column to be unique. 

See Note 1294601.1 GoldenGate workaround for replicating encrypted tables having no PK or UK  To enable processing of TDE-protected data

---Nikhil Tatineni--

---TDE --Ogg--