Oracle Database Errors or Warnings from Error ORA-36812 to ORA-36825
ORA-36812: (XSTBLFUNC06) Invalid Syntax at ‘?’.
Cause: The limitmap has a question mark character outside the context of a string.
Action: Fix the limitmap
ORA-36814: (XSTBLFUNC07) The datatype of the column used in the ROW2CELL clause of a LIMITMAP must be RAW(16).
Cause: Datatype of column used in ROW2CELL clause of a LIMITMAP is not RAW(16).
Action: Change datatype to RAW(16).
ORA-36815: (XSTBLFUNC08) The OLAP_TABLE has attempted to use an AW single row function with the aw_attach parameter set to DURATION QUERY.
Cause: The OLAP_TABLE aw_attach parameter was set to DURATION QUERY.
Action: Change the OLAP_TABLE aw_attach parameter to DURATION SESSION.
ORA-36816: (XSTBLFUNC09) The workspace object dimension is of datatype string which does not support custom member upserts.
Cause: Custom members were attempted to be added via an upsert to a dimension that does not support them
Action: Disable the AW Hash optimization for this query
ORA-36817: (XSTBLFUNC10) The LIMITMAP LOOP clause specifies an invalid type of object. workspace object must be a DIMENSION or COMPOSITE.
Cause: An invalid type of object was specified in the LOOP clause.
Action: Correct the LOOP clause.
ORA-36818: (XSTBLFUNC11) A LIMITMAP DIMENSION clause specifies an invalid type of object. workspace object must be a DIMENSION.
Cause: An invalid type of object was specified in the DIMENSION clause.
Action: Correct the DIMENSION clause.
ORA-36819: (XSTBLFUNC12) workspace object cannot be used in a LIMITMAP string clause.
Cause: An invalid type of object was specified in a LIMITMAP clause.
Action: Correct the LIMITMAP clause.
ORA-36820: (XSLMINFO00) The LIMITMAPINFO function encountered an error while parsing the LIMITMAP.
Cause: Invalid LIMITMAP syntax.
Action: Correct the syntax of the limit map.
ORA-36821: (XSJPUSH00) An error occurred while attempting to push a join of 2 AW tables.
Action: Re-execute the query with parameter _optimizer_aw_join_push_enabled = FALSE.
ORA-36825: (XSTBLFUNC13) An error occurred expanding the cube_name argument in the OLAP table function
Cause: Incorrect metadata or invalid cube name
Action: Correct the metadata.
Above are list of Oracle Database Errors or Warnings from Error ORA-36812 to ORA-36825 received while performing certain operation against Oracle Database or related products.
What are atOracle Database Error Messages?
Oracle Error Messages may be returned while using products which are part of Oracle Database. Each Oracle Dabase Error or Warning Message mentioned above contains the Warning or Error Message Statement, a short explanation of the probable causes of the Error message, and a recommended action.
Hope this was helpful.
Information about Oracle Database Error Messages or Warning Messages on Windows and Linux Operating Systems.