Re: Default DB is remote

Hi there,

You have to set the two Env-Variables ORACLE_HOME and TWO_TASK, where ORACLE_HOME is home on Server B and TWO_TASK is the SQLNet2-Connect String for the Database on Server A. I did it in Pro*C:

Expample:
......
#define OH "ORACLE_HOME=/app/oracle/product/7.3.2.2" #define OT "TWO_TASK=DB_ON_SERVER_A"
........
putenv(OH);
putenv(OT);
.........
EXEC SQL CONNECT :uid IDENTIFIED BY :pwd; ..........
to be continued

Bye !
Stefan Scheck

Ed Jennings wrote:

> I have an application running on unix server 'A'. The Oracle DB is
> also
> running on server 'A'. The application has recently evolved and has
> become extremely cpu intensive, and the number of child processes has
> increased dramatically. With performance degradation the end result,
> I
> have decided to relocate the application to unix server 'B'.
> Relocatng
> the DB is more difficult because there are many other apps using this
> particular DB. My problem is that I don't know how to make the
> application now running on server 'B' log into the DB on server 'A' by
>
> default. All of the scripts, Pro*C, and Pro COBOL DO NOT reference
> the
> DB with the login_at_instance syntax. It would be an enormous effort to
> modify them all to do so. Is there a way to set this up with
> environment variables? Can the app issue a "sqlplus login" command
> and
> have it transparently translated into "sqlplus login_at_instance"?
>
Received on Thu May 15 1997 - 00:00:00 CDT