-901 UNSUCCESSFUL EXECUTION CAUSED BY A SYSTEM ERROR THAT DOES NOT PRECLUDE THE SUCCESSFUL EXECUTION OF SUBSEQUENT SQL STATEMENTS

Explanation
A system error occurred that prevented successful
execution of the current SQL statement.
Multiple forms:  This message
has two forms. The form that is shown above applies if the SQL statement
is not a query that was sent to an accelerator server. The following
form applies if the SQL statement is a query that was sent to an accelerator
server: UNSUCCESSFUL EXECUTION CAUSED BY A SYSTEM ERROR THAT DOES
NOT PRECLUDE THE SUCCESSFUL EXECUTION OF SUBSEQUENT SQL STATEMENTS accelerator-info

accelerator-info
An error message that was returned by the accelerator server.

If the SQL statement is not a query
that was sent to an accelerator server, possible causes for this error
include:
Statement length: The length of the SQL statement is either less
than 0 or greater than the permitted maximum length for a statement. 
Distributed commit processing: Distributed commit processing encountered
an error. All servers in the unit of work that support distributed
two-phase commit back out the unit of work. If a server that does
not support distributed two-phase commit has updates in the unit of
work, that server must be queried to determine if its updates were
committed or backed out.
Incomplete post-processing work: The transaction is aborted and
commit failed. Typical causes for incomplete post-processing include:An update that changes the partition of a row
Resource availability
The existence of held cursors
Violations of uniqueness constraints

If the SQL statement is a query that was sent
to an accelerator server, the error is returned because the accelerator
server could not execute the query.

System action
 The statement cannot be processed. A X'04E' abend
might be requested for the application. The application program can
have a recovery routine to recover from such an abend and can retry
SQL statements.
The error does not prevent successful execution
of further SQL statements.

Programmer response
 If an abend occurred, notify the system
programmer for analysis of the abend that caused this return code.
Even if an abend occurred, an application program receiving this return
code can retry and is not prohibited from executing further SQL statements.
If
the error occurred during a commit, examine any detailed resource
unavailable information that is posted to the system operator console
or in the DB2® ssnmMSTR address
space job log to determine if a resource unavailable problem prevented
commit post-processing from completing.
If the
error occurred for a query that was sent to an accelerator server,
check whether the SQL statement contains a logical error. An example
of a logical error in an SQL statement is a division operation that
results in division by 0. If you determine that your application is
not the source of the error, contact IBM Software Support, and provide the value in
the accelerator-info token.

SQLSTATE
58004