ORA-39135: SYS schema cannot read data using specific SCNs
- 1 Answers
- 7447 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 |
TNS-00141: Failed to get file stream information
LSX-00331: missing comma
ORA-22851: invalid CHUNK LOB storage option value
ORA-06735: TLI Driver: client failed to close error conn
ORA-01038: cannot write database file version string with ORACLE version string
ORA-01252: cannot prevent writes - file string in recovery manager backup
LFI-00141: Unable to abort file in operation string.
ORA-26672: timeout occurred while stopping STREAMS process string
ORA-27004: invalid blocksize specified
TNS-12518: TNS:listener could not hand off client connection
ORA-02876: smpini: Unable to attach to shared memory for PGA
ORA-07710: sksaprs: file name buffer too small
Oracle Errors 
