Strange memory error during import ...
zigz...@yahoo.com
tables have been imported,
I get following emmory errors. I have seen it in 2 different database
instances. No clue, why this error
Occurs.
sh: 3127 Memory fault
sh: 3300 Memory fault
sh: 3441 Memory fault
sh: 3471 Memory fault
sh: 3528 Memory fault
sh: 3531 Memory fault
sh: 3535 Memory fault
Michael Austin
ensure your shared memory segements are set correctly to support your
database:
shmmax
The maximum size, in bytes, of a single shared memory segment. For best
performance, it should be large enough to hold the entire SGA.
shmmin
The minimum size, in bytes, of a single shared memory segment.
shmseg
The maximum number of shared memory segments that can be attached (i.e.
used) by a single process.
shmmni
This determines how many shared memory segments can be on the system.
shmmns
The amount of shared memory that can be allocated system-wide.
either that or your system has a DIMM going bad...
johnb...@sbcglobal.net
Check with your unix system admin and start double checking all your
hpux kernel memory settings.
Could be hardware problems or you got some configuration issues.
10.2.0.3 had more than it's share of problems on hpux any specific
reason you are sitting on 10.2.0.3 versus 10.2.0.4?
zigz...@yahoo.com
I noticed that after these errors rest of the import is successful, os
I was thinking that something is corrupted in exort file,
but same error is happening in different db instances, so it seems
like some OS problem. Import used to be successful (no errors like
this) in the past, that's what is puzzling.
Mladen Gogala
Because your script is screwed up and your shell is dying. How bright
do you have to be to use the -x flag and debug a little?
zigz...@yahoo.com
wrote:
My script is so simple, it is a simple imp statement.., full import
(full=Y). During imp, user1 is impoted (all tables,,, towards the end
when it comes to view stored procedure..., this error occurs, but
subsequenet users user2, user3 etc get imported successfuly. set -x
will not provide any useful information.
johnb...@sbcglobal.net
snip
> > > I am on Oracle 10.2.0.3 on HP UNXI 11. When doing import after all
> > > tables have been imported,
> > > I get following emmory errors. I have seen it in 2 different database
> > > instances. No clue, why this error
> > > Occurs.
> > > sh: 3127 Memory fault
> > > sh: 3300 Memory fault
> > > sh: 3441 Memory fault
> > > sh: 3471 Memory fault
> > > sh: 3528 Memory fault
> > > sh: 3531 Memory fault
> > > sh: 3535 Memory fault
>
> > Because your script is screwed up and your shell is dying. How bright
> > do you have to be to use the -x flag and debug a little?
>
> > --http://mgogala.freehostia.com
>
> My script is so simple, it is a simple imp statement.., full import
> (full=Y). During imp, user1 is impoted (all tables,,, towards the end
> when it comes to view stored procedure..., this error occurs, but
> subsequenet users user2, user3 etc get imported successfuly. set -x
> will not provide any useful information.
You have something wrong probably with either the hardware ... your
unix memory configuration ( my guess ) ... or your oracle software ...
or your operating system software ...
Start eliminating them one by one .... keep us posted.
joel garry
> On May 11, 3:53 am, Mladen Gogala <gogala.mla...@bogus.email.com>
> wrote:
>
>
>
>
>
> > Na Sat, 09 May 2009 12:20:53 -0700, zigzagdna napisao:
>
> > > I am on Oracle 10.2.0.3 on HP UNXI 11. When doing import after all
> > > tables have been imported,
> > > I get following emmory errors. I have seen it in 2 different database
> > > instances. No clue, why this error
> > > Occurs.
> > > sh: 3127 Memory fault
> > > sh: 3300 Memory fault
> > > sh: 3441 Memory fault
> > > sh: 3471 Memory fault
> > > sh: 3528 Memory fault
> > > sh: 3531 Memory fault
> > > sh: 3535 Memory fault
>
> > Because your script is screwed up and your shell is dying. How bright
> > do you have to be to use the -x flag and debug a little?
>
>
> My script is so simple, it is a simple imp statement.., full import
> (full=Y). During imp, user1 is impoted (all tables,,, towards the end
> when it comes to view stored procedure..., this error occurs, but
> subsequenet users user2, user3 etc get imported successfuly. set -x
> will not provide any useful information.
What imp puts out can get truncated when there is an error, so the
last thing outputted may be before the actual error. Wild speculation
here, but watch your swapinfo -am and check what indexes, SP's
actually have been created given this hypothesis:
user1 completes. User2 has a big table with many indices. When you
use the imp defaults (as opposed to creating the indices later), the
indices are created after the table is imported, which uses lots of
memory due to sorts, until they hopefully spill over into temporary
tables. So my guess is you have insufficient swap space, and too big
sort memory to handle everything until the spillover.
So _in addition_ to checking all the memory settings against Oracle
recommendations with a fine tooth comb as everyone else has been
telling you, check your swap space configuration, usage, OS patches
and any pga/sga settings. Remember, when you have two or more
instances on a unix box, you have to add up their memory
requirements! (Beyond that, some things like aborting instances can
keep shared memory, be sure to check with the ipc utilities. Be
especially careful about which hp-ux 11, too, there are some minor
differences that can lead to major consequences - I've seen one
machine that has no problems with a fiber disk array on 11.11 and
11.3x, but major problems on 11.23 IIRC, my guess due to OS
patches.). And as several people have pointed out, it could be a
hardware problem - later versions of hp-ux have the ability to use
memory as swap (yes, it makes sense if you investigate it, and I've
become convinced Oracle dbconsole, at least, doesn't account correctly
for it), and you may be hitting bad memory or disk with the swap.
Also, Oracle has had obscure issues with SGA size and self-
abu^H^H^Htuning, in disparate configurations, that only show up when
something with a different performance profile is run. And Itanium is
different.
Are you setting LD_LIBRARY_PATH or similar things anywhere, or had any
other 32bit/64bit types of errors in the past? Using bash instead of
ksh? core files left around? gazillions of trace files in udump?
jg
--
@home.com is bogus.
Wasn't there a star trek episode about planet eating aliens?
http://www.bloomberg.com/apps/news?pid=20601087&sid=agSuuvCA2EAU&refer=home
Mladen Gogala
> You have something wrong probably with either the hardware ... your unix
> memory configuration ( my guess ) ... or your oracle software ... or
> your operating system software ...
Or Vogons may be at it again?