PCB-00301: Use of non-ANSI function is an Oracle extension
- 1 Answers
- 2129 Views
- I also Faced
- E-Mail Answers
Answer Posted / guest
Cause: An Oracle extension to the ANSI/ISO SQL standard was
used. Specifically, a non-ANSI function was used. This
informational message is issued by the FIPS Flagger when
FIPS=YES.
Action: No action is required. However, for ANSI/ISO
compliance, do not use this function.
Please add more information about this Error
| Is This Answer Correct ? | 0 Yes | 0 No |
Post New Answer View All Answers
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-26032: index string.string loading aborted after string keys
ORA-26030: index string.string had string partitions made unusable due to:
IMP-00063: Warning: Skipping table "string"."string" because object type "string"."string" cannot be created or has different identifier
ORA-16627: No standby databases support the overall protection mode.
ORA-26029: index string.string partition string initially in unusable state
RMAN-05017: no copy of datafile number found to recover
invalid quantity specification negative quantity are not allowed for this item please check this item definition quantity
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-26028: index string.string initially in unusable state
ORA-26079: file "string" is not part of table string.string
when i ran any workflow or session, getting below error: seesion task instance[s_xxx]: Execution terminated unexpecterdly
ORA-26084: direct path context already finished
ORA-26027: unique index string.string partition string initially in unusable state
IMP-00070: Lob definitions in dump file are inconsistent with database.
