My Oracle Support Banner

Troubleshooting The "Protocol Violation" Messages Received By ODI When Using Oracle Database (Doc ID 1277404.1)

Last updated on JANUARY 06, 2020

Applies to:

Oracle Data Integrator - Version 10.1.3.2.0 and later
Information in this document applies to any platform.

Purpose

NOTE: In the examples below, the names represent a fictitious sample for clarity. Any similarity to actual environments, past or present, is purely coincidental and not intended in any manner.

This document is intended to Oracle Data Integrator (ODI) users that receive "Protocol Violation" messages when their Repositories or Data Server are hosted on Oracle technology.

Troubleshooting Steps

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!


In this Document
Purpose
Troubleshooting Steps
 You receive intermittent "Protocol Violation" messages, and Oracle database version is 11.2.0.1...
 Intermittently, ODI does not generate Session Steps and Tasks...
 You are using ODI on Solaris 64-bit operating system, and receive intermittent ORA-174012 and/or "Protocol Violation" messages...
 Sudden "Protocol Violation" messages signaled when connecting to Oracle database...
 You receive "Protocol Violation [0]" messages when using ODI J2EE Agent on Exalogic
 You receive "Protocol Violation" messages when trying to create a transaction using the ODI SDK in Java...
References

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.