3.1.7 Distribute a Wallet

You may need to move or copy your Exascale user wallet to connect using various different Exascale clients.

• To move or copy an Exascale user wallet within the same platform (for example, from one Exadata Linux server to another), you can use an archiving utility, such as zip. When you do this, you must ensure that you copy the entire contents of the wallet location.

  For example:

  $ zip -r wallet.zip /home/user/user.wallet

  In the previous example, the wallet located at /home/user/user.wallet is zipped into an archive named wallet.zip. You can then distribute the archive (wallet.zip) to the required client and unzip it into the required location.

  For example:

  $ unzip wallet.zip -d /path/to/wallet

• To copy an Exascale user wallet across different platforms (for example, from an Exadata Linux server to a non-Linux Exascale client system), you must create a new wallet on the desired host and populate it with the required user credentials. To move an Exascale user wallet across platforms, you must create a copy of the wallet and then delete the original.

  If you have the required user credentials, then you can use the procedures described in:

  • Create a Wallet
  • Store a Private Key in a Wallet
  • Fetch the Trust Store
  • Store the Exascale Control Services Endpoint

  If you do not have the required user credentials, then you can get them from the existing wallet by using the ESCLI lswallet command.

  For example, the following command displays the Exascale user identifier and the Exascale control services endpoint that are stored in the wallet at /home/user/user.wallet:

  @> lswallet --wallet /home/user/user.wallet --attributes user,restEndPoint

  In the following example, the private key is extracted from the wallet and stored in a regular PEM file located at /home/user/priv.pem:

  @> lswallet --wallet /home/user/user.wallet --private-key-file /home/user/priv.pem

Regardless of the method used to duplicate the wallet, to use an Exascale user wallet in conjunction with Oracle Database or Oracle Grid Infrastructure, you must copy the wallet into the correct location on each database cluster node.