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 : 25-09-2017
ORA-23497

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

  • ora-31196 : XML nodes over string in size cannot be printed
  • ora-02179 : valid options: ISOLATION LEVEL { SERIALIZABLE | READ COMMITTED }
  • ora-06554 : package DBMS_STANDARD must be created before using PL/SQL
  • ora-01154 : database busy. Open, close, mount, and dismount not allowed now
  • ora-29342 : user string does not exist in the database
  • ora-14116 : partition bound of partition "string" is too long
  • ora-13443 : GeoRaster metadata SRS error
  • ora-33002 : (XSAGDNGL00) In AGGMAP workspace object, the FLOOR argument of number must be less than the CEILING argument of number.
  • ora-13218 : max number of supported index tables reached for [string] index
  • ora-32306 : updatable materialized views with user-defined types must use SELECT *
  • ora-23610 : internal dbms_streams_tablespaces error: [string] [string] [string] [string]
  • ora-33092 : (XSAGCOMP04) number is not the name of a MODEL in any attached analytic workspace.
  • ora-32314 : REFRESH FAST of "string"."string" unsupported after deletes/updates
  • ora-38467 : user cannot GRANT/REVOKE privileges to/from himself
  • ora-03236 : max # extents (string) reached in index string.string subpartition string
  • ora-10640 : Operation not permitted during SYSTEM tablespace migration
  • ora-19638 : file string is not current enough to apply this incremental backup
  • ora-06793 : TLI Driver: server cannot create new process
  • ora-12012 : error on auto execute of job string
  • ora-25966 : join index cannot be based on an index organized table
  • ora-27065 : cannot perform async vector I/O to file
  • ora-19691 : %s is from different database: id=string, name=string
  • ora-27004 : invalid blocksize specified
  • ora-13448 : GeoRaster metadata BRS error
  • ora-25132 : UNIQUE constraint (string.string) disabled and validated in ALTER TABLE EXCHANGE PARTITION
  • ora-25182 : feature not currently available for index-organized tables
  • ora-29366 : invalid CONSUMER_GROUP argument specified
  • ora-29506 : invalid query derived from USING clause
  • ora-16082 : logical standby is not initialized correctly
  • ora-01129 : user's default or temporary tablespace does not exist
  • 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.