Oracle SQL (64 bit) vs Visual Cron (32 bit) - VisualCron - Forum

Community forum

jaramill
2009-10-15T20:53:53Z
My I.T. admins mentioned that even though I can create a SQL connection fine, I can't execute anything since our Oracle clients are 64-bit (10g, 11g) but Visual Cron is in 32-bit. Do you know when Visual Cron will be written in 64-bit?

Thanks,
Gio
Support
2009-10-15T23:21:10Z
VisualCron uses it's own 32 bit dll (client) to perform executes. So, it should not matter that other Oracle clients (or Servers) are 32 bit.

As for pure 64 bit maybe we will go for that later this year but currently we see no special advantages in x64 or limitations in x86.

Have you tested a query against Oracle from VisualCron?
Henrik
Support
http://www.visualcron.com 
Please like  VisualCron on facebook!
jaramill
2009-10-15T23:29:07Z
Support wrote:

VisualCron uses it's own 32 bit dll (client) to perform executes. So, it should not matter that other Oracle clients (or Servers) are 32 bit.

As for pure 64 bit maybe we will go for that later this year but currently we see no special advantages in x64 or limitations in x86.

Have you tested a query against Oracle from VisualCron?



Yes I have tested a simply query (SELECT SYSDATE FROM DUAL) against Oracle from Visual Cron. Was able to setup an Oracle database connection no problem. But when I run the SQL task here's the error message:

Exception in Task: Attempt to load Oracle client libraries threw BadImageFormatException. This problem will occur when running in 64 bit mode with the 32 bit Oracle client components installed.
Support
2009-10-15T23:31:01Z
What is the operating system VisualCron resides on? Is VisualCron installed in the x86 folder location?
Henrik
Support
http://www.visualcron.com 
Please like  VisualCron on facebook!
jaramill
2009-10-15T23:37:42Z
Support wrote:

What is the operating system VisualCron resides on? Is VisualCron installed in the x86 folder location?


The server it's installed on has 2 drives: (C, D). The C: drive does have 2 "Program Files" folders:

C:\Program Files
C:\Program Files (x86)

But is not in those. It's on the 😨 drive

D:\Visualcron

The server is running:

Microsoft Windows Server 2003
Enterprise x64 Edition
Service Pack 2 wit

Intel(R) Xeon(R) CPU
@2.66GHz
16.0GB of RAM
Support
2009-10-15T23:45:42Z
Try uninstall and then install i default directory (x86) - and then run again.
Henrik
Support
http://www.visualcron.com 
Please like  VisualCron on facebook!
jaramill
2009-10-16T00:09:50Z
Support wrote:

Try uninstall and then install i default directory (x86) - and then run again.


Actually he did have it initially in that directory and it didn't work. But what we will try is to install the 32-bit Oracle client as we only have 64-bit running. The question to you is, which one will Visual Cron choose by default?
Support
2009-10-16T00:12:30Z
Neither, because VisualCron has it's own client locally. I guess the problem is only that VisualCron is not executed from the x86 folder. For VisualCron it is alright, but the dll (client) is x86 and probably not like that environment. That is a guess from my side.

There is also another alternative and that is to change the connection to use OLEDB or ODBC. Then you won't have any problem.
Henrik
Support
http://www.visualcron.com 
Please like  VisualCron on facebook!
jaramill
2009-10-16T00:32:14Z
Support wrote:

There is also another alternative and that is to change the connection to use OLEDB or ODBC. Then you won't have any problem.


Here are the error results for other connection types besides ORACLE:

OLEDB: Exception in Task: The 'OraOLEDB.Oracle' provider is not registered on the local machine.

ODBC: ERROR [IM004] [Microsoft][ODBC Driver Manager] Driver's SQLAllocHandle on SQL_HANDLE_ENV failed
Support
2009-10-16T00:39:33Z
You must setup the ODBC or OLEDB correctly in Windows first (Control panel). Test connection there first. Then select the Connection in VisualCron.
Henrik
Support
http://www.visualcron.com 
Please like  VisualCron on facebook!
jaramill
2009-10-16T02:35:50Z
Support wrote:

You must setup the ODBC or OLEDB correctly in Windows first (Control panel). Test connection there first. Then select the Connection in VisualCron.


Okay I'm on the client machine and I have all the necessary drivers installed and even tested the connections through them via Control Panel -> Administrative Tools. I created a User DSN, System DSN, File DSN, and I have many drivers including the Oracle ones:

Driver: Microsoft ODBC for Oracle version 2.576.3959.00
Filename: MSORCL32.DLL
Date: 2/17/2007

Driver: Oracle in OraClient10g-home1 version 10.02.00.01
Filename: SQORA32.DLL
Date: 8/29/2005

I'm able to create a SQL Connection and test but when I use one of the many examples I created (i.e. using Connection Guide, using existing Data Source) I get this error:

ERROR [IM002] [Microsoft][ODBC Driver Manager] Data source name not found and no default driver specified
PeterW
2009-10-16T21:24:48Z
jaramill wrote:

ERROR [IM002] [Microsoft][ODBC Driver Manager] Data source name not found and no default driver specified



Try using the fix in this link and adding it to both the 64 bit and 32 bit ODBC managers.

http://forums.devarticle...iver-specified-8346.html 

I had a similar problem (not with VisualCron) when I attempted to add an ODBC in a 64 bit version of windows. Good luck and I hope this helps!

-Peter
Scroll to Top