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 : 24-04-2017
ORA-36885

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-27057 : cannot perform async I/O to file
  • ora-03202 : the scan limit specification is invalid
  • ora-12712 : new character set must be a superset of old character set
  • ora-31524 : could not find change set string for CDC change table string.string
  • ora-31028 : Resource metadata length string exceeded maximum length string
  • ora-14081 : new partition name must differ from the old partition name
  • ora-10643 : Database should be mounted in restricted mode and Exclusive mode
  • ora-22982 : cannot create sub-view under this view
  • ora-16807 : unable to change database protection mode
  • ora-24817 : Unable to allocate the given chunk for current lob operation
  • ora-26031 : index maintenance error, the load cannot continue
  • ora-02169 : FREELISTS storage option not allowed
  • ora-15027 : active use of diskgroup "string" precludes its dismount
  • ora-15123 : ASM file name 'string' contains an invalid incarnation number
  • ora-14022 : creation of LOCAL partitioned cluster indices is not supported
  • ora-25448 : rule string.string has errors
  • ora-25439 : duplicate variable value for variable: string
  • ora-23456 : flavor string does not contain "string"
  • ora-14400 : inserted partition key does not map to any partition
  • ora-19043 : Multiply nested XMLROOT function disallowed
  • ora-26098 : direct path context is not prepared
  • ora-02040 : remote database string does not support two-phase commit
  • ora-01580 : error creating control backup file string
  • ora-22160 : element at index [string] does not exist
  • ora-01159 : file is not from same database as previous files - wrong database id
  • ora-06567 : invalid number of values specified
  • ora-02357 : no valid dump files
  • ora-07706 : error in archive text: need disk file name
  • ora-00036 : maximum number of recursive SQL levels (string) exceeded
  • ora-24419 : Proxy sessions are not supported in this mode.
  • 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.