Oracle Configuration for Use with Adaplets

When the foreign federation is an Oracle database, you need to set parameters and environment variables in the init<SID>.ora file used by the Oracle server to support adaplets.

At minimum, these settings must be edited:

SettingValue
global_names = falseSpecify if database names in database links must match the global_name parameter of the database to which the link is connected.
open_cursors = n Use this formula to determine the required number:

(12 * # of concurrent 3DSpace users) + (12 * # of server threads) + 20 (if other Oracle applications are in use)

Each 3DSpace client (thread) normally uses 8 cursors. Adaplets increases the number of cursors to 12. If the 3DSpace Service is in use (clients are accessing 3DSpace over the internet), each thread of the multi-threaded 3DSpace Service requires the same number as other 3DSpace clients. The setting must also allow for open cursors for other Oracle applications that use the same server.

The remote database user (in the sample case, scott) must be defined in Oracle with at least the basic privileges to work with the tables plus CREATE DATABASE LINK. The role CONNECT provides this privilege. The 3DSpace user is generally created with RESOURCE and CONNECT roles, and therefore the other user may be similarly defined.

When using an adaplet with a 3DSpace Service, the remote Oracle instance needs to support more sessions than the connection pool size. These Oracle parameters should be set in init<SID>.ora or pfile as follows:

sessions=200 
processes=250

These values are guidelines, but both should be set to greater than the value of MX_CONNECTION_POOL_SIZE in the enovia.ini file (previously ematrix.ini). The default value for MX_CONNECTION_POOL_SIZE is determined by the Java heap size selected during the 3DSpace server installation (small = 10, medium = 20, large = 30).