Subject | Re: Frequntly "index page error" |
---|---|
Author | mnavahan |
Post date | 2009-05-04T13:41:09Z |
--- In firebird-support@yahoogroups.com, Helen Borrie <helebor@...> ;
Hi
change in doing nightmare for me
after change in recursive stored procedures get
"internal gds software consistency check (can't continue after bugcheck")
after restoring data with last page database working normal ....
wrote:
Hi
change in doing nightmare for me
after change in recursive stored procedures get
"internal gds software consistency check (can't continue after bugcheck")
after restoring data with last page database working normal ....
wrote:
>
> At 02:39 PM 4/05/2009, you wrote:
> >--- In firebird-support@yahoogroups.com, Helen Borrie <helebor@> wrote:
> >>
> >> At 11:03 AM 4/05/2009, you wrote:
> >>
> >> >but think is must not faild the database ! (but not sure)
> >>
> >> If a running Classic process crashes due to an out-of-memory error, it is quite possible to corrupt any data that was in the process of being written. A crashed process cannot correct itself, can it ???
> >>
> >> Configure the cache properly for your server model and its resources, fix your database by another backup and restore, and this problem should disappear.
> >>
> >> ./heLen
> >>
> >
> >Hi heLen
> >
> >yes after every Backup / restore my problem solved but from two day to 4 day i see it again !
> >
> >then this is not good
> >
> >what i do to DON'T SEE it again ?
>
> Change the size of the page cache. Read again the response from Anderson Farias and do what he describes. In fact, I think 50 pages is too little if you have 450 tables; and, unless you have a LOT of free RAM, 500 pages is too much if there are 45 users. Try 128 pages to begin.
>
> ./heLen
>