How To Fix DB6PM235 - Containers cannot be added to tablespaces managed by automatic storage

SAP Error Message - Details

• Message type: E = Error

• Message class: DB6PM - DB2 UDB for UNIX, Windows: Performance Monitoring

• Message number: 235

• Message text: Containers cannot be added to tablespaces managed by automatic storage

Self-Explanatory Message

Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of messages in the SAP system have a message text, however this is frequently insufficient to comprehend or resolve the problem.

To make things easier, more detailed information is frequently added to describe the issue, how to fix it, and the necessary steps or configuration modifications.

Unfortunately, there isn't any extra information in this error notice.

What else can you do?

First, use our AnswerBot below to get a possible cause and solution (requires a premium subscription).

Also, review the in-depth Common Questions & Answers listed below; you could discover a solution there or be able to connect with others who have faced similar challenges.

You can also try searching the SAP support portal (support.sap.com) but you need a special user ID to access it. It is possible that an SAP support note exists that provides additional details about the mistake or even steps for fixing it.

Smart SAP Assistant

• What is the cause and solution for SAP error message DB6PM235 - Containers cannot be added to tablespaces managed by automatic storage ?

  The SAP error message DB6PM235 indicates that there is an issue with trying to add containers (such as data files) to tablespaces that are managed by automatic storage. This typically occurs in database systems that support automatic storage management (ASM), such as Oracle.
  Cause:
  The error arises because:
  
  Automatic Storage Management (ASM): The tablespace is configured to use automatic storage management, which means that the database automatically manages the storage for the tablespace. In this mode, you cannot manually add data files or containers to the tablespace.
  Configuration Issue: There may be a misconfiguration in the database settings or the way the tablespace was created.
  
  Solution:
  To resolve this error, you can take the following steps:
  
  
  Check Tablespace Type: Verify if the tablespace is indeed managed by automatic storage. You can do this by querying the database metadata.
  SELECT tablespace_name, extent_management FROM dba_tablespaces;
  
  
  Avoid Manual Container Addition: If the tablespace is managed by automatic storage, you should not attempt to add containers manually. Instead, let the database handle the storage management.
  
  
  Use Automatic Storage Management Features: If you need to increase the storage capacity, you can:
  
  Increase the size of the existing data files if possible.
  Allow the database to automatically allocate more space as needed.
  
  
  
  Create a New Tablespace: If you need a tablespace that allows manual management, consider creating a new tablespace that is not managed by automatic storage. You can do this by specifying the appropriate parameters during the creation of the tablespace.
  Example SQL command to create a new tablespace:
  CREATE TABLESPACE new_tablespace
  DATAFILE 'new_datafile.dbf' SIZE 100M
  EXTENT MANAGEMENT LOCAL;
  
  
  Consult Documentation: Refer to the database documentation for specific commands and options related to tablespace management and automatic storage.
  
  
  Related Information:
  
  Database Documentation: Check the official documentation for your specific database version (e.g., Oracle, SAP HANA) for detailed information on tablespace management.
  SAP Notes: Look for relevant SAP Notes that may address this specific error or provide additional troubleshooting steps.
  Database Administration: If you are not familiar with database administration, consider consulting with a DBA who can assist with the configuration and management of tablespaces.
  
  By following these steps, you should be able to resolve the DB6PM235 error and manage your tablespaces effectively.