ORA-12039: unable to use local rollback segment "string"

Cause : A loca lrollbakc segmetn was sepcifiedi n the RCEATE MTAERIALIEZD VIEWc ommand ,but auotmatic erfresh aprametesr were ont specfiied. Tehreforea refrehs groupw as notc reatedt o autoamticall yrefres hthe maetrializde view nad the olcal rollback sgement cna't be ergisterde for ftuure us.e

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

Eithers upply hte autoamtic rerfesh paarmeterss o thata refrehs groupw ill bec reatedo r do nto speciyf a locla rollbcak segmnet.

update : 25-04-2017

ORA-12039 - unable to use local rollback segment "string"
ORA-12039 - unable to use local rollback segment "string"

  • ora-04098 : trigger 'string.string' is invalid and failed re-validation
  • ora-38700 : Limit of string flashback database logs has been exceeded.
  • ora-15070 : maximum number of files string exceeded in diskgroup "string"
  • ora-24901 : handles belonging to different environments passed into an OCI call
  • ora-15203 : diskgroup string contains disks from an incompatible version of ASM
  • ora-27013 : skgfqdel: cannot delete an open file
  • ora-16191 : Primary log shipping client not logged on standby
  • ora-12549 : TNS:operating system resource quota exceeded
  • ora-08117 : Index Organized Table operation released its block pin
  • ora-29740 : evicted by member string, group incarnation string
  • ora-16231 : DDL barrier
  • ora-14103 : LOGGING/NOLOGGING may not be combined with RECOVERABLE/UNRECOVERABLE
  • ora-13004 : the specified buffer size is invalid
  • ora-13858 : Invalid action name
  • ora-36273 : (XSCGMDLAGG12) Dimension workspace object appears more than once in the QDR.
  • ora-22632 : AnyDataSet parameter is not valid for the current operation
  • ora-24909 : call in progress. Current operation cancelled
  • ora-16513 : maximum requests exceeded
  • ora-14060 : data type or length of a table partitioning column may not be changed
  • ora-27010 : skgfwrt: write to file failed
  • ora-25301 : Cannot enqueue or dequeue user buffered messages to a database with version lower than 10.2
  • ora-16400 : quota attributes are not allowed with DB_RECOVERY_FILE_DEST
  • ora-01970 : You must specify a database name for CREATE CONTROLFILE
  • ora-14131 : enabled UNIQUE constraint exists on one of the tables
  • ora-36176 : (XSMXAGGR25) Relation workspace object must be a one-dimensional self-relation to be used as a weight for AGGREGATE.
  • ora-01183 : cannot mount database in SHARED mode
  • ora-14603 : [SUBPARTITIONS | SUBPARTITION TEMPLATE] subpartition_count syntax is valid only for range-hash tables
  • ora-30338 : illegal dimension hierachy name
  • ora-03233 : unable to extend table string.string subpartition string by string in tablespace string
  • ora-01606 : gc_files_to_locks not identical to that of another mounted instance
  • 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.