I am getting errors importing an export...from a client ti my database but also from my database and back in.

I am getting the following error:

. . importing table "ACTION_TRIGGER" 0 rows imported
. . importing table "ACTIVITY" 0 rows imported
IMP-00015: following statement failed because the object already exists:
"ALTER TABLE "ACTIVITY" ADD CONSTRAINT "PK_ACTIVITY" PRIMARY KEY ("ACTIVITY"
"_ID") USING INDEX PCTFREE 10 INITRANS 2 MAXTRANS 255 STORAGE(INITIAL 131072"
" NEXT 131072 MINEXTENTS 1 MAXEXTENTS 4096 PCTINCREASE 0 FREELISTS 1 FREELIS"
"T GROUPS 1 BUFFER_POOL DEFAULT) TABLESPACE "USERS" ENABLE "
. . importing table "ACTIVITY_RESOURCE" 0 rows imported
IMP-00015: following statement failed because the object already exists:
"ALTER TABLE "ACTIVITY_RESOURCE" ADD CONSTRAINT "PK_ACTIVITY_RESOURCE" PRIM"
"ARY KEY ("ACTIVITY_RESOURCE_ID") USING INDEX PCTFREE 10 INITRANS 2 MAXTRANS"
" 255 STORAGE(INITIAL 131072 NEXT 131072 MINEXTENTS 1 MAXEXTENTS 4096 PCTINC"
"REASE 0 FREELISTS 1 FREELIST GROUPS 1 BUFFER_POOL DEFAULT) TABLESPACE "USER"
"S" ENABLE "
. . importing table "AC_HARV_DETAIL_B4_PROPCUT" 1330 rows imported



The weird thing is that I drop and recreated the user (and revoked unlimited tablespace from him) so I am not sure why it bombs while trying to add the pkey?

I did more digging...the tables prior to the one that blows up have primary keys on them and they do not blow up... I did an import with show=y and the tables, indexes and pkeys that succeed are created on the users default tablespace, but the table that blows up is being created on the USERS tablespace...and then the index and pkey is as well and that is where it blows up...WHY I do not know.

Why would a few tables out of a few hundred all of a sudden get created on the USERS tablespace???

Thanks in advance!

Bill