General idea, how to implement it?
Hey guys,
I need your help to implement a general idea I have, but not too sure how to go about in Wise Package Studio.
So, I need to package a single Tnsnames.ora for or organization. However, on some machines, Oracle is installed on the %PROGRAMFILES%\Oracle, on others it's in %ROOTDRIVE%. Also, I'd like it to work on multiple versions of Oracle, since we are using versions as old as Oracle 7 and 8 here.
What I thought was to try and use a System Search for something along the lines of "Network\Admin", and if found, write my Tnsnames.ora file in that said folder.
Thing is, I'm not sure how to execute it. I've used System Search in wise 2-3 times, but not in such a capacity. Is this the right way to go? If not, how should I proceed?
Thanks!
Stephane
I need your help to implement a general idea I have, but not too sure how to go about in Wise Package Studio.
So, I need to package a single Tnsnames.ora for or organization. However, on some machines, Oracle is installed on the %PROGRAMFILES%\Oracle, on others it's in %ROOTDRIVE%. Also, I'd like it to work on multiple versions of Oracle, since we are using versions as old as Oracle 7 and 8 here.
What I thought was to try and use a System Search for something along the lines of "Network\Admin", and if found, write my Tnsnames.ora file in that said folder.
Thing is, I'm not sure how to execute it. I've used System Search in wise 2-3 times, but not in such a capacity. Is this the right way to go? If not, how should I proceed?
Thanks!
Stephane
0 Comments
[ + ] Show comments
Answers (4)
Please log in to answer
Posted by:
anonymous_9363
15 years ago
Stephane, you could use one of the many environment variables of which Oracle is so enamoured to determine the installation path.
A much tidier solution would be to have a network location for TNSNAMES.ORA and alter the client environment and registry settings to point to it. At the same time, make that location read-only for users and read-write for SysAdmins/DBAs. You would probably want to have changes to it controlled by a Change Control process, too. This way, you end up with a one-time change to the clients and any server changes/additions/deletions can be centrally managed.
A much tidier solution would be to have a network location for TNSNAMES.ORA and alter the client environment and registry settings to point to it. At the same time, make that location read-only for users and read-write for SysAdmins/DBAs. You would probably want to have changes to it controlled by a Change Control process, too. This way, you end up with a one-time change to the clients and any server changes/additions/deletions can be centrally managed.
Posted by:
anks_09
15 years ago
Hi,
Following Link can help you how to search for TNSnames.ora file:
http://www.dba-oracle.com/t_windows_tnsnames.ora_file_location.htm
Regards,
anks_09
Following Link can help you how to search for TNSnames.ora file:
http://www.dba-oracle.com/t_windows_tnsnames.ora_file_location.htm
Regards,
anks_09
Posted by:
Fau
15 years ago
Hey guys,
Unfortunately, both ideas are good, but I can't use them in my environment. The idea of a centralized server is ohhh so sweet, but we have multiple domains, and trusts aren't fully in place yet.
As for anks's suggestion, problem is my workstations don't have a variable for ORAHOME. Our package has corrected this for future installations, but for existing installations, I'm kind of stuck doing a search for it.
Thanks for your help!
I'll keep reading maybe I'll get lucky!
Stephane
Unfortunately, both ideas are good, but I can't use them in my environment. The idea of a centralized server is ohhh so sweet, but we have multiple domains, and trusts aren't fully in place yet.
As for anks's suggestion, problem is my workstations don't have a variable for ORAHOME. Our package has corrected this for future installations, but for existing installations, I'm kind of stuck doing a search for it.
Thanks for your help!
I'll keep reading maybe I'll get lucky!
Stephane
Posted by:
michaelnowell
15 years ago
Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.
so that the conversation will remain readable.