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

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-29901 : function underlying operator binding does not exist
  • ora-30333 : dimension does not exist
  • ora-13710 : Parameter "string" must have a higher value than parameter "string". The values supplied were "string" and "string" respectively.
  • ora-23392 : could not find materialized view to be associated with "string"."string"
  • ora-23455 : flavor string contains object "string"
  • ora-30159 : OCIFileOpen: Cannot create the file or cannot open in the requested mode
  • ora-12229 : TNS:Interchange has no more free connections
  • ora-25263 : no message in queue string.string with message ID string
  • ora-39081 : failed to unsubscribe agent string from queue "string"
  • ora-23345 : table "string"."string" not registered to collect statistics
  • ora-16596 : object not part of the Data Guard broker configuration
  • ora-09204 : sfotf: error opening temporary file
  • ora-30088 : datetime/interval precision is out of range
  • ora-38435 : missing elementary attribute value or invalid name-value pairs
  • ora-07269 : spdcr: detached process died after exec.
  • ora-25447 : encountered errors during evaluation of rule string.string
  • ora-19106 : invalid XQueryX: expected string - got string
  • ora-40253 : no target counter examples were found
  • ora-16768 : SQL Apply unexpectedly offline
  • ora-22277 : cannot use two different locators to modify the same LOB
  • ora-32637 : Self cyclic rule in sequential order MODEL
  • ora-19202 : Error occurred in XML processingstring
  • ora-13200 : internal error [string] in spatial indexing.
  • ora-22894 : cannot add constraint on existing unscoped REF columns of non-empty tables
  • ora-36872 : (XSTFDSC02) Column type specifier cannot be used when the table function data type is specified.
  • ora-28274 : No ORACLE password attribute corresponding to user nickname exists.
  • ora-13699 : Advisor feature is not currently implemented.
  • ora-02146 : SHARED specified multiple times
  • ora-24088 : AQ Agent string does not exist
  • ora-16598 : Data Guard broker detected a mismatch in configuration
  • 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.