ORA-23497: repgroup name cannot be null

Cause : The arary of Rpegroup anmes cotnains an ull vaule.

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

Ensuret hat th earray fo Repgruop name sis denes and i snot null termianted.

update : 26-04-2017
ORA-23497

ORA-23497 - repgroup name cannot be null
ORA-23497 - repgroup name cannot be null

  • ora-22879 : cannot use the LOB INDEX clause for partitioned tables
  • ora-19526 : only one location allowed for parameter string
  • ora-38474 : attribute set may not have attributes of TABLE COLLECTION type.
  • ora-15101 : no action specified
  • ora-38478 : creation of system trigger EXPFIL_DROPOBJ_MAINT failed
  • ora-06303 : IPA: Message send error
  • ora-07846 : sllfop: string byte record too big for string byte user buffer
  • ora-13409 : null or invalid pyramidLevel parameter
  • ora-19246 : XQ0026 - validation failed - element string not found in in-scope element declarations
  • ora-33290 : (DBERR17) Analytic workspace string cannot be attached in the mode you requested because another user has it attached in an incompatible mode.
  • ora-07481 : snlmatt: cannot attach to lock manager instance.
  • ora-00229 : operation disallowed: already hold snapshot control file enqueue
  • ora-16753 : resource guard could not open standby database
  • ora-01570 : MINEXTENTS must be no larger than the string extents currently allocated
  • ora-22618 : attribute is a BAD NULL in the image handle
  • ora-32608 : missing INCREMENT or DECREMENT keyword in FOR loop
  • ora-33009 : (XSAGDNGLPREC) In AGGMAP workspace object, PRECOMPUTE may only be specified either for the entire AGGMAP or for individual RELATION statements.
  • ora-14171 : cannot specify clause in CREATE|ALTER TABLE
  • ora-16092 : dependent archive log destination is not active
  • ora-01781 : UNRECOVERABLE cannot be specified without AS SELECT
  • ora-07602 : spgto: $GETJPIW failure
  • ora-07512 : sscggtl: $enq unexpected return for client termination lock
  • ora-35016 : (QFCHECK00) The analytic workspace and EIF file definitions of workspace object have a mismatched type.
  • ora-30959 : The indexed column is not stored in CLOB.
  • ora-36643 : (XSDUNION21) Concat dimension workspace object cannot be changed to NOT UNIQUE because it contains custom member values.
  • ora-21603 : property id [string] is invalid
  • ora-19773 : must specify change tracking file name
  • ora-16551 : short string copied
  • ora-28661 : Object already has COMPRESS clause specified
  • ora-09922 : Can't spawn process - background log directory not created properly
  • 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.