Request for Loading Demonstration Data
The customer or system integrator can request to load demonstration (demo) data into an environment. The use of demo data is strictly for product feature references and for training purposes ONLY. For initial product configuration, the customer or system integrator MUST use configuration accelerators. Please refer to Oracle Energy and Water Cloud Services - Implementation Accelerators (Doc ID 2806547.1) on My Oracle Support.
Request Specifications
The customer can request to have demo data loaded into their prod or non-prod environments
The demo data is maintained by Oracle Utilities product teams for every major release and is upgraded once as part of each major release's monthly maintenance pack.
Customer Obligations
The customer must understand and follow the Post Demo Data Load Steps (see below) to complete the demo data load process. These steps would be communicated on the requested Service Request ticket as well as by Oracle after completion of the activity.
The customer needs to specify date and time including time zone (within Service Level Objectives) for the start of this activity.
The customer must submit one service request per Demo Data Load.
The customer must ensure the target schema is set to production in target environment. Select Admin, then Conversion Support, then Switch Schema. The current schema should show as Production.
The scheduling of the Demo Data Load activity for multiple requests made during same day or same week will be scheduled in next available slots in a sequential manner and will not be executed on the same day.
Note: Once the activity has been performed, it will not be possible to revert the environment to a prior state before the activity.
If for any reason, the customer wish to postpone the clone to a different date OR wish to change the environment (source or target), it will require the following:
Customer will need to create a new service request ticket. The ticket will be counted as a fresh request by Oracle and will follow the SLA for the new request.
Customer will intimate this change on the existing Service request ticket providing reference of the new service request created and will then close the ticket
Oracle will acknowledge the new service request, perform pre-checks listed in the Pre-requisites for Requesting Environment Clonessection above and availability of the requested schedule.
Oracle will update the Service request Ticket and confirm schedule.
Oracle Cloud Operations Team Obligations
Acknowledge and schedule the execution of service request.
Execute steps to complete the service request
Verify if the table row counts match between source and target.
Communicate the status upon completion and provide post demo data load steps for the customer and/or the system integrator to perform.
Service Level Objective
Advanced Notice: 7 business days
Acknowledge/ Schedule: 2 business days
Execution Time: It depends on the size of the demo database. Please refer to the table in the Business Impact section below.
Outage Expected: Yes
Business Impact
The target environment will undergo an outage for the duration of data pump import process depending on the size of the demo database.
Demo Data Dump Size
Duration of Refresh
Up to 100 GB
5-8 hours
Between 100 GB and 500 GB
8-12 hours
Note: The customer will receive daily status updates on the service request for the duration of the activity.
Post Demo Data Load Steps
There are post demo data load steps that the customer must perform from the application user interface on the target environment before it can be released to end-users. Please refer to Oracle Utilities Cloud Services - Customer Instructions after a Clone Request (Doc ID 2832335.1) for instructions.