MAXDB Session inactivity timeout

700: Session inactivity timeout (work rolled back) 

Explanation:

Your transaction was implicitly canceled and rolled back by an implicit ROLLBACK statement. The database session was implicitly terminated because the user failed to carry out any operations during a certain period of time (special database parameter SESSION_TIMEOUT, or the timeout value specified in the CONNECT statement).

User Action:

Repeat the CONNECT statement and, if necessary, specify a larger timeout value.

You will also need to check the value of the SESSION_TIMEOUT database parameter, and possibly change this value.