[Date Prev][Date Next][Thread Prev][Thread Next]
[Author Index] [Date Index] [Thread Index]
[SQR-USERS Info] [SQRUG Home Page]

Re: [sqr-users] Illegal Instruction & Memory Fault (coredump)



Chris,

I don't know what your OS ( I am guessing mainframe) or db (I am guessing 
db2) is because you haven't told us, but I'd check for tablespace/container 
limits or a space problem in your file system.

This is a SWAG, so I'll be surprised if it helps, but that's what happens 
when you barnstorm.

clark 'the dragon' willis
dragon enterprises, consulting services.

PSA: Salary <> Slavery.  If you earn a salary, your employer is renting your 
services for 40 hours a week, not purchasing your soul.  Your time is the 
only real finite asset that you have, and once used it can never be 
recovered, so don't waste it by giving it away.

"Time is the coin of your life. It is the only coin you have, and only you 
can determine how it will be spent.  Be careful lest you let other people 
spend it for you."

Carl Sandburg
(1878 - 1967)


----Original Message Follows----

Folks -

I'm looking for some help on resolving the coredump problem that I'm having 
with an SQR.

The SQR is pretty basic with no complicated JOINS.  It selects about 
300,000+ Emplids and then goes through a series of selects to get Bio/Demo 
and Degree data for each person selected.  Ultimately, two output files will 
be created - one for Bio/Demo and one for Degree data - and these will be 
sent to a vendor.  It also inserts each row processed into a custom SQL 
table.  I'm committing after every 15K Emplids processed.

I've commented out the WRITEs to the file and I'm still encountering the 
following coredump errors.  I've tried chunking the main SQL in batches of 
100,000 Emplids but that's when I got the "illegal instruction" error after 
it processed 124K Emplids.

[...snip...]SQR_AVP601CU_115467/prcs_sqr[96]: 54986 Memory fault(coredump)
[...snip...]SQR_AVP601CU_115478/prcs_sqr[96]: 75854 Illegal 
instruction(coredump)

I'd really rather not have the operator have to run this job numerous times, 
running in batches of 100K Emplids from outside of the program but that's 
what I'm considering now.

I expect that as we bring Contributor Relations into Production (scheduled 
for 7/28) and this interface is run in Production, that the number of 
EmplIds processed is going to continue to grow.

Does anyone have any thoughts on how else to handle this situation?

Thanks,
Chris

_________________________________________________________________
Protect your PC - get McAfee.com VirusScan Online  
http://clinic.mcafee.com/clinic/ibuy/campaign.asp?cid=3963

_______________________________________________
sqr-users mailing list
sqr-users@sqrug.org
http://www.sqrug.org/mailman/listinfo/sqr-users