PCC-02107: You may not specify PARSE = FULL when CODE = CPP
- 1 Answers
- 3087 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 |
ORA-06262: NETNTT: nfconn() failed
NID-00600: Internal Error - [number] [number] [number] [number]
NNL-00341: Trace file name is now string
ORA-13520: Database id (string) not registered, Status = string
RMAN-06564: must use the TO clause when the instance is started with SPFILE
TNS-00144: PUMP_CONNECTIONS value in INTCHG.ORA is too large.
ORA-25301: cannot specify recipient list during enqueue
ORA-29805: missing COLUMN keyword
ORA-32771: cannot add file to bigfile tablespace
RMAN-06115: changed backup piece available
ORA-01109: database not open
SQL*Loader-00290: PIECED keyword (on column string) allowed only for lob or long columns
Oracle Errors 
