- #Pl sql developer without tnsnames.ora install
- #Pl sql developer without tnsnames.ora 64 Bit
- #Pl sql developer without tnsnames.ora update
- #Pl sql developer without tnsnames.ora full
- #Pl sql developer without tnsnames.ora download
I’ve tried, but I can’t connect it.Īfter downloading, unzip it and do not need to install it.
#Pl sql developer without tnsnames.ora download
Select the first instant client for Microsoft Windows (32-bit) to download it. Click Connect to enter the following page. At this time, PL / SQL developer cannot be used for direct connection, so other ways are needed to complete the connection.ĭownload address: /technetwork/database/features/instant-client/index-097480.html.
#Pl sql developer without tnsnames.ora 64 Bit
The 64 bit Oracle database is installed on the 64 bit system, but there is no corresponding 64 bit PL / SQL developer.
#Pl sql developer without tnsnames.ora full
In order to make full use of memory resources (32 is the system can only use about 3G memory at most) and improve system performance, many people began to use win7 (64bit) system.
#Pl sql developer without tnsnames.ora update
You are no longer to use Easy Connect.Due to the continuous update of hardware technology, win7 system has gradually become the mainstream, and the computer memory has gradually increased. On the other way, if DBA explicitly disabled the naming method by removing EZCONNECT from the list in sqlnet.ora, like the following: NAMES.DIRECTORY_PATH = (TNSNAMES) SQL> conn seems a simple way to connect to database, you can find out more concepts and examples about Easy Connect naming method in Oracle documentation. In this case, the destination is, the listener port is 1521 and the service name is ORCL. You have to provide the following information in order to use Easy Connect naming method. Which is: NAMES.DIRECTORY_PATH = (TNSNAMES, LDAP, EZCONNECT) Use Easy Connect Methodīy default, you can use Easy Connect naming method to connect databases, this is because the default connect methods of NAMES.DIRECTORY_PATH in sqlnet.ora includes EZCONNECT. Of course, you can also set TNS_ADMIN permanently if you have the right to do it. Please note that, TNS_ADMIN set here is just only for your session, once you exit, the environment variable is reset. Test New Connect Identifier SQL> conn trick is successfully. Of course it got error, because we point the network configuration to the new location TNS_ADMIN. Test Old Connect Identifier C:\Users\edchen>sqlplus /nolog Modify tnsnames.ora File C:\Users\edchen>notepad d:\tnsnames.ora This setting will override the original path to tnsnames.ora. Test New Connect Identifier SQL> conn Windows Platform Set TNS_ADMIN Path C:\Users\edchen>set TNS_ADMIN=d:\
SQL> conn TNS:could not resolve the connect identifier specified Test Old Connect Identifier ~]$ sqlplus /nolog (ADDRESS = (PROTOCOL = TCP)(HOST = )(PORT = 1521)) Modify tnsnames.ora File ~]$ vi /tmp/tnsnames.ora For Linux Platform Set TNS_ADMIN Path ~]$ export ~]$ echo $TNS_ADMIN Then connection tools including sqlplus will know where to find the new tnsnames.ora. The trick is to set a TNS_ADMIN environment variable temporarily for your session and put your own tnsnames.ora in that directory. I know you cannot touch the original tnsnames.ora, but you can use your own tnsnames.ora. SQL> conn = (ADDRESS_LIST = (ADDRESS = (PROTOCOL = TCP)(HOST = )(PORT = 1521)))(CONNECT_DATA = (SERVICE_NAME = ORCL)))"įor safety, we use double quotes to wrap the string. That's why we replace the connect identifier with the connect descriptor to connect a new or moved database. That is to say, the real working thing is the connect descriptor.
SQL> conn other words, the connect identifier, the alias will be translated into its own connect descriptor at connect-time. More specifically, the connect identifier is just an alias which can be used in connection string to represent their own lengthy connect descriptor for convenience. In the above entry, ORA11G is the connect identifier, everything behind the equal sign is the connect descriptor. Every entry in the file contains a pair of connect identifier and connect descriptor. Intrinsically, tnsnames.ora is an alias management of service names in a file. In this post, I provided some ways to sqlplus connect to databases without touching the original tnsnames.ora. How can we connect to a new or moved database by sqlplus? Yes, sometimes we are not allowable to change tnsnames.ora, even a tiny bit.
0 kommentar(er)
