3 Manage Services
When Oracle Analytics Cloud is up and running, you can monitor and manage the services you’ve created through Oracle Cloud Infrastructure Console.
Topics:
Typical Tasks to Manage a Service
Here are the common tasks you will perform as Oracle Analytics Cloud - Classic administrator.
Task | Description | More Information |
---|---|---|
View and manage services |
Access all your services you created with Oracle Analytics Cloud - Classic from Oracle Cloud Infrastructure Console. |
|
Monitor services |
Check on the day-to-day operation of Oracle Analytics Cloud - Classic, monitor performance, and review important metrics and notifications. |
|
Delete a service |
Delete services you don't need anymore to free up resources. |
|
Start, stop and restart cloud services |
Stop services to temporarily prevent access. Start or restart services whenever you want. |
|
Back up a service |
Take regular backups in case you need to restore earlier content. |
|
Restore a service |
Restore your service from a backup. |
|
Patch a service |
Apply a patch or roll back a patch. |
|
Scale service resources |
Change the shape, CPU allocation, storage, and add nodes to meet new demands. |
View and Manage Services
You can view information about services and perform various administration tasks Oracle Analytics Cloud - Classic from Oracle Cloud Infrastructure Console.
- In Oracle Cloud Infrastructure Console, navigate to Analytics Classic.
- Click a service instance to view additional properties and perform various actions on that service.
- Click the Manage this instance icon or the page tabs to explore all the options available.
Monitor Services
You can use Oracle Analytics Cloud - Classic metrics to monitor the performance of your services.
Topics:
About Oracle Analytics Cloud - Classic Metrics
You’ll find status and performance information for Oracle Analytics Cloud - Classic in Oracle Cloud Infrastructure Console.
Instance Metrics
On the Instances tab for Oracle Analytics Cloud - Classic, you’ll find a summary of metrics for the service instances, including the number of CPUs, memory used, storage used, and more.
You can also see metrics on the Services tab per service instance: subscription billing type, product update version, service instance creation date, number of CPUs, and memory and storage sizes.
If you click the service instance name, you can see detailed service instance metrics, public IP addresses, resources, load balancer details, associated services, and operation messages.
-
The Instance Overview pane displays a variety of component, storage, and resource details, including the infrastructure of the database, storage and backup services that supports this service instance are displayed. When you expand Associations, you can also see Database Cloud Service details and status.
-
The Administration pane displays the quantity of storage cloud volumes and backup volumes used, backup and restore history, and available patches.
Activity Metrics
On the Activity tab, you can view recent lifecycle management activities performed for a service, during a specified time range.Run a Health Check
Monitoring information is updated automatically. You can also run a health check to update the display of monitoring information at any time.
- In Oracle Cloud Infrastructure Console, navigate to Analytics Classic.
- On the Overview pane, click the Display monitoring information icon to update the information displayed.
- In the Resources section, click the View Healthcheck Details icon. Healthcheck details are displayed.
Start, Stop and Restart Services
You can start, stop and restart service from the Analytics Classic page in Oracle Cloud Infrastructure Console.
Back Up a Service
Back up Oracle Analytics Cloud - Classic regularly so you can restore your service if something goes wrong.
Schedule Regular Backups
You can schedule regular backups for your service. Service backups are saved to your cloud storage, and contain all the artifacts required to restore your service.
Back Up a Service On Demand
You can back up your service whenever you want. Service backups are saved to your cloud storage and contain all the artifacts required to restore your service.
Disable and Enable Backups
If no one is using your service, you can temporarily disable backups using the Oracle
Analytics Cloud - Classic CLI command update-backup-config
. When you disable backups, you can’t take an on-demand backup and scheduled backups are canceled. All your existing backups are preserved in case you need them.
update-backup-config
in PaaS Service Manager Command Line Interface
Reference.
Restore a Service
You can restore your service from a backup. The service backup must be taken from the same Oracle Analytics Cloud - Classic version as the service you want to restore.
Note:
If you scaled-out your service and a node fails during the restore process, then you must scale-in the failed node, complete the restoration, and then scale-out the node again.Patch and Roll Back
A text notification is displayed on the Oracle Analytics Cloud - Classic dashboard when patches become available. You can view and apply patches for individual services. You can also see what patches have been applied, and roll back to an earlier patch.
Topics:
Apply the Latest Patch to BI Services
Check the FAQs before applying the latest patch.
Frequently Asked Questions About Patching
Check these FAQs to see whether or not you need apply this patch.
-
Several Patches Are Available. Which Patch Do I Apply?
Oracle recommends that you apply the most recent patch as soon as it becomes available. If you don't, your service might be unsupported for future patching and upgrade.
Patches are cumulative, that is, the latest patch includes all the updates included in earlier patches.
-
My Service Uses Oracle WebLogic Embedded LDAP Server. After Patching My Service Can I Use Oracle Identity Cloud Service?
No. If your service uses Oracle WebLogic Embedded LDAP Server for identity management, your service continues to use the same LDAP server after you apply the latest patch.
You can use Oracle Identity Cloud Service if you subscribe to Oracle Analytics Cloud - Classic through Oracle Universal Credits. Oracle Identity Cloud Service Foundation is automatically provided with your subscription. If you do subscribe through Oracle Universal Credits and have existing services that use Oracle WebLogic Embedded LDAP Server, Oracle recommends that you create a brand new service enabled with Oracle Identity Cloud Service and migrate your users and content to the new service. See Migrate BI Content and Users.
-
Can I Use the Pixel-Perfect Reporting (Oracle BI Publisher) Feature After Patching My Service?
In most cases, Yes. If you have a traditional metered subscription, applying this patch doesn’t expose features for pixel-perfect reporting in your existing service. In this case, you must create a new service with the option Enterprise Data Models, and migrate any information that you want to keep from your existing service. See Create a Service and Migrate BI Content and Users.
Before You Patch a BI Service
Before you patch a BI service with the latest update, you must complete some prerequisite steps.
Apply the Latest Patch to a BI Service
Patches for your service are rolled out periodically. Oracle recommends that you apply the most recent patches promptly. Delaying patches could cause your service to be unsupported for future patching and upgrade. Before you patch, you can run a precheck to identify potential problems, such as insufficient disk space storage.
Most patching operations are rolling operations, so your service continues to function with very little interruption during the patch process. The patching operation shuts down one node at a time and applies the patch. After a node is patched, it’s automatically restarted. The load balancer automatically detects that a node is down and doesn’t send requests to that node. The other nodes process requests without interruption. The patching operation continues patching nodes until all nodes are patched. For example, if you have a two-node cluster, one node keeps running while the other is being patched.
After You Patch a BI Service
After patching a BI service with the latest updates you must restore the settings and snapshots that you saved earlier.
- Sign in to your service, and click Console.
- Activate scheduled deliveries (if any).
- In Console, click Monitor Deliveries.
- To activate a delivery, click the Actions menu and select Enable Delivery .
Apply the Latest Patch to Essbase Services
Oracle recommends that you apply the most recent patch as soon as it becomes available. If you don't, your service might be unsupported for future patching and upgrade. Patches are cumulative, that is, the latest patch includes all the updates included in earlier patches.
Patch Essbase Services from 17.3.3 and Earlier
If your Essbase service is patched to 17.3.3 (or earlier) and you want to upgrade to the latest version, you can’t apply the patch through Oracle Cloud Infrastructure Console. Instead, you must create a new (latest) Essbase service, and migrate data from your existing service using scripts.
Note:
If you’re enabling Oracle Identity Cloud Service (IDCS), then in your existing Essbase service, open the Security tab and ensure that all user data fields (including ID, name. email, and role) contain values and aren’t empty. IDCS requires that user fields aren’t empty. Enter values in all fields as necessary.Roll Back a Patch to an Earlier Version
If you experience issues after applying a patch, you can roll back to the previous version.
For rollback to work certain aspects of your environment must be the same before and after the rollback.
-
The database password before and after the rollback must be exactly the same. If you changed the database password between the patches, you must change it back before rolling back.
-
The topology of your service before and after the rollback must be exactly the same. Rollback fails if you scaled your environment in or out between the patches.
Scale Services
If a service you deployed with Oracle Analytics Cloud - Classic is performing poorly or is running out of storage, you can scale the compute shape of the node or the storage attached to the node. You can also add one or more nodes to a cluster; that is, scale out your service in response to changes in the load.
Scale Compute Shape
If a cloud service is performing poorly or is running out of storage, you can scale the compute shape allocated to the service. To save costs, or if your workload is reduced, you might scale down. For example, changing the compute shape from OC5 to OC4 reduces by 50%, the capacity of the node and the amount of RAM allocated.
All-purpose compute shapes include:
-
OC4: 2 OCPUs with 15 GB RAM
-
OC5: 4 OCPUs with 30 GB RAM
-
OC6: 8 OCPUs with 60 GB RAM
-
OC7: 16 OCPUs with 120 GB RAM
-
OC8: 24 OCPUs with 180 GB RAM
-
OC9: 32 OCPUs with 240 GB RAM
If you want to scale up to one of the higher-memory options, the memory–intensive compute shapes include:
-
OC1M: 1 OCPU with 15 GB RAM
-
OC2M: 2 OCPUs with 30 GB RAM
-
OC3M: 4 OCPUs with 60 GB RAM
-
OC4M: 8 OCPUs with 120 GB RAM
-
OC5M: 16 OCPUs with 240 GB RAM
Expect a temporary unavailability of your service, as it scales up or down. You can check scaling progress by clicking next to your service name and then select View Activity.
Scale Storage
If a cloud service is performing poorly or if relevant disks are running out of space, you can scale the allocated storage. Oracle recommends at least 230 GB, that is, 130 GB latency storage, and 100 GB data storage.
Expect a temporary unavailability of your service as your service scales up or down. You can check scaling progress by clicking next to your service name and then selecting View Activity.
Scale a Cluster
When you scale out your service, Oracle Analytics Cloud - Classic adds one or more nodes (analytics servers) to the existing cluster. Each service can have as many as 10 nodes. All new nodes have the same compute shape and amount of storage that you allocated when the service was created. For example, if your service started with an OC3 shape (1 CPU and 7.5 GB RAM) and you decide to scale out, the additional nodes have the same OC3 shape.
Note:
To scale a cluster, you must subscribe to Oracle Analytics Cloud - Classic through Oracle Universal Credits and be patched to 17.4.5 or later.If necessary, you can change the compute shape and add more storage.
Expect your service to be temporarily unavailable while your service scales out or in. You can check scaling progress by clicking next to your service name and then selecting View Activity.