SQL1652N : File I/O error occurred
Moderators: chulett, rschirm, roy
-
- Charter Member
- Posts: 560
- Joined: Wed Jul 13, 2005 5:36 am
- Location: Ohio
SQL1652N : File I/O error occurred
Hi,
I get the following error:
SQL1652N File I/O error occurred.
Error occurred while loading table
Internal Error: Function 'load_data' failed
I extract data to a sequential file and use this sequential file to load into DB2 using bulk load stage.
Before this error message i get sucessfull extraction:
387484 rows read from <Stage> 387484 rows written to <SEQ FILE> 540.320 CPU seconds used, 1722.823 seconds elapsed.
But after i get these error messages i get following.
DSD.SEQOpen Failed to open <FILE NAME> in directory <Path> STATUS = -1.
Any suggestions?
I get the following error:
SQL1652N File I/O error occurred.
Error occurred while loading table
Internal Error: Function 'load_data' failed
I extract data to a sequential file and use this sequential file to load into DB2 using bulk load stage.
Before this error message i get sucessfull extraction:
387484 rows read from <Stage> 387484 rows written to <SEQ FILE> 540.320 CPU seconds used, 1722.823 seconds elapsed.
But after i get these error messages i get following.
DSD.SEQOpen Failed to open <FILE NAME> in directory <Path> STATUS = -1.
Any suggestions?
-
- Premium Member
- Posts: 1255
- Joined: Wed Feb 02, 2005 11:54 am
- Location: United States of America
Check the permissions. Are you writing and reading the sequential file at the same time? Then, that is the issue.
Whale.
Whale.
Anything that won't sell, I don't want to invent. Its sale is proof of utility, and utility is success.
Author: Thomas A. Edison 1847-1931, American Inventor, Entrepreneur, Founder of GE
Author: Thomas A. Edison 1847-1931, American Inventor, Entrepreneur, Founder of GE
-
- Charter Member
- Posts: 560
- Joined: Wed Jul 13, 2005 5:36 am
- Location: Ohio
I am allowed to write and read to same sequential file in the same job. the job will complete writing first before starting to read. I am running 80 jobs successfully with same user and design.
Its jsut this job which aborts.(aborted twice). Maybe because it has much more data. I think its something related to performance. Please comment
Its jsut this job which aborts.(aborted twice). Maybe because it has much more data. I think its something related to performance. Please comment
-
- Participant
- Posts: 54607
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact:
Are you perhaps trying to write to the same sequential file from two stages in the same job? This is not permitted (by the operating system) and will result in a fatal error with the message you received.
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.
-
- Charter Member
- Posts: 560
- Joined: Wed Jul 13, 2005 5:36 am
- Location: Ohio
-
- Charter Member
- Posts: 560
- Joined: Wed Jul 13, 2005 5:36 am
- Location: Ohio
No, there is only one input link to the sequential file and only one sequential stage per job. It runs fine when run alone. It just blows up when run with 12 other jobs parallely through sequence.ray.wurlod wrote:Are you perhaps trying to write to the same sequential file from two stages in the same job? This is not permitted (by the operating system) and will result in a fatal error with the message you received.
I guess your hitting a limit somewhere. This is what IBMhas to say about SQL 1652N.
Code: Select all
SQL1652N File I/O error occurred.
Explanation:
Error occurred either opening, reading, writing, or closing a file.
User Response:
Check the db2diag.log for details. Also, check for disk full conditions, file permissions, and operating system errors.
Creativity is allowing yourself to make mistakes. Art is knowing which ones to keep.
This from the IBM website
Also check with your support providers, if there is a fixpack for this issue.
Code: Select all
SQL1652N File I/O error occurred.
Explanation:
Error occurred either opening, reading, writing, or closing a file.
User Response:
Check the db2diag.log for details. Also, check for disk full conditions, file permissions, and operating system errors.
Narasimha Kade
Finding answers is simple, all you need to do is come up with the correct questions.
Finding answers is simple, all you need to do is come up with the correct questions.
What a co-incidence, DSguru2B and me looking into the same thing at the same time
Looks like people are running into this issue after installing a certain fixpack. There are many discussions on this topic on google.
Looks like people are running into this issue after installing a certain fixpack. There are many discussions on this topic on google.
Narasimha Kade
Finding answers is simple, all you need to do is come up with the correct questions.
Finding answers is simple, all you need to do is come up with the correct questions.
-
- Charter Member
- Posts: 560
- Joined: Wed Jul 13, 2005 5:36 am
- Location: Ohio
I did check the db2diag.log file but found no warnings or errors in there. (thats what my DBA told me). I dont think we have installed any fix packs recently. Will check and see if i can catch hold of IBM for this.narasimha wrote:This from the IBM website
Also check with your support providers, if there is a fixpack for this issue.Code: Select all
SQL1652N File I/O error occurred. Explanation: Error occurred either opening, reading, writing, or closing a file. User Response: Check the db2diag.log for details. Also, check for disk full conditions, file permissions, and operating system errors.
-
- Participant
- Posts: 54607
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact:
-
- Charter Member
- Posts: 560
- Joined: Wed Jul 13, 2005 5:36 am
- Location: Ohio
-
- Premium Member
- Posts: 1255
- Joined: Wed Feb 02, 2005 11:54 am
- Location: United States of America