Kevin
Just to make life confusing Documentum turns the hex number
(80004653) into a signed integer. All numbers over 80000000 actually
turn into negative numbers, which is why all data_tickets are
actually negative. If you have the Windows calculator (or any other
hex to decimal converter) available the quickest way to get to the
data_ticket is to do the following:

1) Subtract 0x80000000 from your hex data ticket.
2) Now subtract this from 0x80000000
3) Convert to decimal and put a minus sign in front.

Alternatively in C:


signed int si = 0x80004653;
printf("%d\n",si);

regards
Robin

____________________________________________________________
Robin East
Xense - Documentum Performance Tuning
http://www.xense.co.uk


--- In documentum-users@yahoogroups.com, "syeandel" <kevin@y...>
wrote:
>
> Hi guys
>
> I've tried to reverse lookup from content to an object id under:
>
>
> /u70/system/1/docbase/content_storage_01/000162b2/80/00/46
> ls
> 02.txt 0b.txt 14.txt 1d.jpg 26.jpg 2f.jpg 38.jpg 41.jpg
4a.jpg
> 53.jpg ...
>
>
> by taking (for example) 80004653 to an integer to produce a data
ticket
> then
>
> select * from dm_sysobject where i_contents_id in
> (select r_object_id from dmr_content where
data_ticket='<dataticket>')
>
> But get no rows back so I am making an assumption the algorithm is
> wrong. I've checked the forums and server admin guide for 5.2.5 and
I
> seem to be doing this right.
>
> I need to trace back to the original r_object_id because content is
> ending up in a storage area which is out of bounds and coming from
> nobody knows where (is just tifs or jpg's up to 30 megs in size).
>
> Any help will be most appreciated.
>
> Thanks
> Kevin
>