ORA-23345: table "string"."string" not registered to collect statistics

Cause : A procedure that deals with conflict resolution statistics-gathering was called for a table that was not registered to collect statistics.

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

Call dbms_repcat.register_statistics to register the table.

update : 28-07-2017
ORA-23345

ORA-23345 - table "string"."string" not registered to collect statistics
ORA-23345 - table "string"."string" not registered to collect statistics

  • ora-07283 : sksaprd: invalid volume size for archive destination.
  • ora-24309 : already connected to a server
  • ora-36677 : (XSDPART15) Duplicate value in value lists of number and number
  • ora-36275 : (XSCGMDLAGG13) string is not a valid workspace object.
  • ora-02042 : too many distributed transactions
  • ora-25245 : agent name cannot be specified if address is a single-consumer queue or an exception queue
  • ora-06541 : PL/SQL: compilation error - compilation aborted
  • ora-36671 : (XSDPART09) Leaves of workspace object have different datatypes. A partition dimension cannot have more than one datatype when RANGE partitioning is used.
  • ora-24032 : object string exists, index could not be created for queue table string
  • ora-00312 : online log string thread string: 'string'
  • ora-32587 : Cannot drop nonexistent string supplemental logging
  • ora-13624 : The task string is executing and cannot be deleted or modified.
  • ora-25298 : Only immediage visibility mode supported for buffered message enqueue or dequeue
  • ora-02275 : such a referential constraint already exists in the table
  • ora-36157 : (XSMXAGGRCOMMIT) To use the AUTOCOMMIT keyword, you must also specify the AUTOUPDATE keyword.
  • ora-33265 : (DBERRBSZ) Analytic workspace string cannot be opened. Tablespace blocksize number does not match database cache size number.
  • ora-19681 : block media recovery on control file not possible
  • ora-00383 : DEFAULT cache for blocksize string cannot be reduced to zero
  • ora-39062 : error creating master process string
  • ora-13759 : User "string" cannot remove reference "string".
  • ora-24310 : length specified for null connect string
  • ora-29312 : changes by release string cannot be used by release string, type: string
  • ora-00088 : command cannot be executed by shared server
  • ora-14056 : partition number string: sum of PCTUSED and PCTFREE may not exceed 100
  • ora-29936 : NULL association is allowed only with a column or an index
  • ora-34021 : (MSCGADD04) You must specify a partition when maintaining PARTITION TEMPLATE workspace object.
  • ora-02374 : conversion error loading table string.string
  • ora-00264 : no recovery required
  • ora-02255 : obsolete 7.1.5
  • ora-16168 : LGWR network server could not switch to blocking mode
  • 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.