RV: MaxDB problems working in ORACLE mode with embedded SQL in C/C++ programs (details)

Dear reader,

As you see the commented problem is resolved for that, and what me
concerns, the list can be closed.

Best regards,

Elbertus Lochtenberg

-----Mensaje original-----
De: Simenec, Thomas [mailto:thomas.simenec@xxxxxxx] 
Enviado el: jueves, 30 de diciembre de 2004 10:34
Para: Elbertus Lochtenberg
CC: Döhr; Markus ICC-H; Carlo Andreoli
Asunto: RE: MaxDB problems working in ORACLE mode with embedded SQL in
C/C++ programs (details)

Hi Elbertus,

To close the problem simply send an email to maxdb@xxxxxxxxxxxxxxx that
the recommended solution worked to let the other users know.

I wish you happy New Year, too.

Regards,

Thomas

-----Original Message-----
From: Elbertus Lochtenberg [mailto:barry@xxxxxxxxxxxxx] 
Sent: Donnerstag, 30. Dezember 2004 09:57
To: Simenec, Thomas
Cc: 'Döhr, Markus ICC-H'; 'Carlo Andreoli'
Subject: RE: MaxDB problems working in ORACLE mode with embedded SQL in
C/C++ programs (details)

Hi Thomas,

Thanks for your recommendation, it Works.

This solution however creates another secondary problem because the
product where we want to use MaxDB, uses depending of the kind of
installation different databases, each actually identified with his own
database user. 

Using this solution the database user and password always must be the
same. 

I tried to put the instance identifier (USING) in a host variable and,
however the pre-compiler generates a warning (-885   Variable may be
truncated), this host variable is accepted and it works. 

strcpy(dbident,"localhost-quorumec");
EXEC SQL CONNECT qecdba IDENTIFIED BY qecdba USING :dbident;

This solution can help us to differentiate the databases by instance
identifier and not by database user. The only particular is that we have
to create a new instance for each database, but OK it works.

As I told you before, I thank you very much for the proposed solution
and for what me concerned, the list can be closed for this reported
problem.

If there is something what I have to do for closing this list let me
know.

Best regards and a happy new year,

Elbertus Lochtenberg  
  

-----Mensaje original-----
De: Simenec, Thomas [mailto:thomas.simenec@xxxxxxx] 
Enviado el: miércoles, 29 de diciembre de 2004 14:21
Para: Elbertus Lochtenberg
CC: maxdb@xxxxxxxxxxxxxxx
Asunto: RE: MaxDB problems working in ORACLE mode with embedded SQL in
C/C++ programs (details)

Hi,

Please try the following connect statement:

EXEC SQL CONNECT qecdba IDENTIFIED BY qecdba AT session1 USING
"localhost-quorumec";

In this case username, password, and session name are handled case
insensitive, that means they are uppered and then used for connect to
the database.

If you want a case sensitive handling of username, password, and session
name, you have to write

EXEC SQL CONNECT "qecdba" IDENTIFIED BY "qecdba" AT "session1" USING
"localhost-quorumec";

In this case username, password, and session name are used in lower case
to connect to the database.

Regards,

Thomas Simenec
SAP Labs Berlin

-----Original Message-----
From: Elbertus Lochtenberg [mailto:barry@xxxxxxxxxxxxx] 
Sent: Mittwoch, 29. Dezember 2004 10:29
To: maxdb@xxxxxxxxxxxxxxx
Subject: MaxDB problems working in ORACLE mode with embedded SQL in
C/C++ programs (details)

Dear Reader,
 
At the following the installation and implementation procedure details 
 
Instalation details MaxDB:
 
Unix server:                              HP-UX
Download MaxDB:                    xdb-all-hpux-64bit-hppa-7_5_00_19.tgz
Installation user:                       root
Development account user :       qec
Installation directory:                 /exportacion/Maxdb
 
Database creation with webdbm:
 
Database server:                       localhost
Name :                                     quorumec
DBM user:                                qecdbm
DBM user password:                 qecdbm
DBA user:                                qecdba
DBA user password:                 qecdba
Initialize parameters with default values
OLTP
Data volume DATA0001 size      10000
Log volume LOG001 size           6000
 
Connecting to the database instance with the DBA user:
 
webdbm:                      OK
websql:                        OK
loadercli:                      OK
dbmcli:                         OK
sqlcli:                           OK
Test program run-time:   errror  -709 (CONNECT failed, check SERVERDB)
 
Some embedded SQL connect statement tried in the test program:
 
EXEC SQL CONNECT 'qecdba' IDENTIFIED BY 'qecdba'
           AT 'sesion1' USING 'quorumec';
 
EXEC SQL CONNECT 'qecdba' IDENTIFIED BY 'qecdba'
           AT 'sesion1' USING 'localhost-quorumec';
 
Pre-compiler options:
 
Source file:                   Prueba.cpc 
cpc -H nocheck -E cansi -S oracle -c Prueba
 
Run time creation instruccions and link libraries used:
 
cc Prueba.c +DD64 -I$HOME/include -I$SMPATH/exits 
-L/explotacion/Maxdb/sdb/programs/sdk/7500/incl
-L/explotacion/Maxdb/sdb/programs/sdk/7500/lib/lib64 
-lpcrl -lsqlca -L/usr/lib/pa20_64 -lc 
-o Prueba
 
Special configuratios for ORACLE connection:
 
Parameter file              NO
Configuration file            NO
Environment variables:
 
The only environment variables that I adapt are LD-LIBRARY_PATH, LPATH y
PATH for the location of link libraries en executables of the proper
MaxDB product.
 
Best Regards,
 
Elbertus Lochtenberg
Project Manager
Teleserver S.A.
Mobile: +34628270643
E-mail: barry@xxxxxxxxxxxxx





--
MaxDB Discussion Mailing List
For list archives: http://lists.mysql.com/maxdb
To unsubscribe:    http://lists.mysql.com/maxdb?unsub=gcdm-maxdb@xxxxxxxxxxx