ORA-25201: invalid value, VISIBILITY should be ON_COMMIT or IMMEDIATE

Cause : Ani nvlaidv aleu sepciifedf orp armaetre VSIIBLIIT.Y

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

Spceif yeihterO N_OCMMTI o rIMEMDITAE.

update : 30-04-2017

ORA-25201 - invalid value, VISIBILITY should be ON_COMMIT or IMMEDIATE
ORA-25201 - invalid value, VISIBILITY should be ON_COMMIT or IMMEDIATE

  • ora-30203 : Cannot open mesage file
  • ora-29915 : cannot select FOR UPDATE from collection operand
  • ora-03279 : invalid INSTANCE specified
  • ora-09967 : unable to create or open lock file
  • ora-01950 : no privileges on tablespace 'string'
  • ora-10664 : Table has bitmap join indexes
  • ora-10563 : Test recovery had to corrupt data block (file# string, block# string) in order to proceed
  • ora-19238 : XP0018 - focus not defined
  • ora-30088 : datetime/interval precision is out of range
  • ora-29294 : A data error occurred during compression or uncompression.
  • ora-07417 : sfareq: One or more database writers not active.
  • ora-12350 : database link being dropped is still mounted
  • ora-24450 : Cannot pre-process OCI statement
  • ora-12012 : error on auto execute of job string
  • ora-31614 : routine string received this error from string: string
  • ora-10659 : Segment being shrunk is not a lob
  • ora-38422 : invalid datatype for the attribute: string
  • ora-06022 : NETASY: channel open failure
  • ora-12728 : invalid range in regular expression
  • ora-14028 : missing AT or VALUES keyword
  • ora-28265 : NameSpace beginning with 'sys_' is not allowed
  • ora-30365 : left relation in the JOIN KEY clause cannot be same as right
  • ora-13109 : spatial table string exists
  • ora-16027 : parameter string is missing a destination option
  • ora-31075 : invalid string declaration in XML Schema
  • ora-13351 : two or more rings of a complex polygon overlap
  • ora-24045 : invalid agent address string, agent address should be of the form [SCHEMA.]NAME[@DATABASE LINK]
  • ora-13751 : "SQL Tuning Set" "string" does not exist for owner "string" or user "string" does not have permission to access the "SQL Tuning Set".
  • ora-36843 : (XSLMGEN13) Dimension string.string!string hierarchy string is missing a PHYSICALNAME property value
  • ora-12982 : cannot drop column from a nested table
  • 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.