ORA-09914: Unable to open the ORACLE password file.

Cause : ORACLE could not open the password file for reading.

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

Check the UNIX error number. If the error number indicates that the file does not exist, have the database administrator create the file by running orapasswd. If the error number indicates insufficient permissions, ask the database administrator to change the permissions. Otherwise, contact ORACLE customer support.

update : 24-08-2017

ORA-09914 - Unable to open the ORACLE password file.
ORA-09914 - Unable to open the ORACLE password file.

  • ora-08102 : index key not found, obj# string, file string, block string (string)
  • ora-07707 : error in archive text: need tape label name
  • ora-14063 : Unusable index exists on unique/primary constraint key
  • ora-25250 : Cannot specify a remote recipient for the message
  • ora-24375 : Cannot use V6 syntax when talking to a V8 server
  • ora-16250 : Failed to acquire starting scn of new log stream
  • ora-12737 : Instant Client Light: unsupported server character set string
  • ora-27477 : "string.string" already exists
  • ora-23316 : the masterdef is string
  • ora-16557 : the database is already in use
  • ora-31622 : ORACLE server does not have string access to the specified file
  • ora-25283 : either agent's name or address needed for non-repudiation
  • ora-16122 : applying large dml transaction at SCN string
  • ora-27484 : Argument names are not supported for jobs without a program.
  • ora-16599 : Data Guard broker detected a stale configuration
  • ora-09846 : soacon: ARCH unable to open named pipe.
  • ora-04097 : DDL conflict while trying to drop or alter a trigger
  • ora-16532 : Data Guard broker configuration does not exist
  • ora-22311 : type for attribute "string" does not exist
  • ora-26524 : nls subsystem initialization failure for product=string, facility=string
  • ora-32126 : Cannot perform operations on a null REF
  • ora-31042 : Too many properties in type 'string'
  • ora-39095 : Dump file space has been exhausted: Unable to allocate string bytes
  • ora-12685 : Native service required remotely but disabled locally
  • ora-27211 : Failed to load Media Management Library
  • ora-14301 : table-level attributes must be specified before partition-level attributes
  • ora-03254 : unable to execute the sql in read only database
  • ora-39959 : invalid warning number (string)
  • ora-09770 : pws_look_up: translation failure.
  • ora-39099 : cannot create index for "string" on master table string
  • 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.