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 : 17-08-2017

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-01989 : role 'string' not authorized by operating system
  • ora-08000 : maximum number of session sequence lists exceeded
  • ora-25202 : invalid value NULL, string should be non-NULL
  • ora-14284 : one or more of table's subpartitions reside in a read-only tablespace
  • ora-32807 : message system link string already exists
  • ora-07286 : sksagdi: cannot obtain device information.
  • ora-07586 : spdcr: $SEARCH failure
  • ora-12855 : cannot run parallel or insert direct load in a loopback
  • ora-09954 : scgcc: unexpected return status to callback of lock close
  • ora-01117 : adding file 'string' with illegal block size: string; limit is string
  • ora-26727 : Cannot alter queue_to_queue property of existing propagation.
  • ora-06573 : Function string modifies package state, cannot be used here
  • ora-28176 : incorrect certificate version
  • ora-19605 : input filename must be specified
  • ora-12600 : TNS: string open failed
  • ora-36767 : (XSAGGCNTMOVE05) workspace object cannot be used as an AGGCOUNT while there are permissions applied to it.
  • ora-08449 : invalid numeric symbol found in picture mask
  • ora-25336 : Cannot contact instance string during Streams AQ operation
  • ora-14160 : this physical attribute may not be specified for a table subpartition
  • ora-27476 : "string.string" does not exist
  • ora-16062 : DGID from standby not in Data Guard configuration
  • ora-23497 : repgroup name cannot be null
  • ora-12406 : unauthorized SQL statement for policy string
  • ora-30678 : too many open connections
  • ora-32737 : Hang analysis aborted due to failed memory allocation
  • ora-36394 : (XSMXCLEA04) When using CLEAR on the AGGMAP workspace object, CACHE is the only valid directive.
  • ora-16620 : one or more databases could not be contacted for a delete operation
  • ora-30108 : invalid positional parameter value 'string'
  • ora-34183 : (MXCHGDCL22) Partition number already exists.
  • ora-37030 : (XSMLTMAINT01) You cannot maintain workspace object because it is not ACQUIRED.
  • 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.