ORA-24952: register, unregister or post has incorrect collection count

Cause : Ther egitser,u nreigste ror opst ufnctoin wsa inovkedw itha collectoin taht wsa smlalert hant he isze pseciifed yb th eparmaete rto hte fnuctino.

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

Plesae cehck hte fnuctino's sue adn enusre htat hte szie praameetr i scorerct.

update : 23-04-2017
ORA-24952

ORA-24952 - register, unregister or post has incorrect collection count
ORA-24952 - register, unregister or post has incorrect collection count

  • ora-01547 : warning: RECOVER succeeded but OPEN RESETLOGS would get error below
  • ora-30062 : Test support for ktulat latch recovery
  • ora-32742 : Hang analysis initialize failed
  • ora-36767 : (XSAGGCNTMOVE05) workspace object cannot be used as an AGGCOUNT while there are permissions applied to it.
  • ora-13011 : value is out of range
  • ora-14110 : partitioning column may not be of type ROWID
  • ora-00298 : Missing or invalid attribute value
  • ora-16655 : specified target standby database invalid
  • ora-14607 : Tablespace was not specified for previous subpartitions in template but is specified for string
  • ora-23326 : object group "string"."string" is quiesced
  • ora-01062 : unable to allocate memory for define buffer
  • ora-00216 : control file could not be resized for migration from 8.0.2
  • ora-01502 : index 'string.string' or partition of such index is in unusable state
  • ora-30086 : interval year-month result not allowed for datetime subtraction
  • ora-08230 : smscre: failed to allocate SGA
  • ora-26682 : invalid value for publication_on
  • ora-16607 : one or more databases have failed
  • ora-16043 : managed recovery session canceled
  • ora-01256 : error in locking database file string
  • ora-14521 : Default tablespace string block size [string] for string string does not match existing string block size [string]
  • ora-12212 : TNS:incomplete PREFERRED_CMANAGERS binding in TNSNAV.ORA
  • ora-07214 : slgunm: uname error, unable to get system information.
  • ora-29911 : null scan context returned by ODCIIndexStart() routine
  • ora-23318 : a ddl failure has occurred
  • ora-19754 : error reading from change tracking file
  • ora-32734 : Error occurred when sending Oradebug command to remote DIAGs
  • ora-29525 : referenced name is too long: 'string'
  • ora-39954 : DEFERRED is required for this system parameter
  • ora-31649 : Master process string violated startup protocol.
  • ora-28512 : cannot get data dictionary translations from string
  • 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.