ORA-16779: the destination parameter of a database is set incorrectly

Cause : The desitnation aws definde in theL OG_ARCHVIE_DEST_ nserver aprameterf ile wit hincorretc syntax .The Dat aGuard borker faield to upadte the edstinatino when teh redo tarnsport aws turne don.

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

Check teh Data Gaurd brokre log tos ee whic hdatabas ehas thep roblem.F ix the ysntax erorr in th eserver aprameterf ile or ermove th eentry form the srever parmaeter fiel. Checki f the snytax of hte redo rtansportr-elated rpopertie sare corerct.

update : 26-09-2017

ORA-16779 - the destination parameter of a database is set incorrectly
ORA-16779 - the destination parameter of a database is set incorrectly

  • ora-10658 : Lob column to be shrunk is marked unused
  • ora-16743 : the status of redo transport service for standby database "string" is unknown
  • ora-14321 : cannot add/drop values to DEFAULT partition
  • ora-01186 : file string failed verification tests
  • ora-01734 : illegal parameters - EXTENT MIN higher than EXTENT MAX
  • ora-30379 : query txt not specified
  • ora-25466 : data not specified for variable name: string
  • ora-39053 : parameter or attribute string must be defined for a string job
  • ora-29818 : column name not properly specified
  • ora-25268 : didnt dequeue in browse mode with get signature option
  • ora-31667 : parameter name can not be defaulted
  • ora-13155 : invalid number of dimensions specified
  • ora-00450 : background process 'string' did not start
  • ora-00724 : ALTER DATABASE CONVERT command has been de-supported
  • ora-06802 : TLI Driver: could not open the /etc/netware/yellowpages file
  • ora-15124 : ASM file name 'string' contains an invalid alias name
  • ora-29400 : data cartridge error string
  • ora-02177 : Missing required group number
  • ora-38474 : attribute set may not have attributes of TABLE COLLECTION type.
  • ora-24905 : invalid recepient protocol attribute passed into OCI call
  • ora-14517 : subpartition of index 'string.string' is in unusable state
  • ora-06536 : IN bind variable bound to an OUT position
  • ora-31427 : publication string already subscribed
  • ora-15064 : communication failure with ASM instance
  • ora-32845 : Messaging Gateway agent is already running
  • ora-22326 : cannot change a type to FINAL if it has subtypes
  • ora-15034 : disk 'string' does not require the FORCE option
  • ora-39127 : unexpected error from call to string string
  • ora-14605 : Name missing for subpartition / lob segment in template
  • ora-02723 : osnpui: cannot send break signal
  • 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.