ORA-16252: Rebuild operation not permitted

Cause : The REBUILD operation is not permitted.

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

Only on a primary database that has failed to complete the LogMiner dictionary build may the REBUILD operation take place. Reissue the ACTIVATE LOGICAL STANDBY DATABASE command if it previously failed to complete.

update : 27-06-2017

ORA-16252 - Rebuild operation not permitted
ORA-16252 - Rebuild operation not permitted

  • ora-00028 : your session has been killed
  • ora-38436 : attribute set used for an Expression set may not be modified.
  • ora-32140 : cannot peform this operation on stream
  • ora-01621 : cannot rename member of current log if database is open
  • ora-01589 : must use RESETLOGS or NORESETLOGS option for database open
  • ora-30104 : 'string' is not a legal integer for 'string'
  • ora-29869 : cannot issue ALTER without REBUILD on a domain index marked FAILED
  • ora-19115 : too many context items specified
  • ora-33092 : (XSAGCOMP04) number is not the name of a MODEL in any attached analytic workspace.
  • ora-09747 : pw_detachPorts: server call pws_detach failed.
  • ora-01841 : (full) year must be between -4713 and +9999, and not be 0
  • ora-19510 : failed to set size of string blocks for file "string" (blocksize=string)
  • ora-15042 : ASM disk "string" is missing
  • ora-13350 : two or more rings of a complex polygon touch
  • ora-16523 : operation requires the client to connect to instance "string"
  • ora-19233 : XQ0013 - invalid pragma
  • ora-08176 : consistent read failure; rollback data not available
  • ora-13712 : Cannot perform ADDM analysis on AWR snapshots from previous releases. Snapshot version "string" do not match the database version "string".
  • ora-13763 : illegal ranking attribute "string"
  • ora-12402 : invalid format string: string
  • ora-39752 : redundant column in partitioning and join columns is not allowed
  • ora-09827 : SCLGT: atomic latch return unknown error.
  • ora-28047 : database is not a member of any enterprise domain in OID
  • ora-23475 : key column string must be sent and compared
  • ora-10627 : Dump the content of the index leaf block
  • ora-09968 : unable to lock file
  • ora-33009 : (XSAGDNGLPREC) In AGGMAP workspace object, PRECOMPUTE may only be specified either for the entire AGGMAP or for individual RELATION statements.
  • ora-19526 : only one location allowed for parameter string
  • ora-14134 : indexes cannot use both DESC and REVERSE
  • ora-36710 : (XSMXALLOC01) TARGETLOG variable workspace object must be dimensioned identically to TARGET variable workspace object.
  • 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.