In DB2 9.7, file system caching is turned OFF for all tablespaces by
default, except for the System Temporary Tablespace created by default when
a database is created.

I understand why file system caching should be turned ON when there is a
separate tablespace used for LOB objects that don't use bufferpools. But why
is it turned ON for system temporary tablespace created by default? Are they
assuming that there may be some LOB's in system temporary tablespaces, or is
there some other reason?

Does it have anything to do with the fact that the default system temporary
tablespace is SMS rather than DMS?

On Oct 6, 10:52*am, "Martin" <n... (AT) none (DOT) com> wrote:

I have the same question for years though I never try to think it
deeply.

I'm a DMS on device lover. I don't care the advantage of Filesystem
SMS temperary tablespace that it only use as much storage as needed.
Manage device is no more difficult and it is even harder for sb. to
delete them by mistake.