Guest

Cisco Tidal Enterprise Scheduler

Tidal Enterprise Scheduler 5.3.1: Unable to Connect Oracle DB Adapter to an Oracle Database Set up as Read-Only

Document ID: 113538

Updated: Aug 10, 2012

   Print

Introduction

This document provides information about issues with the Tidal Enterprise Scheduler 5.3.1 Oracle Database Adapter.

Prerequisites

Requirements

Cisco recommends that you have knowledge of these topics:

  • Windows Tidal Enterprise Master 5.3.1

  • Tidal Enterprise Scheduler Oracle Database Adapter

Components Used

The information in this document is based on the Tidal Enterprise Scheduler Oracle Adapter.

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.

Problem

When you use the Oracle Database Adapter, you are unable to successfully connect the adapter to a database that is setup with the Read-Only mode. You can see this in the service log file:

<<<<<<<<<
02/15 10:51:09:718[MD-4]: (mem=3344216/16711680) java.sql.SQLException: Fail to convert to internal representation
                        at oracle.jdbc.driver.DatabaseError.throwSqlException(DatabaseError.java:125)
                        at oracle.jdbc.driver.DatabaseError.throwSqlException(DatabaseError.java:162)
                        at oracle.jdbc.driver.DatabaseError.throwSqlException(DatabaseError.java:227)
                        at oracle.jdbc.driver.CharCommonAccessor.getInt(CharCommonAccessor.java:146)
                        at oracle.jdbc.driver.OracleResultSetImpl.getInt(OracleResultSetImpl.java:482)
                        at bf.m(Unknown Source)
                        at bf.a(Unknown Source)
                        at bi.e(Unknown Source)
                        at com.tidalsoft.service.logic.ConnectionMessageHandler.onInitializeConnection(Unknown Source)
                        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
                        at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
                        at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
                        at java.lang.reflect.Method.invoke(Unknown Source)
                        at ca.a(Unknown Source)
                        at be.b(Unknown Source)
                        at be.a(Unknown Source)
                        at com.tidalsoft.framework.message.BaseMessageHandlerImpl.onMessage(Unknown Source)
                        at com.tidalsoft.framework.data.DataWrapper.onMessage(Unknown Source)
                        at af.run(Unknown Source)>>>>>>>>>>>

Solution

In a Read-Only database, the session ID is very large that the data type used in the code cannot accommodate. So in order to resolve this, you have to fix the data type so that it can handle the session ID.

This was corrected in build 2.1.0.99 of the Oracle Database Adapter.

Related Information

Updated: Aug 10, 2012
Document ID: 113538