Requirements and Limitations

The following requirements and limitations currently apply for SCM. This information will be updated as needed for subsequent updates.

General Requirements

The following are some of the general requirements for SCM and for deploying Siebel CRM:

The minimum required version of Siebel CRM for migration to OCI is Siebel CRM 18.12 or later. The Siebel CRM on-premises environment must be running when you run the Siebel Lift utility.
All customers must have an OCI tenancy with Compute quota and manage privileges, Oracle Kubernetes Engine (OKE), and File System Storage (FSS).
Siebel CRM deployments on OCI use virtual machines running Oracle Enterprise Linux 7 or 8.
Customers must have an instance of any standards compliant Git distribution such as Oracle DevOps Service, GitHub, GitLab, Bitbucket, and so on installed and available to them. Only one instance is required for the main compartment on OCI in which you're working with SCM. For more information, see Git Repositories for Siebel CRM Deployment.
Hierarchically, the compartment you create in your OCI tenancy must support at least two child compartment levels. For more information, see Creating a Compartment.
SCM instructions currently are in U.S. English (ENU).
While "lift-and-shift" supports all languages that Siebel CRM supports, Greenfield deployments of Siebel CRM using SCM currently support U.S. English (ENU) only.

The following are some of the requirements for the Siebel Lift utility for this release of SCM. See also Downloading and Running the Siebel Lift Utility.

You download and install the Siebel Lift utility in your Siebel CRM on-premises environment.
The Siebel Lift utility is currently supported on Oracle Enterprise Linux and on Microsoft Windows.
The Siebel Lift utility currently supports execution in silent mode or in interactive mode (using a menu-driven command-line interface).
Depending on how you install the Siebel Lift utility, you might be required to install Python. Supported versions are: version 3.9.6 (on Windows), version 3.8.x (on Linux 7), or version 3.9.x (on Linux 8). See also Installing and Configuring Python (for Non-Container Mode).
The Siebel Lift utility requires software (such as 7-Zip) for extracting the utility from the ZIP file or TAR file you download and for installing the utility.
The operating system user running the Siebel Lift utility must have access to the files exported by the utility, or the upload process will fail.
The Siebel Lift utility currently supports U.S. English (ENU).

The following are Oracle Database and Oracle Database client requirements for SCM:

Siebel CRM deployments on OCI support Oracle Database 19c. The Siebel CRM database is migrated into OCI as an Autonomous Database for Transaction Processing in shared mode or as an Oracle Database Cloud Service in virtual machine mode.
The staging location for database artifacts you create must be mounted on the computer where Oracle Database is installed.
The table owner user must have Create Directory and database owner privileges, and must have read privilege for all dictionaries.
If you will be creating database artifacts to migrate the Siebel CRM database, then note that the Siebel Lift utility requires that Oracle Database client of a compatible version is installed where Siebel CRM is installed on premises.
The installed version of Oracle Database client must include the data pump utilities (expdp) in the bin directory.
On the Oracle Database client computer, the following requirements apply:
- The installation type for Oracle Database client must be Administrator.
- The tnsnames.ora file must have the necessary TNS settings applicable to the installed Oracle Database.
- On Linux computers, the TNS_ADMIN environment variable must be set to point to the directory where the SQL*Net configuration files (including sqlnet.ora and tnsnames.ora) are located.
- On Linux computers, the user who will run the Siebel Lift utility must be part of the Database Administrator (DBA) group.