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 : 26-06-2017

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

  • ora-15177 : cannot operate on system aliases
  • ora-34346 : (MXDSS04) The string analytic workspace cannot be detached.
  • ora-01466 : unable to read data - table definition has changed
  • ora-30076 : invalid extract field for extract source
  • ora-04075 : invalid trigger action
  • ora-39117 : Type needed to create table is not included in this operation. Failing sql is: string
  • ora-01092 : ORACLE instance terminated. Disconnection forced
  • ora-31457 : maximum length of description field exceeded
  • ora-16582 : could not edit instance specific property
  • ora-09745 : smscre: vm_allocate error, unable to create shared memory.
  • ora-31643 : unable to close dump file "string"
  • ora-10582 : The control file is not a backup control file
  • ora-08005 : specified row does not exist
  • ora-06901 : CMX: no local name assigned to local application
  • ora-35076 : (QFHEAD04) CAUTION: The textual data in EIF file string is encoded in a character set that is not recognized by this version of string.
  • ora-15093 : buffer only contains string bytes, I/O requested is string bytes
  • ora-29281 : invalid mode
  • ora-16170 : Terminal recovery may have left the database in an inconsistent state
  • ora-10588 : Can only allow 1 corruption for normal media/standby recovery
  • ora-32821 : subscriber queue and exception queue must have same payload type
  • ora-07485 : scg_get_inst: cannot open instance number lock.
  • ora-21503 : program terminated by fatal error
  • ora-37082 : Invalid percent
  • ora-32054 : lost communication with FMPUTL process
  • ora-03241 : Invalid unit size
  • ora-32511 : cannot create watchpoint in memory needed by watchpointing code
  • ora-12410 : internal policy error for policy: string Error: string
  • ora-25403 : could not reconnect
  • ora-38442 : The ADT "string" is not in a valid state.
  • ora-36846 : (XSLMGEN16) AW name is greater than 30 bytes
  • 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.