Environment
Novell ZENworks 7
Desktop Management
Novell ZENworks 6.5 Desktop Management
Novell ZENworks 7 Server Management
Novell ZENworks 6.5 Server Management
Oracle 9i Database
Novell ZENworks 6.5 Desktop Management
Novell ZENworks 7 Server Management
Novell ZENworks 6.5 Server Management
Oracle 9i Database
Situation
Storer error
shows up in the log when using an Oracle Server for Inventory
Within the inventory log the following errors show up when using Oracle as the inventory database:
[1/11/07 12:02:45.118] ZENInv - Storer: Info : Making this connection level TRANSACTION_READ_UNCOMMITTED for Dirty read
[1/11/07 12:02:45.118] ZENInv - Storer: Error : In making connection level TRANSACTION_READ_UNCOMMITTED
Within the inventory log the following errors show up when using Oracle as the inventory database:
[1/11/07 12:02:45.118] ZENInv - Storer: Info : Making this connection level TRANSACTION_READ_UNCOMMITTED for Dirty read
[1/11/07 12:02:45.118] ZENInv - Storer: Error : In making connection level TRANSACTION_READ_UNCOMMITTED
Resolution
The Jdbc
TRANSACTION_READ_UNCOMMITTED corresponds to the ANSI/ISO SQL
standard READ UNCOMMITTED Isolation level.
When a database transaction is set to READ UNCOMMITTED, it provides for a non-blocking data read and thus better performance. But this means that if not handled properly, there is a possibility of reading dirty/corrupt data.
MS SQL and Sybase have support for the READ UNCOMMITTED Isolation level, but Oracle doesn't support it, as the reads in Oracle are non-blocking by default.
The error will show up when inventory is running with an Oracle database, this error message is cosmetic and can be ignored.
When a database transaction is set to READ UNCOMMITTED, it provides for a non-blocking data read and thus better performance. But this means that if not handled properly, there is a possibility of reading dirty/corrupt data.
MS SQL and Sybase have support for the READ UNCOMMITTED Isolation level, but Oracle doesn't support it, as the reads in Oracle are non-blocking by default.
The error will show up when inventory is running with an Oracle database, this error message is cosmetic and can be ignored.