ORA-01435: user does not exist when using imp utility

Question

I installed Oracle 8.1.7.0.0 successfully on WINDOWS 2000 and created a database TEST using DBCA. Then I used a script to creat a tablespace and a user in TEST databse. I could use the imp utility to import the data (a dmp file) to the TEST database without any problem. But after I applied a patch to bring up the version to Oracle 8.1.7.4.1, I got the following error when I tried to use the imp utility again to import the data (a dmp file) to the TEST database.
IMP-00003: ORACLE error 1435 encountered
ORA-01435: user does not exist
IMP-00000: Import terminated unsuccessfully
I checked that I created the same user test (as it is in dmp file I wanted to import) on TEST, and I could login to TEST using:
sqlplus test/test@TEST
The command I used is:
imp system/password@TEST file=test.dmp full=y log=importTEST.TEST.tmp
I also tried to use the following command:
imp system/password@TEST file=test.dmp fromuser=test touser=test log=importTEST.TEST.tmp
and got the same error as before.
Anyone has any clues what could go wrong? The only difference for me to import the data on TEST is that the
previous successful import was done in Oracle 8.1.7.0.0.
Is it possible that I missed something during the applying of the patch 8.1.7.4.1?
Thanks, and your help is greatly appreciated.
Jane

Answer 1

Ther is a set of instruction to be followed after installing the patch set 8.1.7.4.1 after running it thru OUI.They are as follows. Please complete these steps and u should not have problems any more.
When applying this patchset on Windows NT and Windows 2000, you must log onto the system as a user with Administrative privileges (e.g., as a user which is a member of the local Administrators group).
1.Disabling system triggers.
Before performing the next step, you must first set SYSTEMTRIG_ENABLED = FALSE in the initialization parameter file. To do this add the following line to your init<sid>.ora file and restart the database (see Note 149948.1 in Metalink for more information on this issue).
systemtrig_enabled=false
2.Invoke SQL*Plus (sqlplus), connect as internal and run the following:
select * from duc$ where PACK='JIS$INTERCEPTOR$' ;
If no rows were returned go to the next step. If a row was returned delete it using the following:
delete from duc$ where PACK='JIS$INTERCEPTOR$' ;
commit;
3.Invoke SQL*Plus (sqlplus), connect as internal and run the following SQL scripts with event 10520 set. NOTE: This event is not intended for regular database operation and when turned on below by the 'ALTER SESSION' command will automatically be turned off by the subsequent 'CONNECT' command.
ALTER SESSION SET EVENTS '10520 TRACE NAME CONTEXT FOREVER, LEVEL 10';
?/rdbms/admin/catalog.sql
?/rdbms/admin/catproc.sql
?/rdbms/admin/catrep.sql (This only needs to be run if you are using symmetric/advanced replication. This is not necessary for sites using dblinks and read-only snapshots if symmetric/advanced replication is not installed)
CONNECT / AS SYSDBA;
update obj$ set status=5 where type#=29 and owner#!=0;
commit;
4.You can ignore this step if you have already executed it as part of a previous 8.1.7 patch set install.
If Java has previously been loaded into the database, invoke SQL*Plus (sqlplus), connect as internal and run the following SQL DDL command(* Note:If Java has not previously been loaded into the database, skip this step).:
SQL> create or replace java system
2 /
(Note that the / (slash) is important to ensure the execution of the command).
To ensure the correct installation of the XDK in the database run the following 2 scripts (Bug 2115227):
$ORACLE_HOME/oracore/admin/initxml.sql
$ORACLE_HOME/rdbms/admin/catxsu.sql
* To determine whether Java has previously been loaded into the database:
invoke SQL*Plus (sqlplus), connect as internal and run the following:
SQL> select count(*) from all_objects where object_type like 'JAVA%';
Java is installed if you get a non zero result returned from the query.
5.You can ignore this step if you have already executed it as part of a previous 8.1.7 patch set install:
If Java has previously been loaded into the database, invoke SQL*Plus (sqlplus), connect as internal and run the following scripts which are located in $ORACLE_HOME/javavm/install ( Note: If Java has not previously been loaded into the database, you can skip this step):
load_jis.sql
jisja.sql
initjsp.sql
jspja.sql
Notes:
When running the $ORACLE_HOME/javavm/install/jisja.sql script the following error may be reported and can be ignored:
call jis_exit_java_session(0)
ERROR at line 1:
ORA-29515: exit called from Java code with status 0
Bug 1459233 was filed against this problem which is fixed in 9i.
6.If you deleted a row from duc$ in step 8 then reinsert it again. Invoke SQL*Plus (sqlplus), connect as internal and run the following SQL:
insert into duc$ (OWNER, PACK, PROC, FIELD1, OPERATION#, SEQ) values ('SYS', 'JIS$INTERCEPTOR$', 'USER_DROPPED', 0, 1, 1);
commit;
7.Enabling system triggers.
You must either remove SYSTEMTRIG_ENABLED from the initialization parameter file or explicitly set it to TRUE before attempting any other patch set post-install steps. Restart the database.
8.This step is optional - it will recompile all invalid PL/SQL packages now rather than when accessed for the first time - you can also use utlrcmp.sql to parallelize this. Invoke SQL*Plus (sqlplus), connect as internal and run the following SQL script:
?/rdbms/admin/utlrp.sql
9.Execute the following steps only if you have installed Oracle interMedia Text in the database you are attempting to modify:
If you have not previously unlocked the ctxsys account and supplied a password for that account, you need to do so. (If you have needed to use Oracle Text in any way prior to applying the patchset, you will have already performed this step, and you can skip this.) Do so by issuing the following statement:
ALTER USER ctxsys IDENTIFIED BY <passwd> ACCOUNT UNLOCK;
If you have already installed 8.1.7.2 or 8.1.7.3, go directly to step 7 below.
If you have already installed 8.1.7.1, go directly to step 5 below.
CONNECT ctxsys/<passwd>;
@?/ctx/admin/upgrade/u0801071.sql
CONNECT ctxsys/<passwd>;
@?/ctx/admin/upgrade/u0801072.sql
CONNECT / AS SYSDBA;
@?/ctx/admin/upgrade/s0801074.sql
CONNECT ctxsys/<passwd>
@?/ctx/admin/dr0pkh.sql
@?/ctx/admin/dr0plb.sql
@?/ctx/admin/dr0type.plb
@?/ctx/admin/dr0typec.plb
9.You can ignore this step if you have already executed it as part of a previous 8.1.7 patch set install:
The installation of this patch set fixes a potential security hole in the XSQL Servlet - see here for more detail. The patchset installation does not, however, modify any of the Oracle HTTP Server configuration files to reflect changes to the XSQL Servlet installation. If you have previously installed the Oracle HTTP Server, you will need to update one of the configuration files manually after the patchset installation is complete. If you do not do so, the XSQL Servlet may not work in the context of the Oracle HTTP Server after the patchset is installed. To update your Oracle HTTP Server configuration, perform the following steps:
1) Edit the file: $ORACLE_HOME/Apache/Jserv/conf/jserv.properties
2) Search for the string: "XSQLConfig.xml File location"
3) Modify the parameter wrapper.classpath on the line immediately following the above string to read: $ORACLE_HOME/oracore/admin
4) Save the file.
10.You can ignore this step if you have already executed it as part of a previous 8.1.7 patch set install:
The installation of this patch set fixes a potential security hole in the PL/SQL XML parser - see here for more detail. To load the new XML parser in to the database, run the following script as user SYS:
? /xdk/plsql/parser/bin/load.sql
11.If you are using the RMAN catalog then upgrade it as follows:
rman catalog <user/passwd@alias>
upgrade catalog;
upgrade catalog;
The post install actions are now complete and the database is now ready for use.