Search Results check_process




Overview
Explore in AI Chat

Overview

CZ_PB_SYNC_UTIL is a PL/SQL utility package owned by the APPS schema in Oracle E-Business Suite, classified under the ETRM taxonomy as a UTIL object. It provides the shared infrastructure that supports the public-sector synchronization and migration machinery delivered as part of the Oracle Telecommunications/Public Sector vertical applications built on the CZ (Customer Care/CRM-style) schema family. Its header revision ($Header: czclouts.pls 120.2 2005/11/30) indicates it has been stable across releases and is carried forward into EBS 12.1.1 and 12.2.2 without structural change.

The package supplies low-level helper routines used by other synchronization packages: obtaining a run identifier for an execution cycle, resolving target-instance and database-link names, validating remote schemas, verifying target and migration servers, detecting an already-running publishing or public-sync process, and routing error messages into a central log table. It functions as a library rather than a business transaction package — it does not itself move data, but it supplies the plumbing that lets the resync and migration packages operate safely against remote instances.

Key Procedures and Functions

The package exposes eleven documented program units:

  • GET_RUN_ID — returns a NUMBER identifier used to correlate all activities and error records belonging to a single synchronization run.
  • LOG_PB_SYNC_ERRORS — accepts a message_list collection and a run ID, persisting the accumulated error records to the log table for later diagnosis.
  • RETRIEVE_LINK_NAME — resolves the database-link name associated with a given target server local ID from CZ_SERVERS.
  • GET_TARGET_INSTANCE_ID — returns the numeric target-instance identifier corresponding to a supplied instance name.
  • CHECK_DB_LINK — the function sought by the "check_db_link" search. It accepts a database-link name and returns a BOOLEAN indicating whether that link is reachable and usable, serving as the pre-flight connectivity test before any remote operation.
  • VALIDATE_SCHEMA — confirms that the schema on the target server is suitable for synchronization (correct objects and privileges present).
  • CHECK_PROCESS — returns the name of an active publishing or public-sync process, or NULL if none is running, preventing concurrent conflicting executions.
  • SET_DBMS_INFO — registers the module name in DBMS_APPLICATION_INFO so that the running session is identifiable in V$SESSION monitoring.
  • RESET_DBMS_INFO — clears the application-info registration at the end of processing.
  • VERIFY_TGT_SERVER — returns an OUT status and message describing whether the named target server is reachable and valid.
  • VERIFY_MIG_TGT_SERVER — the migration counterpart to the above, validating a target server for migration scenarios.

Tables Accessed

  • CZ_DB_LOGS — the destination for error records written by LOG_PB_SYNC_ERRORS; the message text, calling procedure and status code columns are typed against this table.
  • CZ_SERVERS — the registry of target/source servers, supplying link names and server-local identifiers used by RETRIEVE_LINK_NAME and VALIDATE_SCHEMA.
  • CZ_DB_SETTINGS — configuration parameters that govern synchronization behavior.
  • CZ_XFR_RUN_INFOS_S — the transfer run information table, consumed to obtain run identifiers and status tracking.
  • DBMS_APPLICATION_INFO / V$SESSION — used by SET_DBMS_INFO and CHECK_PROCESS to advertise and detect running sessions.
  • DUAL, PLITBLM — standard utility references used for trivial queries and integer table handling.

Usage Notes

CZ_PB_SYNC_UTIL is not exposed as a standalone concurrent program or form. It is invoked by the two packages that reference it, and by custom code implementing public-sector resynchronization or migration. CHECK_DB_LINK is commonly called at the start of any remote-sync routine to fail fast when a link is invalid, while SET_DBMS_INFO/RESET_DBMS_INFO bracket execution so the activity appears in V$SESSION for DBA monitoring. In 12.1.1 and 12.2.2 the package resides in the APPS schema and should be called with APPS-qualified synonyms in place.