- Even before starting the upgrade, it is better to check whether the assignment of container is correct. This can be done with the help of following SAP note which gives the correct mapping between data classs (TABART) and tablespaces:
541542: Upgrade phase INIT_CNTRANS: Container inconsistency
777615: Incorrect data class/database container assignment
778784: Inconsistencies between data class and database container
If you find any discrepancy, it is better to correct before the upgrade than having an error during upgrade.
- The upgrade may fail even if the mapping is correct but not as per note 541542. In such cases, it is fine to ignore and proceed if the tool permits. If you are not able to proceed, search for notes or KBA's or raise a message with SAP. Few known issues are mentioned in following notes/KBA's:
1589777: Missing owner in menu "System -> Status"
946135: Error in RSUPDTEC creates incorrect entries in IAORA
- If the upgrade is finished and when you go to delete the old tablespace, it doesn't allow you as there are still objects left in it. In such cases, do not delete using force mode and check for objects under the tablespace using following SQL query:
select table_name from dba_tables where tablespace_name='PSAPSR3<OLDREL>';
select index_name from dba_indexes where tablespace_name='PSAPSR3<OLDREL>';
You may need to do a reorg for these objects using brtools in order to move the objects to correct tablespaces. Following KBA talks about the situation and helps to resolve such issues:
1715052: tablespace cannot be deleted after upgrade