PCC-02374: SQLCHECK value exceeds command line value
Answer Posted / guest
Cause: The value given to the SQLCHECK option in an EXEC
ORACLE statement in a program was greater than the value
given either on the command line or greater than the default
value if no SQLCHECK option was given on the command line.
The order of the option values is SEMANTICS>SYNTAX>NONE.
When this warning message is issued, the original value of
SQLCHECK (the default or the command-line value) stays in
effect.
Action: Remove or recode the EXEC Oracle option(s) in the
.pc source file to avoid this warning message.
Please add more information about this Error
| Is This Answer Correct ? | 0 Yes | 0 No |
Post New Answer View All Answers
ORA-16627: No standby databases support the overall protection mode.
RMAN-05017: no copy of datafile number found to recover
ORA-26094: stream format error: input column overflow
ORA-26082: load of overlapping segments on table string.string is not allowed
When i am connect database through toad,one error occured. ORA-12514: TNS:listener does not currently know of service requested in connect descriptor. plz help me thanks advance.............
ORA-26095: unprocessed stream data exists
IMP-00096: Warning: Skipping table "string"."string" because type synonym "string"."string" cannot be created
ORA-16626: failed to enable specified object
NZE-28868: Peer certificate chain check failed.
ORA-26076: cannot set or reset value after direct path structure is allocated
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.
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?
IMP-00064: Definition of LOB was truncated by export
IMP-00063: Warning: Skipping table "string"."string" because object type "string"."string" cannot be created or has different identifier
ORA-26030: index string.string had string partitions made unusable due to: