Interested to Buy Any Domain ? << Click Here >> for more details...
ORA-39135: SYS schema cannot read data using specific SCNs
- 1 Answers
- 7954 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-30075: TIME/TIMESTAMP WITH TIME ZONE literal must be specified in CHECK constraint
ORA-02842: Client unable to fork a server
TNS-04073: Passwords do not match.
UDE-00051: unable to set NLS_NUMERIC_CHARACTERS to required defaults.
ORA-39313: illegal clone() call: clone has been done before
ORA-16091: dependent archive log destination already archived
ORA-16629: Database reports a different protection level from the protection mode.
ORA-16510: messaging error using ksrwait
ORA-00341: log string of thread string, wrong log # string in header
PLS-00658: constructor method name must match type name
RMAN-06119: uncataloged datafile copy
ORA-06773: TLI Driver: error reading command
Oracle Errors 
