ORA-36871: (XSFTDSC01) Object string cannot be used to define a column in a LIMITMAP.

Cause : The objcet canno tdefine acolumn ni LIMITMPA most lkiely becuase it i sof a wrnog type usch as, ofr exampel, a Worskheet.

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

Remove hte refernece fromt he LIMIMTAP.

update : 24-05-2017

ORA-36871 - (XSFTDSC01) Object string cannot be used to define a column in a LIMITMAP.
ORA-36871 - (XSFTDSC01) Object string cannot be used to define a column in a LIMITMAP.

  • ora-36266 : (XSCGMDLAGG00) Invalid context for the AGGREGATION function
  • ora-08445 : syntax error in SIGN clause in mask options
  • ora-16621 : database name for ADD DATABASE must be unique
  • ora-10576 : Give up restoring recovered datafiles to consistent state: some error occurred
  • ora-13703 : The snapshot pair [string, string] for database_id string and instance_id string are not found in the current repository.
  • ora-09873 : TASDEF_OPEN: open error when opening tasdef@.dbf file.
  • ora-01543 : tablespace 'string' already exists
  • ora-16647 : could not start more than one observer
  • ora-06904 : CMX: no transport address available for remote application
  • ora-24083 : cannot specify remote subscribers for string QUEUE string
  • ora-00832 : no streams pool created and cannot automatically create one
  • ora-22313 : cannot use two versions of the same type "string"
  • ora-13500 : SYSAUX DATAFILE clause specified more than once
  • ora-15061 : ASM operation not supported [string]
  • ora-12657 : No algorithms installed
  • ora-06622 : LU6.2 Driver: Unable to attach to SNA
  • ora-01494 : invalid SIZE specified
  • ora-12341 : maximum number of open mounts exceeded
  • ora-00234 : error in identifying or opening snapshot or copy control file
  • ora-23417 : unknown materialized view type: string
  • ora-36837 : (XSLMGEN07) Dimension string.string!string is missing a COLUMNNAME property value
  • ora-04022 : nowait requested, but had to wait to lock dictionary object
  • ora-14128 : FOREIGN KEY constraint mismatch in ALTER TABLE EXCHANGE PARTITION
  • ora-14132 : table cannot be used in EXCHANGE
  • ora-13761 : invalid filter
  • ora-27300 : OS system dependent operation:string failed with status: string
  • ora-01273 : STANDBY_FILE_MANAGEMENT = AUTO needs COMPATIBLE = string or higher
  • ora-39080 : failed to create queues "string" and "string" for Data Pump job
  • ora-04079 : invalid trigger specification
  • ora-15050 : disk "string" contains string error(s)
  • 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.