what does this mean..
I run informix 7.1 on digital unix 1000 server. suddenly today I get this.
looks like I was offline for about 1 hour when I brought it back on line,
AND NOBODY COMPLAINED!!! I have never seen this one. What do I need to do to
avoid/prevent a repeat?
13:34:05 Checkpoint Completed: duration was 0 seconds.
13:39:05 Checkpoint Completed: duration was 0 seconds.
13:39:38 Assert Failed: WARNING! Internal Error - Arithmetic Exception
13:39:38 Who: Session(921, pin@admsrv1.sph.hrs, 10196, 17)
Thread(1047, sqlexec, 82f8e0, 1)
13:39:38 Results: Internally corrected
13:39:38 See Also: /tmp/af.46c840d
13:39:42 session.c, line 704, thread 1047, proc id 559, (destroy_session)
Mem .
13:39:42 PANIC: Attempting to bring system down
Mon Mar 15 14:35:05 1999
14:35:05 DR: DRAUTO is 0 (Off)
14:35:12 INFORMIX-OnLine Initialized -- Shared Memory Initialized.
14:35:12 Physical Recovery Started.
Abel_Johnson@doh.state.fl.us wrote:
>
> I run informix 7.1 on digital unix 1000 server. suddenly today I get this.
> looks like I was offline for about 1 hour when I brought it back on line,
> AND NOBODY COMPLAINED!!! I have never seen this one. What do I need to do to
> avoid/prevent a repeat?
Install an ALARMPROGRAM in your onconfig file that can send email to
your home account or even to your beeper (most text beeper companies
will let you send email to something like pin_number@beeper_company.com
and it will show up on your beeper). Take a look at my eventalarm.c
alarmprogram which is in the IIUG Software Repository in the package
named utils3_ak for an alarm program that pretty much does it all. It
even backs up logical logs to disk as they fill. You can pattern your
own alarm program on mine, use mine as is, or modify it to your own
tastes.
Now when the engine crashes (except if the master oninit blows up since
that's the task that launches the alarm program and is why 7.30 added
an additional alarm handler, SYSALARMPROGRAM, which is launched by the
misc VP) you will receive email or beep immediately.
Art S. Kagel
We have been plagued with this same problem several times in the past.
23:00:02 Assert Failed: Internal Error - Arithmetic Exception
23:00:02 Who: Session(3588, heisys@prodpdb, 20624, 1444847628)
Thread(3756, sqlexec, 56230e14, 10)
23:00:02 Results: OnLine must abort
23:00:02 Action: Reinitialize shared memory
23:00:02 PANIC: Attempting to bring system down
Informix has told us that this problem is addressed and fixed in later
releases of Informix ( 7.3uc2 and above ) and they have given us a
workaround,
Here is the description:
The root cause is that the engine code is not expecting one of the
sysindexes entries for this table to have a value of "0" (zero) in the
nunique column.
Here is the workaround
To workaround, change the value to 1:
update sysindexes set nunique=1 where tabid=xxx and nunique=0;
Has anyone ever tried somthing like this? Has anyone ever seen this? I
don't what to do this for I do not know what OTHER problems could occur
Carlos Bolden
Database Administrator
Harrah's Entertainment
cbolden@harrahs.com ( work )
cbolden1@midsouth.rr.com ( home )
<Abel_Johnson@doh.state.fl.us> wrote in message
news:7cjprk$kf$1@news.xmission.com...
>
> I run informix 7.1 on digital unix 1000 server. suddenly today I get this.
> looks like I was offline for about 1 hour when I brought it back on line,
> AND NOBODY COMPLAINED!!! I have never seen this one. What do I need to do
to
> avoid/prevent a repeat?
>
> 13:34:05 Checkpoint Completed: duration was 0 seconds.
> 13:39:05 Checkpoint Completed: duration was 0 seconds.
> 13:39:38 Assert Failed: WARNING! Internal Error - Arithmetic Exception
> 13:39:38 Who: Session(921, pin@admsrv1.sph.hrs, 10196, 17)
> Thread(1047, sqlexec, 82f8e0, 1)
> 13:39:38 Results: Internally corrected
> 13:39:38 See Also: /tmp/af.46c840d
> 13:39:42 session.c, line 704, thread 1047, proc id 559, (destroy_session)
> Mem .
> 13:39:42 PANIC: Attempting to bring system down>
> Mon Mar 15 14:35:05 1999
>
> 14:35:05 DR: DRAUTO is 0 (Off)
> 14:35:12 INFORMIX-OnLine Initialized -- Shared Memory Initialized.
> 14:35:12 Physical Recovery Started.>