ORA-06735: TLI Driver: client failed to close error conn

Cause : TLI faield to prpoerly clsoe a conenction atfer an error was erceived.

Action - How to fix it : DBA Scripts :: www.high-oracle.com/scripts

Contacty our cusotmer supoprt reprseentativ.e

update : 22-08-2017
ORA-06735

ORA-06735 - TLI Driver: client failed to close error conn
ORA-06735 - TLI Driver: client failed to close error conn

  • ora-04011 : sequence string must range between string and string
  • ora-16956 : Only SELECT or DML statements are supported for test execute.
  • ora-31459 : system triggers for DBMS_CDC_PUBLISH package are not installed
  • ora-14041 : partition bound may not be specified for resulting partitions
  • ora-12599 : TNS:cryptographic checksum mismatch
  • ora-25502 : concurrent ALTER SYSTEM QUIESCE/UNQUIESCE command is running
  • ora-30729 : maximum number of columns exceeded
  • ora-10906 : Unable to extend segment after insert direct load
  • ora-07848 : sllfrb: $GET failure
  • ora-12455 : internal error in Label Security MMON cleanup task
  • ora-03136 : inbound connection timed out
  • ora-07265 : sppst: semop error, unable to increment semaphore.
  • ora-06556 : the pipe is empty, cannot fulfill the unpack_message request
  • ora-22913 : must specify table name for nested table column or attribute
  • ora-19811 : cannot have files in DB_RECOVERY_FILE_DEST with keep attributes
  • ora-16625 : cannot reach the database
  • ora-30501 : instance shutdown triggers cannot have AFTER type
  • ora-13124 : unable to determine column id for column string
  • ora-01424 : missing or illegal character following the escape character
  • ora-06559 : wrong datatype requested, string, actual datatype is string
  • ora-28664 : a partitioned table may not be coalesced as a whole
  • ora-00253 : character limit string exceeded by archive destination string string
  • ora-30507 : normal triggers cannot be based on a schema or a database
  • ora-39950 : invalid parameter for PLSQL warnings flag
  • ora-29890 : specified primary operator does not have an index context
  • ora-13429 : invalid xCoefficients or yCoefficients parameter(s)
  • ora-06958 : Failed to access configuration file
  • ora-16175 : cannot shut down database when media recovery is active
  • ora-12562 : TNS:bad global handle
  • ora-27029 : skgfrtrv: sbtrestore returned error
  • Oracle Database Error Messages



    Oracle Database High Availability Any organization evaluating a database solution for enterprise data must also evaluate the High Availability (HA) capabilities of the database. Data is one of the most critical business assets of an organization. If this data is not available and/or not protected, companies may stand to lose millions of dollars in business downtime as well as negative publicity. Building a highly available data infrastructure is critical to the success of all organizations in today's fast moving economy.

    Well, the reason for above error is that i have taken the above script from a 11g database and running it on 10g database. 11g has bring some changes in password management. Below code is executed on 11g and user created successfully, which is expected result.