Verifying the Server for Upgrade

This procedure tests to make sure the server is ready for the upgrade process. It does not actually perform any upgrade steps.

Start sybcluster. For example, enter:
```
sybcluster -U uafadmin -P -F "mynode:8999"
```
Where:
- -U – is the login name for the Unified Agent. “uafadmin” is the default value.
- -P – is the Unified Agent password. The default password for “uafadmin” is null or blank.
- -F – specifies the node on which the Adaptive Server is running and the listening port for the Unified Agent. The default value is “9999”.
  In this example, the node name is “mynode” and the UAF listening port is “8999”.
  
  Note: You must specify the node on which the upgrade is to take place.
Start the verification. From the sybcluster command line, enter:
```
upgrade server server_name checkonly
```
For example:
```
upgrade server myserver checkonly
```
Respond to the upgrade server checkonly prompts. Default values are displayed in square brackets. The prompts are:
1. Enter the name of the cluster [ server_name ]: Enter the existing Sybase installation directory for server server_name.
2. Enter the complete path to the Sybase installation directory: For example, enter “/myserver/sybase15”.
3. Enter the name of the subdirectory containing the ASE installation for server server_name: For example, enter “ASE-15_0”.
4. Enter the name of the subdirectory containing the OCS installation for server server_name: For example, enter “OCS-15_0”.
5. Enter the name of an sa login on server server_name: For example, enter “sa”.
6. Enter a password: Enter the password for the sa login.
7. Enter the maximum number of instances: [4]
8. How many nodes (hardware hosts) will participate in this cluster? [1]
9. Enter the number representing the cluster node 1: [1]
10. Enter the full path to the quorum disk.
11. Enter any traceflags.
12. Enter the full path to the existing master device.
13. Does this cluster have a secondary network? [Y]
14. Enter the port number from which this range will be applied. [15100]
15. Enter the SYBASE home directory.
  
  Note: sybcluster provides default locations for steps 15 through 19.
16. Enter the environment shell script path.
17. Enter the ASE home directory.
18. Enter the interfaces directory.
19. Enter path to the dataserver configuration file.
20. Enter the name of the first instance in this cluster.
  
  Note: The upgrade process creates a cluster with a single instance.
21. Enter the interface file query port number for instance_name.
  
  Note: Ensure that the instance query port number is same as the query port number for the old nonclustered server, otherwise the upgrade may fail.
22. Enter the local system temporary database device name. You can create local system temporary database on shared disks only. See Chapter 6, “Using temporary databases” in Cluster Edition User Guide for more information about using local disks for temporary data.
23. Enter the local system temporary database device path.
24. Enter local system temporary database device size (MB). [100]
25. Enter the local system temporary database name. For example: [cluster_name_tdb_1]
26. Enter the local system temporary database size (MB). [100]
27. Would you like to save this configuration information in a file? [ Y ]
  Note: If the verification succeeds, you can use this file as input to upgrade the server. You also can use it as input to validate the server for numerous subsequent upgrades, if needed. For example,
```
upgrade server server_name file /data/myserver_ce.xml checkonly
```
28. Enter the name of the file to save the cluster creation information. For example: /data/myserver_ce.xml.
29. Create the cluster now? [Y]
  
  If you enter “Y”, sybcluster starts the verification process. It displays informational messages as the process proceeds. It does not perform any of the upgrade steps.
If the verification process succeeds, you can upgrade the server.
If sybcluster displays error messages, resolve all error messages resulting from the check before upgrading the server.