To answer this question, you need to understand the concept of LOCKSIZE in the context of databases. LOCKSIZE determines the level at which locks are acquired and released during data modification operations.
Let's go through each option to understand why it is correct or incorrect:
Option A) Database - This option is incorrect because LOCKSIZE is not applicable at the database level. LOCKSIZE is set at a more granular level, such as tablespace, table, or view.
Option B) Tablespace - This option is correct because LOCKSIZE can be set at the tablespace level. By specifying the LOCKSIZE at the tablespace level, you can control how locks are acquired and released for tables within that tablespace.
Option C) Table - This option is correct because LOCKSIZE can also be set at the table level. By specifying the LOCKSIZE at the table level, you can control how locks are acquired and released for that particular table.
Option D) View - This option is incorrect because LOCKSIZE is not applicable at the view level. LOCKSIZE is typically associated with physical data structures like tablespace or table.
The correct answer is B and C. These options are correct because LOCKSIZE can be set at the tablespace and table levels to control how locks are acquired and released during data modification operations.