Data pump full export/Full Import - lack of subsidies sys

I finished the complete database and then full import export in the new database. With the help of Data pump. Everything worked except some users lack of subsidies sys objects in the new database.

For example, in the original database where I took full export UserX had this grant:
GRANT SELECT ON SYS. DBA_DATA_FILES UserX, but the same user in the new database does not grant.

Is this expected or a bug like this? I would be grateful if someone who had the same problem to share with me.

Oracle Version: 10.2.4

Thank you.

Please, read the restriction of the following:
http://download.Oracle.com/docs/CD/B19306_01/server.102/b14215/dp_export.htm#sthref126
"+ Grants on belonged to the SYS schema objects are never exported. + »

Nicolas.

Tags: Database

Similar Questions

Export the whole (10 GB) using Data Pump utility export base
Hello

I have a requirement that we have to export all of the base (10 GB) using Data Pump export utility because it is not possible to send the discharge of 10 GB in a CD/DVD for the seller of our application system (to analyze a few problems that we have).

Now when I checked online full export is available but not able to understand how it works, as we never used this data pump utility, we use the method of normal export. In addition, the data pump will reduce the size of the dump file so it can fit on a DVD or can we use utility export parallel DB full to split the files and include them in a DVD, it is possible.

Please correct me if I am wrong and kindly help.

Thank you for your help in advance.
Pravin,

The server saves files in the directory object that you specify on the command line. So what you want to do is:

1. from your operating system, find an existing directory or create a new directory. In case you, C:/Dump is as good a place as any.

2. connect to sqlplus and create the directory object. Just use the path. I use linux, so my directory looks like/scratch/xxx/yyy
If you use Windows, the path to your directory would look like C:/Dump you should not attack.

3. don't forget to grant access to this directory. You can grant access to a single user, group of users, or the public. Just like
any other object.

If it helps, or if she has answered your question, please mark messages with the appropriate tag.

Thank you

Dean

Data Pump Export/Import

Hello Forum,
I have a question regarding imports and exports of data pump, perhaps what I should already know.
I need to empty a table that has about 200 million lines, that I need to get rid of about three quarters of data.
My intention is to use the data pump to export the table and and indexes and constraints etc..
The table has no relationship to any other table, it is composed of approximately 8 columns with constraints not null.
My plan is
1 truncate table
2. disable or remove index
3 leave the constraints in place?
4. use data pump to import a lines to keep.
My question
will be my clues and imported too much constraints I want to import only a subset of my exported table?
or
If I dropped the table after truncation, I'll be able to import my table and indexes, even if I use the sub as part of my statement to import query functionality?
My table using the query sub in data pump functionality must exist in the database before doing the import
or handful of data pump import as usual IE will create table indices grants and statistics etc.?
Thank you for your comments.
Concerning

Your approach is ineffective.

What you need to do is to

create the table in select foo * bar where the

bar of truncate table;

Insert / * + APPEND * / into select bar * foo.

Rebuild the indexes on the table.

Fact.

This whole thing with expdp and impdp is only a waste of resources. My approach generates redo a minimum.

----------

Sybrand Bakker

Senior Oracle DBA

Data Pump: export/import tables in different schemas

Hi all
I use Oracle 11.2 and I would like to use the data pump to export / import data into the tables between the different schemas. The table already exists in the source and target schemas. Here are the commands that I use:

Script working export:
expdp scott/tiger@db12 schema = source include = TABLE:------"IN (\'TB_TEST1 ', \'TB_ABC')\ 'directory = datapump_dir dumpfile = test.dump logfile = test_exp.log
Script to import all the desks:
Impdp scott/tiger@db12 remap_schemas = rΘpertoire source: target = datapump_dir dumpfile = test.dump logfile = test_imp.log content = data_only table_exists_action = truncate
Script error for some tables to import:
Impdp scott/tiger@db12 remap_schemas = source: target include = TABLE:------"IN (\'TB_TEST1')\' directory = datapump_dir dumpfile = test.dump logfile = test_imp.log content = data_only
Export is good, I got the folling error when I try to import the table TB_TEST1 only: "ORA-31655: no metadata data_or objectsz selected for employment. The user scott is a DBA role, and it works fine when I try to import all tables being export without the include clause.
It is possble to import some tables but not all tables in the export file?
Thanks for the help!

942572 wrote:

It's good to import all tables exported through Scott, who do NOT have the clause 'include '.

I have the error only when I try to import some tables with clause "include".

Can I import only some table since the export dump file? Thank you!

you use INCLUDE incorrectly!

do below yourself

Impdp help = yes

INCLUDE

Include the specific object types.

For example, INCLUDE TABLE_DATA =.

Moving database from 1 server to another via Data Pump - some queries
Hello

I am planing to move my database from one windows server to another. Part of the obligation is also to update this database 10g to 11.2.0.3. So I'm combining 2 tasks using the export / import method (via Data Pump) upgrade.

Regarding export / import (which will be a pump full data of the database export) my plan is.

create an empty 11.2.0.3 target database on the server (same number of control files, and redo logs etc.) ready for an import of the source database
Q1. This will create tablespaces SYSTEM and UNDO - I presume the datapump export doesn't include these spaces of storage anyway?

For export, I intend to simulate CONSISTENT = Y using FLASHBACK_TIME = SYSTIMESTAMP
Q2. What is the return of flame characteristics must be active on the source database to use this knowledge should I Flashback Database enabled on the source (as opposed to other flashback features) database?

My target is a virtual server with a single virtual processor
Q3. Is there any point PARALLEL usinng in the import settings file (normally I would fix this number of processors - however in the case of this virtual server, it is actually onely a virtual processor)?

For the import, I intend to use the REMAP_DATAFILE option to change the location of the data files on the target server

Q4. If the import fails before the end, what is the best course of action? for example I just let go of data storage spaces and remake a complete import?

Thank you
Jim
Jim,

I'll take a pass on your questions:

create an empty 11.2.0.3 target database on the server (same number of control files, and redo logs etc.) ready for an import > source database
Q1. This will create tablespaces SYSTEM and UNDO - I presume the datapump export does not include these storage spaces > anyway?

The system tablespace is created when you create a database, but the Data Pump will export and try to import. It will fail with tablespace exists. I am sure that the undo tablespace will be also exported and imported. If they are there, then just import will report that they already exist.

For export, I intend to simulate CONSISTENT = Y using FLASHBACK_TIME = SYSTIMESTAMP
Q2. What is the return of flame characteristics must be active on the source database to use this knowledge should I Flashback Database active > on the source (as opposed to other flashback features) database?

I know not true about it. I thought that you need just enough cancel, but I hope that others will run in.

My target is a virtual server with a single virtual processor
Q3. Y at - it no PARALLEL point usinng in the import settings file (normally I put this on the number of processors - > however in the case of this virtual server, it is actually onely a virtual processor)?

We recommend usually 2 times the number of processes, so 2 parallel should be ok.

For the import, I intend to use the REMAP_DATAFILE option to change the location of the data files on the target server

Q4. If the import fails before the end, what is the best course of action? that is, do I just give up storage of data and redo a > full import?

It depends what is failure. Most of the failures will not stop work, but if this is the case, then most of these jobs may simply be restarted. To restart a job, you just need to know the name of the task, which is printed as you start to export/import, or you name the task in your order Data Pump. To restart, follow these steps:

password/user Impdp attach = job_name

If you do not name the work, the name of the job will be something like

User.sys_import_full_01

Hope that helps - and good luck with your migration.

Dean

a question about data pump
Hello

I'm running a full database export using data pump. (full = y)

To ensure data integrity, I have blocked certain patterns before starting the exp.
I want to assure you that these patterns locked still be exported (not not being ignored), right?

Please help confirm.

Thank you very much.

db version: 10.2.0.3 in Linux 5

Published by: 995137 on April 23, 2013 15:30
Hello
If a schema is locked/unlocked makes no difference to datapump - he extracted them anyway with a full extract. The log file should list all the tables that are expoted, so you should see them there.

Kind regards
Harry

A full import by using datapump will overwrite the target database data dictionary?

Hello
I have a 11G with 127 GB database. I did a full export using expdp as a user of the system. I'll import the created dump file (which is 33 GB) on the basis of data from 12 c target.
When I do the full import on the 12 c database data dictionary is updated with new data. But as is it already contained data dictionary? It will also change?
Thanks in advance

Hello

In addition to the responses of the other comrades

To start, you need to know some basic things:

The dictionary database tables are owned by SYS and must of these tables is created when the database is created.

Thus, in the different versions of database Oracle there could be less or more data dictionary tables of different structure database,.

so if this SYSTEM base tables are exported and imported between different versions of oracle, could damage the features of database

because the tables do not correspond with the version of database.

See the Ref:

SYS, owner of the data dictionary

Database Oracle SYS user is owner of all the base tables and a view of the data available to the user dictionary. No Oracle database user should never change (UPDATE, DELETE, or INSERT) ranks or schema objects contained in the SYS schema, because this activity can compromise the integrity of the data. Security administrator must keep strict control of this central account.

Source: http://docs.oracle.com/cd/B28359_01/server.111/b28318/datadict.htm

Prosecutor, the utilities for export cannot export the dictionary SYS base tables and is marked

as a note in the documentation:

Data Pump export Modes

Note:

Several patterns of system cannot be exported because they are not user patterns; they contain metadata and data managed by Oracle. Examples of system schemas that are not exported MDSYS SYS and ORDSYS.

Source: https://docs.oracle.com/cd/E11882_01/server.112/e22490/dp_export.htm#SUTIL826

That's why import cannot modify/alter/drop/create dictionary database tables. If you can not export, so you can not import.

Import just to add new Non - SYS objects/data in the database, therefore new data are added to the dictionary base tables (as new users, new tables, code pl/sql etc).

I hope that this might answer your question.

Kind regards

Juan M

Differences between Data Pump and always by inheritance, import and export

Hi all
I work as a junior in my organization dba and I saw that my organization still uses legacy import and export utility instead of Oracle Data Pump.
I want to convence my manager to change the existing deal with Oracle Data Pump, I have a meeting with them to keep my points and convence them for Oracle utility pump data.
I have a week very convencing power but I won't miss to discover myself, I can't work myself and really a need with differences of strength against import and export, it would be really appreciated if someone can put strong points against Oracle Data pump on legacy import and export.
Thank you
Cabbage

Hello

a other people have already said the main advantage of datapump is performance - it is not just a little more fast exp/imp it is massively faster (especially when combined with parallel).

It is also more flexible (once much more) - it will even create users with exports level schema which imp can't do for you (and it is very annoying that he could never).

It is reusable

It has an api plsql

It supports all types of objects and new features (exp is not - and that alone is probably reason to spend)

There even a 'legacy' at 11.2 mode where most of your old exp parameter file will still work with him - just change exp expdp and impdp print.

The main obstacle to the transition to datapump seems to be all "what do you mean I have to create a directory so that it works", well who and where is my dumpfile why can't it be on my local machine. These are minor things to go well beyond.

I suggest do you some sort of demo with real data of one of your large databases - do a full exp and a full expdp with parallel and show them the runtimes for them to compare...

See you soon,.

Rich

Export data pump job scheduler does not load

I have a pump a 10.2.0.2.0 data dump file database, and then import on 11.2.0.3.0 fails with this error:

ORA-39083: Object type PROCOBJ failed to create with error:
ORA-06502: PL/SQL: numeric or value error: character to number conversion error
Failing sql is:
BEGIN 
dbms_scheduler.create_job('"MY_JOB_NAME"',
job_type=>'STORED_PROCEDURE', job_action=>
'MY_SCHEMA.MY_PROCEDURE'
, number_of_arguments=>0,
start_date=>'31-JUL-12 02.05.13.782000 PM EUROPE/BERLIN', repeat_interval=> 
'FREQ=WEEKLY;BYDAY=FRI;BYHOUR=7;BYMINUTE=0;BYSECOND=0'
, end_date=>NULL,
job_class=>'"DEFAULT_JOB_CL
{code}

I extracted the SQL Code from the dump file and it looks like this:
{code}
BEGIN 
dbms_scheduler.create_job('"MY_JOB"',
job_type=>'STORED_PROCEDURE', job_action=>
'MY_SCHEMA.MY_PROCEDURE'
, number_of_arguments=>0,
start_date=>'31-JUL-12 02.05.13.782000 PM EUROPE/BERLIN', repeat_interval=> 
'FREQ=WEEKLY;BYDAY=FRI;BYHOUR=7;BYMINUTE=0;BYSECOND=0'
, end_date=>NULL,
job_class=>'"DEFAULT_JOB_CLASS"', enabled=>FALSE, auto_drop=>FALSE,comments=>
'bla bla comment'
);
dbms_scheduler.set_attribute('"MY_JOB"','logging_level','HIGH');
dbms_scheduler.enable('"MY_JOB"');
COMMIT; 
END; 
/ 
{code}



After the job is defined the second statement fails:

{code}
SQL> exec dbms_scheduler.set_attribute('"MY_JOB"','logging_level','HIGH');
BEGIN dbms_scheduler.set_attribute('"MY_JOB"','logging_level','HIGH'); END;

*
ERROR at line 1:
ORA-06502: PL/SQL: numeric or value error: character to number conversion error
ORA-06512: at "SYS.DBMS_SCHEDULER", line 2851
ORA-06512: at line 1
{code}


From the source I see:

{code}
SQL> select logging_level from dba_scheduler_jobs where job_name = 'MY_JOB';

LOGG
----
FULL
{code}

In the docs I see these valid LOGGING_LEVELs:
http://docs.oracle.com/cd/E14072_01/server.112/e10595/scheduse008.htm#CHDFDFAB

DBMS_SCHEDULER.LOGGING_OFF
DBMS_SCHEDULER.LOGGING_FAILED_RUNS
DBMS_SCHEDULER.LOGGING_RUNS
DBMS_SCHEDULER.LOGGING_FULL

So please help me, I can't find something useful on MOS, what is Data Pump exporting there, and can not import it again
Maybe I have overseen a known bug?

Finally I found the bug myself:

MOS: Impdp of objects of treatment fails with ORA-39083 and ORA-06502 [ID 780174.1]

https://support.Oracle.com/epmos/faces/DocContentDisplay?ID=780174.1

DBMS_CRYPTO grant missing after a full import, it should?
People,

We just did a full export of a production database using expdp.

Expdp directory $ = logfile measures = DATA_PUMP_DIR Full.log dumpfile = Full.dmp = is full = Y

Then, we did an import on another system using impdp.

Impdp directory $ = DATA_PUMP_DIR dumpfile = Full.dmp

The two DBs are 11 GR 2. 11.2.0.1 on the source system, target 11.2.0.3 on the system.

While testing one of our applications, we noticed that a couple of functions don't compile for one of our applications. These functions referenced DBMS_CRYPTO.

Other tests revealed that our main user of the application has no grant execute privs on DBMS_CRYPTO. After granting running on DBMS_CRYPTO to the user of the application, everything worked fine.

All other grants (and there are many of them) met very well (as far as we can tell so far).

Is there a reason why a grant on DBMS_CRYPTO would get "failed" during an import?

Thank you

Rich
For importing schema level, there might be some missing privileges, check:

Missing object level grants after that Data Pump import level schema [ID 795784.1]

But your case, import complete. Can you produce sqlfile with only grants and verify that this privilege is in the dump file:

Impdp full = y dumpfile = Full.dmp INCLUDE = GRANT directory = DATA_PUMP_DIR

Data pump - export without data

To export the database without data in old tool exp was the parameter ROWS defined as N. How to import the schema of database without data using data pump technology?

You can see by checking using dump export on your command line like this

C:\Documents and Settings\nupneja>expdp -help

Export: Release 10.2.0.1.0 - Production on Friday, 09 April, 2010 18:06:09

Copyright (c) 2003, 2005, Oracle.  All rights reserved.

The Data Pump export utility provides a mechanism for transferring data objects
between Oracle databases. The utility is invoked with the following command:

   Example: expdp scott/tiger DIRECTORY=dmpdir DUMPFILE=scott.dmp

You can control how Export runs by entering the 'expdp' command followed
by various parameters. To specify parameters, you use keywords:

   Format:  expdp KEYWORD=value or KEYWORD=(value1,value2,...,valueN)
   Example: expdp scott/tiger DUMPFILE=scott.dmp DIRECTORY=dmpdir SCHEMAS=scott
               or TABLES=(T1:P1,T1:P2), if T1 is partitioned table

USERID must be the first parameter on the command line.

Keyword               Description (Default)
------------------------------------------------------------------------------
ATTACH                Attach to existing job, e.g. ATTACH [=job name].
COMPRESSION           Reduce size of dumpfile contents where valid
                      keyword values are: (METADATA_ONLY) and NONE.
*CONTENT*               Specifies data to unload where the valid keywords are:
                      (ALL), DATA_ONLY, and METADATA_ONLY.
DIRECTORY             Directory object to be used for dumpfiles and logfiles.
DUMPFILE              List of destination dump files (expdat.dmp),
                      e.g. DUMPFILE=scott1.dmp, scott2.dmp, dmpdir:scott3.dmp.
ENCRYPTION_PASSWORD   Password key for creating encrypted column data.
ESTIMATE              Calculate job estimates where the valid keywords are:
                      (BLOCKS) and STATISTICS.
ESTIMATE_ONLY         Calculate job estimates without performing the export.
EXCLUDE               Exclude specific object types, e.g. EXCLUDE=TABLE:EMP.
FILESIZE              Specify the size of each dumpfile in units of bytes.
FLASHBACK_SCN         SCN used to set session snapshot back to.
FLASHBACK_TIME        Time used to get the SCN closest to the specified time.
FULL                  Export entire database (N).
HELP                  Display Help messages (N).
INCLUDE               Include specific object types, e.g. INCLUDE=TABLE_DATA.
JOB_NAME              Name of export job to create.
LOGFILE               Log file name (export.log).
NETWORK_LINK          Name of remote database link to the source system.
NOLOGFILE             Do not write logfile (N).
PARALLEL              Change the number of active workers for current job.
PARFILE               Specify parameter file.
QUERY                 Predicate clause used to export a subset of a table.
SAMPLE                Percentage of data to be exported;
SCHEMAS               List of schemas to export (login schema).
STATUS                Frequency (secs) job status is to be monitored where
                      the default (0) will show new status when available.
TABLES                Identifies a list of tables to export - one schema only.
TABLESPACES           Identifies a list of tablespaces to export.
TRANSPORT_FULL_CHECK  Verify storage segments of all tables (N).
TRANSPORT_TABLESPACES List of tablespaces from which metadata will be unloaded.
VERSION               Version of objects to export where valid keywords are:
                      (COMPATIBLE), LATEST, or any valid database version.

The following commands are valid while in interactive mode.
Note: abbreviations are allowed

Command               Description
------------------------------------------------------------------------------
ADD_FILE              Add dumpfile to dumpfile set.
CONTINUE_CLIENT       Return to logging mode. Job will be re-started if idle.
EXIT_CLIENT           Quit client session and leave job running.
FILESIZE              Default filesize (bytes) for subsequent ADD_FILE commands.
HELP                  Summarize interactive commands.
KILL_JOB              Detach and delete job.
PARALLEL              Change the number of active workers for current job.
                      PARALLEL=.
START_JOB             Start/resume current job.
STATUS                Frequency (secs) job status is to be monitored where
                      the default (0) will show new status when available.
                      STATUS[=interval]
STOP_JOB              Orderly shutdown of job execution and exits the client.
                      STOP_JOB=IMMEDIATE performs an immediate shutdown of the
                      Data Pump job.

C:\Documents and Settings\nupneja>

Content to the "metadata_only" parameter will export only the structure of the schema to skip the lines.

Problem of migration of data of characters using a whole export and import

Hi there;
I have a database in my local computer that does not support Turkish characters. My NLS_CHARACTERSET is WE8ISO8859P1, it should be changed to WE8ISO8859P9, because it supports the full Turkish characters. I would like to migrate character data using a full export and import and my strategy is the following:
1. create a full export to a network location,
2 create a new database in the local computer than NLS_CHARACTERSET is WE8ISO8859P9 (I wish NLS_TERRITORY NLS_LANGUAGE change by the way)
3 and to implement a full import of database created.
I've implemented the first step, but I could not implement the second step. I created the second step using Toad editor by clicking Create-> new database, but I can't connect to the new database. I need to connect the new database in order to perform the full import. How can I do this?
Thanks in advance.
Technical details
NLS_LANGUAGE... AMERICAN
NLS_TERRITORY... AMERICA
NLS_CURRENCY... $
NLS_ISO_CURRENCY... AMERICA
NLS_NUMERIC_CHARACTERS.,.
NLS_CHARACTERSET... WE8ISO8859P1
NLS_CALENDAR... GREGORIAN
NLS_DATE_FORMAT... DD-MON-RR
NLS_DATE_LANGUAGE... AMERICAN
NLS_SORT............................... BINARY
NLS_TIME_FORMAT... HH.MI. SSXFF AM
NLS_TIMESTAMP_FORMAT... DD-MON-RR HH.MI. SSXFF AM
NLS_TIME_TZ_FORMAT... HH.MI. SSXFF AM TZR
NLS_TIMESTAMP_TZ_FORMAT... DD-MON-RR HH.MI. SSXFF AM TZR
NLS_DUAL_CURRENCY... $
NLS_COMP............................... BINARY
NLS_LENGTH_SEMANTICS... BYTE
NLS_NCHAR_CONV_EXCP... FAKE
NLS_NCHAR_CHARACTERSET... AL16UTF16
NLS_RDBMS_VERSION... 10.2.0.1.0
:

First of all, if your applications run on Windows, do not use WE8ISO8859P9. Use TR8MSWIN1254.

Second, if you create a new database, the database is not necessarily immediately accessible to the outside world. I don't know of a toad, and I have no idea if it performs all necessary steps required for the new base data is visible. For example, in the toad itself, I guess you need to create a new connection that refers to the new SID of the newly created database and use this new link to connect. However, connections without a connection string using the parameter ORACLE_SID in the registry to indicate applications access which instance (database) to use. To change the database accessed with a connection string empty, you must modify the registry (unless the toad has an option to do it for you). If you want to connect without changing the registry, you need a connection string. This requires the implementation of Oracle Listener to serve the new database (unless the default configuration is used and the database registers itself with the default listener). You must also edit the tnsnames.ora file to create an alias for the new database. Net or Net Configuration Manager Wizard can help you with this.

I wonder if the database Configuration Wizard would not be a better tool to create a new Oracle databases.

Thank you

Sergiusz

FULL IMPORT
Hello
10g R2 on Win 2003, I want to import a complete database from a dump file full expdp. I searched here

http://download.Oracle.com/docs/CD/B19306_01/server.102/b14215/dp_import.htm#sthref421

I found these examples:
```
Performing a Data-Only Table-Mode Import
Example 3-1 shows how to perform a data-only table-mode import of the table named employees. It uses the dump file created in Example 2-1.

Example 3-1 Performing a Data-Only Table-Mode Import

impdp hr/hr TABLES=employees CONTENT=DATA_ONLY DUMPFILE=dpump_dir1:table.dmpNOLOGFILE=y



Example 3-2 Performing a Schema-Mode Import

impdp hr/hr SCHEMAS=hr DIRECTORY=dpump_dir1 DUMPFILE=expschema.dmp EXCLUDE=CONSTRAINT,REF_CONSTRAINT,INDEX TABLE_EXISTS_ACTION=REPLACE



Example 3-3 Network-Mode Import of Schemas

impdp hr/hr TABLES=employees REMAP_SCHEMA=hr:scott DIRECTORY=dpump_dir1
NETWORK_LINK=dblink
```
Not a full import.
Can you suggest a good syntax?
Thank you.

My original export command line was:
expdp DIRECTORY system/%PWD%@%DB% = dpump_dir1 = expdp_ful_ % DB % FULL = Y Logfile=expdp_full_%DB%_XXX.log _XXX DUMPFILE
Hello

Depends on the link and the document which we could refer us
http://www.Oracle.com/technology/OBE/obe10gdb/storage/DataPump/DataPump.htm

consists of expdp - FULL, try to do for impdp - is not so tuff to do

HTH

-Pavan Kumar N
ORACLE 9i / 10g - OCP
http://www.oracleinternals.blogspot.com

Published by: pounet on April 20, 2010 14:56

Data pump import
I cannot using the data pump import tool. I work with Oracle 10.2.4.0 on Windows Server 2008. I am trying to import a large amount of data (several patterns, thousands of paintings, hundreds of GB of data) of the same version of Oracle on Linux. Since there is so much data and will be if long to import, I try to make sure that I can make it work for a table or a diagram before I try. So I will try to import the TEST_USER. Table 1 table using the following command:

Dumpfile = logfile = big_file_import.log big_file.dmp Impdp.exe tables = test_user.table1 remap_datafile=\'/oradata1/data1.dbf\':\'D:\oracle\product\10.2.0\oradata\orcl\data1.dbf\'

I provide sys as sysdba to connect when he asks (not sure how you get this info in the original order). However, I get the following error:

the "TEST_USER" user does not exist

My understanding is that the data pump utility would create all the necessary patterns for me. Is it not the case? The target database is a new facility for the source schemas do not exist here.

Even if I create the schema of test_user by hand, then I get an error message indicating that the tablespace does not exist:

ORA-00959: tablespace "TS_1" does not exist

Then even to do it, I don't want to have to do first, does not work. Then he gives me something about how the user has no privileges on tablespace.

The data pump utility is not supposed to do that sort of thing automatic? What I really need to create all schemas and storage by hand? That will take a long time. I'm doing something wrong here?

Thank you
Dave
tables = test_user.table1

The "TABLES" mode does NOT create database accounts.

The FULL mode creates space storage and database accounts before importing the data.

PATTERNS mode creates the database accounts before importing data - but expect Tablespaces to exist before so that tables and indexes can be created in the correct storage spaces.

Hemant K Collette
http://hemantoracledba.blogspot.com

Update of data by Data Pump Import
Hi all!

I want to update the data in my database using Full Import Data Pump to a different database. But I do not know which option I should use when executing import for the second time? Or I can run full import without encompassing any option again?

Thank you

Tien Lai
What if all you want to do is update of data and if the tables already exist, you can use this:

content of user/password = data_only =(truncate or append) table_exists_action Impdp...

If you use Add, then add new data to the existing data. If you use truncate then existing data will be deleted and the data in the dumpfile will be imported.

There will be problems if you have a referential constraint. Say that table 1 references given in table 2, if datapump loads data into Database2 first, and then it truncates the data again. This truncation may fail because there is a referential constraint on it. If you have a ref, then you must disable them before you run impdp and then allow them once impdp is completed.

If all you want after the first import only the data, you can add the

content = data_only

your order expdp. He would complete much faster.

Do not forget that your statistics on the tables and the indexes will not be reloaded if you use table_exists_action = truncate or replace existing statistics so would probably obsolete.

If you want to replace the table and the data, then the command would be:

Impdp username/password table_exists_action = replace...

This will remove the table and re-create it, and then load the data, then create all dependent objects for tables.

I hope this helps.

Dean

Data pump full export/Full Import - lack of subsidies sys

Similar Questions

Maybe you are looking for