OCIStmtExecute Executes Successfully after Setting OCI_ATTR_CURRENT_SCHEMA to a Non-Existent Schema Twice (Doc ID 2866958.1)

Last updated on JULY 20, 2024

Applies to:

Symptoms

An OCI code connects to the database using a valid user and query a table successfully. It then sets OCI_ATTR_CURRENT_SCHEMA to a non-existent schema and query the same table but it fails with "ORA-01435: user does not exist" which is an expected behavior. The code then sets OCI_ATTR_CURRENT_SCHEMA to the same non-existent schema and query the table again but this time the query succeeds. For example, the OCI code makes the following series of calls.

1.  OCIInitialize()
2.  OCIEnvInit()
3.  OCIHandleAlloc() for error, service, session, server and statement
4.  OCIServerAttach()
5.  OCIAttrSet() for OCI_ATTR_SERVER
6.  OCIAttrSet() for OCI_ATTR_USERNAME with a valid user
7.  OCIAttrSet() for OCI_ATTR_PASSWORD with a valid password
8.  OCISessionBegin()
9.  OCIAttrSet() for OCI_ATTR_SESSION
10.OCIStmtPrepare() for a SELECT statement on a valid Table.
11.OCIDefineByPos()
12.OCIStmtExecute() <<<<<

13.OCIAttrSet() for OCI_ATTR_CURRENT_SCHEMA with a non-existent schema.
14.OCIStmtExecute() <<<<<

15.OCIAttrSet for OCI_ATTR_CURRENT_SCHEMA with a non-existent schema again.
16.OCIStmtExecute <<<<<

17.OCIHandleFree() for freeing handles
18.Exit

Changes

There's no change in the database server or client side. The issue can be seen on any RDBMS version.

Cause

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.