Re: Pervasive.SQL 9.5 problems.

#1

You may wish to patch to 9.52.053, the "Update 1" that is available on
Pervasive's web site.

Second, re-verify your memory allocation and monitor the Virtual Bytes
of the NTDBSMGR.EXE process in the Performance Monitor. If this value
gets over 2GB, the system will fail with the symptoms you are
indicating.

Also, be sure to configure Windows 2003 Server for DrWatson to report
errors visually -- this will help indicate when the engine fails, if
you are indeed getting an engine failure. Microsoft has done a good
job preventing access violations -- but all they have really done is
prevenmt the DrWatson popup -- they can still occur.

Once you enable the visual indicators, see if any errors are actually
shutting down the services...
Goldstar Software Inc.
Pervasive-based Products, Training & Services
Bill Bach
BillBach (AT) goldstarsoftware (DOT) com
http://www.goldstarsoftware.com
*** Chicago: Pervasive Service & Support Class - March 2008 ***

Karl A. Sxrensen wrote:

Quote:

At one customer site, we have big problems running Pervasive. This
installation have rune fine for years, but about a year ago, we began
having problems. This customer have deadlines to keep, and because
the Pervasive server crashes (sometimes several times a day. Today it
have crashed 4 times), this is pretty serious to them (and us).

Server:
Pervasicve.SQL 95.
Windows server 2003 R2 Service pack 1.

Clients:
Windows XP SP2.

There are about 10 to 15 active clients connected to the server, and
sometimes the load is pretty high. The database consist of a bit more
than 700 tables, and a total of about 100GB data. The largest table
is around 47 GB in size.

Our programs is programmed in Visual Dataflex 9.1 (guess nobody have
heard of it), and we use the transactional interface. We have some
web access that uses the relational interface.

At random intervals, the clients looses the connection to the server.
The only solution seems to restart the services on the server. There
are no indication of the problem in the Pervasive, or Windows event
logs (makes it hard to debug).

We have had a similar situation in our developement environment. We
all lost the connection to the pervasive server (9.5), and when I had
a look at the server, the NTDBSMGR.EXE had stoppet without any
logging to the Pervasive or Windows event log. I don't know if this
is happening at the customer site, but will be checking this the next
days.

Lately we have also been getting some error 146:
"146: Duplicate system key. The same key number was generated by two
different threads generating system keys. "

Any ide what to do ?

TIA
Karl

--

Thread Tools
Show Printable Version Email this Page
Display Modes
Linear Mode Switch to Hybrid Mode Switch to Threaded Mode

Re: Pervasive.SQL 9.5 problems.

comp.databases.btrieve comp.databases.btrieve

Re: Pervasive.SQL 9.5 problems. - 03-06-2008 , 05:02 PM