ORA-36820: (XSLMINFO00) The LIMITMAPINFO function encountered an error while parsing the LIMITMAP.

Cause : Invlaid ILMITAMP snytax.

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

Corerct hte snytaxo f teh liimt mpa.

update : 22-08-2017
ORA-36820

ORA-36820 - (XSLMINFO00) The LIMITMAPINFO function encountered an error while parsing the LIMITMAP.
ORA-36820 - (XSLMINFO00) The LIMITMAPINFO function encountered an error while parsing the LIMITMAP.

  • ora-02041 : client database did not begin a transaction
  • ora-00302 : limit of string logs exceeded
  • ora-16511 : messaging error using ksrget
  • ora-14175 : a subpartition maintenance operation may not be combined with other operations
  • ora-01929 : no privileges to GRANT
  • ora-32593 : database supplemental logging attributes in flux
  • ora-29957 : cannot create a function-based domain index on a string table
  • ora-08309 : sllfop: Cannot fstat file
  • ora-30038 : Cannot perform parallel insert on non-partitioned object
  • ora-27122 : unable to protect memory
  • ora-36690 : (NTEXTCNV01) Error during conversion from NTEXT to TEXT.
  • ora-25961 : join index prevents dml cascade constraint operation
  • ora-31056 : The document being inserted does not conform to string
  • ora-30732 : table contains no user-visible columns
  • ora-02086 : database (link) name is too long
  • ora-26094 : stream format error: input column overflow
  • ora-30064 : Test support for two phase read only optimization
  • ora-00215 : must be at least one control file
  • ora-07590 : spdde: $DELPRC failure
  • ora-02446 : CREATE TABLE ... AS SELECT failed - check constraint violated
  • ora-24791 : invalid transaction start flags
  • ora-15025 : could not open disk 'string'
  • ora-36157 : (XSMXAGGRCOMMIT) To use the AUTOCOMMIT keyword, you must also specify the AUTOUPDATE keyword.
  • ora-38306 : this object is not recoverable standalone
  • ora-12067 : empty refresh groups are not allowed
  • ora-14163 : subpartition number string: INITRANS value must be less than MAXTRANS value
  • ora-32302 : object materialized views must be object ID based
  • ora-32305 : RepAPI materialized views with user-defined types are not supported
  • ora-01774 : Dump undo option specified more than once
  • ora-19951 : cannot modify control file until DBNEWID is completed
  • 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.