Siebel CRM Master Error Catalog (Part 10): Database Architecture, Schema Maintenance, Repository Upgrades & ADM Migrations (SBL-DBC-*, SBL-UPG-*, SBL-UDA-*)

Part 10: Database Architecture, Schema Maintenance & Upgrades

Comprehensive Scenario Analysis: Physical RDBMS vs Repository Mismatches, DDL Execution Exceptions, Repository Merges, ADM Migrations, and Database Upgrade Utilities.
Key Prefixes: SBL-DBC-*****, SBL-UPG-*****, SBL-UDA-*****

SBL-DBC-00105: Database Schema Mismatch / Column Definition Discrepancy SCHEMA MISMATCH

Scenario A: Repository Definition Differs from Physical RDBMS Column Type or Length

A custom field added to a Table object in Web Tools specifies `Length = 100`, but the underlying RDBMS table column was created as `VARCHAR2(50)` or lacks the column entirely.

Resolution: Run the Apply / DDL schema wizard in Web Tools / Siebel Tools, or manually execute the generated DDL script against the target RDBMS instance to align physical schema with repository metadata.

Scenario B: Unapplied Schema Changes Delivered in Web Tools Workspace

A developer delivered a schema workspace modifying table columns, but the physical database schema was not updated prior to launching Object Manager components.

Resolution: Inspect pending schema changes using ddldict or execute ddlctl utility from server command line: ddlctl -u <user> -p <pass> -c <dsn> -d <table_owner> -f schema.sql -a apply.

Scenario C: Table Space or Index Space Target Name Missing in Physical DB

Creating or altering a table fails because the Table Space or Index Space property configured in Siebel Tools does not exist in the target database instance.

Resolution: Verify database table space names in RDBMS. Update table properties in Web Tools or request DBA to create missing storage spaces (e.g., TS_DATA / TS_INDEX).

Scenario D: Null Constraint Mismatch Between Repository and Physical Database Schema

A field marked as Nullable = FALSE in Siebel repository allows `NULL` values in physical database definition, causing runtime integrity check failures.

Resolution: Regenerate physical database schema definitions or update mandatory column attributes in Siebel Tools and execute `Apply DDL` with drop/recreate options where safe.

SBL-UPG-00212: Repository Upgrade / Three-Way Merge Execution Error REPOSITORY MERGE

Scenario A: Unresolved Object Merge Conflicts During SRF / Repository Upgrade

During execution of srvrupgwiz (Siebel Upgrade Wizard), the three-way merge algorithm encounters non-mergeable attribute conflicts between Prior Customer, Prior Standard, and New Standard repositories.

Resolution: Launch Siebel Tools / Web Tools Merge Conflict Resolution interface. Manually review conflicting objects in Repository Merge Conflicts, select correct resolution attribute, and override status.

Scenario B: Incompatible Target Schema / Ancestor Version Definition

The repository upgrade utility fails because the specified Ancestor Repository version does not match the actual database patch baseline.

Resolution: Verify baseline version in S_APP_VER table. Ensure correct Upgrade Driver file (`dcupg.ucfg` / `mupg.ucfg`) corresponding to exact source and target release versions is supplied.

Scenario C: Orphaned Repository Objects Interrupting Merge Execution

Custom repository objects reference parent components that were deprecated or deleted in the target release version, halting automatic merge execution.

Resolution: Run repository integrity check prior to merge: siebdev /c config.cfg /u sadmin /p pass /d Server /verifyAllObjects. Delete or fix orphaned repository references.

Scenario D: Repository Merge Lock Timeout on Database Server

Massive concurrent insert operations into `S_REPOSITORY` and related metadata tables lock up database temp space, causing transaction timeouts during merge.

Resolution: Increase DB temporary tablespace and undo logs. Set database optimizer statistics specifically for upgrade execution prior to launching Upgrade Wizard.

SBL-UDA-00008: Application Deployment Manager (ADM) Deployment Failure ADM MIGRATION

Scenario A: ADM XML Data Package Validation Failure / Missing Dependent Objects

An ADM deployment task importing administrative data (e.g., LOVs, Responsibilities, State Models) fails because dependent target objects are missing in the target database environment.

Resolution: Check ADM deployment log files in siebsrvr/ADM. Sequence ADM project deployments so parent configuration data is migrated prior to child dependent records.

Scenario B: Session Timeout During ADM Deploy Business Service Execution

High-volume ADM XML data packages take longer to process than allowed by the Object Manager synchronous invocation HTTP/SOAP session limit.

Resolution: Increase `SessionTimeout` and HTTP transport timeout parameters, or split monolithic ADM deployment packages into smaller batch items using ADM CLI (`admcmd`).

Scenario C: Foreign Key Resolution Failure on Target Environment During Migration

An imported ADM record references user keys (such as `Position` or `Organization`) that exist in the source environment but do not match target environment records.

Resolution: Standardize enterprise seed data (Organizations, Divisions, Positions) across environments prior to triggering ADM migrations.

Scenario D: Inactive Target ADM Project / Data Type Map Profile

Attempting to deploy an ADM package fails because the target Data Type or Project object is marked `Inactive = TRUE` in target environment's ADM configuration views.

Resolution: Navigate to Administration - Application Deployment Manager -> Data Types. Ensure all required deployment data types are active and enabled.

SBL-DBC-00111: DDL Execution Exception During Apply / Schema Alteration DDL EXECUTION

Scenario A: Insufficient Privileges on Database System Account (`SIEBEL` / `DBA`)

Executing `Apply DDL` or database schema updates fails because the database connection account lacks `ALTER TABLE`, `CREATE INDEX`, or `GRANT` privileges.

Resolution: Grant required DDL execution privileges to the Siebel table owner account in RDBMS: GRANT ALTER ANY TABLE, CREATE ANY INDEX TO siebel;.

Scenario B: Table Locked by Active User Sessions During DDL Schema Alteration

Attempting to modify a physical table structure fails because active Siebel Object Manager threads or batch jobs hold exclusive locks on the target table.

Resolution: Place Siebel Enterprise in maintenance mode, stop Application Object Manager components, terminate active database sessions on the target table, and re-run DDL apply.

Scenario C: Database Storage Allocation Limit (Extent Limits / Space Exhaustion)

Creating or altering a table fails with database error (e.g., `ORA-01658: unable to create INITIAL extent`) due to storage quota limits on the target tablespace.

Resolution: Allocate additional datafiles or enable auto-extend on the target tablespace in RDBMS before re-running DDL execution scripts.

Scenario D: Dropping Table or Column with Active Foreign Key Constraints

DDL statement execution fails when attempting to alter or drop a column that is referenced by foreign key constraints on child tables.

Resolution: Generate DDL script to file (`schema.sql`), review foreign key dependencies, drop constraint references explicitly before column alteration, and recreate constraints.

SBL-UPG-00100: Database Upgrade Utility (`dbupgrade` / `srvrupgwiz`) Task Failure UPGRADE WIZARD

Scenario A: SQL Driver Executable Failure During Schema Migration Script Execution

The Upgrade Wizard halts execution because an underlying SQL script (e.g., `schema.sql` or `upgphys.sql`) encountered an unhandled RDBMS SQL exception.

Resolution: Open siebsrvr/log/upgphys/output/*.log. Locate the failing SQL statement, execute manual fix in RDBMS query tool, mark the step as complete in state file (`state.log`), and resume upgrade wizard.

Scenario B: Incomplete Upgrade Environment Setup (Missing Master Dictionary)

The upgrade engine fails to initialize because required dictionary export files (`schema.ddl` / `custrep.dat`) are missing from the `siebsrvr/DBOUTPUT` directory.

Resolution: Re-run the repository export step using repimexp.exe to generate fresh repository data files prior to launching `srvrupgwiz`.

Scenario C: Out-of-Order SQL Script Step Execution Due to Modified Driver Files

Manual edits to upgrade configuration driver files (`.ucfg`) introduce invalid script dependency ordering, causing prerequisite tables to be missing during script execution.

Resolution: Restore original driver files (`.ucfg`) from installer distribution package and restart upgrade process from the last valid checkpoint.

Scenario D: Transaction Log / Redo Log Exhaustion During Bulk Upgrade Table Alteration

Bulk table data migration SQL steps crash the upgrade thread due to database transaction log or UNDO space saturation during mass update queries.

Resolution: Request DBA to temporarily switch database transaction logging mode to bulk-logged or expand UNDO tablespace during upgrade execution.