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-08-2017
ORA-36871

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-39115 : %s is not supported over a network link
  • ora-02084 : database name is missing a component
  • ora-19644 : datafile string: incremental-start SCN is prior to resetlogs SCN string
  • ora-09311 : slsleep: error temporarily suspending process
  • ora-10900 : extent manager fault insertion event #string
  • ora-14305 : List value 'string' specified twice in partition 'string'
  • ora-06420 : NETCMN: SID lookup failure
  • ora-32844 : exceeded maximum number of string values
  • ora-16238 : attempt to use version 9 log
  • ora-29656 : Invalid option for USING
  • ora-14000 : only one LOCAL clause may be specified
  • ora-07219 : slspool: unable to allocate spooler argument buffer.
  • ora-32406 : cannot alter partitioning for existing materialized view log
  • ora-01290 : cannot remove unlisted logfile string
  • ora-01876 : year must be at least -4713
  • ora-27366 : job "string.string" is not running
  • ora-28031 : maximum of string enabled roles exceeded
  • ora-19110 : unsupported XQuery expression
  • ora-02153 : invalid VALUES password string
  • ora-02243 : invalid ALTER INDEX or ALTER MATERIALIZED VIEW option
  • ora-30444 : rewrite terminated by the sql analyzer
  • ora-00166 : remote/local nesting level is too deep
  • ora-14059 : partition "string": INITRANS value must be less than MAXTRANS value
  • ora-32014 : error processing parameter "string" from the SPFILE restore image
  • ora-01914 : invalid auditing option for sequence numbers
  • ora-07825 : sspsck: $QIO failure at AST level
  • ora-02056 : 2PC: string: bad two-phase command number string from string
  • ora-30767 : OID type mismatch
  • ora-16512 : parameter exceeded maximum size limit
  • ora-02028 : fetching an exact number of rows is not supported by the server
  • 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.