Hi Community,
Testing Data Source PRODERP failed: ORA-12154: TNS:could not resolve the connect identifier specified.
it was working with PB2017 after upgrade to PB2019 oracle connectivity is not working.
Thanks,
Raj
-
Rajkumar Elanchelian
- PowerServer 2020 or older (Obsolete)
- Thursday, 11 March 2021 08:13 AM UTC
Comment
- Kai Zhao @Appeon
- Friday, 12 March 2021 05:08 AM UTC
Hi Miguel,
Did you get this issue on database configuration in the PowerServer project? This issue should relate to the Oracle client or the configuration. Please restart the machine after installing Oracle client to make sure its configurations take effect.
1. Please confirm the current machine has correctly installed Oracle 32bit client.
2. Please verify on ODBC if you can add a data source using Oracle driver and whether it can test successfully. If it is not successful, please re-configure your Oracle listening service.
3. Please verify on PB IDE if you can successfully connect to the Oracle database using an ORA Oracle driver.
4 Are there multiple Oracle clients installed on the machine? One of our customers ran into the same issue because there is another Oracle Client installed and the default home is wrong.
Regards,
Zhaokai
Did you get this issue on database configuration in the PowerServer project? This issue should relate to the Oracle client or the configuration. Please restart the machine after installing Oracle client to make sure its configurations take effect.
1. Please confirm the current machine has correctly installed Oracle 32bit client.
2. Please verify on ODBC if you can add a data source using Oracle driver and whether it can test successfully. If it is not successful, please re-configure your Oracle listening service.
3. Please verify on PB IDE if you can successfully connect to the Oracle database using an ORA Oracle driver.
4 Are there multiple Oracle clients installed on the machine? One of our customers ran into the same issue because there is another Oracle Client installed and the default home is wrong.
Regards,
Zhaokai
- Miguel Leeuwe
- Friday, 12 March 2021 08:01 AM UTC
Hi Zhao Kai, thanks for answering,
1. Yes it has
2. ODBC? Okay, yes connects fine.
3. yes I can. (Our application also successfully connects and runs when not using powerserver).
4. I've uninstalled the 12c client that was on this computer and rebooted. Same problem same error.
Our application accesses the registry to get the connection information before connecting to Oracle. I'm thinking that maybe that logic has to change for powerserver?
I'm trying to create a small sample application and create a ticket if I can't figure things out.
regards,
1. Yes it has
2. ODBC? Okay, yes connects fine.
3. yes I can. (Our application also successfully connects and runs when not using powerserver).
4. I've uninstalled the 12c client that was on this computer and rebooted. Same problem same error.
Our application accesses the registry to get the connection information before connecting to Oracle. I'm thinking that maybe that logic has to change for powerserver?
I'm trying to create a small sample application and create a ticket if I can't figure things out.
regards,
- Miguel Leeuwe
- Friday, 12 March 2021 08:24 AM UTC
forgot to answer your first not numbered question:
No, I have no issue configuring the database in the ps project. All connects fine. The only thing I'm wondering about is that I cannot use a "TNS Name" in that configuration. It has to be the physical servername and the service in order to connect. Our program uses tnsnames.ora.
No, I have no issue configuring the database in the ps project. All connects fine. The only thing I'm wondering about is that I cannot use a "TNS Name" in that configuration. It has to be the physical servername and the service in order to connect. Our program uses tnsnames.ora.
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.
However, you are not allowed to reply to this question.