Kbase 17016: BI growth when connecting to db through Report Builder
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
10/05/1998 |
|
BI growth when connecting to db through Report Builder
When connecting to a database through Report Builder on a windows
client, the connection becomes a transaction against the database that
lasts for the duration of the client session, and causes the bi file
to grow.
The transaction is visible in promon->user control->display,
then look at the transaction column. There will be a number for the
remote user upon login.
The result of this behavior is the bi file treating the user
session as one continuous transaction. Login is the begin note, and
and the logout is the anticipated end note. The end note is not
written to the bi until the logout, therefore none of the bi clusters
are reused. If we don't reuse the clusters and keep getting new ones,
this causes the bi file to grow for the life of the session. This is
a concern especially if the bi file approaches the 2 gig file size
limit.
This is a result of Report Builder's use of ESQL to access the
database as it calls sqllogin() when connecting. After this is called,
this transaction is active and remains so until it is committed, which
doesn't occur until the session is ended.
This is a client problem that is a direct result of a remote
client connecting to a database through Report Builder. The version
and platform of the server should not be an issue (provided the client
and server are compatible).
This has been fixed in version 8.1C Report Builder.
The fix consists of two parts. The first part ends the transaction
as soon as Report Builder starts up (a call is made to sqlrollback
after calls to sqllogin, sqlconn and after each fetch for
metaschema). The second part of the fix comes into play after a
report is printed or previewed. When printing or previewing a
new transaction is started. This new transaction will not
end unless a new startup parameter is used. This new parameter is
-rbclearxactions and should be specified on the command line where
Report Builder is started or in the rbstart.pf file.
For example,
prorb.exe -db sports -rbclearxactions
See also the following related Kbases:
15124 Why is my .bi file getting so big ?
17368 How to fix Esql application that causes bi file to grow
This has been logged as bug 96-09-06-015.
Progress Software Technical Support Note # 17016