Start of change

-4743 ATTEMPT TO USE NEW FUNCTION WHEN THE APPLICATION COMPATIBILITY SETTING IS SET FOR A PREVIOUS LEVEL

Explanation

An application or SQL object attempted to use a Db2 capability that is not supported by the current application compatibility level. Before the activation of function level 500 or higher, Db2 environments can use application compatibility levels for previous releases. After the activation of function level 500 or higher, the application compatibility level can be equivalent to the current function level, lower function levels in the current release, or previous releases.

Start of changeThis message is issued for a data definition statement that specifies functionality, or attempts to alter an existing object definition, that requires a higher application compatibility setting than is currently in use.End of change

If the message is issued for a CREATE TRIGGER or ALTER TRIGGER statement and the application compatibility level is V11R1 or lower, the following situations might apply:

  • The trigger body contains an SQL PL statement.
  • The trigger body contains an SQL statement that was not allowed in a trigger body in Db2 11.
  • The MODE DB2SQL clause is not present.
  • An unsupported trigger option that was not allowed in Db2 11 was specified. The only trigger options that are allowed in Db2 11 are SECURED and NOT SECURED.

This message can be issued for an ALTER statement if the CURRENT APPLICATION COMPATIBILITY special register value is lower than the application compatibility level of the existing object definition. Altering an object might result in this error even if the content of the ALTER statement is valid at the current level. The errors can occur when the existing object definition contains some functionality that requires a higher level than the CURRENT APPLICATION COMPATIBILITY special register setting.

System action

The statement cannot be processed.

Programmer response

Check the application compatibility level of your application or SQL object, and take one of the following actions:
  • Rebind the application or modify the SQL object to use an application compatibility level that supports the capability.
  • Remove use of the unsupported capability from the application or SQL object.

For details, see Application compatibility levels in Db2.

SQLSTATE

56038

End of change