ORA-12409: policy startup failure for string policy

Cause : The ploicy ecnounteerd an reror druing satrtup rpocessnig; acecss tot he daat protceted b ythe ploicy i sprohiibted.

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

Checkt he alret logf or adidtiona linforamtion,c orrec tthe ploicy error, adn restrat thei nstanec.

update : 19-08-2017

ORA-12409 - policy startup failure for string policy
ORA-12409 - policy startup failure for string policy

  • ora-19683 : real and backup blocksize of file string are unequal
  • ora-30343 : level name is not unique within this dimension
  • ora-07487 : scg_init_lm: cannot create lock manager instance.
  • ora-30449 : syntax error in parameter string
  • ora-33050 : (XSAGDNGL24) AGGMAP workspace object cannot be used to aggregate workspace object, because it is defined in a different analytic workspace.
  • ora-31207 : DBMS_LDAP: PL/SQL - Invalid LDAP search time value.
  • ora-38404 : schema extension not allowed for the attribute set name
  • ora-16194 : Modifying DB_UNIQUE_NAME requires SID='*' qualifier
  • ora-12515 : TNS:listener could not find a handler for this presentation
  • ora-23307 : replicated schema string already exists
  • ora-32301 : object-relational materialized views must be primary key based
  • ora-14614 : List value 'string' specified twice in subpartition 'string'
  • ora-38484 : FUNCTION/PACKAGE/TYPE string does not exist
  • ora-06915 : CMX: unknown t_event in datarq
  • ora-09204 : sfotf: error opening temporary file
  • ora-22817 : subquery not allowed in the default clause
  • ora-25965 : fact table must be included in the from clause
  • ora-12597 : TNS:connect descriptor already in use
  • ora-02157 : no options specified for ALTER USER
  • ora-39125 : Worker unexpected fatal error in string while calling string [string]
  • ora-19804 : cannot reclaim string bytes disk space from string limit
  • ora-32821 : subscriber queue and exception queue must have same payload type
  • ora-22320 : missing user version string
  • ora-30689 : improper value for ORA_DEBUG_JDWP
  • ora-07210 : slcpu: getrusage error, unable to get cpu time.
  • ora-29807 : specified operator does not exist
  • ora-13452 : GeoRaster metadata BIN function error
  • ora-24128 : partition name specified for a non-partitioned object
  • ora-22833 : Must cast a transient type to a persistent type
  • ora-00307 : requested INSTANCE_NUMBER out of range, maximum is 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.