Is just the filesystem being swung over? I guess you can install it on the passive node, or have the entire volume swing over. It appears the easiest would be to have it installed on the other node.
> -----Original Message----- > From: Weaver, Slade [mailto:[EMAIL PROTECTED] > Sent: Tuesday, April 06, 2004 6:15 PM > To: [EMAIL PROTECTED] > Subject: dbd configuration question > > > Hi, I have a question for the forum...... > > I currently support an environment where $INFORMIXDIR may > swing between > systems. It appears that the Perl DBD module was compiled to look for > the libixsql.so library at > /repsup1/informix/lib/esql/libixsql.so. That > file system is currently active on another physical system. > The active > $INFORMIXDIR on the affected server is /repcrs1/informix. This is > causing a problem with the DBD module because it is searching for the > library in the original file system. Is there any way to circumvent > this problem? > > Error message: > > install_driver(Informix) failed: Can't load > '/usr/local/lib/perl5/site_perl/5.6.0/sun4-solaris/auto/DBD/In > formix/Inf > ormix.so' for module DBD::Informix: ld.so.1: /bin/perl: fatal: > /repsup1/informix/lib/esql/libixsql.so: open failed: No such file or > directory at > /usr/local/lib/perl5/5.6.0/sun4-solaris/DynaLoader.pm line > 200. > at (eval 4) line 3 > Compilation failed in require at (eval 4) line 3. > Perhaps a required shared library or dll isn't installed > where expected > at /usr/local/ids-mon/monitoring_lib.pl line 52 > > Thanks, > > Slade Weaver >
