ORA-16755: failed to set initialization parameter

Cause : The ALTER SYSTEM SET or ALTER SYSTEM RESET command issued by the Data Guard broker failed.

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

Check the Data Guard broker log and Oracle alert log for more details.

update : 24-06-2017

ORA-16755 - failed to set initialization parameter
ORA-16755 - failed to set initialization parameter

  • ora-32738 : Hang analysis aborted due to failed memory copy
  • ora-27064 : cannot perform async I/O to file
  • ora-22984 : view query cannot contain references to a super view
  • ora-01651 : unable to extend save undo segment by string for tablespace string
  • ora-30550 : index depends on a package/function spec/body which is not valid
  • ora-28504 : ROWID not found in ROWID cache for heterogeneous database link
  • ora-13412 : invalid scale parameter
  • ora-39017 : Worker request not supported when job is in string state.
  • ora-34901 : (PPWKDAYS01) Blank lines are not allowed in the DAYNAMES option.
  • ora-06815 : TLI Driver: could not link SPX and IPX streams
  • ora-31427 : publication string already subscribed
  • ora-32635 : not a single cell reference predicate
  • ora-08431 : raw data missing zero as defined in picture
  • ora-19590 : conversation already active
  • ora-01686 : max # files (string) reached for the tablespace string
  • ora-01037 : maximum cursor memory exceeded
  • ora-24240 : invalid database access descriptor (DAD) name
  • ora-15125 : ASM file name 'string' contains an invalid template name
  • ora-02072 : distributed database network protocol mismatch
  • ora-35022 : (QFCHECK03) The analytic workspace and EIF file definitions of workspace object have a mismatched relation.
  • ora-32131 : bind data type cannot be changed
  • ora-30357 : this PL/SQL function cannot be supported for query rewrite
  • ora-10580 : Can not modify datafile header during test recovery
  • ora-29865 : indextype is invalid
  • ora-09817 : Write to audit file failed.
  • ora-28005 : invalid logon flags
  • ora-06419 : NETCMN: server can not start oracle
  • ora-00357 : too many members specified for log file, the maximum is string
  • ora-13461 : the interleaving type is not supported
  • ora-26726 : logical standby and DOWNSTREAM_REAL_TIME_MINE are incompatible
  • 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.