My Oracle Support Banner

Performance Drop Between BRM Application (Sparc M7) And Database on ExaData (OracleCloud) (Doc ID 3031215.1)

Last updated on JUNE 26, 2024

Applies to:

Oracle Communications Billing and Revenue Management - Version 7.5.0.21.0 and later
Information in this document applies to any platform.

Goal

One user is experiencing a performance drop between Billing and Revenue Management (BRM) application (Sparc M7) and database on ExaData (OracleCloud). The response time was 18s before moving the database (DB) on ExaData, now it is 1 minute and 20 seconds.

For the difference in waiting for the application, M7 is having a shorter wait.
  SQL ID: 2w7n1jb8c29us Plan Hash: 900849427 - Queried from application connecting to M7. 
  SQL ID: 2w7n1jb8c29us Plan Hash: 3519978222 - Queried from application connecting to Oracle Call Interface (OCI).

In both the scenarios, same SQL ID got generated as shown below:
  select poid_DB, poid_ID0, poid_TYPE, poid_REV from event_t where event_t.item_obj_ID0 = :1 and event_t.poid_type like '/event/billing/payment%'
  "SQL*Net message from client" took 1.87 seconds in OCI and 0.23 in M7.
  "SQL*Net message from client" indicates the idle wait event experienced by the server while waiting for the client to tell it to do something.

Solution

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!


In this Document
Goal
Solution
References


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.