Results 1 to 4 of 4

Thread: IPC connection

  1. #1
    Join Date
    Jan 2002
    Posts
    165

    Unanswered: IPC connection

    I'm trying (don't ask me why ) to establish IPC connection to my db.Oracle 9.2.0.1,Linux
    LD_ASSUME_KERNEL=2.4.1
    SID_NAME=GAMESMS
    SERVICE_NAME=gamesms.eronet.ba

    I added next line in my listener.ora
    (ADDRESS = (PROTOCOL = IPC)(KEY = IPCKEY))

    Next line is added in tnsnames.ora:
    IPCGAMESMS.LOCALDOMAIN =
    (DESCRIPTION =
    (ADDRESS_LIST =
    (ADDRESS = (PROTOCOL = IPC)(KEY = IPCKEY))
    )
    (CONNECT_DATA =
    ((SID = GAMESMS))
    )
    And,of course,it not working
    Starting of listener told me about unknown handler for GAMESMS,and
    tnsping ipcgamesms told me "Segmentation fault".
    Please help !
    TIA,Zvonimir

  2. #2
    Join Date
    Sep 2003
    Location
    Virginia, USA
    Posts
    246
    Change the value of KEY from IPCKEY to the database's SID, or to the service name that you registed with the local listener. For example, if your database has init.ora parameter service_names = foo.world then your KEY should be set to foo.world. My older setup uses the SID and that works fine.
    MarkRem
    Author, Oracle Database 10g: From Nuts to Soup
    http://www.remidata.com/book_nuts2soup.htm

  3. #3
    Join Date
    Aug 2003
    Location
    Where the Surf Meets the Turf @Del Mar, CA
    Posts
    7,776
    Provided Answers: 1
    IPC, why?
    In order for IPC to work, both the client must be logged into/onto the DB server system.
    Yes, IPC is more efficient than TCP.
    However since the client is logged onto the DB server, then BEQ protocol can be used;
    which does NOT require any Oracle listener.
    You can lead some folks to knowledge, but you can not make them think.
    The average person thinks he's above average!
    For most folks, they don't know, what they don't know.
    Good judgement comes from experience. Experience comes from bad judgement.

  4. #4
    Join Date
    Sep 2003
    Location
    Virginia, USA
    Posts
    246
    Yes, but we must be carefult. We cannot say "Bequeath bypasses the Listener", because it does not in all cases. What you described fits in with Oracle Note 16653.1, but we should also consider Oracle Note 16654.1 which states "all non-local connections require the Oracle Listener." In client-server computing, the Listener spawns the server process, and can either redirect the client to the server process or bequeath to the server process the information and rights needed to contact the client. In server-only computing, it is correct to say Bequeath protocol allows applications to communicate with the database without requiring an Oracle Listener.

    To illustrate that Bequeath is built into the Listener, issue the Version command within the Listener Control Utility.

    c:\>lsnrctl version

    LSNRCTL for 32-bit Windows: Version 10.1.0.3.0 - Product

    Copyright (c) 1991, 2004, Oracle. All rights reserved.

    Connecting to (DESCRIPTION=(ADDRESS=(PROTOCOL=TCP)(HOST=
    TNSLSNR for 32-bit Windows: Version 10.1.0.3.0 - Product
    TNS for 32-bit Windows: Version 10.1.0.3.0 - Pro
    Oracle Bequeath NT Protocol Adapter for 32-bit W
    Windows NT Named Pipes NT Protocol Adapter for 3
    Windows NT TCP/IP NT Protocol Adapter for 32-bit
    The command completed successfully
    MarkRem
    Author, Oracle Database 10g: From Nuts to Soup
    http://www.remidata.com/book_nuts2soup.htm

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •