Setting Oracle xmeta database idle time to any value except unlimited will cause Information Server errors when idle time is exceeded

Problem

Security compliance may dictate that the Oracle xmeta database must have idle_time set to a value of 30 minutes or less. The idle_time is the designated amount of time when the Oracle apps client is not doing any activity. This is often set for security, performance issues, or to free up system resources. When the idle_time is met, the Oracle application terminates the client session. When the Information Server users have their database profile set up to have the parameter idle_time set to 30 minutes and they attempt to then use Information Server, they get error messages. For example, attempting to log into the Information Server web console will result in the error, "Commit attempt failed: [There is no currently active transaction]". For other operations, all subsequent database operations will fail and that includes client login failures. The only way that the user may then log into Information Server is by stopping the services and then restarting them.