I have been getting ORA-3113 connection errors which aborts my job and it seems to be happening during commits. I have increased the rows per transaction in hopes that more frequent commits would help me get out of this mode. However I am still getting the 3113's and wondering if there is a timeout / session parameter in datastage that could be set so that I don't loose my connection for long running commits. Or at least that is what I'm assuming is happening.
Thanks.
Ora-3113 error during a commit
Moderators: chulett, rschirm, roy
-
sabrewster
- Participant
- Posts: 1
- Joined: Mon Feb 06, 2006 12:00 pm
- Location: Lansing, MI
-
ray.wurlod
- Participant
- Posts: 54595
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact:
Type in oerr ORA 3113 to find out other possible remedies. Involve your Oracle DBA and network administrator. Increasing rows/transaction is not likely to make much difference if the problem is network dropouts.
IBM Software Services Group
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
Yah, I loves me that utility:

Code: Select all
$ oerr ORA 3113
03113, 00000, "end-of-file on communication channel"
// *Cause:
// *Action:
$-craig
"You can never have too many knives" -- Logan Nine Fingers
"You can never have too many knives" -- Logan Nine Fingers
