Solution : https://service.sap.com/sap/support/notes/24864 (SAP Service marketplace login required)
Summary :
During SAP upgrade or support package import, converting the BSEG table may lead to prolonged execution times, terminations from insufficient database memory, or issues in old releases due to field count exceeding database limits (e.g., Oracle versions below 8.1024 encountering 'ORA-1792'). Problems primarily stem from trying to make significant structural changes like field deletions or additions. Effective solutions involve avoiding these modifications or managing field lists accurately to prevent or correct unwarranted conversions using tools like SE14 and ensuring transaction SE11 settings are correctly reset before proceeding with upgrades, particularly in systems with SAP_BASIS below 7.00.
Key words :
upgrade phase pcon_<release>, spam/saint activation phase, missing primary index increases, large sap cluster table, activation errors lead, standard sap system, extremely large amount, customer-specific appends, oracle versions lower, happen indirectly due
Related Notes :
| 315377 | Additional information about upgrading to 3.1I SR1 |
| 202169 | Additional Info: Upgrade to 4.6C - DB2/400 |
| 178823 | Additional Information: Upgrade to 4.6B - DB2/400 |
| 162117 | Additional Information: Upgrade to 4.6A - DB2/400 |
| 141661 | Additional Info: Upgrading to 4.5B DB2/400 |
| 108377 | Additional Info: Upgrading to 4.5A DB2/400 |
| 99379 | Additional Info: Upgrading to 4.0B DB2/400 |
| 91594 | Additional Info: Upgrading to Release 3.1I |
| 90922 | Restarting pool/cluster conversions |
| 76604 | Additional Info: Upgrading to 3.1H |
| 64570 | Additional Info: Upgrading to 3.1G |
| 48632 | Additional Info: Upgrading to 3.0F |
| 43288 | Additional Info: Upgrading to 3.0E |
| 37387 | Additional Info: Upgrading to 3.0D |
| 33004 | Additional Info: Upgrading to 3.0C |