Taking export/import of full database without data

What would be the parameters to take expoert/import for DB without Data?

i did ignore=y but still import is ending like this.
IMP-00017: following statement failed with ORACLE error 1917:
"GRANT CREATE INDEXTYPE TO "EBS_XE_REPO4""
IMP-00003: ORACLE error 1917 encountered
ORA-01917: user or role 'EBS_XE_REPO4' does not exist
IMP-00017: following statement failed with ORACLE error 1917:
"GRANT CREATE OPERATOR TO "EBS_XE_REPO4""
IMP-00003: ORACLE error 1917 encountered
ORA-01917: user or role 'EBS_XE_REPO4' does not exist
IMP-00017: following statement failed with ORACLE error 1917:
"GRANT CREATE PROCEDURE TO "EBS_XE_REPO4""
IMP-00003: ORACLE error 1917 encountered
ORA-01917: user or role 'EBS_XE_REPO4' does not exist
IMP-00017: following statement failed with ORACLE error 1917:
"GRANT CREATE SEQUENCE TO "EBS_XE_REPO4""
IMP-00003: ORACLE error 1917 encountered
ORA-01917: user or role 'EBS_XE_REPO4' does not exist
IMP-00017: following statement failed with ORACLE error 1917:
"GRANT CREATE SESSION TO "EBS_XE_REPO4""
IMP-00003: ORACLE error 1917 encountered
ORA-01917: user or role 'EBS_XE_REPO4' does not exist
IMP-00017: following statement failed with ORACLE error 1917:
"GRANT CREATE TABLE TO "EBS_XE_REPO4""
IMP-00003: ORACLE error 1917 encountered
ORA-01917: user or role 'EBS_XE_REPO4' does not exist
IMP-00017: following statement failed with ORACLE error 1917:
"GRANT CREATE TRIGGER TO "EBS_XE_REPO4""
IMP-00003: ORACLE error 1917 encountered
ORA-01917: user or role 'EBS_XE_REPO4' does not exist
IMP-00017: following statement failed with ORACLE error 1917:
"GRANT CREATE TYPE TO "EBS_XE_REPO4""
IMP-00003: ORACLE error 1917 encountered
ORA-01917: user or role 'EBS_XE_REPO4' does not exist
IMP-00017: following statement failed with ORACLE error 1917:
"GRANT CREATE SESSION TO "EBS_XE_REPO_USER""
IMP-00003: ORACLE error 1917 encountered
ORA-01917: user or role 'EBS_XE_REPO_USER' does not exist
IMP-00017: following statement failed with ORACLE error 1917:
"GRANT CREATE ANY TYPE TO "EBS_XE_REPO5""
IMP-00003: ORACLE error 1917 encountered
ORA-01917: user or role 'EBS_XE_REPO5' does not exist
IMP-00017: following statement failed with ORACLE error 1917:
"GRANT CREATE ANY TYPE TO "EBS_XE_REPO6""
IMP-00003: ORACLE error 1917 encountered
ORA-01917: user or role 'EBS_XE_REPO6' does not exist
IMP-00017: following statement failed with ORACLE error 1917:
"GRANT UNLIMITED TABLESPACE TO "EBS_XE_REPO5""
IMP-00003: ORACLE error 1917 encountered
ORA-01917: user or role 'EBS_XE_REPO5' does not exist
IMP-00017: following statement failed with ORACLE error 1917:
"GRANT UNLIMITED TABLESPACE TO "EBS_XE_REPO6""
IMP-00003: ORACLE error 1917 encountered
ORA-01917: user or role 'EBS_XE_REPO6' does not exist
IMP-00017: following statement failed with ORACLE error 1917:
"GRANT CREATE PROCEDURE TO "EBS_XE_REPO2""
IMP-00003: ORACLE error 1917 encountered
ORA-01917: user or role 'EBS_XE_REPO2' does not exist
IMP-00017: following statement failed with ORACLE error 1917:
"GRANT CREATE TYPE TO "EBS_XE_REPO2""
IMP-00003: ORACLE error 1917 encountered
ORA-01917: user or role 'EBS_XE_REPO2' does not exist
IMP-00017: following statement failed with ORACLE error 1917:
"GRANT ALTER SYSTEM TO "EBS_XE_REPO2""
IMP-00003: ORACLE error 1917 encountered
ORA-01917: user or role 'EBS_XE_REPO2' does not exist
IMP-00017: following statement failed with ORACLE error 1917:
"GRANT CREATE CLUSTER TO "EBS_XE_REPO2""
IMP-00003: ORACLE error 1917 encountered
ORA-01917: user or role 'EBS_XE_REPO2' does not exist
IMP-00017: following statement failed with ORACLE error 1917:
"GRANT CREATE INDEXTYPE TO "EBS_XE_REPO2""
IMP-00003: ORACLE error 1917 encountered
ORA-01917: user or role 'EBS_XE_REPO2' does not exist
IMP-00017: following statement failed with ORACLE error 1917:
"GRANT CREATE OPERATOR TO "EBS_XE_REPO2""
IMP-00003: ORACLE error 1917 encountered
ORA-01917: user or role 'EBS_XE_REPO2' does not exist
IMP-00017: following statement failed with ORACLE error 1917:
"GRANT CREATE SEQUENCE TO "EBS_XE_REPO2""
IMP-00003: ORACLE error 1917 encountered
ORA-01917: user or role 'EBS_XE_REPO2' does not exist
IMP-00017: following statement failed with ORACLE error 1917:
"GRANT CREATE TABLE TO "EBS_XE_REPO2""
IMP-00003: ORACLE error 1917 encountered
ORA-01917: user or role 'EBS_XE_REPO2' does not exist
IMP-00017: following statement failed with ORACLE error 1917:
"GRANT CREATE TRIGGER TO "EBS_XE_REPO2""
IMP-00003: ORACLE error 1917 encountered
ORA-01917: user or role 'EBS_XE_REPO2' does not exist
IMP-00017: following statement failed with ORACLE error 1917:
"GRANT "CONNECT" TO "EBS_XE_REPO""
IMP-00003: ORACLE error 1917 encountered
ORA-01917: user or role 'EBS_XE_REPO' does not exist
IMP-00017: following statement failed with ORACLE error 1917:
"GRANT "CONNECT" TO "EBS_XE_REPO2""
IMP-00003: ORACLE error 1917 encountered
ORA-01917: user or role 'EBS_XE_REPO2' does not exist
IMP-00017: following statement failed with ORACLE error 1917:
"GRANT "CONNECT" TO "EBS_XE_REPO_ALR""
IMP-00003: ORACLE error 1917 encountered
ORA-01917: user or role 'EBS_XE_REPO_ALR' does not exist
IMP-00017: following statement failed with ORACLE error 1917:
"GRANT "CONNECT" TO "EBS_XE_REPO4""
IMP-00003: ORACLE error 1917 encountered
ORA-01917: user or role 'EBS_XE_REPO4' does not exist
IMP-00017: following statement failed with ORACLE error 1917:
"GRANT "CONNECT" TO "EBS_XE_REPO6""
IMP-00003: ORACLE error 1917 encountered
ORA-01917: user or role 'EBS_XE_REPO6' does not exist
IMP-00017: following statement failed with ORACLE error 1917:
"GRANT "CONNECT" TO "EBS_XE_REPO5""
IMP-00003: ORACLE error 1917 encountered
ORA-01917: user or role 'EBS_XE_REPO5' does not exist
IMP-00017: following statement failed with ORACLE error 1917:
"GRANT "RESOURCE" TO "EBS_XE_REPO5""
IMP-00003: ORACLE error 1917 encountered
ORA-01917: user or role 'EBS_XE_REPO5' does not exist
IMP-00017: following statement failed with ORACLE error 1917:
"GRANT "RESOURCE" TO "EBS_XE_REPO6""
IMP-00003: ORACLE error 1917 encountered
ORA-01917: user or role 'EBS_XE_REPO6' does not exist
IMP-00017: following statement failed with ORACLE error 1918:
"ALTER USER "EBS_XE_REPO" DEFAULT ROLE ALL"
IMP-00003: ORACLE error 1918 encountered
ORA-01918: user 'EBS_XE_REPO' does not exist
IMP-00017: following statement failed with ORACLE error 1918:
"ALTER USER "EBS_XE_REPO2" DEFAULT ROLE ALL"
IMP-00003: ORACLE error 1918 encountered
ORA-01918: user 'EBS_XE_REPO2' does not exist
IMP-00017: following statement failed with ORACLE error 1918:
"ALTER USER "EBS_XE_REPO_ALR" DEFAULT ROLE ALL"
IMP-00003: ORACLE error 1918 encountered
ORA-01918: user 'EBS_XE_REPO_ALR' does not exist
IMP-00017: following statement failed with ORACLE error 1918:
"ALTER USER "EBS_XE_REPO5" DEFAULT ROLE ALL"
IMP-00003: ORACLE error 1918 encountered
ORA-01918: user 'EBS_XE_REPO5' does not exist
IMP-00017: following statement failed with ORACLE error 1918:
"ALTER USER "EBS_XE_REPO6" DEFAULT ROLE ALL"
IMP-00003: ORACLE error 1918 encountered
ORA-01918: user 'EBS_XE_REPO6' does not exist
IMP-00017: following statement failed with ORACLE error 1918:
"ALTER USER "EBS_XE_REPO_USER" DEFAULT ROLE ALL"
IMP-00003: ORACLE error 1918 encountered
ORA-01918: user 'EBS_XE_REPO_USER' does not exist
IMP-00017: following statement failed with ORACLE error 1918:
"ALTER USER "EBS_XE_REPO4" DEFAULT ROLE ALL"
IMP-00003: ORACLE error 1918 encountered
ORA-01918: user 'EBS_XE_REPO4' does not exist
IMP-00017: following statement failed with ORACLE error 1918:
"ALTER USER "EBS_XE_REPO" QUOTA UNLIMITED ON "EBS_XE_REPO_INDX" QUOTA UNLIMI"
"TED ON "EBS_XE_REPO_DATA""
IMP-00003: ORACLE error 1918 encountered
ORA-01918: user 'EBS_XE_REPO' does not exist
IMP-00017: following statement failed with ORACLE error 1918:
"ALTER USER "EBS_XE_REPO2" QUOTA UNLIMITED ON "EBS_XE_REPO2_INDX" QUOTA UNLI"
"MITED ON "EBS_XE_REPO2_DATA""
IMP-00003: ORACLE error 1918 encountered
ORA-01918: user 'EBS_XE_REPO2' does not exist
IMP-00017: following statement failed with ORACLE error 1918:
"ALTER USER "EBS_XE_REPO_ALR" QUOTA UNLIMITED ON "EBS_XE_REPO_ALR_INDX" QUOT"
"A UNLIMITED ON "EBS_XE_REPO_ALR_DATA""
IMP-00003: ORACLE error 1918 encountered
ORA-01918: user 'EBS_XE_REPO_ALR' does not exist
IMP-00017: following statement failed with ORACLE error 1918:
"ALTER USER "EBS_XE_REPO4" QUOTA UNLIMITED ON "EBS_XE_REPO4_INDX" QUOTA UNLI"
"MITED ON "EBS_XE_REPO4_DATA""
IMP-00003: ORACLE error 1918 encountered
ORA-01918: user 'EBS_XE_REPO4' does not exist
IMP-00017: following statement failed with ORACLE error 959:
"ALTER USER "EBSJM" QUOTA UNLIMITED ON "EBSJM_INDEX" QUOTA UNLIMITED ON "EBS"
"JM_DATA""
IMP-00003: ORACLE error 959 encountered
ORA-00959: tablespace 'EBSJM_INDEX' does not exist
IMP-00017: following statement failed with ORACLE error 1918:
"ALTER USER "EBS_XE_REPO6" QUOTA UNLIMITED ON "EBS_XE_REPO6_INDX" QUOTA UNLI"
"MITED ON "EBS_XE_REPO6_DATA""
IMP-00003: ORACLE error 1918 encountered
ORA-01918: user 'EBS_XE_REPO6' does not exist
IMP-00017: following statement failed with ORACLE error 1918:
"ALTER USER "EBS_XE_REPO5" QUOTA UNLIMITED ON "EBS_XE_REPO5_INDX" QUOTA UNLI"
"MITED ON "EBS_XE_REPO5_DATA""
IMP-00003: ORACLE error 1918 encountered
ORA-01918: user 'EBS_XE_REPO5' does not exist
. importing EBS_ADMIN's objects into EBS_ADMIN
. importing EBS_XE_REPO's objects into EBS_XE_REPO
IMP-00003: ORACLE error 1435 encountered
ORA-01435: user does not exist
. importing EBS_XE_REPO2's objects into EBS_XE_REPO2
IMP-00003: ORACLE error 1435 encountered
ORA-01435: user does not exist
. importing EBS_XE_REPO_ALR's objects into EBS_XE_REPO_ALR
IMP-00003: ORACLE error 1435 encountered
ORA-01435: user does not exist
. importing EBS_DWH's objects into EBS_DWH
. importing EBS_XE_REPO4's objects into EBS_XE_REPO4
IMP-00003: ORACLE error 1435 encountered
ORA-01435: user does not exist
. importing PERFSTAT's objects into PERFSTAT
. importing EBS_XE_REPO6's objects into EBS_XE_REPO6
IMP-00003: ORACLE error 1435 encountered
ORA-01435: user does not exist
. importing EBS_XE_REPO5's objects into EBS_XE_REPO5
IMP-00003: ORACLE error 1435 encountered
ORA-01435: user does not exist
. importing SYSTEM's objects into SYSTEM
. importing WMSYS's objects into WMSYS
. importing TOAD's objects into TOAD
. importing EBS_REPO's objects into EBS_REPO
. importing EBS_STAGE's objects into EBS_STAGE
. importing EBS_XE_REPO's objects into EBS_XE_REPO
"ALTER SESSION SET CURRENT_SCHEMA= "EBS_XE_REPO""
IMP-00003: ORACLE error 1435 encountered
ORA-01435: user does not exist
IMP-00000: Import terminated unsuccessfully

Similar Messages

Export/import to/from database

hi,
i do not know what is this for. i read the help but still no idea.
i know to use export/import to/from memory id and also set/get but not export/import to/from database.
1) what help says it stores data cluster? what is data cluster
2) can have example of export/import to/from database?
3) what is the different for export/import to/from memory id and database?
thanks

Hi,
1) A data cluster is a set of data objects grouped together for the purpose of storage in a storage medium(Like database, local memory or shared meomory etc), which can only be edited using ABAP statements like EXPORT, IMPORT and DELETE.
2) Suppose you want to export the data in a internal table to database.
Here TABLE_ID is the identifer of your data cluster. You are exporting your data to a SAP table INDX and giving it an ID (TABLE_ID in this case and this ID you are giving it an area by name XY where your data will be stored). EXPORT tab = itab
TO DATABASE indx(XY)
CLIENT '000'
ID 'TABLE_ID'.
You can get this data as follows.
IMPORT tab = itab
FROM DATABASE indx(xy)
CLIENT '000'
ID 'TABLE_ID'.
3) The difference is simple when you use MEMORY ID the data you export is stored in the application server MEMORY where as in the case of DATABASE it is stored in the database.
Regards,
Sesh

Full list of schemas not exported / imported when FULL=Y

Hi Guys,
Verison: 10.2.0.5
Can advise on the full list of schemas not exported / imported when FULL=Y?
thanks!

dbaing wrote:
Hi Guys,
Verison: 10.2.0.5
Can advise on the full list of schemas not exported / imported when FULL=Y?
thanks!System schemas. Please see the following:
http://docs.oracle.com/cd/B19306_01/server.102/b14215/dp_export.htm#i1006790
http://docs.oracle.com/cd/E11882_01/server.112/e22490/dp_export.htm#i1006790
You may also be interested in the following:
-How to Perform A Full Database Export Import During Upgrade, Migrate, Copy Or Move Of A Database [ID 286775.1]
-Oracle DataPump Quick Start [ID 413965.1]
-How To move Or Copy A Database Using DataPump [ID 855268.1]

What is the best way to import a full database?

Hello,
Can anyone tell me, what is the best way to import a full database called test, into an existing database called DEV1?
when import into an existing database do you have drop the users say pinfo, tinfo schemas are there. do i have drop these and recreate or how it will work, when you impport full database?
Could you please give step by step instructions....
Thanks a lot...

Nayab,
http://youngcow.net/doc/oracle10g/backup.102/b14191/rcmdupdb005.htmA suggestion that please don't use external sites which host oracle docs since there can not be any assurance that whether they update their content with the latest corrections or not. You can see the updated part no in the actual doc site from oracle,
http://download.oracle.com/docs/cd/B19306_01/backup.102/b14191/rcmdupdb.htm#i1009381
Aman....

Export and import tables with and without data

I have few table which i want to take export with data and some without data, and import that in new db? Send me the command plz for this.

exp and imp all have a flag
ROWS import data rows (Y/N)
but that flag apply to the whole export/import process.
You will need do export twice,
ROWS=Y first with list of tables that need data
and ROWS=N with list of tables without data.

Some objects in sys schema not imported usinf full database import/export.

Hello All,
We need to migrate database from one server to new server using same database version 11g Release 2 (11.2.0.1.0). We have some production objects in sys schema. We took full export using full=y and then import on new server using full=y. Other objects belonging to different tablespaces and users has successfully imported but production objects i.e table in sys schema not import.
We used following commands for export and import:
# exp system file=/u01/backup/orcl_full_exp.dmp log=/u01/backup/orcl_full_exp.log full=y statistics=none
# imp system file=/u01/backup/orcl_full_exp.dmp log=/u01/backup/orcl_full_imp.log full=y ignore=y
Kind Regards,
Sharjeel

Hi,
First of all it is not good practice to keep user object in the sys schema
second you are useing version 11gr2 what not you go for datapump export/import method.
third, did you get any error in import, what is the error

Export/import to clone database -- please advise

Hi All,
Need help especially from exports that are strong in export/import.
can someone advise me how to use export/import to clone a database?
I know how to clone database using cold backup and hot backup.
But wish to know the full steps in using export/import to do cloning.
I'm going to do a full export on my "TEST" database, drop the database, create a database and import using the full export.
After doing a full database export, full=y. What are the steps to follow. Have a few doubts about it.
1) export the database (full=y)
2) drop the database
3) re-create the database, will be using the same name "TEST".
4) create the users (IDs created by DBA, eg: schemas), tablespace and datafiles. --> import doesn't do it right?
5) do a full import (full=y). In this step, will i encounter any problems? As in understand that all the oracle-owned objects (example SYSTEM, SYS, AUX) are already in the newly created database, will import full=y cause any problems?
6) do i have to re-create the roles, SYNONYMS and grant role,sys,obj privileges to IDs not created by oracle. (example schema owner)
in short i would like to know what EXPORT will export and not export
what IMPORT will import and not import.
Please advise.

Hi zetabouy,
thanks for ur input, definately helpful for me.
just to confirm. am i right to say that only a full database level (full=y) export/import will export/import out roles as well as public synonyms? because i have tried also exporting a user from the database, and imported that user into a different database, but public synonyms and roles were not imported.
one more question:
For example we are going to do port data from production to uat database using export and import for only the schema.
After exporting from production with such syntax (owner=OWNER01),
is is better to drop all objects beloging to the schema owner in UAT before importing it (touser=OWNER01, ignore=y) using the production dumpfile?
I'm asking this question as I'm afraid that if we did not drop all the pl/sql objects in UAT database, the updated procedures/fuctions/triggers exported from the production database will not get imported to the UAT database as UAT database have the same procedures/fuctions/triggers names (but not updated code) .
will profiles be exported and imported too duing full database level exp/imp?
please kindly advise.
thanks
Message was edited by:
chew

Export / import tablespace with all objects (datas, users, roles)

Hi, i have a problem or question to the topic export / import tablespace.
On the one hand, i have a database 10g (A) and on the other hand, a database 11g (B).
On A there is a tablespace called PRO.
Furthermore 3 Users:
PRO_Main - contains the datas - Tablespace PRO
PRO_Users1 with a role PRO_UROLE - Tablespace PRO
PRO_Users2 with a role PRO_UROLE - Tablespace PRO
Now, i want to transfer the whole tablespace PRO (included users PRO_MAIN, PRO_USER1, PRO_User2 and the role PRO_UROLE) from A to B.
On B, I 've created the user PRO_Main and the tablespace PRO.
On A , i execute following statement:
expdp PRO_Main/XXX TABLESPACES=PRO DIRECTORY=backup_datapump DUMPFILE=TSpro.dmp LOGFILE=TSpro.log
On B:
impdp PRO_Main/XXX TABLESPACES=PRO DIRECTORY=backup_datapump DUMPFILE=TSpro.dmp LOGFILE=TSpro.log
Result:
The User PRO_Main was imported with all the datas.
But i 'm missing PRO_USER1, PRO_User2 and the role PRO_UROLE...
I assume, i 've used wrong parameters in my expd and / or impdp.
It would be nice, if anybody can give me a hint.
Thanks in advance.
Best Regards,
Frank

When you do a TABLESPACE mode export by specifying just the tablespaces, then all that gets exported are the tables and their dependent objects. The users, roles, and the tablespace definitions themselves don't get exported.
When you do a SCHEMA mode export by specifying the schemas, you will get the schema definitions (if the schema running the export is privied) and all of the objects that the schema owns. The schema does not own roles or tablespace definitions.
In your case, you want to move
1. schemas - which you already created 1 on your target database
2. roles
3. everything in the tablespaces owned by multiple schemas.
There is no 1 export/import command that will do this. This is how i would do this:
1 - move the schema definitions
a. you can either create these manually or
b1. expdp schemas=<your list of schemas> include=user
b2 impdp the results from b1.
2. move the roles
expdp full=y include=role ...
remember, this will include all roles. If you want to limit what gets exported, then use:
include=role:"in ('ROLE1', 'ROLE2', ETC.)
impdo the roles just exported
3. move the user information
a. If you want to move all of the schema's objects like functions, packages, etc, then you need to use a schema mode
export
expdp user/password schemas=a,b,c ...
b. If you want to move only the objects in those tablespaces, then use the tablespace export
expdp user/password tablespaces=tbs1, tbs2, ...
c. import the dumpfile generated in step 3
impdp user/password ...
Hope this helps.
Dean

Importing a full database

Hi,
I want to transfer a database from one computer A to another computer B. On the B computer I created manually the database. If I imported one time the database with full = y, and appeared errors, the users were created but the tables were without data if I give again the command imp with full=y and ignore=y options everything can be ok? What I import at the new import is written on the old import?
Thank you,
Mihaela

If the table already exists you will have an exception and the import will continue. The create table statement wil not be execute. It means that if your tables structure is equal you can import your data (rows=y) without any problems. The rows will not be overwritten! If you have another table structure you must first drop the table. If the table contains rows and you want to have only those in your import you must execute a truncate on your tables.
Bye, Aron

How to export/import plan witch a scheduler data

How to export/import plan witch a scheduler data

Hi,
See the BAM Enterprise Link Utilities User's Guide for additional Enterprise Link import/export capabilities not exposed via ICommand.
Regards, Stephen

Export / Import with FULL=Y

Hello DBA's,
after consulting several thread on exp/imp with the option full=y the doubt that I have left is when using imp with full=y ignore=y in a new data base, the data base obtained will be equal to the data base from which export with full=y became. Thanks for its answers.

export full=y
will export all the user ,roles,tablespace creation scripts,tables all the datadictionary views
for example if u connect the databse with single user try to get the privileges from the existing Db and then
create the database in the new server
create users and grant privileges before import;
then import with fromuser= ,touser
if you issues FULL=y
it will start creating all the system ,index and all the other tablespaces provided it should have the same directories as it is in current DB
to avoid create the dataabse ,tablespace users then import with fromuser,touser option
thanks

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

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

Export/Import Data Pump

HI
AIX 5.3
Oracle 11.2.0.1
Oracle 10.2.0.3
I have done FULL export in 10g and Import 10g and also 11g using DATA PUMP. But I could not find any DBLINK in target database.
Does it create DBLINK while import?
Thanks,
Vishal

I have done FULL export in 10g and Import 10g and also 11g using DATA PUMP. But I could not find any DBLINK in target database.
Does it create DBLINK while import?It does. Depends on the option used while Datapump Import.
Full Database export exports DB_LINKS.
database_export_objects shows
SELECT named, object_path, comments FROM database_export_objects WHERE named='Y';
Y DB_LINK Private and public database linksHTH
-Anantha

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

Taking export/import of full database without data

Similar Messages

Maybe you are looking for