Kbase P131224: Business Objects Enterprise applies share-locks to database tables despite Read Uncommitted Isolatio
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
5/6/2008 |
|
Status: Unverified
FACT(s) (Environment):
Crystal
All Supported Operating Systems
SYMPTOM(s):
Business Objects Enterprise XI (11.5)
Using Business Objects Enterprise for reporting
PROMON displays share-locks generated by the SQL-92 user using Business Objects
ODBC DSN has Default Isolation Level set to Read Uncommitted
CAUSE:
The share-locks seen in PROMON are caused by Business Objects Enterprise overriding the Default Isolation Level used by ODBC DSN
FIX:
The following steps are derived from Business Objects article 18864.
1) Backup the current version of file ODBC.SBO, located here by default:
C:\Program Files\business Objects\businessObjects Enterprise 11.5\win32_x86\dataAccess\connectionServer\odbc
2) Differing from article 18864, the current version of ODBC.SBO is XML-based. The equivalent modification is:
<Parameter Name="Transaction Isolation Level">READ UNCOMMITTED</Parameter>
3) Add this line to the following sections in the ODBC.SBO file:
Defaults
Generic ODBC datasource
Generic ODBC3 datasource
4) After making the changes, restart the Business Objects Enterprise instances and re-test the report(s) generating the locks