The web blog www.atonepoint.com strives to be a comprehensive guide to SCCD, TADDM, SERVICE NOW and MAXIMO tools. This is a personal site maintained solely by me. I intend to update it regularly.For live updates please follow us on.

DB2 Vs Oracle Database for Maximo


DB2 Vs Oracle Database for Maximo
IBM supports the use of three (3) core database platforms with the EAM product suite. The EAM architecture uses a close variant of ANSI SQL through Java Database Connectivity (JDBC) to store and retrieve data in databases. This design provides flexibility in supporting multiple database platforms but limitations in leveraging database platform specific functionality such as server side stored procedures.

For this reason, all database platforms used with this technology are not created equal. A detailed understanding of a client’s existing platform knowledge, the projected load expected, and the best support model for this implementation must be considered in the selection of the database platform.
IBM DB2 is one of the most commonly selected platforms. Because IBM can provide a single vendor option for the software stack, it is common for clients to select IBM WebSphere as the application server, IBM DB2 as the database and IBM Maximo as the Asset Management software. This single provider approach often reduces the cost of the solution through bundling, improves the supportability of the software stack, and eliminates communication barriers between vendors.
Oracle Database Server is a powerful platform option with the IBM Maximo environment. Oracle is a leading producer of database software with high transaction rates and many capabilities for fault tolerance, mirroring and scalability.

Feature
Oracle
DB2
Concurrency Model
Multi-version read consistency.
No.

Non-Escalating row-level locking
Locks escalate.
Clustered configurations
Transparent scalability with Real Application Clusters.
Rigid data partitioning required with DB2.
Indexing capabilities
Wide variety of indexing schemes.
Only B-Tree and Dynamic Bitmap Indexes.
Additional data warehousing capabilities
Multi-table INSERT
Not supported.
Self-tuning capabilities
Automatic Performance Diagnosis
Automatic SQL Tuning
Self-tuning memory, free space, and I/O management
No equivalent or limited capabilities.
Security
Oracle handles its own security within the DBMS itself and has more options for locking down certain rows or columns within the database than DB2 does.
DB2 tends to rely more on the security of the underlying OS platform.




Note: Major factors to decide database selection is:
  • Cost
  • Performance
  • No of users
  • Transactions
  • Incoming interfaced data from External System
  • Scheduled Cron tasks and Escalations.
  • Support model from product vendor
  • Client’s existing platform knowledge   


Option 1: Less users, Customer concern about cost. We can recommend DB2.
Option 2: Less users, Performance matters and if customer not concern about cost. We can recommend Oracle.
Option 3: More users, Performance Matters and customer not concern about cost. Always we can recommend Oracle.

3 comments: