XADM: Information Store Shuts Down; Database at Maximum Size

This article was previously published under Q185457
This article has been archived. It is offered "as is" and will no longer be updated.
Symptoms
The Microsoft Exchange information store service shuts down. In the WindowsNT application event log, the following event is logged:
   Event ID:1112   Source: MSExchangeIS   Description:  The database has reached the maximum allowed size.   Attempting to stop the Microsoft Exchange Information Store.				
Cause
The Microsoft Exchange information store utilizes the Exchange database engine.The maximum allowed size of a single database in Exchange versions 4.0 and5.0 is 16 GB (Priv.edb can be 16 GB and Pub.edb can be 16 GB). After thelimit is reached, the Exchange database engine stops taking transactions andnotifies the information store to shut down.

NOTE: Microsoft Exchange Server 5.5 Enterprise Edition information storedatabases are not limited to 16 GB; they are limited only by availablehardware.
Workaround
The database (Priv.edb or Pub.edb) that has hit the 16-GB limit must bedecreased so that the affected process can be started and remain started.

First, the affected database must be defragmented to reclaim any freespace. This can be accomplished by doing the following:
  1. Defragment the database. To do so, run the following command:
    edbutil /d /ispriv
    -OR-
    edbutil /d /ispub
    NOTE: If you are using the 5.5 version of Microsoft Exchange Server, run the following command:
    eseutil /d /ispriv
    -OR-
    eseutil /d /ispub
  2. Start the information store service, let it run for a couple of minutes, and then stop the service gracefully. (This is done to make sure all uncommitted transactions are flushed into the database; see the "MoreInformation" section later in this article for details.)
  3. After the process is back up and running, perform a FULL online backup.
    -OR-
    After the process is back up and running, stop the information store service and perform an offline backup of the Exchsrvr\Mdbdata directory.
Defragmenting the database should result in a decrease in size of thedatabase; however, it is possible that the database will still be veryclose to the 16-GB limit. Therefore, steps must be taken to decrease theamount of information in that database. This can be accomplished by eithermoving some users from this server to another server with more free space,or implementing personal information store (PSTs) for users and having themmove mail into PSTs. The Mailbox Resources tab in the Microsoft ExchangeAdministrator program can assist the system administrator in finding thelargest mailboxes.

It is a good idea to implement storage limits on user mailboxes in theprivate information store. Storage limits can be configured through theExchange Administrator program and will help prevent from the databasereaching the 16-GB limit.

For more information about use of personal folders and storage limits, seethe online documentation.

NOTE: If users are moved to another server, the information store should be defragmented again by running edbutil /d /ispriv or edbutil /d /ispub so as toreclaim the space used by the users who were moved.
More information
When the Exchange database is committing a transaction from a log file andthat transaction, if committed, will make the database surpass the 16-GB limit,the Exchange database engine takes the following steps:
  1. The transaction is wholly rolled back, meaning that no part of thetransaction succeeds, and the checkpoint holds a pointer to this transaction in the log file where it was contained.
  2. The Exchange database engine alerts the information store that the 16-GB limit has been reached.
  3. The information store then performs a graceful shutdown of the service.
After the database size has been decreased and the service is restarted,the transactions that were not committed because the limit was reached willbe committed. To ensure this happens, do this: After the information storeis restarted following the defragmentation, stop the service again. Thiscauses all the log files to be committed into the database.

If you are using Exchange Server 5.5 Standard Edition and plan to upgrade to Exchange Server 5.5 Enterprise Edition with unlimited storage, you do not need to defragment the database. Run Setup.exe from the Exchange Server 5.5 Enterprise CD-ROM or Srvmax.exe from the Select CD-ROM.
JET_errOutOfDatabaseSpace -1012 Gig gigabyte
Properties

Article ID: 185457 - Last Review: 10/26/2013 04:00:00 - Revision: 4.0

  • Microsoft Exchange Server 4.0 Standard Edition
  • Microsoft Exchange Server 5.0 Standard Edition
  • Microsoft Exchange Server 5.5 Standard Edition
  • kbnosurvey kbarchive kbprb KB185457
Feedback