Sbspace logging
When an sbspace is logged, the database server slows down, and the logical logs fill up quickly. If you use logging for sbspaces, you must ensure that the logical logs are large enough to hold the logging data. For more information, see Estimate the log size when logging smart large objects.
When you
turn on logging for a database, the database server does not begin
logging until you perform a level-0 backup. However, when you turn
on logging for a smart large object, the database server begins logging
changes to it immediately. To reduce the volume of log entries, load
smart large objects with logging turned off and then turn logging
back on to capture updates to the smart large objects.
Important: When you turn logging on for a smart large object,
you must immediately perform a level-0 backup to be able to recover
and restore the smart large object.
For more information, see Back up sbspaces and the HCL OneDB™ Backup and Restore Guide.