ISTech Support Forum

ISTech Support Forum
http://www.istechforum.com/YaBB.pl
Evo-ERP and DBA Classic >> Problem Reports - Repeatable >> Extended Pervasive files
http://www.istechforum.com/YaBB.pl?num=1276542131

Message started by bjones on 06/14/10 at 12:02:11

Title: Extended Pervasive files
Post by bjones on 06/14/10 at 12:02:11

BKAPHPOL just met a magic limit of 2 gigs and automatically extended itself with two files BKAPHPOL.^01 and BKAPHPOL.^02.

Now Dba quits out of Inventory inguiries (the window flashes open then closes). I can still see the data through the Pervasive.SQL data manager, but nothing in DBA which accesses that file works.

Any ideas?

Thanks in advance.

Bob

Title: Re: Extended Pervasive files
Post by Kelloggs on 06/14/10 at 12:08:12

It is Archiving Time.
Login as the ADMIN SM-J-R

Make a copy of your BKAPHPOL and BKAPHPO before you use the archive feature.

:)

Kelloggs

Title: Re: Extended Pervasive files
Post by bjones on 06/14/10 at 12:28:24

Thanks, But I have no SM-J-R, it stops at SM-J-Q.

Title: Re: Extended Pervasive files
Post by bjones on 06/14/10 at 12:31:32

I do have a SM-J-F Purge Purchase Order History. Will that work? I have nightly backups, so I have all the data elsewhere.

.... Nope doesn't work. Won't open the file to purge it.

How 'bout if I substitute an older file, then purge it? What else will I mess up?
It's just a history... right?

Title: Re: Extended Pervasive files
Post by GasGiant on 06/14/10 at 12:47:51

It stops at Q when you are logged in as ADMIN? How old is your update?

Title: Re: Extended Pervasive files
Post by bjones on 06/14/10 at 12:49:15

Help About says 2004.1 Feb 04 2004

Title: Re: Extended Pervasive files
Post by bjones on 06/14/10 at 13:22:34

By the long silence,I am guessing that is not a good date ;-)

Title: Re: Extended Pervasive files
Post by Lynn_Pantic on 06/14/10 at 13:25:09

You need the IS Tech Support updates to have the option to archive but nothing in DBA will work until you get the file size down. You could try the Pervasive Rebuiild utility; it might work to get the file size down. Jut rebuild the BKAPHPOL and it may swallow up the ^01 file.

Title: Re: Extended Pervasive files
Post by bjones on 06/14/10 at 13:34:38

I am trying the rebuilding, but it doesn't look good.

It says the output file exceeds the available disk space, yet I have 93 gigs available.

How bout I take a file before it got extended and delete a bunch of records? Any major risk there?

Title: Re: Extended Pervasive files
Post by bjones on 06/14/10 at 14:01:15

ok I got a two day old "BKAPHPO","BKAPHPOL" and started purging everything before 2006-01-01.

Dust is flying everywhere. It looks hopeful. Thanks for the help.

If the accountant hasn't done his books for then, I suspect it is more his problem than mine ;-)

One can be daring when one has backups ;-)

Title: Re: Extended Pervasive files
Post by bjones on 06/14/10 at 14:21:12

When I purge, the file actually gets bigger and pervasive split it again. haha can't win.

So the rebuild index doesn't work on the split file.

I am doing it again, but will examine the data and delete voided records manually.

See you in November ;-)

If anyone has any other suggestions I am always open.
---------------------------------

OK. I am using a 2-day old file pair that haven't been split.
I am first reindexing, which appears to be working. This should hopefully reduce the size of the file.
Then I will purge and re index again.

If this doesn't work... Lynn just called me from IS Tech Support. What a pleasant surprise! And gave another suggestion that I will try.

------------------------------------
This didn't work either. Re indexing also made the file larger. After it counted down on the records it went negative .

Title: Re: Extended Pervasive files
Post by bjones on 06/14/10 at 19:01:13

I have tried installing Pervasive WG twice. The server says its running but dragging the old DBA directory on to the new server doesn't work. The path variable contains the location of the missing dll in the error message. Running the set up from the Dba workstation dir doesn't work.