could not retrieve fields from Oracle database

[serajeg]

Hi all,
I have a customer who wants the caller to be directed to a group based on his preferred service path automatically based on his CLID.
the customer has an Oracle dbase with the customers CLID & preferred service path for each of them.
I created a VMPro module to connect to the dbase & retrieve the preferred path from it but I could not retrieve the required field from the dbase although I could open the dbase successfully.
here is the setup information:

1- IP Office 500 V2 with release 9.1.2.0.91
2- Voicemail pro release 9.1.2.0.61
3- Oracle database 11.2.0.1G R2 64bit Enterprise Edition
4- All applications are installed on Windows server 2008R2 64bit
5- attached are the snapshots of the VMPro module & Oracle dbase.
Link
any idea why I could not retrieve the required fields?
BR,
Moataz Zaki

 

[Gunnaro]

Never done an Oracle, but it looks like your setup is more or less correct.
VMPro manages to read the Table list of the DB, but not the Field names. That's really strange.

Wild guessing, but could it be that they are hidden/not published properly?
You could try to remove the ";persist security..." part shown in Step 4. Had some issues with that on Access DB's in the past.

Alternatively create a new dummy DB from scratch, see if you can connect to that.

Kind regards

Gunnar
_______
B.U.B.F

 

[stownsend]

I'm using MS SQL Server 2008 R2 and MS SQL Server 2014

My DB Path looks like:
Provider=MSDASQL.1;Password=<password>;Persist Security Info=True;User ID=<user>;Data Source=DFP-ODBC;Initial Catalog=<myDBName>

My Provider is selected to 'Microsoft OLE DB Provider for ODBC Drivers' then I have an ODBC DSN Defined to use 'ODBC Driver 11 for SQL Server'

Maybe for your Provider select the 'Oracle Provider for OLE DB' Might be the MS Oracle Driver not playing nice.

Or use the ODBC Drivers and define a DSN for your DB using the Oracle Driver. Is there another App you can use on that machine (Excel, the old Query Analyzer ) to use the same DSN to Query data?

Scott<-

 

[serajeg]

Hi Gunnaro,
I will try removing persist security once I am back to the customer.
I already created another dummy oracle dbase with the same result.I also exported this dbase to access dbase & it worked fine with the same setup.
the problem seems to be with Oracle dbase only.
BR,
Moataz

 

[serajeg]

Hi stownsend,
when I tried using 'Oracle Provider for OLE DB'& the connection did not success at all.
I used the same setup with access dbase after exporting it from Oracle & it works fine.
I am not sure how to define a DSN for my dbase using the Oracle driver, could you provide more information?
BR,
Moataz

 

[stownsend]

ODBC can be a Bit Tricky on a Win2008R2 system because of the 32bit vs 64 bit. On my 2008R2 system I created both 32bit and 64 bit DSNs as I didn't know which one VMPro used.

To Create a 64 Bit, Go to control panels, Admin Tools, Data Sources (ODBC)
Add, Select 'Microsoft ODBC for Oracle' and its Similar to how you create it in VMPro.

To Create a 32 Bit, Launch C:\Windows\SysWOW64\odbcad32.exe
Add, Select 'Microsoft ODBC for Oracle' and its Similar to how you create it in VMPro.


Then in VMPro, You select the Provider Tab, MS OLE DB for ODBC, Connection Tab, Use Datasource Name and select the name that you created in the ODBC Tool.

 

[intrigrant]

In my experience the VM Pro database wizard does not create a correct connection string for other databases as the Microsoft databases.
I use SQL Explorer to create a connection string and test the database, then I copy the connection string into the VM Pro database connection action. This hase saved me a lot of time many times.
I hope it works for you as well.