When you perform a check on a transfer session, the check ensures that you can create a system account on the remote server.
rootsessions, analyze the transfer session and validate whether you can transfer a username to the remote server.
- For user transfer sessions, validate whether you can transfer a username to the remote server.
In these examples, the following statements are true:
- You have two servers:
- You logged in to the local server with the
example.com,and you want to transfer it from the remote server to the local server.
- You want to transfer the
package1package from the remote server to the local server.
rootpassword for the remote server is
Analyze the transfer session
To confirm that the transfer session contains all of the items that you want to transfer, analyze the transfer session. To do this, use the
retrieve_transfer_session_remote_analysis function, as in the following examples:
The function call returns the following list:
- Transfer session settings.
- Local and remote groups and users.
- Databases and database users.
- Packages and accounts (transfer items) that the transfer session contains.
The function returns metadata, as in the following example:
dbs containers are empty. Those containers will hold accounts, packages, databases, and database users.
Validate the username
To ensure that the username is not currently in use, validate whether you can transfer that username to the remote server. To do this, use the
validate_system_user function, as in the following examples:
The output contains the following Boolean values which you can use to check the username:
There is no content with the specified labels