Let's call your newly patched computer "Machine 1". Here are the steps to ensure connectivity between Machine 1's Oracle 10g client and some database within your domain:
1) Locate another machine (let's call it Machine 2) that has:
a) the same operating system as Machine 1, and
b) an existing, working connection to an Oracle database on some other machine (which we'll call "Machine 3"). It doesn't matter whether Machine 2 has a client or a server install of Oracle.
2) Just to be sure of the connection, using Machine 2, successfully log into the target Oracle 10g database on Machine 3.
3) On Machine 2, change directory to its $ORACLE_HOME/network/admin (or %ORACLE_HOME%\network\admin if Windows) directory. In that directory, there should be a file named "tnsnames.ora". That file contains connectivity definitions to Oracle databases, including the one to which you just connected in Step 2, above. Copy that file over to Machine 1's $ORACLE_HOME/network/admin directory. (If, along with the tnsnames.ora file, that directory on Machine 2 also has files named "sqlnet.ora" and "protocol.ora", copy those files over with the "tnsnames.ora" file.)
4) On Machine 1, open up a SQL*Plus session and connect to the Oracle database on Machine 3, using the same, successful login information that you used in Step 2.
This confirms a successful connection from the new client to the remote Oracle database.
Let us know the outcome.
![[santa] [santa] [santa]](/data/assets/smilies/santa.gif)
Mufasa
(aka Dave of Sandy, Utah, USA)
[I provide low-cost, remote Database Administration services:
www.dasages.com]