Logging

When you create an sbspace, you can specify whether to turn on logging for the smart large objects.

The default is no logging. For more information, see Log sbspaces and smart large objects.

Important: When you use logging databases, turn logging on for the sbspaces. If a failure occurs that requires log recovery, you can keep the smart large objects consistent with the rest of the database.

You specify the logging status with the LOGGING tag of the onspaces -c -Df option. The default is LOGGING=off. You can change the logging status with the onspaces -c -Df option. You can override this logging status with the PUT clause in the SQL statements CREATE TABLE or ALTER TABLE. For more information about these SQL statements, see the HCL OneDB™ Guide to SQL: Syntax.

The programmer can override this logging status with functions that the DataBlade® API and provide. For more information about the DataBlade API functions for smart large objects, see the HCL OneDB DataBlade API Function Reference. For more information about the functions for smart large objects, see the HCL OneDB ESQL/C Programmer's Manual.

When you turn on logging for an sbspace, the smart large objects pass through the resident portion of shared memory. Although applications can retrieve pieces of a smart large object, you still must consider the larger size of data that might pass through the buffer pool and logical-log buffers. For more information, see Access smart large objects.