Error using OE Explorer Data Administration - Enable Multi-tenancy for Tables - Forum - OpenEdge Deployment - Progress Community

Error using OE Explorer Data Administration - Enable Multi-tenancy for Tables

 Forum

Error using OE Explorer Data Administration - Enable Multi-tenancy for Tables

This question is answered

Hi All 

I have created a multi-tenanted DB with TYPE II storage areas one for data and one for index.

When i manage the DB in the OE Explorer DB admin area and use the Enable Multi-tenancy for Tables option i get the following error:

Attached is the ST and the DF for the database.

Thanks

Christian.

Verified Answer
  • Progress Support sorted this:

    Hi Christian,

    The reported issue seems to be a known issue mentioned in KB 000042621.

    000042621,OpenEdge Explorer cannot complete multitenancy enabling of table and no warning or error is given why the enablement does not succeed when any portion of the table (such as a lob or clob field) is in Type I area.

    https://knowledgebase.progress.com/articles/Article/000042621

    You have to move the blob / clob data to a Type II area.

    The article is somewhat old and needs to be updated which I will do. If you have any additional questions regarding this case then please let me know.

    Thanks,
    Waqas

  • Progress support resolved this for me:

    Hi Christian,

    The reported  issue seems to be a known issue mentioned in KB 000042621.

    000042621,OpenEdge Explorer cannot complete multitenancy enabling of table and no warning or error is given why the enablement does not succeed when any portion of the table (such as a lob or clob field) is in Type I area.

    knowledgebase.progress.com/.../000042621

    You have to move the blob / clob data to a Type II area.

    The article is somewhat old and needs to be updated which I will do. If you have any additional questions regarding this case then please let me know.

    Thanks,

    Waqas

  • Progress Support sorted this:

    Hi Christian,

    The reported  issue seems to be a known issue mentioned in KB 000042621.

    000042621,OpenEdge Explorer cannot complete multitenancy enabling of table and no warning or error is given why the enablement does not succeed when any portion of the table (such as a lob or clob field) is in Type I area.

    knowledgebase.progress.com/.../000042621

    You have to move the blob / clob data to a Type II area.

    The article is somewhat old and needs to be updated which I will do. If you have any additional questions regarding this case then please let me know.

    Thanks,

    Waqas

  • Hi Christian,

    The reported  issue seems to be a known issue mentioned in KB 000042621.

    000042621,OpenEdge Explorer cannot complete multitenancy enabling of table and no warning or error is given why the enablement does not succeed when any portion of the table (such as a lob or clob field) is in Type I area.

    knowledgebase.progress.com/.../000042621

    You have to move the blob / clob data to a Type II area.

    The article is somewhat old and needs to be updated which I will do. If you have any additional questions regarding this case then please let me know.

    Thanks,

    Waqas

All Replies
  • Progress Support sorted this:

    Hi Christian,

    The reported issue seems to be a known issue mentioned in KB 000042621.

    000042621,OpenEdge Explorer cannot complete multitenancy enabling of table and no warning or error is given why the enablement does not succeed when any portion of the table (such as a lob or clob field) is in Type I area.

    https://knowledgebase.progress.com/articles/Article/000042621

    You have to move the blob / clob data to a Type II area.

    The article is somewhat old and needs to be updated which I will do. If you have any additional questions regarding this case then please let me know.

    Thanks,
    Waqas

  • Progress support resolved this for me:

    Hi Christian,

    The reported  issue seems to be a known issue mentioned in KB 000042621.

    000042621,OpenEdge Explorer cannot complete multitenancy enabling of table and no warning or error is given why the enablement does not succeed when any portion of the table (such as a lob or clob field) is in Type I area.

    knowledgebase.progress.com/.../000042621

    You have to move the blob / clob data to a Type II area.

    The article is somewhat old and needs to be updated which I will do. If you have any additional questions regarding this case then please let me know.

    Thanks,

    Waqas

  • Progress Support sorted this:

    Hi Christian,

    The reported  issue seems to be a known issue mentioned in KB 000042621.

    000042621,OpenEdge Explorer cannot complete multitenancy enabling of table and no warning or error is given why the enablement does not succeed when any portion of the table (such as a lob or clob field) is in Type I area.

    knowledgebase.progress.com/.../000042621

    You have to move the blob / clob data to a Type II area.

    The article is somewhat old and needs to be updated which I will do. If you have any additional questions regarding this case then please let me know.

    Thanks,

    Waqas

  • Hi Christian,

    The reported  issue seems to be a known issue mentioned in KB 000042621.

    000042621,OpenEdge Explorer cannot complete multitenancy enabling of table and no warning or error is given why the enablement does not succeed when any portion of the table (such as a lob or clob field) is in Type I area.

    knowledgebase.progress.com/.../000042621

    You have to move the blob / clob data to a Type II area.

    The article is somewhat old and needs to be updated which I will do. If you have any additional questions regarding this case then please let me know.

    Thanks,

    Waqas

  • Indexes have to be in type ii data areas too. These days, with or without partitioning, except for the schema tables, NOTHING should be in type i data areas. tables and indexes should be in separate areas.

    Note that the areas housing the partitioned table segments and indexes must have enough storage allocated or available for expansion to accomodate each new tenant.