IMP-00031 fromuser touser

import and export from original schema to another dedicated schema. Often, I have no idea what people gave me. I was asking for datapump and what I got was something else with no export log.

imp SRM1/passwordfile=/backup/srmadmin.exp full=n buffer=2000000 commit=y ignore=y log=/backup/srmadmin.log


Import: Release 11.2.0.1.0 - Production on Tue Nov 11 09:23:37 2014
Copyright (c) 1982, 2009, Oracle and/or its affiliates.  All rights reserved.
Connected to: Oracle Database 11g Enterprise Edition Release 11.2.0.1.0 - 64bit Production
With the Partitioning, OLAP, Data Mining and Real Application Testing options
Export file created by EXPORT:V11.02.00 via conventional path
Warning: the objects were exported by SYSTEM, not by you

import done in US7ASCII character set and AL16UTF16 NCHAR character set
import server uses WE8MSWIN1252 character set (possible charset conversion)
export client uses UTF8 character set (possible charset conversion)
export server uses UTF8 NCHAR character set (possible ncharset conversion)
IMP-00031: Must specify FULL=Y or provide FROMUSER/TOUSER or TABLES arguments
IMP-00000: Import terminated unsuccessfully

imp SRM1/password file=/backup/srmadmin.exp full=n buffer=2000000 commit=y ignore=y log=/backup/srmadmin.log fromuser=SRMADMIN touser=SRM1

imp instead of impdp was provided causing ORA-39000

In this case, I was told a "datapump" export file was provided. However, when I performed the datapump import, it failed with ORA-39000. From my best knowledge
only couple things could trigger this error. There are either corrupted datapump import file or user performed an import with "imp" instead of datapump. Datapump file
corruption usually resulted of zip being trimmed during ftp or uploading.


Importing with "impdp" will trigger the following error.


Connected to: Oracle Database 11g Enterprise Edition Release 11.2.0.1.0 - 64bit Production
With the Partitioning, OLAP, Data Mining and Real Application Testing options
ORA-39001: invalid argument value
ORA-39000: bad dump file specification
ORA-39143: dump file "/backup/RD_20140217-2.dmp" may be an original export dump file


imp RDU file=/home/oracle/downloads/CHGPR_20140217.dmp full=n buffer=2000000 commit=y ignore=y log=/home/oracle/downloads/imp_RDU_20140217.log

lsnrctl hung . Unable to start or check on status.

./pcmScheduler|10411|01/25/12 15:24:24|       Raw data: ORA-12514: TNS:listener does not currently know of service requested in connect descriptor

./pcmScheduler|10411|01/25/12 15:24:24|     Error With Sql Return

./pcmScheduler|10411|01/25/12 15:24:24|       Raw data:

./pcmScheduler|10411|01/25/12 15:24:24|     Error With Sql Return

./pcmScheduler|10411|01/25/12 15:24:24|       Raw data:

./pcmScheduler|10411|01/25/12 15:24:24|     Error With Sql Return

./pcmScheduler|10411|01/25/12 15:24:24|       Raw data:       FROM pcm_schedule

./pcmScheduler|10411|01/25/12 15:24:24|     Error With Sql Return

./pcmScheduler|10411|01/25/12 15:24:24|       Raw data:            *

./pcmScheduler|10411|01/25/12 15:24:24|     Error With Sql Return

./pcmScheduler|10411|01/25/12 15:24:24|       Raw data: ERROR at line 2:

./pcmScheduler|10411|01/25/12 15:24:24|     Error With Sql Return

./pcmScheduler|10411|01/25/12 15:24:24|       Raw data: ORA-12514: TNS:listener does not currently know of service requested in connect descriptor

./pcmScheduler|10411|01/25/12 15:24:24|     Error With Sql Return

./pcmScheduler|10411|01/25/12 15:24:24|       Raw data:

./pcmScheduler|10411|01/25/12 15:24:24|     Error With Sql Return

./pcmScheduler|10411|01/25/12 15:24:24|       Raw data:

./pcmScheduler|10411|01/25/12 15:24:25|     Error With Sql Return

./pcmScheduler|10411|01/25/12 15:24:25|       Raw data:       FROM pcm_schedule

acshc:ccuser[live]/u/ccuser 104> lsnrctl status

LSNRCTL for HPUX: Version 10.1.0.5.0 - Production on 25-JAN-2012 15:16:32

Copyright (c) 1991, 2004, Oracle.  All rights reserved.

Connecting to (DESCRIPTION=(ADDRESS=(PROTOCOL=IPC)(KEY=EXTPROC1)))

...hang indefinitely right here ... It turns out, 2 listeners of the same name were running. Not sure how that's possible but it does. Killed both and restarted the lsnrctl .. everything worked fine.