How to Solve :
not string's tag archives
Oracle Database Error Code ORA-36210 Description :
(XSAGOP05R) In AGGMAP workspace object, you can only specify the REMOPERATOR string with the PROPORTIONAL, EVEN, or HEVEN operators, not string.
Error Cause:
The user specified a REMOPERATOR without using PROPORTIONAL, EVEN, or HEVEN.
How to Solve :
Remove the REMOPERATOR clause from the RELATION line.
Filed under: How to Solve, Oracle 10g, Oracle 11g, Oracle 9i, Oracle Error Codes Etiketler: EVEN, not string, or HEVEN operators, ora - 36210, you can only specify the REMOPERATOR string with the PROPORTIONAL, (XSAGOP05R) In AGGMAP workspace object, 36210, about oracle ORA-36210 error, help ORA-36210 about, ORA-36210 error code, ORA-36210 problem, Oracle 9i 10g 11g, Oracle Database Server Error Messages, Oracle Error Codes, oracle number 36210 error code, oracle ORA-36210 example
No Comment Yet
No Comment Yet
Oracle Database Error Code ORA-36212 Description :
(XSAGOP06) In AGGMAP workspace object, you can only specify the MIN, MAX, FLOOR, and CEILING arguments while using the PROPORTIONAL operator, not string.
Error Cause:
The user specified MIN, MAX, FLOOR, or CEILING when using an operator other than PROPORTIONAL.
How to Solve :
Remove the incorrect argument from the RELATION line.
Oracle Database Error Code ORA-36170 Description :
(XSMXAGGR12) The data type of the WEIGHT workspace object must be numeric or BOOLEAN, not string.
Error Cause:
The user specified a WEIGHT variable or formula which wasnt numeric or boolean
How to Solve :
Specify a numerical or boolean weight instead
Oracle Database Error Code ORA-36162 Description :
(XSMXAGGR05) COUNTVAR variable workspace object must be of type INTEGER, not string.
Error Cause:
The user specified a non-INTEGER variable as a COUNTVAR for aggregation
How to Solve :
Redefine the COUNTVAR to be an INTEGER
Oracle Database Error Code ORA-1222 Description :
MAXINSTANCES of string requires MAXLOGFILES be at least string, not string
Error Cause:
Attemping to create a database or control file that does not have room for at least two logs per thread of redo. A thread of redo must have two online logs in order to be enabled. It does not make sense to allow more redo threads than can be supported by the logs.
How to Solve :
Either reduce the MAXINSTANCES argument or increase MAXLOGFILES.
Search Oracle Error Codes and Descriptions:
Recent Entries
- Oracle database error code ORA-31604 – invalid string parameter “string” for object type string in function string
- Oracle database error code ORA-29961 – too many warnings occurred in the execution of ODCIIndex DDL routine
- Oracle database error code ORA-31603 – object “string” of type string not found in schema “string”
- Oracle database error code ORA-29960 – line string, string
- Oracle database error code ORA-31602 – parameter string value “string” in function string inconsistent with string
- Oracle database error code ORA-29964 – missing ADD or DROP keyword
- Oracle database error code ORA-31606 – XML context number does not match any previously allocated context