DataStage 8.7 Oracle Connector stage unable to load ccora11g.dll

-

Problem(Abstract)

DataStage 8.7 job utilizing Oracle Connector errors with error message "Error loading connector library ccora11g.dll. %1 is not a valid Win32 application."

Symptom

DataStage Oracle Connector job errors with message "Error loading connector library ccora11g.dll. %1 is not a valid Win32 application."


Cause

DataStage 8.7 on Windows is still a 32 bit application and therefore still requires the use of 32 bit 3rd party drivers. Either the 64 bit Oracle client libraries are installed or the Windows system environment variables PATH and LIB are still pointing to the Oracle 64 bit client install folders.

Environment

Window Server 64 bit installs with Information Server V8.7

Diagnosing the problem

1. Check if the Windows Server installation is 64 bit


2. If the Windows is 64 bit, check if the Oracle Client install is 64 bit


Resolving the problem

If Windows is 64 bit and the Oracle client installed on the DataStage Server is 64 bit, the 64 bit Oracle client needs to be uninstalled and the Oracle 32 bit client installed.

If Windows is 64 bit and the Oracle client installed is already 32 bit, check the System environment variables LIB and PATH to ensure that they do not include any 64 bit Oracle client folders and they do include 32 bit Oracle client folders instead.



Source: http://www-01.ibm.com/support/docview.wss?uid=swg21580377






Popular posts from this blog

Shrink you container size up to 95%.

-
BLAFS is a bloat-aware filesystem for container debloating. The design principles of BLAFS are effective, efficient, and easy to use. It detects the files used by the container, and then debloats the container by removing the unused files. The debloated containers are still functional and can run the same workload as the original containers, but with a much smaller size and faster deployment. https://github.com/negativa-ai/BLAFS?tab=readme-ov-file
Read more

alma linux: dnf Module yaml error: Unexpected key in data

-
While applying recent updates to a server running Rocky Linux 8, an error presented itself. Module yaml error: Unexpected key in data: static_context [line 9 col 3] Module yaml error: Unexpected key in data: static_context [line 9 col 3] The solution turned out to be a simple one. Update the libmodulemd first to correct the problem then perform the dnf updates as usual. dnf update libmodulemd For a detailed explanation as to the cause of this problem.
Read more