DSXchange

We have certain jobs that use Oracle connector. I just want to understand if the it can handle the following:
- Table being loaded ran out of extents or the tablespace ran out of room?
- Network disconnect, database outage, or other issue that prevents data from being loaded?

The question is whether these kinds of events can be captured in the Oracle Connector reject link.

That's not what a 'reject' link is for. The events you mention will cause the job to abort, not records to be rejected.

All those examples require someone, like a DBA or network person, to take action. In cases like those, you can set your sequence job to detect the abort job status from the job with the Oracle Connector stage. You can have the sequence job email to one or more people, to a help desk, or to a mail group, etc. to alert them.