RADE

Source Code Manager

The Oracle Glue Library

Dealing with versions of the Oracle client library

Use Case

Abstract

    This article is useful when installing the SCM product on one Unix platform and upon Oracle and when the version of the Oracle client library that is available on the site is too different than the one used when building SCM. This paper explains how to rebuild a SCM library in order for SCM programs to be able to use this Oracle client library.

  • Purpose of The Oracle Glue Library
  • How To Rebuild It
  • In Short

Purpose of The Oracle Glue Library

OracleGlue.gif (1818 bytes) The Oracle Glue library is a small library used by the kernel for calling the functions provided by the OCI library. The interest of this library is to be avoid to deliver the full SCM kernel in case of differences in the OCI library: only the Oracle Glue library should be rebuilt and this can be done directly in a SCM installation.

information.gif (174 bytes) Note that the "Oracle Glue" layer does not allow the use of any version of Oracle. The purpose of this library is just to help to support changes between close versions of the Oracle client library. The versions of Oracle that can be used with a version of SCM are those described in the corresponding level of documentation of CAA RADE.

[Top]

How To Rebuild It

Considering <CAA_Root> as the CAA RADE root installation directory, go under <CAA_Root>/OS/resources/Adele/OracleGlue (*), and run the ReplaceLib shell.

(*) Where OS is a directory the name of which is an acronym that depends on the operating system. Refer to [6] to get the current list of operating systems supported and associated acronyms.

Before running the shell, check that

The ReplaceLib shell will

If the shell runs successfully, SCM command should be ready to be used.

[Top]


In Short

The calls to the OCI's functions are embedded in a small SCM library which can be rebuilt on a site in order to deal with an incompatible version of the OCI library.

[Top]


References

[1] Building and Launching a CAA V5 Use Case

[Top]

History

Version: 1 [May 2001] Document created
[Top]

Copyright © 2000, Dassault Systèmes. All rights reserved.