error when launching cadence IC610

 HI Andrew,

 My OA setup situlation is: I configured OpenAccess after I installed IC610 base (directory: /cadence/IC610/OA), but I didn't change the OA configuration after I updating to 614 (When I did the configuration after updating, I jumped the OA part).Now there is another OA profile: /cadence/IC610/oa_v22.04.072, which I believe comes with the IC614. 

NOt sure if I have $OA_HOME set. What I did was set OA_HOME in the "bash" file (export OA_HOME=/cadence/IC610/OA).

Besides, could you please let me know how to "unset the envionment variable (in csh "unsetenv OA_HOME")?" what do you mean by "csh"? Sorry I'm a rookie.

THanks Andrew 

Please remove the definition of OA_HOME from your .bashrc (if that's where you put it). Interactively (in the bash shell) you can always type "unset OA_HOME" (unsetenv is the equivalent csh (C shell, an alternative to "bash" or "ksh" or the various other shells in UNIX) syntax, but since you're not using csh it's irrelevant). Setting OA_HOME is not a good idea for any of the Cadence releases; they should always use the OpenAccess libraries that come with the tools, as that is what they were tested with. It certainly will not work to use IC614 with the OA libraries from IC610 - they aren't even the same data model.

Having done this, can you check that /cadence/IC610/share/oa is a link to the oa_v22.04.072 directory (do an "ls -l /cadence/IC610/share/" to check).

Regards,

Andrew.

 HI Andrew,

 I unset the OA_HOME, then I got another error

 /cadence/IC610/tools/dfII/bin/64bit/virtuoso: error while loading shared libraries: libQtAssistantClient.so.4: cannot open shared object file: No such file or directory

If I further remove  "export CDS_AUTO_64BIT=ALL" in the bash file, the error information goes back to our very first one with IC610.

/cadence/IC610/tools/dfII/32bit/virtuoso: symbol lookup error: /cadence/IC610/tools/QT/lib/libQTGui.so.4: undefined symbol: XRenderFindStandardFormat

I guess I should keep the  "export CDS_AUTO_64BIT=ALL" since our machine is 64 bit, right?

THe result of  "ls -l /cadence/IC610/share/" is:

total 172
drwxr-xr-x  2 cdsmgr cdsmgr 4096 Feb  4 03:33 bin
drwxr-xr-x  7 cdsmgr cdsmgr 4096 Oct 22 11:45 catena
drwxrwxr-x  3 cdsmgr cdsmgr 4096 Apr  8 15:42 cdsdoc
drwxr-xr-x 19 cdsmgr cdsmgr 4096 Feb  4 03:33 cdssetup
drwxr-xr-x  3 cdsmgr cdsmgr 4096 Nov 10 15:44 csr_cco
drwxr-xr-x  3 cdsmgr cdsmgr 4096 Jan 10 05:23 deft
drwxr-xr-x  3 cdsmgr cdsmgr 4096 Feb  4 03:33 dfII
drwxr-xr-x  2 cdsmgr cdsmgr 4096 Oct 11  2006 gpdk
drwxr-xr-x  2 cdsmgr cdsmgr 4096 Aug 25  2009 il
drwxr-xr-x  3 cdsmgr cdsmgr 4096 Jan  6 22:24 iota
drwxr-xr-x  5 cdsmgr cdsmgr 4096 Feb  4 03:45 java
drwxr-xr-x  2 cdsmgr cdsmgr 4096 Oct 11  2007 license
lrwxrwxrwx  1 cdsmgr cdsmgr   16 Apr 11 18:56 oa -> ../oa_v22.04.072
drwxr-xr-x  2 cdsmgr cdsmgr 4096 Jan  4 04:14 oaInstallers
drwxr-xr-x  2 cdsmgr cdsmgr 4096 Jan  3 20:14 oaPlugIns
drwxr-xr-x  5 cdsmgr cdsmgr 4096 Nov  6  2009 patchData
drwxr-xr-x  3 cdsmgr cdsmgr 4096 Jan  7  2005 sev
drwxrwxr-x  3 cdsmgr cdsmgr 4096 Oct 25  2006 sna
drwxr-xr-x  2 cdsmgr cdsmgr 4096 Aug 25  2009 tcl
drwxr-xr-x  3 cdsmgr cdsmgr 4096 Apr 15  2010 tlfUtil
drwxrwxr-x  4 cdsmgr cdsmgr 4096 May 19  2006 verity
drwxr-xr-x  2 cdsmgr cdsmgr 4096 Jan  4 04:14 version

Thanks Andrew 

Just because you're running on a 64 bit machine doesn't mean you have to run the 64-bit versions of the executables. The 32 bit versions will run perfectly well on 64 bit hardware (in fact there's a small performance penalty with running the 64-bit versions, because the memory usage is greater as all pointers become 8 bytes rather than 4 bytes, so the memory access takes longer). So you only need to use 64 bit mode if your designs have capacity limitations (i.e. the executable needs more than about 3.7Gbytes of memory).

The error about  libQtAssistantClient.so.4 is very odd - this should be found in the tools/QT/lib/64bit dir in the installation (and also in the tools/QT/lib dir for 32 bit).

Something sounds very wrong here. You seem to be getting very peculiar failures which do not match what we've seen anywhere else. 

You should contact Customer Support (or contact Cadence through your normal support channel if you're a university) - as it's going to be very hard to diagnose this in a community forum.

Regards,

Andrew.

 Thanks for the advices. We'll turn to them and see what they can do.

Thanks for all the help.