Sybrand Bakker <gooiditweg_at_sybrandb.demon.nl> wrote in
news:u8liiv8ajrpc30mrqhr99omfrkj4qfa6gv_at_4ax.com:
> On 31 Jul 2003 06:52:53 -0700, avsrk_at_mailcity.com (Subrahmanyam Arya)
> wrote:
>
>>Dear oracle gurus,
>>
>>This is exactly my scenario. I have a java application which talks to
>>Master oracle DB. From with in this java application, i create
>>database links to remote oracle databases and do queries. the database
>>links are dynamically created as and when new remote database comes
>>up.
>>Presently we are distributing this application and are having the
>>customers edit the tnsnames.ora either manually or use them netasst
>>(SQL Net configurator)
>>
>>But eventually we do not want them to edit manually.
>>
>>Has anybody attempted to programatically update the tnsnames.ora
>>either using a unix script or from inside java. are there any bad
>>consequences to doing this.
>>
>>Previously i had miserable experience with editing this file manually
>>and things did not work until i used netasst (SQL Net program).
>>
>>Another reason why we donot want customers to edit tnsnames / use SQL
>>Net is licensing restrictions and contractual obligations. We got
>>oracle licenses for cheap and we cannot expose oracle or expect the
>>end user to do any kind of DBA activity
>>
>>So what i am looking for is some easy custom script / tool that does
>>exactly what SQL.Net does to tnsnames.ora
>>
>>-thx,
>>avsrk
>
>
> Just setup Oracle Names and/or Oracle Internet Directory and forget
> about the other suggestions. Both products will provide the user to a
> central tnsnames.ora. You only will need sqlnet.ora and that will
> never change.
>
Problem with this solution is he wants to make changes "dynamically", and
that only to dblinks. LDAP and ONAMES will provide automatic links but
must be administered outside of the database and those services must be
configured in advance before you can use them as a dblink.
Received on Fri Aug 01 2003 - 07:54:23 CDT
