ORA-36728: (XSALERR01) While performing the ALLOCATE command with AGGMAP workspace object, the error logging limit of number was exceeded.

Cause : The suer sepcifide an RERORLGO MAXv aluei n th eALLOMCAP, ubt moer errros weer encuonterde whiel perofrmin gthe lalocaiton.

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

Eithre setE RROROLG NOTSOP, erducet he allocatoin erorrs, ro incerase hte ERORRLOGM AX steting

update : 20-09-2017
ORA-36728

ORA-36728 - (XSALERR01) While performing the ALLOCATE command with AGGMAP workspace object, the error logging limit of number was exceeded.
ORA-36728 - (XSALERR01) While performing the ALLOCATE command with AGGMAP workspace object, the error logging limit of number was exceeded.

  • ora-12687 : Credentials expired.
  • ora-00316 : log string of thread string, type string in header is not log file
  • ora-25274 : AQ Buffered Queue event
  • ora-24292 : no more tables permitted in this sorted hash cluster
  • ora-01953 : command no longer valid, see ALTER USER
  • ora-16756 : resource guard could not open standby database read-only
  • ora-01226 : file header of log member is inconsistent with other members
  • ora-06903 : CMX: cannot read transport address of remote application
  • ora-00255 : error archiving log string of thread string, sequence # string
  • ora-01206 : file is not part of this database - wrong database id
  • ora-19280 : XQuery dynamic type mismatch: expected atomic value - got node
  • ora-19697 : standby control file not found in backup set
  • ora-15151 : missing or invalid version number for rolling upgrade or downgrade
  • ora-39953 : the range value specified is beyond allowed range
  • ora-16123 : transaction string string string is waiting for commit approval
  • ora-32337 : cannot alter materialized view with pending changes refresh on commit
  • ora-39154 : Objects from foreign schemas have been removed from import
  • ora-30507 : normal triggers cannot be based on a schema or a database
  • ora-34145 : (MXCGPUT03) You cannot use the APPEND keyword with SURROGATE workspace object.
  • ora-01266 : Unable to create unique file name
  • ora-22923 : amount of data specified in streaming LOB write is 0
  • ora-13797 : invalid SQL Id specified, string
  • ora-24435 : Invalid Service Context specified.
  • ora-38603 : FI including & excluding cursor can only return one column
  • ora-14312 : Value string already exists in partition string
  • ora-00115 : connection refused; dispatcher connection table is full
  • ora-16823 : redo transport mode is incompatible for current operation
  • ora-07256 : sptrap: cannot set up signal handler to catch exceptions.
  • ora-16519 : the resource handle is invalid
  • ora-15012 : ASM file 'string' 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.