ORA-12599: TNS:cryptographic checksum mismatch

Cause : The data received is not the same as the data sent.

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

Attempt the transaction again. If error persists, check (and correct) the integrity of your physical connection.

update : 26-05-2017
ORA-12599

ORA-12599 - TNS:cryptographic checksum mismatch
ORA-12599 - TNS:cryptographic checksum mismatch

  • ora-16543 : invalid request made to broker
  • ora-00080 : invalid global area specified by level string
  • ora-16253 : Logical Standby cannot start due to incomplete terminal apply
  • ora-25154 : column part of USING clause cannot have qualifier
  • ora-23536 : the object "string"."string" is not cached at the middle tier as expected.
  • ora-28183 : proper authentication not provided by proxy
  • ora-06133 : NETTCP: file not found
  • ora-08311 : sllfop: bad value for maxrecsize
  • ora-30929 : ORDER SIBLINGS BY clause not allowed here
  • ora-06110 : NETTCP: message send failure
  • ora-24275 : function 'string' parameter 'string' missing or invalid
  • ora-06917 : CMX: error in data read (too many bytes read)
  • ora-32310 : object materialized views must select from an object table
  • ora-31434 : purge is currently running
  • ora-06423 : NETCMN: Error in receiving data
  • ora-02381 : cannot drop PUBLIC_DEFAULT profile
  • ora-38951 : Target platform string not cross platform compliant
  • ora-36628 : (XSAGMODLIST03) MODEL workspace object could not be added to AGGMAP workspace object.
  • ora-36820 : (XSLMINFO00) The LIMITMAPINFO function encountered an error while parsing the LIMITMAP.
  • ora-25261 : JOB_QUEUE_PROCESSES must be at least 2 for AQ propagation
  • ora-06707 : TLI Driver: connection failed
  • ora-08106 : cannot create journal table string.string
  • ora-16509 : the request timed out
  • ora-12651 : Encryption or data integrity algorithm unacceptable
  • ora-40271 : no statistically significant features were found
  • ora-02445 : Exceptions table not found
  • ora-02310 : exceeded maximum number of allowable columns in table
  • ora-23411 : materialized view "string"."string" is not in refresh group "string"."string"
  • ora-01905 : STORAGE keyword expected
  • ora-26095 : unprocessed stream data exists
  • 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.