Re: Checkpoint problem.
Posted in 1997
This message is in MIME format. The first part should be readable text,
while the remaining parts are likely unreadable without MIME-aware tools.
Send mail to mime@docserver.cac.washington.edu for more info.
---2050821805-1755404083-868429351=:1500
Content-Type: TEXT/PLAIN; charset=US-ASCII
Hi Ignacio,
On Tue, 8 Jul 1997, Ignacio Bisso wrote:
> Hi Milen,
>
> I nedd some aditional information in order to know exactly waht is your
> problem, but...
I put more info in attacment file.
>
> Check your ckpt interval parameter in your tbconfig/onconfig file.
> if ckpt interval is 300, the problem could be
ckpt is 300 (default and we didn't change it)
> when the checkpoint arrives, if any user is in critical section, the
> checkpoint must wait until the users finish their process and close the
> critical section. If the user (for any reason) doesn't leave the critical
> section, the checkpoint never begins.
Yes, there's been one user in a critical section when we stoped the
Informix.
What may be the reason for the user to be in a critical section for
such a long time?
> Other users trying to write can't begin critical sections because we have a
> checkpoint required, and checkpoint never begins. So look for users in
> critical section whit tbstat/onstat -u
>
> I hope this help
>
> Ignacio
After the crash I ran the tbcheck utility.
There are a lot of warnings and errors in the log file.
Only the logical logs were started at the time of the crash.
Milen.
----------------------
dbadmin@svilosa.bis.bg
----------------------
---2050821805-1755404083-868429351=:1500
Content-Type: TEXT/PLAIN; charset=US-ASCII; name="crash.inf"
Content-Transfer-Encoding: BASE64
Content-ID: <Pine.LNX.3.95.970709092231.1500B@svilosa.bis.bg>
Content-Description:
====================================
This is a part of Informix log file.
====================================
09:13:05 Checkpoint Completed
09:13:06 Logical Log 2203 Complete
09:13:13 Logical Log 2201 Backed Up
09:13:16 Checkpoint Completed
09:13:23 Logical Log 2202 Backed Up
09:13:29 Logical Log 2203 Backed Up
09:14:02 Logical Log 2204 Complete
09:14:28 Checkpoint Completed
09:14:31 Checkpoint Completed
09:14:40 Logical Log 2204 Backed Up
09:16:26 Checkpoint Completed
09:54:38 Process Aborted Abnormally: pid=-1378 user=203 us=80401bb0 flags=3
09:54:38 Process Aborted Abnormally: pid=-3328 user=296 us=80401c20 flags=3
09:54:38 Process Aborted Abnormally: pid=-890 user=277 us=80401c90 flags=3
09:54:38 Process Aborted Abnormally: pid=-3321 user=284 us=80401d00 flags=3
09:54:38 Process Aborted Abnormally: pid=-1088 user=213 us=80401d70 flags=3
09:54:38 Process Aborted Abnormally: pid=-1748 user=261 us=80401de0 flags=3
09:54:39 Process Aborted Abnormally: pid=-3176 user=312 us=80401e50 flags=3
09:54:39 Process Aborted Abnormally: pid=-2925 user=295 us=80401ec0 flags=109
09:54:39 Process Aborted Abnormally (critical section): pid=-2925 user=295 flags=109
09:54:39 INFORMIX-OnLine entering ABORT mode!!!
09:54:39 -- Online Aborting -- us=804019f0, pid=385, uid=0
09:54:44 INFORMIX-OnLine Stopped
Tue Jul 8 09:58:57 1997
09:58:57 INFORMIX-OnLine Initialized -- Shared Memory Initialized
09:58:57 Physical Recovery Started
09:58:58 Checkpoint Completed
09:58:58 Physical Recovery Complete: 107 Pages Restored
09:58:58 allocpage:warning pagenum (3) > npused (0)
09:58:58 allocpage: partp (806005b0), partnum (1000182)
09:58:58 allocpage:warning pagenum (2) > npused (0)
09:58:58 allocpage: partp (806006b0), partnum (1000183)
09:58:58 allocpage:warning pagenum (2) > npused (0)
09:58:58 allocpage: partp (806007b0), partnum (1000184)
09:58:58 allocpage:warning pagenum (2) > npused (0)
09:58:58 allocpage: partp (806008b0), partnum (100018c)
09:58:58 allocpage:warning pagenum (3) > npused (0)
09:58:58 allocpage: partp (806009b0), partnum (1000182)
09:58:58 allocpage:warning pagenum (2) > npused (0)
09:58:58 allocpage: partp (806005b0), partnum (1000183)
09:58:58 allocpage:warning pagenum (2) > npused (0)
09:58:58 allocpage: partp (806006b0), partnum (1000184)
09:58:58 allocpage:warning pagenum (2) > npused (0)
09:58:58 allocpage: partp (806007b0), partnum (100018c)
09:58:58 allocpage:warning pagenum (3) > npused (0)
09:58:58 allocpage: partp (806008b0), partnum (1000182)
09:58:58 allocpage:warning pagenum (2) > npused (0)
09:58:58 allocpage: partp (806009b0), partnum (1000183)
09:58:59 allocpage:warning pagenum (2) > npused (0)
09:58:59 allocpage: partp (806005b0), partnum (1000184)
09:58:59 allocpage:warning pagenum (2) > npused (0)
09:58:59 allocpage: partp (806006b0), partnum (100018c)
09:58:59 allocpage:warning pagenum (2) > npused (0)
09:58:59 allocpage: partp (806008b0), partnum (1000184)
09:58:59 allocpage:warning pagenum (3) > npused (0)
09:58:59 allocpage: partp (806008b0), partnum (1000183)
09:58:59 allocpage:warning pagenum (3) > npused (0)
09:58:59 allocpage: partp (806005b0), partnum (1000185)
09:58:59 allocpage:warning pagenum (2) > npused (0)
09:58:59 allocpage: partp (80600ab0), partnum (100018a)
09:58:59 allocpage:warning pagenum (2) > npused (0)
09:58:59 allocpage: partp (80600bb0), partnum (100018b)
09:58:59 allocpage:warning pagenum (2) > npused (0)
09:58:59 allocpage: partp (80600cb0), partnum (100018c)
09:58:59 allocpage:warning pagenum (3) > npused (0)
09:58:59 allocpage: partp (80600db0), partnum (1000185)
09:58:59 allocpage:warning pagenum (2) > npused (0)
09:58:59 allocpage: partp (806005b0), partnum (100018a)
09:58:59 allocpage:warning pagenum (2) > npused (0)
09:58:59 allocpage: partp (80600ab0), partnum (100018b)
09:58:59 allocpage:warbm