vania-janet/multiturn-rag-retrieval-data huggingface dataset:
Make Ordering Service2 MSP an admin

While it is also possible to upload a JSON representing the MSP by clicking the Upload JSON tab, be aware that if you do this, the MSP will not appear in the Organizations tab and will therefore not be selectable later (for example, when updating an application channel to add the MSP as an ordering service administrator). For this reason, the best practice is to import the MSP through the Organizations tab first.

After the MSP has been added as an ordering service administrator, the operator of Console 1 must export the ordering service to Console 2. To export a node, navigate to the node and click on the "download" button (the button looks the same as it does in the above image showing the download of Ordering Service2 MSP). Then send the JSON file representing the ordering service to the operator of Console 2.





 Console 2: import Ordering Service 

After the operator of Console 2 has the JSON representing Ordering Service on its file system, they must click Add ordering service on the Nodes panel. Then, they must click Import an existing ordering service and click Next. On the following panel, they can click Add file and select the ordering service. Note that importing and associating an admin identity for this ordering service is an optional step. You can create a new node either way.

After Console 2 has imported the Ordering Service, they will be able to create the new node.

Zoom

![Import the ordering service](https://cloud.ibm.com/docs-content/v1/content/c5288bed34c3820e3a5251d820ee91adcd2591a3/blockchain/images/addremove_import_orderingservice.png)

Figure 4. Import the ordering service







 Create the node
How to resolve the Database related issues? 

If you get error messages or warnings during the database enrolment, check for the following troubleshooting tips:



1.  Message: Database credentials are incorrect

Ensure the Database Username and Password are correct.
2.  Message: Hostname or IP address is not submitted

Copy and paste the database endpoint precisely in the appropriate field, with no extra characters or spaces.
3.  Message: SSL certificate is not accepted

Ensure you have uploaded a valid SSL certificate.
4.  Message: Max connections reached on the database

Some database instances contain a limit on the maximum allowed connections to the server.



*  If the Postgres database is not connecting, check for the following troubleshooting tips:



a. Specify the Postgres Database name.

b. For PostgreSQL database servers, you must also pass the name of the database itself, which you intend to connect.

c. The default name is postgres; however, if there is not a database named "postgres" on your server, then the connection fails.
Click Service Credentials.
4. Click New credential and provide the necessary information. If you want to generate HMAC credentials, click the 'Include HMAC Credential' check box. Select the "Manager" service access role to allow the user to manage the bucket that you will select next.
5. Click Add to generate service credential.







 How do I resolve a 404 error when using the command line? 

You can view a bucket or object in the IBM Cloud console but the following error occurs when you use a command line interface to access that same bucket:



* Cloud CLI error: “The specified bucket was not found in your IBM Cloud account. This may be because you provided the wrong region. Provide the bucket's correct region and try again.”
* AWS CLI error: “An error occurred (NoSuchBucket) when calling the ListObjectsV2 operation: The specified bucket does not exist.”



The bucket’s location must correspond to the endpoint used by the CLI. This error occurs when the bucket or object cannot be found at the default endpoint for the CLI.

To avoid the error, make sure the bucket location matches the endpoint used by the CLI. For the parameters to set a region or endpoint, refer to the documentation for [Cloud Object Storage CLI](https://cloud.ibm.com/docs/cloud-object-storage?topic=cloud-object-storage-cli-plugin-ic-cos-cli) or [AWS CLI](https://cloud.ibm.com/docs/cloud-object-storage?topic=cloud-object-storage-aws-cli).





 How do I copy or move files to another bucket in a different location? 

Refer to [Move data between buckets](https://cloud.ibm.com/docs/cloud-object-storage?topic=cloud-object-storage-region-copy) for an example of how to use the rclone command line utility for copying data.
This requires the creation of a new ordering service that is located in Germany to ensure that the orderer's copy of the channel ledger is stored inside the country. Since in this case the ordering service, the OrgC-peer, and the OrgD-peer are located in Germany, Org C and Org D can now keep the data public on the channel if they choose, or they could still decide to use private data collections to prevent the full transaction data from being stored on the ordering service.

Creating a channel with all of the components in one country ensures that all of the data resides within one region, including the key-value pairs, the blocks, and the hashes of any private data. However, this option requires the resources to maintain a new channel and the costs that are associated with maintaining the ordering service.





 Option four: A separate channel with only ordering nodes from one country 

When you initially deploy an ordering service, you create a set of ordering nodes that will be available to the application channels for transaction processing. A major benefit of the Raft ordering service is that you can configure a channel to only use specific ordering nodes from the ordering service. That's why the console includes an Advanced Channel creation option to select a subset of ordering nodes to include in the channel consenter set, where each ordering node that you select will contain a copy of the channel ledger. Therefore, it is possible to restrict the channel ledger locations to only nodes that reside in country.

Zoom

![Spreading ordering nodes across countries](https://cloud.ibm.com/docs-content/v1/content/c5288bed34c3820e3a5251d820ee91adcd2591a3/blockchain/images/data_res_4.png)

Figure 6. Org C and Org D create a Channel Y using ordering nodes only located in Germany. All data is stored in the country on Ledger Y.

In Figure 6, the ordering nodes that participate in the Raft ordering service are spread across the two countries. Two ordering nodes are located in the United States, and three ordering nodes are in Germany for a total of five ordering nodes.