Upgrading RED

WhereScape Versions

WhereScape RED has a four-part version number normally shown as xx.xx.xx.xx. An example of this may be 6.0.6.0. The first number represents the major release. The second number represents the metadata repository version. The third and fourth numbers relate to application specific releases.From the example above we see that the current version is version 6 of WhereScape RED. We are on version 6.0 of the metadata repository.

Metadata Changes

A change from a 6.0.. release to a 6.5.. release would indicate a change in the metadata tables. All metadata changes are non destructive. They simply add new columns or new meta tables. In this way they can be applied without harming an existing metadata repository. The impact of a metadata change is that the associated applications (namely the RED executable, the Scheduler, security module etc.) will need to be at the same metadata version. Therefore a 6.0.6.0 version of RED may not successfully run against a version 6.5 metadata repository. 

Application changes

The final two numbers in the version represent application releases. Applications are deemed to be all of the executable images supplied with WhereScape RED as well as the UNIX scheduler scripts and the stored procedures. Application changes reflect enhancements and bug fixes. A change in the first number indicates a major enhancement in one of the application components.

Upgrading RED

Upgrading WhereScape RED consists of the following steps:

  1. Allow any active jobs to complete. Halting active jobs will allow running tasks to complete with no new tasks starting. Aborting active jobs will kill any running tasks and stop running jobs.
  2. Stop all schedulers. Windows schedulers can be stopped with WhereScape's Setup Administrator. To stop a UNIX or Linux scheduler, kill the active scheduler process and comment their crontab entries (to stop the scheduler re-starting itself).
  3. Close any WhereScape programs that are running on your machine.
  4. Install the new version of RED on your machine.
  5. Back up your metadata.
  6. In RED Setup Administrator, select the Validate Metadata Repository option. This function may re-compile existing or create new metadata procedures; metadata tables may be altered or new tables created. When performing an upgrade of RED:
    • Click OK when prompted to validate metadata tables.
    • Click Yes when prompted to re-create metadata views.
    • Click Yes when prompted to re-compile metadata procedures.

      Note

      If the above steps are not all completed during an upgrade the metadata may be left in an inconsistent state.

  7. For Oracle metadata updates see the note below on recompiling Oracle invalid procedures during a RED upgrade.
  8. Back up your metadata again (just in case).
  9. If using a UNIX or Linux scheduler and this is a major application enhancement then rename the wsl/bin directory to say wsl/bin_versionxxxxxx. Create a new bin directory and ftp over the files under the unix directory (see the main install instructions). Change the protections on the files (chmod 750 *.sh). 
  10. Restart all schedulers. Windows schedulers can be restarted with WhereScape's Setup Administrator. For any UNIX or Linux schedulers, uncomment any commented out crontab entries - this is enough to restart the schedulers.
  11. Restart any halted or aborted jobs.

Note

  1. There are different versions of the scripts for each database and for UNIX versus Linux. You should also be looking in the sub directory with the highest version number. When using a UNIX/Linux scheduler for Oracle, It is recommended that users copy the new meta_backup_680.sh file to use Datapump's expdb/impd instead the deprecated exp/imp tools. This version uses the data pump export executables expdp/impdp. It assumes that the scheduler and the Oracle database reside on the same server.
  2. Metadata tables do not change between minor releases, but metadata procedure often and usually do change.
  3. RED will not let you sign into an old repository version, using a newer version of RED.
  4. RED will let you sign into a new repository version, using an older version of RED, but it will warn you that this may potentially cause issues.
  5. It is very important when using the Windows scheduler to have the installed RED version on the scheduler server EXACTLY matching the stored procedures.
  6. Side by side installations are possible (two versions in two directories on the same machine), but be careful with schedulers. If you install the new version of RED in a new directory, you will have to remove and reinstall all windows schedulers in order for the scheduler(s) to use the new version of RED.
  7. As a general rule, the UNIX and Linux scheduler scripts, metadata tables/procedures and RED front end should all be in sync.
  8. If the scripts for the UNIX or Linux scheduler have changed, you should replace files in your old and new shell scripts in the WhereScape Program Files directory and see if any have changed.

Oracle invalid procedures:

When validating an Oracle Metadata Repository, tick the Recompile any invalid procedures checkbox to have any invalid user procedures recompiled during a metadata validate.

  • No labels