We've been running 5.7.8 on Win2k8 (64-bit) w/ VC forced into 32-bit mode via the VisualCronBitSetter.application w/o issue.

We've upgraded to 6.0.5 (now 6.0.6 w/ same issue) and forced back to 32-bit mode w/ the VisualCronBitSetter.application now we're getting "'OraOLEDB.Oracle provider is not registered on the local machine" while testing our Oracle connections.

Please help?

There is no difference between the versions in terms of SQL execution. What is important is to verify:

1. in the Task manager - is the VisualCron service running as 32 or 64 bit?
2. are you using the 32 or 64 bit driver?

The most probably reason is that these above are not the same.

---

VC service is showing *32; VC client is not.

How do we know if we're using 32 or 64 bit driver? It's whatever is in VC. Locally install Oracle client is 32-bit and was working fine in 5.7.8.

Thanks much.

Are you using option Oracle->Oracle and not any ODBC or OLEDB driver?

---

Type is Standard Security (Oracle), Provider is OraOLEDB.Oracle, if I understand correctly.

I think, if you use the built in driver in VisualCron will not have problem with 32 or 64 bit. Try creating a new Connection with option Oracle->Oracle and not use OLEDB and ODBC.

---

Just got a report back from the user, our original jobs are running as originally configured in 5.7.8, it's just that the "test" in the connection setup indicates it failed.

Haven't we been through this before w/ VC?

That is normal behavior. The reason for this is that configuration is done with the Client (without sending the actual connection through the Server). This works in 99% of the cases. But in your case the client is running in x64 mode and cannot find the driver because of that. You need to use the bitsetter on the client as well.

Still, we recommend using our own driver. It is a lot faster too.

Just got a report back from the user, our original jobs are running as originally configured in 5.7.8, it's just that the "test" in the connection setup indicates it failed.

Haven't we been through this before w/ VC?

---

Terrific, how do we set the bit rate for the client please?

We will investigate using the built-in drivers for our Oracle connection. Question, we're using tnsnames and for some of the connections, wallet. Will this affect being able to use the built-in drivers?

Same way as you set it for the server.

---