SQL1652N : File I/O error occurred

Krazykoolrohit · Post by **Krazykoolrohit** » Mon Jan 29, 2007 1:49 pm

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_Server_Whale · Post by **I_Server_Whale** » Mon Jan 29, 2007 1:56 pm

Check the permissions. Are you writing and reading the sequential file at the same time? Then, that is the issue.

Whale.

Krazykoolrohit · Post by **Krazykoolrohit** » Mon Jan 29, 2007 2:27 pm

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

DSguru2B · Post by **DSguru2B** » Mon Jan 29, 2007 2:58 pm

Are you doing extracting and loading both in the same job? If yes then check that both input and output tabs of the sequential file have identical file names.

ray.wurlod · Post by **ray.wurlod** » Mon Jan 29, 2007 2:59 pm

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.

Krazykoolrohit · Post by **Krazykoolrohit** » Mon Jan 29, 2007 3:52 pm

DSguru2B wrote:Are you doing extracting and loading both in the same job? If yes then check that both input and output tabs of the sequential file have identical file names.

The file name and format are same.

Krazykoolrohit · Post by **Krazykoolrohit** » Mon Jan 29, 2007 3:53 pm

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.

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.

DSguru2B · Post by **DSguru2B** » Mon Jan 29, 2007 3:58 pm

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.

narasimha · Post by **narasimha** » Mon Jan 29, 2007 4:01 pm

This from the IBM website

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.

Also check with your support providers, if there is a fixpack for this issue.

narasimha · Post by **narasimha** » Mon Jan 29, 2007 4:11 pm

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.

Krazykoolrohit · Post by **Krazykoolrohit** » Mon Jan 29, 2007 4:20 pm

narasimha wrote:This from the IBM website
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. 
Also check with your support providers, if there is a fixpack for this issue.

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.

ray.wurlod · Post by **ray.wurlod** » Mon Jan 29, 2007 4:49 pm

Krazykoolrohit wrote:It just blows up when run with 12 other jobs parallely through sequence.

All trying to write to the same sequential file? Tch! Tch!

DSguru2B · Post by **DSguru2B** » Mon Jan 29, 2007 5:18 pm

ray.wurlod wrote:
Krazykoolrohit wrote:It just blows up when run with 12 other jobs parallely through sequence.
All trying to write to the same sequential file? Tch! Tch!

Thats a good one,

Krazykoolrohit · Post by **Krazykoolrohit** » Tue Jan 30, 2007 9:19 am

DSguru2B wrote:
ray.wurlod wrote:
Krazykoolrohit wrote:It just blows up when run with 12 other jobs parallely through sequence.
All trying to write to the same sequential file? Tch! Tch!
Thats a good one,

lol..ya it is...no Ray. we are not trying to write to the same file.

I_Server_Whale · Post by **I_Server_Whale** » Tue Jan 30, 2007 9:24 am

Can you post the contents of the the db2diag.log?

Whale.