You are setting up your Oracle database server and want to know if you can use the Partitioning and Compression Options available?
Partitioning is a feature that comes with Oracle Enterprise Edition only and involves the subdivision of tables and indexes by date, type, or "hash", the idea being that the logicial subgroup would provide an extra indice of sorting making queries zippier. They also provide a methodology of archiving data.
That the opportunity to have partitioning (that particular module) is present, there is no foreseeable problem. Partitioning comes with Oracle Enterprise Edition (not supported at this time). DLP does not use it, therefore, it is a non-issue.
Partitioning, conceptually and done properly, ought to be transparent to the database user. It’s something that lives on the RDBMS side of things. When something is selected, inserted, updated or deleted, the expectation is that the we need to only state the table and/or the data and don’t really care where Oracle has stashed anything.
Problems would most likely arise if partitions are “pruned” or “archived”. The DLP schema would become inconsistent.
The ability to archive incidents, (…no, really archive incidents) has long been anticipated by all. The very complex manner in which DLP stores messages and incidents prevents that from being included for years to come.
Partitioning the LOB_TABLESPACE will put a customer in a seriously unsupported bind if their system fails. DLP is not made to anticipate partitioning as a feature, it’s not certified, and they will be referred to Oracle, or will have to recreate their issue in a supported platform and configuration.
The DLP product is currently only supported with Oracle Standard Edition and where partitioning is explicitly not supported.
Oracle Compression is similarly unsupported as it does not appear in the Oracle Standard Edition. Compression has not been tested or certified in use with DLP.
Imported Document ID: TECH222013
Subscribing will provide email updates when this Article is updated. Login is required.