Oci_connect using easy connect naming method needs listener??

Hi,
I was thinking that using the easy connect naming method in oci_connect does not require a running local tnslsnr!? Am I wrong?
I tried:
$db = '(DESCRIPTION = (ADDRESS = (PROTOCOL = TCP)(HOST = my-ora-host.example.com)(PORT = 1521)) (CONNECT_DATA = (SERVER = DEDICATED) (SERVICE_NAME = my-service.example.com)))';
// $db = '//my-ora-host.example.com:1521/my-service.example.com';
$ora_conn = oci_connect('test', 'test', $db);
Using both versions of the 'db' I receive the error:
mod_fcgid: stderr: PHP Warning: oci_connect(): ORA-12541: TNS:no listener in ....
I am using a self compiled PHP 5.3.8 using Oracles instantclient 11.2.0.3.0 (on Linux, 32bit).
There are NO special environment variables ( like ORACLE_HOME or TNS_ADMIN), because I was thinking that I don't need them...
Am I wrong? Is a running tnslsnr always required? Or am I doing wrong in specifying the connection string?
Any help is appreciated!
chuan

The connection strings are fine. They only control how PHP attempts to connect to the DB. The DB will need a listener started so that those incoming requests are handled. Use: 'lsnrctl start' on the DB machine.

Similar Messages

  • TIP 02: Easy Connect Naming Method in 10g by Joel Pèrez

    Hi OTN Readers!
    Everyday I get connection on Internet and one of the first issues that
    I do is to open the OTN main page to look for any new article or any
    new news about the Oracle Technology. After I open the main page of
    OTN Forums and I check what answers I can write to help some people
    to work with the Oracle Technology and I decided to begin to write some
    threads to help DBAs and Developers to learn the new features of 10g.
    I hope you can take advantage of them which will be published here in
    this forum. For any comment you can write to me directly to : [email protected]
    Please do not replay this thread, if you have any question related to
    this I recommend you to open a new post. Thanks!
    The tip of this thread is: Easy Connect Naming Method
    Joel Pérez
    http://otn.oracle.com/experts

    Let's go to test it removing the BASE1 service of the listener.ora file
    # listener.ora Network Configuration File: C:\oracle\product\10.1.0\db_1\NETWORK\ADMIN\listener.ora
    # Generated by Oracle configuration tools.
    SID_LIST_LISTENER =
      (SID_LIST =
        (SID_DESC =
          (GLOBAL_DBNAME = BASE2)
          (ORACLE_HOME = C:\oracle\product\10.1.0\db_1)
          (SID_NAME = BASE2)
    LISTENER =
      (DESCRIPTION =
        (ADDRESS = (PROTOCOL = TCP)(HOST = oracle10g)(PORT = 1521))
      )and Now, I am going to reload the listener service in order to
    apply the change to the enviroment.
    Microsoft Windows 2000 [Version 5.00.2195]
    (C) Copyright 1985-2000 Microsoft Corp.
    C:\>
    C:\>lsnrctl stop
    LSNRCTL for 32-bit Windows: Version 10.1.0.2.0 - Production on 20-APR-2004 13:20
    :35
    Copyright (c) 1991, 2004, Oracle.  All rights reserved.
    Connecting to (DESCRIPTION=(ADDRESS=(PROTOCOL=TCP)(HOST=oracle10g)(PORT=1521)))
    The command completed successfully
    C:\>lsnrctl start
    LSNRCTL for 32-bit Windows: Version 10.1.0.2.0 - Production on 20-APR-2004 13:20
    :39
    Copyright (c) 1991, 2004, Oracle.  All rights reserved.
    Starting tnslsnr: please wait...
    TNSLSNR for 32-bit Windows: Version 10.1.0.2.0 - Production
    System parameter file is C:\oracle\product\10.1.0\db_1\network\admin\listener.or
    a
    Log messages written to C:\oracle\product\10.1.0\db_1\network\log\listener.log
    Listening on: (DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=127.0.0.1)(PORT=1521)))
    Connecting to (DESCRIPTION=(ADDRESS=(PROTOCOL=TCP)(HOST=oracle10g)(PORT=1521)))
    STATUS of the LISTENER
    Alias                     LISTENER
    Version                   TNSLSNR for 32-bit Windows: Version 10.1.0.2.0 - Produ
    ction
    Start Date                20-APR-2004 13:20:41
    Uptime                    0 days 0 hr. 0 min. 2 sec
    Trace Level               off
    Security                  ON: Local OS Authentication
    SNMP                      OFF
    Listener Parameter File   C:\oracle\product\10.1.0\db_1\network\admin\listener.o
    ra
    Listener Log File         C:\oracle\product\10.1.0\db_1\network\log\listener.log
    Listening Endpoints Summary...
      (DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=127.0.0.1)(PORT=1521)))
    Services Summary...
    Service "BASE2" has 1 instance(s).
      Instance "BASE2", status UNKNOWN, has 1 handler(s) for this service...
    The command completed successfully
    C:\>Joel Pérez
    http://otn.oracle.com/experts

  • Multiple Data Source (for FAILOVER) in Easy Connect Naming method

    Hi All,
    I was wondering if there is a way to specify multiple addresses as part of data source property in the connection string when trying to connect to Oracle with Easy Connect Naming method? this is basically for failover scenario.
    I know its straight forward, if i use Connect Descriptor. But not sure how to do it with EZConnect
    For ex. this is what I want to achieve with EZConnect
    sales.us.example.com=
    (DESCRIPTION=
    (ADDRESS_LIST=
    (LOAD_BALANCE=off)
    (FAILOVER=ON)
    *(ADDRESS=(PROTOCOL=tcp)(HOST=sales1-server)(PORT=1521))*
    *(ADDRESS=(PROTOCOL=tcp)(HOST=sales2-server)(PORT=1521)))*
    (CONNECT_DATA=(SERVICE_NAME=sales.us.example.com)))
    I appreciate your suggestions...
    Thanks

    You might get better answers in one of the DB forums from a generic fail-over perspective as EZconnect isn't specific to ODP.NET.
    I don't know if there's a way to do it or not with EZConnect version of the connect string, but you can certainly provide the fully qualified connect string without using tnsnames.ora..
    constring = "data source=(DESCRIPTION=(ADDRESS_LIST=(LOAD_BALANCE=off)(FAILOVER=ON)(ADDRESS=(PROTOCOL=tcp)(HOST=sales1-server)(PORT=1521))(ADDRESS=(PROTOCOL=tcp)(HOST=sales2-server)(PORT=1521)))(CONNECT_DATA=(SERVICE_NAME=sales.us.example.com))); user id=scott;password=tiger"
    Hope it helps,
    Gres

  • Try to use easy connect to connect from isqlplus but to no avail

    Using the Easy Connect Naming Method
    from http://download.oracle.com/docs/cd/B19306_01/network.102/b14212/naming.htm#sthref783
    I want to connect from isqlplus remotely.
    pardon me if I ask this stupid question,
    do I need to install oracle client to use isqlplus. if yes, then no need to answer the above question.
    I mean with browser no doubt I can reach the url, but when it prompt for the connect string, i try to substitute the
    (DESCRIPTION =
    (ADDRESS = (PROTOCOL = TCP)(HOST = globalro-417667)(PORT = 1522))
    (CONNECT_DATA =
    (SERVER = DEDICATED)
    (SERVICE_NAME = tomkyte)
    so I wonder if I'm doing the right thing or not.
    thanks!

    Hi,
    See the link care fully, the page which you reffered it self says "This chapter describes how to configure connectivity information for client connections to the database server." So Client is required.
    Clients can connect to a database server using easy connect naming if the following conditions are met:
    - Oracle Database 10g Net Services software installed on the client.
    - Oracle TCP/IP protocol support on both the client and database server
    - No features requiring a more advanced connect descriptor are required
    Every thing is there in ORACLE Document.
    - Pavan Kumar N

  • Question about "Easy Connect Naming"

    Good evening,
    My installation consists of 11gR2 where both host and client are on the same machine.
    I wanted to test the "Easy Connect Naming" functionality, to that end, I renamed tnsnames.ora and proceeded to connect using the following command:
    sqlplus sys/abc123@"Oracle2Day1.john.local/orcl.john.local:1521" as sysdbaas expected, the command was successful in connecting to the orcl instance.
    To ensure that everything was as expected, I also tried:
    sqlplus sys/abc123 as sysdbaUnexpectedly, this command also connected to the orcl instance.
    I expected it to fail since there is no tnsnames.ora and I did not specify the host and service names.
    The question is: why was the command sqlplus sys/abc123 as sysdba" successful given that there is no tnsnames.ora ?
    Thank you for your help,
    John.

    The question is: why was the command sqlplus sys/abc123 as sysdba" successful given that there is no tnsnames.ora ?Above only works when logged directly on to DB server, because this flavor of connection does not use SQL*Net; but uses BEQ protocol.

  • Unable to use "easy connect" method to XE database

    All,
    I have an XE database running on Oracle Enterprise Linux. If I create a tnsnames.ora entry I can connect to the server fine. However, if I try to connect via the easy connect method
    sqlplus user@host:port:sid it fails with
    Enter password:
    ERROR:
    ORA-12545: Connect failed because target host or object does not exist
    the hostname I am using is definitely correct and I've also tried with ip address and get same error message. If I change from SID to SERVICE_NAME
    sqlplus user@host:port/service
    I get the following error message
    ERROR:
    ORA-12514: TNS:listener does not currently know of service requested in connect
    descriptor
    I've used both XE and xe as service name. The service name in my tnsnames.ora entry that works uses lower case xe for service name.
    Any help out there would be appreciated.

    Maybe this is more significant for you ?
    Microsoft Windows XP [Version 5.1.2600]
    (C) Copyright 1985-2001 Microsoft Corp.
    C:\Documents and Settings\User1>sqlplus test/test@xe
    SQL*Plus: Release 10.2.0.1.0 - Production on Sat Feb 3 14:05:49 2007
    Copyright (c) 1982, 2005, Oracle.  All rights reserved.
    ERROR:
    ORA-12154: TNS:could not resolve the connect identifier specified
    Enter user-name: test/[email protected]/xe
    Connected to:
    Oracle Database 10g Express Edition Release 10.2.0.1.0 - Production
    SQL> select * from v$version;
    BANNER
    Oracle Database 10g Express Edition Release 10.2.0.1.0 - Product
    PL/SQL Release 10.2.0.1.0 - Production
    CORE    10.2.0.1.0      Production
    TNS for Linux: Version 10.2.0.1.0 - Production
    NLSRTL Version 10.2.0.1.0 - Production
    SQL>

  • NET8의 LOCAL NAMING METHODS 이용관련 CHECK POINTS & TROUBLESHOOTING

    제품 : SQL*NET
    작성날짜 : 2000-12-15
    ===================================================================
    Net8의 Local Naming Methods 이용관련 Check Points & Troubleshooting
    ====================================================================
    Net8 관련 내용중 Local Naming Methods(sqlnet.ora와 tnsnames.ora
    를 이용해서 DB에 Connect하는 방법)에 관한 일반적인 Check Points 및
    Troubleshooing 사항을 정리해보도록 하겠다.
    [Client Connection : Local Naming Methods]
    1. Local Naming method resolves service names by using the local configuration files tnsnames.ora and sqlnet.ora.
    2. One of the benefits of the Local Naming method is that it provides a simple method for resolving service name addresses. It is easy to configure local naming by using a GUI called the Net8 Assistant. When you configure a client machine for local naming by using the Net8 Assistant, a tnsnames.ora file is generated. To configure all the other client machines on the network that need to use the same database services, you can simply copy this file to the client machines.
    3. Another benefit of using the local-naming method is that it resolves service name across networks running different protocols.
    [Local Naming : Configuration]
    1. The local-naming method resolves service names by using the information configured and stored on each individual client. Local naming is most appropriate for simple distributed networks with a small number of services that change infrequently.
    2. Local naming requires the configuration of two local files, tnsnames.ora and sqlnet.ora. The tnsnames.ora file contains the address needed to direct a connection request to the specified listener on the specified node by using the specified database. The sqlnet.ora file stores information about the selected naming method.
    3. Local naming is easy to configure by using the Net8 Assistant. The Net8 Assistant is implemented in Java and is packed with the Java Runtime Environment. You can run the Net8 Assistant on any platform on which Net8 is installed.
    4. When you configure an Oracle8 server to use the local-naming method for service names resolution, the client-side configuration files tnsnames.ora and sqlnet.ora are automatically generated. After the configuration is complete, you copy these two files from the server to the client machines.
    [Client Files : Parameters]
    1. The tnsnames.ora and sqlnet.ora files are generated at the default location ORACLE_HOME\net80\admin.
    2. The first parameter in the tnsnames.ora file specifies the service name and the domain name for the client.
    3. The tnsnames.ora file contains a parameter called DESCRIPTION. This parameter contains information about the connect descriptor for the client.
    4. The ADDRESS parameter in the tnsnames.ora file specifies the network address of the host to which the client is connected. If multiple addresses are specified, use the keyword ADDRESS_LIST before the ADDRESS parameter.
    5. Another parameter in the tnsnames.ora file is the CONNECT_DATA parameter. This parameter specifies the SID of the database to which the client is connected.
    6. The DEFAULT_DOMAIN parameter of the sqlnet.ora file specifies the domain from which the client most often requests names. When this parameter is set, the domain name is automatically appended to the service name in a connect string.
    7. The DIRECTORY_PATH parameter is another key parameter of the sqlnet.ora file. This parameter specifies the names resolution method to be used for the client-server connection.
    8. The sqlnet.ora file also contains a parameter called DEFAULT_ZONE.
    This parameter specifies the region to which the client belongs.
    [Troubleshooting the Client Side]
    These are common client-side problems and the error messages associated with
    each error code.
    ORA-12154: "TNS: could not resolve service name"
    ORA-12198: "TNS: could not find path to destination"
    ORA-12203: "TNS: unable to connect to destination"
    ORA-12533: "TNS: illegal ADDRESS parameters"
    1. The ORA-12154 error occurs when Net8 cannot locate the connect descriptor specified in the tnsnames.ora configuration file. To solve this problem, first verify that a tnsnames.ora file exists and is accessible. Next, verify that multiple copies of the tnsnames.ora file are not present. After checking the existence of the tnsnames.ora file, verify that the service name specified in the connect string is mapped to a connect descriptor in the tnsnames.ora file. Verify also that the file does not contain any syntaz errors. The ORA-12154 error also occur if there is more than one copy of the sqlnet.ora file. Verify that duplicate copies of the sqlnet.ora file are not present.
    2. The ORA-12198 and ORA-12203 errors occur when the client is unable to find the required database. To solve this problem, first verify that you have correctly entered the service name that you want to use. Next verify that the service name parameters in the ADDRESS section of the connect descriptor in the tnsnames.ora file are correctly defined. Then, verify that the tnsnames.ora file is stored in the correct directory. The ORA-12198 and ORA-12203 errors can also occur if the listener on the remote node is not running. Verify that the listener on the remote node has started and is running. If the listener is not running, start the listener by using the Listener Control(LSNRCTL) utility.
    3. The ORA-12533 error occurs if the protocol-specific parameters in the ADDRESS section of the designated connect descriptor in the tnsnames.ora file are incorrect. To solve this problem, use the correct protocol-specific parameters in the ADDRESS section of the connect descriptor.
    4. The ORA-12545 error occurs when the listener on the remote node cannot be contacted. This may happen if the values of the ADDRESS parameter in the tnsnames.ora file and the listener.ora file are incorrect. In this case replace the incorrect values with the correct values in both the files. The ORA-12545 error can also occur if the listener on the remote node is not
    started. To verify whether or not the listener is started, determine its status with the STATUS command of the LSNRCTL utility. If necessary, start the listener on the remote node with the START command.

    제품 : SQL*NET
    작성날짜 : 2000-12-15
    ===================================================================
    Net8의 Local Naming Methods 이용관련 Check Points & Troubleshooting
    ====================================================================
    Net8 관련 내용중 Local Naming Methods(sqlnet.ora와 tnsnames.ora
    를 이용해서 DB에 Connect하는 방법)에 관한 일반적인 Check Points 및
    Troubleshooing 사항을 정리해보도록 하겠다.
    [Client Connection : Local Naming Methods]
    1. Local Naming method resolves service names by using the local configuration files tnsnames.ora and sqlnet.ora.
    2. One of the benefits of the Local Naming method is that it provides a simple method for resolving service name addresses. It is easy to configure local naming by using a GUI called the Net8 Assistant. When you configure a client machine for local naming by using the Net8 Assistant, a tnsnames.ora file is generated. To configure all the other client machines on the network that need to use the same database services, you can simply copy this file to the client machines.
    3. Another benefit of using the local-naming method is that it resolves service name across networks running different protocols.
    [Local Naming : Configuration]
    1. The local-naming method resolves service names by using the information configured and stored on each individual client. Local naming is most appropriate for simple distributed networks with a small number of services that change infrequently.
    2. Local naming requires the configuration of two local files, tnsnames.ora and sqlnet.ora. The tnsnames.ora file contains the address needed to direct a connection request to the specified listener on the specified node by using the specified database. The sqlnet.ora file stores information about the selected naming method.
    3. Local naming is easy to configure by using the Net8 Assistant. The Net8 Assistant is implemented in Java and is packed with the Java Runtime Environment. You can run the Net8 Assistant on any platform on which Net8 is installed.
    4. When you configure an Oracle8 server to use the local-naming method for service names resolution, the client-side configuration files tnsnames.ora and sqlnet.ora are automatically generated. After the configuration is complete, you copy these two files from the server to the client machines.
    [Client Files : Parameters]
    1. The tnsnames.ora and sqlnet.ora files are generated at the default location ORACLE_HOME\net80\admin.
    2. The first parameter in the tnsnames.ora file specifies the service name and the domain name for the client.
    3. The tnsnames.ora file contains a parameter called DESCRIPTION. This parameter contains information about the connect descriptor for the client.
    4. The ADDRESS parameter in the tnsnames.ora file specifies the network address of the host to which the client is connected. If multiple addresses are specified, use the keyword ADDRESS_LIST before the ADDRESS parameter.
    5. Another parameter in the tnsnames.ora file is the CONNECT_DATA parameter. This parameter specifies the SID of the database to which the client is connected.
    6. The DEFAULT_DOMAIN parameter of the sqlnet.ora file specifies the domain from which the client most often requests names. When this parameter is set, the domain name is automatically appended to the service name in a connect string.
    7. The DIRECTORY_PATH parameter is another key parameter of the sqlnet.ora file. This parameter specifies the names resolution method to be used for the client-server connection.
    8. The sqlnet.ora file also contains a parameter called DEFAULT_ZONE.
    This parameter specifies the region to which the client belongs.
    [Troubleshooting the Client Side]
    These are common client-side problems and the error messages associated with
    each error code.
    ORA-12154: "TNS: could not resolve service name"
    ORA-12198: "TNS: could not find path to destination"
    ORA-12203: "TNS: unable to connect to destination"
    ORA-12533: "TNS: illegal ADDRESS parameters"
    1. The ORA-12154 error occurs when Net8 cannot locate the connect descriptor specified in the tnsnames.ora configuration file. To solve this problem, first verify that a tnsnames.ora file exists and is accessible. Next, verify that multiple copies of the tnsnames.ora file are not present. After checking the existence of the tnsnames.ora file, verify that the service name specified in the connect string is mapped to a connect descriptor in the tnsnames.ora file. Verify also that the file does not contain any syntaz errors. The ORA-12154 error also occur if there is more than one copy of the sqlnet.ora file. Verify that duplicate copies of the sqlnet.ora file are not present.
    2. The ORA-12198 and ORA-12203 errors occur when the client is unable to find the required database. To solve this problem, first verify that you have correctly entered the service name that you want to use. Next verify that the service name parameters in the ADDRESS section of the connect descriptor in the tnsnames.ora file are correctly defined. Then, verify that the tnsnames.ora file is stored in the correct directory. The ORA-12198 and ORA-12203 errors can also occur if the listener on the remote node is not running. Verify that the listener on the remote node has started and is running. If the listener is not running, start the listener by using the Listener Control(LSNRCTL) utility.
    3. The ORA-12533 error occurs if the protocol-specific parameters in the ADDRESS section of the designated connect descriptor in the tnsnames.ora file are incorrect. To solve this problem, use the correct protocol-specific parameters in the ADDRESS section of the connect descriptor.
    4. The ORA-12545 error occurs when the listener on the remote node cannot be contacted. This may happen if the values of the ADDRESS parameter in the tnsnames.ora file and the listener.ora file are incorrect. In this case replace the incorrect values with the correct values in both the files. The ORA-12545 error can also occur if the listener on the remote node is not
    started. To verify whether or not the listener is started, determine its status with the STATUS command of the LSNRCTL utility. If necessary, start the listener on the remote node with the START command.

  • Windows "Easy Connect" does not reply with the password / "Easy Connect is not Available"

    Hello,
    I have posted a related question some time ago, which was eventually resolved. However, after some time a problem with Easy Connect (used for MSRA) came back:
    Whenever I arrive at the point in setting up a MSRA session where Easy Connect is needed, I get the reply: "Easy Connect is not Available". Here is an example of the problem:
    Start MSRA
    --> as expected, a window with "invite someone to help you" and " Help some who has invited you" appears
    Select "invite someone to help you"
    --> as expected, a window with "Who do you want to get help from" appears 
    Select "Invite someone to help you"
    --> as expected, a windows with "How do you want to invite your trusted helper?" appears
    Select "Use Easy Connect"
    --> as expected, the temporary "Create invitation window / checking network capabilities" window appears
    Next, I would expect this windows to close a new window to provide me with the Easy Connect password. However, instead I get the window "Easy Connect is not available".
    I cannot continue. (I have screenshots so can repost with them if that would clarity my question)
    Any suggestion how to resolve would be appreciated.
    (Please do not reply with the 3 suggestions from the FAQ (both computers must run windows 7 / Access to internet is limited / your router does not support Easy Connect - doesn't help)
    More background information and things I have tried:
    The "Easy Connect is not available" window offers the "Tell me more about how to fix this problem" which I have tried, but those suggestions do not help
    If I use the other MSRA option: "Help someone who has invited you" (this would be my typical use case), followed by "help someone new" and than select "Use Easy Connect", I also get the "Easy Connect is not available"
    window instead of the expected option to enter the Easy Connect password. I believe this is that same problem.
    This happed with both the 32 as well as the 64 MSRA versions
    I'm using Window 7 Ultimate, 64 bit with all the latest updates
    This desktop PC is wired to the internet via an Edimax gigabit switch, a Dlink DIR-855 wireless router and a fiber modem in bridge mode
    The W7 desktop has a single active network connection only
    I'm using Windows Firewall and Windows Security Essentials
    Disabling the firewall on the PC did not help
    Network discovery is enabled in Control Panel\All Control Panel Items\Network and Sharing Center\Advanced sharing settings (that’s UPnP – right?)
    The Internet Connectivity Evaluation Tool does not seem to be available anymore from MSFT sites
    Restarting "Peer Name Resolution Protocol" did not help
    Restarting "Peer Networking Identity Manager Properties" did not help
    Starting up with a "Clean Boot" (disabled all non-Microsoft services using MSConfig) did not help
    I would also be interested to understand how I can check on the status of the "Easy Connect" service. Is this a service hosted somewhere, or??
    Thanks!

    Dear Andy,
    Thanks a lot for your reply. Let me answer your questions:
    Q: Could you use the other methods: save this invitation as a file and use e-mail to send invitation?
    A: yes, that way I can establish a MSRA connection
    Q: Have you disable other network connections, including disable all virtual network card?
    A: if I check with ‘Device Manager/Network Adapters’ (or Control Panel/Network and Internet/Network Connections) I see two network adapters (my Asus motherboard has two network connectors). Both are available, but only one is used. I have
    disabled one. Unfortunately, this does not solve the problem. I will leave it disable for now.
    Q: To find detailed information about this issue, please locate to event view and find the logs about remote assistance.
    A: I have to admit that the Event Viewer is unfamiliar territory for me. So, I’m not sure where and what to look for. However, as suggested, I found "Event Viewer (local)/Applications and Services Logs/Microsoft/Windows/Remote assistance/Operational".
    Each time, I attempt to use MSRA/Easy Connect, it seems two entries are added. As I cannot seem to upload files with this post, here are just the two entries:
    “Diagnosis Repro Attempt resulted in a failure.”
    “Remote Assistance troubleshooting has confirmed the problem: Remote Assistance Easy Connect isn't available.”
    If you need more details, please suggest what to forward or check. I'm eager to find a solution!
    W.

  • Cannot connect: ORA-12505 error (listener does not know SID..)

    I have an Oracle 10g installation insde a VM with private IP (192.168.109.128) and I'm trying to access it from the host operating system with aqua data studio, but get ORA-12505 error (listener does not currently know of SID...). The identical error occurs if I try to cennect from within the VM itself.
    "tnsping dbdemo" prints:
    ==================
    Used parameter files:
    C:\oracle\product\10.2.0\db_1\network\admin\sqlnet.ora
    Used TNSNAMES adapter to resolve the alias
    Attempting to contact (DESCRIPTION = (ADDRESS = (PROTOCOL = TCP)(HOST = VMDSINW2K3S)(PORT = 1521)) (CONNECT_DATA =
    (SERVER = DEDICATED) (SERVICE_NAME = dbdemo.datadsin)))
    OK (10 msec)
    and lsnrctl status:
    =============
    Connecting to (DESCRIPTION=(ADDRESS=(PROTOCOL=IPC)(KEY=EXTPROC1)))
    STATUS of the LISTENER
    Alias LISTENER
    Version TNSLSNR for 32-bit Windows: Version 10.2.0.1.0 - Production
    Start Date 12-MAR-2007 15:22:55
    Uptime 0 days 0 hr. 5 min. 14 sec
    Trace Level off
    Security ON: Local OS Authentication
    SNMP OFF
    Listener Parameter File C:\oracle\product\10.2.0\db_1\network\admin\listener.ora
    Listener Log File C:\oracle\product\10.2.0\db_1\network\log\listener.log
    Listening Endpoints Summary...
    (DESCRIPTION=(ADDRESS=(PROTOCOL=ipc)(PIPENAME=\\.\pipe\EXTPROC1ipc)))
    (DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=VMDSINW2K3S)(PORT=1521)))
    Services Summary...
    Service "PLSExtProc" has 1 instance(s).
    Instance "PLSExtProc", status UNKNOWN, has 1 handler(s) for this service...
    The command completed successfully
    and the listener.log:
    ===============
    12-MAR-2007 15:29:21 * (CONNECT_DATA=(CID=(PROGRAM=)(HOST=__jdbc__)(USER=))(SERVICE_NAME=dbdemo.datadsin)) * (ADDRESS=(PROTOCOL=tcp)(HOST=10.10.10.10)(PORT=1325)) * establish * dbdemo.datadsin * 12514
    TNS-12514: TNS:listener does not currently know of service requested in connect descriptor
    12-MAR-2007 15:29:21 * (CONNECT_DATA=(CID=(PROGRAM=)(HOST=__jdbc__)(USER=))(SERVICE_NAME=dbdemo.datadsin)) * (ADDRESS=(PROTOCOL=tcp)(HOST=10.10.10.10)(PORT=1327)) * establish * dbdemo.datadsin * 12514
    TNS-12514: TNS:listener does not currently know of service requested in connect descriptor
    12-MAR-2007 15:29:21 * (CONNECT_DATA=(CID=(PROGRAM=)(HOST=__jdbc__)(USER=))(SERVICE_NAME=dbdemo.datadsin)) * (ADDRESS=(PROTOCOL=tcp)(HOST=10.10.10.10)(PORT=1328)) * establish * dbdemo.datadsin * 12514
    TNS-12514: TNS:listener does not currently know of service requested in connect descriptor
    12-MAR-2007 15:29:45 * (CONNECT_DATA=(CID=(PROGRAM=)(HOST=__jdbc__)(USER=))(SERVICE_NAME=dbdemo.datadsin)) * (ADDRESS=(PROTOCOL=tcp)(HOST=10.10.10.10)(PORT=1331)) * establish * dbdemo.datadsin * 12514
    TNS-12514: TNS:listener does not currently know of service requested in connect descriptor
    12-MAR-2007 15:29:51 * (CONNECT_DATA=(CID=(PROGRAM=)(HOST=__jdbc__)(USER=))(SERVICE_NAME=dbdemo.datadsin)) * (ADDRESS=(PROTOCOL=tcp)(HOST=10.10.10.10)(PORT=1335)) * establish * dbdemo.datadsin * 12514
    TNS-12514: TNS:listener does not currently know of service requested in connect descriptor
    12-MAR-2007 15:29:51 * (CONNECT_DATA=(CID=(PROGRAM=)(HOST=__jdbc__)(USER=))(SERVICE_NAME=dbdemo.datadsin)) * (ADDRESS=(PROTOCOL=tcp)(HOST=10.10.10.10)(PORT=1336)) * establish * dbdemo.datadsin * 12514
    TNS-12514: TNS:listener does not currently know of service requested in connect descriptor
    12-MAR-2007 15:29:51 * (CONNECT_DATA=(CID=(PROGRAM=)(HOST=__jdbc__)(USER=))(SERVICE_NAME=dbdemo.datadsin)) * (ADDRESS=(PROTOCOL=tcp)(HOST=10.10.10.10)(PORT=1338)) * establish * dbdemo.datadsin * 12514
    TNS-12514: TNS:listener does not currently know of service requested in connect descriptor
    12-MAR-2007 15:29:51 * (CONNECT_DATA=(CID=(PROGRAM=)(HOST=__jdbc__)(USER=))(SERVICE_NAME=dbdemo.datadsin)) * (ADDRESS=(PROTOCOL=tcp)(HOST=10.10.10.10)(PORT=1339)) * establish * dbdemo.datadsin * 12514
    TNS-12514: TNS:listener does not currently know of service requested in connect descriptor
    my sqlnet.ora is:
    ============
    # sqlnet.ora Network Configuration File: C:\oracle\product\10.2.0\db_1\network\admin\sqlnet.ora
    # Generated by Oracle configuration tools.
    # This file is actually generated by netca. But if customers choose to
    # install "Software Only", this file wont exist and without the native
    # authentication, they will not be able to connect to the database on NT.
    SQLNET.AUTHENTICATION_SERVICES= (NTS)
    NAMES.DIRECTORY_PATH= (TNSNAMES, EZCONNECT)

    12514, 00000, "TNS:listener does not currently know of service requested in connect descriptor"
    // *Cause:  The listener received a request to establish a connection to a
    // database or other service. The connect descriptor received by the listener
    // specified a service name for a service (usually a database service)
    // that either has not yet dynamically registered with the listener or has
    // not been statically configured for the listener.  This may be a temporary
    // condition such as after the listener has started, but before the database
    // instance has registered with the listener.
    // *Action:
    //  - Wait a moment and try to connect a second time.
    //  - Check which services are currently known by the listener by executing:
    //    lsnrctl services <listener name>
    //  - Check that the SERVICE_NAME parameter in the connect descriptor of the
    //    net service name used specifies a service known by the listener.
    //  - If an easy connect naming connect identifier was used, check that
    //    the service name specified is a service known by the listener.
    //  - Check for an event in the listener.log file.

  • Source System creation in BI 7.0 for SQL Server using DB Connect

    Hi
    My requirement  is to extract data from SQL Server 2005 to BI 7.0 using DB Connect.
    I need to create a SOURCE SYSTEM for that purpose,As i am new to BW i don't know how to start to create a  SOURCE SYSTEM.
    What are the parameters i require either from Basis team to install or for DB team User ID in SQL (What type of user).
    Questions:
    1)  create a db user with authorization to read this views.......as i created views on tables...do i need authorisation to read table or views
    "On BW Server side (If BW server isn't based on SQL Server):
    (1) Install SQL Server client and test connection to SQL Server DB.
    (2) Install DBSL of SQL server (download lib_dbsl_<num>.sar file from service market and sapcar to BW kernel)"
    How can i know on which server our BW System is Based and HOW Install SQL Server client and test connection to SQL Server DB and
    Install DBSL of SQL server (download lib_dbsl_<num>.sar file from service market and sapcar to BW kernel
    and
    how to create Source System to SQL Server on BW
    Please update me in details i this is my first Source System Creation in BW
    Thanks in advance

    go through the link this may be helpful                  http://msdn.microsoft.com/en-us/library/dd299430.aspx

  • BW extraction using DB connect

    Can some one post me step by ste guide for BW extraction using DB connect.
    I need to extract data from Oracle 10G.
    Thanks and Regards
    Babu

    Hi Babu:
    Please refer to SAP Note 518241 - "DB Connect in BW for an external Oracle database".
    This paper also might help.
    "Transferring Data with DB Connect"
    http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/2f0fea94-0501-0010-829c-d6b5c2ae5e40?QuickLink=index&overridelayout=true
    Regards,
    Francisco Milán.

  • Connecting oracle using Directory Naming Method

    Hi,
    I am just checking the possibilities of implementing Directory Naming Method in our organization. currently we are using Local Naming method (using tnsnames.ora).
    I did google to find the pre-requsites to use directory naming method and I couldnt' find the right document.
    could somebody who has implemented and using directory naming method (via centralized LDAP-compliant directory server) could help me in finding the pre-requistes and what kind of infrastucture we should be having to implement the same in our organization.
    Thanks in advace for your help.
    Krishna.

    I'm trying to figure these things out myself.
    I have some questions for you:
    1. What operating systems does your server and workstations use?
    If they're all Windows and you're on a Windows Domain, consider Active Directory as the directory service.
    2. If it is all unix-like operating systems, consider using Oracle Internet Directory as the directory service.
    3. Mixed Windows and Unix-like operating systems - use whatever you are currently using as the directory service.
    At http://tahiti.oracle.com/ you may want to read some of the following books from oracle:
    - Platform Guide for Microsoft Windows (if you're using Windows)
    - Advanced Security Administrator's Guide
    - Enterprise User Security Administrator's Guide
    - Net Services Administrator's Guide
    - Net Services Reference
    - Oracle Internet Directory Administrator's Guide
    - Oracle Database 2 Day DBA
    Options to consider: Kerberos or Active Directory
    If using Windows and you already using Active Directory, consider this:
    Microsoft Environment: Configuring Oracle Advanced Security Option (ASO) Kerberos Adapter with Windows 2003 Active Directory
    See Metalink doc-id: 368321.1

  • In the ReportDocument.Load method it tries to connect using the using the connection information embedded in the Report File

    Post Author: bhaveshbusa
    CA Forum: Crystal Reports
    In the ReportDocument.Load method it tries to connect using the using the connection information embedded in the Report File. When the application calls ReportDocument.Load(reportFileName). This
    tries to connect to the database using the connection information embedded in
    the "reportFileName". This was only realised on checking the ODBC Trace
    Log. The connection itself is not a problem. The problem is that the embedded
    connection information is related to OLD production system. And failed
    connections had raised some concerns.
    Note: I am using
    SetDataSource to populate the data for the report. So I don't need the
    connection.
    Is there any way I
    can disable this auto-connect?
    Thanks and
    regards,
    Bhavesh

    960738 wrote:
    I need a help in answering one of the issue encountered last week.
    I have created a database link and tried to access the information from a table using the program written in another language. The password provided was incorrect for that user while creating database link. So we expected that,while retrieving the data, Database connection has to be errored out as password provided is incorrrect.
    But unfortunately, user account was locked out. When i checked with DBAs they mentioned that it tries to connect 16 ports with in a min of time.we were shocked as it STOPS another scheduled jobs with that user. and affects production badly.
    As per the program, it has to connect only one time and yesterday we tried to execute the program in DBAs observation and it errored out as expected. Didn't tried for multiple ports.
    Now the question is, WHY the database connection established 16 times last week and caused user account locked. DBAs are unable to answer it. Any EXPERTs opinion on this would greatly appreciated.
    I have verified managing ports in oracle documentation, it was mentioned that if one port is busy it will try to connect to another port in the range of ports mentioned during the installtion. DBAs verified ports related file and it was blank. and they are not agreeing with this reason. Please HELP me in finding the correct REASON for this.
    is it a NETWORK issue or issue with DATABASE SERVER only?
    Thanks
    SSP
    Edited by: 960738 on Sep 22, 2012 9:13 PMDBLINK is 100% oblivious to the fact any port exists.
    DBLINK only contains username, password & TNS Alias.
    can you post actual SQL & results?

  • I used to able to access and listen to my itunes library from my ipad using the remote app but this no longer works.  I am connected but sound thru ipad.  Is this because of they want us to use itunes match

    I used to able to access and listen to my itunes library on my ipad  using the remote app but this no longer works.  I am connected but sound thru ipad- just controls my library on iMac.  Is this because of they want us to use itunes match

    That has nothing to do with iTunes match. The Remote app on iPad can control the computer's iTunes but not play content from iTunes on your iPad.
    To play for example iTunes imusic on iPad
    You need to have Home Sharing On.
    Check Settings > Music > Home Sharing (key in your Apple ID & password here, must be the same on computer's iTunes)
    Start iPad's Music app, tap the ... More (bottom right), tap Shared.
    Choose your iTunes' library and have fun.

  • Naming Method Use

    Hi,
    TNSNAMES.ORA
    MASTER=(DESCRIPTION=
    (ADDRESS=
    (PROTOCOL=tcp)
    (HOST=TELSTAR)
    (PORT=1521))
    (CONNECT_DATA=
    (SERVICE_NAME=LOC)))
    SQLNET.ORA
    NAMES.DEFAULT_DOMAIN=US.TELSTAR.COM
    NAMES.DIRECTORY_PATH=(LDAP, TNSNAMES, HOSTNAME)
    In here why it uses LDAP?.... Whts the purpose of using LDAP here!
    What is the naming method using here....
    ThankX
    Edited by: Ushman on Sep 15, 2008 4:06 PM

    names.directory_path:- Specifies the order of naming methods that are used when a client tries to connect to a database.
    If you are not using LDAP then simply delete it. LDAP here, refers to Oracle internet Directory a component or Oracle Application Server.
    Regards
    Christopher Soza
    Orix Consultancy Services Ltd

Maybe you are looking for

  • How to copy a text element to another in sapscript

    Question Have a bug in the system and need to copy an existing text element to a new one. How do you do this. I have found the text elelement in tihe MAIN window - the code /E   510-C  <-- this needs to be copied to a new text element called /E    51

  • Problems with the HP 1441A using the 33120A VXI pnp driver

    Hi, I am building a VXI system which incorporates the HP1441A Arb. I am using the 33120A/1441A VXIpnp driver (within LabView 6) and am having some 'issues' with it. I am able to see my instrument in the Visa Assistant screens and am able to run a sof

  • WHERE ARE "DESKTOP" AND "DOCK" SETTINGS STORED?

    I want to backup my desktop and dock settings. Where are they stored so that I can do this? Thx. Mike

  • Volume up key (F12) is not working?

    Last night my volume up key was working perfectly fine but this morning it's being unresponsive. I've tried resetting the PRAM and SMC and that hasn't helped at all. I can still adjust the volume through sytestem preferences but the keyboard function

  • Applet web communication

    I have a Visual Basic program that collects data from a number of PLC's using OPC. The program also opens a WinSock Listener on port 80. What I want to do is to open a web browser and enter the address of the url where the visual basic program is run