• No results found

... WinINSTALL MSI Packager Professional. Upgrade Guide ...

N/A
N/A
Protected

Academic year: 2021

Share "... WinINSTALL MSI Packager Professional. Upgrade Guide ..."

Copied!
14
0
0

Loading.... (view fulltext now)

Full text

(1)

. . . . .

WinINSTALL 8.70.04

MSI Packager Professional

. . . Upgrade Guide

(2)

Disclaimer

The information contained in this publication is subject to change without notice.

Attachmate Corporation makes no warranty of any kind with regard to this manual, including, but not limited to, the implied warranties of merchantability and fitness for a particular purpose. Attachmate Corporation shall not be liable for errors contained herein or for incidental or consequential damages in connection with the furnishing, performance, or use of this manual.

Copyright

© Copyright 1991-2006 by Attachmate Corporation. All Rights Reserved.

Migration Engine © Copyright 1998-2006 by Tranxition Corporation. All Rights

Reserved.

(3)

U PGRADING W IN INSTALL FROM VERSION

8.70, 8.70.0100, 8.70.0200, 8.70.0201,

. . . . .

. . . . OR 8.70.0300 TO VERSION 8.70.0400

This document provides instructions for upgrading WinINSTALL MSI Packager Professional from version 8.70, 8.70.0100, 8.70.0200, 8.70.0201, or 8.70.0300 to WinINSTALL MSI Packager Professional 8.70.0400.

This patch will not upgrade WinINSTALL Limited Edition (LE), WinINSTALL, WinINSTALL Software Distribution Suite, WinINSTALL, WinINSTALL Desktop Management Suite, WinINSTALL Desktop Availability Suite, or WinINSTALL MSI Packager Professional 8.6x or earlier. This patch will upgrade only WinINSTALL MSI Packager Professional 8.70, 8.70.0100, 8.70.0200, 8.70.0201 and 8.70.0300.

To upgrade from any version of WinINSTALL LE, or from WinINSTALL MSI Packager Professional version 8.6x or earlier, you must first uninstall your current version and then install WinINSTALL 8.70.04. This uninstall and reinstall procedure will not alter or remove any of your packages.

To upgrade from WinINSTALL Software Distribution Suite or from WinINSTALL, WinINSTALL Desktop Management Suite or WinINSTALL Desktop Availability Suite, you will need the patch for your particular WinINSTALL product.

. . .

P R O C E S S O V E R V I E W

The upgrade process involves the following three steps, each of which is described in detail later in this document:

STEP ONE: PREPARING TO UPGRADE

• Assure that you will not encounter file contention during the upgrade process, either by stopping all the WinINSTALL MSI Packager consoles or by un-sharing the

WinINSTALL share.

STEP TWO: UPGRADING THE CONSOLE AND THE WININSTALL SHARE

• Unzip the patch to a folder and run MSPApply.exe. MSPApply will populate the Available Shares pulldown with any shares it can find. If you have more than one WinINSTALL share, each must be patched individually. You can also manually enter a share.

(4)

• Click on Apply Patch… to begin upgrading the selected share. When the Windows Installer completes, the Patch Status window should show the patch as successfully applied.

Repeat as necessary for any additional WinINSTALL MSI Packager shares.

STEP THREE: UPGRADING THE DATABASE

• On launching the Console after upgrading, you will be asked if you want the upgrade DDL applied to upgrade the database. It is recommended that you do so. If you do not, you will need to apply the DDL manually (see the Database Schema Upgrade section of the appendix to this guide).

. . .

S T E P O N E : P R E P A R I N G T O U P G R A D E

A couple of steps are required before the WinINSTALL upgrade can be done. These steps are important as failure to follow these steps can result in a failed patch process which may not always be evident until WinINSTALL is back in use.

The following steps must be taken prior to running MSPAPPLY.EXE:

1 ALL WinINSTALL consoles must be closed.

2 If you were previously given a drop on file by technical support to resolve an issue with WinINSTALL you must restore the file to its original version, failure to do so results in a patch error which will force a cancellation of the patch process.

S T E P T W O : U P G R A D I N G T H E C O N S O L E A N D

. . .

T H E W I N I N S T A L L S H A R E

Follow these steps only if Help>About displays your current version as WinINSTALL MSI Packager Profesional 8.70, 8.70.0100, 8.70.0200, 8.70.0201, or 8.70.0300.

1 Follow the steps mentioned above for preparing for the upgrade.

2 Create a temporary folder on your Share machine and copy the extracted patch files there.

NOTE: If you have stopped sharing the WinINSTALL share, you must

run MSPApply on the local machine where the share is located.

(5)

. . . . .

U P G R A D I N G W I N I N S TA L L F R O M V E R S I O N 8 . 7 0 , 8 . 7 0 . 0 1 0 0 , 8 . 7 0 . 0 2 0 0 , 8 . 7 0 . 0 2 0 1 , O R 8 . 7 0 . 0 3 0 0 T O V E R S I O N 8 . 7 0 . 0 4 0 0

3 Run MSPAPPLY.EXE

4 Make sure the Available Shares drop down box at the top of the window has the correct location of the WinINSTALL folder.

5 Once the Status shows Ready to apply patch… Click Apply Patch.

(6)

6 Upon successful completion of the patch the status box will say Patch Application successful for WinINSTALL Share 8.x (where X is the appropriate version number). You can now click the Close button.

The Console upgrade is now complete.

. . . S T E P T H R E E : U P G R A D I N G T H E D A T A B A S E

WinINSTALL 8.70.0400 requires a database schema upgrade. The schema upgrade can usually be carried out automatically when the Console is first started following the upgrade of the Console to the new version.

1 When the Console is first started after the upgrade, you will be prompted whether or not to upgrade the database schema. Click the Yes button to display the Database Upgrade dialog, which looks like this:

(7)

. . . . .

U P G R A D I N G W I N I N S TA L L F R O M V E R S I O N 8 . 7 0 , 8 . 7 0 . 0 1 0 0 , 8 . 7 0 . 0 2 0 0 , 8 . 7 0 . 0 2 0 1 , O R 8 . 7 0 . 0 3 0 0 T O V E R S I O N 8 . 7 0 . 0 4 0 0

2 The recommended action is to leave the check boxes as they are. If the Apply Update to Database checkbox is checked, the update will be performed.

Checking the Create DDL File checkbox will cause a file to be created, containing the DDL commands needed to upgrade the database. This file may be useful for archival purposes.

Alternatively, you may deselect the Apply Update to Database checkbox, select the Create DDL File checkbox, and follow the instructions in the Database Schema Upgrade section of the appendix of this guide to manually pass the resulting DDL file to a database utility to do the upgrade.

3 Pressing the Start button will begin the processing. The results will display in the window on the Database Upgrade dialog, and should look something like this when complete:

NOTE: When updating an Oracle database, since the Oracle client is installed on the Console machine, there should be no problems in

accomplishing the update. The same is true for MSDE, if that is installed on the same machine as the Console. In the case of SQL Server, where the database typically resides on a different machine, it will not be possible to update the schema without access to osql.exe (which is found on the DBMS machine). There will be a warning message in this situation. In such an instance, you can create the DDL file (see the following paragraphs) and then manually apply the DB schema update (see the Database Schema Upgrade section of the appendix to this guide).

NOTE: If you want to update the database manually, be sure you have checked the Create DDL File checkbox before clicking the Start button.

You will be prompted to specify the name and location of the DDL file to

be created. For details on using the DDL file to upgrade your database

manually, see the Database Schema Upgrade section in the appendix to

this manual.

(8)

The text field contains descriptions of the actions taken, the SQL statements executed, and the results of each statement. The message ***Database upgraded successfully indicates that there were no problems. If there were errors, a message indicating that there were errors will appear and the error details will appear after the relevant SQL statement.

Clicking the Write Results to Text File button will produce a text file containing all of the contents of the text field.

TIP: If the last message indicates that problems occurred during the

upgrade process, it may be helpful to click the Write Results to Text File

button to save the details of the upgrade attempt for diagnostic purposes.

(9)

. . . . .

U P G R A D I N G W I N I N S TA L L F R O M V E R S I O N 8 . 7 0 , 8 . 7 0 . 0 1 0 0 , 8 . 7 0 . 0 2 0 0 , 8 . 7 0 . 0 2 0 1 , O R 8 . 7 0 . 0 3 0 0 T O V E R S I O N 8 . 7 0 . 0 4 0 0

To continue to the WinInstall console, click OK. The upgrade is now complete, and choosing Help>About should now display the version as 8.70.04.

WARNING: The Cancel button is available up until the database

upgrade is finished. Pressing the Cancel button will cause the upgrade process not to complete. Though the upgrade process can usually be successfully restarted, it is highly recommended not to interrupt the process once it has started.

NOTE: The database upgrade process begins by reading the schema definition from the database. This initial step is the most time-consuming part of the process, and it may appear that nothing is happening.

Cancelling during this time will not cause the process to stop

immediately, though it will prevent any upgrades from actually taking

place. However, once the SQL statements start appearing on the

screen, it is best to let the process complete.

(10)
(11)

. . . . . . . . .

A PPENDIX

. . .

D A T A B A S E S C H E M A U P G R A D E

If you follow the upgrade instructions in this document, you will be asked whether or not to upgrade the schema when the Console is first started following the share upgrade. If you decline, you can follow these steps to upgrade manually, outside of the Console.

CREATE THE DATABASE UPDATE DDL

If you have not already created the DDL necessary to update the database schema (as described earlier in this manual), you can do so now by starting the Console again. If the database schema requires updating, you will be prompted to perform the upgrade or create the DDL file to use in doing so.

To create the DDL, follow these steps:

1 Be sure that the Apply Update to Database checkbox is unchecked.

2 Be sure that the Create DDL File checkbox is checked.

3 Click the Start button to create the DLL file. You will be prompted for the filename and location.

(12)

MANUAL STEPS TO UPGRADE SQL SERVER

Open a Command Prompt and use OSQL.EXE to update the database schema using the DDL file you created earlier (see Create the Database Update DDL, above, for instructions on creating this DDL file). If you previously installed MSDE, do this from that machine.

Otherwise do this where your database resides.

If SQL Server authentication is being used, you would enter the following command line:

osql -I -n -S YourDBMachine\WinINSTALL -d YourDatabase -i C:\Program Files\WinINSTALL\Bin\WI_SSRV_UPD.DDL -U sa -P pwd In the above example, YourDBMachine\WinINSTALL refers to the machine where your database resides, \WinINSTALL refers to the instance name, ‘sa’ is the account and ‘pwd’

the password.

If NT authentication is being used, you would enter this command line:

osql -I -n -S YourDBMachine\WinINSTALL -d YourDatabase -i C:\Program Files \WinINSTALL\Bin\WI_SSRV_UPD.DDL -E”

MANUAL STEPS TO UPDATE ORACLE

Upgrading the database requires the use of the program SQLPLUS, provided with Oracle.

You may use either the command line utility, SQLPLUS, or the version providing a window interface, SQLPLUSW.

The following instructions apply to SQLPLUS.

To perform the upgrade, you will need the following information:

• The local net service name associated with the WinINSTALL database.

• The user ID of the owner of that database.

• The password associated with the user ID.

• The path of the DDL file you created earlier (see Create the Database Update DDL, above, for instructions on creating this DDL file).

It is easiest to run the utility on a machine where the WinINSTALL console is installed.

Such machines should already have a local net service name assigned to the database.

Running SQLPLUS to perform the upgrade is a four-step process:

1 Open a Command Prompt window for entering the command.

2 Start the SQLPLUS program.

3 Tell SQLPLUS to run the .DDL file.

4 Exit the SQLPLUS program.

(13)

. . . . .

A P P E N D I X Upgrade Problems

Here is an example of how to perform steps two through four:

First, start SQLPLUS via a command prompt:

sqlplus system/pwd@YourDB

A few lines of copyright information will be displayed, followed by a SQL> prompt. At this prompt, enter the following:

start \\ShareMachine\WinINSTALL\Bin\WI_ORAC_UPD.DDL

This will cause several screens full of informational messages to display as the schema is updated.

You may want to scroll back to ensure that no errors were encountered.

Finally, to exit the program, at the next SQL> prompt, enter:

exit

This command will return you to the Command Prompt window's command prompt, where another exit will close the Command Prompt window.

. . .

U P G R A D E P R O B L E M S

It is possible that the console will not upgrade properly. If this happens, the database schema will also not be upgraded properly, and any or all of the following symptoms may appear:

• The console will fail to update the database when it starts for the first time after applying the patch.

• The WinINSTALL logs will show numerous database errors.

• The console will display numerous SQL errors.

• The console’s Help->About dialog will not show a product version of 8.70.0400.

You can correct the problem by following this procedure:

Local Net Service Name:

• YourDB

User ID: • System

Password: • pwd

DDL File

Path: • \\ShareMachine\WinINSTALL\Bin\WI_ORAC_UPD.DDL

(14)

1 Start the Control Panel and select Add/Remove Programs.

2 Select the WinINSTALL Console entry and click on the ‘support information’ link 3 Finally, click the ‘Repair’ button. An install session will run, after which the console

should be repaired.

4 Start the console again and verify the version. If the version does not display as 8.70.0400, please repeat this process.

References

Related documents

You can talk to PALS which provides confidential advice and support to patients, families and their carers, and can provide information on the NHS and health related matters...

○ If BP elevated, think primary aldosteronism, Cushing’s, renal artery stenosis, ○ If BP normal, think hypomagnesemia, severe hypoK, Bartter’s, NaHCO3,

[r]

You can manage all of your Windows 10 devices alongside your mobile devices with whatever mobile device management (MDM) solution you already have in place. Windows 10 allows

Both of the hypotheses relate variations in the size of the divorce effect to changes in the prevalence of divorce: Is the negative effect of breakup stronger (as is predicted by

You can select each file by clicking the checkbox to the left of the filename, or if you want to download all files click the ALL hyperlink above the first checkbox, and then click

Use this technique to upgrade multitenant architecture Oracle Database releases (Oracle Database 12c Release 1 (12.1.0.1) and later by upgrading container databases (CDBs), and

Atos’s Oracle Database Upgrade service provides an upgrade to not only the specific database products but if required an update to the whole technology stack The Atos Oracle