Error Description:
Not logged on

Error Cause:
A host language program issued an Oracle call, other than OLON or OLOGON, without being logged on to Oracle.

This can occur when a user process attempts to access the database after the instance it is connected to terminates, forcing the process to disconnect.

This may also occur if the server has run out of available connections.

This problem may also be caused by using MSDAORA. When you end the connection to the Oracle database on the server side while using MSDAORA, the broken connection is returned to the connection pool.

The connection pooling code incorrectly interacts with the ResetConnection property of MSDAORA. When this property is not supported by the provider, the pooling code incorrectly interprets that the connection is reset, and that the connection is a valid one.

When the client code opens a new connection, the broken connection that was returned to the connection pool may be retrieved. Therefore, you receive the error message that is mentioned in the "Symptoms" section. For more information, please visit this page: http://support.microsoft.com/kb/834905.

Action:
Log on to Oracle, by calling OLON or OLOGON, before issuing any Oracle calls. When the instance has been restarted, retry the action.

If the problem is due to running out of connections, kill some connections or increase the value of the 'processes' parameter.

If the problem is caused by MSDAORA, please use the Hotfix available here: http://support.microsoft.com/kb/834905.

There haven't been any comments added for this error yet. You may add one if you like.  Add a comment

Name: Email: URL: Chars left:  1000  (1000 max) (No HTML, but newlines will be preserved)