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 : 28-06-2017
ORA-25145

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

  • ora-36849 : (XSLMGEN19) AW owner does not match View token owner
  • ora-07637 : smsdbp: buffer protect option not specified when sga created
  • ora-28048 : database is a member of multiple enterprise domains in OID
  • ora-32614 : illegal MODEL SELECT expression
  • ora-28331 : encrypted column size too long for its data type
  • ora-00372 : file string cannot be modified at this time
  • ora-06959 : Buffer I/O quota is too small
  • ora-23514 : invalid or incorrect number of arguments
  • ora-08276 : No room in nameserver for pid
  • ora-06306 : IPA: Message write length error
  • ora-06907 : CMX: error during connect confirmation
  • ora-16507 : unrecognized request identifier
  • ora-38620 : DT expressions in input cursor do not have an alias name
  • ora-14032 : partition bound of partition number string is too high
  • ora-29346 : invalid tablespace list
  • ora-03230 : segment only contains string blocks of unused space above high water mark
  • ora-13628 : Insufficient privileges to access the task belonging to the specified user
  • ora-16518 : unable to allocate virtual instance id
  • ora-10565 : Another test recovery session is active
  • ora-01618 : redo thread string is not enabled - cannot mount
  • ora-10373 : parallel query server kill event
  • ora-13380 : network not found
  • ora-14196 : Specified index cannot be used to enforce the constraint.
  • ora-23407 : object name string must be shaped like "schema"."object" or "object"
  • ora-01144 : File size (string blocks) exceeds maximum of string blocks
  • ora-16566 : unsupported document type
  • ora-33309 : (DBVALID05) SEVERE ERROR: Record number used but not allocated (PS number)
  • ora-06438 : ssaio: the asynchronous read was unable to read from the database file.
  • ora-18003 : an outline already exists with this signature
  • ora-08121 : Number of indexes need to be maintained offline exceeds limit for DML
  • 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.