Tidal Enterprise Orchestrator: Upgrade of Oracle Database Targets Causes Issue with Port

Introduction

This document describes an issue customers will see when they upgrade from Tidal Enterprise Orchestrator (TEO) 2.1.x to 2.2 with Oracle Database Targets.

Prerequisites

Components Used

The information in this document is based on Tidal Enterprise Orchestrator 2.2 or 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.

Conventions

Refer to Cisco Technical Tips Conventions for more information on document conventions.

Issue

After the upgrade from a 2.1.x TEO system to a 2.2 TEO system, the targets will need to be checked and information added. However, the targets will have an error when attempting to connect. This is typically seen in an ORA-12541 error or some error in relation to the port. This issue only occurs when the target was defined in 2.1.x, and will not occur if the target is newly defined in 2.2.

Workarounds

There are two workarounds for this issue:

• The target can be deleted and re-created.

• The connection string can be changed to Data Source={DS};SID={SID};Port={PT};Unicode=true.

  Note: Make sure the ports are correct when you update the connection string.

  The target should then be able to be saved.

Related Information

• Technical Support & Documentation - Cisco Systems