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 : 16-08-2017
ORA-25125

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

  • ora-38771 : unnamed datafile(s) added to control file by flashback recovery
  • ora-14510 : can specify VALIDATE INTO clause only for partitioned tables
  • ora-13390 : error in spatial analysis and mining function: [string]
  • ora-24331 : user buffer too small
  • ora-19763 : compatibility version string is higher than maximum allowed: string
  • ora-13112 : cannot delete topo_geometry layer [string] from topology
  • ora-27028 : skgfqcre: sbtbackup returned error
  • ora-32825 : Messaging Gateway agent has not been started
  • ora-01939 : only the ADMIN OPTION can be specified
  • ora-14010 : this physical attribute may not be specified for an index partition
  • ora-32634 : automatic order MODEL evaluation does not converge
  • ora-29378 : invalid consumer group mapping priorities
  • ora-16723 : setting AlternateLocation property conflicts with the redo transport setting
  • ora-09830 : snyAddPort: failed to perform a remote procedure call.
  • ora-01261 : Parameter string destination string cannot be translated
  • ora-09317 : szprv: insufficient privileges
  • ora-28272 : Domain policy restricts password based GLOBAL user authentication.
  • ora-19729 : File string is not the initial version of the plugged in datafile
  • ora-09773 : osnmgetdatmsg: message from host had incorrect message type
  • ora-19690 : backup piece release string incompatible with Oracle release string
  • ora-23398 : user name "string" at database link "string" does not match local user name "string"
  • ora-32314 : REFRESH FAST of "string"."string" unsupported after deletes/updates
  • ora-16237 : SGA specified for Logical Standby is too small
  • ora-02729 : osncon: driver not in osntab
  • ora-16042 : user requested cancel immediate of managed recovery operation
  • ora-26058 : unexpected error fetching metadata for column string in table string
  • ora-37171 : dimension sources not specified
  • ora-19211 : column 'string', specified as key using DBMS_XMLSTORE.setKeyColumn() , must be of scalar type
  • ora-01663 : the contents of tablespace 'string' is constantly changing
  • ora-36672 : (XSDPART10) A RANGE or LIST PARTITION TEMPLATE can only have a single partition dimension.
  • 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.