Skip to main content

How oracle Uses Encrypted Passwords for Database Links with Oracle Data Pump


<<Back to Oracle DB Security Main Page

Error ORA-39395 Introduced To Support Encrypted Passwords For Database Links

Assuming that your have keystore and configured Step by Step instruction for the same is provided in Step by Step How to Configure Software Keystore/ Oracle Wallet post.
In Oracle Database 12c, passwords for database links are stored obfuscated in the database, and when an export with Data Pump (expdp) is performed, the obfuscated value is stored in the dump file
In Oracle Database 18c, when the feature “credentials encryption in the dictionary” is enabled, passwords for database links are not exported, they are replaced with an invalid value; thus, the password has to be reset after import. Lets See with an example.
 

Step1> Check the Keystore Status
SQL> select STATUS,WRL_PARAMETER WALLET_DIR,WALLET_TYPE from V$ENCRYPTION_WALLET;
STATUS                WALLET_DIR                       WALLET_TYPE
--------------------- -------------------------------- --------------------
OPEN                  /u01/dbatst1/stage/wallet/tde/   AUTOLOGIN
OPEN                                                   AUTOLOGIN
OPEN                                                   AUTOLOGIN
Step2> Check Dictionary Encryption Status
SQL> select enforcement from dictionary_credentials_encrypt;
ENFORCEM
--------
DISABLED<=== The feature is not enabled
Step3<Create a test User and grant necessary Privileges
SQL> alter session set container=PDB01;
Session altered.
SQL> create user test_user identified by test_user;
User created.
SQL> grant dba,connect,resource,alter database link to test_user;
Grant succeeded.
Step4> Create Public & Private Database Links
SQL> CREATE PUBLIC DATABASE LINK my_public_dblink CONNECT TO admin identified by password using 'PDB01';
Database link created.
SQL> select sysdate from dual@my_public_dblink;
SYSDATE
---------
19-FEB-19
$ sqlplus  test_user/test_user@PDB01
SQL> CREATE DATABASE LINK my_private_dblink CONNECT TO test_user identified by test_user using 'PDB01';
Database link created.
SQL> select sysdate from dual@my_private_dblink;
SYSDATE
---------
19-FEB-19
Step5> Create directory
SQL> create directory exp as '/u01/dbatst1/stage';
Directory created.
SQL> grant read, write on directory exp to admin;
Grant succeeded.
Step6> Perform Export While Dictionary Encryption is disabled
$expdp admin/password@PDB01 directory=exp full=yes dumpfile=dblink.dmp include=db_link
Export: Release 18.0.0.0.0 - Production on Tue Feb 19 11:33:25 2019
Version 18.3.0.0.0
Copyright (c) 1982, 2018, Oracle and/or its affiliates.  All rights reserved.
Connected to: Oracle Database 18c Enterprise Edition Release 18.0.0.0.0 - Production
Starting "ADMIN"."SYS_EXPORT_FULL_01":  admin/********@PDB01 directory=exp full=yes dumpfile=dblink.dmp include=db_link
Processing object type DATABASE_EXPORT/SCHEMA/DB_LINK
Master table "ADMIN"."SYS_EXPORT_FULL_01" successfully loaded/unloaded
******************************************************************************
Dump file set for ADMIN.SYS_EXPORT_FULL_01 is:
  /u01/dbatst1/stage/dblink.dmp
Job "ADMIN"."SYS_EXPORT_FULL_01" successfully completed at Tue Feb 19 11:34:10 2019 elapsed 0 00:00:38
Step6> Perform import While Dictionary Encryption is disabled
$ impdp admin/password@PDB01 directory=exp full=yes dumpfile=dblink.dmp
Import: Release 18.0.0.0.0 - Production on Tue Feb 19 11:38:33 2019
Version 18.3.0.0.0
Copyright (c) 1982, 2018, Oracle and/or its affiliates.  All rights reserved.
Connected to: Oracle Database 18c Enterprise Edition Release 18.0.0.0.0 - Production
Master table "ADMIN"."SYS_IMPORT_FULL_01" successfully loaded/unloaded
Starting "ADMIN"."SYS_IMPORT_FULL_01":  admin/********@PDB01 directory=exp full=yes dumpfile=dblink.dmp
Processing object type DATABASE_EXPORT/SCHEMA/DB_LINK
Job "ADMIN"."SYS_IMPORT_FULL_01" successfully completed at Tue Feb 19 11:38:40 2019 elapsed 0 00:00:05
SQL> alter session set container=PDB01;
Session altered.
SQL> select sysdate from dual@my_public_dblink;
SYSDATE
---------
19-FEB-19
SQL> select sysdate from dual@my_private_dblink;
SYSDATE
---------
19-FEB-19
NOTE: As you can see there was no warning and DB links are working fine as long as you got the right TNS Entry. You could have seen the warning ORA-39173: Encrypted data has been stored unencrypted in dump file set if you would have encrypted data in the database
This is how the expdp and impdp reacted until 12c.
Now Let us Enable the DICTIONARY ENCRYPT Feature and see how expdp/impdp behaves 
Step7> Enable the Dictionary Encryption
$ sqlplus admin/password@PDB01 as syskm
SQL*Plus: Release 18.0.0.0.0 - Production on Tue Feb 19 13:06:09 2019
Version 18.3.0.0.0
Copyright (c) 1982, 2018, Oracle.  All rights reserved.
Connected to:
Oracle Database 18c Enterprise Edition Release 18.0.0.0.0 - Production
Version 18.3.0.0.0
SQL>
SQL> ALTER DATABASE DICTIONARY ENCRYPT CREDENTIALS;
Database dictionary altered.
SQL> select enforcement from dictionary_credentials_encrypt;
ENFORCEM
--------
ENABLED<== Dictionary Encryption is now enabled
Step8> Perfrom the export
$ expdp admin/password@PDB01 directory=exp full=yes dumpfile=dblink.dmp include=db_link
Export: Release 18.0.0.0.0 - Production on Tue Feb 19 13:08:13 2019
Version 18.3.0.0.0
Copyright (c) 1982, 2018, Oracle and/or its affiliates.  All rights reserved.
Connected to: Oracle Database 18c Enterprise Edition Release 18.0.0.0.0 - Production
Starting "ADMIN"."SYS_EXPORT_FULL_01":  admin/********@PDB01 directory=exp full=yes dumpfile=dblink.dmp include=db_link
Processing object type DATABASE_EXPORT/SCHEMA/DB_LINK
ORA-39395: Warning: object TEST_USER.MY_PRIVATE_DBLINK requires password reset after import
ORA-39395: Warning: object PUBLIC.MY_PUBLIC_DBLINK requires password reset after import
Master table "ADMIN"."SYS_EXPORT_FULL_01" successfully loaded/unloaded
******************************************************************************
Dump file set for ADMIN.SYS_EXPORT_FULL_01 is:
  /u01/dbatst1/stage/dblink.dmp
Job "ADMIN"."SYS_EXPORT_FULL_01" completed with 2 error(s) at Tue Feb 19 13:08:29 2019 elapsed 0 00:00:15
NOTE: As you can see the Password is no more usable and you have to reset the password after import to make the DB_LINKS working again 

$ impdp admin/password@PDB02 directory=exp full=yes dumpfile=dblink.dmp
Import: Release 18.0.0.0.0 - Production on Tue Feb 19 13:26:09 2019
Version 18.3.0.0.0
Copyright (c) 1982, 2018, Oracle and/or its affiliates.  All rights reserved.
Connected to: Oracle Database 18c Enterprise Edition Release 18.0.0.0.0 - Production
Master table "ADMIN"."SYS_IMPORT_FULL_01" successfully loaded/unloaded
Starting "ADMIN"."SYS_IMPORT_FULL_01":  admin/********@PDB02 directory=exp full=yes dumpfile=dblink.dmp
Processing object type DATABASE_EXPORT/SCHEMA/DB_LINK
ORA-39395: Warning: object TEST_USER.MY_PRIVATE_DBLINK requires password reset after import
ORA-39395: Warning: object PUBLIC.MY_PUBLIC_DBLINK requires password reset after import
Job "ADMIN"."SYS_IMPORT_FULL_01" completed with 2 error(s) at Tue Feb 19 13:26:15 2019 elapsed 0 00:00:06

Comments

Post a Comment

Popular posts from this blog

How to Power On/off Oracle Exadata Machine

<<Back to Exadata Main Page How to Power On/off Oracle Exadata Machine Oracle Exadata machines can be powered on/off either by pressing the power button on front of the server or by logging in to the ILOM interface. Powering on servers using  button on front of the server The power on sequence is as follows. 1. Start Rack, including switches  Note:- Ensure the switches have had power applied for a few minutes to complete power on  configuration before starting Exadata Storage Servers 2.Start Exadata Storage Servers  Note:- Ensure all Exadata Storage Servers complete the boot process before starting the   database servers 3. Start Database Servers Powering On Servers Remotely using ILOM The ILOM can be accessed using the Web console, the command-line interface (CLI), IPMI, or SNMP. For example, to apply power to server dm01cel01 using IPMI, where dm01cel01-ilom is the host name of the ILOM for the serve...
Post a Comment
Read more

ORA-28374: typed master key not found in wallet

<<Back to Oracle DB Security Main Page ORA-46665: master keys not activated for all PDBs during REKEY SQL> ADMINISTER KEY MANAGEMENT SET KEY FORCE KEYSTORE IDENTIFIED BY xxxx WITH BACKUP CONTAINER = ALL ; ADMINISTER KEY MANAGEMENT SET KEY FORCE KEYSTORE IDENTIFIED BY xxxx WITH BACKUP CONTAINER = ALL * ERROR at line 1: ORA-46665: master keys not activated for all PDBs during REKEY I found following in the trace file REKEY: Create Key in PDB 3 resulted in error 46658 *** 2019-02-06T15:27:04.667485+01:00 (CDB$ROOT(1)) REKEY: Activation of Key AdnU5OzNP08Qv1mIyXhP/64AAAAAAAAAAAAAAAAAAAAAAAAAAAAA in PDB 3 resulted in error 28374 REKEY: Keystore needs to be restored from the REKEY backup.Aborting REKEY! Cause: All this hassle started because I accidently deleted the wallet and all wallet backup files too and also forgot the keystore password. There was no way to restore the wallet back. Fortunately in my case the PDB which had encrypted data was supposed to be deco...
7 comments
Read more

How to Find VIP of an Oracle RAC Cluster

<<Back to Oracle RAC Main Page How to Find Out VIP of an Oracle RAC Cluster Login clusterware owner (oracle) and execute the below command to find out the VIP hostname used in Oracle RAC $ olsnodes -i node1     node1-vip node2     node2-vip OR $ srvctl config nodeapps -viponly Network 1 exists Subnet IPv4: 10.0.0.0/255.255.0.0/bondeth0, static Subnet IPv6: Ping Targets: Network is enabled Network is individually enabled on nodes: Network is individually disabled on nodes: VIP exists: network number 1, hosting node node1 VIP Name: node1-vip VIP IPv4 Address: 10.0.0.1 VIP IPv6 Address: VIP is enabled. VIP is individually enabled on nodes: VIP is individually disabled on nodes: VIP exists: network number 1, hosting node node2 VIP Name: node2-vip VIP IPv4 Address: 10.0.0.2 VIP IPv6 Address: VIP is enabled. VIP is individually enabled on nodes: VIP is individually disabled on nodes:
1 comment
Read more

ORA-46630: keystore cannot be created at the specified location

<<Back to DB Administration Main Page ORA-46630: keystore cannot be created at the specified location CDB011> ADMINISTER KEY MANAGEMENT CREATE KEYSTORE '+DATAC4/CDB01/wallet/' IDENTIFIED BY "xxxxxxx"; ADMINISTER KEY MANAGEMENT CREATE KEYSTORE '+DATAC4/CDB01/wallet/' IDENTIFIED BY "EncTest123" * ERROR at line 1: ORA-46630: keystore cannot be created at the specified location Cause  Creating a keystore at a location where there is already a keystore exists Solution To solve the problem, use a different location to create a keystore (use ENCRYPTION_WALLET_LOCATION in sqlnet.ora file to specify the keystore location), or move this ewallet.p12 file to some other location. Note: Oracle does not recommend deleting keystore file (ewallet.p12) that belongs to a database. If you have multiple keystores, you can choose to merge them rather than deleting either of them.
Post a Comment
Read more

ORA-65104: operation not allowed on an inactive pluggable database alter pluggable database open

<<Back to DB Administration Main Page ORA-65104: operation not allowed on an inactive pluggable database SQL> alter pluggable database TEST_CLON open; alter pluggable database TEST_CLON open * ERROR at line 1: ORA-65104: operation not allowed on an inactive pluggable database Cause The pluggable database status was UNUSABLE. It was still being created or there was an error during the create operation. A PDB can only be opened if it is successfully created and its status is marked as NEW in cdb_pdbs.status column SQL> select PDB_NAME,STATUS from cdb_pdbs; PDB_NAME             STATUS -------------------- --------------------------- PDB$SEED             NORMAL TEST_CLON            UNUSABLE Solution:  Drop the PDB and create it again. Related Posts How to Clone Oracle PDB (Pluggable Database) with in the Same Container
Post a Comment
Read more

ORA-16905: The member was not enabled yet

<<Back to Oracle DataGuard Main Page ORA-16905 Physical Standby Database is disabled DGMGRL> show configuration; Configuration - DG_ORCL1P   Protection Mode: MaxPerformance   Members:   ORCL1PP - Primary database     ORCL1PS - Physical standby database (disabled)       ORA-16905: The member was not enabled yet. Fast-Start Failover:  Disabled Configuration Status: SUCCESS   (status updated 58 seconds ago) DGMGRL> DGMGRL> enable database 'ORCL1PS'; Enabled. DGMGRL>  show configuration; Configuration - DG_ORCL1P   Protection Mode: MaxPerformance   Members:   ORCL1PP - Primary database     ORCL1PS - Physical standby database Fast-Start Failover:  Disabled Configuration Status: SUCCESS   (status updated 38 seconds ago)
Post a Comment
Read more

How to Switch Log File from All Instances in RAC

<<Back to Oracle RAC Main Page Switch The Log File of All Instances in Oracle RAC. In many cases you need to switch the logfile of the database. You can switch logfile using alter system switch logfile command but if you want to switch the logfile from all the instances you need to execute the command on all the instances individually and therefore you must login on all the instances. You can avoid this and switch logfile of all instances by just running the below command from any of the instance in RAC database SQL> ALTER SYSTEM SWITCH ALL LOGFILE;   System altered.
Post a Comment
Read more

Starting RMAN and connecting to Database

  <<Back to Oracle Backup & Recovery Main Page Starting RMAN and connecting to Database Starting RMAN and connecting to Database To start RMAN you need to set the environment and type rman and press enter. You can connect to database either using connect command or using command line option. using command line option localhost:$ export ORACLE_HOME=/ora_app/product/18c/dbd2 localhost:$ export PATH=$ORACLE_HOME/bin:$PATH localhost:$ export ORACLE_SID=ORCL1P localhost:$ rman target / Recovery Manager: Release 18.0.0.0.0 - Production on Sun Apr 4 08:11:01 2021 Version 18.11.0.0.0 Copyright (c) 1982, 2018, Oracle and/or its affiliates.  All rights reserved. connected to target database: ORCL1P (DBID=4215484517) RMAN> using connect option localhost:$ rman RMAN> connect target sys@ORCL1P  target database Password:******** connected to target database: ORCL1P (DBID=4215484517) NOTE: To use connect command you need to ensure that  you have proper TNS sentry...
Post a Comment
Read more

How to Attach to a Datapump Job and Check Status of Export or Import

<<Back to Oracle DATAPUMP Main Page How to check the progress of  export or import Jobs You can attach to the export/import  job using ATTACH parameter of oracle datapump utility. Once you are attached to the job you check its status by typing STATUS command. Let us see how Step1>  Find the Export/Import Job Name You can find the datapump job information from  DBA_DATAPUMP_JOBS or  USER_DATAPUMP_JOBS view. SQL> SELECT OWNER_NAME,JOB_NAME,OPERATION,JOB_MODE,STATE from DBA_DATAPUMP_JOBS; OWNER_NAME JOB_NAME                       OPERATION            JOB_MODE   STATE ---------- ------------------------------ -------------------- ---------- ---------- SYSTEM     SYS_EXPORT_FULL_02          ...
7 comments
Read more

ORA-46655: no valid keys in the file from which keys are to be imported

<<Back to DB Administration Main Page SQL> administer key management import encryption keys with secret "xxxx" from '/tmp/pdb02_tde_key.exp' force keystore identified by "xxxx" with backup; administer key management import encryption keys with secret "xxxxxx" from '/tmp/pdb02_tde_key.exp' force keystore identified by "xxxxxx" with backup * ERROR at line 1: ORA-46655: no valid keys in the file from which keys are to be imported Cause: Either the keys to be imported already present in the target database or correct container (PDB) is not set. Solution: In my case I got the error because I attempted to import the keys for newly plugged database PDB02 from CDB$ROOT container. To Solve the issue just switched to the correct container and re run the import. SQL> show con_name CON_NAME ------------------------------ CDB$ROOT <===Wrong Container selected  SQL> alter session set container=PDB02; Session alt...
Post a Comment
Read more