Subscribe via RSS
Toggle Submenu
  1. Categories
  2. Recent
  3. Tags
View Replies (4)

Resolved Use of IBM UDB database through ODBC

  1. How-to
0
Votes
Undo
  1. Mark Lundell
    Mark Lundell
  2. PowerServer 2020 or older (Obsolete)
  3. Friday, 13 March 2020 22:35 PM UTC

I can connect if I use the .net driver, but there seems to be a bug in the driver causing some very slow responses.

I have set up a 64 bit ODBC connection and tested successfully via the ODBC tool.

I have set up datasource NSDADEV_CONTROL and linked it to this ODBC source and tested successfully.

I have set up my sqlca transaction object to the datasource NSDADEV_CONTROL and tested successfully.

I run the app (web) using sqlca and get Error SQLDBCODE = 1, and DBError = Invalid Argument.

If I set  dbms = 'odb_db2' , and dbparm="ConnectionCache='NSDADEV_CONTROL'  I get the same error.

Any Ideas????

 

 

  1. DB2
  2. PowerServer Web
increase powerserver developer version user sessio...
Edge Chromium for Powerserver apps
Responses (4)
Armeen Mazda @Appeon
Armeen Mazda @Appeon Accepted Answer Pending Moderation
  1. Friday, 13 March 2020 22:44 PM UTC
  2. PowerServer 2020 or older (Obsolete)
  3. # 1

The ODBC is only for SAP/Sybase databases.  Please refer to the documentation: https://docs.appeon.com/appeon_online_help/ps2019/server_configuration_guide_for_net/supported_database_drivers.html

We are not aware of other customers complaining about performance issues with IBM UDB.  I think it may be a config/environment issue.

Comment
There are no comments made yet.
Chris Pollach @Appeon
Chris Pollach @Appeon Accepted Answer Pending Moderation
  1. Friday, 13 March 2020 22:59 PM UTC
  2. PowerServer 2020 or older (Obsolete)
  3. # 2

Hi Mark;

   Please use PowerServer's "native" DB2 driver and not ODBC.

Regards ... Chris

Comment
There are no comments made yet.
Mark Lundell
Mark Lundell Accepted Answer Pending Moderation
  1. Saturday, 14 March 2020 01:38 AM UTC
  2. PowerServer 2020 or older (Obsolete)
  3. # 3

Thanks for the response.  When I referred to the .net driver I meant the native DB2 driver.  With the Native driver I was able to connect, but the PowerServer error log showed a list of data base errors.  When I get the chance, I'll cut and paste some of the error list.

 

Comment
There are no comments made yet.
Mark Lundell
Mark Lundell Accepted Answer Pending Moderation
  1. Monday, 16 March 2020 16:52 PM UTC
  2. PowerServer 2020 or older (Obsolete)
  3. # 4

Chris,  when you told me to use the dbms="ODBC TRACE"  did you intend for me to try that with the DB2 native driver?  If so, I tried that and can't find a trace file.

 

 

 

Comment
Chris Pollach @Appeon
  1. Chris Pollach @Appeon
  2. Monday, 16 March 2020 18:29 PM UTC
Hi Marc;

For SQL tracing in *native* PB Apps, you would use ... SQLCA.DBMS = "TRACE ODB"

For tracing in PowerServer, you would can set the "server" trace level in PS's AEM Console to either to "Standard" (default), "Developer" or "Debug" mode depending on the level of tracing you require. For the App itself, you can then choose "Error", "Info" or "debug". Note that both must be set to get detailed information.

HTH

Regards ... Chris
  1. Helpful
There are no comments made yet.
  • Page :
  • 1


There are no replies made for this question yet.
However, you are not allowed to reply to this question.