Support Article
CMD tablespace memory issue
SA-30680
Summary
Bussiness is currently facing issues with the tablespace, which is used by Marketing Director.
It is almost full and business needs to execute important campaigns with lots of clients. While searching for options to clean up some space they found some tables, which they could not relate to any Object in the Marketing Director.
For example user found 139 table name like CS1602_....., which are using quite much space. But user did not know to which object they belong. According to user knowledge, they suspect it to be belonging to Campaign 1602. But there is no campaign 1602 available anymore.
User seeks support help to know, if it is safe to delete these tables or if they are referenced somehow.
Error Messages
Not applicable
Steps to Reproduce
Not applicable
Root Cause
Below tables are created for trigger segment:
CS1602_1002_0_1
CS1602_1094_0_6
CS1602_1096_0_11
CS1602_1109_0_4
The naming convention for above tables is: CS<seg_id>_<camp_id>_0_<camp_cyc>
Resolution
Generally it is not recommended to delete above mentioned tables (CSxxx_) manually. It is because, these tables will be left out in Database if the cycle has not yet completed and deleted automatically when the respective cycle completed.
User is suggested to use “Purge Scripts” to delete unused/orphaned objects from CMD schema.
Published December 1, 2016 - Updated December 2, 2021
Have a question? Get answers now.
Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.