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 : 22-07-2017

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

  • ora-01189 : file is from a different RESETLOGS than previous files
  • ora-08342 : sropen: failed to open a redo server connection
  • ora-16090 : archive log to be replaced not created by managed standby process
  • ora-37035 : (XSMLTDCL01) You can only DEFINE SESSION objects in analytic workspace string because it is attached in MULTI mode.
  • ora-30431 : refresh method must be ANY or INCREMENTAL or FORCE_FULL, not string
  • ora-26737 : version string already has an export dump file
  • ora-12809 : cannot set string_INSTANCES when mounted in exclusive mode
  • ora-29895 : duplicate base datatype specified
  • ora-14138 : An unexpected error encountered during drop table operation
  • ora-09988 : error while detaching SGA
  • ora-27046 : file size is not a multiple of logical block size
  • ora-32623 : incorrect use of MODEL PRESENT* functions
  • ora-09708 : soacon: failed to bind socket to port.
  • ora-09950 : Unable to get server operating system privileges
  • ora-02247 : no option specified for ALTER SESSION
  • ora-24281 : invalid access past the maximum size of LOB parameter string
  • ora-28134 : object cannot have fine-grained access control policy
  • ora-33100 : (APABBR02) Value 'number' is not valid for the workspace object option.
  • ora-30186 : '' must be followed by four hexdecimal characters or another ''
  • ora-26705 : cannot downgrade capture process after Streams data dictionary has been upgraded
  • ora-12534 : TNS:operation not supported
  • ora-07236 : slemop: open error.
  • ora-36820 : (XSLMINFO00) The LIMITMAPINFO function encountered an error while parsing the LIMITMAP.
  • ora-06610 : LU6.2 Driver: Failed during deallocation
  • ora-14409 : inserted partition key is outside specified subpartition
  • ora-01229 : data file string is inconsistent with logs
  • ora-14508 : specified VALIDATE INTO table not found
  • ora-01325 : archive log mode must be enabled to build into the logstream
  • ora-27194 : skgfdvcmd: sbtcommand returned error
  • ora-28525 : unable to create Heterogeneous Services error message text
  • 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.