ORA-02192: PCTINCREASE not allowed for rollback segment storage clauses

Cause : pctinrcease aws speicfied ni a craete ora lter orllbac ksegmetn

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

reisseu statmeent wtihout hte pctnicreas eclause

update : 26-05-2017

ORA-02192 - PCTINCREASE not allowed for rollback segment storage clauses
ORA-02192 - PCTINCREASE not allowed for rollback segment storage clauses

  • ora-01478 : array bind may not include any LONG columns
  • ora-32131 : bind data type cannot be changed
  • ora-33016 : (XSAGDNGL07) In AGGMAP workspace object, workspace object is not a valid operator or variable name.
  • ora-37039 : (XSMLTDCL05) You cannot maintain triggers in analytic workspace string because it is attached in MULTI mode.
  • ora-06705 : TLI Driver: remote node is unknown
  • ora-00020 : maximum number of processes (string) exceeded
  • ora-29936 : NULL association is allowed only with a column or an index
  • ora-25467 : table alias not specified
  • ora-36816 : (XSTBLFUNC09) The workspace object dimension is of datatype string which does not support custom member upserts.
  • ora-08342 : sropen: failed to open a redo server connection
  • ora-23609 : unable to find directory object for directory string
  • ora-31609 : error loading file "string" from file system directory "string"
  • ora-39029 : worker string with process name "string" prematurely terminated
  • ora-00347 : log string of thread string, expected block size string doesn't match string
  • ora-13263 : column string in table string is not of type SDO_GEOMETRY
  • ora-29316 : datafile string been imported twice
  • ora-14629 : cannot drop the only subpartition of a partition
  • ora-19372 : invalid update condition
  • ora-37138 : (XSCCOMP13) You cannot delete values from workspace object because it is an aggregated COMPRESSED COMPOSITE.
  • ora-10640 : Operation not permitted during SYSTEM tablespace migration
  • ora-29289 : directory access denied
  • ora-07480 : snchmod: cannot change permissions on ?/dbs/sgalm.dbf.
  • ora-19709 : numeric parameter must be non-negative integer
  • ora-13526 : baseline (string) does not exist
  • ora-38739 : Flashback log file is more recent than control file.
  • ora-00269 : specified log file is part of thread string not string
  • ora-25231 : cannot dequeue because CONSUMER_NAME not specified
  • ora-16067 : activation identifier mismatch in archive log string
  • ora-24752 : OCI_TRANS_NEW flag must be specified for local transactions
  • ora-38956 : Target platform string not cross platform compliant
  • 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.