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 : 17-08-2017

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

  • ora-30338 : illegal dimension hierachy name
  • ora-14301 : table-level attributes must be specified before partition-level attributes
  • ora-39067 : Unable to close the log file.
  • ora-31165 : cannot load object-relational XML attribute using direct path
  • ora-10691 : Set background process core file type (Unix only)
  • ora-04941 : required operating system patch needs to be applied
  • ora-07658 : slsprom:$QIOW read failure
  • ora-01170 : file not found 'string'
  • ora-19771 : cannot rename change tracking file while database is open
  • ora-22857 : cannot modify columns of object tables
  • ora-31117 : Table "string"."string" is not resource metadata enabled
  • ora-10653 : Table is in a cluster
  • ora-06572 : Function string has out arguments
  • ora-32839 : property string is reserved, names with MGWPROP$_ prefix are not valid
  • ora-00381 : cannot use both new and old parameters for buffer cache size specification
  • ora-01181 : file string created before last known RESETLOGS, cannot recreate
  • ora-01878 : specified field not found in datetime or interval
  • ora-29289 : directory access denied
  • ora-14643 : Hakan factor mismatch for tables in ALTER TABLE EXCHANGE PARTITION
  • ora-09342 : Detached process terminated by Oracle during shutdown abort
  • ora-27166 : tried to join current thread
  • ora-01208 : data file is an old version - not accessing current version
  • ora-32586 : multiple specification of a supplemental logging attribute
  • ora-22905 : cannot access rows from a non-nested table item
  • ora-13619 : The procedure argument string is greater than the maximum allowable length of string characters.
  • ora-32846 : Messaging Gateway agent cannot be started; status is string
  • ora-24504 : data length larger than expected
  • ora-13381 : table:string not found in network:string
  • ora-24150 : evaluation context string.string does not exist
  • ora-01026 : multiple buffers of size > 4000 in the bind 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.