Symptom
- The 'sp_rename' command can rename a table even if there is an open transaction against it.
- After renaming the table, the transaction remains open, but the table is no longer accessible under its original name.
- A warning is displayed stating that changing an object or column name could break existing stored procedures, cached statements, or other compiled objects.
Image/data in this KBA is from SAP internal systems, sample data, or demo systems. Any resemblance to real data is purely coincidental.
Read more...
Environment
SAP Adaptive Server Enterprise 16.0 and later
Product
SAP Adaptive Server Enterprise 16.0 ; SAP Adaptive Server Enterprise 16.1
Keywords
sp_rename, rename table, open transaction, SAP ASE, sysobjects, metadata lock, table name change, stored procedures, cached statements, compiled objects, exclusive lock, active transactions , KBA , BC-SYB-ASE , Sybase ASE Database Platform (non Business Suite) , Known Error
About this page
This is a preview of a SAP Knowledge Base Article. Click more to access the full version on SAP for Me (Login required).Search for additional results
Visit SAP Support Portal's SAP Notes and KBA Search.
SAP Knowledge Base Article - Preview