Home
AdministeringIn addition to administering the database server, you can tune performance, replicate data, and archive data.
System administrationThese topics contain concepts, procedures, and reference information for database and database server administrators to use for managing and tuning HCL OneDB™ database servers.
Performance GuideThe HCL OneDB™ Performance Guide describes how to configure and operate your HCL OneDB™ database server to improve overall system throughput and to improve the performance of SQL queries.
LockingThe database server uses locks, which can affect concurrency and performance. You can monitor and administer locks.
Locks for smart large objectsSmart large objects have several unique locking behaviors because their columns are typically much larger than other columns in a table.
Byte-range lockingRather than locking the entire smart large object, you can lock only a specific byte range of a smart large object.
How the database server manages byte-range locksThe database server manages byte-range locks in the lock table in a similar fashion to other locks placed on rows, pages, and tables. However, the lock table must also store the byte range.

How the database server manages byte-range locks

The database server manages byte-range locks in the lock table in a similar fashion to other locks placed on rows, pages, and tables. However, the lock table must also store the byte range.

If you place a second lock on a byte range adjacent to a byte range that is currently locked, the database server consolidates the two locks into one lock on the entire range.

If a user holds locks that the Example of byte-range locking shows, and the user requests a lock on byte five, the database server consolidates the locks placed on bytes two through six into one lock.

Likewise, if a user unlocks only a portion of the bytes included within a byte-range lock, the database server might be split into multiple byte-range locks. In the Example of byte-range locking the user could unlock byte three, which causes the database server to change the one lock on bytes two through four to one lock on byte two and one lock on byte four.