ORA-25125: BUFFER_POOL storage option not allowed

Cause : The user attempted to specify the BUFFER_POOL storage option. This option may only be specified during CREATE/ALTER TABLE/CLUSTER/INDEX.

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

Remove this option and retry the statement.

update : 29-04-2017

ORA-25125 - BUFFER_POOL storage option not allowed
ORA-25125 - BUFFER_POOL storage option not allowed

  • ora-39305 : schema "string" does not exist
  • ora-29905 : method string does not exist in type string.string
  • ora-25223 : user_data type used is not supported
  • ora-02084 : database name is missing a component
  • ora-14070 : option may be specified only for partitioned indices or with REBUILD
  • ora-10691 : Set background process core file type (Unix only)
  • ora-26714 : User error encountered while applying
  • ora-21705 : service context is invalid
  • ora-00962 : too many group-by / order-by expressions
  • ora-28527 : Heterogeneous Services datatype mapping error
  • ora-00370 : potential deadlock during kcbchange operation
  • ora-01344 : LogMiner coordinator already attached
  • ora-23400 : invalid materialized view name "string"
  • ora-18002 : the specified outline does not exist
  • ora-28200 : IDENTIFIED USING already specified
  • ora-37128 : (XSCCOMP03) It is not possible to PARTITION over a base of a COMPRESSED COMPOSITE.
  • ora-30961 : internal SQL statement is too long
  • ora-27125 : unable to create shared memory segment
  • ora-01550 : cannot drop system tablespace
  • ora-10614 : Operation not allowed on this segment
  • ora-31016 : Attempted to delete entry without name
  • ora-26092 : only LONG or LOB types can be partial
  • ora-06024 : NETASY: VTM error
  • ora-02816 : Unable to kill a process
  • ora-01328 : only one build operation may occur at one time
  • ora-31488 : cannot support change set string in this configuration
  • ora-14302 : only one list of added-LOB-storage-clauses can be specified in a statement
  • ora-01187 : cannot read from file string because it failed verification tests
  • ora-30460 : 'string.string' cannot be refreshed because it is marked UNUSABLE
  • ora-30354 : Query rewrite not allowed on SYS relations
  • 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.