DBMS crash with segmentation violation Ingres 2.6 sp2 on Tru64 5.1a

Thread view:

Enable EMail Alerts

Start New Thread

Thread rating:

Oscar - 21 Jun 2004 16:11 GMT

Hi there!!

I am experimenting esporadic and ramdom segmentation violation
situation in my production environment (after migrating from II 2.0).

The machine is a DS20 with 2 CPU, with RAID 5 and 3 Gb RAM. 240 ingres
conexion.

I have one DBMS server default that I use on ONLINE working and a
particular DBMS, server_class O3 that I use with batch processes.

Since Monday 14th I have 3 segmentation violation on differents
applications queries.

stack_size = 393216
cache_sharing = ON
qef_qep_mem = 100000
2 K dmf_memory = 83132416
8 k dmf_memory = 173539328

I would appreciate any help

Thanks in advanced

Reply to this Message

Mike Lay - 22 Jun 2004 12:22 GMT

> Since Monday 14th I have 3 segmentation violation on differents
> applications queries.
[quoted text clipped - 6 lines]
>
> I would appreciate any help

And the error messages were...?

Signature

Mike Lay - Clinical Trial Service Unit
"I can barely speak for myself, let alone the CTSU"
w: http://www.ctsu.ox.ac.uk/
e: michael dot lay at ctsu (with an ox, an ac, and an uk on the end).

Reply to this Message

Gerhard Hofmann - 23 Jun 2004 09:28 GMT

> I am experimenting esporadic and ramdom segmentation violation
> situation in my production environment (after migrating from II 2.0).
[quoted text clipped - 15 lines]
>
> I would appreciate any help

I can remember that we also had serious troubles on Tru64 machines. I
think workaround was to use old-fashioned Ingres-6.4-style threads by
setting II_THREAD_TYPE=INTERNAL (not sure about correct syntax, better
ask CA tech support).

After trying millions of different patches we somehow managed to get
things running stable also with OS threads.

Will ask a colleague about the patch numbers.

Regards
Gerhard

Reply to this Message

Oscar - 23 Jun 2004 19:29 GMT

The message error is:

SUN_CENT::[1276 , 0000000159017e80]: Client pid:
922439
SUN_CENT::[1276 , 0000000159017e80]: Client
connection target:
sol
SUN_CENT::[1276 , 0000000159017e80]: Client
information: user='
cevz',host='sun.centro.familiar.com.py',
tty='sun.centro.familiar.com.py',pid=922439,conn='sol'
SUN_CENT::[1276 , 0000000159017e80]: Description:
SUN_CENT::[1276 , 0000000159017e80]: Query: Execute
cap11nti

sun.cent::[1276 , 59017e80]: Tue Jun 15 16:34:32 2004
Segmentation Violation (SIGSEGV)
@PC=3ff800d47f4,PS=8,PV=1,GP=1401aefa0,SP=20004652440,VFP=20004652440,RA=12027d
164,v0=0
a0-5[162c50000,1,0,1,1,20]
t0-11[469ee58469f0006,144313ee8,1,0,20,144315808,20,1,0,1,162b12078,1]
s0-5[144314648,1,200046524c0,3a,32,14250d178]

I contacted with CA technician and they suggested me to add one
parameter that is not documented:
Using iisetres add the parameter ulm_pad_bytes=64 to the config.dat,
according to your machine name.

This was two days ago. Since this, no more crash.

Regards

Reply to this Message

Gerhard Hofmann - 24 Jun 2004 09:04 GMT

> I contacted with CA technician and they suggested me to add one
> parameter that is not documented:
> Using iisetres add the parameter ulm_pad_bytes=64 to the config.dat,
> according to your machine name.
>
> This was two days ago. Since this, no more crash.

Sounds interesting. Can you copy the line from your config.dat or the
exact iisetres command and post it here? Thanks!

Regards
Gerhard

Reply to this Message

Oscar - 25 Jun 2004 15:29 GMT

> > I contacted with CA technician and they suggested me to add one
> > parameter that is not documented:
[quoted text clipped - 8 lines]
> Regards
> Gerhard

Follow this steps:

1) log in as an ingres user.
2) Run the following command at system prompt:

iisetres 'ii.srv_subdomain_domain_com_cl.dbms.*.ulm_pad_bytes' 64

(The above will set this parameter in your config.dat file)
3) Restart your ingres installation for this change to take an effect

Reply to this Message