This content has been marked as final. Show 1 reply
I don't think there is an official statement for this (that I am aware of anyway) but if you look at the following parameter:
You will see one of the possible settings is:
Attempts to create all LOBs as SecureFile LOBs but creates any LOBs not in an Automatic Segment Space Managed tablespace as BasicFile LOBs, unless SECUREFILE is explicitly specified. Any BasicFile LOB storage options that are specified will be ignored and the SecureFile defaults will be used for all storage options not specified.
So, given it is possible to force lobs to be SecureFile's on creation you would have to assume it is ok to use them in association with Queue Tables payloads or Oracle would not have created a parameter setting that allowed it to happen (or you would like to think so anyway!).
Hope this helps,