Search Results register_instance

Overview

The APPS.FND_CONC_DATABASE package is a low-level Oracle E-Business Suite registration utility that maintains the metadata records describing the database tier of a multi-tier EBS deployment. It belongs to the Oracle Applications Technology (FND) foundation layer and is owned by the APPS schema, declared with AUTHID CURRENT_USER. Its sole business function is to enroll database and database instance definitions into the EBS data dictionary so that the concurrent processing architecture can resolve which database instances participate in a given configuration and how they are reached over the network. The package header carries the revision stamp AFCPDBMS.pls 115.0 dated 2003/03/05, indicating that the interface has been stable across the 11i and R12 release families, including 12.1.1 and 12.2.2.

Key Procedures and Functions

• register_database — A function returning BOOLEAN. Its documented purpose is to register database information into the FND_DATABASE table. Parameters include database name, database domain, a two-task flag, host name, and port number, though the precise argument list should be confirmed from the current package header before invocation.
• register_instance — A function returning BOOLEAN, and the object most commonly searched by administrators. Its documented purpose is to register database instance information into the FND_DATABASE_INSTANCE table. It accepts the parent database name together with instance-level attributes such as instance name, instance number, task, host name, port number, SID name, configuration, and description.
• assign_database — A function returning BOOLEAN that associates, or de-associates, a registered database with a target context, driven by a database name and an assignment indicator.

Because all three are PL/SQL functions rather than procedures, callers must capture the BOOLEAN return value, typically through a wrapper or a SELECT ... FROM dual construct, to determine success or failure.

Tables Accessed

The package writes directly into the FND database registry. register_database populates FND_DATABASE, the master list of known database definitions. register_instance populates FND_DATABASE_INSTANCE, the child table describing individual instances of a registered database, including SID and connectivity details used by the concurrent manager when dispatching work across nodes. assign_database updates the assignment state of a database record. These tables underpin the Distributed Concurrent Processing and load-balancing features of the EBS application tier.

Usage Notes

FND_CONC_DATABASE is an internal registration API rather than an end-user interface. It is invoked during installation, cloning, and node-addition operations when AutoConfig or the Rapid Install / adcfgdb utilities must enroll a new database or instance. In practice, DBAs rarely call it directly; instead they rely on the documented configuration tools that wrap these functions. Direct invocation is occasionally seen in custom migration scripts that repair or rebuild FND_DATABASE and FND_DATABASE_INSTANCE rows after a database rename or a host change, in which case the calls must be wrapped to handle the BOOLEAN return and executed with the APPS schema as the connecting user. The ETRM metadata records no inbound callers from other packages, confirming its role as a leaf-level registration service. Committing after successful calls is the caller's responsibility.