No rows in table when run by scheduler

[SynexusStuart]

Hi all,

We have a windows scheduler that runs a jobstream every night (in Data Manager 8.4). There is a specific fact build in this jobstream which seemingly runs successfully and when audited, the rows inserted shows over 400k but when we look at the table in SQL Server, it is empty.

If i re-run the fact build manually, the data is delivered correctly, also, if I start the jobstream manually, the data is delivered correctly.

Does anyone know how this can happen?

We're really stuck!

Stuart

[MFGF]

Is it anything to do with the specific user running the job?  Sounds a little odd that the job should run fine when fired off manually but not via the scheduler.

Oh... another random thought.  If you look at the command line being run by the scheduler, does it still have the -P switch to force a "Press return to continue" at the end?  If so, this may be preventing the scheduled job from exiting and committing the database transaction.

MF.

[SynexusStuart]

The command line runs a .bat file containing this:

"C:\Program Files\cognos\c8-DM\bin\rundsjob.exe" "OLEDB" "Database=data manager catalog;Data Source=SERVERNAME;Provider=sqlncli (SQL Server 2005 native client);Integrated Security=TRUE" "JobSTREAM"


The bat file doesn't contain the -P you referred to but it sets off a Job Stream with over 100 build nodes and they all build fine except this individual one. Is it possible that it would affect 1/100 build nodes? Also, when I build it manually, there is no need to "press return to continue" when I run the job manually.

I have tried a SQL node to drop the table and rebuild, I have tried creating a new build from scratch and slipped it into the Job Stream in place of the original.

I just can't think of anything else?

[MFGF]

If you grab the command line for the individual build, strip out the -P switch, then try submitting this directly via the windows scheduler, does it still fail to deliver rows?  If this works, you could try removing the build from the jobstream, adding a Procedure Node in its place, and using the system() function within the procedure node to call the build via its command line.

Not an ideal solution, but it may buy you some time to investigate the problem further.

Cheers!

MF.

[SynexusStuart]

MF, thanks for the suggestion.

What we have done is add a "Last Modified date" into the source tabel and now run it as an UPDATE/INSERT. It was a stab in the dark to buy time (as at least we wouldn't lose data) but it actually worked! 

We are moving to new environments at the moment and the (identical) DM Catalog in the new environment works fine.

Thanks again.

[MFGF]

Thanks for the update.  Glad you found a workaround, but I'm at a loss to explain what the original problem may be.  Hope the move to the new environment goes well!

MF.