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:

• View and Manage Services

• Monitor Services

• Delete a Service

• Start, Stop and Restart Services

• Back Up a Service

• Restore a Service

• Patch and Roll Back

• Scale Services

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.	View and Manage Services
Monitor services	Check on the day-to-day operation of Oracle Analytics Cloud - Classic, monitor performance, and review important metrics and notifications.	Monitor Services
Delete a service	Delete services you don't need anymore to free up resources.	Delete a Service
Start, stop and restart cloud services	Stop services to temporarily prevent access. Start or restart services whenever you want.	Start, Stop and Restart Services
Back up a service	Take regular backups in case you need to restore earlier content.	Back Up a Service On Demand
Restore a service	Restore your service from a backup.	Restore a Service
Patch a service	Apply a patch or roll back a patch.	Patch and Roll Back
Scale service resources	Change the shape, CPU allocation, storage, and add nodes to meet new demands.	Scale Services

View and Manage Services

You can view information about services and perform various administration tasks Oracle Analytics Cloud - Classic from Oracle Cloud Infrastructure Console.

1. In Oracle Cloud Infrastructure Console, navigate to Analytics Classic.
2. Click a service instance to view additional properties and perform various actions on that service.
3. 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

• Run a Health Check

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.

1. In Oracle Cloud Infrastructure Console, navigate to Analytics Classic.
2. On the Overview pane, click the Display monitoring information icon to update the information displayed.
3. In the Resources section, click the View Healthcheck Details icon. Healthcheck details are displayed.

Delete a Service

You can delete services you created but don't need anymore.

1. In Oracle Cloud Infrastructure Console, navigate to Analytics Classic.
2. Click the Manage the service icon for the service you want to delete.
3. Select Delete, enter your database administration credentials, and then click Delete again to confirm.
   Select Force service deletion if you want to delete a service, regardless of whether there are processes running and any other warnings and messages you might see.
   The Force service deletion option doesn’t delete the schemas created for the service in Oracle Database Classic Cloud Service. This is the cloud database you specified when you created the service. You must manually delete these schemas.

Start, Stop and Restart Services

You can start, stop and restart service from the Analytics Classic page in Oracle Cloud Infrastructure Console.

1. In Oracle Cloud Infrastructure Console, navigate to Analytics Classic.
2. Select Manage the service for service you want to start, stop or restart.
3. Select the action you want to perform.

   • Select Start to start the service.

   • Select Stop to stop the service.

   • Select Restart to restart the service.

   Alternatively, click the icon for Start Service, Stop Service, or Restart Service on the Overview pane.

Back Up a Service

Back up Oracle Analytics Cloud - Classic regularly so you can restore your service if something goes wrong.

Topics:

• Schedule Regular Backups

• Back Up a Service On Demand

• Disable and Enable Backups

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.

1. In Oracle Cloud Infrastructure Console, navigate to Analytics Classic.
2. Click the name of the service you want to schedule backups for.
3. Click Administration.
   The Backup tab shows your current cloud storage and backup storage usage, available backups, and restore history.
4. Click Manage backups for this instance , and then click Configure Backups.
   You can’t change any backup options when a service backup is in progress.
5. Set up a suitable schedule for weekly backups. For Full Backup, set the day and time you want weekly backups to start.

   By default, the first backup starts 12 hours after you create the service (to the nearest five-minute interval). For example, if you create a service at 1:01 PM on a Monday, weekly backups are initiated at 1:00 AM on Tuesdays.

6. Set up a suitable schedule for daily backups. For Incremental Backup, set the time you want daily backups to start.

   Incremental backups are initiated every day except the day when full backups are initiated. For example, if you create a service at 1:01 PM on a Monday, by default, incremental backups are initiated at 1:00 AM every day except Tuesdays.

   For Oracle Analytics Cloud - Classic, the content included in full and incremental backups is exactly the same.

7. Optional: Change the length of time that backups are stored.
   1. Click Manage backups for this instance .
   2. Select Configure Backups.
   3. In the Set new retention period to field, specify the number of days you want to keep backups.

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.

1. In Oracle Cloud Infrastructure Console, navigate to Analytics Classic.
2. Click the name of the service you want to back up.
3. Click Administration.
   The Backup tab shows your current cloud storage and backup storage usage, available backups, and restore history.
4. Click Manage backups for this instance , and then click Backup Now.
   When completed successfully, details about your on-demand backup are displayed.
5. Optional: Change the length of time that backups are stored.
   1. Click Manage backups for this instance .
   2. Select Configure Backups.
   3. In the Set new retention period to field, specify the number of days you want to keep backups.

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.

1. Run the CLI command psm analytics update-backup-config.
   For help with that command, run the command with the -h option.
2. To disable backups, set the backups parameter to DISABLE.
   For example: "backups":"DISABLE"
3. To enable backups, set the backups parameter to ENABLE.
   For example: "backups":"ENABLE"

See analytics 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.

1. In Oracle Cloud Infrastructure Console, navigate to Analytics Classic.
2. Click the name of the service you want to restore.
3. Click Administration.
   You can see the quantity of cloud storage and backup used, as well as monitor available backups and restore history
4. Click the Manage this service icon for the backup you want to restore, and click Restore.
5. Enter some notes to remind yourself why you’re restoring the service, and click Restore.
   When the restore process completes, you see the details of the last successful restore process in the Restore History section.

If your service uses the WebLogic embedded LDAP server and you recently changed the administrator password, your backups might not contain the latest password. If this is the case when you restore your service, the administrator password reverts to the password in the backup.

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

• Apply the Latest Patch to Essbase Services

• Roll Back a Patch to an Earlier Version

Apply the Latest Patch to BI Services

Check the FAQs before applying the latest patch.

Topics:

• Frequently Asked Questions About Patching

• Before You Patch a BI Service

• Apply the Latest Patch to a BI Service

• After You Patch a BI Service

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.

1. Always take a snapshot of your service before you apply a patch.
   1. Sign in to Oracle Analytics Cloud, and navigate to Console.
   2. Click Snapshots.
   3. Click Create Snapshot.
   4. Enter a short description, for example: Snapshot before applying January 2022 updates.
2. Sign in to your Oracle Cloud account.
3. Verify that you have enough resources before you apply the patch.

   Oracle recommends 230 GB, that is, 130 GB latency, and 100 GB data.

   If required, scale up the compute shape or add more storage.

4. In Oracle Cloud Infrastructure Classic Console, back up the database associated with your service.
   1. Navigate to the Database Classic page and navigate to the database cloud service.
      If you need to confirm the exact database service, open the Oracle Analytics Cloud - Classic dashboard and navigate to your service where its database information is displayed.
   2. Back up the database. Click the Administration tile, then Back up Now.
5. Restart your service before you patch.
   If you made any changes or customizations on the compute node associated with your service you must restart your service before you patch.
6. Sign in to your service to verify that your service up and running, and ready to be patched.

Now you’re ready to patch your BI service.

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.

1. Complete the prerequisite before you patch steps.
2. In Oracle Cloud Infrastructure Console, navigate to Analytics Classic.
3. Click the name of the service you want to patch
4. Click Administration.
   On the Patching tab, you can view available patches, run a patch, and view patch installation and rollback history.
   Patches are cumulative, that is, the latest patch includes all the updates included in previous patches.
5. To check a patch before running it, click the Manage this service icon for the patch, and click Precheck.
   Upon completion, click Precheck summary link to view ramifications or possible conflicts due to running the patch.
6. If required, correct the database administrator (DBA) credentials for the database.
   If you changed the DBA credentials after setting up the service or after the last patch, the precheck fails with a message telling you that the stored credentials are incorrect.
   1. Connect to the compute node for your service using the ssh utility:
      $ ssh -i private-key-file-location opc@node-ip-address
   2. Change to the oracle user.
      sudo su oracle
   3. Run the script /bi/app/public/bin/store_dba_credentials.
      When prompted, enter the database administrator user name 'SYS as SYSDBA' and then enter the password for the SYS user. For example:
      store_dba_credentials 'SYS as SYSDBA' 'mydbadminpassword'
   4. Exit the compute node.
      It’s important that you log out from your ssh session.
7. To apply a patch, click the Manage this service icon for the patch you want to apply, and click Patch.
   Upon successful completion, a notification is displayed. The completed patch is listed in the Patch and Rollback History section.
8. If the patch succeeds, complete the postpatch steps.
9. If the patch fails, your service remains at the previous version.

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.

1. Sign in to your service, and click Console.
2. Activate scheduled deliveries (if any).
   1. In Console, click Monitor Deliveries.
   2. 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.

1. Export Essbase applications and users from your service (17.3.3 or earlier) and save them locally.
   1. Connect to the service using Secure Shell (SSH) client software.
   2. Check the required migration script exists at this location:
      /u01/app/oracle/tools/acss/BI/esscs_tools/lcm/esscs_lcm.py

      Note:

      If the scripts aren’t available, you must create a new Essbase service and copy the following scripts from the new service to this location:

      • /u01/app/oracle/tools/acss/BI/esscs_tools/lcm/esscs_lcm.py

      • /u01/app/oracle/tools/acss/BI /esscs_tools/lcm/idcs_users.py

      • /u01/app/oracle/tools/acss/BI /esscs_tools/lcm/ldap_users.py

      • /u01/app/oracle/tools/acss/BI /esscs_tools/lcm/user_group.py

      • /u01/app/oracle/tools/acss/BI /esscs_tools/public/essbase_export.sh

      • /u01/app/oracle/tools/acss/BI /esscs_tools/public/essbase_import.sh

      Stop your existing service before you create a new one. Copy the scripts, stop the new service, and then restart the existing service to perform the export.

   3. Export your content to a file:

      1. Change to the oracle user.

      2. Go to the export scripts location: cd /bi/app/public/bin

      3. Run the export script:

         essbase_export.sh filename

         Where:

         filename   Full path to the tar archive file that contains all your Essbase applications, CSV files of users and groups, and files of settings.

2. Stop your existing Essbase service.
   Oracle recommends stopping the existing Essbase service so you don't incur multiple CPU costs when you create a new service in the next step. A stopped service still requires disk space so you need a quota for additional disk space for the new service.

   Caution:

   Oracle doesn't recommend that you delete your Essbase service until you’ve migrated your data to the new service. When you delete a service, all your data is deleted and it isn't recoverable. If you decide to delete the service because you don’t have quota for additional disk space or for some other reason, you risk losing all your data.
3. Create a new Essbase service.
4. Import content from the exported file:
   1. Connect to the new service using SSH client software.
   2. Copy the exported tar file to the new service.
   3. Change the user to oracle.
   4. Go to the import script location: cd /bi/app/public/bin
   5. Run the import script:

      essbase_import.sh filename

      Where:

      filename   Full path to the previously copied tar archive file that contains all your Essbase applications, CSV files of users and groups, and files of settings.

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.

1. In Oracle Cloud Infrastructure Console, navigate to Analytics Classic.
2. Click the name of the service you want to roll back.
3. Click Administration.
   On the Patching tab, expand the Patch and Rollback History accordion.
4. To roll back a patch, click the Manage this service icon for the patch, click Rollback and then confirm that you want to start the rollback.
   A message notifies you when the rollback has completed.

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.

Topics:

• Scale Compute Shape

• Scale Storage

• Scale a Cluster

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

For more information about these compute shapes and considerations for selecting shapes, see About Machine Images and Shapes in Using Oracle Cloud Infrastructure Compute Classic.

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.

1. In Oracle Cloud Infrastructure Console, navigate to Analytics Classic.
2. Click the name of the service you want to scale.
3. Expand the Resources section, and click Manage this node for the node you want to scale.
4. Click Scale Up/Down.
5. Select a new compute shape to adjust the allocated resources.
6. Click Yes, Scale Up/Down VM.
7. Restart your service if you see this message in the activity log.
   Access OAC via http://ip-address/va gives following error. Service is not accessible.
   .

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.

1. In Oracle Cloud Infrastructure Console, navigate to Analytics Classic.
2. Click the name of the service you want to scale.
3. Expand the Resources section, and click Manage this node for the node you want to scale.
4. Click Add Storage.
5. Select the quantity of storage space to add to the Data and Latency disks, and click Yes, Add Storage. You can see the storage space reflected as part of the total storage value shown in your displayed resources.
   Data disks store configuration and log settings. Latency disks store Essbase applications data.

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.

1. In Oracle Cloud Infrastructure Console, navigate to Analytics Classic.
2. Click the name of the service you want to scale.
3. To scale out a service:
   1. Click next to your service name, and select Scale Out.
   2. Select the number of nodes (analytics servers) you want to add, and click Scale Out.
      If you previously requested and reserved IP addresses, select an IP reservation from the Select IP Reservation list.
   New nodes are listed in the Resources pane. You can stop additional nodes if you don't need the extra OCPU right away.
4. To scale in a service:
   1. Click next to the node you want to remove, and select Remove Node.
   2. Confirm how you want to scale in:

      • To scale in gracefully, click Remove Node.

      • To forcibly scale in, select Force Remove and click Remove Node.

        If you forcibly scale in, the service removes the node even if the node is unresponsive.