3 Datapump parameters that can help

-

 

1) REMAP_TABLESPACE

Of course we know what this parameter does. It is used on the import to remap the source tablespace to the target tablespace. Usually, I use it this way:

REMAP_TABLESPACE=HRPRD_DATA1:HRTST_DATA, HRPRD_DATA2:HRTST_DATA

In the example above, I am remaping 2 tablespaces to the same target tablespace. This is pretty easy and fast to write, but when you have 10 tablespaces that you want to remap to only one, it’s becoming more inconvenient.

There is a better way that I discovered! The above remap, can be simplified to:

REMAP_TABLESPACE=%:HRTST_DATA

This means that I remap all the source tablespaces to HRTST_DATA. This is amazing, all in one line!

2) LOGTIME

This parameter can be use for export or import datapump, and specifies that the messages that are displayed during the export or import be timestamped. The values for this parameter could be NONE (the default), STATUS, LOGFILE or ALL. I would use ALL for LOGTIME. If you are using older versions of Oracle, ie 11g, this parameter will not be available for you, as it was introduced with 12c.

If you set LOGTIME=ALL, the output will be similar to:

13-DEC-21 19:37:09.920: . . imported "HR_COPY"."EMPLOYEES"       17.08 KB     107 rows
13-DEC-21 19:37:10.154: . . imported "HR_COPY"."EMPLOYEES_COPY"  17.09 KB     107 rows
13-DEC-21 19:37:10.404: . . imported "HR_COPY"."EMPLOYEES_COPY1" 17.09 KB     107 rows
13-DEC-21 19:37:10.716: . . imported "HR_COPY"."LOCATIONS"       8.437 KB      23 rows

You can see the timestamp at the left side, which is very useful!

3) METRICS

This parameter can be used to get additional information on the export or import. The values that you can set are YES or NO (default). The extra information you will receive is the number of objects and elapsed time during the import or export.

If you set METRICS=ALL, the output will be similar to:

W-1 . . imported "HR_COPY"."EMPLOYEES"         17.08 KB     107 rows in 0 seconds using direct_path
W-1 . . imported "HR_COPY"."EMPLOYEES_COPY"    17.09 KB     107 rows in 1 seconds using direct_path
W-1 . . imported "HR_COPY"."EMPLOYEES_COPY1"   17.09 KB     107 rows in 0 seconds using direct_path
W-1 . . imported "HR_COPY"."LOCATIONS"         8.437 KB      23 rows in 1 seconds using direct_path
...
W-1 Processing object type SCHEMA_EXPORT/TABLE/TRIGGER
W-1      Completed 2 TRIGGER objects in 1 seconds
W-1 Processing object type SCHEMA_EXPORT/TABLE/STATISTICS/TABLE_STATISTICS
W-1      Completed 15 TABLE_STATISTICS objects in 0 seconds
source: Diana Robet

Comments

Post a Comment

Popular posts from this blog

Oracle Cloud Infrastructure(OCI) - Part2

-
Image
In my earlier post (OCI -Part1 ), we have gone through OCI basic details, let's dive deep more into it. Before that, we need to u nderstand the following concepts and terminology to help you get started with Oracle Cloud Infrastructure.  Note: OCI is re-branding of Bare Metal Cloud Service (BMCS) BARE METAL HOST Oracle Cloud Infrastructure provides you control of the physical host (“bare metal”) machine. Bare metal compute instances run directly on bare metal servers without a hypervisor. When you provision a bare metal compute instance, you maintain sole control of the physical CPU, memory, and network interface card (NIC). You can configure and utilize the full capabilities of each physical machine as if it were hardware running in your own data center. You do not share the physical machine with any other tenants. REGIONS AND AVAILABILITY DOMAINS  Oracle Cloud Infrastructure is physically hosted in regions and availability domains. A region is a localized geographic area, an...
Read more

Script to display the SQL text for a specific SQL_ID

-
--> Purpose:    Script to display the SQL text  for a specific SQL_ID. -->             It returns the SQL_TEXT. --> Parameters: sql_id --> To Run:     @sqltext.sql sql_id --> Example:    @sqltext.sql 27b3qfm5x89xn --> --> Copyright 2020@The Ultimate SQL Tuning Formula set echo off set define '&' set verify off define _sql_id=&1 set verify off set feedback off set linesize 200 set heading on set termout on col sqltext format a100 word_wrapped select  sql_text as sqltext from gv$sqltext where sql_id = '&_sql_id' order by piece; **************************************************************************************** --> Purpose:    Script to display the SQL text  for a specific SQL_ID. -->             It returns the SQL_TEXT. --> Caution:  ...
Read more

How to Change Your EnterpriseOne Environment Color

-
Image
Sometimes users start working and then forget which EnterpriseOne environment they are logged into. Can you tell which environment you are logged into? Luckily, there is a new UDC that allows you to change your EnterpriseOne environment color. You can now set up environments to be color-coded for when you need a clear visual distinction as to which environment you are logged into. This enables you to quickly identify the non-production environments by color. The new UDC is 98/CO and is available in EnterpriseOne Tools Release 9.2.4 with Applications Release 9.1 and 9.2. The image below shows the default EnterpriseOne environment color. However, you can easily change the color to reflect different environments. For example, DV could be red, PY could be green, and PD could be yellow, as shown below. To do so, just add a new row in the User Defined Codes section, enter the EnterpriseOne environment name and the HEX value of the color you want the environment to be, and ...
Read more