Oracle Data Pump


This chapter gives the original Export and Import utilities a primer on how to move up to the faster, more powerful, and more flexible Data Pump Export and Import utilities.

In this Chapter I going to export and import SALES schema

Export Schema

Step 1 : Login to Source Database server

login as: orapreprod

password:******

$ cd /u03/CRP02/db/tech_st/12.1.0/

$ . CRP2_dev.env

$ sqlplus "/as sysdba"

Step 2 : Connect as system user

SQL> conn system/clonemanager
Connected.

SQL> desc all_directories;
 Name                                      Null?    Type
 ----------------------------------------- -------- ----------------------------
 OWNER                                     NOT NULL VARCHAR2(128)
 DIRECTORY_NAME                            NOT NULL VARCHAR2(128)
 DIRECTORY_PATH                                     VARCHAR2(4000)
 ORIGIN_CON_ID                                      NUMBER

Step 4 : Creating Directory Objects If doesn’t exist

If You Want to create New DATAPUMP_DIR DIRECTORY

SQL> CREATE OR REPLACE DIRECTORY DATA_PUMP_DIR AS '/u03/CRP02/DATA_PUMP_DIR';

SQL> select OWNER,DIRECTORY_NAME,DIRECTORY_PATH from ALL_DIRECTORIES;

SYS
DATA_PUMP_DIR
/u03/CRP02/DATA_PUMP_DIR

$ cd /u03/CRP02/

$ mkdir DATA_PUMP_DIR

$ cd /u03/CRP02/DATA_PUMP_DIR/

$ pwd
/u03/CRP02/DATA_PUMP_DIR

$ cd /u03/CRP02/db/tech_st/12.1.0/

$ . CRP2_dev.env

Step 5 : Export shema from source database

$ expdp system/clonemanager schemas=SALES directory=DATA_PUMP_DIR dumpfile=30AUG17_SALES_SCHEMA.dmp logfile=30AUG17_SALES_SCHEMA.log

Master table "SYSTEM"."SYS_EXPORT_SCHEMA_01" successfully loaded/unloaded
******************************************************************************
Dump file set for SYSTEM.SYS_EXPORT_SCHEMA_01 is:
  /u03/CRP02/DATA_PUMP_DIR/30AUG17_SALES_SCHEMA.dmp
Job "SYSTEM"."SYS_EXPORT_SCHEMA_01" successfully completed at Wed Aug 30 16:17:58 2017 elapsed 0 00:15:11

$ cd /u03/CRP02/DATA_PUMP_DIR/

$ ls -lrt
-rw-r--r-- 1 orapreprod dba     41016 Aug 30 16:17 30AUG17_SALES_SCHEMA.log
-rw-r----- 1 orapreprod dba 493174784 Aug 30 16:17 30AUG17_SALES_SCHEMA.dmp

Step 6 : Copy Exported dumpfile to target database

$ scp -pr 30AUG17_SALES_SCHEMA.dmp orauat@172.25.4.50:/u01/UAT/DATA_PUMP_DIR

The authenticity of host '172.25.4.50 (172.25.4.50)' can't be established.
RSA key fingerprint is 49:81:30:ed:2c:17:5c:79:ee:30:79:2d:15:b0:f3:9e.
Are you sure you want to continue connecting (yes/no)? yes
Warning: Permanently added '172.25.4.50' (RSA) to the list of known hosts.
orauat@172.25.4.50's password:
30AUG17_SALES_SCHEMA.dmp                      100%  470MB 156.8MB/s   00:03

Import Schema

Step 1 : Login to Target database server

login as : orauat

password : ******

$ cd /u01/UAT/db/tech_st/12.1.0

$ . UAT_ebsuatdb.env

$ sqlplus "/as sysdba"

$ cd /u01/UAT

Step 2 : Creating Directory Objects If doesnot exist

$ mkdir DATA_PUMP_DIR

SQL> CREATE OR REPLACE DIRECTORY DATA_PUMP_DIR AS '/u01/UAT/DATA_PUMP_DIR';

$ cd DATA_PUMP_DIR/

$ pwd
/u01/UAT/DATA_PUMP_DIR

Step 3 : Backup SCHEMA if already exist target database 

$ expdp system/clonemanager schemas=SALES directory=DATA_PUMP_DIR dumpfile=30AUG17_SALES_SCHEMA_BACKUP.dmp logfile=30AUG17_SALES_SCHEMA_BACKUP.log

Master table "SYSTEM"."SYS_EXPORT_SCHEMA_01" successfully loaded/unloaded
******************************************************************************
Dump file set for SYSTEM.SYS_EXPORT_SCHEMA_01 is:
  /u01/UAT/DATA_PUMP_DIR/30AUG17_SALES_SCHEMA_BACKUP.dmp
Job "SYSTEM"."SYS_EXPORT_SCHEMA_01" successfully completed at Wed Aug 30 16:04:49 2017 elapsed 0 00:14:20

$ ls -lrt
-rw-r-----. 1 orauat dba 35319808 Aug 30 16:04 30AUG17_SALES_SCHEMA_BACKUP.dmp
-rw-r--r--. 1 orauat dba    33531 Aug 30 16:04 30AUG17_SALES_SCHEMA_BACKUP.log

$ pwd
/u01/UAT/DATA_PUMP_DIR

Step 4 : Drop Existing Schema

Before drop user connect and check the DEFAULT TABLESPACE and TEMPORARY TABLESPACE of particular schema.

SQL> select * from DBA_USERS where username='SALES';

$ sqlplus "/as sysdba"

SQL> drop user sales cascade;
drop user sales cascade
*
ERROR at line 1:
ORA-01940: cannot drop a user that is currently connected

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

Currently SALES User connected
So disconnect the SALES user by below steps

Kill connected user session
---------------------------------
SQL > select
       substr(a.spid,1,9) pid,
       substr(b.sid,1,5) sid,
       substr(b.serial#,1,5) ser#,
       substr(b.machine,1,6) box,
       substr(b.username,1,10) username,
--       b.server,
       substr(b.osuser,1,8) os_user,
       substr(b.program,1,30) program
from v$session b, v$process a
where
b.paddr = a.addr
and type='USER'
order by spid; 

$ kill -9 26713

$ sqlplus "/as sysdba"

SQL> drop user sales cascade;

User dropped.

Step 5 : Create Schema

SQL>CREATE USER SALES IDENTIFIED BY sales DEFAULT TABLESPACE APPS_POS_DATA TEMPORARY TABLESPACE TEMP1 PROFILE DEFAULT ACCOUNT UNLOCK;

$ ls -lrt

-rw-r-----. 1 orauat dba  35319808 Aug 30 16:04 30AUG17_SALES_SCHEMA_BACKUP.dmp
-rw-r--r--. 1 orauat dba     33531 Aug 30 16:04 30AUG17_SALES_SCHEMA_BACKUP.log
-rw-r-----. 1 orauat dba 493174784 Aug 30 16:17 30AUG17_SALES_SCHEMA.dmp

Step 6: Now Import the schema from source dump file.

Copy the source dump file to target database.
And run the below command

$ impdp system/clonemanager schemas=SALES directory=DATA_PUMP_DIR dumpfile=30AUG17_SALES_SCHEMA.dmp logfile=30AUG17_SALES_SCHEMA.log remap_schema=SALES:SALES

OERR: ORA-28040 "No matching authentication protocol" Reference Note (Doc ID 288402.1)

OERR: ORA-28040 "No matching authentication protocol" Reference Note (Doc ID 288402.1)

PURPOSE

This is a brief reference note to show the meaning of database error "ORA-28040". It includes the error text, "Cause" and "Action" from message files for each database version from 9.2 onwards, along with search links and details of any database bug issues related to the error.

SCOPE

This note is intended for general audience as a starting point to check the meaning of "ORA-28040". It does not give detailed information about the error and does not give error message text for versions below 9.2 .

DETAILS

Error Text, Cause and Action from Message File/s for ORA-28040

Versions 12.1

Error:  ORA-28040 No matching authentication protocol 
---------------------------------------------------------------------------
Cause:  There was no acceptable authentication protocol for either client or 
 server. 
Action: The administrator should set the values of the 
 SQLNET.ALLOWED_LOGON_VERSION_SERVER and 
 SQLNET.ALLOWED_LOGON_VERSION_CLIENT parameters, on both the client and 
 on the server, to values that match the minimum version software 
 supported in the system. This error is also raised when the client is 
 authenticating to a user account which was created without a verifier 
 suitable for the client software version. In this situation, that 
 account's password must be reset, in order for the required verifier to 
 be generated and allow authentication to proceed successfully. 

Versions 10.1, 10.2, 11.1, 11.2

Error:  ORA-28040 No matching authentication protocol 
---------------------------------------------------------------------------
Cause:  No acceptible authentication protocol for both client and server 
Action: Administrator should set SQLNET_ALLOWED_LOGON_VERSION parameter on 
 both client and servers to values that matches the minimum version 
 supported in the system. 

1.Go to Database server

2.source database environment file

3.cd $TNS_ADMIN

4.vi sqlnet.ora

5.add below line



SQLNET.ALLOWED_LOGON_VERSION_SERVER=8

SQLNET.ALLOWED_LOGON_VERSION_CLIENT=8

TABLESPACE And Temporary Tablespace Analyse

select file_name,bytes/1024/1024/1024 from dba_data_files where TABLESPACE_NAME='APPS_TS_TX_DATA';

--ALTER DATABASE DATAFILE '/kzn01/TEST/db/apps_st/data/a_txn_data06.dbf' RESIZE 2G;

----------------------------------------
select * from dba_data_files where TABLESPACE_NAME='APPS_TS_TX_IDX';

ALTER TABLESPACE APPS_TS_TX_IDX ADD DATAFILE '/kzn03/Oracle/PROD/db/apps_st/data/a_txn_ind07.dbf' SIZE 2G;

---------------------------------------
list tablespaces, size, free space, and percent free
 
SELECT df.tablespace_name TABLESPACE, 
df.total_space_mb TOTAL_SPACE_GB,
(df.total_space_mb - fs.free_space_mb) USED_SPACE_GB, fs.free_space_mb FREE_SPACE_GB,
ROUND(100 * (fs.free_space / df.total_space),2) PCT_FREE
FROM (SELECT tablespace_name, SUM(bytes) TOTAL_SPACE,TRUNC((SUM(bytes) / 1048576/1024),2) TOTAL_SPACE_MB
FROM dba_data_files GROUP BY tablespace_name) df,
(SELECT tablespace_name, SUM(bytes) FREE_SPACE,TRUNC((SUM(bytes) / 1048576/1024),2) FREE_SPACE_MB
FROM dba_free_space GROUP BY tablespace_name) fs
WHERE df.tablespace_name = fs.tablespace_name(+) ORDER BY fs.tablespace_name;



--------------------------------------------------
Full database size

SELECT ROUND (SUM (used.bytes) / 1024 / 1024 / 1024) || ' GB'
"Database Size",ROUND (SUM (used.bytes) / 1024 / 1024 / 1024)
- ROUND (free.p / 1024 / 1024 / 1024)|| ' GB' "Used space",
ROUND (free.p / 1024 / 1024 / 1024) || ' GB' "Free space"
FROM (SELECT   bytes FROM v$datafile UNION ALL
SELECT bytes FROM v$tempfile UNION ALL SELECT bytes FROM v$log) used,
(SELECT SUM (bytes) AS p FROM dba_free_space)free GROUP BY free.p;

============================================================================

Master Note: Overview of Oracle Temporary Tablespaces (Doc ID 1498442.1)

SELECT PROPERTY_NAME, PROPERTY_VALUE
FROM database_properties
WHERE property_name='DEFAULT_TEMP_TABLESPACE';

SELECT group_name, tablespace_name FROM dba_tablespace_groups;
SELECT * FROM dba_tablespace_groups;

SELECT PROPERTY_NAME, PROPERTY_VALUE
FROM database_properties
WHERE property_name='DEFAULT_TEMP_TABLESPACE';


SELECT * FROM dba_tablespace_groups;

SELECT TABLESPACE_NAME,free_space/1024/1024/1024 from DBA_TEMP_FREE_SPACE;

SELECT * from DBA_TEMP_FREE_SPACE;

SELECT file#, name, bytes/1024/1024 mb FROM v$tempfile;

SELECT * FROM v$tempfile;

 
 
-- /u03/CRP1GST/db/apps_st/data/temp02.dbf
 
--ALTER DATABASE TEMPFILE '/u01/UAT/db/apps_st/data/temp03.dbf' RESIZE 2G;
 --ALTER TABLESPACE TEMP2 ADD TEMPFILE '/u01/app/oracle/tempfile/tempo3.dbf' size 1000M reuse;
 commit;
 

TBALESPACE CHECK

 
 SELECT df.tablespace_name TABLESPACE, 
df.total_space_mb TOTAL_SPACE_GB,
(df.total_space_mb - fs.free_space_mb) USED_SPACE_GB, fs.free_space_mb FREE_SPACE_GB,
ROUND(100 * (fs.free_space / df.total_space),2) PCT_FREE
FROM (SELECT tablespace_name, SUM(bytes) TOTAL_SPACE,TRUNC((SUM(bytes) / 1048576/1024),2) TOTAL_SPACE_MB
FROM dba_data_files GROUP BY tablespace_name) df,
(SELECT tablespace_name, SUM(bytes) FREE_SPACE,TRUNC((SUM(bytes) / 1048576/1024),2) FREE_SPACE_MB
FROM dba_free_space GROUP BY tablespace_name) fs
WHERE df.tablespace_name = fs.tablespace_name(+) ORDER BY fs.tablespace_name;

EXPDP / IMPDP TABLE in oracle database

If You Want Export Particular Table 

expdp system/manager directory=DATA_PUMP_DIR tables='sales.XXPOS_NEW_ORDER_LINES_STG' DUMPFILE=XXPOS_NEW_ORDER_LINES_STG.dmp

Import Command

impdp system/manager directory=DATA_PUMP_DIR tables='sales.XXPOS_NEW_ORDER_LINES_STG' DUMPFILE=XXPOS_NEW_ORDER_LINES_STG.dmp

Reference Video

https://www.youtube.com/watch?v=QmFsC_3tSgU

EXPDP / IMPDP Schema in oracle database

Export Command

expdp system/manager schemas=PMS directory=DATA_PUMP_DIR dumpfile=13JUL17PMS_SCHEMA.dmp logfile=13JUL17PMS_SCHEMA.log

Import Command

impdp system/clonemanager schemas=PMS directory=DATA_PUMP_DIR dumpfile=13JUL17PMS_SCHEMA.dmp logfile=13JUL17PMS_SCHEMA.log remap_schema=PMS:PMS

Source : CRP1

Destination : GST

I am Having PMS Schema in CRP1 Instance.

I need the same schema in GST Instance.

So First I am going to Export PMS schema

Step 1:

Connect as system/manager

desc ALL_DIRECTORIES;

select OWNER,DIRECTORY_NAME,DIRECTORY_PATH from ALL_DIRECTORIES;

Find the DATA_PUMP_DIR Location

Step 2:

If You Want to create New DATAPUMP_DIR DIRECTORY

CREATE OR REPLACE DIRECTORY DATA_PUMP_DIR AS '/u01/backup/DATAPUMP_DIR';

Step 3:

expdp system/manager schemas=PMS directory=DATA_PUMP_DIR dumpfile=13JUL17PMS_SCHEMA.dmp logfile=test.log

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

Once PMS Schema Exported need to be import in GST instance.

Import the same schema in GST instance.

Step to remember,

In GST instance there is no schema available with name of PMS.

Now only i am going to Import.

Step 1:

desc ALL_DIRECTORIES;

select OWNER,DIRECTORY_NAME,DIRECTORY_PATH from ALL_DIRECTORIES;

CREATE OR REPLACE DIRECTORY DATA_PUMP_DIR AS '/u03/CRP1GST/DATA_PUMP_DIR';

commit;

Before Import Schema Need to create the same TABLESPACE which exist in CRP1 instance for default PMS schema.

Step 2 :

CREATE TABLESPACE TBZ_CUSTOM DATAFILE '/u03/CRP1GST/db/apps_st/data/tbz_custom01.dbf' SIZE 2G;

CREATE TEMPORARY TABLESPACE TEMP_CUSTOM TEMPFILE '/u03/CRP1GST/db/apps_st/data/tbz_temp01.dbf' SIZE 500M AUTOEXTEND ON;

Step 3 :

impdp system/clonemanager schemas=PMS directory=DATA_PUMP_DIR dumpfile=13JUL17PMS_SCHEMA.dmp logfile=13JUL17PMS_SCHEMA.log remap_schema=PMS:PMS

Create DB LINK

Create DB LINK

step 1:

connect as system user 

select * from dba_db_links;

step 2:

I am getting already created db link named below.

PUBLIC APPS.CHEMFABNT.COM APPS (DESCRIPTION =(ADDRESS = (PROTOCOL = TCP)(HOST = caltest.chemfabnt.com)(PORT = 1562))(CONNECT_DATA = (SERVICE_NAME = TEST))) 01-DEC-16 12.40.39
DROP PUBLIC DATABASE LINK APPS;


step 3:

suppose i need to use existing db link or create new dblink

step 4:

now i am going to drop existing db link created by system user (db link name is PUBLIC)

DROP PUBLIC DATABASE LINK APPS;

step 5:

to create new db link (as a system user)

CREATE PUBLIC DATABASE LINK APPS  connect to apps identified by cloneapps USING '(DESCRIPTION =(ADDRESS = (PROTOCOL = TCP)(HOST = caltest.chemfabnt.com)(PORT = 1562))(CONNECT_DATA = (SERVICE_NAME = TEST)))';

step 6:

to create new db link ( as a another user)

APPS (DESCRIPTION= (ADDRESS=(PROTOCOL=tcp)(HOST=prodebs.chemfabnt.com)(PORT=1522)) (CONNECT_DATA= (SERVICE_NAME=PROD) (INSTANCE_NAME=PROD))) 22-JUN-16 10.27.51



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


select db_link from USER_DB_LINKS;


create database link XXCAL  connect to apps identified by cloneapps USING '(DESCRIPTION =(ADDRESS = (PROTOCOL = TCP)(HOST = caltest.chemfabnt.com)(PORT = 1562))(CONNECT_DATA = (SERVICE_NAME = TEST)))';

select CREATED,LOG_MODE,OPEN_MODE,ARCHIVELOG_CHANGE# from v$database@APPS;

desc V$database;

Database User check / Query

DBA USER Check
------------------------

SQL> select * from dba_users  where username='APPSREADONLY';

DROP User in Oracle Database

DROP USER
-----------------

DROP USER APPSREADONLY CASCADE;

 select * from dba_users  where username='APPSREADONLY';

 DROP USER APPSREADONLY CASCADE;

 commit;

Read only User Create in Oracle Database

1. Create user:

create user APPSREADONLY identified by APPSREADONLY123 default tablespace APPS_TS_TX_DATA;


2. Create Role:

Create role readrole;
Grant create session to readrole;
Grant connect to readrole;
Grant select any table to readrole;
Grant execute any procedure to readrole;
Grant create trigger to readrole;

3. Grant role to user:

Grant readrole to APPSREADONLY;

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

If User need to have an existing user privelegemeans run below query
Eg.
I am creating now APPSREADONLY user and this user having all the priveleges of APPS user.


4. Create trigger:

Login as APPSREADONLY and create the following trigger:

Create or replace trigger rlogin_trigger
After logon on APPSREADONLY.schema
declare
Begin
EXECUTE IMMEDIATE 
        'declare begin ' ||
        'dbms_application_info.set_client_info ( 101 ); end;';
EXECUTE IMMEDIATE 'ALTER SESSION SET CURRENT_SCHEMA =APPS';
END;
/

Schema / User Creation in Oracle Database

Schema Creation in Oracle Database
---------------------------------------------

-- TO CREATE TABLESPACE

CREATE TABLESPACE TBS_XXAPLDALL DATAFILE 'datafile_name.dbf' SIZE 3G;

CREATE TEMPORARY TABLESPACE TEMP_XXAPLDALL TEMPFILE 'tempfile_name.dbf' SIZE 5M AUTOEXTEND ON;

-- TO CREATE SCHEMA

CREATE USER XXAPLDALL IDENTIFIED BY XXAPLDALL DEFAULT TABLESPACE TBS_XXAPLDALL TEMPORARY TABLESPACE TEMP_XXAPLDALL PROFILE DEFAULT ACCOUNT UNLOCK;

-- TO CREATE SESSION

GRANT CREATE SESSION TO systemappsil;

-- TO ALTER SESSION

GRANT ALTER SESSION TO systemappsil;

-- TO CREATE SYNONYM

GRANT CREATE SYNONYM TO systemappsil;

-- TO CREATE TABLE

GRANT CREATE TABLE TO systemappsil;

-- TO CREATE VIEW

GRANT CREATE VIEW TO systemappsil;

-- TO CREATE SEQUENCE

GRANT CREATE SEQUENCE TO systemappsil;

-- TO CREATE TRIGGER 

GRANT CREATE TRIGGER TO systemappsil;

-- TO CREATE PROCEDURE

GRANT CREATE PROCEDURE TO systemappsil;

-- TO UNLIMIT TABLESPACE

GRANT UNLIMITED TABLESPACE TO systemappsil;

-- TO GIVE THE EDITIONS:

ALTER USER XXAPLDALL ENABLE EDITIONS;

-- TO GIVE THE "ENQUEUE","DEQUEUE" PRIVILEGE

begin
 DBMS_AQADM.GRANT_SYSTEM_PRIVILEGE(
        PRIVILEGE => 'ENQUEUE_ANY',
        GRANTEE => 'XXAPLDALL',
        ADMIN_OPTION => FALSE);

DBMS_AQADM.GRANT_SYSTEM_PRIVILEGE(
        PRIVILEGE => 'DEQUEUE_ANY',
        GRANTEE => 'XXAPLDALL',
        ADMIN_OPTION => FALSE);
        end ;

-- TO CREATE EXECUTE PRIVILEGE

grant execute any procedure to XXAPLDALL;


*************************************************************************************************************
USER CREATION LIKE APPS/SYSTEM :

CREATE OR REPLACE TRIGGER readonly_logon_trg
AFTER logon ON systemappsil.SCHEMA
DECLARE
BEGIN
EXECUTE IMMEDIATE 
        'declare begin ' ||
        'dbms_application_info.set_client_info ( 101 ); end;';
EXECUTE IMMEDIATE 'ALTER SESSION SET CURRENT_SCHEMA =SYSTEM';
END;
/

*************************************************************************************************************