Interested to Buy Any Domain ? << Click Here >> for more details...
PCC-02107: You may not specify PARSE = FULL when CODE = CPP
- 1 Answers
- 3886 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-12001: cannot create log: table 'string' already has a trigger
PCB-00236: Cannot use PIC N/G variable. NLS_NCHAR not set or set incorrectly.
ORA-25445: invalid column number: string for table alias: string
NNL-00538: stop|shutdown [<server_list>] : stop one or more Names servers
PCC-02313: malformed VARCHAR declaration - missing length
KUP-04049: record number discarded from file string
PCC-02415: Cannot manipulate Object attributes in an OBJECT GET or SET
PLS-00707: unsupported construct or internal error [string]
RMAN-20039: format requires character when duplexing
ORA-16139: media recovery required
CLSS-03202: out of sync with master: [string] [string] [string] [string]
RMAN-06019: could not translate tablespace name "string"
Oracle Errors 
