LOAD issue



IBM's flagship relational database management system

LOAD issue

Postby p19689 » Thu Apr 12, 2012 2:08 pm

Hi I have run Load on a partion table with over 3ooM records. Job abend with the following:
UTILITY BATCH MEMORY EXECUTION ABENDED, REASON=X'00E40005'
UTILITY BATCH MEMORY EXECUTION ABENDED, REASON=X'00E40347'

However it seems that it has loaded total number of records it supposed to be loaded as job output shows as below:

NUMBER OF RECORDS=300,635,998 FOR TABLE EMP100

TOTAL NUMBER OF RECORDS LOADED=300,635,998 FOR tABLE EMP100

NUMBER OF INPUT RECORDS PROCESSED=300,635,998

Can someone explain why memory execution error appered after loading all the records it supposed to be loaded and the job abend with S04E' please ?
p19689
 
Posts: 65
Joined: Fri Oct 01, 2010 1:13 pm
Has thanked: 0 time
Been thanked: 0 time

Re: LOAD issue

 

Re: LOAD issue

Postby Robert Sample » Thu Apr 12, 2012 2:40 pm

This is a HELP forum, not a READ-THE-MANUAL-FOR-YOU service. Please go find the manual of error messages and look up the two reason codes you were provided. If they do not provide adequate insight, then post the reason meanings here and we can help interpret them for you.
Robert Sample
Global moderator
 
Posts: 3367
Joined: Sat Dec 19, 2009 8:32 pm
Location: East Dubuque, Illinois
Has thanked: 1 time
Been thanked: 222 times

Re: LOAD issue

Postby p19689 » Thu Apr 12, 2012 2:46 pm

Thanks Robert, I had checked the manual and there are few reasons forr above errors. But my specific question question was after loading the expected no of rows then job abend with the above errors. That's the reason I posted the question. Have you come across this type of situation before ?
p19689
 
Posts: 65
Joined: Fri Oct 01, 2010 1:13 pm
Has thanked: 0 time
Been thanked: 0 time

Re: LOAD issue

Postby Robert Sample » Thu Apr 12, 2012 5:00 pm

Google is your friend. Goolging 00E40005 returns 284 hits, the very first of which says
00E40005

Explanation

A nonzero reason code was returned from MVSâ„¢ sort.
System action

Any error message generated by sort in conjunction with the nonzero reason code is directed to the device/data set identified by the UTPRINT DD statement in the utility job step.

Error message DSNU044I, that contains the nonzero reason code, is directed to the device/data set identified by the SYSPRINT DD statement in the utility job step.
Operator response

An operator with SYSOPR authority can issue the -TERM UTILITY command to release the resources claimed by the stopped utility (this may not be necessary).
User response

Determine the cause of the error. If the error can be corrected, the utility may be restarted from the beginning of the sort phase by using the 'RESTART(PHASE)' parameter. If the error prevents the utility from completing, the -TERM command should be issued to remove the stopped utility from the system. The -TERM UTILITY should seldom be used when the stopped utility is REORG.
Problem determination

This abend is accompanied by the utility message DSNU044I, that contains the sort reason code and an SVC dump. In most cases, the error messages from SORT that are sent to the device/data set identified by the UTPRINT DD statement identify the problem. The dump may not be needed. If SORT is unable to open the UTPRINT data set, only the message and abend are provided. In this case, correct the problem associated with the UTPRINT DD statement, and restart the job with the RESTART(PHASE) option.
Collect the following diagnostic items:

Console output from the system on which the job was run, and a listing of the SYSLOG data set for the period of time spanning the failure.
Listing of SYS1.LOGREC data set, obtained by executing IFCEREP1.
SYSPRINT output, including JCL, for the application program or batch job, and system messages that were issued. Make sure that MSGLEVEL=(1,1) on the JOB statement so that all diagnostic information is sent to SYSPRINT.
UTPRINT output, produced by utility invocation of SORT.
Dynamic dump, taken to SYS1.DUMPxx data set, by DB2® (for 04E and 04F abends). Availability of this dump is dependent on the failing environment.
SYSABEND, SYSUDUMP, or SYSMDUMP output. Availability of these dumps is dependent on the failing environment.

If the problem resulted in an SVC dump, you should have your site support group analyze the SVC dump. Otherwise, you might need to open a PMR with IBM.

As far as why it happened, there are things to be done after the base load is complete (sorting records to create indexes comes to mind), so that could be where the problem is.
Robert Sample
Global moderator
 
Posts: 3367
Joined: Sat Dec 19, 2009 8:32 pm
Location: East Dubuque, Illinois
Has thanked: 1 time
Been thanked: 222 times

Re: LOAD issue

Postby GuyC » Thu Apr 12, 2012 8:45 pm

probably : out of sort space
GuyC
 
Posts: 315
Joined: Tue Aug 11, 2009 3:23 pm
Has thanked: 1 time
Been thanked: 4 times

Re: LOAD issue

Postby p19689 » Thu Apr 12, 2012 9:11 pm

Thanks all, I had incresed the region size and SORTOUT and the job completed Ok.
p19689
 
Posts: 65
Joined: Fri Oct 01, 2010 1:13 pm
Has thanked: 0 time
Been thanked: 0 time


Return to DB2

 


  • Related topics
    Replies
    Views
    Last post