DBAsupport.com Forums - Powered by vBulletin
Results 1 to 5 of 5
  1. #1
    Join Date
    Nov 2000

    Urgent: IMP-00003: ORACLE error 3114 encountered

    Dear all,

    I am trying to replicate a production database by using import and export utilities. My production database is in Unix HP and the new database is going to be on Windows XP, and both database servers are in Oracle

    The export was done successfully; however I got the following errors during importing:

    IMP-00003: ORACLE error 3113 encountered
    ORA-03113: end-of-file on communication channel
    IMP-00003: ORACLE error 3114 encountered
    ORA-03114: not connected to ORACLE

    The import command is:
    C:\> imp system/pwd file=full.dmp full=y log=full.log buffer=64000
    C:\> imp / file=full.dmp full=y log=full.log buffer=64000

    Prior to the import, I created all the tablespaces; however, none of data from any schema got imported since there was no connection to the database. Also when I tried to login as system, I got invalid password error. I have to alter user in order to login. Can anyone tell me why the system or OS authenticated user password got changed during the import? And how do I prevent from getting the IMP-00003 error?

    Any help is appreciated.


  2. #2
    Join Date
    Jan 2005
    make sure you have you environment path set:

    on windows do:

    export ORACLE_SID=BLUH

    on linux do:

    export ORACLE_SID=bluh

  3. #3
    Join Date
    Nov 2000
    Thanks, but I already have ORACLE_HOME and ORACLE_SID set in environment parameters.

    I can get the data imported if I set the the owner=user; however, we have so many schemas, I don't want to import all these schemas one at a time. Now my problem is there is no connection to the database, since somewhere along the import my password got changed.

  4. #4
    Join Date
    Jan 2005
    Change The Sys Password By Using Orapwd

  5. #5
    Join Date
    Nov 2000
    Thank you all for your help. Using orapwd doesn't prevent the database from disconnecting. However, I found the solution from metalink:

    1. Login as sys in the SQLPLUS and run the following sqls


    2. Retry the import.


Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts

Click Here to Expand Forum to Full Width

We have made updates to our Privacy Policy to reflect the implementation of the General Data Protection Regulation.