When a new release is available, you will receive a notification from the Oracle Cloud Infrastructure Notifications service. To upgrade your instance before the specified deadline, complete the following steps. If you don't upgrade the instance by the deadline, the instance is upgraded automatically.

The platform version is the version of Hyperledger Fabric that Oracle Blockchain Platform is based on. When a new version is available, you will receive a notification from the Oracle Cloud Infrastructure Notifications service. For example, you will receive a notification that you can upgrade an instance that is based on Hyperledger Fabric v1.4.7 to Hyperledger Fabric v2.2.4. To learn more about platform versions, see What's a Platform Version?.

• The platform upgrade function to Hyperledger Fabric v2.2.4 is available only for founder instances with no participant instances in the same network. If your Oracle Blockchain Platform network contains multiple instances (founder and participants), Oracle will assist you with the upgrade. For more information, see Request a Platform Upgrade for Multiple Instances.
• Upgrading to Hyperledger Fabric v2.2.4 means that you will use a new chaincode life cycle and a new model that separates chaincode packages from chaincode definitions. To learn more about the new features, see Deploy and Manage Chaincodes on Hyperledger Fabric v2.2.4. When you upgrade the platform version, you might need to make changes to your existing applications and REST API calls so that they work with the new version of Hyperledger Fabric. To learn more about the impact of a new version of Hyperledger Fabric on existing applications, see Updating Applications for Hyperledger Fabric v2.2.4.
• Because client SDK versions have to be upgraded to work with Hyperledger Fabric v2.2.4, for applications that use client SDKs typically you first upgrade and verify them in a test environment before upgrading your production environment.
• When you upgrade an instance from Hyperledger Fabric v1.4.7 to Hyperledger Fabric v2.2.4, the ordering service settings are not updated. In other words, an upgraded instance uses the existing ordering service settings of the Hyperledger Fabric v1.4.7 instance, not the default settings for a new Hyperledger Fabric v2.2.4 instance. For more information about the ordering service, see Manage Ordering Service.
• The typical downtime for a platform upgrade is 60 minutes for a single founder instance.
• Once the upgrade starts, all traffic to the instance is rejected until the upgrade completes. In other words, no administrative operations or transactions can be processed during the platform upgrade process.

When the upgrade is complete, the state of the Upgrade Blockchain Platform work request changes to Succeeded and the Platform Version displays the new version of Hyperledger Fabric. In the Oracle Blockchain Platform console, all of the previously instantiated Hyperledger Fabric v1.4.7 chaincodes are displayed in the Deployed Chaincodes list for each specific channel page under the Channels tab, with the Sequence, Package ID, Approved, and Committed settings all shown as N/A. Where the Chaincode tab for the Hyperledger Fabric v1.4.7 platform displayed the fields Chaincode ID, Versions, Chaincode Path, Installed on Peers, and Instantiated on Channels, the Chaincodes tab for the Hyperledger Fabric v2.2.4 platform displays the fields Package ID, Installed on Peers, and Deployed on Channels. Existing Hyperledger Fabric v1.4.7 chaincodes are not listed as installed on the Chaincodes tab. When chaincode packages are installed again, they will be listed on the Chaincodes tab. After the upgrade, you must use Hyperledger Fabric v2.2.4 life cycle operations to deploy new or upgrade existing chaincodes.

Scaling the OCPU Capacity of an Enterprise Instance

If you've selected an Enterprise edition when provisioning your instance, you can scale its OCPU capacity up or down. When you scale OCPU capacity, the platform shape changes to Custom in the Instance Details view. The total OCPU capacity represents the total number of OCPUs that are equally allocated among all the VMs in the Oracle Blockchain Platform cluster.

Scaling Components of Your Instance

You can scale components of your instance by selecting it in the Oracle Cloud Infrastructure console and clicking Scale.

You can see the availability domains or fault domains for the existing peers on the Scale Blockchain Platform window. Each Oracle Blockchain Platform instance is deployed across three availability domains or fault domains.

You can use the following REST API call to get more information about the logical OCPU consumption for each VM: Get Blockchain Platform Information.

The peers array in the BlockchainPlatformComponentDetails object shows information for each peer, including the host where the peer is located and the ocpuAllocationNumber, which indicates the number of OCPUs allocated to the peer.

The hostOcpuUtilizationInfo array shows the ocpuCapacityNumber and ocpuUtilizationNumber values for each VM (host). To determine the remaining OCPU capacity that can be allocated on a VM, subtract the ocpuUtilizationNumber value from the ocpuCapacityNumber value.

When you add a peer to a particular availability domain or fault domain, if the specified OCPUs value is greater than the remaining OCPU capacity on the VM in that domain, then a new VM is allocated. Otherwise, the existing VM is used to host the new peer. For domains that already have multiple VMs, if at least one VM has enough OCPU capacity, the peer is hosted there. Otherwise, a new VM is allocated.

Monitor Status by Using the Console

1. In the Console, click the navigation menu icon () in the top left corner.
2. Under Developer Services, select Blockchain Platform.
3. Select the compartment that contains the Oracle Blockchain Platform instances that you want to monitor.

   A list of all the instances in the compartment is displayed.

4. Check the State column to determine the current status of your instance.
   • Creating: The instance is in the process of being created.
   • Active: The instance is running normally.
   • Updating: The instance is being updated.
   • Scaling: The instance is in the process of being scaled.
   • Inactive: The instance has been temporarily stopped or is stopping.
   • Failed: The instance isn't running due to an error.
   • Deleting: The instance is in the process of being deleted.
5. Click the name of your instance to access the work request details.
   Use the Work Requests table to track the history and status of activities (work requests) related to the instance. For example, create, start, stop, scale, and so on. The status of a work request is shown in the State column of the Work Requests table.

   • Accepted: The request is in the queue to be processed.
   • InProgress: The work request started but isn't complete.
   • Succeeded: A work request record exists for this request and an associated WORK_COMPLETED record is in the state SUCCEEDED.
   • Failed: A work request record exists for this request and an associated WORK_COMPLETED record is in the state FAILED.
   • Canceling: The work request is in the process of being canceled.
   • Canceled: The work request was canceled.

Monitor Status by Using the Command Line

You can use the work-request list and work-request get commands to get the current status of operations on Oracle Blockchain Platform instances. To cancel an operation, use the work-request delete command. To check errors and access logs, use the work-request-error list and work-request-log list commands.

For more information on how to use the commands, see the Oracle Cloud Infrastructure CLI Command Reference:

• work-request list
• work-request get
• work-request delete
• work-request-error list
• work-request-log list

Monitor Status by Using the REST API

You can use the GetWorkRequest API call to get the current status of operations on Oracle Blockchain Platform instances. To cancel an operation, use the DeleteWorkRequest API call. To check errors and access logs, use the ListWorkRequestErrors and ListWorkRequestLogs API calls.

For more information on how to use the API calls, see the Oracle Cloud Infrastructure REST API Reference:

• GetWorkRequest
• DeleteWorkRequest
• ListWorkRequestErrors
• ListWorkRequestLogs

Required IAM Policy

To monitor resources, you must be given the required type of access in a policy written by an administrator, whether you're using the Cloud console or the REST API with an SDK, CLI, or other tool. The policy must give you access to the monitoring services as well as the resources being monitored. If you try to perform an action and get a message that you don’t have permission or are unauthorized, confirm with your administrator the type of access you've been granted and which compartment you should work in. For more information on user authorizations for monitoring, see the Authentication and Authorization section for the related service: Monitoring or Notifications.

Available Metrics: oci_blockchainplatform

The metrics listed in the following table are automatically available for any Oracle Blockchain Platform that you create. You don't need to enable monitoring on the resource to get these metrics.

View Default Metric Charts in the Console

Default metric charts use predefined service queries. You can select resources of interest and update the interval, statistic, and time range.

To view default metric charts for all Blockchain Platforms in a compartment:

1. Open the navigation menu. Under Observability & Management, go to Monitoring and click Service Metrics.
2. For Compartment, select the compartment that contains the instances that you're interested in.
3. For Metric Namespace, select oci_blockchainplatform. The Service Metrics page dynamically updates the page to show charts for each metric that is emitted by the selected metric namespace.

Optionally, you can specify other dimensions to filter your displayed metrics. For more information, see To filter results and To select different resources in the Oracle Cloud Infrastructure documentation.

For more information about monitoring and notifications in Oracle Cloud Infrastructure, see Monitoring Overview and Notifications Overview in the Oracle Cloud Infrastructure documentation.

To view default metric charts for a specific Blockchain Platform instance:

1. Open the navigation menu. Under Developer Services, select Blockchain Platform.
2. Select the compartment that contains the instance that you're interested in, and click that instance name from the list of instances.
3. On the Instance page, under Resources, click Metrics. The default metrics for your instance will be displayed.

Create Metric Queries in the Console

To create a query for a customized view of your metrics:

1. Open the navigation menu. Under Observability & Management, go to Monitoring and click Metrics Explorer.

   The Metrics Explorer page displays an empty chart with fields to build a query.

2. Fill in the fields for a new query.

   For more information, see Building Metric Queries in the Oracle Cloud Infrastructure documentation.

View Metrics By Using the API

For information about using the API and signing requests, see REST APIs and Security Credentials in the Oracle Cloud Infrastructure documentation. For information about SDKs, see Software Development Kits and Command Line Interface.

Use the following APIs for monitoring:

• Monitoring API for metrics and alarms
• Notifications API for notifications (used with alarms)