Hi Luís,

When I had this problem several years ago, I didn't find a better solution than to compile Virtuoso from source (being careful to use the same version as your server), install it onto a clean image, extract the necessary library and config files used in local connections by the isql client and then transplant them to the client instance. Once the source package is installed on the temporary instance, you'll find most of what you need referenced in the ODBC config files located under /etc/ I think, check for variations on the name, iodbc, unixodbc etc. You're going to want those config files and the libraries mentioned in them, possibly the whole /lib/virtuoso directory or wherever virtodbc.so is found. The config files will do double duty of defining the connections and the libraries they use. It's been a few years since I did this so I'm a bit hazy and you'll need to hunt around for the right config files, it's probably going to be a process of trial and error.

If your server was installed with the right options, you could also grab them from there but it's arguably easier, if slower, to install onto a clean instance with the right client options. It makes it easier to know what the package added and changed under /etc and /lib, so as to replicate those changes on your client instance, this also matters if the server and client have different OSs.

An easier solution is to install Virtuoso on the client instance and just disable the Virtuoso service, then edit the config files above with the remote server details, that would probably work too but you'll have an empty Virtuoso DB taking up a little disk space I guess. It's still necessary to get the Virtuoso version right of course.

Good luck,
Guiding Hand Solutions

Virtuoso-users mailing list

Reply via email to