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 : 25-04-2017
ORA-12599

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

  • ora-39056 : invalid log file specification.
  • ora-13901 : Object string was not found.
  • ora-19677 : RMAN configuration name exceeds maximum length of string
  • ora-32837 : invalid configuration state string
  • ora-23478 : object group "string" is already mastered at string
  • ora-12002 : there is no materialized view log on table "string"."string"
  • ora-23617 : Block string for script string has already been executed
  • ora-36698 : (XSRELTBL03) QDR dimension workspace object should be in the dimension list that dimensions the relation.
  • ora-02288 : invalid OPEN mode
  • ora-25400 : must replay fetch
  • ora-02147 : conflicting SHARED/EXCLUSIVE options
  • ora-22927 : invalid LOB locator specified
  • ora-30748 : column string already enabled to store objects of type string.string
  • ora-02279 : duplicate or conflicting MINVALUE/NOMINVALUE specifications
  • ora-32331 : type "string"."string" is incompatible with the master site
  • ora-01211 : Oracle7 data file is not from migration to Oracle8
  • ora-07203 : sltln: attempt to translate a long environment variable.
  • ora-12084 : must use ALTER MATERIALIZED VIEW to alter "string"."string"
  • ora-00328 : archived log ends at change string, need later change string
  • ora-32050 : %s operation failed
  • ora-01757 : Must specify an object number
  • ora-25147 : UNIFORM SIZE value greater than maximum extent size
  • ora-08233 : smsdes: cannot unmap SGA
  • ora-29958 : fatal error occurred in the execution of ODCIINDEXCREATE routine
  • ora-37082 : Invalid percent
  • ora-27513 : parameter string contains invalid value string
  • ora-10926 : trace name context forever
  • ora-14456 : cannot rebuild index on a temporary table
  • ora-27417 : BYWEEKNO clause is only supported when FREQ=YEARLY
  • ora-31649 : Master process string violated startup protocol.
  • 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.