ORA-36873: (XSTFDSC03) Column type must be specified explicitly.

Cause : Missing column type specification.

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

Please, make sure to specify a column type in COLUMN MAP. Normally, users should not call OLAP Random Access Cursor table function themselves and therefore should not encounter this error.

update : 16-08-2017
ORA-36873

ORA-36873 - (XSTFDSC03) Column type must be specified explicitly.
ORA-36873 - (XSTFDSC03) Column type must be specified explicitly.

  • ora-30066 : test support - drop rollback segment wait
  • ora-09787 : sllfop: unrecognizable processing option, incorrect format.
  • ora-21301 : not initialized in object mode
  • ora-16401 : archivelog rejected by RFS
  • ora-19590 : conversation already active
  • ora-14631 : the partition bounds do not match the subpartition bounds of the partition
  • ora-06957 : No SID is currently available
  • ora-24186 : wrong object type, could not transform message
  • ora-13853 : Tracing for service (module/action) string is already enabled
  • ora-02062 : distributed recovery received DBID string, expected string
  • ora-09851 : soacon: Archmon unable to lock named pipe.
  • ora-09301 : osncon: local kernel only supported in standard mode
  • ora-32319 : Cannot use direct loader log to FAST REFRESH materialized view "string"."string"
  • ora-28111 : insufficient privilege to evaluate policy predicate
  • ora-14299 : total number of partitions/subpartitions exceeds the maximum limit
  • ora-37105 : (XSVPART05) Only variables dimensioned by a CONCAT PARTITION TEMPLATE can have string partitions.
  • ora-33918 : (MAKEDCL33) You cannot define a surrogate of dimension workspace object because it is a string.
  • ora-01548 : active rollback segment 'string' found, terminate dropping tablespace
  • ora-02349 : invalid user-defined type - type is incomplete
  • ora-14626 : values being added already exist in DEFAULT subpartition
  • ora-13148 : failed to generate SQL filter
  • ora-19028 : Invalid ADT parameter passed to toObject() function
  • ora-08184 : attempting to re-enable Flashback while in Flashback mode
  • ora-02767 : Less than one request descriptor was allocated per server
  • ora-14097 : column type or size mismatch in ALTER TABLE EXCHANGE PARTITION
  • ora-12500 : TNS:listener failed to start a dedicated server process
  • ora-22998 : CLOB or NCLOB in multibyte character set not supported
  • ora-19646 : cannot change size of datafile string from string to string
  • ora-19700 : device type exceeds maximum length of string
  • ora-00478 : SMON process terminated due to error string
  • 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.