CMOD table space.

[pankaj.puranik]

I recently found out that our CMOD installation doesnot use SMS table space for System Log and System Load application groups.
I am able to update these application groups and check the box for SMS.
But I am not sure if doing just this would cause the System Log and System Load application group tables to use SMS.
Is there anything else that need to be done.

Unrelated to this, the second question I have is on the default tablespace USERSPACE1.
If I have to move data entirely from USERSPACE1 to a new table space, which the DBA can easily do, where and how do I tell CMOD that the table space USERSPACE1 no more exists and that it has to use a new table space?

[Justin Derrick]

Not sure about your first question, but the answer to the second one is that CMOD doesn't care which tablespace the tables live in.  Your DBA should be able to move them without issue (providing you bring down CMOD first).  I've never done this myself, so test it out before you do it in production! 

[Mike]

I had the same problem after moving to 8.5.0.6, and we filled up the filesystem that the system logs started writing to which caused OD to stop in the middle of the day. Lovely stuff.

I haven't tried to move either of these (we just added a bunch of space for the system log and monitor it now), but I would be curious as to what your results are if you do try and move them.