Exploring the Oracle LOCALLISTENER Parameter edstevensdba. In my previous post, Registering the Oracle Database with the listener,  I mentioned the role of the initialization parm LOCALLISTENER in dynamic registration of the database instance to the listener. Now Id like to deliver on my promise to explore that piece of the puzzle. To quickly recap that post, there are two methods by which a listener comes to know what databases it can service. In Oracle terminology, this is referred to as registering with the listener. Static Instance Registration. My cookbook on resolving Oracle remote database connection issues using different client tools like ping, telnet, tnsping, sqlplus, etc. The first and older method is static registration. In this method, the instance is listed in the SIDLIST section of the listeners configuration file, listener. Such a registration would show in the listener. Network Configuration File u. Generated by Oracle configuration tools. DESCRIPTIONLIST. DESCRIPTION. ADDRESS PROTOCOL TCPHOST vblnxsrv. PORT 1. 52. 1. ADDRESS PROTOCOL IPCKEY EXTPROC1. SQL Server is gaining popularity and there are many shops that I know of that have this database system within their walls. Learn how to make a connection from Oracle. To learn more about these techniques, see the book Advanced Oracle Utilities The Definitive Reference. You can buy it directly from the publisher and get. Establishing a Network and Testing the Connection. Once you have completed configuring the network, you should make a connection and test each component to ensure. Hello Everyone, I am trying to access a schema from another database using db links. I am able to tnsping that machine without. SIDLISTLISTENER. SIDDESC. GLOBALDBNAMEtulsa. ORACLEHOME u. SIDNAME tulsa. Fig. 1. And that static registration shows up in the listener status with a status of UNKNOWN. LSNRCTL for Linux Version 1. Production on 2. 3 JAN 2. Copyright c 1. 99. Oracle. All rights reserved. Connecting to DESCRIPTIONADDRESSPROTOCOLTCPHOSTvblnxsrv. PORT1. 52. 1. STATUS of the LISTENER. Alias LISTENER. Version TNSLSNR for Linux Version 1. SQORAS32 unsupported operation tips. Expert Oracle Database Tips by Donald BurlesonNovember 17, 2015. Production. Start Date 2. JAN 2. 01. 6 1. 6 2. Oracle Tnsping Windows' title='Oracle Tnsping Windows' />Uptime 0 days 0 hr. Trace Level off. Security ON Local OS Authentication. SNMP OFF. Listener Parameter File u. Listener Log File u. IASCE.png' alt='Oracle Tnsping Windows 7' title='Oracle Tnsping Windows 7' />Listening Endpoints Summary. DESCRIPTIONADDRESSPROTOCOLtcpHOSTvblnxsrv. PORT1. 52. 1. DESCRIPTIONADDRESSPROTOCOLipcKEYEXTPROC1. Services Summary. Service tulsa has 1 instances. Instance tulsa, status UNKNOWN, has 1 handlers for this service. The command completed successfully. Fig. 2. At Fig. 2, line 2. UNKNOWN because there is no mechanism to guarantee that the specified instance even exists. The listener just assumes that the instance will be there when a connect request is received. In fact, my database was down when I took the status shown in Fig. Dynamic Instance Registration. With version 9. 0 Oracle introduced the concept of dynamic registration. With this, it is no longer necessary to list the database instance in the listener. Instead, the database instance contacts the listener directly and registers itself. We can observe the result of that in the listener status. First, Ill remove my listner. The listener is quite capable of running without a listner. It will simply start and run with all default values. LSNRCTL for Linux Version 1. Production on 2. 3 JAN 2. Copyright c 1. 99. Oracle. All rights reserved. Connecting to DESCRIPTIONADDRESSPROTOCOLTCPHOSTvblnxsrv. Crack Empleados Msd 3.0. PORT1. 52. 1. The command completed successfully. LSNRCTL for Linux Version 1. Production on 2. 3 JAN 2. Copyright c 1. 99. Oracle. All rights reserved. Starting u. 01apporacleproduct1. TNSLSNR for Linux Version 1. Production. Log messages written to u. Listening on DESCRIPTIONADDRESSPROTOCOLtcpHOSTvblnxsrv. PORT1. 52. 1. Connecting to ADDRESSPROTOCOLtcpHOSTPORT1. STATUS of the LISTENER. Alias LISTENER. Version TNSLSNR for Linux Version 1. Production. Start Date 2. JAN 2. 01. 6 1. 6 2. Uptime 0 days 0 hr. Trace Level off. Security ON Local OS Authentication. SNMP OFF. Listener Log File u. Listening Endpoints Summary. DESCRIPTIONADDRESSPROTOCOLtcpHOSTvblnxsrv. PORT1. 52. 1. The listener supports no services. The command completed successfully. Fig. 3. So we can see in Fig. If we try to connect at this point we will get the ora 1. C tnsping tulsa. TNS Ping Utility for 6. Windows Version 1. Production on 2. 3 JAN 2. Copyright c 1. 99. Oracle. All rights reserved. Used parameter files. C apporacleproduct1. Used TNSNAMES adapter to resolve the alias. Attempting to contact DESCRIPTION ADDRESSLIST ADDRESS PROTOCOL TCP. HOST vblnxsrv. 02PORT 1. CONNECTDATA SERVICENAME tulsa. C sqlplus scotttigertulsa. SQLPlus Release 1. Production on Sat Jan 2. Copyright c 1. 98. Oracle. All rights reserved. ORA 1. 25. 14 TNS listener does not currently know of service requested in connect. Fig. 4. In Fig. 4, line 1, a tnsping proves that our tnsnames resolution is correct. But at line 2. 3 we see that an actual attempt to connect to the service proves the listener doesnt know anything about the service tulsa. Now lets start the instance and check again. SQLlus Release 1. Production on Sat Jan 2. Copyright c 1. 98. Oracle. All rights reserved. Connected to an idle instance. SQL startup. ORACLE instance started. Total System Global Area 7. Fixed Size 2. 92. Variable Size 5. 20. Database Buffers 1. Redo Buffers 5. 45. Database mounted. Database opened. Disconnected from Oracle Database 1. Enterprise Edition Release 1. Production. With the Partitioning, OLAP, Advanced Analytics and Real Application Testing options. LSNRCTL for Linux Version 1. Production on 2. 3 JAN 2. Copyright c 1. 99. Oracle. All rights reserved. Connecting to ADDRESSPROTOCOLtcpHOSTPORT1. STATUS of the LISTENER. Alias LISTENER. Version TNSLSNR for Linux Version 1. Production. Start Date 2. JAN 2. 01. 6 1. 6 2. Uptime 0 days 0 hr. Trace Level off. Security ON Local OS Authentication. SNMP OFF. Listener Log File u. Listening Endpoints Summary. DESCRIPTIONADDRESSPROTOCOLtcpHOSTvblnxsrv. PORT1. 52. 1. Services Summary. Service tulsa has 1 instances. Instance tulsa, status READY, has 1 handlers for this service. Service tulsa. XDB has 1 instances. Instance tulsa, status READY, has 1 handlers for this service. The command completed successfully. Fig. 5. In Fig. 5 we observe that once the instance is started line 9, when we re check the listener line 2. READY line 4. 5. This obviously did not come from listener. I had removed that file. Notice also that, unlike the static registration, this time the status is READY. The listener knows the instance is ready because the instance itself told the listener it was ready. And we can prove it by establishing a connection from a remote system. C sqlplus scotttigertulsa. SQLlus Release 1. Production on Sat Jan 2. Copyright c 1. 98. Oracle. All rights reserved. Oracle Database 1. Enterprise Edition Release 1. Production. With the Partitioning, OLAP, Advanced Analytics and Real Application Testing opt. Fig. 6. The LOCALLISTENER initialization parameter. So weve seen that the listener is able to start up and successfully handle connection requests without a listener. It does this by using all defaults including the listener name and port and the database instance is able to register itself with the listener. How does the instance know how to contact the listener in order to register itself It uses the initialization parameter LOCALLISTENER. From the Oracle Database Reference 1. LOCALLISTENER specifies a network name that resolves to an address or address list of Oracle Net local listeners. Lets see what my instance says about that. SQL show parameter locallistener. NAME TYPE VALUE.