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 : 25-06-2017
ORA-19527

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

  • ora-02234 : changes to this table are already logged
  • ora-25253 : listen failed, queue string.string is not enabled for dequeue
  • ora-14302 : only one list of added-LOB-storage-clauses can be specified in a statement
  • ora-09340 : Specified ORACLE_SID is either invalid or too long
  • ora-30130 : invalid parameter key type received
  • ora-28651 : Primary index on IOTs can not be marked unusable
  • ora-16632 : instance being added to database profile
  • ora-02188 : Cannot enable instance publicly
  • ora-27488 : unable to set string because string was/were already set
  • ora-32624 : illegal reordering of MODEL dimensions
  • ora-09953 : scggc: unexpected return of a lock convert
  • ora-02494 : invalid or missing maximum file size in MAXSIZE clause
  • ora-19246 : XQ0026 - validation failed - element string not found in in-scope element declarations
  • ora-37115 : New OLAP API history is not allowed
  • ora-23602 : Invalid streams process type string
  • ora-30742 : cannot grant SELECT privilege WITH HIERARCHY OPTION on this object
  • ora-19503 : cannot obtain information on device, name="string", type="string", parms="string"
  • ora-14516 : subpartition corrupt. all rows do not fall within subpartition bounds
  • ora-14005 : missing RANGE keyword
  • ora-09976 : skxfqdini: Error Creating Port
  • ora-26723 : user "string" requires the role "string"
  • ora-36391 : (XSMXCLEA01) When CLEAR is used with the STATUS keyword or an AGGMAP, workspace object must be dimensioned identically to workspace object.
  • ora-00019 : maximum number of session licenses exceeded
  • ora-24335 : cannot support more than 1000 columns
  • ora-02210 : no options specified for ALTER TABLE
  • ora-19736 : can not plug a tablespace into a database using a different national character set
  • ora-19750 : change tracking file: 'string'
  • ora-22619 : all collection elements have already been accessed
  • ora-25004 : WHEN clause is not allowed in INSTEAD OF triggers
  • ora-31103 : Resource locked in shared mode. Cannot add exclusive lock
  • 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.