ORA-39135: SYS schema cannot read data using specific SCNs
- 1 Answers
- 7489 Views
- I also Faced
- E-Mail Answers
Answer / guest
Cause: The user was operating under the SYS schema and
either explicitly specified an SCN via the FLASHBACK_SCN or
FLASHBACK_TIME or TABLE_CONSISTENCY parameters or the job
required that a specific SCN be used because of streams or
logical replication activity.
Action: Do not perform Data Pump jobs using the SYS schema
or 'AS SYSDBA'.
Please add more information about this Error
| Is This Answer Correct ? | 1 Yes | 1 No |
ORA-14169: invalid ALTER TABLE MODIFY SUBPARTITION option
RMAN-04016: could not get OCI error handle
KUP-04069: error fetching data for external table
DRG-13306: 'len' attribute value must be in the range string..string, at line string
TNS-00143: Illegal PREFERRED_CMANAGERS entry in TNSNAV.ORA
TNS-04077: WARNING: No password set for the Oracle Connection Manager instance.
PCC-00011: Already in a declare section at line number in file string
ORA-00100: no data found
ORA-12207: TNS:unable to perform navigation
ORA-14609: Tablespace was not specified for the previous lob segments of column string in template but is specified for string
ORA-19604: conversation file naming phase is over
ORA-06042: NETDNT: message receive failure
Oracle Errors 
