Note: You might need to change the permissions of this file to make it executable.Īssuming that you have source dsenv already then run:Ĭd $DSHOME/./branded_odbc/samples/example It can be found under either $DSHOME/./branded_odbc/example or $DSHOME/./branded_odbc/samples/example. The location of this program varies depending what version of DataStage you are using.
To do this you can use the program "example". This won't affect DataStage but can alter the results of your test, so if you modify the settings for these variables in dsenv, it is a good idea to start a brand new telnet session to make sure you are not inheriting unneeded values in these variables.Īfter you have confirmed that ddtestlib is working successfully following the instructions in previous step then you can continue to check if the DSN is properly configured.
As result of this, if you source dsenv multiple times in the same session you can end up with long values for these variables and this can cause some library conflicts. Note: When you source the dsenv file some variables like PATH and LIBPATH append new values to the existing value of the variables as opposed to replacing the entire value. Load of /opt/IBM/InformationServer/Server/branded_odbc/lib/VMdb222.so successful, qehandle is 0x3 A successful execution ddtestlib will show the version of the driver. If you change the dsenv you should source it and run this test again until ddtestlib works successfully. Note: Some databases may require the user to be part of a particular group for the user to access the libraries. To fix this problem you need to edit the file $DSHOME/dsenv and make sure that all the environment variables for this driver are properly set and that this user has proper access to these files. If you get a result like this, then the odbc driver is not accessing the libraries it needs. This is just an example:Įxec(): 0509-036 Cannot load program /opt/IBM/InformationServer/Server/branded_odbc/lib/VMdb222.so because of the following errors:Ġ509-022 Cannot load module /opt/IBM/InformationServer/Server/branded_odbc/lib/VMdb222.so.Ġ509-150 Dependent module libVMicu22.a(VMicu22.so) could not be loaded.Ġ509-022 Cannot load module libVMicu22.a(VMicu22.so).Ġ509-026 System error: A file or directory in the path name does not exist.Ġ509-150 Dependent module /opt/IBM/InformationServer/Server/branded_odbc/lib/VMdb222.so could not be loaded. If the libraries are not configured properly you will get one or more lines saying "Cannot load. ddtestlib /opt/IBM/InformationServer/Server/branded_odbc/lib/VMdb222.so This program is located under $DSHOME/./branded_odbc/bin, for example to test the driver of the example, you can run opt/IBM/InformationServer/Server/branded_odbc/lib/VMdb222.soĬ) Once you have identified this driver you can use the program ddtestlib to confirm that you have acess to the libraries that the driver needs. For example in this DSN:ĭriver=/opt/IBM/InformationServer/Server/branded_odbc/lib/VMdb222.soĭescription=DataDirect DB2 Wire Protocol Driver
Invalid database file driver genius 14 full#
Each DSN has a line that starts with "Driver=" and then the full path to the odbc driver used. This also will set the environment variable PATH and the library path (the name of this variable depends on the platform, LIBPATH for AIX and LD_LIBRARY_PATH for Linux, Solaris, and HP-UX).ī) Then you need to identify the driver you are using in your DSN. odbc.ini containing the Data Source Names (DSN). This will set the environment variable ODBCINI that points to the. Then source the dsenv file by going to $DSHOME and executing: Note: Please be aware that changes in this file are not reflected in DataStage until the Engine is restarted.Ī) Open a telnet session with the machine where the DataStage Engine is running and log as the same user that is trying to connect in DataStage.
The access to these libraries is configured in the file $DSHOME/dsenv which DataStage sources every time the Engine is started.
Invalid database file driver genius 14 drivers#
The first step to troubleshoot an ODBC connectivity error is to validate that DataStage can successfully load the libraries that the ODBC drivers need to connect to a database. To troubleshoot ODBC connectivity problems please follow these steps in sequential order.ġ) Test access to database libraries and odbc drivers outside of DataStage
0 kommentar(er)
