Oracle FAQ | Your Portal to the Oracle Knowledge Grid |
Home -> Community -> Usenet -> c.d.o.server -> Re: Full Ex/Im-port to New Instance, NT
Oracle Corporation Support
Microsoft Servers and Utilities Technical Forum.
Displayed below are the messages of the selected thread.
From: Charles Cooper
Subject: Export/Import problem with Oracle 7.3 and Win NT 4.0
Posted on: 12-Feb-1998 07:35:47
RDBMS Version: 7.3.3
Error Number (if applicable):
Operating System and Version: Windows NT 4.0
Tool (i.e. SQL*Loader, Import, etc.): Export/Import
Tool Version: 7.3
I am moving a PeopleSoft Financial database from one machine to another using a full export of the database and reorganising tablespaces etc. during the process. I have created the database instance and all the new tablespaces on the destination machine in their new locations. However, despite using FULL=Y on the export, when I run the full import, the user SYSADM does not get created and thus all PeopleSoft objects fail to import (since this is the schema in which they reside). Am I doing something wrong? Is there a limitation of export that I'm hitting?
Thanks for any help.
Charles
From: Mark Harper
Subject: Re : Export/Import problem with Oracle 7.3 and Win NT 4.0
Posted on: 12-Feb-1998 12:35:28
I think there are a few questions which come to
mind.
Try to answer these questions or perhaps pass on some of these details, if you wish.
From: Charles Cooper
Subject: Re : Export/Import problem with Oracle 7.3 and Win NT 4.0
Posted on: 13-Feb-1998 10:59:47
Thanks for the response. In answer to your questions:
1. The tablespaces in the new database are identically named, but are larger
and in some cases on different drives
2. The export was performed by SYS 3. The export was indeed of the full database (FULL=Y) 4. The LOG file tells me everything was OK (Export terminated successfullywithout warnings).
I appreciate any help you can give.
From: Bill Prendergast
Subject: Re : Export/Import problem with Oracle 7.3 and Win NT 4.0
Posted on: 16-Feb-1998 09:58:43
The log file should show all the Schema and the
tables within the schemas that were imported. What
does it show for the SYSADM schema?
If it does not show any tables for this schema, please let me know what the complete command lines are for you export and import.
Bill Prendergast
Oracle Support
From: Charles Cooper
Subject: Re : Export/Import problem with Oracle 7.3 and Win NT 4.0
Posted on: 16-Feb-1998 11:05:26
No, all objects for this schema fail on import
because the user does not exist (even though
export was done with FULL=Y and import was done
with FULL=Y. The parameter files used are blow:
FULLEXP.PAR:
FILE = FULLEXP.DMP
LOG = FULLEXP.LOG
BUFFER = 1048576
FULL = Y
CONSISTENT = Y
CONSTRAINTS = Y
GRANTS = Y
INDEXES = Y
ROWS = Y
COMPRESS = Y
STATISTICS = NONE
FULLIMP.PAR:
FILE = FULLEXP.DMP
LOG = FULLIMP.LOG
BUFFER = 1048576
FULL = Y
GRANTS = Y
INDEXES = Y
ROWS = Y
COMMIT = Y
DESTROY = N
Thanks for your help.
Charles
From: Bill Prendergast
Subject: Re : Export/Import problem with Oracle 7.3 and Win NT 4.0
Posted on: 16-Feb-1998 14:27:41
Does the SYSADM Schema show up in the export log?
If not, let's try the following:
exp73 sysadm/password_at_db file=sysadm.dmp log=sysadm.log buffer = 1048576
This should give you an export of the SYSADM schema.
Bill Prendergast
Oracle Support
From: Charles Cooper
Subject: Re : Export/Import problem with Oracle 7.3 and Win NT 4.0
Posted on: 17-Feb-1998 07:46:09
Yes - all SYSADM's objects are in the export, the
problem is that the CREATE USER statement for
SYSADM doesn't get into the export, so on import
into the new, empty, database all of SYSADMs
objects fail because the user doesn't exist.
I had to get the import done, so I created the userid and then ran the import. It worked OK - the only failures were for creates of objects that already existed, which I expected anyhow.
I still want to understand why it didn't work correctly though - it seems to be an export bug to me (doesn't add a CREATE USER statement to the export for any userids beginning SYS?).
Thanks, Charles.
From: Bill Prendergast
Subject: Re : Export/Import problem with Oracle 7.3 and Win NT 4.0
Posted on: 17-Feb-1998 08:48:31
This is really strange! Have you verified that the
create user statement does not exist. You can open
up the dump file in WORDPAD and examine it. If the
file is too large, you can re-export the database
with ROWS=NO to get a smaller file.
I have recently worked with some Peoplesoft databases where the schema was SYSADM and have done what you are trying to do several times. What is the exact version of the database you are using. I have tried reproducing it here with versions 7.3.4.0 and 8.0.4.0 and each time it exported the SYSADM user.
Bill Prendergast
Oracle Support
From: Charles Cooper
Subject: Re : Export/Import problem with Oracle 7.3 and Win NT 4.0
Posted on: 19-Feb-1998 10:07:18
Sorry this took a while to get back to you.
Interestingly, when I look in the export file the
CREATE USER statement for SYSADM is indeed
present. I'm going to try creating an empty
database again and re-importing to ensure that I'm
not going insane (that the problem really did
happen!). The version of Oracle I'm using is
7.3.3.0.0 with utilities version 7.3.3.0.0. We
have installed no patches etc., it's straight from
the CD-ROM.
From: Bill Prendergast
Subject: Re : Export/Import problem with Oracle 7.3 and Win NT 4.0
Posted on: 23-Feb-1998 11:41:28
When you retry it, check the import log file to see
if the create user gives an error.
Bill Prendergast
Oracle Support
From: Charles Cooper
Subject: Re : Export/Import problem with Oracle 7.3 and Win NT 4.0
Posted on: 27-Feb-1998 08:45:54
Sorry it took a while again - no, nothing in the
import log, just failed to do it. If I have time,
I'll play with it and see if I can come up with a
simple test case that causes the problem.
Thanks, Charles.
begin 666 Yassir Khogaly.vcf
M0D5'24XZ5D-!4D0-"E9%4E-)3TXZ,BXQ#0I..DMH;V=A;'D[66%S<VER#0I&
M3CI987-S:7(@2VAO9V%L>0T*3U)'.D%%154-"E1)5$Q%.E-E;FEO<B!/<F%C
M;&4_at_1$)!#0I414P[2$]-13M63TE#13HK-#0H,"DQ.#$@-#8P-# T,@T*5$5,
M.T-%3$P[5D])0T4Z*S0T-#$Q.3 V-S<V#0I!1%([2$]-13M%3D-/1$E.1SU1
M54]4140M4%))3E1!0DQ%.CL[1FQA=" Y/3!$/3!!,3D_at_4V]U=&AL86YD)W,@
M1W)O=F4],$0],$$[0FEC:VQE>3M+96YT.T)2,2 R1$$[16YG;&%N9 T*3$%"
M14P[2$]-13M%3D-/1$E.1SU154]4140M4%))3E1!0DQ%.D9L870@.3TP1#TP
M03$Y(%-O=71H;&%N9"=S($=R;W9E/3!$/3!!/3!$/3!!0FEC:VQE>2P_at_2V5N
M="!"4C$@,D1!/3!$/3!!16YG;&$]#0IN9 T*55),.FAT=' Z+R]W=W<N:VAO
M9V%L>2YF<F5E<V5R=F4N8V\N=6L-"E523#IH='1P.B\O=W=W+F%E974N;W)G
M+G5K#0I%34%)3#M04D5&.TE.5$523D54.GEA<W-I<D!K:&]G86QY+F9R965S
M97)V92YC;RYU:PT*4D56.C$Y.3_at_Q,#$R5# W,3<T,UH-"D5.1#I60T%21 T*
`
end
Received on Mon Oct 12 1998 - 02:17:43 CDT