User`s guide

214 Chapter 14: Database Administration
VCPDBA and all script files are bundled into a zip file. Please unzip all files into
one folder.
Example: C:\temp\VCPDBA
This section contains information on the following topics:
Current Limitations
Upgrade Considerations
Upgrade Limitations
Current Limitations
VCP DBA’s install path cannot contain spaces.
VCP DBA can only logon with Oracle’s
system
user.
Upgrade Considerations
As a general rule, the schema version should be upgraded to the same version as
the Viz Content Pilot (VCP) client tools. Although, it is important to remember in
which order to do the upgrade, and to do the actual schema upgrade work at a
convenient time when the system is not in use.
Please refer to the VCP release notes for recommended schema version for a
specific version of VCP System.
As the order is crucial for the functioning of the templates in the VCP system, the
following order of upgrading is recommended. If instructions are not followed,
and a newer version of Viz Template Wizard (VTW) is used to save a template, the
template will most likely not work inside the Newsroom Component (NrC) and
VCP client.
1. Upgrade Viz Content Pilot system’s schema in the VCP database
2. Upgrade all clients except the Viz Template Wizard client(s)
3. Upgrade the Viz Template Wizard client(s)
The order of 1 and 2 can be switched, but the last component to be upgraded
should always be the VTW. This is to avoid saving down templates with new
functionality that may come with the version, which is not supported by older
versions of the NrC or VCP client.
Test the versions of the NrC, VTW and VCP client you want to upgrade to, at least
on one non-live client of each. The test should involve at least opening all
templates in each client, saving down one data element of each template in the
NrC, and finally playing all those data elements out from the updated VCP client.
Contact local support team with information about the current state of the VCP
database; for example which version the current VCP schema is on, what version
you want to upgrade to so that support is aware that the upgrade is happening
and can prepare second line and personal follow-up, if needed.
When you start the upgrade process any data elements or new templates saved
after this time may be lost if the upgrade is not successful. The chances of this are
small, but it may happen and it should be incorporated into the plans.