External connect ( no username or password needed ) ? What I've tried so far: I built against Oracle 8 client and external connection ( based on system id ) works only for oracle 8 - oracle 10 uses a wallet. Then I built against oracle 10 - worked with wallet (external connection) but not an external connection on oracle 8 ( system id based ).
Currently trying to keep in separate processes by using oracle 8 build in stand-alone DBI proxy server for 8 and using regular oracle dbi build in current perl for oracle 10. This works somewhat - except the 'prepare' is apparently postponed so no values are returned and I need those values ( column names and types ). So is there a hack to get 2 oracle dbd build ( called by different names ) in the same perl build ? On Mon, 2009-12-14 at 16:27 +0100, Alexander Foken wrote: > You need only one client version to connect to both 8 and 10, preferably > the newer 10 client. It shuld work in 99.9% of all cases. If that > doesn't work, try 8. If that still does not work, try 9. > > Alexander > > On 14.12.2009 13:18, jeff wrote: > > I need to connect simultaneously to both Oracle 8 and oracle 10 from the > > same script using 'external' connection (ie, no username or password). > > The Oracle libraries, from my experimentations, are not compatible for > > external connections. Oracle 8 uses system ID and Oracle 10 uses wallet > > and they do not overlap. > > > > I need to stress that this is NOT an option. I have no say in this > > regardless of how insecure it may sound. > > > > Anyway, since Oracle DBD can only be built against 1 at a time , this > > presents a problem. I have been trying to use DBI Proxy in a PAR > > standalone for Oracle 8 connections and the usual setup for Oracle 10 > > connections with some limited success. > > > > What would be ideal would be to have 2 different Oracle DBD connections > > from within the same perl build. Any suggestions or ideas for potential > > solutions out there ? > > > > Thanks. > > Jeff > > > > > >
