DSNT286I csect-name bind-type FOR object-type  = object-name, USE OF APREUSE RESULTS IN count-1 STATEMENTS WHERE APREUSE IS SUCCESSFUL count-2 STATEMENTS WHERE APREUSE IS EITHER NOT SUCCESSFUL OR PARTIALLY SUCCESSFUL count-3 STATEMENTS WHERE APREUSE COULD NOT BE PERFORMED count-4 STATEMENTS WHERE APREUSE WAS SUPPRESSED BY OTHER HINTS.

Explanation

This message reports information about the reuse of access paths.

csect-name
The name of the control section that issued the message.
bind-type
The type of bind subcommand: BIND or REBIND
object-name
Start of changeThe type of object: PACKAGE or SERVICEEnd of change
object-name
Start of changeThe name of the PACKAGE or SERVICE in the format location-id.collection-id.package-id or location-id.collection-id.service-name.End of change
count-1
The number of statements where the previous the access path was successfully applied.
count-2
The number of statements where the previous access path could not be applied. Reuse fails for the package when this value is not zero.
count-3
The number of statements where the previous access path could not be reused. This situation happens either because the previous access path was not found or because a new access path was not generated. Some common reasons are that the query used REOPT(ALWAYS) or VALIDATE(RUN) bind behavior, or the package was bound before DB2 9.
count-4
The number of statements where the previous access path was not used because of the use of other types of hints such as PLAN_TABLE or SYSIBM.SYSQUERYPLAN hints.

The sum of the total counters in message DSNT286I might be larger than the number of static statements in the package. The sum of counters is equal to number of the statements in the SYSIBM.SYSPACKSTMT table. If the sum is larger than the number of static statements in the package, one or more statements might have been bound twice, which occurs in the following situations:

  • SYSTIMESENSITIVE is set to YES, and the statement references a system-period temporal table or bitemporal table.
  • The ARCHIVESENSITIVE bind option is set to YES, and the statement references an archive table.

For more information about why these statements are bound twice, see the APREUSE bind option information.

System action

The command terminates and no changes are applied.

User response

Determine whether the APREUSE usage reported in the message matches the expected result. If EXPLAIN(YES) or EXPLAIN(ONLY) was used, refer to the PLAN_TABLE.HINT_USED column for more information about individual statements.