Siebel CRM 64-bit

Get ready for the planned transition to a 64-bit application architecture. Use the checklist to plan your adoption, then explore answers to common questions about compatibility, testing, and deployment.

Your 64-bit preparation checklist

01Start Now - Plan for 64-bit Adoption

Siebel CRM is moving to a 64-bit architecture, and monthly updates for Linux and Windows—which include security fixes, bug fixes and enhancements—will be available only in 64-bit.

Plan your adoption now so you are ready to keep receiving the Siebel CRM Release Updates after the move to 64-bit architecture. Backports containing critical bug fixes for older releases are limited under the Siebel CRM Error Correction Policy (PNEWS2743).

02Inventory your native dependencies

Identify customer-developed and third-party libraries, COM/DCOM integrations, Java Data Bean dependencies, Windows API calls, security adapters, communications and CTI drivers, database providers, and data quality connectors.

Create a list and record each component’s business purpose, owner, supplier, and source-code availability.

03Confirm a compatible version or rebuild path.

Engage the suppliers of your dependencies early to confirm 64-bit driver, adapter and library availability.

Identify the components you must replace or rebuild, including their dependent libraries.

04Review integrations and native code

Check in-process libraries for 64-bit compatibility. Assess separately hosted COM/DCOM applications according to their interfaces and deployment model.

Review Windows API declarations, pointer types, arguments and data structures where necessary.

05Prepare a representative test environment

Migrate affected components into an environment that reflects your target deployment.

Review database clients, ADO/ODBC providers, native drivers and connection settings for compatibility.

06Test complete business workflows

Validate authentication, including Gateway access where applicable, communications and CTI, external data reads and writes, data quality results, automation and error handling.

07Validate capacity and performance

Test representative data volumes, transaction mixes, concurrent sessions and peak loads. Since 64 bit applications require more memory, ensure your current infrastructure sizing is appropriate for the increased demands.

Measure memory consumption, throughput and response times to refine Object Manager sizing, infrastructure capacity and monitoring.

08Rehearse deployment and rollback

Include all affected extensions in your deployment and rollback plan. Rehearse the plan before production cutover.

09Confirm readiness before production cutover

Make successful testing and readiness of the Siebel platform and all critical external dependencies release criteria. Schedule Linux and Windows adoption before applying the 64-bit Update.

A stronger foundation for modern enterprise operations

Greater memory capacity for processes

A significant benefit of a 64-bit architecture is a substantially larger address space for each Siebel CRM application process.

Moving beyond the address-space constraints of 32-bit applications will give processes in Siebel CRM more room to handle memory-intensive operations.

Aligned to modern enterprise infrastructure

Enterprise technology increasingly centers on 64-bit operating systems, libraries and operational tools.

A 64-bit Siebel CRM runtime will align the application tier with that ecosystem and reduce reliance on legacy 32-bit compatibility packages.

Foundation for advanced database technologies

The 64-bit architecture provides the necessary foundation for leveraging advanced database technologies and features that are optimized for larger memory footprints and more complex data processing requirements.

This includes Oracle database 26ai technologies including AI Vector Search, hybrid search and graph capabilities.

Building on your Siebel investment

The move to 64-bit is a positive evolution of the core Siebel CRM architecture, providing greater memory capacity and aligned with modern infrastructure.

This enables the adoption of more innovation and advanced technologies while preserving the value of existing business configurations and processes.

    Overview and availability

    Open all Close all
  • 1. What is changing with Siebel CRM 64-bit?

    The planned transition introduces a 64-bit Siebel CRM application architecture on Linux and Windows. It modernizes the application tier while preserving business models, configuration assets and core user processes. The main benefits are greater memory capacity, alignment with modern enterprise infrastructure and reduced reliance on legacy 32-bit compatibility packages.

  • 2. When should Linux and Windows customers plan to adopt 64-bit?

    Moving forward, both 32-bit and 64-bit versions are planned to be available until we move to only 64-bit Release Updates.

    Once the 64-bit versions are available on Linux and Windows; the strategy will be to focus on the 64-bit version, and the 32-bit version will no longer be available on these platforms. Customers should begin dependency assessment and preparation now.

  • 3. Does the Linux and Windows transition schedule apply to AIX?

    No. Under the current plan, Siebel will continue to operate as a 32-bit application on AIX. Support for 64-bit Siebel on AIX remains on the roadmap, with no delivery timeline currently available.

    AIX customers can begin dependency assessment and testing preparation now to support future planning as platform guidance becomes available.

    Note for a mixed platform setup where the Siebel Application Interface runs a 64bit platform (Windows / Linux) and the Siebel Server are running on AIX, this architecture will not work with 64-bit Release Updates and later.

  • 4. Will 64-bit improve capacity and performance?

    A 64-bit architecture gives each application process a substantially larger address space. For Application Object Managers, this can support larger caches, more demanding transactions and increased session workloads. Depending on the deployment, an individual Object Manager process may be able to accommodate more users or transactions.

    Capacity and performance improvements are not guaranteed. Results depend on configuration, customizations, transaction patterns, integration activity and available infrastructure. Use representative workload testing to establish appropriate production sizing.

  • 5. How does 64-bit align with modern infrastructure and containers?

    A 64-bit runtime aligns the Siebel application tier with current operating systems, libraries and operational tools, reducing reliance on legacy 32-bit compatibility packages.

    This can simplify maintenance, patching, deployment image preparation and lifecycle automation. It also aligns more naturally with standard 64-bit container images, Kubernetes worker nodes and supporting services, and provides a more consistent foundation for security, monitoring and diagnostics.

    Configuration and compatibility

    Open all Close all
  • 6. Do scripts, workflows and Open UI customizations need to be migrated?

    Ordinary scripts, workflows, repository configuration, Open UI customizations and Java business services do not require migration solely because of the architecture change.

    Any external native dependencies they invoke still need assessment. Preparation should focus on customer-developed and third-party native components used by your deployment.

  • 7. Can a 64-bit Siebel process load a 32-bit native library?

    No. Native libraries loaded within a 64-bit Siebel process must be compatible 64-bit versions. Rebuild or replace affected libraries and their dependencies, and review arguments and data structures used by the calling code.

    For separately hosted applications, assess compatibility according to the interface and deployment model.

  • 8. Which COM, DCOM, and Java Data Bean integrations should we review?

    Assess COM Data Control, COM Data Server, Mobile Web Client Automation Server, and external objects invoked through COMCreateObject in eScript or CreateObject in Siebel VB, together with their dependent applications.

    Components loaded inside a 64-bit Siebel process require compatible 64-bit versions. Separately hosted COM/DCOM applications need assessment according to their interfaces and deployment model. Replace or rebuild affected components and regression-test the complete integration.

    Java Data Bean integrations should also be reviewed for compatibility with the 64-bit environment. For JDB connects to work, the latest client-side Java packages will be required, so customers using JDB should test and check if their middleware can be upgraded.

  • 9. What should we check in Windows API calls and automation?

    Review code that calls Windows APIs and update declarations, pointer types and data structures where necessary. For example, VBA calls to CreateProcess may require PtrSafe declarations and compatible parameter types.

    Validate WScript-based and other automation scenarios in the target environment.

  • 10. What should we do about custom libraries called by scripts?

    Rebuild or replace affected native libraries and their dependencies, and review arguments and structures. Incompatible libraries can cause custom calculations, validations or integrations to fail, so test the complete business workflows that use them.

  • 11. How should we prepare custom security adapters?

    Rebuild or replace affected custom security adapters and their dependencies with compatible versions. An incompatible adapter can prevent users or integration accounts from authenticating.

    Validate the complete authentication flow, including Gateway access where applicable.

  • 12. What should we do about communications and CTI drivers?

    Obtain compatible native drivers from your suppliers and test the communications workflows used by your business. Incompatible custom communications or CTI drivers can affect connected telephony and communications functions.

  • 13. How could VBCs and scripted database access be affected?

    Virtual Business Components (VBCs) and scripted database access may depend on ADO/ODBC providers or native database drivers. If a provider is incompatible, external information may fail to display or update.

    Replace affected providers or drivers, verify connection settings and test both read and write operations.

  • 14. Do custom data quality connectors need attention?

    Yes, where they depend on native connector libraries affected by the architecture change. Obtain compatible libraries and validate the resulting cleansing and matching behavior against your business requirements.

  • 15. What if we have no affected native dependencies?

    Customers without affected native dependencies will have no extension-specific remediation arising from the move to 64-bit. Complete the dependency assessment to establish whether this applies to your environment, and include representative workflow and capacity testing in your adoption plan.

  • 16. What should our dependency inventory include?

    Record each affected component’s business purpose, owner, supplier and source-code availability. Confirm a compatible supplier release or a rebuild path for every critical dependency.

    Engage suppliers early so that driver and adapter availability can inform a realistic migration schedule.

    Testing and production readiness

    Open all Close all
  • 17. What should we test before adopting 64-bit?

    Migrate affected components into a representative environment and validate complete business workflows, error handling and performance. Include authentication, communications, automation, external data access and any dependent data quality functions.

    Use representative data volumes, transaction mixes, concurrent sessions and peak-load conditions. Measure memory consumption, throughput and response times to refine Object Manager sizing, infrastructure capacity and monitoring.

  • 18. What should be ready before production cutover?

    Include affected components in a rehearsed deployment and rollback plan. Make successful testing and readiness of both the Siebel platform and critical external extensions part of your production cutover criteria.

    Equip teams with an inventory checklist, supported interface details, rebuild guidance, supplier compatibility information and business workflow test guidance. Plan Linux and Windows adoption within the transition period preceding the Siebel CRM 64-bit Release Updates.

  • 19. Verify upper memory limits with VM and Container deployment

    A 64-bit system architecture when used with an original 32-bit platform may require adjustments in terms of maxtasks/maxmtservers as they will need more memory and upper memory limits for VMs and Containerized deployments.

    For customers performing a full blown load runner test to simulate production load, using a 32-bit platform may require more memory.

    Database connectivity

    Open all Close all
  • 20. What does the transition mean for database clients and drivers?

    A 64-bit runtime enables the use of compatible 64-bit database clients and drivers, helping standardize connectivity and reduce architecture-specific exceptions.

    Review the clients, providers and native drivers used by your integrations, and verify connection settings and read/write operations in your target environment.

  • 21. Does adopting 64-bit automatically enable new Oracle AI Database capabilities?

    No. The platform modernization provides a path for the evolution of Siebel CRM database capabilities, including Oracle AI Database 26ai technologies such as AI Vector Search, hybrid search and graph capabilities.

    Please refer to the Siebel CRM Statement of Direction for more details.