DBPROCESS is dead or not enabled

Post questions here relative to DataStage Server Edition for such areas as Server job design, DS Basic, Routines, Job Sequences, etc.

Moderators: chulett, rschirm, roy

Post Reply
poorna_76
Charter Member
Charter Member
Posts: 190
Joined: Thu Jul 08, 2004 10:42 am

DBPROCESS is dead or not enabled

Post by poorna_76 »

We ran a job on 09/27/2005 8:39:45 AM in Production.

The job aborted at 09/27/2005 8:40:06 AM with PrimaryKey Violation Error.

After deleting the data from a particular table , the job was Reset at 09/27/2005 8:46:19 AM and we Ran the job again.

The job finished at 09/27/2005 8:46:59 AM successfully, without any warnings.

When we verified the data that was loaded into the table, it was incorrect.

Surprisingly there were 3 Warnings generated in the log at 09/28/2005 8:15:37 AM, after almost 24 hours later the job was finished

**************
LD_T4_ADULT_TRACKING_ASSIGN_CODE_19..LDLoadAdultTracking.stgBCPL4_ADULT_TRACKING.IDENT10: DBPROCESS is dead or not enabled.

LD_T4_ADULT_TRACKING_ASSIGN_CODE_19..LDLoadAdultTracking.stgBCPT4_ADULT_TRACKING.IDENT7: DBPROCESS is dead or not enabled.

LD_T4_ADULT_TRACKING_ASSIGN_CODE_19..LDLoadAdultTracking.stgBCPL4_ADULT_TRACKING: DBPROCESS is dead or not enabled.
*************

LD_T4_ADULT_TRACKING_ASSIGN_CODE_19 is the jobname.

LDLoadAdultTracking is the SharedContainer ,inside that we use BCPStage to load SQL Server data.

Any thoughts?

Thanks in Advance
ray.wurlod
Participant
Posts: 54607
Joined: Wed Oct 23, 2002 10:52 pm
Location: Sydney, Australia
Contact:

Post by ray.wurlod »

This is a SQL Server process. You have to fix the problem in SQL Server. DataStage is simply informing you that the problem exists, and is preventing DataStage from doing its task.
IBM Software Services Group
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
poorna_76
Charter Member
Charter Member
Posts: 190
Joined: Thu Jul 08, 2004 10:42 am

Post by poorna_76 »

ray.wurlod wrote:This is a SQL Server process. You have to fix the problem in SQL Server. DataStage is simply informing you that the problem exists, and is preventing DataStage from doing its task.
Hi Ray,

Thanks for your Reponse.

But why does that DataStage job gave warning about SQL Server , when that job is not running and no activity is going on?

Morever why the warning after almost 24 hours of jobs finished time?

Please clarify me.

Thanks in Advance.
ray.wurlod
Participant
Posts: 54607
Joined: Wed Oct 23, 2002 10:52 pm
Location: Sydney, Australia
Contact:

Post by ray.wurlod »

DataStage posts the message because it is being prevented from doing whatever it needs to by a defunct SQL Server process.

Everything else follows from that.
IBM Software Services Group
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
Post Reply