Importing full database

Hello,
I am transferring a full database from a unixware711 based server running oracle 8.0.4 to a windows xp with sp2 based machine using export / import.
I have exported the db on the unix server , since there is an issue on unix servers that dont allow export dmp files to exceed 2gb limit the export file has been generated as three split files each under 2 gb. The total export file size comes to around 5gb.
now how do I import from these split files on the windows machine since these export split files are unix based will windows be able to concatenate these files if yes please advise how
if not then please suggest how this can be accomplished.
thanks.

This isn't really the appropriate forum for this. You should try the Database - General forum.
You can transfer the files to windows using FTP binary mode and then concatenate them using copy, (assuming the files were created using split)
copy part1+part2+part3 wholefile.dmp

Similar Messages

Importing Full database wid Crrent production dumpfile on test Database

hi,
I have production database 9.2.0.4 on widows server.
I have Current Dumpfile of Production database.
I Have test Database on another server which is too 9.2.0.4 on windows server.
I need to Import full database on test Database with Current Production Dump file.
COuld u reply the complete procedure
I have tested on test Server But i am not getting all tables some tables are missing.
Thankx
Edited by: oradb on Nov 29, 2010 1:54 AM

which method are you using to take the dump ?
if you are using the imp/exp method ,
then simple create a parameter file with the following parameters :
indexes=y
rows=y
grants=y
buffer=500000
ignore=y
statistics=none
full=y
log=logfile.log
and then run the following command :
imp system/**** <parfilename>
Always refer to the logfile to see for successfull completion of the import.
hope this helps
- KKukreja-
that should help
Edited by: rattlesnake on Nov 29, 2010 3:15 AM

Import full database to different version (from 11.2 to 10.2)

I have source database which is
SQL>select * from v$version;
BANNER
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 - ProductionI have target database which is
SQL>select * from v$version;
BANNER
Oracle Database 11g Enterprise Edition Release 11.2.0.2.0 - 64bit Production
PL/SQL Release 11.2.0.2.0 - Production
CORE    11.2.0.2.0      Production
TNS for IBM/AIX RISC System/6000: Version 11.2.0.2.0 - Production
NLSRTL Version 11.2.0.2.0 - ProductionI took export of the source database using below command
expdp "'/ as sysdba'" full=Y dumpfile=DATA_PUMP1:full%U.dmp, DATA_PUMP2:full%U.dmp logfile=DATA_PUMP1:full.log FILESIZE=10G PARALLEL=4I am expecting my import command to be
impdp "'/ as sysdba'" full=Y dumpfile=DATA_PUMP1:full%U.dmp, DATA_PUMP2:full%U.dmp logfile=DATA_PUMP1:impdp_full.log FILESIZE=10GMy question is
1.     What change do I need to make while importing since database version in source and target are different?
2.     Do I need to change any thing in my import command?

1. What change do I need to make while importing since database version in source and target are different?You don't have to do anything. You are exporting metadata that will be recreated in your new database and new version. Just run the import command.
2. Do I need to change any thing in my import command?I don't think you need to change anything. You an add parallel if you want, but the import parallel does not have to match the export parallel, so keeping it as you have it will be fine.
Dean

Importing full database in 8i

I have a full database export of a database.
I will have to import that into an oracle 8i database.
May I know what are the considerations to be made/ precautions to be taken care of in precise?
Shd I create all the tablespaces and users forehand? Or the full=y statement during import creates it all ?

imp will attempt to run CREATE TABLESPACE statement with the DATAFILE names and sizes being the same as in the source database.
If your filesystem structure / filesystem sizes are different at the target you should manually precreate each Tablespace.
Also, manually precreating Tablespaces gives you the option to change DEFAULT STORAGE parameters.
Hemant K Chitale

Export/Import full database dump fails to recreate the workspaces

Hi,
We are studying the possibility of using Oracle Workspace to maintain multiple versions of our business data. I recently did some tests with the import/export of a dump that contains multiple workspaces. I'm not able to import the dump successfully because it doesn't recreate the workspaces on the target database instance, which is an empty Oracle database freshly created. Before to launch the import with the Oracle Data Pump utility, I have the "LIVE" workspace that exists in the WMSYS.WM$WORKSPACES_TABLE table. After the import is done, there is nothing in that table...
The versions of the Oracle database and Oracle Workspace Manager are the same on source and target database:
Database version (from the V$VERSION view):
Oracle Database 10g Enterprise Edition Release 10.2.0.4.0 - 64bi
PL/SQL Release 10.2.0.4.0 - Production
CORE 10.2.0.4.0 Production
TNS for 64-bit Windows: Version 10.2.0.4.0 - Production
NLSRTL Version 10.2.0.4.0 - Production
Workspace Manager version (from the WM_INSTALLATION view):
OWM_VERSION: 10.2.0.4.3
In order to recreate the tablespaces successfully during the full import of the dump, the directory structure for the tablespaces is the same on the target database's computer. I used the instructions given in this document, section "1.6 Import and Export Considerations" at page 1-19:
http://www.wyswert.com/documentation/oracle/database/11.2/appdev.112/e11826.pdf
Considering that the release of Oracle database used is version 10.2.0.4, I use the following command to import the dump since it doesn't contain the WMSYS schema:
impdp system/<password>@<database> DIRECTORY=data_pump_dir DUMPFILE=expfull.dmp FULL=y TABLE_EXISTS_ACTION=append LOGFILE=impfull.log
The only hints I have in the import log file are the following block of lines:
1st one:
==============================
Traitement du type d'objet DATABASE_EXPORT/SYSTEM_PROCOBJACT/PRE_SYSTEM_ACTIONS/PROCACT_SYSTEM
ORA-39083: Echec de la création du type d'objet PROCACT_SYSTEM avec erreur :
ORA-01843: ce n'est pas un mois valide
SQL en échec :
BEGIN
if (system.wm$_check_install) then
return ;
end if ;
begin execute immediate 'insert into wmsys.wm$workspaces_table
values(''LIVE'',
''194'',
''-1'',
2nd one at the end of the import process:
==============================
Traitement du type d'objet DATABASE_EXPORT/SCHEMA/POST_SCHEMA/PROCACT_SCHEMA
ORA-39083: Echec de la création du type d'objet PROCACT_SCHEMA avec erreur :
ORA-20000: Workspace Manager Not Properly Installed
SQL en échec :
BEGIN
declare
compile_exception EXCEPTION;
PRAGMA EXCEPTION_INIT(compile_exception, -24344);
begin
if (system.wm$_check_install) then
return ;
end if ;
execute immediate 'alter package wmsys.ltadm compile';
execute immediate 'alter packag
The target operating system is in french... here is a raw translation:
1st one:
==============================
Treatment of object type DATABASE_EXPORT/SYSTEM_PROCOBJACT/PRE_SYSTEM_ACTIONS/PROCACT_SYSTEM
ORA-39083: Object type creation failed PROCACT_SYSTEM with error :
ORA-01843: invalid month
failed SQL :
BEGIN
if (system.wm$_check_install) then
return ;
end if ;
begin execute immediate 'insert into wmsys.wm$workspaces_table
values(''LIVE'',
''194'',
''-1'',
2nd one at the end of the import process:
==============================
Treatment of object type DATABASE_EXPORT/SCHEMA/POST_SCHEMA/PROCACT_SCHEMA
ORA-39083: Object type creation failed PROCACT_SCHEMA with error :
ORA-20000: Workspace Manager Not Properly Installed
failed SQL :
BEGIN
declare
compile_exception EXCEPTION;
PRAGMA EXCEPTION_INIT(compile_exception, -24344);
begin
if (system.wm$_check_install) then
return ;
end if ;
execute immediate 'alter package wmsys.ltadm compile';
execute immediate 'alter packag
By the way, the computer of the source database is Vista 64 in english and the destination computer is Vista 64 in french, do you think this has anything to do with these error messages? The parameters of the NLS_SESSION_PARAMETERS view are the same in the source and target database...
Thanks in advance for your help!
Joel Autotte
Lead Developer
Edited by: 871007 on Jul 13, 2011 7:31 AM

I tried to import the full database dump with the "imp" command and I had the same error message with more detail:
. Import d'objets SYSTEM dans SYSTEM
IMP-00017: Echec de l'instruction suivante avec erreur ORACLE 1843 :
"BEGIN "
"if (system.wm$_check_install) then"
" return ;"
" end if ;"
" begin execute immediate 'insert into wmsys.wm$workspaces_ta"
"ble"
" values(''LIVE'',"
" ''194'',"
" ''-1'',"
" ''SYS'',"
" *to_date(''09-DEC-2009 00:00:00'', ''DD-MON-YYYY HH"*
*"24:MI:SS''),"*
" ''0'',"
" ''UNLOCKED'',"
" ''0'',"
" ''0'',"
" ''37'',"
" ''CRS_ALLNONCR'',"
" to_date(''06-APR-2011 14:24:57'', ''DD-MON-YYYY HH"
"24:MI:SS''),"
" ''0'',"
" '''')'; end;"
"COMMIT; END;"
IMP-00003: Erreur ORACLE 1843 rencontrée
ORA-01843: ce n'est pas un mois valide
ORA-06512: à ligne 5
The call to the TO_DATE function with the string of the date format is incompatible with the format and language set in the NLS parameters of my database. Since I know that the "imp" and "exp" commands work client side (unlike "impdp" and "expdp"), I did a full export of the source database from the computer on which I try to import the dump to have the same language exported in the dump and I was able to import the dump successfully.
But, I would like to use the Data Pump tool instead of the old import and export tools. How would it be possible to set the NLS parameters that "impdp" must use before to launch the import of the dump?
The NLS parameters are set to the "AMERICAN" settings in both source and destination database when I validate that with the "NLS_DATABASE_PARAMETERS" view. The dump I did with "expdp" on the source database exported the data with the "AMERICAN" settings as well...
On the destination database, the computer language is in french and I guess it is considered by the Data Pump import tool since it outputs the log in the language of the computer and it tries to do a TO_DATE with the wrong date format because it works with the "CANADIAN FRENCH" settings...
Any suggestions? I'll continue to read on my side and re-post if I find the solution.
Thanks!
Edited by: 871007 on Jul 19, 2011 8:42 AM
Edited by: 871007 on Jul 19, 2011 8:43 AM
Edited by: 871007 on Jul 19, 2011 8:43 AM

Importing full database to different name

Hi i have one douhgt ,i want to import a full database dump to a new database with different name and new location.Can i do that i will explain the steps what i am plan to do
1) create an blank database with new name eg dev and same talbepsaces
2) take and full db export from source name prod using system
3) import with full db with system
4)Source is 9i and dest is 10grel2
Whether it will throw any error ?
rgds
jon

fine.
But i think exp/imp binary don't support 9i to 10g import.
so you using 10g export binary to take the 9i database full backup and import into 10g database use the 10g export binary.
Regards
Rajabaskar

Importing full database and SYSTEM password

Hi,
I have a export dump of a database (full database dump). Want to import on my existing database.
I have create a database, with tablespaces matching names with source database (i.e. got a list of tablespaces from the dba of source database and created them). Now, I am ready to import with imp command (with FULL=Y option).
Will the full database import change my SYSTEM's password to the system's password on the source database ?
Reason for this question is, If you try to read the export of full database (using wordpad !!), you will find all commands creating tablespaces, users, roles etc etc etc. Also, you will see commands which alter the users SYS and SYSTEM to change the password !!!
Any past experiences ??
Thanks in advance.

Hi,
>>Will the full database import change my SYSTEM's password to the system's password on the source database ?
Yes, take a look at demonstration below:
C:\>exp system/pass file=test.dmp full=y statistics=none
Export: Release 10.2.0.1.0 - Production on Mon Apr 21 13:59:51 2008
Copyright (c) 1982, 2005, Oracle. All rights reserved.
Connected to: Oracle Database 10g Express Edition Release 10.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^C
C:\>findstr /C:"ALTER USER SYS" TESTE.DMP
ALTER USER SYS IDENTIFIED BY VALUES '5638228DAF52805F' TEMPORARY TABLESPACE "TEMP"
ALTER USER SYSTEM IDENTIFIED BY VALUES 'D4DF7931AB130E37' TEMPORARY TABLESPACE "TEMP"
Cheers
Legatti

Importing full database xport

Hello all,
I have made a full database export.
When I now do an import can I: 1) use the DBA user of the database in which i do the import?
2) is there an automatical creation of the tabespaces and user from the import file
3) If not what do I have to do to get the exact the same database
Thanks in advance!
Hans Puts

Hi
It creates the tablespaces and users.Check your export dump file in wordpad.U will find details whatall it creates.
Jitesh

Import full database

please tell me complete steps of importing database in full mode.
the steps which I followed are:
1.I created a database with system and undo tablespace
2. I performed import using the following command
imp userid=system/manager file=c:\abc.dmp full=y
But there are so many errors
and nothing could be imported
somebody told me to create all the tablespaces and then to perform import
then I created 'USERS' tablespace and again performed import,
then even data of this tablespace could not be imported!! please help

1.I created a database with system and undo tablespace
2. I performed import using the following commandimp userid=system/manager file=c:\abc.dmp full=y
First, what is your oracle version?
Second,Was it a Full Database export?
what was the export parameters used?

Import full database question

We running oracle rdbms 11.2.0.3 on aix 6.2 and I am going to create a copy of a production database by using expdp and impdp. My quesition is that the target database for the impdp already has all of the data from the last time we refreshed from prod.
Can I do a fulll database import over the top of what is already there or do I have to start with a blank general purpose database first?
Thanks.

>
Can I do a fulll database import over the top of what is already there or do I have to start with a blank general purpose database first?You can use APPEND which would just append the data.
Also, you can clear the objects on the target database and do a fresh import.

Exp/Imp full database

Hello guys,
I'm having an issue with importing full database from one database(machine 1) to another database (machine2).
I am getting errors that users don't exist, datafile cannot be read etc errors.
I'm using Windows, and Oracle 9.2.0.6
How can I export the 'create objects' scripts from the source db that can run on the target db?
Any help appreciated.
Thanks,
Bharath

thank you. I actually sorted it out. The path of the datafiles in the source database is not present for the target database. So I created a similar path but kept no datafiles in it.
the import ran successfully and created the users and tablespaces as well.
thanks again

Export full DB/Import full DB privilege

Hii,
How to grant export full database and import full database privilege to a user in 920720 DB.
SQL> grant export full database to almasar;
ORA-00990: missing or invalid privilege
But its working in 10.1.0.2.0
Thankx

Hi
What does catexp do? It "Creates internal views for Export/Import utility", says the script
Also, if I need to export import
just a few tables from another schema, do I still
need EXP_FULL_DATABASE and IMP_FULL_DATABASE role?Yes you need to have EXP_FULL_DATABASE and IMP_FULL_DATABASE role

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

Import from a full database export having 5 .dmp files

i have a full database export having 5 .dmp files of 2g each, its having a user agvlc and which contains some partitioned tables,i imported the data for the user agvlc in a tablespace agvlc al the tables gets imported but the partitions are not getting imported what can i do to import the partitions as well
thanx in advance

Hello,
al the tables gets imported but the partitions are not getting imported what can i do to import the partitions as wellHow do you see that the Partitions are not imported ? Do you have any error message ?
Which options did you use for the Import ?
Please, as previously said, post all the informations so that we can help you efficiently.
Best regards,
Jean-Valentin

Importing full database

Similar Messages

Maybe you are looking for