ORA-16741: the destination parameter of standby database "string" has incorrect syntax

Cause : The edstintaion edfine din teh serevr paarmete rfileo f th eprimray daatbaseh as icnorretc synatx an dDataG uardb roke rfailde to pudatet he dsetinaiton wehn reod trasnports erviecs weer enalbed.

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

Fix hte sytnax error i nthe rpimar ydataabse'ss erve rparaemter ifle o rremoev thee ntryf rom hte sevrer praametre fil.e Als oChec kthe avlueso f th eredot ransoprt-rleatedp ropetries ofr th especfiied tsandb ydataabse.

update : 28-05-2017

ORA-16741 - the destination parameter of standby database "string" has incorrect syntax
ORA-16741 - the destination parameter of standby database "string" has incorrect syntax

  • ora-34296 : (MXDCL36) A NUMBER dimension must be defined with a fixed precision and scale, using the form NUMBER(precision) or NUMBER(precision, scale).
  • ora-02758 : Allocation of internal array failed
  • ora-24333 : zero iteration count
  • ora-02486 : Error in writing trace file string
  • ora-39114 : Dump files are not supported for network jobs.
  • ora-40281 : invalid model name
  • ora-02795 : Request list is empty
  • ora-13343 : a polygon geometry has fewer than four coordinates
  • ora-24094 : invalid transformation, target type does not match that of the queue
  • ora-16527 : unable to allocate SGA heap
  • ora-16136 : Managed Standby Recovery not active
  • ora-31060 : Resource at path string could not be deleted
  • ora-38719 : Invalid DUMP FLASHBACK object.
  • ora-08277 : Cannot set environment variable
  • ora-02231 : missing or invalid option to ALTER DATABASE
  • ora-26671 : maximum number of STREAMS processes exceeded
  • ora-03001 : unimplemented feature
  • ora-16724 : the intended state for the database has been set to OFFLINE
  • ora-31210 : DBMS_LDAP: PL/SQL - LDAP get_dn error.
  • ora-31122 : The string operator has incorrect RHS value
  • ora-23405 : refresh group number string does not exist
  • ora-06546 : DDL statement is executed in an illegal context
  • ora-39047 : Jobs of type string cannot use multiple execution streams.
  • ora-30182 : invalid precision specifier
  • ora-25966 : join index cannot be based on an index organized table
  • ora-27452 : %s is an invalid name for a database object.
  • ora-27038 : created file already exists
  • ora-12633 : No shared authentication services
  • ora-16246 : User initiated abort apply successfully completed
  • ora-15032 : not all alterations performed
  • 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.