I'm running an import on NT to create only the indexes, and upon trying to create a few large indexes, it gives this error. Any ideas??
Printable View
I'm running an import on NT to create only the indexes, and upon trying to create a few large indexes, it gives this error. Any ideas??
Metalink is a good resource for troubleshooting error messages. Apparently there is a bug on 8.0.5 running on HP platforms that can cause this error. I also found the following which might just do the trick for you. Unfortunately, you did not disclose the entire error stack, so I don't know if this really matches what you are seeing or not.
Doc ID: Note:1062162.6
Subject: ORA-4030, IMP-44, IMP-3 WHEN IMPORTING DUMP FILE
Type: PROBLEM
Status: PUBLISHED
Content Type: TEXT/PLAIN
Creation Date: 24-NOV-1998
Last Revision Date: 03-FEB-1999
Problem Description:
====================
You are attempting to import a dump file using the Import utility.
You are getting the following errors:
ORA-4030: out of process memory when trying to allocate %s bytes (%s,%s)
IMP-44: unable to allocate enough memory for statement ""
IMP-3: ORACLE error %lu encountered
Problem Explanation:
====================
You are inadvertantly overloading the Import utility memory buffer.
Search Words:
=============
process recordlength import
Solution: INCREASE THE BUFFER_SIZE PARAMETER IN THE IMPORT STATEMENT TO 1M.
Solution Summary:
=================
Increase the buffer size parameter or increase the recordlength parameter in
the Import statement. Oracle current recommends using the following formula:
buffer = rows in array * recordlength.
Currently, import divides the user-specified buffer size by the max record
length, to determine the number of rows for the array. So, the number of rows
is adjusted according to the amount of memory allocated by the buffer. Note
that the default values for buffer and recordlength vary by operating system.
Solution Description:
=====================
The larger the memory buffer allocated, the less likely that the application
will write out of its memory bounds. Conversely, by accurately determing the
maximum record length and passing the information in as a parameter, the less
likely that import will miscalculate the array size and cause a memory fault.
Solution References:
====================
Oracle8 Release 8.0 Utilities manual. See "Buffer" in "Import Parameters"
section.
.
Copyright (c) 1995,2000 Oracle Corporation. All Rights Reserved. Legal Notices and Terms of
Use.