multiple OA installations, which one to use?

I'm setting up IC613 for the first time and I see that OA comes with
EXT71 (oa_v22.04.013), IC613 (oa_v22.04.032) as well as a standalone
OA directory (.02.02-p049). I'm not sure which one to use as OA_HOME.
In this post:

http://groups.google.com/group/comp...ad/0b136f534faf4f66/a78f755a6dea985c?lnk=raot

the user is advised to unset OA_HOME altogether, but I've read in the
EXT documentation that the OA installation that comes with EXT should
be used. If I unset OA_HOME, virtuoso complains. If I do need to set
OA_HOME, which path should I use? Thanks.

 

Show us the message where Virtuoso complains and don't set OA_HOME.
Maybe the local Virtuoso OA installation isn't right. You should have it
in the <Installation>/share/oa directory.

Marc

 

ERROR: $OA_HOME is not set and the Cadence installation does not
seem to have a valid default OA installation under
/.../IC610_lnx86/share/oa
Check your OA installation (you may need to re-run
the post-install configure step for your Cadence tools), or set the
OA_HOME variable to point to a valid OA installation.
See the "OpenAccess Installation and Configuration Guide"
for more information.
ERROR: Unable to set OA shared library path.

I just noticed that there is no OA installation in the IC6 folder.
We're upgrading to IC613ISR today so maybe that will solve that. But
back to the original question, which of my OA installations should be
used for OA_HOME? As I mentioned, EXT documentation says to use the OA
folder in /EXT/share/oa instead of /IC/share/oa. Does this only apply
if I want to use OA input to QRC instead of Assura input?

 

Again, don't set OA_HOME. Always install the OA version which is coming
with the tool (EXT, IC,..). The OA installation should be located in
<toolinstallation>/share/oa. The tool will pick it up from there.
The idea to have a central common OA installation is nice, but
unfortunately it does not work in the real world.


Marc

 

Marc Heise wrote, on 10/13/09 16:34:

Marc's right. You should always use the OA version that the software was built
and tested with. Trying to pick a central version which is at least as new as
all the software releases (which is what you'd have to do with $OA_HOME) that
you're using at once, is really hard. Especially as IC610 was DM3 based, and
EXT71 is DM4 based (IC612/IC613 are DM4 based). And even then, it's not what it
was tested with, and there's very little reason to mess with the OA version a
release was built with.

When you install a release, you should do the "configuration" step (provided
that it is offered). In the cases of older OA-enabled releases, this was
required to install the OpenAccess build somewhere (I always used to install it
in <instDir>/OpenAccess and then it would create a link <instDir>/share/oa to
point to this.

With newer releases the OA installation is pre-installed, so it will ask you
during configuration whether you want to use a different OA installation. For
example:

The current installation is [/cds/lnx86/IC613_hot/oa_v22.04.049]^
Do you want to use a different OpenAccess installation (y/n/q) ? [y]

And then answer n (unfortunately the default is "y").

Regards,

Andrew.

 

Thanks for the detailed responses Marc and Andrew. Another OA-related
problem: How do I configure Assura to use OA-compatible binaries
instead of CDB-compatible binaries? Is it a separate installation or
is there a matter of settings environment variable(s) (perhaps during
iscape configuration)? The Assura Installation Guide isn't really
clear on this, it just says you must use Assura OA with DFII OA and
Assura CDBA for DFII CDBA. Thanks.

 

Never mind, I got my network admin to check downloads.cadence.com and
there is indeed a separate installation for OA.