| T.R | Title | User | Personal Name
 | Date | Lines | 
|---|
| 5007.1 | Questions, questions | ukvms3.uk.oracle.com::PJACKSON | Oracle UK Rdb Support | Fri Feb 07 1997 05:36 | 5 | 
|  |     What network transport are you trying to use? Are you trying to use
    ODBC, or are you field testing native connect? If you are using ODBC,
    does the test program work?
    
    Peter
 | 
| 5007.2 | As Peter said questions, questions | CHSR38::ROHR | The Packers did it! | Fri Feb 07 1997 06:34 | 25 | 
|  |     This is from note 19791.1
    
    Error:  ORA 3114
    Text:   not connected to ORACLE
    -------------------------------------------------------------------------------
    Cause:  A call to Oracle was attempted when no connection was 
            established. Usually this happens because a user-written 
            program has not logged on. It may also happen if communication
            trouble causes a disconnection.
    Action: Try again. If the message recurs and the program is
    user-written,
            check the program. 
    
    Explanation:
            This error basically means 'I do not appear to be talking to an
            Oracle Server'.
    
    What does Rdb on the server say? Does it  connect or try to connect at all?
    Or is there not even a talk between the PC and the server?
    
    Have you loaded the Oracle 7 tables in the Rdb database? See in the D2k
    directory for the document explaining this (rdbinfo.pdf, amybe also in
    the OCA directory).
    
    /Regina
 | 
| 5007.3 | ODBC and TCP/IP are cool -- any ideas ? | NOMAHS::SECRIST | Rdb WWS; [email protected] | Fri Feb 07 1997 15:58 | 17 | 
|  |     
    Customer is using ODBC and TCP/IP and the ODBC test program, etal.
    work fine.  I went through the complete install in advance on
    my W95 system and then made sure he did the same steps, although
    he is using DOS/Windows 3.1.  I successfully connect and he does
    not (but he can turn right around and use the ODBC test program).
    
    Although UBT dies with a WSANOTCONNECT error which results in the
    need to reboot, Reports should still connect even though the
    database tables from the script are not loaded yet (for example,
    on Windows95 I get "REP-1098, Error reading PRODUCT_USER_PROFILE
    or SYSTEM_PRODUCT_PROFILE data" if I connect to a database without
    those tables... but I still connect).
    
    Regards,
    rcs
    
 | 
| 5007.4 | You should also try th ODBC notes file | CHSR38::ROHR | The Packers did it! | Mon Feb 10 1997 03:50 | 8 | 
|  |     Does logging on the PC give any more clues? 
    
    Also, you might want to put this note into the ODBC notes file. I am
    not sure Sue and Simon and Joe and all the other fine people who
    help out with ODBC and SQL Services are reading regularly in this notes
    conference.
                                   
    /Regina
 | 
| 5007.5 | client log needed | SQLSRV::MAVRIS | Sue Mavris - [email protected] | Mon Feb 10 1997 10:09 | 5 | 
|  | We're here (some of us anyway).  Regina is right.  For us to get anywhere 
with this, we're going to have to turn on client logging and see what that 
tells us.
Sue
 | 
| 5007.6 | Would you believe... | NOMAHS::SECRIST | Rdb WWS; [email protected] | Tue Feb 11 1997 16:17 | 8 | 
|  |     
    	The rdbodbc.ini wasn't in the C:\WINDOWS directory.  Apparently
    	ODBC Test, MS-Acces, etal. can live without this, but Developer
    	2000 products cannot ;-)
    
    	Regards,
    	rcs
    
 |