Skip to main content

Oracle Datapump Source_Edition Parameter


<<Back to Oracle DATAPUMP Main Page

EXPDP SOURCE_EDITION

Default: the default database edition on the system
Purpose
Specifies the database edition from which objects will be exported.
Syntax and Description
SOURCE_EDITION=edition_name
This parameter is only useful if there are two or more versions of the same versionable objects in the database. Check Out here Edition Based Redefinition in Oracle Database 11g Release 2 for an overview of Editioning in oracle

Environment Prepration for expdp source_edition demonstration
SQL>  grant create any edition to test;
Grant succeeded.
SQL>select USERNAME,EDITIONS_ENABLED from dba_users where USERNAME='TEST';
USERNAME             E
-------------------- -
TEST                 N
SQL>  create edition my_exp_edition ;
Edition created.
SQL> create edition my_exp_edition2 ;
Edition created.

SQL> SELECT * FROM dba_editions;
EDITION_NAME    PARENT_EDITION_NAME  USA
--------------- -------------------- ---
ORA$BASE                             YES
MY_EXP_EDITION  ORA$BASE             YES
MY_EXP_EDITION2 MY_EXP_EDITION       YES
SQL> alter user test enable editions;
User altered.
SQL> alter session set edition=MY_EXP_EDITION;
Session altered.
SQL> show edition;
EDITION
------------------------------
MY_EXP_EDITION
SQL> create editioning view  MY_EXP_EDITION_V as select * from EXP_EDITION_TEST;
View created.
SQL> alter session set edition=MY_EXP_EDITION2;
Session altered.
SQL> create or replace editioning view  MY_EXP_EDITION_V as select name  from EXP_EDITION_TEST;
View created.
SQL>  select * from MY_EXP_EDITION_V;
NAME
--------------------
TEST
TEST
TEST
TEST
TEST
TEST
TEST
TEST
TEST
TEST
TEST
NAME
--------------------
TEST
TEST
TEST2
14 rows selected.
SQL>  alter session set edition=MY_EXP_EDITION;
Session altered.
SQL> select * from MY_EXP_EDITION_V;

        ID NAME
---------- --------------------
         1 TEST
         1 TEST
         1 TEST
         1 TEST
         1 TEST
         1 TEST
         1 TEST
         1 TEST
         1 TEST
         1 TEST
         1 TEST
        ID NAME
---------- --------------------
         1 TEST
         1 TEST
         1 TEST2
14 rows selected.
Note: As you can see now we have 2 editions of MY_EXP_EDITION_V view one with column id and name and the other with just name

 Lets Export the TEST SCHEMA with specific edition using SOURCE_EIDTION parameter

 $ cat exp.par
DIRECTORY=EXP
DUMPFILE=EXP.DMP
LOGFILE=EXP.LOG
SCHEMAS=TEST
SOURCE_EDITION=MY_EXP_EDITION2
REUSE_DUMPFILES=Y

$ expdp test@PDB01 parfile=exp.par
Export: Release 12.2.0.1.0 - Production on Tue Nov 13 11:15:15 2018
Copyright (c) 1982, 2017, Oracle and/or its affiliates.  All rights reserved.
Password:
Connected to: Oracle Database 12c Enterprise Edition Release 12.2.0.1.0 - 64bit Production
Starting "TEST"."SYS_EXPORT_SCHEMA_01":  test/********@PDB01 parfile=exp.par
Processing object type SCHEMA_EXPORT/TABLE/TABLE_DATA
Processing object type SCHEMA_EXPORT/TABLE/INDEX/STATISTICS/INDEX_STATISTICS
Processing object type SCHEMA_EXPORT/TABLE/STATISTICS/TABLE_STATISTICS
Processing object type SCHEMA_EXPORT/STATISTICS/MARKER
Processing object type SCHEMA_EXPORT/USER
Processing object type SCHEMA_EXPORT/SYSTEM_GRANT
Processing object type SCHEMA_EXPORT/ROLE_GRANT
Processing object type SCHEMA_EXPORT/DEFAULT_ROLE
Processing object type SCHEMA_EXPORT/TABLESPACE_QUOTA
Processing object type SCHEMA_EXPORT/PRE_SCHEMA/PROCACT_SCHEMA
Processing object type SCHEMA_EXPORT/DB_LINK
Processing object type SCHEMA_EXPORT/TABLE/TABLE
Processing object type SCHEMA_EXPORT/TABLE/COMMENT
Processing object type SCHEMA_EXPORT/VIEW/VIEW
Processing object type SCHEMA_EXPORT/TABLE/INDEX/INDEX
Processing object type SCHEMA_EXPORT/TABLE/CONSTRAINT/CONSTRAINT
. . exported "TEST"."EMP"                                5.531 KB       5 rows
. . exported "TEST"."EMP1"                               5.476 KB       1 rows
. . exported "TEST"."TEST"                               5.476 KB       1 rows
. . exported "TEST"."EMP_EDITION2"                       5.484 KB       1 rows
. . exported "TEST"."EXP_EDITION_TEST"                   5.648 KB      14 rows
Master table "TEST"."SYS_EXPORT_SCHEMA_01" successfully loaded/unloaded
******************************************************************************
Dump file set for TEST.SYS_EXPORT_SCHEMA_01 is:
  /u01/dbatst1/stage/EXP.DMP
Job "TEST"."SYS_EXPORT_SCHEMA_01" successfully completed at Tue Nov 13 11:16:15 2018 elapsed 0 00:00:56

 Let us perform an Import using the above export DUMP and see if the SOURCE_EDITION parameter was used while exporting.

 $ cat imp.par
DIRECTORY=EXP
DUMPFILE=EXP.DMP
REMAP_SCHEMA=TEST:TEST_ED
LOGFILE=IMP.LOG

$ impdp test@PDB01 parfile=imp.par
Import: Release 12.2.0.1.0 - Production on Tue Nov 13 11:19:26 2018
Copyright (c) 1982, 2017, Oracle and/or its affiliates.  All rights reserved.
Password:
Connected to: Oracle Database 12c Enterprise Edition Release 12.2.0.1.0 - 64bit Production
Master table "TEST"."SYS_IMPORT_FULL_01" successfully loaded/unloaded
Starting "TEST"."SYS_IMPORT_FULL_01":  test/********@PDB01 parfile=imp.par
Processing object type SCHEMA_EXPORT/USER
Processing object type SCHEMA_EXPORT/SYSTEM_GRANT
Processing object type SCHEMA_EXPORT/ROLE_GRANT
Processing object type SCHEMA_EXPORT/DEFAULT_ROLE
Processing object type SCHEMA_EXPORT/TABLESPACE_QUOTA
Processing object type SCHEMA_EXPORT/PRE_SCHEMA/PROCACT_SCHEMA
Processing object type SCHEMA_EXPORT/DB_LINK
Processing object type SCHEMA_EXPORT/TABLE/TABLE
Processing object type SCHEMA_EXPORT/TABLE/TABLE_DATA
. . imported "TEST_ED"."EMP"                             5.531 KB       5 rows
. . imported "TEST_ED"."EMP1"                            5.476 KB       1 rows
. . imported "TEST_ED"."TEST"                            5.476 KB       1 rows
. . imported "TEST_ED"."EMP_EDITION2"                    5.484 KB       1 rows
. . imported "TEST_ED"."EXP_EDITION_TEST"                5.648 KB      14 rows
Processing object type SCHEMA_EXPORT/VIEW/VIEW
Processing object type SCHEMA_EXPORT/TABLE/STATISTICS/TABLE_STATISTICS
Processing object type SCHEMA_EXPORT/STATISTICS/MARKER
Job "TEST"."SYS_IMPORT_FULL_01" successfully completed at Tue Nov 13 11:19:52 2018 elapsed 0 00:00:24

SQL> select object_name ,object_type from dba_objects where owner='TEST_ED' and object_type='VIEW';
OBJECT_NAME                    OBJECT_TYPE
------------------------------ -----------------------
MY_EXP_EDITION_V               VIEW
SQL>
SQL> select * from MY_EXP_EDITION_V;
NAME
--------------------
TEST
TEST
TEST
TEST
TEST
TEST
TEST
TEST
TEST
TEST
TEST
NAME
--------------------
TEST
TEST
TEST2
14 rows selected.

As you can see only the 2nd edition of the view was exported because we have specified the parameter  SOURCE_EDITION=MY_EXP_EDITION2 in exp.par file.
NOTE: SOURCE_EDITION parameter is also available in impdp with restrictions as mentioned below.

IMPDP SOURCE_EDITION

Default: the default database edition on the remote node from which objects will be fetched
PurposeSpecifies the database edition on the remote node from which objects will be fetched.
Syntax and DescriptionSOURCE_EDITION=edition_name

1> The SOURCE_EDITION parameter is valid on an import operation only when the NETWORK_LINK parameter is also specified.

2> This parameter is only useful if there are two or more versions of the same versionable objects in the database



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