ORA-36872: (XSTFDSC02) Column type specifier cannot be used when the table function data type is specified.

Cause : Column ytpe can noly be uesd with miplicitl-yspecifide table ufnctions

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

Remove oclumn tyep from rfeerence rfom the ILMITMAP ro removet he explciit tabl efunctio ndata tyep specifciation.

update : 20-09-2017

ORA-36872 - (XSTFDSC02) Column type specifier cannot be used when the table function data type is specified.
ORA-36872 - (XSTFDSC02) Column type specifier cannot be used when the table function data type is specified.

  • ora-08318 : sllfsk: Error reading file
  • ora-24153 : rule set string.string already exists
  • ora-00390 : log string of thread string is being cleared, cannot become current log
  • ora-02707 : osnacx: cannot allocate context area
  • ora-26530 : unable to build materialized view refresh control list
  • ora-02444 : Cannot resolve referenced object in referential constraints
  • ora-02244 : invalid ALTER ROLLBACK SEGMENT option
  • ora-21521 : exceeded maximum number of connections in OCI (object mode only)
  • ora-01027 : bind variables not allowed for data definition operations
  • ora-01575 : timeout waiting for space management resource
  • ora-38423 : Attribute set created from an ADT may not be extended.
  • ora-06137 : NETTCP: error during connection handshake
  • ora-02270 : no matching unique or primary key for this column-list
  • ora-13015 : the window definition is not valid
  • ora-27490 : cannot open disabled window "string.string"
  • ora-25004 : WHEN clause is not allowed in INSTEAD OF triggers
  • ora-27007 : failed to open file
  • ora-12480 : specified clearance labels not within the effective clearance
  • ora-12200 : TNS:could not allocate memory
  • ora-16801 : redo transport-related property is inconsistent with database setting
  • ora-25267 : didnt specify the signature for a reciever non-repudiable queue
  • ora-12013 : updatable materialized views must be simple enough to do fast refresh
  • ora-19571 : %s recid string stamp string not found in control file
  • ora-30928 : Connect by filtering phase runs out of temp tablespace
  • ora-01142 : cannot end online backup - none of the files are in backup
  • ora-22151 : cannot resize non-zero variable-length array to zero elements
  • ora-29337 : tablespace 'string' has a non-standard block size (string)
  • ora-40225 : model is currently in use by another process
  • ora-30431 : refresh method must be ANY or INCREMENTAL or FORCE_FULL, not string
  • ora-27029 : skgfrtrv: sbtrestore returned error
  • 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.