FileNet Content Services Concepts - Part 4

Deleting Sessions

In a library system, an active session is the open session that a user is currently working in. There are actually two sessions involved when a user is logged in to a library system via a Content Services client application, such as IDM Desktop or CS Web Admin environment. One is the database connection session, and the second is the Content Services library session.

When a CS client application exits or is killed, the corresponding database connection session is deleted from the database. You can also delete all the database connections at once by stopping and restarting the database. If a database connection session is deleted, then any corresponding active CS library session is said to be an orphan session.

CS library system sessions are tracked by CS Explorer but cannot be removed by it. Neither stopping and restarting the database or CS services will delete an orphan session. Nor will rebooting a workstation where a CS client application is running. To remove these orphan CS library sessions, you can invoke DSSTOP on the server where the library system is resident. Alternatively, you can simply allow the daemon running on the database custodial server to periodically check for suspended sessions. The daemon will remove any orphaned sessions that are more than two days old. To find out what sessions are open in a particular library system and to see whether these sessions are active or suspended, you can check the status of the Sessions object using CS Explorer.

Resetting the Session ID

The library system maintains a unique session ID for each library system session. The session ID is incremented each time a user opens a new session. Over time, it is possible to exceed the limit of approximately 2 billion (231) session IDs.

To avoid an overflow condition, we recommend that you periodically check the value of the Session Number  property in a Session object (the value of this property is the session ID). When the value of the Session Number property approaches 2 billion, you should reset the session ID to 0.

To reset the session ID:

1. Stop the library system and database services.

2. Restart the database services.

3. Using your SQL query tool (SQL Server Query Analyzer for SQL Server or sqlplus for Oracle), reset the session ID to 0.

• For SQL Server enter:

use system_name

go

delete from session

go

update numid set se_id_num=0

go

• For Oracle enter:

delete from system_name.session;

update system_name.numid set se_id_num=0

4. Restart the library system services