When running a CIS update query, the ASE will check the query for any of the updatable columns being used in table joins and/or search arguments then make decisions about the execution plan accordingly. There is an error in this logic such that join columns and search columns get confused by ASE which can result in an incorrect execution plan or the rejection of a valid abstract plan. This can lead to poor performance. For example, a valid abstract plan might give an error like this:
Abstract Plan (AP) Warning : An error occured while applying the AP:
<your plan here>
The children of the <your join operator> operator don't have the required properties, as ordering, partitioning. The logical relational operation is valid at this point but it can not be implemented by this physical operator.
The AP property enforcer operators 'sort', 'xchg' or 'enforce' can be used to create the needed physical properties.
There may also be a suggested template abstract plan in the error message which also gives the same error.
- SAP Adaptive Server Enterprise (ASE) 16.0 (15.7 unaffected)
- SAP Adaptive Server Enterprise Cluster Edition (ASE CE) 16.0 (15.7 unaffected)
- Component Integration Services (CIS)
Sybase, ASEServer, SAPASE, dataserver, CR817834, CR#817834 , KBA , BC-SYB-ASE , Sybase ASE Database Platform (non Business Suite) , BC-SYB-ASE-CE , ASE Cluster Edition (Standalone) , Problem
About this pageThis 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.