I have inherited a universe to maintain (BO 4.1.3) and there is a subclass with a dimension object which, whenever I try to use it in reports gives me the following Oracle error:
“ORA-01858: a non-numeric character was found where a numeric was expected :-1858”
I checked the Table.Column, data type where this object maps to and
the properties window in Designer of this object, and everything is fine! I did a refresh on the structure also but the problem persists.
I have inherited a universe to maintain (BO 4.1.3) and
there is a subclass with a dimension object which, whenever I try to use it in reports
gives me the following Oracle error:
“ORA-01858: a non-numeric character was found where a numeric was expected :-1858”
I checked the Table.Column, data type where this object maps to
and
the properties window in Designer of this object, and everything is fine!
I did a refresh on the structure also but the problem persists.
In designer, try using the “val” function. So in your Where clause, it should look something like this: Val(table name.column name) Hope this works for ya…but I haven’t tested this yet myself so no promises. Happy New Year!
In designer, try using the “val” function. So in your Where clause, it
should look something like this: Val(table name.column name) Hope this
works for ya…but I haven’t tested this yet myself so no promises. Happy
New Year!
In a message dated 98-12-31 09:17:49 EST, you write:
dimension object which, whenever I try to use it
in reports
gives me the following Oracle error:
“ORA-01858: a non-numeric character was found where a numeric was expected :-1858”
Often this is found in one of two situations.
The database value is supposed to be numeric (say an invoice number) but is stored in a character database column. In that case, your object should be defined as a character field. If you are trying to convert the value to a number via the TO_NUMBER() function, then you have to validate that the database column contains strictly numeric values or the function will fail. If you need this validation to be done, then please let me know. I have a fairly long formula that will validate numeric data in a character field, but it requires some explanation.
More common - you are converting a character field to a date, via the TO_DATE() function, and your date format does not exactly match what is specified in your database. In other words, if Oracle is expecting the date in a standard format of DD-MON-YY but you are using the function as TO_DATE(some_date,‘DD/MM/YY’) then you would see this error. The “non-numeric” value would be the month name.
It would help to solve your problem if you post the actual object definition, and more about the database format. Without that, these are just guesses! Hope that they help in any case.
In a message dated 98-12-31 09:17:49 EST, you write:
dimension object which, whenever I try to use it
in reports
gives me the following Oracle error:
“ORA-01858: a non-numeric character was found where a numeric was
expected :-1858”
Often this is found in one of two situations.
The database value is supposed to be numeric (say an invoice number) but is
stored in a character database column. In that case, your object should be
defined as a character field. If you are trying to convert the value to a
number via the TO_NUMBER() function, then you have to validate that the
database column contains strictly numeric values or the function will fail. If
you need this validation to be done, then please let me know. I have a fairly
long formula that will validate numeric data in a character field, but it
requires some explanation.
More common - you are converting a character field to a date, via the
TO_DATE() function, and your date format does not exactly match what is
specified in your database. In other words, if Oracle is expecting the date in
a standard format of DD-MON-YY but you are using the function as
TO_DATE(some_date,‘DD/MM/YY’) then you would see this error. The “non-numeric”
value would be the month name.
It would help to solve your problem if you post the actual object definition,
and more about the database format. Without that, these are just guesses! Hope
that they help in any case.