Neoview Repository User Guide (R2.4 SP1)

2 Getting Started with Repository
Installation
The Repository is initially installed on the Neoview platform by HP Manufacturing. Repository
upgrades are installed by HP Support in the context of Neoview platform upgrades.
NOTE: Although data collected in Release 2.4 is preserved by the installation script, no tools
are provided for migrating existing data to Release 2.4 SP1 tables.
The upgrade from Release 2.4 to Release 2.4 SP1 moves the R2.4 data to a different table. The
data is still located on the Neoview platform and is accessible through three new views available
in this release:
• ODBC_QUERY_STATS_V1_2400
• ODBC_QUERY_STATS_V2_2400
• QUERY_RUNTIME_STATS_V1_2400
This data is considered to be archived and is not updated as queries are executed on the platform.
Only new data is written to the new table and is available via the new QUERY_STATS_VW1
view.
Also, in certain cases HP Support might explicitly uninstall an older Repository version before
upgrading to Release 2.4 SP1. 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 ISO8859-1, Japan Shift-JIS, or UTF-8 character set. If the Neoview platform is
configured for the ISO88591 configuration, then character fields in all Repository tables and
views will contain ISO8859-1 data. If the platform is configured for the SJIS or Unicode
configuration, 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 From a Workstation Configured
for ISO8859-1” (page 86) discusses how to retrieve UCS2 data from an ISO8859-1 workstation
or “from a workstation configured for the ISO8859-1 character set”).
Regardless of the character set used by the Neoview platform, column names in Repository views
are encoded using ISO8859-1, and segment names are not internationalized.
Obtaining Prepackaged Queries
Prepackaged queries against the Repository are distributed as part of the Neoview Reports
product. These queries can also be run from HPDM.
Starting the Repository
During installation, the Repository is configured to come up automatically when the Neoview
platform starts.
Installation 19