No new writeups yet.
1000 18 Abstract Plan (AP) Internal Error : An error occurred while looking for the AP group ID in sysattributes. If the error persists, please contact SAP Technical Support.
1001 18 Abstract Plan Internal Error : Attempting to hard-cast the non-object data structure at %1! as an APOM object. Please contact SAP Technical Support.
1002 16 Abstract Plan (AP) : The query does not contain an UNION operator to match the one in the AP expression. The AP will not be applied.
Check the AP syntax and its correspondence to the query.
1003 16 Abstract Plan (AP) : The number of operands of the UNION operator in the AP differs from the number of sides of the UNION SQL query.
The extra items will be ignored. Check the AP syntax and its correspondence to the query.
1004 16 Abstract Plan (AP) : The AP expression does not contain an UNION operator to match the one in the SQL query. The AP will not be applied.
Check the AP syntax and its correspondence to the query.
1005 16 Abstract Plan (AP) : The number of operands of the PLAN operator in the AP differs from the number of steps needed to compute the query.
The extra items will be ignored. Check the AP syntax and its correspondence to the query.
1006 16 Abstract Plan (AP) : The SQL query step does not create a work table matching the one described by the corresponding STORE operator in the AP.
This part of the AP will not be applied. Check the AP syntax and its correspondence to the query.
1007 16 Abstract Plan (AP) : The AP expression describes a bushy join tree, while the Server only supports left deep join trees. The bushy right join operand will not be applied.
Check the AP syntax.
1008 16 Abstract Plan (AP) : The SQL query step does not contain a subquery to match the subquery %d described in the AP. The subquery will be ignored.
Check the AP syntax and its correspondence to the query.
1009 16 Abstract Plan (AP) : The SQL query does not contain a base table to match the base table '%.*s' described in the AP. The base table will be ignored.
Check the AP syntax and its correspondence to the query.
1010 16 Abstract Plan (AP) : The SQL query step does not contain a work table to match the work table '%.*s' described in the AP. The work table will be ignored.
Check the AP syntax and its correspondence to the query.
1011 16 Abstract Plan (AP) : The AP expression uses the work table '%.*s', but does not define it through a STORE operator. The table will be ignored. Check the AP syntax.
1012 16 Abstract Plan (AP) : The AP expression describes the materialization of a join, while the Server only supports single table reformatting.
The operand of the STORE operator will be ignored. Check the AP syntax.
1013 16 Abstract Plan (AP) : %s; line %d, occurring near '%.*s'. Check the AP syntax.
1014 16 Abstract Plan (AP) : The correlation name '%.*s' is used in the AP expression for the table '%.*s' and in the SQL query for the table '%.*s'. The table will be ignored.
Check the AP syntax and its correspondence to the query.
1015 16 Abstract Plan (AP) : You cannot use a variable of type %s. Use CHAR, VARCHAR or TEXT instead.
1016 16 Abstract Plan (AP) : There is no destination group for the new AP. The AP was not created. Specify a destination group within the statement or enable the AP capture mode.
1017 18 Abstract Plan (AP) : sysqueryplans manager error. The operation was aborted, no AP was created or deleted.
1018 16 Abstract Plan (AP) : There is no AP group with the name '%.*s'. The AP mode settings will not be changed.
1019 16 Abstract Plan (AP) : The %s mode is already enabled for group '%.*s'. The AP mode settings will not be changed. To enable the LOAD mode for another group, disable it first.
1020 16 Abstract Plan (AP) : The REPLACE sub-mode is already enabled.
1021 16 Abstract Plan (AP) : The DUMP mode is not enabled. Adaptive Server cannot enable the REPLACE sub-mode. Enable the DUMP mode first.
1022 16 Abstract Plan (AP) : The %s mode is not currently enabled. The AP mode settings will not be changed.
1023 0 Abstract Plan (AP) : The LOAD mode is not enabled. Adaptive Server cannot enable the EXISTS CHECK sub-mode. Enable the LOAD mode first.
1024 20 Abstract Plan (AP) : Fatal error in the lexer while scanning the Abstract Plan. Please contact SAP Technical Support.
1025 16 Abstract Plan (AP) Warning : An error occured while applying the AP:
1026 16 to the SQL query:
1027 16 The following template can be used as a basis for a valid AP:
1028 16 Failed to apply the top operator '%s' of the following AP fragment:
1029 16 %.*s
1030 16 Abstract Plan (AP) Internal Error: An error occured while applying an internally generated AP. The AP implements the SQL level forced options, as forced index,
FORCEPLAN, etc. If the error persists, please contact SAP Technical Support.
1031 10 The optimizer will try to complete the compilation of this query; on success, the query will be executed normally.
1032 16 The query contains no %s that matches the '%s' AP operator at this point.
1033 16 The %s in the query expects %d children but the '%s' AP operator has %d children.
1034 16 The children of the '%s' 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.
1035 16 The AP property enforcer operators 'sort', 'xchg' or 'enforce' can be used to create the needed physical properties.
1036 16 The following AP operators are legal at this point: %s.
1037 16 When an ordering is missing, the %s peer physical operators that don't need an ordering can be used.
1038 16 Abstract Plan (AP) Warning: all FROM clause forced options (and their internally generated AP, given below) were ignored.
1039 16 Abstract Plan (AP) Warning: the FORCEPLAN and any FROM clause forced options (and their internally generated AP, given below) were ignored.
1040 16 The following AP, given in the PLAN clause, was used by the optimizer:
1041 16 The following AP, loaded from SYSQUERYPLANS, was used by the optimizer:
1042 16 The Abstract Plan (AP) of the final query execution plan:
1043 16 To experiment with the optimizer behavior, this AP can be modified and then passed to the optimizer using the PLAN clause:
SELECT/INSERT/DELETE/UPDATE ... PLAN '( ... )'.