Entering content frame

-901: Log full 

Explanation:

The log area is full. The following reasons are possible:

...

       1.      Log backup is not active. The Database Manager makes modifications which together with modifications of other transactions result in a log area overflow.

       2.      Log backups are performed. but the backups are not performed fast enough or there is a very long transaction whose modifications together with the modifications of transactions running in parallel result in a log area overflow. The Database Manager performs change operations.

The issued SQL statement fails.

User Action:

...

       1.      Save the log area.
Repeat the SQL statement.

       2.      The database system saves the log area that is required by the very long transaction in other areas of the database instance. The command can then be repeated.

Check whether this state occurs frequently, that is whether the log area is too small for the number of users and average transaction length. In this case, the log area should be increased.

You should also check whether there is an error in the application programming which results in the very long or endless transaction and correct this if necessary.

 

Leaving content frame