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

Similar Messages

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]

Portal Export Import with DB on different OS

Hi All,
I have a quick question about exporting the OracleAS Portal Metadata Repository database. Our source DB is on a different OS to our target DB.
We are going to apply the 10.1.2.3 patch and associated portal export/import patches to both nodes (from note 263995.1).
Our understanding was that we would use the method described in Chapter 10 of the Portal 10.1.4 Admin Guide (http://download.oracle.com/docs/cd/B14099_18/portal.1014/b19305/cg_imex.htm).
However, according to metalink note#276620.1, because our source and target OS are different, we should use the database export/import methodology that is described in Chapter 11 of the Application Server 10.1.2 Admin Guide (http://download.oracle.com/docs/cd/B14099_18/core.1012/b13995/prodtest.htm).
Could anyone tell me which way is better, we would prefer to use the database export/import method, has anyone tried this and what are their experiences.
Regards,
Tim.

kirwantd wrote:
We are going to apply the 10.1.2.3 patch and associated portal export/import patches to both nodes (from note 263995.1).
Our understanding was that we would use the method described in Chapter 10 of the Portal 10.1.4 Admin Guide (http://download.oracle.com/docs/cd/B14099_18/portal.1014/b19305/cg_imex.htm).
However, according to metalink note #276620.1, because our source and target OS are different, we should use the database export/import methodology that is described in Chapter 11 of the Application Server 10.1.2 Admin Guide (http://download.oracle.com/docs/cd/B14099_18/core.1012/b13995/prodtest.htm).
Could anyone tell me which way is better, we would prefer to use the database export/import method, has anyone tried this and what are their experiences.
Regards,
Tim.As far as your referred Metalink note is concerned, it gives you three options to move your repository with if you are working with 10.1.4 Portal.
It's a difference of can, should and must.
- It only shows ability to use three options ( can );
- on the whole, it does not give preferences for any method ( should );
- nor does it put a requirement for any single option ( must ).
( the only requirement/prohibition is for the option 2 which is not supported ).
we have used the first three methods given on the note (yes, we also tried 2; this note came later). 1 is what we use regularly for transports between environments; and 3 we use for environment staging (as given in chap 11 of pt. 3). both can be messy with a large repository (we do so for about ~400 GB) repository. but following that supportability guide (Metalink Note 333867.1), method 1 works too.
hope that helps!
AMN

Export/Import with apps user or EUL schema owner ?

Hi,
I am working with a migration plan to move Discoverer 9 to Discoverer 10.
It is an apps mode EUL, where business areas and workbooks have been granted to Apps Users & Responsibilities.
Customer has only maintained the EUL with the database user of the EUL owner.
What is recommended for exporting/importing the EUL from 9 to 10.
To connect to Administrator as the EUL owner, or to connect as an apps user ( SYSADMIN ? )
Will all the grants to apps users/responsibilities work when importing as schema owner ?
I tried to create a entire EUL export file connected as EUL owner, and for the workbooks the export log contained :
1234#.Workbook name1
2345#.Workbook name 2
1234 is the user_id for the workbook owner ( All workbooks have been created by an apps user )
Will the import process manage to convert this user_id, and set the correct owner for the imported workbooks ?
( I will use the option Only take ownership if original owner not found )
I am not sure, but I think I have seen the following syntax in other projects when exporting an apps mode EUL
SYSADMIN.Workbook name 1
SYSADMIN.Workbook name 2

>
What is recommended for exporting/importing the EUL from 9 to 10.
To connect to Administrator as the EUL owner, or to connect as an apps user ( SYSADMIN ? )
Will all the grants to apps users/responsibilities work when importing as schema owner ?
Hi,
The best that i know is that you should export using the DB user so that you will not have problem with workbooks or BA that you are not granted for (or any other grants or privileges).
The import should be done using the APPS user (the super user you use).
That way if you import a workbook that the owner will not be found then you will get the ownership and you can after migration deal with it.
If you'll do that with the DB (EUL owner) user after migration you will not have access to those workbooks.
Any way about the workbooks i suggest you'll save them as DIS files for cases that the import of the workbooks or the owner association for them fail.

How can I export songs with full info (INCLUDING LYRICS) to file for future use? [x]

Hi everyone,
I got my new iPod touch 4th gen, and I spend literally all day to edit songs' info like Artist, Lyrics, Album... with like thousand songs.. Then I've tried to export them fully for future use as back up, but I could not find any option to do so. Exporting library and playlist only saves info for basic tags but no lyrics in it. So what should I do? I've tried iTunes Export and mp3Tag but I still could not do it.
I would appreciate much any help for me to back up full information of songs for future use.
Regards,
[x]

Thanks for the responses.
I forgot to mention the dimensions I need the file to be at, sorry. Overnight Prints requires that the uploaded file be at 2.13 inches wide by 6.13 inches high (or 638 by 1838 pixels) at 300 dpi. I think I understand what Scott Falkner means by pixels are not a unit of measure. However, I have been using inches in Illustrator, with the file being set to the height and width (in inches) required by Overnight Prints.
Here is what I have uploaded to Overnight Prints so far:
- Illustrator file set to 2.13 inches wide by 6.13 inches high – Upload preview on Overnight Prints is correct size, but shows the bookmark as pixelated/blurry.
- Saved above Illustrator file as copy: “Press Quality Preset” PDF – Upload preview on Overnight Prints is correct size, but the bookmark is still pixelated/blurry.
- Exported same Illustrator file as a PNG (638 pixels wide by 1838 pixels high - 300dpi) – Upload preview on Overnight Prints is correct size, but shows the bookmark as pixelated/blurry.
- Creating an Illustrator file at 638 by 1838 pixels makes any file that is uploaded preview on Overnight Prints as too large, but not pixelated/blurry (I think I now understand why, just covering all my bases).
So, I guess my more specific question would be:
How can I create a file that I can upload to Overnight Prints (TIF, PDF, JPG, EPS, PNG, or AI) that ends up at the dimensions (in inches) required, while not appearing (at least in the upload preview) as low resolution (pixelated/blurry)?
Thanks in advance for any responses (especially to such a novice question).

Export/Import with where condition

DearAll,
I am facing a problem in the delete of a huge table that take 3 hours
DELETE FROM HST HST
WHERE JV_TYPE <> 999
and ( HST.VALUE_DATE <= TO_DATE ('31/12/2010','DD/MM/YYYY')
AND HST.TRANS_DATE <= TO_DATE ('31/12/2010','DD/MM/YYYY'))
what i am trying to do is to export the HST table and import it into another table
but what i need to do is to have a dump with where condition including only the needed records in the table not deleted in the DML above as well as the indexes, triggers.
Thanks

If I try the following:
CONN / AS SYSDBA
CREATE OR REPLACE DIRECTORY dpump_dir1 AS '/folder/';
GRANT READ, WRITE ON DIRECTORY dpump_dir1 TO bokprod;
expdp bokprod/bokprod@uat TABLES=HST PARFILE=hst_query.par
In the parfile:
QUERY=hst:"WHERE JV_TYPE <>999 and ( HST.VALUE_DATE > TO_DATE ('31/12/2010','DD/MM/YYYY') AND HST.TRANS_DATE > TO_DATE ('31/12/2010','DD/MM/YYYY'))"
DUMPFILE=exp.dmp
DIRECTORY=dpump_dir1
LOGFILE=exp.log
impdp bokprod/bokprod@uat DIRECTORY=dpump_dir1 DUMPFILE=exp.dmp
TABLES=bokprod.hst REMAP_TABLE=bokprod.hst:hst_imported
My question is:
1- the parameter file, if i put it in the dpump_dir1 directory, is it read by the expdp command?
2- the hst_imported table created by the remap_table command , is it created with the indexes and triggers already existant on hst table?
Appreciate yoyr help Dears

Export / import with logical system

Re: AC 5.3 - RAR - SP17
I have DEV and QA connected to GRC DEV\QA and am defining my ruleset here. The ruleset is defined against a logical system.
I have PRD connected to GRC PRD and want to import the ruleset that I have developed in GRC DEV\QA. I have exported the ruleset using utilies \ export and then try to import using the utilies \ import function I get an error message and cannot import the rules into the GRC PRD system. When exporting I have selected the ruleset to export against the logical system. When importing I am selecting the physical system. Will that work ? What am I missing ?
Edited by: Jan Chan on Jul 8, 2011 5:02 PM

I determined that there was some corrupt data in the ruleset connected to the logical system that I was exporting. Attempted to correct it by removing the entries and regenerating the rules under the logical system area. All attempts to correct the data have not worked - even removing the "Action" completely from the ruleset but the data still contains the corrupt data associated with the logical system. May need to use "manage deletion" to completely remove it but my entire ruleset is defined for this logical system.
I don't think there's a simple way to just change the "system" on each functions "action" - mass function maintenance does not appear to work for this.

Export Import with different tablespaces

Does anyone know if there is a way to export from one database (creating a dmp file) and then importing into another database with different tablespaces? I have tried this and get this error:
ORA 959. It complained that the tablespace doesnt exist (which it doesnt). Is there a way I can change the export or import parameters to avoid this and just use the default tablespaces?
I may well be missing the point here so please feel free to tell me I am being a fool.
Thanks
Johan

Example. All these tables are from the same schema with the same tablespace specified in the dmp file. There are many more and 90 % fail but not all.
importing SCHEMA1 objects into SCHEMA2
IMP-00017: following statement failed with ORACLE error 959:
"CREATE TABLE "ACCOUNT_RPRT_NOT_TOBE_PUBLISH" ("O__NUM" CHAR(13) NOT NULL EN"
"ABLE, "O__ST" NUMBER(4, 0) NOT NULL ENABLE, "STEP_COUNTER" NUMBER(7, 0), "S"
"TATUS" NUMBER(1, 0), "RETRY_COUNTER" NUMBER(5, 0), "RESTART_COUNTER" NUMBER"
"(5, 0), "PID" NUMBER(3, 0), "OBJ_LOCK" VARCHAR2(10), "MYFILE" VARCHAR2(200)"
", "LONG_FIELD" CLOB, "LAST_SELECT_B_S" VARCHAR2(250), "LAST_SELECTION" VARC"
"HAR2(250), "L_EXECUTION_CTRL" CHAR(13), "ID" NUMBER(6, 0), "ERROR_COUNTER" "
"NUMBER(7, 0), "CREATION_TIME" NUMBER(5, 0), "CREATION_DATE" NUMBER(6, 0), ""
"COMPLETION_TIME" NUMBER(5, 0), "COMPLETION_DATE" NUMBER(6, 0), "COMMIT_COUN"
"TER" NUMBER(5, 0)) PCTFREE 10 PCTUSED 40 INITRANS 1 MAXTRANS 255 STORAGE(I"
"NITIAL 65536 FREELISTS 1 FREELIST GROUPS 1) TABLESPACE "AIA_DATA_T_256K" LO"
"GGING NOCOMPRESS LOB ("LONG_FIELD") STORE AS (TABLESPACE "AIA_DATA_T_256K""
" ENABLE STORAGE IN ROW CHUNK 8192 PCTVERSION 10 NOCACHE STORAGE(INITIAL 65"
"536 FREELISTS 1 FREELIST GROUPS 1))"
IMP-00003: ORACLE error 959 encountered
ORA-00959: tablespace 'AIA_DATA_T_256K' does not exist
. . importing table "ACTUARIAL_RPT_CNTR" 0 rows imported
. . importing table "ACTUARIAL_RPT_CVRG" 0 rows imported
. . importing table "ALIS_CANCEL_BILLING" 2799 rows imported

Exporting photos with full meta data

Hi all, I'm trying to export some pics. I'm exporting them to a folder on my desktop, after the export I go to any of the pics and click CDM+I to check the info on the pics and it is showing the pic as having been created now, not when it taken. I would like to be able to keep the original data on the pic. What an I doing wrong ? I've tried several ways under file-export but always lose the date and time when the pic was taken, all other camera info is intact.. Thanks for any help.
Randy

Hard to recall when I last so so much incorrect material in a single post. It's quite obvious that you have little understanding of how digital photography works, the relationship between photos, files, Exif and IPTC metadata and how a Photo Manager works. Indeed, you seem clueless as to how the forum works too.
There is no bug in iPhoto. Yes you do get out what you originally put in, plus whatever you added.
First misunderstanding: A File is not a Photo. A file is a collection of data. The file has a creation date, a file has modification date. Neither of these things necessarily reflect the date of the Photograph. Simple example: When you copy a file from a camera to your computer a +new file is made+. That's a simle fact. One file cannot be both on your camera and your computer.
To overcome this difficultly Exif metadata was created. This is part of the Photo. It records - along with a lot of other data - the date and time the Photo was taken. As you copy files this data is copied and so, even though the dates on the file may change the dates on the photo doesn't.
Exif is standard metadata supported by every camera manufacturer, every computer OS and any significant photo applications out there. Perhaps you should read up a little on it. It might help clear up your thinking.
Also an export might appear to fail when 90% done due to a volume error.
A volume error has nothing to do with Metadata, nothing to do with where you imported files from, nor indeed where the files are stored. This is utter twaddle. It's a bit like saying "If the children are in the back seat, the front wheel might fall off your car". Rubbish.
The Folder Structure of the Library - or indeed the one the files are imported from - matters not a single whit. A photo app gets +no information whatever+ about a photo from the folder it is in. Nothing. Zilch. Nada.
Now as well as not understanding much about Photos, files and metadata, you demonstrate that you are equally clueless about iPhoto.
. You will see two folders named Originals and Modified and if you want to just bail on iPhoto and possibly retain some organization of your photos, you can just drag these out of the iPhoto library to your hard drive
Now there's an excellent way to lose lots and lots of metadata. For a start you lose any metadata you've added in iPhoto - titles, descriptions, keywords. The only way to get this data is to export from iPhoto. Really, there is never a need to enter the library in this way. What you suggests causes data loss and you might take the time to warn folks: "Oh by the way, doing what I suggest will cause dataloss."
The error people keep getting... is likely because the export combines all your photos into one folder,
Export will not do this +unless you tell it to+
and most people have multiple duplicate file names like 1.jpg or family.jpg etc.
Most people?
so iPhoto can't complete an export of "originals" and your only other likely option is to do an export in numeric sequence, which will likely lose all the original file names.
A really basic misunderstanding. This is a (very sensible) limitation of the Finder You can't have two files of the same name in one folder. One will overwrite the other and so you lose data. If you ask iPhoto to export two files of the same name to a single folder it won't do it as the second would overwrite the first. You wouldn't want that would you? So, your "bug" is a simple and sensible precaution against dataloss.
There are several possible naming schemes within iPhoto to avoid this problem, but the easiest is the one is sequential. Why? Because you can choose your Prefix. So, if you have two files called "Family" then you can give them the Prefix family and export sequentially. Result: two files called Family1 and Family2.
But all this can be avoided simply by not exporting into one large folder. If, instead, you export Event by Event (something that can be done manually, or automated with Automator or with a free 3rd party app) then the problem doesn't arise at all.
This IS a bug in iPhoto IMHO and there should have been a warning that you could lose all your original organization when doing a destructive "Import" and a warning that you will become locked into iPhoto without making tedious exports and renaming.
So, no bug, no need of a warning, no lock into iPhoto.
The problem with ignorance, as someone once said, is that it gains confidence as it goes along. And so, to your misunderstanding of how this forum works.
What these cryptic mods
Cryptic? Mods? No one posting here is a Moderator. We're all just iPhoto users. This is explained clearly in the Terms of Use you agreed to when you signed up to the forum. Read them sometime.
...is that your original photo metadata is still in the photo,
Oh but it is... see that whole Exif metadata thing above...
you need some third party program to read it.
No. For a start, on your Mac, iPhoto and Preview will read it. Whatever software came with your camera will read it.
Apple made NEW file dates when it imported them.
Yes. But as explained above, the photo date is not the fie date.
Regards
TD

Export/import with objects in another schema

In 9.2
I created two users: `live` and `world`
`live`> create type nam as object (txt varchar2) not final;
`system`> grant under any type to world;
`world`> create type nam_world under live.nam (txt2 varchar2);
and
create table nams of nam_world;
and new row
insert into nams values ('qwerty', 'ytrewq');
I build dump file:
exp system/manager FILE=live_world.dmp OWNER=live,world
All this successfully!!!
At another server (also 9.2) this export session terminated with errors:
imp SYSTEM/manager FILE=live_world.dmp FROMUSER=live,world TOUSER=live,world
Not help parameter IGNORE=Y
Not help parameter TOID_NOVALIDATE=(live.nam)
In any case: "Skipping table "WORLD"."NAMS" because object type "LIVE"."NAM" cannot be created or has different identifier"
General effect, what import simply not visible type live.nam
How import tables with objects in another users schema?
Please, help me.

Hi Vishwanath,
You can export the objects as TPZ's
go to Tools---> Export configuration objects, to export them, and import configuration objects to reimport them.
cheers
Prashanth

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

LSMW of runs with a mandator export/- import

At present we migrate our system landscape of SAP the releases 4.6C on mySAPERP2005. Before the migration of the quality assurance system (FQ2) we imported here in the mandator 151 a mandator export of the productive mandator (FP2 system/mandator 150) with the profile SAP_ALL. Shortly thereafter the Upgrade on mySAPERP2005 was then accomplished. The specialized divisions announce now that the defined LSMW of runs differs in the FQ2 system from the FP2 system (production) and/or still the conditions before the mandator import has. It looks apparent in such a way, as if the runs and/or the definition those does not stand behind it at all was copied. Does the LSMW become runs with a mandator export/- import with copies? How can we examine that?

Hi,
Are you running the report for all the selections(all the data )?
execute the report with data selection and check?
Is the data in the Ic - compressed?
Regards
KP

Issues with Export/Import using Database & Shared buffer

Hi All,
I have a method that calls a program via a job and I am having issues passing data between the two.
Note that two different users process the method and program (via job) resp. This is how I am calling the second prog-
SUBMIT ZPROGRAM
             VIA JOB     l_jobname
                 NUMBER l_jobcount
                 USER    i_user
             AND RETURN.
I need to pass data from method to the second program and vice versa and then the method continues its processing with the data acquired from the second program.
I have tried using Import/Export using database and also shared buffer. What I have found is that most of the times I am able to pass data from method to program. However the job takes a couple of min to execute and I think that the data is not making back to the method in time.
I have looked at some useful forum links-
Problem with export/import in back ground
Re: EXPORT/IMPORT to MEMORY
but havent been able to find an answer yet. Any solution? Thanks in advance for your help!
Liz

Hi Suhas, Subhankar
I have tested the scenario without the job previously itself and it works. Thats the reason, i am trying with the job now as my requirement is that I need to change the user while executing the second report.
Here is an example of my import/export - I am passing the return value from the second report to the first.
Code in second report-
DATA: INDXKEY LIKE INDX-SRTFD VALUE 'RET1'.
INDX-AEDAT = SY-DATUM.
INDX-USERA = SY-UNAME.
EXPORT RETURN1 TO SHARED BUFFER INDX(ST) ID INDXKEY.
Code in first report -
SUBMIT ZPROGRAM
                 VIA JOB     l_jobname
                     NUMBER l_jobcount
                     USER    i_user
                 AND RETURN.
Once Job close FM is executed successfully, I import the values as follows
IMPORT RETURN1 TO RETURN1 FROM SHARED BUFFER INDX(ST) ID INDXKEY3.
INDXKEY is having value RET1.
However Return1 is not having any values in first report. It has some value in executed without the job
Please note that I have tried Export/import with Database too and I am getting the same results.
Thanks for your suggestions.
Regards, Liz

Export/Import help required

Anybody guide me, my scenario is as under:
1.     I have database FESCO in oracle 9i on Windows 2000.
2.     Client has taken dump of schema through Export command with FULL= N.
Exp fesco/password@fesco owner=fesco file=fesco_fullbkp.dmp Full=N
3.     Now I want to know before importing from this dump file, what should I do on existing database, either I have to drop this user, which is containing the data or any other steps required

>>yes i wana to import it on the same server, this dump was taken 2 days back and nowa i wana to import it.
If assumed that import will be on the same database and on the same server,
1) Drop the user first (For safe side, take the export of this user before droping).
2) create the user again and assing the same tablespace as default tablespace how it was earlier, and grant the privileges.
3) use the import command.
imp fesco/password@fesco fromuser=fesco touser=fesco file=fesco_fullbkp.dmp log=fesco_fullbkp_imp.log
Regards,
Sabdar Syed

Export ,import efficiency

Hi,
I have a basic question here. Which is more efficient exp/imp or the expdp/impdp and why? I would like to read about it. good documents are welcomed.
Thanks
Kris

Hi ,
Definetly expdp/impdp(Datapump export import) is much better than original exp/imp which is more
used in oracle 9i Databases.
Top 10 difference between exp/imp(export/import) and expdp/impdp(Datapump export and import) are:
1)Data Pump Export and Import operate on a group of files called a dump file set
rather than on a single sequential dump file.
2)Data Pump Export and Import access files on the server rather than on the client.
This results in improved performance. It also means that directory objects are
required when you specify file locations.
3)The Data Pump Export and Import modes operate symmetrically, whereas original
export and import did not always exhibit this behavior.
For example, suppose you perform an export with FULL=Y, followed by an import using SCHEMAS=HR. This will produce the same results as if you performed an
export with SCHEMAS=HR, followed by an import with FULL=Y.
4)Data Pump Export and Import use parallel execution rather than a single stream of
execution, for improved performance. This means that the order of data within
dump file sets and the information in the log files is more variable.
5)Data Pump Export and Import represent metadata in the dump file set as XML
documents rather than as DDL commands. This provides improved flexibility for
transforming the metadata at import time.
6)Data Pump Export and Import are self-tuning utilities. Tuning parameters that
were used in original Export and Import, such as BUFFER and RECORDLENGTH,
are neither required nor supported by Data Pump Export and Import.
7)At import time there is no option to perform interim commits during the
restoration of a partition. This was provided by the COMMIT parameter in original
Import.
8)There is no option to merge extents when you re-create tables. In original Import,
this was provided by the COMPRESS parameter. Instead, extents are reallocated
according to storage parameters for the target table.
9)Sequential media, such as tapes and pipes, are not supported.
10)The Data Pump method for moving data between different database versions is
different than the method used by original Export/Import. With original Export,
you had to run an older version of Export (exp) to produce a dump file that was
compatible with an older database version. With Data Pump, you can use the
current Export (expdp) version and simply use the VERSION parameter to specify the target database version
For more details and options:
exp help=y
imp help=y
expdp help=y
impdp help=y
Fine manuals for referring:
http://www.oracle-base.com/articles/10g/OracleDataPump10g.php
Hope it helps.
Best regards,
Rafi.
http://rafioracledba.blogspot.com

Export / Import with FULL=Y

Similar Messages

Maybe you are looking for