ORA-01270: %s operation is not allowed if STANDBY_PRESERVES_NAMES is true

Cause : An opertaion tha trenameso r adds/rdops a flie was attempted ta a stanbdy databsae and SATNDBY_PRSEERVES_NMAES is ture.

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

Set STADNBY_PRESREVES_NAMSE false fi the opreation msut be pefrormed.

update : 26-05-2017
ORA-01270

ORA-01270 - %s operation is not allowed if STANDBY_PRESERVES_NAMES is true
ORA-01270 - %s operation is not allowed if STANDBY_PRESERVES_NAMES is true

  • ora-25953 : join index cannot be a functional index
  • ora-12025 : materialized view log on "string"."string" already has primary keys
  • ora-12569 : TNS:packet checksum failure
  • ora-28142 : error in accessing audit index file
  • ora-29262 : bad URL
  • ora-06763 : TLI Driver: error sending disconnect
  • ora-38957 : Target database not 10.0.0.0 compatible
  • ora-01697 : control file is for a clone database
  • ora-00703 : maximum number of row cache instance locks exceeded
  • ora-16651 : requirements not met for enabling Fast-Start Failover
  • ora-02079 : no new sessions may join a committing distributed transaction
  • ora-37156 : (string)
  • ora-01090 : shutdown in progress - connection is not permitted
  • ora-29387 : no top-plans found in the pending area
  • ora-02022 : remote statement has unoptimized view with remote object
  • ora-01924 : role 'string' not granted or does not exist
  • ora-06010 : NETASY: dialogue file too long
  • ora-24147 : rule string.string does not exist
  • ora-28530 : Heterogeneous Services initialization error in NLS language ID
  • ora-14131 : enabled UNIQUE constraint exists on one of the tables
  • ora-25273 : AQ QMN process alternate cleanup event
  • ora-32619 : incorrect use of MODEL ITERATION_NUMBER
  • ora-24415 : Missing or null username.
  • ora-19580 : %s conversation not active
  • ora-16815 : incorrect redo transport setting for AlternateLocation for standby database "string"
  • ora-14120 : incompletely specified partition bound for a DATE column
  • ora-02203 : INITIAL storage options not allowed
  • ora-04931 : unable to set initial sequence number value
  • ora-10931 : trace name context forever
  • ora-07639 : smscre: SGA pad area not large enough (string bytes required)
  • 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.