HP Neoview Release 2.3 Software - Manual (Page 17)

2 Getting Started with Repository 2.3
Installation
The Repository is initially installed on the Neoview platform by HP Manufacturing. Repository
upgrades are installed by field personnel in the context of Neoview platform upgrades.
If no Repository program files or tables have ever existed on the platform, the installation script
creates Repository tables and views, and installs and starts Repository 2.3 processes.
If an earlier version of the Repository software is installed on the platform, the script removes
the existing Repository program files, then installs and starts the Repository 2.3 processes.
If tables from Repository 2.2 exist on the platform, the installation script does not remove those
tables. Release 2.3 Repository tables and view definitions are created in a catalog and schema
different from those used in earlier releases, so new tables and views do not overwrite existing
data.
NOTE: Although data collected in Release 2.2 is preserved by the installation script, no tools
are provided for migrating existing data to Release 2.3 tables.
Also, in certain cases HP Support might explicitly uninstall an older Repository version before
upgrading to Release 2.3. Conditions that might necessitate an uninstall include
• System malfunctions affecting the database
• Database malfunctions that cause tables to be corrupted
• Missing prerequisite software
• Mismatches between the database and Repository processes (for example, if a prior
installation of Repository software succeeded but the corresponding database upgrade
failed)
In such cases, accumulated data will not be retained. Please consult your HP representative prior
to a platform upgrade if you require preservation of old Repository data.
Character Set Support in Repository Views
The Repository installation script is aware of whether a Neoview platform is configured to
support the ISO88591, Japan Shift-JIS, or UTF-8 character set. If the platform is configured for
ISO88591, then character fields in all Repository tables and views will contain ISO88591 data. If
the platform is configured for Japan Shift-JIS or UTF-8, character fields in some, but not all,
Repository views contain double-wide UCS2–encoded data. The description of each view in
Chapter 3 (page 21) indicates whether the view supports UCS2–encoded data. “Retrieving UCS2
Columns” (page 69) discusses how to retrieve UCS2 data from an ISO88591 workstation.
Regardless of the character set used by the Neoview platform, column names in Repository views
are encoded using ISO88591, and segment names are not internationalized.
Adapting Existing Queries to a New Repository Version
Queries against views defined in previous Repository versions must be updated, as described
in this section, to work with Repository 2.3.
Installation 17