Tablespace sizes were increased to support the Injection rate.
Scripts to create the DB are included in the FDA.
Table and index initrans were modified.
The C_CUSTOMER, C_CUSTOMERINVENTORY, M_LARGEORDER, M_WORKORDER, O_ORDERLINE,
O_ORDERS, S_COMPONENT, S_PURCHASEORDER and S_PURCHASEORDERLINE tables were
horizontally partitioned. M_PARTS, M_BOM, M_INVENTORY, and O_ITEM were hash clustered.
Automatic segment space management was used for all tablespaces.
System managed undo was used.
Table locks were disabled during the run using disable_lock.sql

Load Program Modifications:

The load program was not modified.
The driver was changed to fix a bug due to which throughput data was truncated
in Mfg.details and not captured Dealer.details. The change to the driver is
included in the FDA under Config/Primary_driver.

Benchmark Configuration Information

Isolation Requirement Info:

The following Beans were deployed in READ_COMMITTED mode as per the benchmark
requirement:
Mfg - AssemblyEnt, BomEnt, ComponentEnt, LargeOrderEnt, PartEnt
Orders - ItemEnt
Supplier - SupplierCompEnt, SupplierEnt
All other beans were deployed using pessimistic locking mode such that all
selects including finders are issued with a FOR UPDATE clause in select
statement:
Corp - CustomerEnt, CustomerInventoryEnt
Mfg - InventoryEnt, WorkOrderEnt
Orders - OrderEnt, OrderLineEnt
Supplier - POEnt, POLineEnt, SComponentEnt
Util - SequenceEnt
The ItemEnt bean was cached for 20 minute intervals by setting
the following in bea-orders.xml deployment descriptor:
concurrency-strategy to ReadOnly
read-timeout-seconds to 1200

Durability Requirement Info:

To ensure database durability, RAID 1 was used for the data files and redo logs.
The application server used RAID 1 to provide durability for
server logs and JMS persistence filestores.
The RAID controller on the database and the application server machines were
configured with Write-Back cache policy supported with battery backup unit on
the controller.

Storage Requirement Info:

A 75 min run at Injection Rate of 12000 increased storage by 35 GB.
Extrapolating for 24 hrs we need 672 GB. The system is configured with
5.6TB of durable storage.

The xerces implementation version 2.8.1 from xml.apache.org was used as it comes
packaged with Oracle Weblogic Server Standard Edition.
Requests were directed to the Appserver instances using DNS round robin, with
the database node acting as the DNS server.

General Notes

On the database, incremental checkpointing ensured that no buffer will remain
dirty (in the cache) for more than the allowed time.
The only errors in the driver error logs are the application errors generated by
this benchmark.

For questions about this result, please contact the submitter: HP
For other inquiries, please contact
webmaster@spec.org