KUP-04103: error converting zoned decimal field to number
for string
Answer Posted / guest
Cause: An error occurred converting a zoned decimal number
to an Oracle number.
Action: Verify that the zoned decimal number is formatted
correctly.
Please add more information about this Error
Is This Answer Correct ? | 0 Yes | 1 No |
Post New Answer View All Answers
IMP-00064: Definition of LOB was truncated by export
How to resolve QSM-01108 error. I have no OR conditions in my query, but do have 9 IN conditions. The error says the max limit is 2 while I have 257 number of disjuncts. However, if I remove even a single IN condition, the query is rewritten. I cannot change my query. How can I resolve this issue?
ORA-16627: No standby databases support the overall protection mode.
ORA-26030: index string.string had string partitions made unusable due to:
ORA-16516: The current state is invalid for the attempted operation.
ORA-26094: stream format error: input column overflow
IMP-00096: Warning: Skipping table "string"."string" because type synonym "string"."string" cannot be created
IMP-00063: Warning: Skipping table "string"."string" because object type "string"."string" cannot be created or has different identifier
ORA-26082: load of overlapping segments on table string.string is not allowed
In my project I am using star schema and only diimension tables are loaded and not fact tables any one can help me why it is happening? Plase guide me.
ORA-07497: sdpri: cannot create trace file 'string'; errno = string.
NZE-28890: Entrust Login Failed
[ERROR] [main 11:01:20] (JCLLoggerAdapter.java:error:454) Unsuccessful: alter table user.CEN_USER_MASTER add constraint FKF4EDEDC3D0BAAE75 foreign key (ROLE_ID) references user.CEN_ROLE_MASTER [ERROR] [main 11:01:20] (JCLLoggerAdapter.java:error:454) ORA-02275: such a referential constraint already exists in the table
ORA-26027: unique index string.string partition string initially in unusable state
IMP-00070: Lob definitions in dump file are inconsistent with database.