Troubleshooting

---

If shadow updating is delayed TRANSDB grows. This can happen for several reasons:

• A shadow has been set offline and forgotten. If this happens, transactions will be buffered until the shadow is set online again.

  To check if a shadow is offline, in BSQL use the LIST SHADOWS command or the The Performance Report.

• A shadow is corrupt. Updates to the shadow result in an I/O error, and are buffered in TRANSDB.

  When this happens, the operator is notified by the system. To check, for notification, use the The Performance Report and check your Mimer SQL database server log, see Database Server Log.

• There are too few background threads to update the shadows, or they get too little machine resources.

Mimer Information Technology AB Voice: +46 18 780 92 00 Fax: +46 18 780 92 40 info@mimer.se