1. Administering Oracle Blockchain Platform on Oracle Cloud Infrastructure (Gen 2)
  2. Manage the Life Cycle of an Instance
  3. Upgrade an Instance

Upgrade an Instance

When a new release is available, you can upgrade an instance by using the Oracle Cloud Infrastructure console or the REST APIs.

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.
  1. In the Oracle Cloud Infrastructure console, under Developer Services, select Blockchain Platform.
  2. Select the correct compartment, and click the instance that you want to upgrade.
    A message is displayed that indicates a new version is available.
  3. Click Upgrade Platform Instance, and then click Upgrade to confirm.

    Note:

    Oracle Blockchain Platform restarts as part of the upgrade process. The system remains available for most of the upgrade process, but is not available while it restarts, which can typically take up to ten minutes.
    The State Message changes to Upgrading and an entry of the Upgrade Blockchain Platform type is displayed in the Work Requests table.

Upgrade the Platform Version of an Instance

When a new platform version is available, you can upgrade an instance by using the Oracle Cloud Infrastructure console.

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?.

Upgrading from Hyperledger Fabric v2.2.4 to Hyperledger Fabric v2.5.3

If you want to upgrade from Hyperledger Fabric v2.2.4 to Hyperledger Fabric v2.5.3, Oracle will assist you with the upgrade.

Upgrading from Hyperledger Fabric v1.4.7 to Hyperledger Fabric v2.2.4

  • 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.

To upgrade the platform version of an instance, complete the following steps.

  1. Review the impact to existing client applications and REST API calls and plan any required updates. For more information, see Updating Applications for Hyperledger Fabric v2.2.4.
  2. In the Oracle Cloud Infrastructure console, under Developer Services, select Blockchain Platform.
  3. Select the correct compartment, and click the instance that you want to upgrade.
    A message is displayed that indicates a new platform version is available.
  4. Click Upgrade Platform Instance, and then click Upgrade to confirm.

    Note:

    Oracle Blockchain Platform will not be available during the upgrade process, which typically takes 60 minutes or less for a single instance.
    The State Message changes to Upgrading and an entry of the Upgrade Blockchain Platform type is displayed in the Work Requests table.
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.
After the instance is upgraded, complete the following steps:

Request a Platform Upgrade for Multiple Instances

If your Oracle Blockchain Platform network contains multiple instances (founder and participants), Oracle will assist you with the platform upgrade.

The upgrade from Hyperledger Fabric v1.4.7 to Hyperledger Fabric v2.2.4 must be coordinated across all instances in your network. The Oracle DevOps team uses internal tools and processes to complete the upgrade. The downtime for the platform upgrade process is a function of the number of instances, and is typically in the range of 4 to 10 hours.

The platform upgrade includes the following high-level steps:

  • You review the impact to existing chaincodes, client applications, and REST API calls and make any required updates. For more information, see Updating Applications for Hyperledger Fabric v2.2.4. Due to the potential impact to existing applications, typically you will schedule with the Oracle DevOps team to upgrade your test environment or stage environment first before upgrading your production environment.
  • You submit a service request to Oracle to upgrade a specified set of instances that belongs to one or more Oracle Blockchain Platform networks, and provide a contact to coordinate the upgrade. To request an upgrade, open a service request (SR) in My Oracle Support. To learn more about Service Requests, see the documentation that is available at My Oracle Support. Include the following information in the Service Request:
    • Oracle Cloud Infrastructure region
    • Tenancy name
    • Oracle Blockchain Platform instance names
  • The Oracle DevOps team coordinates the upgrade schedule with you.
    • All instances in an Oracle Blockchain Platform network must be upgraded in the same time period.
    • Once the upgrade starts, all traffic to the instances is rejected until the upgrade completes. In other words, no administrative operations or transactions can be processed during the platform upgrade process.
  • The Oracle DevOps team runs the platform upgrade process and then notifies the specified customer contact when the upgrade is complete.
  • After instances are upgraded, update your client application if needed and verify that your client application works on the upgraded instances. For more information, see Updating Applications for Hyperledger Fabric v2.2.4.