Conference rocks::dec_edi

Hi Peter,

I had the same problem when a collegue of mine changed IP-numbers and IP-names.

>>     I log in as root and specify the host ip address instead of the host
>>    name.
  
Is there a reason why you logged in with IP-number instead of IP-name.

What happens if you just specify ediit2 instead if the number.

Martin

    Yes, that did it, thanks, but.....
    
    I now get the following error after I try to log into oracle:
    
    Drivers sqlconnect option failed
    Driver not capable
    ORA-6108: NETTCP: connect to host failed
    Invalid connection string attribute
    
    
    I checked up the meaning of this error, the oracle listener was not
    running, so I started it.
    
    lsnrctl service
    oracle:decedidb:/usr/users/oracle>lsnrctl service
    
    LSNRCTL for DEC OSF/1 AXP: Version 2.2.2.0.0 - Production on 17-APR-97
    14:06:19
    
    Copyright (c) Oracle Corporation 1994.  All rights reserved.
    
    Connecting to
    (ADDRESS=(COMMUNITY=TCP.world)(PROTOCOL=TCP)(Host=ediit2)(Port=15)
    Services Summary...
      decedidb              has 1 service handlers
        DEDICATED SERVER established:0 refused:0
    The command completed successfully
    oracle:decedidb:/usr/users/oracle>
    
    Peter.
    

Hi Peter,

So now all is up and running ?

Regards,

Martin

    Nope, unfortunately, I have now climbed up a layer to the ODBC drivers
    and seemed to be having some trouble here. I still get:
    
    Driver's SQLSetConnectOption failed
    Driver not capable
    ORA-06108 NETTCP: connect to host failed.
    
I think I may have messed up the ODBC config somewhere with all my
    fiddling. I find it rather confusing. If I go into the control panel
    and double click on the ODBC icon and then click on DRIVERS, the only
    oracle drivers listed are:
    Oracle73  v 1.15.0301 
    
    I have added it here with the
    correct datasource name : EDIIT2 CommandCenter and the SQL*net string
    as T:ediit2.
    
    If I fire up the oracle odbc administrator and click on drivers I see
    listed under the oracle drivers:
    Oracle    v 1.00.3112
    Oracle7   v 1.11.0000
    Oracle71  v 1.11.0002
    
    These are old drivers??
    
    
    Where does one configure these drivers?

    Hi,
    
    Should there be an entry in the tnsnames.ora which defines the service,
    and if so what should this service name be? Is it the one defined on
    the pc decedi_pc? The reason I ask this is because when I try to fire
    up the cockpit I get the following error:
    
    Driver's SQLSetConnectOption failed
    Driver not capable
    ORA-12154 TNS:could not resolve service name.
    
    When I look up this error using oerr ora 12154 it tells me to check if
    the service name exists in the tnsnames.ora file and ensure that it is
    in the right directory. I copied from the data area to /etc together
    with the listener.ora and tnsnav.ora files. The service name was not
    anywhere to be found in any of these *.ora files, I tried adding it but
    to no avail.
    
    Secondly when setting up the oracle odbc, the SQL*Net connect string,
    should it be defined as T:ediit2 or T.ediit2? and should the sid be
    included?
    
    Peter.

Hi Peter,

After my opinion your Data Source Name is not correct.

In /etc/tnsnames.ora you'll find the following information

################
# Filename......: tnsnames.ora
# Name..........: LOCAL_REGION.world
# Date..........: Tue Feb 18 12:35:10 MET 1997
################
axpone_decedidb.world =
  (DESCRIPTION =
    (ADDRESS_LIST =
        (ADDRESS =
          (COMMUNITY = TCP.world)
          (PROTOCOL = TCP)
          (Host = axpone.uto.dec.com)
          (Port = 1521)
        )
    )
    (CONNECT_DATA =
       (SID = decedidb)
    )
  )

The line axpone_decedidb.world = defines which services SQL*NET is expecting.
So in my case, it's looking for axpone_decedidb.

On the PC in the ORACLE 7 ODBC setup should be as follow:

Data Source Name      : axpone_decedidb
Description           : DEC/EDI
SQL*NET Connect String: T:axpone.uto.dec.com:decedidb

In the SQL*NET Easy Configuration, Your entry should look like:

Database Alias        : axpone_decedib
Protocol              : TCP/IP
Host Name             : axpone.uto.dec.com
Database instance     : decedidb

And finally my Server setup within Command Center

Name                  : AXPONE_DECEDIDB
Server Nodename       : axpone.uto.dec.com
Server Type           : Digital UNIX
Network               : TCP/IP
Driver                : Oracle73
Account               : Smeets
Database              : decedidb

I hope this helps !

Martin

    From what I remember...
    
    The Oracle stuff on the PC should be setup with Oracle Easy Config (or
    whatever it's called), and this is all documented in the Installation
    Guide.
    
    The Data Source is configured by the CommandCenter, so you shouldn't
    need to use the ODBC Administrator.
    
    Pete.

    Hey, what do you know, It is working. The problem seems to have been
    that a file got corrupted on the PC which had the config for command
    center. I had tried reinstalling command center, but got the same
    problem again, then I deleted all the command center files and
    re-installed it and this fixed it. The problem with command center
    manifested itself when I tried to define the server from any of the
    editors or the cockpit - as soon as I clicked on setup under define
    server or 'new' it would just crash. Once reinstalled, I set up the
    server connection to use the ORACLE73 ODBC driver by default and it
    worked. The data source is not a problem any more since I am using the
    oracle73 odbc driver which is recognized by command center. The
    datasource name is set to: CommandCenter.
    
    Many thanks Martin and Pete.