Imp full db successful with warnings

Question

Looking for options to fix those , or can i ignore them? What would be side effect if i drop/cascade users and re-run imp after increasing tablespace TS_PUBLIC size or i should not do that? and just fix the little warnings or even just ignore them?
Most of tables (i would say 95% ) & there data imported successfully after full imp , db size is 80GB around, import terminated successfully with warnings , which are below.....
IMP-00017: following statement failed with ORACLE error 1659:
"CREATE TABLE "CA_QUERY_1"
"ABLESPACE "TS_PUBLIC""
IMP-00041: Warning: object created with compilation warnings
"CREATE FORCE VIEW "ADMIN"."CHECK_EXTENTS_V"
IMP-00041: Warning: object created with compilation warnings
"CREATE TRIGGER MT1758.MEDDRA_MT1758_THE_SYN_UPD"

Answer 1

DBA2011 wrote:
Looking for options to fix those , or can i ignore them? What would be side effect if i drop/cascade users and re-run imp after increasing tablespace TS_PUBLIC size or i should not do that? and just fix the little warnings or even just ignore them?
Most of tables (i would say 95% ) & there data imported successfully after full imp , db size is 80GB around, import terminated successfully with warnings , which are below.....
IMP-00017: following statement failed with ORACLE error 1659:
"CREATE TABLE "CA_QUERY_1"
"ABLESPACE "TS_PUBLIC""
IMP-00041: Warning: object created with compilation warnings
"CREATE FORCE VIEW "ADMIN"."CHECK_EXTENTS_V"
IMP-00041: Warning: object created with compilation warnings
"CREATE TRIGGER MT1758.MEDDRA_MT1758_THE_SYN_UPD"; I would suggest you to look at export log and find out which are the tables that got failed and import only those tables again. Since the size is quite high as you said.
Secondly, since 95% tables are already import, so i suggest you to increase the Tablespace size by adding datafile or extending existing one, then run the import for rest 5% tables.
Third, You said can you ignore warning? During import oracle tries to create Views, it first check if the tables from which view is being create are already exists or not. If the tables doesn't exists oracle will create view forcefully, and mark these view as invalid. The only way to make the views valid is to alter the views definition to point to the correct base tables.
So there is little activity left after import is done with warning, that you have to alter the view definitions so that correct tables can be used.
Also see MOS -> IMP-00041 ORA-04063 FROMUSER/TOUSER IMPORT INTO NEW DATABASE [ID 1059520.6]
Hope my suggestions helps you