Full database refresh

Hello Gurus,
I am need to take make full database refresh from one database to other, Can someone let me know step how to do it?
select * from V$VERSIONBANNER
Oracle Database 10g Enterprise Edition Release 10.2.0.5.0 - 64bi
PL/SQL Release 10.2.0.5.0 - Production
CORE     10.2.0.5.0     Production
TNS for HPUX: Version 10.2.0.5.0 - Production
NLSRTL Version 10.2.0.5.0 - Production

CKPT wrote:
jgarry wrote:
I'm with Ed and Brendan on this. 3 main reasons:
1. Legacy has some special requirements.
2. Definitely want different schema names, this has saved my bacon sooo many times. Even so, people still get it wrong (including me, and I'm totally paranoid about it to begin with).
3. There are many more copies of production than actual production, for various reasons (test, several dev, special projects, future app versions...) . We would rather have one db with many schemata than many db's, right?
Now if we could just rename user...Agreed some extent, I can say to refresh entire database the preferred method is RMAN restore, where it can manage very easily
how?
1) To import again we need to create a new database
2) Need to create all the tablespaces with same names or we can use REMAP option
3) need to monitor entire import process,
4) need to take care of other things like , temp utilization and all.
5) need to perform export, Need to copy those dumpfiles, We should have enough space on mount points of both source & destinations. ;-)
I would just caution there that you shouldn't think that because you are taking rman backups you have no need to also regularly export the db. A good backup policy includes both physical backup (rman) and logical backup of the data (export).
If you talk with couple of schemas the preferred method is EXPDP/IMPDP, totally agreed.
If in case of database size is huge, then better to go with RMAN to refresh database. Either DUPLICATE or manual way restore.
as ED said, still we could have chance to test RMAN backups too. Multiple advantages.
Let me know if I'm wrong. :)

Similar Messages

SYS, SYSTEM and SYSAUX when full database refresh.

I took full export from database using below command
expdp "'/ as sysdba'" full=Y directory=DPUMP_DIR dumpfile=expdp_11032011.dmp logfile=expdp_11032011.log Now, I need to import this file to an other database.
When do schema refresh we usually drop all the object in that schema and start refresh, but when doing fullback up, do we need to drop all user?
what about sys, system and sysaux user?

user3636719 wrote:
So, the tables in the SYS and SYSTEM will remain same when we refresh?
Structure will not be modified but contents will be automatically modified when DLL is executed when importing.
And do we have to drop other user before we import?Applications schemas that you have created should be dropped. In general don't modify any schema that is directly managed by Oracle such as SYS or SYSTEM or any schema used by some database option like Oracle Text, Oracle Spatial, etc.

Planning Database Refresh

We have a Planning application which is used as follows: the outline is administered through planning but everything else (such as entering data etc) is done using excel. We end up with a lot of fragmentation and wanted to setup a script to fragment the db every so often. Question is since this is a planning app will a MaxL script running on essbase ("alter database force restructure") do the trick or must the restructure be done using refresh through Planning -> Manage Databases -> Refresh database ?
Thanks.

If you want to defrag then yes you can run a maxl full restructure and it doesn't have to be a refresh from planning.
Cheers
John
http://john-goodwin.blogspot.com/

How to determine who performed the last full database dump before cumulative dump

Hello,
ASE 15.7 SP100 allows cumulative backups, and if cumulative dump is tried before a full dump, ASE shows this error:
You cannot execute an incremental dump before a full database dump.
From my experiments, it seems that it does not matter how the full dump is performed (by native isql, or by a 3rd party API). As long as a full dump is done on a database, ASE seems to be keeping track of all the changed pages since the last full dump. So this means that you can perform a full dump using a 3rd party API, and then on isql, if you run a cumulative dump command, the cumulative dump succeeds, which is based on the last full dump by another library!
So, my question is: is there any way to programmatically determine how (by native isql or 3rd party) the last full backup was performed? I believe $SYBASE_HOME/ASE-15_0/dumphist contains this info, but it requires 'enable dump history' to be set first, and I am looking for a solution which does not involve checking a disk file.
Thanks,
Ali

Dear Mr Razib,
I have not explored the feature but ASE autiding might provide you the possibility to access information on past database dumps via SQL.
Apart from that - I am not aware of an SQL interface to the dumphist file (would be nice to have, I agree)
Enabling dump history is definitley highly recommended (in my opinion) .
There is yet another feature which might help you to prevent an DBA from dumping databases and transactions to various locations.
When you create a DUMP CONFIGURATION and additionally set parameter
enforce dump configuration
ASE will prevent normal (free style) DUMP commands but enforce the use of an existing dump configuration. The mechanism is not fool proof (nothing prevents from creating yet another dump configuration on the fly) - but at least something.
With kind regards
Tilman Model-Bosch

Database Refresh Failed

Hi All,
I am working on a database refresh and it failed with the following errors
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of Duplicate Db command at 04/15/2011 16:27:41
RMAN-03015: error occurred in stored script Memory Script
ORA-00283: recovery session canceled due to errors
RMAN-11003: failure during parse/execution of SQL statement: alter database recover logfile '/srv/database/arch2/1_65508_689972797.dbf'
ORA-00283: recovery session canceled due to errors
ORA-00368: checksum error in redo log block
ORA-00353: log corruption near block 256 change 43879018791 time 04/12/2011 04:30:54
ORA-00334: archived log: '/srv/database/arch2/1_65508_689972797.dbf'
Do you have any idea of how to solve this error.
Please help.

Hi;
What is your OS? If its solaris than please see:
Duplicate Fails with Corruption Errors on Solaris QFS Filesystem [ID 764113.1]
Regard
Helios

Problem with full database backup.

This is what I got after execute backup full database statement
"RMAN-03009: failure of backup command on ORA_DISK_1 channel at 03/03/2009 14:15:15
ORA-19502: write error on file "/u01/app/oracle/backup/ORCL/ora_df680537660_s2_s1", blockno 25985 (blocksize=8192)
ORA-27072: File I/O error
Linux Error: 2: No such file or directory
Additional information: 4
Additional information: 25985
Additional information: 483328"
I have quite the same problem with create tablespace, I can't create tablespace 512m, but I can create the same tablespace only 100m.
I think it must be somethink with storage???

Starting backup at 03-MAR-09
using channel ORA_DISK_1
input datafile fno=00015 name=/u01/app/oracle/oradata/o2_mf_system_48fprop3_.dbf
input datafile fno=00003 name=/u01/app/oracle/oradata/ORCL/datafile/o1_mf_sysaux_48fpropg_.dbf
input datafile fno=00014 name=/u01/app/oracle/oradata/o2_mf_sysaux_48fpropg_.dbf
input datafile fno=00005 name=/u01/app/oracle/oradata/ORCL/datafile/o1_mf_example_48fpw04c_.dbf
input datafile fno=00017 name=/u01/app/oracle/oradata/ORCL/datafile/rcvcat01.dbf
input datafile fno=00002 name=/u01/app/oracle/oradata/ORCL/datafile/o1_mf_undotbs1_48fprovo_.dbf
input datafile fno=00016 name=/u01/app/oracle/oradata/inventory03.dbf
input datafile fno=00011 name=/u01/app/oracle/oradata/ORCL/datafile/inventory01.dbf
input datafile fno=00012 name=/u01/app/oracle/oradata/ORCL/datafile/inventory02.dbf
input datafile fno=00006 name=/u01/app/oracle/oradata/ORCL/datafile/ts01.dbf
input datafile fno=00008 name=/u01/app/oracle/oradata/ORCL/datafile/ts02.dbf
input datafile fno=00001 name=/u01/app/oracle/oradata/ORCL/datafile/o1_mf_system_48fprop3_.dbf
channel ORA_DISK_1: specifying datafile(s) in backupset
channel ORA_DISK_1: starting full datafile backupset
input datafile fno=00009 name=/u01/app/oracle/oradata/ORCL/datafile/undo01.dbf
channel ORA_DISK_1: starting piece 1 at 03-MAR-09
input datafile fno=00013 name=/u01/app/oracle/oradata/ORCL/datafile/val01.dbf
input datafile fno=00007 name=/u01/app/oracle/oradata/ORCL/datafile/test_reorg0
input datafile fno=00004 name=/u01/app/oracle/oradata/ORCL/datafile/o1_mf_users_48fprowb_.dbf
input datafile fno=00010 name=/u01/app/oracle/oradata/ORCL/datafile/ts01b.dbf
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03009: failure of backup command on ORA_DISK_1 channel at 03/03/2009 14:15:15
ORA-19502: write error on file "/u01/app/oracle/backup/ORCL/ora_df680537660_s2_s1", blockno 25985 (blocksize=8192)
ORA-27072: File I/O error
Linux Error: 2: No such file or directory
Additional information: 4
Additional information: 483328
Additional information: 25985
Directory exist because I can backup single tablespace, into the same directory, I just can't backup whole database.
Edited by: val75 on Mar 3, 2009 1:57 PM

Getting error in full database export

hi,
I am exporting full database i am getting this error shown below:
operating system:windows 2003 server
oracle:oracle 10g
C:\Documents and Settings\Administrator.SRCSD>exp system/systemsms file=d:\21041
0.dmp log=d:\210410.log full=y
Export: Release 10.1.0.2.0 - Production on ╟ط╟╤╚┌╟┴ ╟╚╤وط 21 11:15:42 2010
Copyright (c) 1982, 2004, Oracle. All rights reserved.
Connected to: Oracle Database 10g Enterprise Edition Release 10.1.0.2.0 - Produc
tion
With the Partitioning, OLAP and Data Mining options
Export done in AR8MSWIN1256 character set and AL16UTF16 NCHAR character set
server uses AR8ISO8859P6 character set (possible charset conversion)
About to export the entire database ...
. exporting tablespace definitions
. exporting profiles
. exporting user definitions
. exporting roles
. exporting resource costs
. exporting rollback segment definitions
. exporting database links
. exporting sequence numbers
. exporting directory aliases
. exporting context namespaces
. exporting foreign function library names
. exporting PUBLIC type synonyms
. exporting private type synonyms
. exporting object type definitions
. exporting system procedural objects and actions
. exporting pre-schema procedural objects and actions
. exporting cluster definitions
EXP-00056: ORACLE error 4021 encountered
ORA-04021: timeout occurred while waiting to lock object
ORA-06512: at "SYS.DBMS_METADATA", line 1511
ORA-06512: at "SYS.DBMS_METADATA", line 1548
ORA-06512: at "SYS.DBMS_METADATA", line 1864
ORA-06512: at "SYS.DBMS_METADATA", line 3707
ORA-06512: at "SYS.DBMS_METADATA", line 3689
ORA-06512: at line 1
EXP-00056: ORACLE error 4021 encountered
ORA-04021: timeout occurred while waiting to lock object
ORA-06512: at "SYS.DBMS_METADATA", line 1511
ORA-06512: at "SYS.DBMS_METADATA", line 1548
ORA-06512: at "SYS.DBMS_METADATA", line 1864
ORA-06512: at "SYS.DBMS_METADATA", line 3707
ORA-06512: at "SYS.DBMS_METADATA", line 3689
ORA-06512: at line 1
EXP-00000: Export terminated unsuccessfully
C:\Documents and Settings\Administrator.SRCSD>
plz reply me appropriate solution.
thanks.

Possibly bug 3386590 (4021: TIMEOUT OCCURRED WHILE WAITING TO LOCK OBJECT), upgrade to 10gR2 or even better 11gR2.
Werner

Full database Export

Hi
We are having a database 10g running on solaris OS. We are getting a new server and I need to move the data. This is what I am planning to do.
Take full database export from original server. (This includes tablespaces, all schemas and data)
Import in new server, from SYS schema once Oracle is installed. so all the schemas and objects are imported.
Can you let me know this approach is right any precautions to be taken?
Thanks

user625850 wrote:
Hi
We are having a database 10g running on solaris OS. We are getting a new server and I need to move the data. This is what I am planning to do.
Take full database export from original server. (This includes tablespaces, all schemas and data)
Import in new server, from SYS schema once Oracle is installed. so all the schemas and objects are imported.
Can you let me know this approach is right any precautions to be taken?
ThanksRMAN DUPLICATE

Full database export hangs (Oracle9i rel2)

I recently migrated successfully from oracle8i rel 8.0. to oracle9i release 2,But now am not able to do a full database export.has anyone experienced this and whats the remedy?.
the text i get is listed below.
Microsoft Windows [Version 5.2.3790]
(C) Copyright 1985-2003 Microsoft Corp.
C:\Documents and Settings\Administrator>exp system/manager@ORCL file=C:\orclbk\p
oll.dmp full=y
Export: Release 9.2.0.1.0 - Production on Tue Aug 9 18:36:13 2005
Copyright (c) 1982, 2002, Oracle Corporation. All rights reserved.
Connected to: Oracle9i Enterprise Edition Release 9.2.0.1.0 - Production
With the Partitioning, OLAP and Oracle Data Mining options
JServer Release 9.2.0.1.0 - Production
Export done in WE8MSWIN1252 character set and AL16UTF16 NCHAR character set
About to export the entire database ...
. exporting tablespace definitions
. exporting profiles
. exporting user definitions
. exporting roles
. exporting resource costs
. exporting rollback segment definitions
. exporting database links
. exporting sequence numbers
. exporting directory aliases
. exporting context namespaces
. exporting foreign function library names
. exporting PUBLIC type synonyms
. exporting private type synonyms
. exporting object type definitions
EXP-00090: cannot pin type "OE"."CUSTOMER_TYP"
EXP-00056: ORACLE error 22303 encountered
OCI-22303: type "OE"."CUSTOMER_TYP" not found
EXP-00056: ORACLE error 24323 encountered
ORA-24323: value not allowed
EXP-00000: Export terminated unsuccessfully
C:\Documents and Settings\Administrator>

You have to run the export with the SYS user. This error may arise on any plattform ranging form 9.0.1 to 10.2.0.
C:\>exp "'sys/oracle as sysdba'" full=y

Full database backup and restore

I have a doubt on the syntax for a full database backup and restore. For a single schema, the syntax for backup & restore is :-
exp JISPREPCORBILLINGPRD501/JISPREPCORBILLINGPRD501 owner=JISPREPCORBILLINGPRD501 STATISTICS=none
log=JISPREPCORBILLINGPRD501_exp.log grants=y constraints=Y rows=y compress=N
file=JISPREPCORBILLINGPRD501
imp <userid/password> file=<export dump file location> fromuser=<export user name> touser=<import user name>
grants=y constraints=Y rows=y log=<import log file location>
I hope, my question is clear.
Please, help in solving the doubt.
regards

hi,
thanks, for your answer. I took a export of one schema of the database. But, when I tried to import the schema to the destination database, it showed
imported with errors with the existence of functions showing. The commands used by me for export and import are as follows:-
exp JISPREPCORBILLINGPRD501/JISPREPCORBILLINGPRD501 owner=JISPREPCORBILLINGPRD501 STATISTICS=none log=JISPREPCORBILLINGPRD501_exp.log grants=y constraints=Y rows=y compress=N file=JISPREPCORBILLINGPRD501
imp JISPREPCORBILLINGPRD501/JISPREPCORBILLINGPRD501 file=JISPREPCORBILLINGPRD501 fromuser=JISPREPCORBILLINGPRD501 touser=JISPREPCORBILLINGPRD501 grants=y constraints=Y rows=y log=JISPREPCORBILLINGPRD501_imp.log
Do, we need to drop the existing schema before importing or somethinig else. Please, help.
regards

Full Database Backup

Hi people,
I´ve the next doubt about the backups of MS SQL Server.
If I make a full database backup, the transaction log (SIDLOG1) are backed? Or I´ve to do the backup of transactional log separated?
In the note Note 44449 - Backup strategies with the SQL server, says this:
"If you run a complete database backup, the contents of the transaction log are saved (database dump), but the log is not shortened. The transaction log is only shortened when you save the log (transaction dump)."

A FULL SQL backup includes all of the changes that are contained in the LOG file, so that the backup is recoverable to any point in time from the beginning to the end of the time it takes to backup the database. However, it does NOT truncate the log file because you may still need a log backup in order to be recoverable to a point in time AFTER the FULL backup mentioned earlier, or if you have to utilize a different FULL backup in the event the other backup is corrupted, lost, etc.
For example:
Full backup A taken 11/8/2010, begin 8:00 AM, completed 9:00 AM.
Transaction Log backup 1 taken 11/8/2010, 11:00 AM
Transaction Log backup 2 taken 11/8/2010, 3:00 PM
Transaction Log backup 3 taken 11/8/2010, 7:00 PM
Full backup B taken 11/9/2010, begin 8:00 AM, completed 9:00 AM.
Transaction Log backup 4 taken 11/9/2010, 11:00 AM
Transaction Log backup 5 taken 11/9/2010, 3:00 PM
Transaction Log backup 6 taken 11/9/2010, 7:00 PM
If you need to recover to point in time 11/9/2010 at 8:30 AM, all you need is Full backup B.
If you need to recover to point in time 11/9/2010 at 5:00 PM, you need Full backup B, and Transaction Logs 4, 5, and 6.
If you need to recover to point in time 11/9/2010 at 5:00 PM, and Full backup B is corrupted, you need Full backup A, and Transaction Logs 1, 2, 3, 4, 5, and 6.
If Full backup B had truncated the log, then you would not be recoverable to any point in time after 7:00 PM on 11/8/2010.

Full Database Exp & Imp

Hi,
I am trying to Exp & Imp a full database. I am working on Oracle 9i & 10g on Solaris 9. I am not using Data Pump. Can anyone please help me with the following:
1. I am performing the full export using SYSTEM user.
1.a Does a Full export include (or backups up) the DATA DICTIONARY of the database?
1.b Does a Full export include the backup of SYS and SYSTEM objects?
I am using the following command to export
exp system/system@testdb file=$HOME/testdbfullexp.dmp full=y statistics=none
I have tried importing the FULL export to another database and i did see that SYS and SYSTEM objects were also being imported ( got some errors regarding constraints and inconsistencies).
I would like to ask like what are the ideal steps to follow to copy a database from DB1 to DB2 using EXP and IMP
Any information will be of a great help
Thanks,
Harris.

1 a) No, as the data dictionary will be automagicall recreated by implicit SQL.
This means any non dictionary objects under SYS will be lost
1 b) as above. SYSTEM however is a normal user.
any %SYS user will NOT be exported (CTXSYS, MDSYS, etc)
On import of SYSTEM there will be always errors, as SYSTEM is non-empty after initial database creation.
Sybrand Bakker
Senior Oracle DBA

Full Database Export/Import

I was attempting to export a full database from one server (DB files on the N: drive) and import it into a freshly created new database with the same instance name on a new server (DB files on the D: drive).
I was told to:
1) Export the full database as sys using full=y
2) Pre-create all of the tablespaces on the target database that do not exist on the target database
3) Import the full database as sys using full=y
=========================================================
Here are the steps I had to follow:
1) Export the full database as sys using full=y
2) Pre-create all of the tablespaces on the target database
3) Import the full database as sys using full=y - Result: over 1900 invalid objects and thousands of errors
4) Run Utlrp.sql - Result: 8 to 10 invalid objects
5) Manually attempt to compile or rebuild objects. Several grants were required to get most of these to work. - Result: After quite a bit of hand crafting, two objects are still invalid.
6) After spending almost two hours in a Collaborative Conference with an analyst who is working very hard to sold this, there are still two objects that are invalid.
Note: From my perspective this is not a straight forward process
=========================================================
Questions:
1) Has anyone successfully moved a database as described without all of these annoying steps?
2) Is there a document that details the full database export/import?
Thanks, RJZ

Hello RJZ,
There is not sufficient information to reply accurately to your queries,
1. Could you post the error message that you're getting when you compile these two programs? Do they compile okay on the old server?
2. What was the reason you choose exp and imp, to move your db to the new server and different disk? Were you migrating to a different version, or was it because of the db-reorg? It would have been possible to simple copy the db-files to the new location, and then rename the datafiles in mount-state. It would be more simpler I believe unless as stated above
Did you check the import logs? While importing were there any errors? Actually it should have been pretty straight forward (no reason why you need documentation for exp / imp). Grants should have automatically come, unless you have select grants=n option
I think because of the changes you have done for step-5, you might have changed some stuff somewhere. Please post the error message, and tell us if you have migrated the db to a higher version
Regards
Sudhanshu

Full database import(impdp) error

HI ppl,
Plz help..
My full database import is failing due to
ORA-39126: Worker unexpected fatal error in KUPW$WORKER.LOAD_METADATA [TABLE_DATA:"SYS"."SYS_IMPORT_FULL_04"]
SELECT process_order, flags, xml_clob, NVL(dump_fileid, :1), NVL(dump_position, :2), dump_length, dump_allocation, grantor, object_row, object_schema, object_long_name, processing_status, processing_state, base_object_type, base_object_schema, base_object_name, property, size_estimate, in_progress FROM "SYS"."SYS_IMPORT_FULL_04" WHERE process_order between :3 AND :4 AND processing_state <> :5 AND duplicate = 0 ORDER BY process_order
ORA-25153: Temporary Tablespace is Empty
ORA-06512: at "SYS.DBMS_SYS_ERROR", line 105
ORA-06512: at "SYS.KUPW$WORKER", line 6272
----- PL/SQL Call Stack -----
object line object
handle number name
c000000267348288 14916 package body SYS.KUPW$WORKER
c000000267348288 6293 package body SYS.KUPW$WORKER
c000000267348288 3511 package body SYS.KUPW$WORKER
c000000267348288 6882 package body SYS.KUPW$WORKER
c000000267348288 1259 package body SYS.KUPW$WORKER
c00000026fb2de68 2 anonymous block
Job "SYS"."SYS_IMPORT_FULL_04" stopped due to fatal error at 14:56:10
regards

Hi..
ya temporary tablespace is present,and also contains 2gb freespace,with 2 datafiles.Are you sure its a datafile.It must be a tempfile. :)
Secondly, have you checked the default temporary tablespace of the database.Is it the one that you have mentioned.
SELECT PROPERTY_NAME,PROPERTY_VALUE FROM DATABASE_PROPERTIES where PROPERTY_NAME='DEFAULT_TEMP_TABLESPACE';
Anand

Full database exp/imp between RAC and single database

Hi Experts,
we have a RAC database oracle 10GR2 with 4 node in linux. i try to duplicate rac database into single instance window database.
there are same version both database. during importing, I need to create 4 undo tablespace to keep imp processing.
How to keep one undo tablespace in single instance database?
any experience of exp/imp RAC database into single instance database to share with me?
Thanks
Jim
Edited by: user589812 on Nov 13, 2009 10:35 AM

JIm,
I also want to know can we add the exclude=tablespace on the impdp command for full database exp/imp?You can't use exclude=tablespace on exp/imp. It is for datapump expdp/impdp only.
I am very insteresting in your recommadition.
But for a full database impdp, how to exclude a table during full database imp? May I have a example for this case?
I used a expdp for full database exp. but I got a exp error in expdp log as ORA-31679: Table data object "SALE"."TOAD_PLAN_TABLE" has long columns, and longs can not >be loaded/unloaded using a network linkHaving long columns in a table means that it can't be exported/imported over a network link. To exclude this, you can use the exclude expression:
expdp user/password exclude=TABLE:"= 'SALES'" ...
This will exclude all tables named sales. If you have that table in schema scott and then in schema blake, it will exclude both of them. The error that you are getting is not a fatal error, but that table will not be exported/imported.
the final message as
Master table "SYSTEM"."SYS_EXPORT_FULL_01" successfully loaded/unloaded
Dump file set for SYSTEM.SYS_EXPORT_FULL_01 is:
F:\ORACLEBACKUP\SALEFULL091113.DMP
Job "SYSTEM"."SYS_EXPORT_FULL_01" completed with 1 error(s) at 16:50:26Yes, the fact that it did not export one table does not make the job fail, it will continue on exporting all other objects.
. I drop database that gerenated a expdp dump file.
and recreate blank database and then impdp again.
But I got lots of error as
ORA-39151: Table "SYSMAN"."MGMT_ARU_OUI_COMPONENTS" exists. All dependent metadata and data will be skipped due to table_exists_action of skip
ORA-39151: Table "SYSMAN"."MGMT_BUG_ADVISORY" exists. All dependent metadata and data will be skipped due to table_exists_action of skip
......ORA-31684: Object type TYPE_BODY:"SYSMAN"."MGMT_THRESHOLD" already exists
ORA-39111: Dependent object type TRIGGER:"SYSMAN"."SEV_ANNOTATION_INSERT_TR" skipped, base object type VIEW:"SYSMAN"."MGMT_SEVERITY_ANNOTATION" >already exists
and last line as
Job "SYSTEM"."SYS_IMPORT_FULL_01" completed with 2581 error(s) at 11:54:57Yes, even though you think you have an empty database, if you have installed any apps or anything, it may create tables that could exist in your dumpfile. If you know that you want the tables from the dumpfile and not the existing ones in the database, then you can use this on the impdp command:
impdp user/password table_exists_action=replace ...
If a table that is being imported exists, DataPump will detect this, drop the table, then create the table. Then all of the dependent objects will be created. If you don't then the table and all of it's dependent objects will be skipped, (which is the default).
There are 4 options with table_exists_action
replace - I described above
skip - default, means skip the table and dependent objects like indexes, index statistics, table statistics, etc
append - keep the existing table and append the data to it, but skip dependent objects
truncate - truncate the existing table and add the data from the dumpfile, but skip dependent objects.
Hope this helps.
Dean

Full database refresh

Similar Messages

Maybe you are looking for