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

Resolved Oracle 19 ORA-28040 Error

  1. Issue
0
Votes
Undo
  1. Alexander Campbell
    Alexander Campbell
  2. PowerBuilder
  3. Monday, 22 August 2022 19:24 PM UTC

I'm trying to connect a PowerBuilder 2021 (Build 1509) program to Oracle 19c (upgraded from Oracle 10g.) Using Oracle SQL Developer, I can connect to the new servers.

However, in PowerBuilder, I get this error:

Any solutions?

Note: I don't want to ask the DBA to roll back to a less secure authentication.

Thanks.

How to use RUN powerscript function in a loop?
Datawindow Error - Item doesn't pass the validatio...
Responses (8)
Alexander Campbell
Alexander Campbell Accepted Answer Pending Moderation
  1. Wednesday, 24 August 2022 13:43 PM UTC
  2. PowerBuilder
  3. # 1

According to my DBA, I need a different Oracle client. I've asked him to confirm that 12.1 or 11.2 will work.

I found the matrix pasted in this discussion: oracle - Connecting to Oracle19C Server using Oracle11g client - Stack Overflow

Comment
There are no comments made yet.
John Fauss
John Fauss Accepted Answer Pending Moderation
  1. Tuesday, 23 August 2022 18:44 PM UTC
  2. PowerBuilder
  3. # 2

The PowerBuilder IDE is a 32-bit application, and therefore requires the 32-bit version of Oracle Client.

I suspect that SQL Developer is a 64-bit application and thus uses a 64-bit version of Oracle Client.

Comment
Alexander Campbell
  1. Alexander Campbell
  2. Wednesday, 24 August 2022 13:37 PM UTC
I have the 32-bit version of Oracle client. However, according to various on-line comments, SQL Developer doesn't use Oracle Client. Instead, it uses it's own java library. In my case, this is "jdbc.library C:\SQLdeveloper\jdbc\lib\ojdbc8.jar". (From the Properties tab of SQL Developer Help/About.)
  1. Helpful
There are no comments made yet.
Alexander Campbell
Alexander Campbell Accepted Answer Pending Moderation
  1. Tuesday, 23 August 2022 17:29 PM UTC
  2. PowerBuilder
  3. # 3

Olan,

Thanks for the suggestions. The SQLCA.DBMS = "ORA Oracle" is generated by the database painter. I tried creating a db profile under Oracle 10 and got the same result.

Comment
There are no comments made yet.
Bruce Armstrong
Bruce Armstrong Accepted Answer Pending Moderation
  1. Tuesday, 23 August 2022 01:01 AM UTC
  2. PowerBuilder
  3. # 4

What version of the Oracle client layer are you using?  And what minimum version of the Oracle client layer is your server configured to require.

Are you able to connect with some other product to the Oracle database from the same machine?

Normally this error means that the server is configured to require a certain minimum version of the Oracle client layer and the connection attempt is being make use a client layer that doesn't meet that minimum.

 

 

Comment
Alexander Campbell
  1. Alexander Campbell
  2. Tuesday, 23 August 2022 17:32 PM UTC
Bruce, thanks for your input. Per my post, I am able to connect with Oracle SQL Developer. But I have contacted the DBA about incompatibility between my client and Oracle 19.
  1. Helpful
There are no comments made yet.
Olan Knight
Olan Knight Accepted Answer Pending Moderation
  1. Monday, 22 August 2022 22:19 PM UTC
  2. PowerBuilder
  3. # 5

Try specifying just "ORA", and if that fails try using the O10 connection.
I have code that uses the Oracle 10 drive to connect to an Oracle 19 database that works.


Note:  the ORA connection SHOULD be working. Are you SURE the other parms are correct?

SQLCA.DBMS = "ORA"        or try "O10"
SQLCA.LogPass = <******************************>
SQLCA.ServerName = "xxxxxx:1521/xxxxx"
SQLCA.LogId = "sacampbe"
SQLCA.AutoCommit = False
SQLCA.DBParm = ""

Comment
There are no comments made yet.
Alexander Campbell
Alexander Campbell Accepted Answer Pending Moderation
  1. Monday, 22 August 2022 21:03 PM UTC
  2. PowerBuilder
  3. # 6

Thanks for the suggestion. This is the syntax of the database profiles:

SQLCA.DBMS = "O10 Oracle10g (10.1.0)"
SQLCA.LogPass = <********>
SQLCA.ServerName = "xxxxxx:1521/xxxxx"
SQLCA.LogId = "sacampbe"
SQLCA.AutoCommit = False
SQLCA.DBParm = "PBCatalogOwner='sacampbe'"

SQLCA.DBMS = "ORA Oracle"
SQLCA.LogPass = <******************************>
SQLCA.ServerName = "xxxxxx:1521/xxxxx"
SQLCA.LogId = "sacampbe"
SQLCA.AutoCommit = False
SQLCA.DBParm = ""

Comment
There are no comments made yet.
Alexander Campbell
Alexander Campbell Accepted Answer Pending Moderation
  1. Monday, 22 August 2022 20:48 PM UTC
  2. PowerBuilder
  3. # 7

I am using ORA.

Comment
John Fauss
  1. John Fauss
  2. Monday, 22 August 2022 20:55 PM UTC
OK. I'm not an Oracle person, but there are several people that are in the Community. I think it would be helpful and reduce the number of back/forth iterations if you would please post the SQLCA settings you are attempting to use (mask out any sensitive values!), so that everyone can inspect them? Do you still have a working connection to 10g? If so, I suggest you also include those connection settings.
  1. Helpful 1
There are no comments made yet.
John Fauss
John Fauss Accepted Answer Pending Moderation
  1. Monday, 22 August 2022 20:04 PM UTC
  2. PowerBuilder
  3. # 8

Which PowerBuilder native client database interface are you using? (SQLCA.DBMS = ???). I believe you should be using "ORA" for 19g.

Comment
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.