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-04-2017

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

  • ora-34342 : (MXDSS01) IMPORTANT: Analytic workspace string is read-only. Therefore, you will not be able to use the UPDATE command to save changes to it.
  • ora-07568 : slspool: $OPEN failure
  • ora-16727 : resource guard cannot close database
  • ora-09928 : Unable to restore the label of server
  • ora-02150 : invalid new tablespace name
  • ora-40285 : label not in the model
  • ora-01503 : CREATE CONTROLFILE failed
  • ora-32006 : %s initialization parameter has been deprecated
  • ora-09801 : Unable to get user ID from connection
  • ora-01268 : invalid TEMPFILE clause for alter of permanent TABLESPACE
  • ora-02222 : invalid PCTINCREASE storage option value
  • ora-12093 : invalid interim table "string"."string"
  • ora-07483 : snlkget: cannot convert(get) lock.
  • ora-01506 : missing or illegal database name
  • ora-23379 : connection qualifier "string" is too long
  • ora-25274 : AQ Buffered Queue event
  • ora-10587 : Invalid count for ALLOW n CORRUPTION option
  • ora-13640 : The current operation was cancelled because it timed out, and was not in interruptible mode.
  • ora-07645 : sszfsl: $CHANGE_CLASS failure
  • ora-03274 : both ALLOCATE EXTENT and DEALLOCATE UNUSED options are specified
  • ora-06316 : IPA: Invalid database SID
  • ora-37070 : You may not execute OLAP DML programs in a parallel query session.
  • ora-09745 : smscre: vm_allocate error, unable to create shared memory.
  • ora-01093 : ALTER DATABASE CLOSE only permitted with no sessions connected
  • ora-00304 : requested INSTANCE_NUMBER is busy
  • ora-39203 : Partition selection is not supported over a network link.
  • ora-27469 : %s is not a valid string attribute
  • ora-09764 : osnmop: access error on oracle executable
  • ora-06763 : TLI Driver: error sending disconnect
  • ora-12812 : only one PARALLEL or NOPARALLEL clause may be specified
  • 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.