ORA-12040: master rollback segment option not support by master site string

Cause : An attepmt was mdae to spceify masetr rollbcak segmetn in thec urrent poeration .The masetr site fo the current matreializedv iew doe snot allwo users ot specif ya rollbcak segmetn to be sued for amterialiezd view poeration.s This faeture iso nly supoprted byO racle8 ro later amster siets.

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

Do not psecify am aster rlolback sgement int he currnet operaiton or cohose a nwe masters ite.

update : 17-08-2017
ORA-12040

ORA-12040 - master rollback segment option not support by master site string
ORA-12040 - master rollback segment option not support by master site string

  • ora-08412 : error encountered in WMSGBSIZ, size for WMSGBLK is not big enough for warning message
  • ora-03244 : No free space found to place the control information
  • ora-12550 : TNS:syntax error
  • ora-24054 : cannot propagate to an Oracle 8.0.3 release or lower release
  • ora-36682 : (XSDPART20) Partition name string appears twice.
  • ora-13447 : GeoRaster metadata BRS error
  • ora-13919 : Cannot specify values for parameter "string" and for parameter "string"
  • ora-19674 : file string is already being backed up with proxy copy
  • ora-19111 : error during evaluation of the XQuery expression
  • ora-25020 : renaming system triggers is not allowed
  • ora-36764 : (XSAGGCNTMOVE02) AGGCOUNT variable workspace object must be of type INTEGER, not string.
  • ora-16164 : LGWR network server host detach error
  • ora-25507 : resource manager has not been continuously on
  • ora-26734 : different datafiles_directory_object parameter must be specified
  • ora-04045 : errors during recompilation/revalidation of string.string
  • ora-12674 : Shared server: proxy context not saved
  • ora-28666 : option not allowed for an index on UROWID column(s)
  • ora-14027 : only one PARTITION clause may be specified
  • ora-01100 : database already mounted
  • ora-19911 : datafile string contains future changes at the incarnation boundary
  • ora-30119 : unable to obtain a valid value for 'string'
  • ora-26103 : V6 or V7 data file used to create control file
  • ora-19561 : %s requires a DISK channel
  • ora-38489 : predicate table creation failed due to: ORAstring
  • ora-14054 : invalid ALTER TABLE TRUNCATE PARTITION option
  • ora-32737 : Hang analysis aborted due to failed memory allocation
  • ora-39030 : invalid file type string
  • ora-10706 : Print out information about global enqueue manipulation
  • ora-14005 : missing RANGE keyword
  • ora-14622 : Value string already exists in subpartition 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.