btrieve page locked

[dgillz]

Using Pervasive SQL 2000i, a user is suddenly getting an error:

"OEORDHDR - Btrieve page locked - please wait".

Is there a Pervasive setting that hs been changed that could be causing this? Any insight would be helpful.

Software Sales, Training, Implementation and Support for Exact Macola, eSynergy, and Crystal Reports

http://www.trianglepartners.com

 

[MacolaHelp]

Btrieve does do page locking rather than record locking. Are you still getting the error? Double check pervasive monitor, too, & be sure all users are out. Once in a while, the user will stay active in pervasive even when they end the macola task.

 

[MacolaHelp]

FYI: I'm actively working with a site right now that has experienced this error but neglected to tell me (page locking on oeordhdr). They are on psql2000i sp3 & now have some xp workstations, so I suspect I need to update to psql2000i sp4 w/hot fixes. I think their server is still nt4/sp6, not win2k, definitely not 2003. They say (and I have never personally seen this) that when they try to reboot or shut down the macola server (only macola & pvsw are on this server, BTW), they get a message about the oeordhdr is page locked intermittently. Can't imagine why that would occur on the server. Inside macola, I'm not terribly surprised, but sounds wierd on the server. I'll be out there again Monday & will let you know if I have any success.

 

[MacolaHelp]

Update: while there today, I discovered they have not configured all their xp workstations to have local off in the client configuration on access. We changed those settings today & I will be back out on Friday, but am seriously considering service packing pvsw2000i to sp4 w/hot fixes since xp was barely released when sp3 came out (where they are now). I also noticed last week & today that I couldn't rename the macola user in vbaprj\oe0101.o even after all users were out of the users folder & the pervasive monitor. Also, I tried stopping pervasive services on the server to rename the folder. No dice. Had to actually reboot the server to rename the oe0101.o\macola folder. This was before I found the improper settings on the xp clients.

If anyone else has any thoughts or updates, great. Otherwise, I'll let you know what I find out Friday. Another FYI: not all users get the oeordhdr locked message. I have copied the oe0101.0 vba project to each user macola ID now as I read on another thread that the macola user can cause record locking problems, even tho it saves administrative overhead on maintenance of the vba code. We have about 30 user IDS & 25 concurrent macola users. Server is definitely nt4/sp6, dual processor 1.4 gig w/1 meg memory, but not dual NICs. I did get a Dr Watson memory conflict error today when I rebooted the server after manual shutting off pervasive services prior to reboot. I didn't have users log off their WS, only macola. More later.

 

[dgillz]

Peggy,

Any update on this issue?

Software Sales, Training, Implementation and Support for Exact Macola, eSynergy, and Crystal Reports

http://www.trianglepartners.com

 

[dgillz]

I have a client that is still getting this error. Does anyone know what causes page locking in Pervasive SQL 2000i, or how to fix it?

Software Sales, Training, Implementation and Support for Exact Macola, eSynergy, and Crystal Reports

http://www.trianglepartners.com

 

[mirtheil]

What causes page locks (status 84) errors in Btrieve/Pervasive is that two (or more) clients read and insert/update/delete records on the same data/index/header page. If you get them once in a while and retrying the operation resolves it, then it's probably a timing issue.
If you're getting them consistently, that's something else. What you need to check would be using the Function Executor and see if it returns a status 84. If it does, call Pervasive and see what they say.

info@mirtheil.com
Custom VB and Btrieve development.
Certified Pervasive Developer
Certified Pervasive Technician

 

[MacolaHelp]

Some more info: my client is still getting lockups, tho I think they are more from corrupted views due to header/line records being out of sync. I put the vbmacexe fix in for the 100% cpu utilization & while record locking seems to be better, other problems have cropped up such as inability to alt tab between screens. We are doing file validation, clean up right now. I will then service pack to 4 w/hot fixes. We are on 7.6.200.5 macola. I suspect a timing issue on the page locks, too, but if they never experienced it before why does it happen now? Can they make it fail at will, or it is one of our favorites, the "intermittent" locking problem?

 

[dgillz]

This is happening every single day at my client. They hav eto reboot the server to fix this.

Software Sales, Training, Implementation and Support for Exact Macola, eSynergy, and Crystal Reports

http://www.trianglepartners.com