-L
To:Multiple recipients of list ORACLE-L [EMAIL PROTECTED]
cc:
Subject:RE: Making dispatchers re-read tnsnames.ora?
Well, my first objection to ONames was just in the context of solving
my problem. Dispatchers cache addresses for outgoing connections,
whether
or clients **
-Original Message-
From: Jeremiah Wilton [mailto:[EMAIL PROTECTED]]
Sent: Thursday, January 30, 2003 4:30 PM
To: Multiple recipients of list ORACLE-L
Subject: RE: Making dispatchers re-read tnsnames.ora?
Well, my first objection to ONames was just in the context
Dispatchers and job queue processes read tnsnames.ora on process
startup in case they need to make an outound database link on behalf
of one of he sessions using that dispatcher.
If you make a change to the tnsnames.ora, dispatchers and job queue
processes won't register it unless you restart
Yeah! Put it in Oracle*Names.
-Original Message-
From: Jeremiah Wilton [mailto:[EMAIL PROTECTED]]
Sent: Thursday, January 30, 2003 7:49 AM
To: Multiple recipients of list ORACLE-L
Subject: Making dispatchers re-read tnsnames.ora?
Dispatchers and job queue processes read
to that Rubik's cube.
--
Jeremiah Wilton
http://www.speakeasy.net/~jwilton
-Original Message-
From: Jeremiah Wilton [mailto:[EMAIL PROTECTED]]
Sent: Thursday, January 30, 2003 7:49 AM
To: Multiple recipients of list ORACLE-L
Subject: Making dispatchers re-read tnsnames.ora
to that Rubik's cube.
--
Jeremiah Wilton
http://www.speakeasy.net/~jwilton
-Original Message-
From: Jeremiah Wilton [mailto:[EMAIL PROTECTED]]
Sent: Thursday, January 30, 2003 7:49 AM
To: Multiple recipients of list ORACLE-L
Subject: Making dispatchers re-read tnsnames.ora
Not that ONames doesn't have it's shortcomings, but I'm not sure how ONames
is a single point of failure. Even in our little 35-alias ONames repository
with only the root region, we have a secondary Names Server. With local
checkpoint files, the repository is not required for continuous access,
Well, my first objection to ONames was just in the context of solving
my problem. Dispatchers cache addresses for outgoing connections,
whether they cache them from tnsnames.ora or ofrom Oracle Names. Or
so I understand it. If someone knows differently about Names then I
would like to hear
dispatchers re-read tnsnames.ora?
Not that ONames doesn't have it's shortcomings, but I'm not
sure how ONames
is a single point of failure. Even in our little 35-alias
ONames repository
with only the root region, we have a secondary Names Server.
With local
checkpoint files
