Ansicht
Dokumentation

SQL0428 - SQL statement cannot be run. ( OS/400 )

BAL_S_LOG - Application Log: Log header data   Addresses (Business Address Services)  
This documentation is copyright by IBM.


Message : SQL0428
SQL statement cannot be run.

Message Long Text :

Cause . . . . . : A SET TRANSACTION, DISCONNECT, or SET SESSION AUTHORIZATION statement cannot be run in the current application state. The reason code is &1. Reason codes and their meanings are:
1 -- A connection is not at a commit boundary.
2 -- The current server is a local relational database and there is an active connection to a remote relational database.
3 -- The SYSTEM_USER is one of the system-supplied user profiles such as QSYS, QDFTOWN, or QSPL.
4 -- A stored procedure, user-defined function, or trigger is running.
5 -- Resources are being held because a COMMIT HOLD statement has been run.
6 -- Resources are being held because a HOLD LOCATOR statement has been run.
7 -- The maximum number of ProfileHandles have been generated.
Recovery . . . : Do one of the following actions prior to running the SQL statement. Try the request again.
1 -- If the connection is not at a commit boundary, issue a COMMIT or ROLLBACK SQL statement.
2 -- If connections to remote relational databases are active, disconnect the remote connections.
3 -- If the SYSTEM_USER is one of the system-supplied user profiles, sign-on with a different user profile.
4 -- Run the SET SESSION AUTHORIZATION statement either before or after the stored procedure, user-defined function, or trigger is run.
5 -- If resources are being held because a COMMIT HOLD has been run, issue a COMMIT or ROLLBACK SQL statement.
6 -- If resources are being held because a HOLD LOCATOR has been run, issue a ROLLBACK or FREE LOCATOR SQL statement.
7 -- If the maximum number of ProfileHandles have been generated, release some of the ProfileHandles that are no longer needed using the Release ProfileHandle (QSYRLSPH) program.
Technical description . . . . . . . . : A SET TRANSACTION, DISCONNECT and SET SESSION AUTHORIZATION can fail with reason code 1. Only the SET SESSION AUTHORIZATION will fail with reason codes 2 through 7.

Message File : QSQLMSG
Library Message File : QSYS2924


ABAP Short Reference   CL_GUI_FRONTEND_SERVICES - Frontend Services  
This documentation is copyright by IBM.

Length: 3240 Date: 20240425 Time: 190751     sap01-206 ( 3 ms )