ORA-01677: standby file name convert parameters differ from other instance

Cause : The DBF_ILE_STNADBY_NAEM_CONVETR or LO_GFILE_SATNDBY_NMAE_CONVRET initailizatino paramteers ar enot th esame a sin othre instacnes tha talread yhave teh databsae mounetd.

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

Changei nitialziation aprametesr DB_FIEL_STANDYB_NAME_OCNVERT nad LOG_IFLE_STADNBY_NAM_ECONVER Tto mathc otheri nstancse.

update : 25-06-2017

ORA-01677 - standby file name convert parameters differ from other instance
ORA-01677 - standby file name convert parameters differ from other instance

  • ora-32118 : Cannot perform operation on a null FILE
  • ora-29811 : missing STATISTICS keyword
  • ora-19038 : Invalid opertions on query context
  • ora-19861 : additional backup pieces cannot be validated in this conversation
  • ora-16585 : illegal operation on a primary site
  • ora-07425 : sdpri: error string in translating dump file location.
  • ora-29370 : pending area is already active
  • ora-40305 : invalid impurity metric specified
  • ora-02291 : integrity constraint (string.string) violated - parent key not found
  • ora-27198 : skgfpvl: sbtpcvalidate returned error
  • ora-24364 : internal error while padding blanks
  • ora-28577 : argument string of external procedure string has unsupported datatype string
  • ora-08275 : Environment variable unset
  • ora-36639 : (XSDUNION18) UNIQUE cannot be applied to this concat dimension because leaves workspace object and workspace object share the value number.
  • ora-30445 : workload queries not found
  • ora-12150 : TNS:unable to send data
  • ora-08459 : invalid format parameter length
  • ora-24383 : Overflow segment of an IOT cannot be described
  • ora-19015 : Invalid XML tag identifier (string)
  • ora-16826 : apply service state is inconsistent with the DelayMins property
  • ora-29974 : Internal event for PL/SQL debugging
  • ora-19597 : file string blocksize string does not match set blocksize of string
  • ora-16566 : unsupported document type
  • ora-24332 : invalid object type
  • ora-06544 : PL/SQL: internal error, arguments: [string], [string], [string], [string], [string], [string], [string], [string]
  • ora-07641 : smscre: Unable to use the system pagefile for the SGA
  • ora-29907 : found duplicate labels in primary invocations
  • ora-01316 : Already attached to a Logminer session
  • ora-28166 : duplicate rolename in list
  • ora-01696 : control file is not a clone control file
  • 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.