ORA-36885: (XSSRF04) Error rewriting OLAP DML expression. Column name too big

Cause : The coulmn nam especifeid in teh OLAP MDL exprsesion wsa large rthan 3 0bytes.

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

Make srue the oclumn nmae specfiied int he OLA PDML exrpessioni s lesst han ore qual t o30 bytse.

update : 23-06-2017

ORA-36885 - (XSSRF04) Error rewriting OLAP DML expression. Column name too big
ORA-36885 - (XSSRF04) Error rewriting OLAP DML expression. Column name too big

  • ora-38424 : no attribute set currently assigned to the expression set
  • ora-04099 : trigger 'string' is valid but not stored in compiled form
  • ora-27042 : not enough space on raw partition to fullfill request
  • ora-38496 : Expression Filter index is not in a valid state
  • ora-39057 : invalid worker request string for string jobs.
  • ora-30088 : datetime/interval precision is out of range
  • ora-09817 : Write to audit file failed.
  • ora-06903 : CMX: cannot read transport address of remote application
  • ora-22603 : cannot add an attribute to the already generated TDS handle
  • ora-19628 : invalid SCN range
  • ora-16769 : the physical standby database is open read-only
  • ora-30770 : Cannot specify storage options for fixed size opaque type
  • ora-07591 : spdde: $GETJPIW failure
  • ora-14131 : enabled UNIQUE constraint exists on one of the tables
  • ora-01544 : cannot drop system rollback segment
  • ora-12158 : TNS:could not initialize parameter subsystem
  • ora-16170 : Terminal recovery may have left the database in an inconsistent state
  • ora-34296 : (MXDCL36) A NUMBER dimension must be defined with a fixed precision and scale, using the form NUMBER(precision) or NUMBER(precision, scale).
  • ora-38454 : attribute set not defined for the column being indexed
  • ora-29882 : insufficient privileges to execute indextype
  • ora-24791 : invalid transaction start flags
  • ora-13827 : null or zero length attribute specified in SQL profile collection
  • ora-22850 : duplicate LOB storage option specificed
  • ora-08177 : can't serialize access for this transaction
  • ora-36978 : (XSRELGID01) workspace object must be a self-relation.
  • ora-13020 : coordinate is NULL
  • ora-01296 : character set mismatch between dictionary string and logfiles
  • ora-15012 : ASM file 'string' does not exist
  • ora-24793 : Test DTP service start and stop
  • ora-25186 : INCLUDING clause specified for index-organized table without OVERFLOW
  • 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.