Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations SkipVought on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Imp errors on 8.0.5.1 on HPUX 10.20? 1

Status
Not open for further replies.
Jun 15, 1999
3
0
0
US
I have been having doing a full import into an Oracle 8.0.5.1 instance The following is the error I've been getting: <br>
<br>
ORA-04030: out of process memory when trying to allocate 24 bytes (callheap,temporary memory)<br>
<br>
I've tried playing around with the buffer size to no avail.<br>
<br>
Oracle says it's an OS problem, but we've used the same account for the exact database in oracle7, and never had any problems???<br>
<br>
Any help appreciated!
 
My first reaction would be to check how much swap space you have allocated.<br>
<br>
I've only ever got "out of memory" errors on unix boxes when there's insufficient swap (paging) space allocated.<br>
<br>
This wouldn't be inconsistent with your experiences with Oracle7 as I'm sure Ora8 uses memory in a different way to Ora7.<br>
<br>
There's a way to check on how much swap is marked as "in use" (I can't remember how...) but it might be interesting to monitor that whilst your imp is running - also - are there hard user or process memory limits configured in the kernel?<br>
<br>
Regards<br>
<br>
Mike<br>

 
I support some Digital Unix systems and I agree with Mike that V8 does require more resources than V7 did so I would check that out first.<br>
<br>
But also, in VMS, not HPUX, so kind of a long shot but...<br>
<br>
If you are importing some procedures...<br>
We have gotten a similar error trying to execute some SQL statements in V8 that worked fine in V7. Turns out that the optimizer was lost in some king of loop when it was parsing the statement and just kept allocating more and more memory until it ran out. The work around was to put a RULE hint into the statement. That worked OK for us because the performance on the query was still OK. This might occur since the procedures are compiled after they are loaded.<br>

 
I would tend to agree with Mike on the lack of swap space. I know that in Linux you can use the 'top' command to see the stats on how much swap space is being used....but I don't know if Top comes with HPUX by default, though you can certainly find it on a GNU ftp site.<br>
<br>
Good luck,<br>
<br>
--Bryan
 
We figured out the problem, and Oracle Support is working on a bug fix.<br>
<br>
The problem was that We were importing the schema, then the data, then the indices as 3 different imports. The failure occured on the data step.<br>
<br>
It turns out that there was a view (a non-SYSTEM view) that became invalid and caused Oracle to go into a loop, and ending with the noted error.<br>
<br>
The work-a-round is to recompile all invalid views before importing the data. This resolved the problem.<br>
<br>
There was a similiar bug found in SUN, Bug # 575214. This bug should be resolved in 8.0.6.<br>
<br>
Thanks for everyones help!
 
Thanks for posting your solution. It's a bit frustrating when you're searching for a problem (because you've got it yourself now) and the problems listed on a help forum -- but not the answer.<br>
<br>
Regards<br>
<br>
Mike<br>

 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top