| Oracle FAQ | Your Portal to the Oracle Knowledge Grid | |
 |
 | |||
| Oracle FAQ | Your Portal to the Oracle Knowledge Grid | |
|
| |||
Home -> Community -> Mailing Lists -> Oracle-L -> RE: EXPORT BUG: oncorrect storage parameters being produced RESOLVED new bug
Hi,
Check out Bug 1575222 in metalink (someone sent it to me).
Exact bug. Suppoesedly fised in 8.1.7.2
-----Original Message-----
From: Patricia Karla Cordeiro <pcordeiro@usiminas.com.br>@SUNGARD
Sent: Friday, June 07, 2002 2:55 PM
To: LazyDBA.com Discussion
Subject: RE: EXPORT BUG: oncorrect storage parameters being produced Bug :617486
Hi,
Not sure if it helps, but if the object ACCOUNT already exists, on another
schema, isn't it possible that you have a public synonym for this object (on
the old schema), and imp is trying to create the PK on the wrong object?
Try running IMP with same USER as TOUSER clause.
HTH,
Patricia.
-----Original Message-----
From: johanna.doran@sungard.com [mailto:johanna.doran@sungard.com]
Sent: Sexta-feira, 7 de Junho de 2002 15:10
To: LazyDBA.com Discussion
Subject: EXPORT BUG: oncorrect storage parameters being produced
Bug:617486
I posted earlier and someone responded that this was a bug prior to 8.1.7
Please note that error occurs ONLY with the constraints.... tables etc are
all created without error. If I strip the tablespace params out of the
statement and THEN run the statement, I get no errors.
I had the departmental dba re-run the export using the exp version that
comes with 8.1.7 and we still are getting the same error on import
IMP-00015: following statement failed because the object already exists:
"ALTER TABLE "ACCOUNT" ADD CONSTRAINT "PK_ACCOUNT" PRIMARY KEY
("ACCOUNT_ID"
"","GENERATION") USING INDEX PCTFREE 10 INITRANS 2 MAXTRANS 255
STORAGE(INIT"
"IAL 8388608) TABLESPACE "AURDEV_TS" ENABLE "
Furthermore, I believe that the error message itself is incorrect.
Here's the setup.
The schema that the export was run on has default tbs of AURDEV_TS
The schema I am trying to import into has default tbs of Users
Both schemas in same Oracle instance.
I dont know if it is looking to try to create the object in the other tbs as
written, but the import users has no rights to that tbs. The object DOES
indeed exist in the tbs but under a different schema.
I found an OLDer bug as follows:
Bug:617486 caused exports to contain invalid DDL for storage clauses. This
fix allow IMPort to IGNORE the ORA-2219 error if the table already exists
providing a way to import any EXPORT generated with a version of EXP
suffering from Bug:617486
Similar but older version and different error message though similar
behavior.
But we are on 8.1.7 and should not see this.
Any comments? (I have no access to metalink)
Thanks,
Hannah
--------
Oracle documentation is here:
http://tahiti.oracle.com/pls/tahiti/tahiti.homepage
To unsubscribe: send a blank email to oracledba-unsubscribe@LAZYDBA.com
To subscribe: send a blank email to oracledba-subscribe@LAZYDBA.com
Visit the list archive: http://www.LAZYDBA.com/odbareadmail.pl
Tell yer mates about http://www.farAwayJobs.com
By using this list you agree to these
terms:http://www.lazydba.com/legal.html
--------
Oracle documentation is here: http://tahiti.oracle.com/pls/tahiti/tahiti.homepage
To unsubscribe: send a blank email to oracledba-unsubscribe@LAZYDBA.com
To subscribe: send a blank email to oracledba-subscribe@LAZYDBA.com
Visit the list archive: http://www.LAZYDBA.com/odbareadmail.pl
Tell yer mates about http://www.farAwayJobs.com
By using this list you agree to these terms:http://www.lazydba.com/legal.html
 |
 |