PCC-02107: You may not specify PARSE = FULL when CODE = CPP
- 1 Answers
- 3071 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 |
TNS-12666: Dedicated server: outbound transport protocol different from inbound
ORA-00067: invalid value string for parameter string; must be at least string
PLS-00164: cursor subqueries are not supported in this release
NNL-00562: unregister <name> [-d<address>] [-l<listener_name>] : unregister an object with Oracle Names
ORA-09914: Unable to open the ORACLE password file.
O2I-00132: Unable to close a Java file
DRG-12229: special section string already exists in this section group
IMG-00713: unsupported destination image format
TNS-12582: TNS:invalid operation
ORA-23293: Cannot rename a column which is part of a join index
PCC-00039: Unable to open input file "string"
ORA-01269: Destination parameter string is too long
Oracle Errors 
