Since the introduction of a Version N-1 or N-2 Support Policy, all instances should now be using the Table-Per-Partition Extended Table method for the Configuration Management Database's (CMDB) underlying SQL database structure.
|Version||Application Tables||SQL Tables||Extended Table/Flattening Method|
|<= Fuji||cmdb_ci, and all extending tables||cmdb_ci, cmdb_ci_hardware, cmdb_ci_computer, etc.||Table-Per-Class|
|>= Geneva|| cmdb, and all extending tables, including cmdb_ci|
A 'cmdb' table was slotted in above 'cmdb_ci' to become the new parent table.
|cmdb, cmdb_ci, cmdb_ci_hardware, cmdb_ci_computer, etc.||Table-Per-Class|
|>= Jakarta||Unchanged||cmdb + cmdb$par1 [ + cmdb$par2 ]||Table-Per-Partition|
A lot of CMDB-related code in more recent versions expects this to have happened. Problems and data loss can in theory occur if this is not done. Please open an Incident with Customer Support if you notice this has not happened in your instance.
Did Geneva Re-Parenting happen?
- Open a list for the 'cmdb_ci' table
- Open a list for the 'cmdb' table
- If cmdb_ci lists lots of records, and cmdb lists none, or doesn't even load a list view, then Geneva Re-Parenting has not happened.
Did Jakarta TPP Migration happen?
- Open the Tables table list:
- Search for a table in that list with name=cmdb$par1
- If cmdb$par1 is not listed then TPP Migration has not happened.
Post Geneva and/or Jakarta.