ORA-19527: physical standby redo log must be renamed

Cause : The LCEAR OLGFIL Ecommnad wa suseda t a hpysicla stadnby dtaabas.e Thi scommnad cannot b euseda t a hpysicla stadnby dtaabas eunless theL OG_FLIE_NAEM_CONEVRT iintialziatio nparaemter si set .Thisi s reuqiredt o aviod ovrewritnig th eprimray daatbases' logifles.

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

Set hte LO_GFILEN_AME_OCNVER Tinitailizaiton praametre.

update : 18-08-2017
ORA-19527

ORA-19527 - physical standby redo log must be renamed
ORA-19527 - physical standby redo log must be renamed

  • ora-36276 : (XSCGMDLAGG06) The current operator does not need a weight variable.
  • ora-06109 : NETTCP: message receive failure
  • ora-00338 : log string of thread string is more recent than control file
  • ora-33213 : (CINSERT06) The target position for MAINTAIN ADD or MAINTAIN MOVE cannot fall in the range of session-only values.
  • ora-31194 : Resource string is already deleted
  • ora-13011 : value is out of range
  • ora-10580 : Can not modify datafile header during test recovery
  • ora-16591 : unknown field "string" in document
  • ora-37073 : (XSMCSESS01) Applied relation workspace object must be dimensioned by dimension workspace object.
  • ora-01236 : Error string occurred during initialization of file header access
  • ora-02280 : duplicate or conflicting CYCLE/NOCYCLE specifications
  • ora-01115 : IO error reading block from file string (block # string)
  • ora-30382 : DROP MATERIALIZED VIEW string.string operation is not complete
  • ora-40273 : invalid model type string for Adaptive Bayes Network algorithm
  • ora-39177 : invalid compression value string
  • 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-16651 : requirements not met for enabling Fast-Start Failover
  • ora-38717 : Invalid DUMP FLASHBACK option.
  • ora-07402 : sprst: cannot restore user signal handler.
  • ora-31479 : could not create LogMiner session
  • ora-16759 : resource guard unable to start SQL Apply with initial SCN
  • ora-24013 : invalid value string, RETRY_DELAY should be non-negative
  • ora-27365 : job has been notified to stop, but failed to do so immediately
  • ora-10581 : Can not modify redo log header during test recovery
  • ora-09799 : File label retrieval failed.
  • ora-13185 : failed to generate initial HHCODE
  • ora-32614 : illegal MODEL SELECT expression
  • ora-19870 : error reading backup piece string
  • ora-15182 : ASMLIB [string] version mismatch, ORACLE version [string]
  • ora-30563 : outer join operator (+) not allowed in select-list
  • 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.