ORA-00600 and user identified by values ”

With rel. 10.2.0.5 was possibile to do this:

With 11.2.0.3 an ORA-00600 is raised.

The following two tabs change content below.

Ludovico

Oracle ACE Director and Computing Engineer at CERN
Ludovico is an Oracle ACE Director, frequent speaker and community contributor, working as Computing Engineer at CERN, the European Organization for Nuclear Research, in Switzerland.

One thought on “ORA-00600 and user identified by values ”

  1. You can look this note oracle ID 554605.1 :

    ORA-600 [kzsviver:1] Error On Setting Users’ Passwords [ID 554605.1]
    Modified 20-SEP-2010 Type PROBLEM Status PUBLISHED

    In this Document
    Symptoms
    Changes
    Cause
    Solution
    References

    Applies to:
    Oracle Server – Enterprise Edition – Version: 11.1.0.6 and later [Release: 11.1 and later ]
    Information in this document applies to any platform.
    Checked for relevance on 20-Sep-2010
    Symptoms
    ORA-600 [kzsviver:1] possibly followed by ORA-600 [kks-hash-collision] errors can occur when trying to set a users password via SQL or PL/SQL scripts using the “CREATE/ALTER USER … IDENTIFIED BY VALUES …” command syntax if a null password value, e.g. an empty string ”, is used.
    Changes
    The code is being executed in Oracle11g, and works successfully in previous releases.
    Cause
    This is due to unpublished bug:6755379 as identified in bug:6833049, and was deemed as expected behaviour by development due to the use of unsupported command syntax as the use of the ‘IDENTIFIED BY VALUES’ clause on a CREATE/ALTER USER statement is not officially documented, and is intended purely for internal use by the export/import utilities within the Oracle RDBMS. Therefore it was deemed appropriate for this to raise an internal error as opposed to a user error as encountering a null password string would otherwise not be possible.

    Additionally the use of export/import for general use is desupported in Oracle11g.
    Solution
    Ensure that users have none null passwords defined and don’t use the “ALTER USER … IDENTIFIED BY VALUES …” command syntax which is not officially documented and therefore not supported, and may cease to work in a future Oracle RDBMS version.

    In 11g, the new hash value is stored in the USER$.SPARE4 column, see note 429465.1, if existing passwords must be migrated, make sure to make no errors in transferring this value to avoid this internal error.

    References
    BUG:6833049 – ORA-600 [KZSVIVER:1] AND ORA-600 [KKS-HASH-COLLISION] CHANGING PASSWORDS
    NOTE:1051962.101 – Restoring a user’s original password
    NOTE:429465.1 – 11g R1 New Feature : Case Sensitive Passwords and Strong User Authentication

    Show Related Information Related
    Products

    Oracle Database Products > Oracle Database > Oracle Database > Oracle Server – Enterprise Edition

    Keywords
    UTILITY; IMPORT UTILITY
    Errors
    ORA-600[KZSVIVER; 1]; ORA-600[KKS-HASH-COLLISION]

Leave a Reply

Your email address will not be published. Required fields are marked *

This site uses Akismet to reduce spam. Learn how your comment data is processed.