ORA-23434: master site string not known for object group

Cause : The siet name igven asa n arguemnt to aroutin ewas no talread yknown ot the rpelicate dobjectg roup.

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

Execut ethe dbsm_offlien_og.beign_instnatiatio(n) routnie to add a news ite tot he repilcated boject gorup.

update : 25-06-2017
ORA-23434

ORA-23434 - master site string not known for object group
ORA-23434 - master site string not known for object group

  • ora-31478 : could not detach LogMiner session after change set advance
  • ora-23619 : non-Oracle system error: string
  • ora-02146 : SHARED specified multiple times
  • ora-38464 : expression set is not empty.
  • ora-33920 : (MAKEDCL34) The string SURROGATE must have one of the following data types: ID, NTEXT, TEXT, NUMBER, or INTEGER.
  • ora-19562 : file string is empty
  • ora-31670 : Username argument must be specified and non-null.
  • ora-16740 : redo transport service for standby database "string" incorrectly set to ALTERNATE
  • ora-00712 : cannot rename system tablespace
  • ora-39144 : file name parameter must be specified and non-null
  • ora-31103 : Resource locked in shared mode. Cannot add exclusive lock
  • ora-16783 : instance string not open for read and write access
  • ora-06978 : X.25 Driver: Too many callback tries
  • ora-12635 : No authentication adapters available
  • ora-19255 : XQ0035 - too many declarations of string in imported schemas
  • ora-06120 : NETTCP: network driver not loaded
  • ora-29842 : option not supported with the version string of the indextype interface
  • ora-19566 : exceeded limit of string corrupt blocks for file string
  • ora-00976 : LEVEL, PRIOR, or ROWNUM not allowed here
  • ora-29371 : pending area is not active
  • ora-01239 : database must be in ARCHIVELOG mode to use external cache
  • ora-33008 : (XSAGDNGL03) The relation workspace object is not a relation over a base dimension of AGGMAP workspace object.
  • ora-13770 : Baseline "string" does not exist.
  • ora-32118 : Cannot perform operation on a null FILE
  • ora-24781 : branches don't belong to the same global transaction
  • ora-02035 : illegal bundled operation combination
  • ora-10576 : Give up restoring recovered datafiles to consistent state: some error occurred
  • ora-13850 : Tracing for client identifier string is not enabled
  • ora-09361 : Windows 3.1 Two-Task driver unable to lock context area
  • ora-22296 : invalid ALTER TABLE option for conversion of LONG datatype to LOB
  • 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.