I only have one comment to add to this. We truncate our bi file about
once every 2 months. The one performance gain that we get is that the
database will start up much faster than when the bi file is large.
From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com] On Behalf
Of Ned
Sent: Thursday, August 20, 2009 8:37 AM
To: vantage@yahoogroups.com
Subject: Re: [Vantage] Bi or B1 File
1. What is in the Bi/B1 file? The BI/B1 file is the "Before-Image" File,
which is why it is called BI. It is a B1 in the directory because that
is
the first BI file. It is possible through advanced Progress techniques
to
break up the BI File into multiple files(B1, B2, B3), yes it can be done
but
it is not supported through Epicor, but it can increase performance in a
progress DB to go more granular, but it is a lot of work and takes a lot
of
knowledge. Same can be done with the datafile(D1, D2, D3) What happens
is
basically this...
You have information in a record in a table in the database, let's call
this
Data A. Then you have changes to that record you want to write to the
Database, we can call this Data B. When you want to commit those changes
of
Data B, Progress will copy Data A to the BI file, then write Data B to
the
database.
Simply put, BI is the Progress version of transaction logs of data that
was
replaced which can be used to roll back the DB. Conversely, there are
also
what are known as "After Image", or AI/A1 files which do almost the same
thing as the Before Image, only they are copies of Data B in the
previously
mentioned scenario, this is not setup by default in the system, but it
is
reccomended to be setup. The combination of these 2 file types give you
a
full and complete transaction log. Which can be used to roll forward or
backward your DB in Progress/OpenEdge.
2. Does the growing size cause performance issues? Easy answer, no, not
really. However, performance can be improved by putting the D1, A1, and
B1
files on different physical disks due to bottlenecks in I/O which is
really
the cause of the performance hits.
3. Is there a way to manage it? There are ways through the Progress
command
line tools to manage it, if you have interest in that then I would
suggest
going directly to Progress and taking their OpenEdge Admin courses, they
are
very educational and you will learn much more directly from the source
instead of filtered through Epicor.
4. What is causing it to grow so fast? Lots of transactions on the
database.
once every 2 months. The one performance gain that we get is that the
database will start up much faster than when the bi file is large.
From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com] On Behalf
Of Ned
Sent: Thursday, August 20, 2009 8:37 AM
To: vantage@yahoogroups.com
Subject: Re: [Vantage] Bi or B1 File
1. What is in the Bi/B1 file? The BI/B1 file is the "Before-Image" File,
which is why it is called BI. It is a B1 in the directory because that
is
the first BI file. It is possible through advanced Progress techniques
to
break up the BI File into multiple files(B1, B2, B3), yes it can be done
but
it is not supported through Epicor, but it can increase performance in a
progress DB to go more granular, but it is a lot of work and takes a lot
of
knowledge. Same can be done with the datafile(D1, D2, D3) What happens
is
basically this...
You have information in a record in a table in the database, let's call
this
Data A. Then you have changes to that record you want to write to the
Database, we can call this Data B. When you want to commit those changes
of
Data B, Progress will copy Data A to the BI file, then write Data B to
the
database.
Simply put, BI is the Progress version of transaction logs of data that
was
replaced which can be used to roll back the DB. Conversely, there are
also
what are known as "After Image", or AI/A1 files which do almost the same
thing as the Before Image, only they are copies of Data B in the
previously
mentioned scenario, this is not setup by default in the system, but it
is
reccomended to be setup. The combination of these 2 file types give you
a
full and complete transaction log. Which can be used to roll forward or
backward your DB in Progress/OpenEdge.
2. Does the growing size cause performance issues? Easy answer, no, not
really. However, performance can be improved by putting the D1, A1, and
B1
files on different physical disks due to bottlenecks in I/O which is
really
the cause of the performance hits.
3. Is there a way to manage it? There are ways through the Progress
command
line tools to manage it, if you have interest in that then I would
suggest
going directly to Progress and taking their OpenEdge Admin courses, they
are
very educational and you will learn much more directly from the source
instead of filtered through Epicor.
4. What is causing it to grow so fast? Lots of transactions on the
database.
----- Original Message -----
From: "jplehr" <jlehr@... <mailto:jlehr%40astromfg.com> >
To: <vantage@yahoogroups.com <mailto:vantage%40yahoogroups.com> >
Sent: Thursday, August 20, 2009 8:59 AM
Subject: [Vantage] Bi or B1 File
> Vantage 8.03.408A
>
> I am currious if anyone can provide some insight to the Bi/B1 file
found
> in the database folder? I list this as Bi/B1 because it is the B1
within
> your database directory, but it is also refered to as the Bi... go
figure.
>
> Issue is that my database recently shut down and it was due to the
total
> size of the database (and all surrounding files... I assume). At that
time
> the database was approximately 1.3 GB and the Bi/B1 was 2+ GB. With
> supports help we truncated the Bi/B1 and then went through the process
to
> allow large file sizes. Apparently I will not have this issue again.
>
> However, I now see the Bi/B1 file grow uncontrollably. I have been
seeing
> some performance issues. Although, these issue have come from
personnel
> performing manual Labor Entry (not MES). Epicor Support has provided
me
> with a 1-off fix, which appeared to resolve the Labor Entry issue...
until
> today.
>
> So, I looked at the Bi/B1 file and it is 4+ GB and I just truncated
it,
> again, this past weekend.
>
> Questions...
> 1. What is in the Bi/B1 file?
> 2. Does the growing size cause performance issues?
> 3. Is there a way to manage it?
> 4. What is causing it to grow so fast?
>
> Jeff
>
>
>
> ------------------------------------
>
> Useful links for the Yahoo!Groups Vantage Board are: ( Note: You must
> have already linked your email address to a yahoo id to enable access.
)
> (1) To access the Files Section of our Yahoo!Group for Report Builder
and
> Crystal Reports and other 'goodies', please goto:
> http://groups.yahoo.com/group/vantage/files/.
<http://groups.yahoo.com/group/vantage/files/>
> (2) To search through old msg's goto:
> http://groups.yahoo.com/group/vantage/messages
> (3) To view links to Vendors that provide Vantage services goto:
> http://groups.yahoo.com/group/vantage/linksYahoo! Groups Links
>
>
>
[Non-text portions of this message have been removed]