OCI Orlon call snafoo

From: David Trahan <p00775_at_psilink.com>
Date: Thu, 07 Oct 93 08:25:55 -0500
Message-ID: <2959081889.1.p00775_at_psilink.com>


Please tell me I'm not losing my noodle... (I know I lost it a long time ago!)

        I'm trying to write a simple little Oracle application in C using OCI calls. In this particular case, I need to have two (count 'em - 2) SEPARATE logons to the SAME instance, each logged in under a different user name. So... upon flipping through Oracle's Programmer's Guide to the Oracle Call Interface (version 7), I see the 'orlon' call has the following description:

	"An OCI program can connect to one or more Oracle instances
	multiple times.  Communication takes place using the logon
	data area defined within the program."

Then they go on to show a nice little example of two LDAs and two HDAs connecting to two DIFFERENT instances (how about an unambiguous example guys!?!) Clearly in their example you can connect to two DIFFERENT instances, but it is completely UNCLEAR if you can connect twice to the SAME instance. I ASSUMED (big mistake when dealing with Oracle) that I could do this, and wrote my code accordingly. However, when I run it, the "second" orlon returns "ORA-01075 you are already logged on meathead". Well alright, it didn't say meathead, but it was sure implied.

        The reason I'm doing this is that my application does some analysis on the data dictionary of a "target" DB, and writes some results to an "analysis" DB. The analysis DB *might* be a different instance on even a different host, but it *might* be the same instance on the same host - it's up to the user who decides at runtime. I kinda thought that was the beauty of this whole client-server thang.

        I'm running RDBMS 7.0.13 on a DEC Alpha running OpenVMS 1.5. I have a tar into Oracle but I need an answer before Christmas.

        Your help will make my otherwise meaningless life seem worthwhile!

					Dave Trahan
					p00775_at_psilink.com
Received on Thu Oct 07 1993 - 14:25:55 CET

Original text of this message