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

Resolved Can't connect to Oracle database

  1. Issue
0
Votes
Undo
  1. Dmitry Funt
    Dmitry Funt
  2. PowerBuilder
  3. Monday, 5 April 2021 14:25 PM UTC

There is a serious problem with PowerBuilder 2019 R3:

We worked successively with Oracle 10 via native interface, afterwards 

we changed database profile to Oracle 19 via native interface, it worked

fine. Afterwards we wanted to return to Oracle 10 but PB writes

ORA-03134: Connections to this server version are no longer supported.

ORACLE_HOME and TNS_ADMIN are correct because SQL*Plus has

access to the both servers OK. What could be the matter?

Thanks.

  1. Database Profile
Estimated release date for MR 2019 R3
Error when running Task Scheduler
Responses (2)
Chris Pollach @Appeon
Chris Pollach @Appeon Accepted Answer Pending Moderation
  1. Monday, 5 April 2021 14:53 PM UTC
  2. PowerBuilder
  3. # 1

Hi Dimitry;

   Most likely it's because you set SQLCA.DBMS = "ORA" for O19C support. If you go back to O10g, you'll need to reset your driver to SQLCA.DBMS = "O10".

Regards ... Chris

Comment
Miguel Leeuwe
  1. Miguel Leeuwe
  2. Monday, 5 April 2021 15:24 PM UTC
Chris is probably right, but if that's not your problem....

Try doing a "TNSPING name_of_your_tnsname" from the command line.

That way you'll see the information of which oracle client is being found (since I assume you have both clients installed, the one for Oracle 10 and the one for Oracle 19c?)

Also check the bitness (32 or 64) of the the client used in the tns-ping
  1. Helpful
There are no comments made yet.
Dmitry Funt
Dmitry Funt Accepted Answer Pending Moderation
  1. Monday, 5 April 2021 19:08 PM UTC
  2. PowerBuilder
  3. # 2

Hi, Chris!

I am afraid the reason is another, as my settings

look like

// Profile orcl10
SQLCA.DBMS = "O10 Oracle10g (10.1.0)"
SQLCA.LogPass = <***>
SQLCA.ServerName = "orcl10"
SQLCA.LogId = "***"
SQLCA.AutoCommit = False
SQLCA.DBParm = "PBCatalogOwner='***',QualifyPublic=1,PackageProcs=1,DisableBind=1"
 

I guess something (in register may be) was changed

when PB worked with Oracle 19c. I changed only

ORACLE_HOME and TNS_ADMIN when shifted from

O10 to O19 and vice versa.

 

Regards...

Comment
Chris Pollach @Appeon
  1. Chris Pollach @Appeon
  2. Monday, 5 April 2021 19:32 PM UTC
Hi Dimitry ... In that case, my next guess would be that the Oracle DB client software vO19C is no longer compatible with O10G
  1. Helpful
Dmitry Funt
  1. Dmitry Funt
  2. Tuesday, 6 April 2021 12:51 PM UTC
Yes, this is a clue to difficulties, of course. Only

I don't understand why works client O19c when

ORACLE_HOME point to O10.
  1. Helpful
Chris Pollach @Appeon
  1. Chris Pollach @Appeon
  2. Tuesday, 6 April 2021 18:28 PM UTC
Sounds like Oracle has changed their more recent DB client drivers to be tuned more for O19C than comparability with older Oracle DBMS version. Just my guess.
  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.