VoiceGuide IVR Software Main Page
Jump to content

ORACLE Database Query

Recommended Posts

Hello I have a client that I need to migrate from 7.4 to 7.6.

but before it is necessary to make a query to an Oracle database.

in 7.4 and 7.6 give me the same error, I thought it was the version that was updated. but no.

try all these kinds of connections without result

Driver={Oracle in OraClient11g_home2};Server=;Dbq=DBHVQ;Uid=callcenter;Pwd=call;

Driver={Oracle in OraClient11g_home2};Dbq=DBHVQ;Uid=callcenter;Pwd=call;

ODBC;Driver={Oracle in OraClient11g_home2};SERVER=[];UID=[callcenter];PWD=[call];DBQ=[DBHVQ];

Driver={Oracle in OraClient11g_home2};Server=DBHVQ;Uid=callcenter;Pwd=call;

Driver={Oracle in OraClient11g_home2};Dbq=dbhvq.quito.hcjb.org;Uid=callcenter;Pwd=call;

Driver={Oracle in OraClient11g_home2};Dbq=DBHVQ;Uid=callcenter;Pwd=call;














Please your help, br







Share this post

Link to post

In supplied trace we could see 8 different approach attempts to achieve a connection to the database, all unsuccessful:


Driver={Oracle in OraClient11g_home2};Server=;Dbq=DBHVQ;Uid=callcenter;Pwd=call;,

ERROR [08004] [Oracle][ODBC][Ora]ORA-12154: TNS:could not resolve the connect identifier specified

Driver={Oracle in OraClient11g_home2};Dbq=DBHVQ;Uid=callcenter;Pwd=call;

ERROR [08004] [Oracle][ODBC][Ora]ORA-12154: TNS:could not resolve the connect identifier specified

Driver={Oracle in OraClient11g_home2};SERVER=[];UID=[callcenter];PWD=[call];DBQ=[DBHVQ];

ERROR [08004] [Oracle][ODBC][Ora]ORA-12154: TNS:could not resolve the connect identifier specified

Driver={Oracle in OraClient11g_home2};Server=DBHVQ;Uid=callcenter;Pwd=call;

ERROR [HY000] [Oracle][ODBC][Ora]ORA-12560: TNS:protocol adapter error


ERROR [HY000] [Oracle][ODBC][Ora]ORA-12541: TNS:no listener

Driver={Oracle in OraClient11g_home2};Dbq=DBHVQ;Uid=callcenter;Pwd=call;

ERROR [08004] [Oracle][ODBC][Ora]ORA-12154: TNS:could not resolve the connect identifier specified

Oracle.DataAccess.Client, (DESCRIPTION=(ADDRESS=(PROTOCOL=TCP)(HOST=, Provider=Oracle.DataAccess.Client,

ConnectAndRun_AdoNetFactory : '(DESCRIPTION' is an invalid connection string attribute


ERROR [08004] [Oracle][ODBC][Ora]ORA-12154: TNS:could not resolve the connect identifier specified


7 approaches were using the ODBC approach, which was accessed through ADO.NET System.Data.Odbc provider:

System.Data.Odbc : 

and one was using the ADO.NET Oracle.DataAccess.Client provider, which on your system is version:

Oracle.DataAccess.Client :


On thing of note is that the VoiceGuide Dialer was able to connect to the Oracle database using the ADO.NET Oracle.DataAccess.Client provider.

So suggest looking at VoiceGuide's Config.xml and the OutDialQue_ConnectString parameter. Same connection approach should work when used in a Database Query module.

143249.200   9                     db    config OutDialQue_ADODB_Provider = Oracle.DataAccess.Client
143249.200   9                     db    config OutDialQue_Database = dbhvq.quito.hcjb.org
143249.200   9                     db    config OutDialQue_ConnectString.len = 171

As the ADO.NET Oracle.DataAccess.Client approach works the suggest you use ADO.NET connection method instead of ODBC in the Database Query module.



If you however would like to establish the connection using ODBC :

It looks like there are many possible reasons why Oracle returns the "ORA-12154: TNS:could not resolve the connect identifier specified" error.

It's an error from Oracle so maybe Oracle support can shed more light why this error is returned in your case and what changes in Oracle's own configuration are needed for it to not return that error. No idea why the test of connection from the "Oracle ODBC Driver Configuration" app would return "Connection Successful", when attempts to use that ODBC connection return ORA-12154. Maybe there are some traces generated by Oracle that would shed more light on cause.

Searching for above error on internet brings up many hits.

Would recommend ensuring that only 32-bit Oracle clients are installed on system, and remove all 64-bit versions, and remove the ODBC DSN entries from the 64-bit ODBC Data Source Administrator.

Otherwise it looks like you have to reconfirm that the compatible versions of drivers are used and that Oracle configuration files and System-wide Environment Variables etc. are all correctly set in order for Oracles ODBC drivers to establish this connection.

Here are some threads that may provide some suggestions on what to look at. There are many other similar discussion that can be found on internet that may provide an answer.





Share this post

Link to post

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now