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 : 23-05-2017
ORA-19527

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

  • ora-26752 : Unsupported LCR received for "string"."string"
  • ora-12701 : CREATE DATABASE character set is not known
  • ora-12409 : policy startup failure for string policy
  • ora-28011 : the account will expire soon; change your password now
  • ora-13447 : GeoRaster metadata BRS error
  • ora-13287 : can't transform unknown gtype
  • ora-29536 : badly formed source: string
  • ora-24003 : Queue table index string inconsistent with queue table string
  • ora-27087 : unable to get share lock - file not readable
  • ora-25241 : cannot change correlation ID from string to string without FIRST_MESSAGE option
  • ora-28005 : invalid logon flags
  • ora-39169 : Local version of string cannot work with remote version of string.
  • ora-03126 : network driver does not support non-blocking operations
  • ora-19704 : file name exceeds maximum length of string
  • ora-06751 : TLI Driver: bound addresses unequal
  • ora-36995 : (XSRELGID12) There are duplicate values in the surrogate dimension gid. Use the levelorder option to resolve the ambiguity.
  • ora-30202 : NULL pointer to OCIMsgh was passed to OCIMsg function
  • ora-22882 : object creation failed
  • ora-13035 : Invalid data (arcs in geodetic data) in the SDO_GEOMETRY object
  • ora-13262 : geometry column string does not exist in table string
  • ora-39706 : schema 'string' not found
  • ora-38950 : Source platform string not cross platform compliant
  • ora-16567 : Data Guard broker internal parser error at "string"
  • ora-02190 : keyword TABLES expected
  • ora-30965 : fragment does not fit into the VARCHAR2 VALUE column
  • ora-03252 : initial extent size not enough for LOB segment
  • ora-07846 : sllfop: string byte record too big for string byte user buffer
  • ora-01663 : the contents of tablespace 'string' is constantly changing
  • ora-15066 : offlining disk "string" may result in a data loss
  • ora-10924 : import storage parse error ignore event
  • 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.