RE: error when importing dump imp-00058 ora-06550 pls-00302

  • From: "Goulet, Richard" <Richard.Goulet@xxxxxxxxxxx>
  • To: <grlongo.ireland@xxxxxxxxx>, <oracle-l@xxxxxxxxxxxxx>
  • Date: Tue, 7 Dec 2010 17:24:59 -0500

 
According to what I've done in the past the TABLESPACES parameter
applies only to transportable tablespaces.  Now data pump does have a
tablespace filter.

Dick Goulet 
Senior Oracle DBA 

 

________________________________

From: oracle-l-bounce@xxxxxxxxxxxxx
[mailto:oracle-l-bounce@xxxxxxxxxxxxx] On Behalf Of Guilherme Raymo
Longo
Sent: Tuesday, December 07, 2010 2:54 PM
To: oracle-l@xxxxxxxxxxxxx
Subject: Re: error when importing dump imp-00058 ora-06550 pls-00302


Just one question that arose was do I or I do not need to specifies the
tablespace when importing?  


On Tue, Dec 7, 2010 at 5:51 PM, Guilherme Raymo Longo
<grlongo.ireland@xxxxxxxxx> wrote:


        Ok mates, 
        
        end of the day and the DBA just called to tell me the good news.
        The erros was in the command I was issuing to import the db
        
        I was issuing:
        imp system/oracle@tcp file=f:\bkp.dmp log=f:\bkp_imp.log
fromuser=tcp touser=tcp tablespaces=dados
        
        IMP SYSTEM/ORACLE FILE=f:\BKP.DMP  FROMUSER=TCP  TOUSER=TCP
LOG=f:\BKP_IMPORT.LOG  BUFFER=100000
        
        The only thing I had to remove was the tablespaces parameter. I
found it strange since I used to import with this command.
        
        Well, problem solved!
        

        On Mon, Dec 6, 2010 at 10:14 PM, Guilherme Raymo Longo
<grlongo.ireland@xxxxxxxxx> wrote:
        

                Hi mates,  

                I am having a hard time with something that should be
simple task.
                It's a error with the imp tool

                I have the following cenario:

                Source -> windows 2000 server / Oracle 9i / Client 9i 
                Destination -> Windows 2008 server / Oracle 11g /
Cliente 11g

                The error is the following:

                http://yfrog.com/75oraclep

                I thought i should export with a newer client so I tried
with the 10g client as well but at this time even the export had the
same behavior and thrown the error.
                I can do nothing anymore since I had to send the
computer to a DBA to fix the problem, but it is killing me that a had no
time to try it myself. 

                Do you guys could you please gimme a hint why oracle is
complaining??

                Regards.



Other related posts: