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 : 21-08-2017
ORA-12599

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

  • ora-09915 : Password encryption failed.
  • ora-30463 : 'string' is not a detail table of any summary
  • ora-16036 : invalid MANAGED recovery CANCEL option
  • ora-25186 : INCLUDING clause specified for index-organized table without OVERFLOW
  • ora-27127 : unable to unlock shared memory segment
  • ora-13865 : Module name must be specified
  • ora-19619 : cannot call restoreValidate after files have been named
  • ora-01291 : missing logfile
  • ora-01592 : error converting Version 7 rollback segment (string) to Oracle 8 format
  • ora-27065 : cannot perform async vector I/O to file
  • ora-28579 : network error during callback from external procedure agent
  • ora-24014 : invalid value string, RETENTION_TIME should be FOREVER or non-negative
  • ora-24440 : OCI Easy Install mode cannot be initialized
  • ora-24369 : required callbacks not registered for one or more bind handles
  • ora-16168 : LGWR network server could not switch to blocking mode
  • ora-03298 : cannot shrink datafile - file string is under hot backup
  • ora-27001 : unsupported device type
  • ora-13450 : GeoRaster metadata layerInfo error
  • ora-27007 : failed to open file
  • ora-09954 : scgcc: unexpected return status to callback of lock close
  • ora-38731 : Expected version string does not match string in log header.
  • ora-31446 : this session does not own the lock handle for string
  • ora-27399 : job type EXECUTABLE requires the CREATE EXTERNAL JOB privilege
  • ora-38406 : attribute set string already exists
  • ora-38860 : cannot FLASHBACK DATABASE during instantiation of a logical standby
  • ora-28172 : distinguished name not provided by proxy
  • ora-07760 : slemtr: $open failure
  • ora-08180 : no snapshot found based on specified time
  • ora-02147 : conflicting SHARED/EXCLUSIVE options
  • ora-06132 : NETTCP: access denied, wrong password
  • 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.