top of page
Writer's pictureShashi Kallae

Critical Factors To Take Into Account As a Siebel Administrator and Oracle DBA

When performing a dual role and after careful planning and designing, what would be the critical factors to consider as a Siebel Administrator and Oracle DBA?


I understand there are so many other tasks involved as a Siebel administrator during the planning and designing stage, but here are a few of the critical steps I have outlined off the top of my head. I took RHEL as an example Linux operating system.

Oracle DBA

  1. Oracle DBA must ensure enough resources are available to spin the new database(s) for Siebel.

  2. Enough resources mean Servers (Virtual/Physical stand-alone), CPUs, RAM, Disk Space, NAS drives/CIFS Shares, Samba Mounts, etc.

  3. As a DBA, work closely with the Siebel development team to ensure their applications efficiently use the database.

  4. As a DBA, work closely with the Siebel Administrator Team (In this scenario, it is the DBA himself).

  5. Careful planning on the users/schemas, grants/privileges, Indexes, Tablespace, firewall policies on the database ports, oracle database listener, RMAN backup, dataguard, TNS names.

  6. As an Oracle DBA, it becomes that person's responsibility to design the Oracle Database architecture and understand how that instance works as per the Siebel application.

  7. As an Oracle DBA,

    1. Install, upgrade, and apply any maintenance releases or Oracle DB patches.

    2. Design the databases = Identify the requirements + create logical design + physical database design.

    3. Manage users/schemas and security.

    4. Manage storage for the database and develop a backup strategy (cold or hot).

    5. Recover the databases in case of failures (RMAN/TAPE/Any other latest methods).

    6. Manage Oracle Database and servers startup and shutdown by automation.

    7. Manage database objects such as Siebel Tables, Siebel Indexes, Siebel Data, and Views.

    8. Evaluate and test new database patches, maintenance releases, and features.

    9. Periodic monitoring and tuning of Oracle databases.

    10. Report and Raise incidents to Oracle support regarding any critical database errors.


Siebel Administrator


  1. Thorough Understanding of Siebel architecture and framework capabilities, including understanding Gateway Server, Siebel Enterprise Server, and Siebel Application Servers.

  2. Design Siebel/OHS/Weblogic/BIP/OBIEE Servers for optimal performance, failover, and scalability. Suggest proper hardware and software load-balancing options for the web and Network teams.

  3. Design and install the Siebel Infrastructure on RHEL servers and distribute the Siebel components onto all the servers.

  4. Install any Missing Library Files on the RHEL boxes corresponding to the Siebel, OBIEE/BIP, IBM LDAP Client, etc.

  5. Gather requirements for Siebel File System and design the File System as per the requirements.

  6. Install Siebel CRM on Windows (Document Servers).

  7. Install OHS/webserver on Linux 64-bit platform and perform OHS/SSL configuration. Install SSL Certs using Oracle Wallet in OHS Webservers.

  8. Work with Security Teams to get the Trusted and User Certs.

  9. Perform Siebel IBM LDAP Configuration by installing the IBM LDAP Client and necessary library files at the root level.

  10. Install Siebel Tools/Siebel Developer Client on Developer machines and Dedicated Windows machines.

  11. Load balance the Siebel servers and configure the Siebel env for High Availability.

  12. Write shell scripts to monitor the Siebel comps, log levels, App servers, web servers, etc.

  13. Create custom Object Managers for each country and tune the Max Tasks, MinMT Servers, and MaxMTServers.

  14. Performed cfgmerge.

  15. Configure Siebel Components as needed to meet the business needs.

  16. Write SQLs during the Siebel upgrade process to ensure the data flow is happening correctly and smoothly.

  17. Monitor the SQLs during the upgrade process for any unexpected data issues.

  18. Worked with QA Teams, BSAs, and Developers after the upgrade to ensure no unexpected issues with the infrastructure, data, workflows, triggers, RCRs, etc.


Comments

Rated 0 out of 5 stars.
No ratings yet

Add a rating
bottom of page