Oracle Securefile Validation errors in Oracle 19C

Products

• Data Loss Prevention Enforce
• Data Loss Prevention Oracle Standard Edition 2

Issue/Introduction

URT output shows warnings for Oracle Securefile Validation in Oracle 19C:

Start: Oracle Securefile Validation
Table name Column name Tablespace name
------------------------------ ------------------------------ ------------------------------
CONDITIONVIOLATIONLOB CRACKEDCOMPONENTMARKERS USERS
MESSAGECOMPONENTLOB UNCRACKEDCOMPONENT USERS
MESSAGECOMPONENTLOB CRACKEDCOMPONENT USERS
MESSAGELOB NETWORKORIGINALMESSAGE USERS
*** Basicfile LOB Storage detected ***
*** Enforce will run inefficiently and LOB space will not be reclaimed ***
*** Please refer to the Support Center article below for details about LOB storage handling ***
*** https://knowledge.broadcom.com/external/article?legacyId=TECH252716 ***
End : Oracle Securefile Validation - elapsed .06s - WARNING (0 errors, 4 warnings)

Environment

Oracle 19C

Cause

These tables are using BasicFiles LOB storage

Resolution

1. If you’re not utilizing blob externalization(External storage for incident attachments), a critical task is to convert these four LOBs to use SecureFiles.

2. It is critical because BasicFiles LOB storage does not allow for effective reused of the LOB space as incidents are deleted causing new incidents to need new space allocated to the lob data instead of using the space taken up by previous LOB data within the same segment. As these 4 LOB segments contain the bulk of the data from incidents they carry a significant impact to the size of tablespace. This is further complicated given that these 4 LOB segments were deliberately moved out of the LOB_TABLESPACE to the USERS tablespace causing quite a bit of fragmentation within the USERS tablespace.

3. If these tables are empty and you’re utilizing blob externalization, the mentioned errors can be disregarded. However, even in that scenario, it’s advisable to switch these four LOB segments to use SecureFiles. Doing so would eliminate the need to verify this during every upgrade.

4. If you’re using Oracle Enterprise version, there are straightforward commands to switch these segments to SecureFiles. However, this process necessitates a significant amount of available space within the tablespace. Oracle will rebuild the segments in the background and then transition to the rebuilt segment once the conversion is complete. Your database administrator (DBA) should be well-versed in using Oracle’s online redefinition function to address this.

5. If you are using Oracle Standard version, then following the instructions provided in this article.