• All Break Glass events will constitute scheduled downtime from the time the Break Glass event is initiated to when the actions performed are either rolled back or committed. Therefore:

• Customer administrators must ensure timely response to all Oracle requests and timely involvement of customer personnel in reviewing Break Glass actions for the period of an initiated Break Glass event.

• The System Availability SLO (Service Level Objective) does not apply during an initiated Break Glass event.

• Uncommitted Break Glass actions may not be applied in the secondary instance in the event of a DR (Disaster Recovery) event occurring during a Break Glass event.

• Only customer administrators are able to approve or reject Break Glass events and related actions (for the customer).

• All approvals and sensitive data regarding Break Glass events must be provided to Oracle via My Oracle Support.

• Customer administrators are responsible for:

• Ensuring that any non-Oracle personnel participating in Break Glass events or activity reviews are authorized to view customer data.

• All decisions made regarding the committing or rolling back of Break Glass actions.

• For all customer initiated Break Glass events, the Customer is responsible for verifying the correctness of any requested changes.