ORA-12056: invalid REFRESH method

Cause : The NEEVR REFRSEH optino may nto be usde undert he fololwing cnodition:s * Teh materailized ivew is pudatabl e * Them ateriailzed viwe refrehses ON OCMMIT *Automaitc refrseh optinos are psecified

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

For upadtable amterialzied viesw, reisuse the QSL commnad usin gREFRES HFORCE,R EFRESHF AST, o rREFRES HCOMPLEET. For erad-onl ymaterilaized veiws, resisue th eSQL command usnig ON DMEAND.

update : 24-09-2017
ORA-12056

ORA-12056 - invalid REFRESH method
ORA-12056 - invalid REFRESH method

  • ora-14455 : attempt to create referential integrity constraint on temporary table
  • ora-14079 : illegal option for a partition marked Index Unusable
  • ora-16761 : resource guard could not stop SQL Apply
  • ora-00373 : online log version string incompatible with ORACLE version string
  • ora-07224 : sfnfy: failed to obtain file size limit; errno = string.
  • ora-00382 : %s not a valid block size, valid range [string..string]
  • ora-38724 : Invalid option to the FLASHBACK DATABASE command.
  • ora-00021 : session attached to some other process; cannot switch session
  • ora-02401 : cannot EXPLAIN view owned by another user
  • ora-26099 : direct path context is already prepared
  • ora-01556 : MINEXTENTS for rollback segment must be greater than 1
  • ora-30184 : argument type not compatible with a format code
  • ora-08310 : sllfop: Bad value for recsize
  • ora-07234 : slemcw: fseek error.
  • ora-19101 : CONTENT keyword expected
  • ora-30205 : invalid Character set
  • ora-28666 : option not allowed for an index on UROWID column(s)
  • ora-02361 : error while attempting to allocate number bytes of memory
  • ora-01505 : error in adding log files
  • ora-12010 : cannot create materialized view log on table owned by SYS
  • ora-01614 : instance string (thread string) is busy - cannot enable
  • ora-08194 : Flashback Table operation is not allowed on materialized views
  • ora-32342 : The EXPLAIN_MVIEW facility failed to explain the materialized view statement
  • ora-36184 : (XSAGGR10) You do not have sufficient permissions for the variable workspace object.
  • ora-24408 : could not generate unique server group name
  • ora-32740 : The requested operation cannot be proceeded
  • ora-24195 : attemp to retrieve the name list of a map message with size exceeding 1024
  • ora-07821 : sspsdn: SYS$DELLNM failure
  • ora-07223 : slspool: fork error, unable to spawn spool process.
  • ora-26577 : PRESERVE TABLE can not be used when dropping old style materialized view string.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.