This content has been marked as final. Show 4 replies
We are using basic compression behind the scenes. Users don't need to do anything.
For the tables in your own schema, you can add "compress" to the create table DDLs.
An example can be found in slide #34 of the following document.
If you have license for OLTP compression, then you can certainly turn it on for application table
creation or staging table creation. Please see section 7.2.2 of the following document
Compressing the triple tables is highly recommanded for performance and storage reasons.
However, if you are to enable versionning with Workspace Manager, it will fail during dbms_wm.disableversioning
because the command dbms_wm.enableversioning only partially (with no exception) creates necessary oracle objects (triggers,...) on a compressed table.
Full explanation is here [http://oracle-plsql10g.blogspot.com/2011/11/ora-20231-failed-during.html].
(I'm not the author but I have had the same problem as described in the article).
So, always compress triple table except if you use WM.
Which DB version are you using?
I had a conversation with Oracle Workspace Manager dev team and I was told that the bug has been fixed in 188.8.131.52.
I have reproduced the error (with exactly the same procedure as described in the above link)
using Oracle Enterprise Edition *184.108.40.206.0*, on Windows and Linux OS.
Hopefully, my a RDF Model is of medium size (50 millions triples), and I have had no significant negative impact on performances without compressing.