Unable to run through Sequencer

v_bhaskar · Post by **v_bhaskar** » Wed Mar 26, 2014 11:56 pm

Thanks for you information.

Let me google it how i can clear the db2 logs

ray.wurlod · Post by **ray.wurlod** » Wed Mar 26, 2014 11:59 pm

chulett wrote:I don't really see this as being a parameter issue.

It might be. I have had one experience of a job running in PROD that was passed parameters to the DEV environment, which did not have the capacity to do all the things that were being requested to be done in PROD environment. Took a while to diagnose, should have looked in the "job starting" entry to check parameter values sooner. That's now much higher on my personal list of troubleshooting techniques.

v_bhaskar · Post by **v_bhaskar** » Thu Mar 27, 2014 12:08 am

hi,

As i checked the Db2 is having 109 gb free space of memory and for datastage 90gb free space of memory is there.

still is it the problem with memory

any how i will try to make it free some more space in both the servers

dsetlteam · Post by **dsetlteam** » Thu Mar 27, 2014 12:50 am

Still no resolution found...this thread is very interesting

priyadarshikunal · Post by **priyadarshikunal** » Thu Mar 27, 2014 6:42 am

Are you using parameter set by any chance and are you using value files or some thing else like default value for each parameter set and you pass a name which contains value for that parameter set? I have see some cases mainly in 8.0 where you must compile the jobs if using parameter set as new values will not be reflected.

chulett · Post by **chulett** » Thu Mar 27, 2014 7:32 am

v_bhaskar wrote:still is it the problem with memory

How do you know it is a problem with memory? I never said that, nor did I suggest you clear your logs - specifically noted you should check the diagnostic log file that was named in the linked thread.

If you did, what were the contents?

v_bhaskar · Post by **v_bhaskar** » Thu Mar 27, 2014 8:10 am

hi

from db2 diagnostic log file

i find out the below log .. please correct me if i am checking wrong

PID : 5505208 TID : 258 PROC : db2sysc 0
INSTANCE: db2inst1 NODE : 000
EDUID : 258 EDUNAME: db2sysc 0
FUNCTION: DB2 UDB, oper system services, sqloLoadModule, probe:130
CALLED : OS, -, dlopen
OSERR : ENOEXEC (8) "Exec format error"
MESSAGE : Attempt to load specified library failed.
DATA #1 : Library name or path, 40 bytes
/home/db2inst1/sqllib/lib64/libdb2iocp.a
DATA #2 : shared library load flags, PD_TYPE_LOAD_FLAGS, 4 bytes
2
DATA #3 : String, 627 bytes
0509-130 Symbol resolution failed for /home/db2inst1/sqllib/lib64/libdb2iocp.a because:
0509-136 Symbol CreateIoCompletionPort (number 0) is not exported from
dependent module /unix.
0509-136 Symbol GetQueuedCompletionStatus (number 1) is not exported from
dependent module /unix.
0509-136 Symbol GetMultipleCompletionStatus (number 2) is not exported from
dependent module /unix.
0509-022 Cannot load module /home/db2inst1/sqllib/lib64/libdb2iocp.a.
0509-026 System error: Cannot run a file that does not have a valid format.
0509-192 Examine .loader section symbols with the
'dump -Tv' command.

chulett · Post by **chulett** » Thu Mar 27, 2014 9:20 am

So nothing to do with memory but rather a shared library format error / load failure. In your shoes, I would get that in front of your official support provider to help track down the cause.

What exact parameters are you passing in to the job? I still don't think that is the issue as they really shouldn't be able to affect the job in this manner but let's detail them so that maybe we can get that off the table once and for all.

v_bhaskar · Post by **v_bhaskar** » Thu Mar 27, 2014 10:24 am

Hi

i am just passing parameter value file which contains db credentials and company_id

the Db2 table is an partitioned table

based on company_id value we are loading into respective partition data area

so in the parameter file contains
company_id ,db2 credentials

almost all 200+ tables are partitioned and working fine
only few jobs are getting issue, when i tried with doing some changes and complied. by that time sequencer and job is running fine .

this is first time i am facing issue. the same job is working fine in UAT and Prod

finally i tried to recreate the table by taking structure from UAT but no luck

chulett · Post by **chulett** » Thu Mar 27, 2014 11:44 am

Your issue could be resource related, if I'm understanding all of your steps. Are your sequence jobs running many jobs? When some jobs running under a sequence fail but work fine if run individually or rerun from the point of failure, that is very typically a resource constraint... too much going on at a time.

Still think you need to involve support to confirm why the load error.

v_bhaskar · Post by **v_bhaskar** » Fri Mar 28, 2014 1:45 am

Thanks for your information

Let me check with my official support