Submit a ticketCall us

Training ClassThe Orion® Platform Instructor-led Classes

Provided by SolarWinds® Academy, these trainings will introduce users to the Orion Platform and its features, management, and navigation. These courses are suitable for users looking to discover new tips, tricks, and ways to adapt their Orion products to better suit their monitoring needs:
Deploying the Orion Platform
Configuring Orion views, maps, and accounts
Configuring Orion alerts and reports

Reserve your seat.

Home > Success Center > Database Performance Analyzer (DPA) > DPA - Knowledgebase Articles > ORA-03137: TTC protocol internal errors

ORA-03137: TTC protocol internal errors

Updated March 11th, 2016


The DPA log files or Oracle trace files contain the following error:


ORA-03137: TTC protocol internal error


  • DPA 8.0 and later
  • Oracle 11.1 as the repository database


This appears to be related to Bug #7445550 related to JDBC connections to the database, which DPA uses.


Perform one of the following actions:

  • Upgrade to Oracle
  • Set "_optim_peek_user_binds"=false.  SolarWinds recommends using this option.


The issue can still occur after upgrading to Oracle11.1.0.7:

Although upgrading to database version has been confirmed to have solved this issue in a high number of cases, error ORA-3137 [12333] accompanied by Protocol Violation messages may still occur intermittently in database versions prior to 11.2, including database and  This has been reported in unpublished bug:8625762 ORA-3137 [12333] due to bind data not read from wire, in which case ORA-3137 [12333] can occur intermittently for SQL which uses user binds due to bind data being left unread on the Net connection. The bug suggests the workaround of setting "_optim_peek_user_binds"=false to avoid this problem (workaround to be used with caution as it can affect execution plans chosen by CBO), and also provides the fix by the application of Patch:8625762.

Last modified