Known Issues for Oracle Blockchain Platform Enterprise Edition for Besu

Learn about the issues you may encounter when using Oracle Blockchain Platform and how to work around them.

Administration Operation Failed After Deploying a Sample Application

After you deploy the wholesale CBDC or tokenized deposit sample application, you might see one or more of the following errors when you open the application URL.

  • Administration operation failed.
  • Service is temporarily unavailable. Please try again.
  • Besu ORDS token retrieval failed (HTTP 404).

Workaround: Complete the following steps to resolve this issue.

  1. Refresh your web browser.
  2. Select Initialize Token from the Quick Actions menu.
  3. If the error still occurs after initializing the token, delete the application and then deploy it again.

List Rules API Returns Incorrect updatedBy information

The List Rules API endpoint does not return the correct user information in the updatedBy field. Instead of the user who last updated the rule, the field is returned as null or as the placeholder value n/a in the response body.

Workaround: There is no workaround for this issue.

Assertion Failed Error When Using Blockchain App Builder

If you use Blockchain App Builder for Besu on Microsoft Windows 11, the following error message is displayed when uploading manifests to the smart contract registry:
Assertion failed: !(handle->flags & UV_HANDLE_CLOSING), file src\win\async.c, line 94

This is a known issue for Node.js running on Microsoft Windows 11.

Workaround: You can ignore this error message. The manifests will still be published to the smart contract registry.

Cannot Create Wallet for Other Organizations

When using IDCS as the identity provider, an error is returned when you attempt to create a wallet for a user in a different organization.

Workaround: Complete the following steps to create user wallets in the other organization directly in Blockchain Platform Manager. Then return to the application, load the wallet, and complete the account creation workflow.
  1. Identify the target organization, organization network, user ID, and wallet service instance that will be used for the new deposit token account.
  2. In Blockchain Platform Manager, open the Wallet page and the select the Users tab.
  3. Check whether the target user already exists for the target organization.
    • If the user exists, confirm that the organization and user ID are correct and that the user status is Active.
    • If the user does not exist, select Register User and enter the required details.
  4. Select Register User, then confirm that the new user is displayed in the Users list with an Active status.
  5. Select the Wallets tab, and then select Create Wallet.
  6. In the Create Wallet window, enter the details for the selected user
  7. Select Create Wallet. Confirm that the wallet is displayed under the target organization in the Wallets list and that its status is Active.
  8. Return to the Deposit Token application and open Create Bank Account for the target organization.
  9. Enter the same Bank User ID, select Load wallets, and choose the wallet that you created in Blockchain Platform Manager.
  10. Select the required application group, configure the account limits, and then select Create Account.
  11. Confirm that the deposit token account is created and that the user can select the expected wallet when signing in.

Identity Provider Configuration Using the API Does Not Work

You cannot add an identity provider by using the API.

Workaround: Use the GUI to add an identity provider.

Stack Information UI Mentions Incorrect Hosts Entry

The Stack information area of the installation UI incorrectly mentions wrapperapi.<instance-name>.<instance-domain> instead of wrapper.<instance-name>.<instance-domain> in the list of entries to add to the hosts file.

Workaround: Disregard the UI and use wrapper.<instance-name>.<instance-domain> instead.