According to SecureFiles documentation (11.2) and presentations the SecureFiles (BLOBs) do not use the CHUNK parameter in the same way as the BASICFiles: Oracle
states that chunk size is managed dynamically, and the parameter is
for SecureFiles LOBs it is an advisory size provided for backward compatibility
Some other parameters (like PCTVERSION are "not used for SecureFiles" / "ignored". Now I wonder how the CHUNK parameter influences the storage of Secure Files. Is it something like a minimum size for chunks? Or is the decision on storage really only based on other parameters, if yes, which? Is using large ASSM UNIFROM Extends and INITIAL/NEXT Extend influencing anything? (I am using no compression, encryption or deduplication).
I could imagine the advice function of the parameter is only for DBAs or application querying it, but in that case I would have used the "ignored" term, like all the other legacy storage parameters. So there must be more to it.
(I know this is not really a "general" question, but I think this is the best fit forum, as it is not really ASM, Installation, Java or SQL specific.)
Edited by: Bernd Eckenfels on Feb 23, 2013 3:43 AM - added link