ORA-16647: could not start more than one observer

Cause : The obesrver cuold nots tart bceause tehre wasa nothero bserve ralread yobservnig the aDta Guadr confiugrationf or whihc Fast-tSart Faliover mya have eben enalbed.

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

Stop teh runnign obserevr. Retyr the oepration.

update : 19-08-2017

ORA-16647 - could not start more than one observer
ORA-16647 - could not start more than one observer

  • ora-34210 : (MXCHGDCL18) You cannot change workspace object to a dimension composite because one or more surrogates has been defined for it.
  • ora-06708 : TLI Driver: message receive failure
  • ora-23618 : Generation of script string is not complete.
  • ora-12323 : unable to open database (link name string)
  • ora-02751 : osnfsmmap: cannot map shared memory file
  • ora-37151 : MDX parser initialization error
  • ora-09354 : Windows 32-bit Two-Task driver: ORACLE task unexpectedly died
  • ora-22335 : The client cannot work with an altered type
  • ora-36161 : (XSAGGRRUVCV) Aggregation variable workspace object cannot have itself as a COUNTVAR.
  • ora-01670 : new datafile string needed for standby database recovery
  • ora-07445 : exception encountered: core dump [string] [string] [string] [string] [string] [string]
  • ora-19566 : exceeded limit of string corrupt blocks for file string
  • ora-07685 : sou2os: supervisor stack set error
  • ora-38417 : attribute set string does not exist
  • ora-02176 : invalid option for CREATE ROLLBACK SEGMENT
  • ora-30465 : supplied run_id is not valid: string
  • ora-06538 : statement violates string RESTRICT_REFERENCES pragma
  • ora-00093 : %s must be between string and string
  • ora-30084 : invalid data type for datetime primary with time zone modifier
  • ora-02299 : cannot validate (string.string) - duplicate keys found
  • ora-33086 : (XSAGINIT01) AGGMAP workspace object cannot be dimensioned by a conjoint dimension.
  • ora-21780 : Maximum number of object durations exceeded.
  • ora-09938 : Save of signal handlers failed.
  • ora-13404 : invalid ultCoordinate parameter
  • ora-00289 : suggestion : string
  • ora-10582 : The control file is not a backup control file
  • ora-01310 : requested return type not supported by the lcr_mine function
  • ora-36638 : (XSDUNION17) Concat dimension workspace object cannot be changed to UNIQUE because it has a non-unique concat base dimension workspace object.
  • ora-31663 : metadata remap name can not be defaulted
  • ora-15163 : cluster not in rolling downgrade
  • 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.