We are attempting to configure our application with a dedicated Oracle 8.0 database server on a separate Solaris 2.7 host.
We've set the TWO_TASK environment variable to the separate alias name configured in the tnsnames.ora file, and it works fine. All connections are diverted to the dedicated database server.
The problem is that the default username and password logon are disabled as soon as TWO_TASK is set. Hence, all the supporting shell scripts which use default logon in the form "sqlplus /", or "sqlplus -s /" now fail. Default logon has been used extensively in our application environment, so this is a major hurdle.
Any suggestions or tips that don't require major rework of the shell scripts would be most welcome.
Network Monitoring is essential to ensure that computer systems and network devices are running. Use PRTG to monitor LANs, servers, websites, applications and devices, bandwidth, virtual environments, remote systems, IoT, and many more. PRTG is easy to set up & use.
A previously published article on Experts Exchange ("Joins in Oracle", http://www.experts-exchange.com/Database/Oracle/A_8249-Joins-in-Oracle.html) makes a statement about "Oracle proprietary" joins and mixes the join syntax with gen…
Configuring and using Oracle Database Gateway for ODBC
First, a brief summary of what a Database Gateway is. A Gateway is a set of driver agents and configurations that allow an Oracle database to communicate with other platforms…