Copying and activating the customer’s administration and options
Recovering from failed installation scripts
If an error message is displayed, such as the following, a failure occurred in one of the installation scripts.
ERROR[1]: FUNCTION S00install_sql() FAILED at <time stamp> script /adminsave/init.d/S00install_sql failed
You may be able to recover and continue with the upgrade. Some of the installation scripts can be skipped during this part of the upgrade. However, any script that is skipped during this part of the upgrade must be installed later using the standard software installation procedures found in the CMS software installation document.
The following table lists all of the possible software installation scripts, and explains what to do if one of them fails during the upgrade. When identifying the installation scripts, be aware that each script is numbered with a prefix (for example, S04) before the script name.
Script name | Description |
| How to recover | |
|
|
| ||
|
|
| ||
install_sql | ISQL software | All of these scripts install optional software or | ||
|
| drivers needed by the customer. You can skip the | ||
install_nts | NTS drivers | |||
script and reinstall the software later. To skip the | ||||
|
| script: | ||
install_odbcX_X | ODBC software | |||
1. | Enter: cd /adminsave/init.d | |||
init_visual_vectors | Visual Vectors software | 2. Enter: mv scriptname /adminsave/ where | ||
scriptname is the name of the script. | ||||
|
| |||
|
| 3. | Enter: cd /cdrom/cdrom0 | |
|
| 4. | Run the ./cvue_activate command again. | |
|
| 5. | Install the software package that you skipped | |
|
| before you migrate the customer’s data. | ||
|
| After each script is executed, a copy of the script is | ||
|
| automatically moved to the directory | ||
|
| /adminsave/init.d.completed. | ||
|
|
|
| |
58 Avaya CMS R12 Sun Enterprise 3500 Computer CMS Upgrade Express
