.B1 File Grew Very Fast

I saw the same problem at a previous job and it was caused by a DB lock. The strange thing for us was that it BI would blow up after MRP ran if the PO table was locked. We ended up getting a script from Epicor support that we could run to check the DB for locks and we could then kill the user session that was causing the lock. This would release the lock and our BI file would be fine. I don't think they were ever able to find out what was causing the locking issue though.

John

My 8.03 Vantage nightly database backup file grew about 400MB (10%) in size during the last week with no known changes to the system.

 

In doing a proutil tabanalys I see no real table size changes. 

 

But looking at my LIVE and TEST /db folders, I see that my .b1 file may be the culprit because it seems that it grew 400MB in a week.  I’m assuming the .b1 + .d1 file = your online backup file (probkup). 

 

What would cause this .b1 file to grow?  Even over the weekend when nobody was working it grew 40MB per day; very odd. 

 

Thanks in advance.

 

 

 

 

 

Vic Drecchio

 

Director of Information Technology

Swepco Tube, LLC

 

Mobile:  704.530.3092

Office:  x1379

 

A runaway BAQ. Or I've had it happen when a LaborDtl record gets locked up.

Online backups can be an issue with a big bi file...
Sometime the error situation will clear.. sometimes a reboot.
Either way I had to truncate the bi file... didn't automatically shrink.
>>8.03 Vantage nightly database
P.S.
Also runaway ODBC queries
Unfortunately....
Logging in V8 doesn't capture the likely candidates.
They were updated in E9, easier to spot the causes.

We have had this issue a few times previously (it averages around annually) - I think our last one grew at around 2am with no cause found.  Epicor advised us that it's classed as large if it's greater than 10% of your database.


We have been monitoring it over the last few years and recommendations from Epicor were to set the Server logs to verbose and run the BI monitor and lock logger (we have although nothing obvious has been picked up when it's happened).  Answerbook 1452BRK provides some information too.


We just monitor the file (we now have an email alert if it increases to a certain size) and then truncate.  Hope you sort it.