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

Resolved ORA-12154

  1. Issue
0
Votes
Undo
  1. Chee Boon Ang
    Chee Boon Ang
  2. PowerBuilder
  3. Wednesday, 5 July 2017 11:53 AM UTC

Hi Community,

 

Just installed Appeon PB2017. 

export the DB profile from current PB12.5 and import to Appeon PB2017. ( on the same machine )

Encounter the ORA-12154: TNS: Could not resolve the connect identifier specified.

i have no problems connect from the PB12.5 ( classic ) but face the problems from PB2017.

 

What could i have missed ! 

  1. Oracle
New Windows 10 icons?
Copying datawindows
Accepted Answer
Appeon Support Team
Appeon Support Team Accepted Answer Pending Moderation
  1. Friday, 7 July 2017 05:52 AM UTC
  2. PowerBuilder
  3. # Permalink

Hi,

 

It may cause by a bug of Oracle, Oracle doesn’t support the application contains parentheses in the installation path which connect to the Oracle database.

Please upgrade Oracle client or install PB on another path to solve this issue.

https://blogs.msdn.microsoft.com/debarchan/2009/02/03/good-old-connectivity-issue-with-oracle-in-x64-environment/

 

Regards,

ZhaoKai

Comment
There are no comments made yet.
Responses (6)
Miguel Leeuwe
Miguel Leeuwe Accepted Answer Pending Moderation
  1. Sunday, 30 June 2019 13:36 PM UTC
  2. PowerBuilder
  3. # 1

I have seen the same error.

The solution was to set the following line in sqlnet.ora file:

#previously set to: (NTS) but gives an error, so now:
SQLNET.AUTHENTICATION_SERVICES = (NONE)

 

The file is located (in my case) here:

D:\app\miguel\product\11.2.0\client_3\network\admin

 

Another solution might be to set the TNS_ADMIN variable to where your tnsnames.ora file is located (and sqlnet.ora):

  1. Create a new environmental variable called TNS_ADMIN and set the value to "C:\xxx\product\xxx\client_x\Network\Admin"
  2. Restart machine
Comment
There are no comments made yet.
jordi fernandez
jordi fernandez Accepted Answer Pending Moderation
  1. Wednesday, 26 June 2019 16:00 PM UTC
  2. PowerBuilder
  3. # 2

the problem is the oracle  installation from  C:\Program Files (x86)  with 

parenthesis
Comment
There are no comments made yet.
Olan Knight
Olan Knight Accepted Answer Pending Moderation
  1. Saturday, 23 February 2019 17:43 PM UTC
  2. PowerBuilder
  3. # 3

We always install our Oracle clients onto the C drive directly, when possible.

C:\oracle\product\11.2\client_1\.......

 

Olan

Comment
There are no comments made yet.
Jack Huang
Jack Huang Accepted Answer Pending Moderation
  1. Saturday, 23 February 2019 03:24 AM UTC
  2. PowerBuilder
  3. # 4

I got the sam issue, too. 

pb 2017 R3 LTS 1880 install on windows 64bit and use oracle instant client 10.2.1. 

I can use Oracle instant client to connect to my database successfully.

Comment
There are no comments made yet.
Chris Pollach @Appeon
Chris Pollach @Appeon Accepted Answer Pending Moderation
  1. Wednesday, 5 July 2017 15:05 PM UTC
  2. PowerBuilder
  3. # 5

Hi Chee Boon;

  Please re-check all the DB Profile settings in PB 2017 against PB 12..5.x's to make sure all the connection information was transposed OK.

Also, are you running PB 12.5 or PB 2017 in ADMIN mode?

Regards ... Chris

Comment
Chee Boon Ang
  1. Chee Boon Ang
  2. Thursday, 6 July 2017 01:21 AM UTC
Hi Chris,



Yes, have re-checked the DB profile setting and they are identical.



Yes, running in ADMIN mode.



 



my machine is 64bits ( win 7 )



the default installed path for PB2017 is "C:\Program Files (x86)\Appeon"



does it matter ? 

  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.