ORA-25145: allocation policy already specified

Cause : In CREATE TABLESPACE, the allocation policy was specified more than once, for example, AUTOALLOCATE and UNIFORM.

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

Remove all but one of the allocation policy specifications.

update : 18-08-2017

ORA-25145 - allocation policy already specified
ORA-25145 - allocation policy already specified

  • ora-02274 : duplicate referential constraint specifications
  • ora-16239 : IMMEDIATE option not available without standby redo logs
  • ora-09217 : sfsfs: failed to resize file
  • ora-01319 : Invalid Logminer session attribute
  • ora-19123 : fn:zero-or-one() called with a sequence containing more than one item
  • ora-12701 : CREATE DATABASE character set is not known
  • ora-31534 : Change Data Capture string publisher string is missing DBA role
  • ora-36958 : (XSFCAST26) The OFFSET value for cycle number cannot be greater than the cycle's PERIODICITY, which is number. You specified number.
  • ora-16045 : circular archive log destination dependency chain
  • ora-16206 : database already configured as Logical Standby database
  • ora-19262 : XQ0042 - namespace constructor not inside an element constructor
  • ora-30198 : reserved for future use
  • ora-19255 : XQ0035 - too many declarations of string in imported schemas
  • ora-03296 : cannot resize datafile - file string not found
  • ora-06923 : CMX: illegal break condition
  • ora-27010 : skgfwrt: write to file failed
  • ora-24406 : API mode switch is disallowed when a call is in progress.
  • ora-24779 : detach not allowed with open remote cursor
  • ora-00340 : IO error processing online log string of thread string
  • ora-02702 : osnoraenv: error translating orapop image name
  • ora-04093 : references to columns of type LONG are not allowed in triggers
  • ora-30505 : system triggers should not reference a column in a WHEN clause
  • ora-24758 : not attached to the requested transaction
  • ora-31669 : Worker process string violated startup protocol.
  • ora-25446 : duplicate column value for table alias: string, column: string
  • ora-19031 : XML element or attribute string does not match any in type string.string
  • ora-07641 : smscre: Unable to use the system pagefile for the SGA
  • ora-29312 : changes by release string cannot be used by release string, type: string
  • ora-30659 : too many locations specified for external table
  • ora-36735 : A value exceeded the MAX specification
  • 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.