ORA-09944: Password entry is corrupt.

Cause : An entry in an ORACLE password file was not in the format that ORACLE expected.

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

Removed the corrupt file(s) and re-run "orapasswd."

update : 29-06-2017

ORA-09944 - Password entry is corrupt.
ORA-09944 - Password entry is corrupt.

  • ora-00991 : only MAC privileges may be granted to procedures
  • ora-32300 : cannot drop a secondary materialized view "string"."string"
  • ora-23300 : %s
  • ora-19024 : Cursor expression must be named
  • ora-14041 : partition bound may not be specified for resulting partitions
  • ora-38755 : Flashback is already turned on for this tablespace.
  • ora-25014 : cannot change the value of a PARENT reference variable
  • ora-38860 : cannot FLASHBACK DATABASE during instantiation of a logical standby
  • ora-07562 : sldext: extension must be 3 characters
  • ora-04082 : NEW or OLD references not allowed in table level triggers
  • ora-40251 : no support vectors were found
  • ora-16094 : database shutdown during archival operation
  • ora-10587 : Invalid count for ALLOW n CORRUPTION option
  • ora-26761 : Standby Redo Logs not available for real time mining
  • ora-39769 : finish is not allowed with an incompletely loaded last row
  • ora-02804 : Allocation of memory failed for log file name
  • ora-09292 : sksabln: unable to build archive file name
  • ora-19244 : XQ0024 - invalid attribute node in element constructor
  • ora-00228 : length of alternate control file name exceeds maximum of string
  • ora-02158 : invalid CREATE INDEX option
  • ora-13917 : Posting system alert with reason_id string failed with code [string] [string]
  • ora-09213 : slgfn: error fabricating file name
  • ora-06021 : NETASY: connect failed
  • ora-02734 : osnftt: cannot reset shared memory permission
  • ora-24053 : PRIMARY_INSTANCE and SECONDARY_INSTANCE must be non-negative
  • ora-09916 : Required password was not specified.
  • ora-16088 : archive log has not been completely archived
  • ora-33413 : (EIFMAKEF01) You cannot export compressed composite workspace object because one of its bases has limited status or a PERMIT READ restriction.
  • ora-14080 : partition cannot be split along the specified high bound
  • ora-32772 : BIGFILE is invalid option for this type of tablespace
  • 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.