Dynamic Log Messages

Dynamically added log file logid to DBspace dbspace_number.

Cause:

The next active log file contains records of an open transaction. Whenever the database server adds a log dynamically, it logs this message. Example: Dynamically added log file 38 to DBspace 5.

Action:

Complete the transaction as soon as possible.

Log file logid added to DBspace dbspace_number.

Cause:

Whenever the administrator adds a log file manually, the database server logs this message. Example: Log file 97 added to Dbspace 2.

Action:

None required.

Log file number logid has been dropped from DBspace dbspace_number.

Cause:

When you drop a newly-added log file, the database server logs this message. Example: Log file number 204 has been dropped from DBspace 17.

Action:

None required.

Log file logid has been pre-dropped.

Cause:

When you drop a used log file, it is marked as deleted (status D) and cannot be used again. After you perform a level-0 backup, the database server drops this log file and can reuse the space. Example: Log file 12 has been pre-dropped.

Action:

To delete the log file, perform a level-0 backup of all storage spaces.

Pre-dropped log file number logid has been deleted from DBspace dbspace_number.

Cause:

After a backup, the database server deletes a pre-dropped log file and logs this message. Example: Pre-dropped log file number 12 has been deleted from DBspace 3.

Action:

None required.

ALERT: Because the oldest logical log (logid) contains records from an open transaction (transaction_address), the server is attempting to dynamically add a log file. But there is no space available. Please add a DBspace or chunk. Then complete the transaction as soon as possible.

Cause:

If the database server is unable to dynamically add a log file because the instance is out of space, it logs this message.

Action:

Add a dbspace or chunk to an existing dbspace. Then complete the transaction as soon as possible.

ALERT: The oldest logical log (logid) contains records from an open transaction (transaction_address). Logical logging will remain blocked until a log file is added. Add the log file with the onparams -a command, using the -i (insert) option, as in:
onparams -a -d dbspace -s size -i
Then complete the transaction as soon as possible.

Cause:

If the DYNAMIC_LOGS parameter is set to 1, the database server prompts the administrator to add log files manually when they are needed.

Action:

Use the onparams -a command with the -i option to add the log file after the current log file. Then complete the transaction as soon as possible.

Log file logid has been pre-dropped. It will be deleted from the log list and its space can be reused once you take level-0 archives of all BLOBspaces, Smart BLOBspaces and non-temporary DBspaces.

Cause:

When you drop a used log file, it is marked as deleted (status D) and cannot be used again, and onparams prints this message.

Action:

To delete the log file, perform a level-0 backup of all storage spaces.