Process Orchestrator: TEOReporting Database Failed to Upgrade

Available Languages

Updated:January 24, 2012
Document ID:113402

Bias-Free Language

The documentation set for this product strives to use bias-free language. For the purposes of this documentation set, bias-free is defined as language that does not imply discrimination based on age, disability, gender, racial identity, ethnic identity, sexual orientation, socioeconomic status, and intersectionality. Exceptions may be present in the documentation due to language that is hardcoded in the user interfaces of the product software, language used based on RFP documentation, or language that is used by a referenced third-party product. Learn more about how Cisco is using Inclusive Language.

Introduction

This document describes why the Reporting Database upgrade can fail if the Tidal Enterprise Orchestrator (TEO) instance has been down for some time.

Prerequisites

Components Used

The information in this document is based on the Cisco Process Orchestrator 2.2 and later.

The information in this document was created from the devices in a specific lab environment. All of the devices used in this document started with a cleared (default) configuration. If your network is live, make sure that you understand the potential impact of any command.

Problem

Assuming you are using the defaults with grooming, and assuming either the TEO instance has been down for 6+ months or that the SQL jobs for your TEOReporting database have not run for 6+ months, the TEOReporting database upgrade might fail when executed.

Solution

Complete these steps:

  1. Run the TEOReporting - Partition Tables Maintenance SQL job in order to bring your tables up to date and perform the proper maintenance.

  2. Run the TEOReporting Upgrade script found in the database scripts folder of the install media in order to complete the upgrade.

Related Information

Was this Document Helpful?

FeedbackFeedback

Contact Cisco

This Document Applies to These Products