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 : 24-05-2017

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

  • ora-30017 : segment 'string' is not supported in string Undo Management mode
  • ora-31499 : null value specified for required parameter string
  • ora-29291 : file remove operation failed
  • ora-31415 : change set string does not exist
  • ora-36692 : (XSRELTBL00) The format of the HIERHEIGHT command is: HIERHEIGHT relation1[(dimension dimvalue, ...)] into relation2 [using relation3 | a | d] [levelorder lovs] [inhierarchy {variable | valueset}].
  • ora-30930 : NOCYCLE keyword is required with CONNECT_BY_ISCYCLE pseudocolumn
  • ora-02047 : cannot join the distributed transaction in progress
  • ora-09926 : Unable to set effective privilege set of the server
  • ora-14302 : only one list of added-LOB-storage-clauses can be specified in a statement
  • ora-16599 : Data Guard broker detected a stale configuration
  • ora-28171 : unsupported Kerberos version
  • ora-12472 : policy string is being used
  • ora-12229 : TNS:Interchange has no more free connections
  • ora-09787 : sllfop: unrecognizable processing option, incorrect format.
  • ora-01168 : physical block size string does not match size string of other members
  • ora-06400 : NETCMN: No default host string specified
  • ora-00305 : log string of thread string inconsistent; belongs to another database
  • ora-00271 : there are no logs that need archiving
  • ora-01968 : Only specify RESETLOGS or NORESETLOGS once
  • ora-16566 : unsupported document type
  • ora-37171 : dimension sources not specified
  • ora-10926 : trace name context forever
  • ora-09951 : Unable to create file
  • ora-02815 : Unable to attach shared memory
  • ora-13116 : [string]_FACE$ table does not exist
  • ora-30556 : functional index is defined on the column to be modified
  • ora-26088 : scalar column "string" must be specified prior to LOB columns
  • ora-26095 : unprocessed stream data exists
  • ora-31461 : logfile location string contains no files that match pattern string
  • ora-01621 : cannot rename member of current log if database is open
  • 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.