× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.


  • Subject: Re: ODBC - DB2
  • From: Rob Berendt <rob@xxxxxxxxx>
  • Date: Thu, 27 Apr 2000 8:20:07 -0500

Can we see the entire SQL statement?  The additional help on the message is:
                                                             System:   GDISYS 
 Message ID . . . . . . . . . :   SQL0114                                     
 Message file . . . . . . . . :   QSQLMSG                                     
   Library  . . . . . . . . . :     QSYS                                      
                                                                              
 Message . . . . :   Relational database &1 not the same as current server &2.
 Cause . . . . . :   Relational database &1 was specified in a 3 part name in 
   the statement.  However, either the name is not the same as the current    
   server &2, or the name is not the same as a relational database name       
   specified previously in the statement.                                     
 Recovery  . . . :   Change the statement so the relational database name     
   specified is the same as the current server or so that all relational      
   database names in the statement match.                                     


From:
DSPMSGD RANGE(SQL0114) MSGF(QSQLMSG)






Imaginor@aol.com on 04/26/2000 05:43:24 PM
Please respond to RPG400-L@midrange.com@Internet
To:     RPG400-L@midrange.com@Internet
cc:      
Fax to: 
Subject:        ODBC - DB2

Just finished upgrading our AS/400 from a model 500 to a 720 series. One of 
our daily procedures includes sending/receiving sales data through ODBC 
connections to a software product called COGNOS.

After the upgrade was completed, the following error condition began 
appearing when we tried to execute the ODBC interface:  "A general exception 
has occurred during the operation to prepare request. Client Access ODBC 
driver (32 bit) (DB2/400 SQL) SQL0114 - Relational database S101A20M not the 
same as current server."

S101A20M is our AS/400 system name. We suspect some type of configuration 
problem but we need some assistance to pinpoint the specific cause. 

Thanks,

Mike Kim   
+---
| This is the RPG/400 Mailing List!
| To submit a new message, send your mail to RPG400-L@midrange.com.
| To subscribe to this list send email to RPG400-L-SUB@midrange.com.
| To unsubscribe from this list send email to RPG400-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---


+---
| This is the RPG/400 Mailing List!
| To submit a new message, send your mail to RPG400-L@midrange.com.
| To subscribe to this list send email to RPG400-L-SUB@midrange.com.
| To unsubscribe from this list send email to RPG400-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---

As an Amazon Associate we earn from qualifying purchases.

This thread ...


Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.