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 : 16-08-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-12021 : materialized view "string"."string" is corrupt
  • ora-00213 : cannot reuse control file; old file size string, string required
  • ora-40226 : model upgrade/downgrade must be performed by SYS
  • ora-29842 : option not supported with the version string of the indextype interface
  • ora-06700 : TLI Driver: incorrect message type from host
  • ora-02494 : invalid or missing maximum file size in MAXSIZE clause
  • ora-38500 : %s
  • ora-16711 : the resource guard index is out of bounds
  • ora-14110 : partitioning column may not be of type ROWID
  • ora-23426 : deferred RPC queue has entries for string
  • ora-29376 : number of consumer groups string in top-plan string exceeds string
  • ora-15091 : operation incompatible with open handle in this session
  • ora-30160 : Unable to access the file
  • ora-00476 : RECO process terminated with error
  • ora-01153 : an incompatible media recovery is active
  • ora-16129 : unsupported dml encountered
  • ora-29881 : failed to validate indextype
  • ora-16813 : log apply service not running on apply instance string recorded by the broker
  • ora-22978 : only simple attribute name is allowed in the WITH OBJECT OID clause
  • ora-34487 : (MXMAINT08) You cannot string values of non-unique concat dimension workspace object.
  • ora-24185 : transformation string.string does not exist
  • ora-00334 : archived log: 'string'
  • ora-01240 : too many data files to add in one command
  • ora-08450 : invalid specification of CR in picture mask
  • ora-22890 : cannot specify name for REF column constraint
  • ora-39601 : Hash key is required.
  • ora-16956 : Only SELECT or DML statements are supported for test execute.
  • ora-07584 : spdcr: invalid value for ORA_sid_(proc_)PQL$_item
  • ora-39306 : schema name mismatch expected "string" got "string"
  • ora-13276 : internal error [string] in coordinate transformation
  • 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.