dbTalk Databases Forums  

RE Pervasive System error and Continuous Ops

comp.databases.btrieve comp.databases.btrieve


Discuss RE Pervasive System error and Continuous Ops in the comp.databases.btrieve forum.



Reply
 
Thread Tools Display Modes
  #1  
Old   
John Anisy
 
Posts: n/a

Default RE Pervasive System error and Continuous Ops - 01-19-2004 , 05:21 PM






Hi,
I have a site running P2000 SP2a and am trying to figure out the best way to
manage backups. Please see options below. Has anyone had any experience
with problems caused by stopping pervasive services with users possibly
logged on?

Option 1 - Stop the Pervasive services
'should' be OK as long as you aren't running anything major on the database
at the time that is updating the records - note the 'should'
Any application that was running will not be able to connect to the database
when it is down
Option 2 - open file backup
This just copies the files that are open
This can cause backups with files out of sync and may corrupt data

Option 3 - Continuous operations
This locked up Pervasive on our server and we wound up with a corrupted
database
From some research it seems to be unreliable before Pervasive 2000 SP3
Pervasive 2000 SP3 & SP4 cause problems with file locking in the
application we are running
This is doesn't seem to be a problem with Pervasive v8

Option 4 - Upgrade to Pervasive v8
Cost


--
John Anisy



Reply With Quote
  #2  
Old   
Leonard
 
Posts: n/a

Default Re: RE Pervasive System error and Continuous Ops - 01-19-2004 , 11:51 PM






Hi again.

Option 1 should be fine.
The engine should do an orderly shutdown regardless of load.
Transactions aborted, files closed, sessions closed cache committed
then down.
Of course it will be unavailable to the application when stopped.

Option 2 is a maybe.
A good open file manager should let you get a snapshot of the data
files. Unfortunately there is no guarantee the data files are in a
consistent state when the snapshot is taken. However the engine is
pretty good about recovering from a partial system transaction.

Option 3, well.
SP2 in your experience just does not work reliably.
Actually SP1 was ok. SP2 added AsyncIO and well...
SP3 added row level locking. Not behaving properly with the
application is possible.
SP4 is pretty well behaved with locking. Depends on whether the
application likes row level or page level locking. Rebuilding the
files with repeating duplicate instead of linked duplicate keys may
help.
V8 has the same row level locking so I do not know why the application
would work any better with it than SP4.

Leonard

On Tue, 20 Jan 2004 12:21:34 +1300, "John Anisy"
<j.anisy (AT) cchlawbase (DOT) co.nz> wrote:

Quote:
Hi,
I have a site running P2000 SP2a and am trying to figure out the best way to
manage backups. Please see options below. Has anyone had any experience
with problems caused by stopping pervasive services with users possibly
logged on?

Option 1 - Stop the Pervasive services
'should' be OK as long as you aren't running anything major on the database
at the time that is updating the records - note the 'should'
Any application that was running will not be able to connect to the database
when it is down
Option 2 - open file backup
This just copies the files that are open
This can cause backups with files out of sync and may corrupt data

Option 3 - Continuous operations
This locked up Pervasive on our server and we wound up with a corrupted
database
From some research it seems to be unreliable before Pervasive 2000 SP3
Pervasive 2000 SP3 & SP4 cause problems with file locking in the
application we are running
This is doesn't seem to be a problem with Pervasive v8

Option 4 - Upgrade to Pervasive v8
Cost


Reply With Quote
  #3  
Old   
John Anisy
 
Posts: n/a

Default Re: RE Pervasive System error and Continuous Ops - 01-20-2004 , 01:33 PM



Thanks Leonard,
That explains it rather well.
I will set them up so the services shut down and do some testing in house
with SP4. From memory SP4 was just an engine Patch (nothing for the
client)?

Cheers

John


"Leonard" <lharvey (AT) austin (DOT) rr.com> wrote

Quote:
Hi again.

Option 1 should be fine.
The engine should do an orderly shutdown regardless of load.
Transactions aborted, files closed, sessions closed cache committed
then down.
Of course it will be unavailable to the application when stopped.

Option 2 is a maybe.
A good open file manager should let you get a snapshot of the data
files. Unfortunately there is no guarantee the data files are in a
consistent state when the snapshot is taken. However the engine is
pretty good about recovering from a partial system transaction.

Option 3, well.
SP2 in your experience just does not work reliably.
Actually SP1 was ok. SP2 added AsyncIO and well...
SP3 added row level locking. Not behaving properly with the
application is possible.
SP4 is pretty well behaved with locking. Depends on whether the
application likes row level or page level locking. Rebuilding the
files with repeating duplicate instead of linked duplicate keys may
help.
V8 has the same row level locking so I do not know why the application
would work any better with it than SP4.

Leonard

On Tue, 20 Jan 2004 12:21:34 +1300, "John Anisy"
j.anisy (AT) cchlawbase (DOT) co.nz> wrote:

Hi,
I have a site running P2000 SP2a and am trying to figure out the best way
to
manage backups. Please see options below. Has anyone had any experience
with problems caused by stopping pervasive services with users possibly
logged on?

Option 1 - Stop the Pervasive services
'should' be OK as long as you aren't running anything major on the
database
at the time that is updating the records - note the 'should'
Any application that was running will not be able to connect to the
database
when it is down
Option 2 - open file backup
This just copies the files that are open
This can cause backups with files out of sync and may corrupt data

Option 3 - Continuous operations
This locked up Pervasive on our server and we wound up with a corrupted
database
From some research it seems to be unreliable before Pervasive 2000 SP3
Pervasive 2000 SP3 & SP4 cause problems with file locking in the
application we are running
This is doesn't seem to be a problem with Pervasive v8

Option 4 - Upgrade to Pervasive v8
Cost




Reply With Quote
Reply




Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

vB code is On
Smilies are On
[IMG] code is On
HTML code is Off



Powered by vBulletin Version 3.5.3
Copyright ©2000 - 2012, Jelsoft Enterprises Ltd.