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 : 26-04-2017

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

  • ora-30376 : prevent sharing of a parsed query of an explain rewrite session
  • ora-08234 : smsget: cannot get instance listener address
  • ora-00020 : maximum number of processes (string) exceeded
  • ora-38726 : Flashback database logging is not on.
  • ora-10658 : Lob column to be shrunk is marked unused
  • ora-19282 : XQ0068 - It is a static error if a Prolog contains more than one xmlspace declaration
  • ora-04074 : invalid REFERENCING name
  • ora-32690 : Hash Table Infrastructure ran out of memory
  • ora-13866 : Client identifier must be specified
  • ora-19035 : Invalid select item of the query in newContextFromHierarchy()
  • ora-06702 : TLI Driver: cannot allocate context area
  • ora-02431 : cannot disable constraint (string) - no such constraint
  • ora-25152 : TEMPFILE cannot be dropped at this time
  • ora-10662 : Segment has long columns
  • ora-31411 : change set string is referenced by a change table
  • ora-02165 : invalid option for CREATE DATABASE
  • ora-13869 : Instance-wide SQL tracing on instance string is already enabled
  • ora-09836 : addCallback: could not add a port to the callback set.
  • ora-12236 : TNS:protocol support not loaded
  • ora-02065 : illegal option for ALTER SYSTEM
  • ora-25220 : enqueue failed, signature not specified for a non-repudiable queue
  • ora-25327 : Array size is invalid
  • ora-19911 : datafile string contains future changes at the incarnation boundary
  • ora-09840 : soacon: Name translation failure.
  • ora-29875 : failed in the execution of the ODCIINDEXINSERT routine
  • ora-01517 : log member: 'string'
  • ora-32056 : invalid number of extents
  • ora-25298 : Only immediage visibility mode supported for buffered message enqueue or dequeue
  • ora-03290 : Invalid truncate command - missing CLUSTER or TABLE keyword
  • ora-00052 : maximum number of enqueue resources (string) exceeded
  • 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.