PCC-02107: You may not specify PARSE = FULL when CODE = CPP
- 1 Answers
- 3415 Views
- I also Faced
- E-Mail Answers
Answer / guest
Cause: The PARSE=FULL and CODE=CPP options were both
specified on the command line. The PARSE=FULL option invokes
the C parser which does not understand any C++ constructs
generated by the precompiler with CODE=CPP option.
Action: Set the PARSE option to either NONE or PARTIAL if
the CODE=CPP option is specified.
Please add more information about this Error
| Is This Answer Correct ? | 0 Yes | 0 No |
LPX-00225: end-element tag "~1S" does not match start-element tag "~2S"
ORA-06423: NETCMN: Error in receiving data
ORA-00150: duplicate transaction ID
NZE-29024: Certificate validation failure
ORA-01217: logfile member belongs to a different logfile group
NNL-00253: Server-generated requests currently request forwarding
ORA-01280: Fatal LogMiner Error.
NNO-00107: line string: ignoring stale checkpoint data
ORA-39150: bad flashback time
ORA-27159: failure setting process scheduling priority
ORA-29842: option not supported with the version string of the indextype interface
ORA-16799: Physical apply service is offline
Oracle Errors 
