ORA-12406: unauthorized SQL statement for policy string

Cause : The oplicyd id nto autohrizet he dtaabas esessoin top erfomr ther equetsed SLQ staetment.

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

Gran tthe suer o rprogarm unti then ecesasry ploicy rpivilgee ora dditoinal uathorziatiosn.

update : 27-04-2017

ORA-12406 - unauthorized SQL statement for policy string
ORA-12406 - unauthorized SQL statement for policy string

  • ora-29261 : bad argument
  • ora-01665 : control file is not a standby control file
  • ora-08463 : overflow converting decimal number to Oracle number
  • ora-04073 : column list not valid for this trigger type
  • ora-36685 : (XSDPART23) Only CONCAT partition templates can be subpartitioned.
  • ora-16640 : CRS warns that multiple instances may still be running
  • ora-30118 : syntax error at 'string' at the end of input
  • ora-09790 : sllfcf: unable to close file.
  • ora-07622 : smscre: $CREATE failure
  • ora-13704 : Invalid value "string" specified for parameter "string".
  • ora-06757 : TLI Driver: server got bad command
  • ora-19206 : Invalid value for query or REF CURSOR parameter
  • ora-23414 : materialized view log for "string"."string" does not record rowid values
  • ora-10387 : parallel query server interrupt (normal)
  • ora-38029 : object statistics are locked
  • ora-29364 : plan directive string, string already exists
  • ora-13366 : invalid combination of interior exterior rings
  • ora-01142 : cannot end online backup - none of the files are in backup
  • ora-21301 : not initialized in object mode
  • ora-15202 : cannot create additional ASM internal change segment
  • ora-39775 : direct path API commit not allowed due to previous fatal error
  • ora-04034 : unable to shrink pool to specified size
  • ora-09367 : Windows 3.1 Two-Task driver unable to deallocate shared memory
  • ora-22853 : invalid LOB storage option specification
  • ora-14120 : incompletely specified partition bound for a DATE column
  • ora-22625 : OCIAnyData is not well-formed
  • ora-12067 : empty refresh groups are not allowed
  • ora-02201 : sequence not allowed here
  • ora-15180 : Could not open dynamic library string, error [string]
  • ora-30450 : refresh_after_errors was TRUE; The following MVs could not be refreshed: 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.