SAP Knowledge Base Article - Preview

2385695 - Forceplan is ignored due to AP can't force join order - SAP ASE

Symptom

  • A query run with forceplan is picking the same plan as without forceplan when it should be forcing the join order as declared
  • A query contains no join that matches the 'join' AP operator at this point
  •  Abstract Plan (AP) Warning : An error occured while applying the AP:
    ( also_enforce ( sequence ( also_enforce ( store ( also_enforce ( values 1 ) ) ) ) ( also_enforce ( join ( also_enforce ( join ( also_enforce ( join ( also_enforce ( scan ( table ( a sysobjects ) ) ) ) ( also_enforce ( scan ( table ( b syscolumns ) ) ) )
    ) ) ( also_enforce ( scan ( table ( d syspartitions ) ) ) ) ) ) ( also_enforce ( scan dt ) ) ) ) ) )
    to the SQL query:
    select * from sysobjects a join syscolumns b on a.id=b.id left join (select 1 as col) dt on a.id=dt.col left join syspartitions d on dt.col=d.id
    Failed to apply the top operator 'join ' of the following AP fragment:
    ( join ( also_enforce ( join ( also_enforce ( scan ( table ( a sysobjects ) ) ) ) ( also_enforce ( scan ( table ( b syscolumns ) ) ) ) ) ) ( also_enforce ( scan ( table ( d syspartitions ) ) ) ) )

Read more...

Environment

  • SAP Adaptive Server Enterprise (ASE) 15.7
  • SAP Adaptive Server Enterprise (ASE) 16.0

Product

SAP Adaptive Server Enterprise 15.7 ; SAP Adaptive Server Enterprise 16.0

Keywords

forceplan, Abstract Plan, AP, join order, CR791474, CR#791474, 791474 , KBA , BC-SYB-ASE , Sybase ASE Database Platform (non Business Suite) , Problem

About this page

This is a preview of a SAP Knowledge Base Article. Click more to access the full version on SAP ONE Support launchpad (Login required).

Search for additional results

Visit SAP Support Portal's SAP Notes and KBA Search.