Populating I_DS_JOBS

[admin]

Anything with an I_ name is a secondary index. Ordinarily you would not be able to list it with LIST, clearly you have created a VOC item called I_DS_JOBS.OBJIDNO (and that almost certainly points to I_DS_JOBS/INDEX.000 rather than anything else.

What happens when you count the items in DS_JOBS? (For example, COUNT DS_JOBS or (in SQL) SELECT COUNT(*) FROM DS_JOBS;)

Assuming that you do have more than two jobs, it seems that the index, or your pointer to it, is out of date in some way. What happens if you execute the following commands:
LIST.INDEX DS_JOBS ALL
LIST.INDEX DS_JOBS OBJIDNO STATS
LIST.INDEX DS_JOBS OBJIDNO DETAIL

Have you tried DS_REINDEX on just the DS_JOBS table? You need exclusive access to DS_JOBS (no clients connected, no jobs running) to run this.

----- Original Message -----
From: Leon Kingsley-Smith
Date: Mon, 10 Nov 2003 14:05:20 +1100 (EST)
To: datastage-users@oliver.com
Subject: Populating I_DS_JOBS

> We have a problem with I_DS_JOBS in our project.
> It only has two records.
> Other datastage projects at our site have all jobs listed in I_DS_JOBS.
> We have tried, project cleanup and reindex as dsadm.
>
> The command
> LIST I_DS_JOBS.OBJIDNO ID.SUP JobNo JobName JobCategory
>
> Gives this result.
> LIST I_DS_JOBS.OBJIDNO ID.SUP JobNo JobName JobCategory 03:53:25pm 10
> Nov 2003
> PAGE 1
> JobNo....... 0
> JobName..... JobA
> JobCategory. PERSONAL\
> JobNo....... 2
> JobName..... JobB
> JobCategory. LANDING\
> 2 records listed.
>
> Any ideas? - Thanx - Leon
>
>
>
>
>
> ---------------------------------
> Yahoo! Personals
- New people, new possibilities. FREE for a limited time!