Below is the workaround to fix the server type AFTER attempting to upgrade to 7.0.0.05.000 from a pre-6.3 release.  It is intended to resolve the upgrade failure, not to provide an alternative to following the recommended action of installing 6.3.0.xx code first.

1. Fix Server Type in MySQL from node 1.

a) Stop the VSM6 application and verify the nodes are down with the scstat. You should see two lines with dashes(--------)

/opt/vsm/bin/killtikka.pl

scstat -g

b)Start MySQL.

sudo /opt/vsm/bin/vsm_db.py --start

c) Change the SERVER_TYPE in the database. These are two separate commands.

source /opt/vsm/bin/mysql-env

mysql --port=3306 --protocol=tcp --user=root --password=egbdf123 --database=VSM6DB --host=mysql-lh -e "UPDATE VSM6DB.TIKKA_PROPERTIES SET PROPERTY_VALUE_CHAR='T4' WHERE PROPERTY_NAME='SERVER_TYPE'"

d) Verify the SERVER_TYPE is T4.

mysql --port=3306 --protocol=tcp --user=root --password=egbdf123 --database=VSM6DB --host=mysql-lh -e "SELECT PROPERTY_VALUE_CHAR FROM VSM6DB.TIKKA_PROPERTIES WHERE PROPERTY_NAME='SERVER_TYPE'"

You should see the following in the output:
.
+---------------------+
| PROPERTY_VALUE_CHAR |
+---------------------+
| T4 |
+---------------------+
.
If you see SPARC-T4 in place of T4, you missed some text.

e)Stop MySQL.

sudo /opt/vsm/bin/vsm_db.py --stop

f) Rerun the DCL.

/home/vsmadm/download/dcl -v 7.0.0.05.000

g) Verify the VSM6 nodes are fully operational with the scstat.

scstat -g

The following error may be found in the log file erip.out.  You can also verify the issue by running the commands in step 1. d) above in the workaround.

2016-06-06 14:37:23.215146 if>420 [ClusterProbeCommunicationServer] DEBUG com.sun.vtss.servers.clusterprobe.ClusterProbeCommunication - sendResponse(): Setting state to Starting: 16
2016-06-06 14:37:23.697358 if>902 [main] ERROR com.sun.vtss.config.VSMSystem - com.sun.vtss.config.ConfigException: java.lang.NumberFormatException: For input string: "P"
2016-06-06 14:37:23.697775 if>Exception in thread "main" com.sun.vtss.config.TikkaConfigException: Error to get VSM Model.

The above error means the Server type is not correctly set in MySQL database. We have "SPARC-T4" instead of "T4"

In addition, you will see the following.

Node 1 will show in the /vsm_logfiles/majorevents.log the following.
ClusterFail:FSC00100024_CLUSTER_FAILED_STARTING_MQB

Node 2 will show in the /vsm_logfiles/majorevents.log the following.
ClusterFail:FSC00100079_CLUSTER_FAILED_STARTING_ERIP2