Recovering from Session Data Corruption

The following are indications that session data may be corrupted:

• Error messages appear in the Enterprise Server system log (server.log) every time an application tries to save session state.

• Error messages in the server log indicate that the session could not be found or could not be loaded during session activation.

• Sessions that are activated after previously being passivated contain empty or incorrect session data.

• When an instance fails, failed-over sessions contain empty or incorrect session data.

• When an instance fails, instances that try to load a failed-over session cause an error in the server log indicating the session could not be found or could not be loaded.

To bring the session store back to a consistent state

If you determine that the session store has been corrupted, bring it back to a consistent state by following this procedure:

1. Clear the session store.

   Determine if this action corrects the problem. If it does, then stop. If not—for example, if you continue to see errors in the server log—then continue.

2. Re-initialize the data space on all the nodes and clear the data in the database.

   See Clearing a database .

   Determine if this action corrects the problem. If it does, then stop. If not—for example, if you continue to see errors in the server log—then continue.

3. Delete and then recreate the database.

   See Removing a Database and Creating a Database