So, since ObjectCall is an unsupported connectivity method and has been for quite some time, I figured I'd post this to the group to see if anybody's done anything with it. Apparently, ObjectCall seems to work ok up until Unidata 6.1 under Linux. We recently moved our development to Red Hat Enterprise 5 & Unidata 7.1.8 but still have some ObjectCall interfaces that are running on our production system...Solaris 9 / Unidata 7.1.
The main issue which I ran into was after installing a fresh copy of Unidata under RH, I went to try setting up the server & database for ObjectCall via uniapi_admin. Unfortunately, was getting an error such that "chmod ... failed" when trying to open the uniapi_server_db & uniapi_admin_db files for modification. That made me sad. So, I thought, hmm, I wonder if I can copy of the 4 files for ObjectCall over from the Solaris (working) machine and restart Unidata. Did that. No dice...but now I am getting the following: Cannot open ObjectCall server database. Press any key to continue.. So, then I went to check permissions and seems to have the right permissions...and I am invoking uniapi_admin as root. $ ls -l /usr/ud71/ods total 32 drwxr-xr-x 4 root root 4096 Aug 15 08:42 demo drwxr-xr-x 2 root root 4096 Aug 15 08:42 include -rwxr-xr-x 2 root root 2048 Sep 19 10:05 uniapi_admin_db.dir -rwxr-xr-x 2 root root 2048 Sep 19 10:05 uniapi_admin_db.pag -rwxr-xr-x 2 root root 1024 Sep 19 10:05 uniapi_server_db.dir -rwxr-xr-x 2 root root 1024 Sep 19 10:05 uniapi_server_db.pag Eh, anybody have any ideas or know of any "quick fixes" aside from moving to Intercall and/or UniObjects? Our Datastage environment (even in prod) still uses ObjectCall to connect to Unidata and have not yet transitioned to these other methods of client access. TIA, Andy Pflueger Programmer/DBA Ivy Hill - Louisville, KY ------- u2-users mailing list [email protected] To unsubscribe please visit http://listserver.u2ug.org/
