Tidal Enterprise Scheduler: Transporter Will Not Connect to Two Different Databases if the Tidal Account Passwords Do Not Match

Available Languages

Download Options

PDF (5.5 KB)
View with Adobe Reader on a variety of devices

Updated:January 30, 2012

Document ID:113415

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

Prerequisites

Components Used

Conventions

Problem

Reason

Related Information

Introduction

This document describes why Transporter will not connect to two different databases if the Tidal passwords do not match.

Prerequisites

Make sure that you meet these requirements before you attempt this configuration:

5.3.1 Master

Components Used

This document assumes the use of 5.3.1 Transporter.

Conventions

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

Problem

Transporter will not connect to two different databases if the Tidal passwords do not match.

Reason

The Tidal account password must be the same on both the source and destination databases. When the database password is changed from the default password, the new password is stored in the registry of the Windows client machines in an encrypted key. Transporter is a client tool that connects to both source and destination databases, and knows to use the password that is in that encrypted key. Since there can only be one key, the passwords have to match.