Results for “local_name”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

CZ_SERVERS is a Configurator (CZ) module table in the Oracle E-Business Suite, owned by the CZ schema. Its documented purpose is to identify the database servers used by the Configurator for model import and publication operations. In a distributed Configurator deployment, model definitions and their associated runtime data may reside on more than one database instance; CZ_SERVERS provides the registry through which those instances are named, located, and reached. Each row describes a single server, including its host, listener port, instance name, database version, and the database link names used to connect to it.

From a Data Vault modeling perspective, the mined relationship structure suggests a hub-leaning classification: CZ_SERVERS carries a stable surrogate primary key (SERVER_LOCAL_ID) and a business key (LOCAL_NAME), and is referenced by several downstream tables rather than being a transaction or attribute-history table. It should therefore be treated as a reference or master entity in any analytical model built over Configurator metadata.

Key Information Stored

The table contains fifteen documented columns. The most significant are summarized below.

• SERVER_LOCAL_ID — the surrogate primary key, enforced by CZ_SERVERS_PK. It is the value propagated to all child tables as the server reference.
• LOCAL_NAME — the business-key candidate, enforced by the unique index CZ_SERVERS_U1. This is the human-readable server identifier used in Configurator administration screens.
• HOSTNAME — the network host on which the target database instance resides.
• DB_LISTENER_PORT and INSTANCE_NAME — the connection coordinates for reaching the instance, used in conjunction with the host name.
• SERVER_DB_VERSION — the version of the remote database, relevant when import or publication crosses release boundaries.
• CZ_OWNER and FNDNAM — the Configurator schema owner and the Applications schema on the target server, respectively.
• CZ_LINK_NAME and FNDNAM_LINK_NAME — the database link names through which Configurator and Applications objects are accessed on the remote server.
• IMPORT_ENABLED, SOURCE_SERVER_FLAG, and CONVERTED_TARGET_FLAG — control flags indicating whether imports are permitted from the server, whether it acts as a source, and whether it is a converted target.
• GLOBAL_IDENTITY and NOTES — the global identifier for the server and free-form administrative commentary.

Common Use Cases and Queries

The principal operational use case is diagnosing model import and publication failures. When a publication fails, the server reference held on CZ_MODEL_PUBLICATIONS or CZ_PB_MODEL_EXPORTS is resolved back to CZ_SERVERS to verify connectivity details.

• Listing all servers available for import: SELECT SERVER_LOCAL_ID, LOCAL_NAME, HOSTNAME, INSTANCE_NAME FROM CZ.CZ_SERVERS WHERE IMPORT_ENABLED = 'Y'.
• Identifying source versus target servers: filter on SOURCE_SERVER_FLAG and CONVERTED_TARGET_FLAG and order by LOCAL_NAME.
• Resolving the server for a publication: join CZ_MODEL_PUBLICATIONS to CZ_SERVERS on CZ_MODEL_PUBLICATIONS.SERVER_ID = CZ_SERVERS.SERVER_LOCAL_ID.
• Auditing version drift across a multi-server deployment by grouping on SERVER_DB_VERSION.
• Reporting on database link configuration by selecting CZ_LINK_NAME and FNDNAM_LINK_NAME alongside the host and instance.

Related Objects

Three documented foreign keys reference CZ_SERVERS, and each represents a distinct Configurator process area.

• CZ_MODEL_PUBLICATIONS — references CZ_SERVERS through SERVER_ID; identifies the server on which a model publication was produced.
• CZ_PB_MODEL_EXPORTS — references CZ_SERVERS through SERVER_ID; records the server involved in a model export operation.
• CZ_XFR_PROJECT_BILLS — references CZ_SERVERS through SOURCE_SERVER; identifies the originating server for transferred project bills.

These relationships confirm CZ_SERVERS as a foundational reference table for Configurator import, publication, and transfer workflows, and any query traversing those three tables should join back to it via SERVER_LOCAL_ID.