This is an archive of the Maximo Yahoo Community. The content of this pages may be a sometimes obsolete so please check post dates.
Thanks to the community owner Christopher Wanko for providing the content.
Seven years later I'm supporting a SQL Server installation of Maximo 7.5, and wished I'd read this earlier. Now at least I know how to avoid this ridiculousity.
-C
Talk about reviving an old thread... *lol* at the end of the day you can
still do everything you can in Oracle, the caching just puts a twist in the
process. I suppose that if you were really particular about it then you
could easily write a script to reset each sequence back to the "next plus
one" value prior to starting up Maximo so that you salvage those values
that are lost to the caching process - if it's that important to you.
The main thing I always found is in manipulating sequences, if you want to
block a range of identifiers you need to update and restart to refresh the
cache, other than that it's all pretty much business as usual for SQL
Server.
I wonder if DB2 has it's own variation - if anyone is actually using DB2...
I've yet to come across an actual client who went that way.
C.
On Tue, May 16, 2017 at 8:26 AM, maximal@wanko.com [MAXIMO] <
MAXIMO@yahoogroups.com> wrote:
>
>
> Seven years later I'm supporting a SQL Server installation of Maximo 7.5,
> and wished I'd read this earlier. Now at least I know how to avoid this
> ridiculousity.
>
> -C
>
>
>
>
>
>
>
>
>
>
>
---In MAXIMO@yahoogroups.com, <lawlessc@gmail.com> wrote :
Talk about reviving an old thread... *lol* at the end of the day you can
still do everything you can in Oracle, the caching just puts a twist in the
process. I suppose that if you were really particular about it then you
could easily write a script to reset each sequence back to the "next plus
one" value prior to starting up Maximo so that you salvage those values
that are lost to the caching process - if it's that important to you.
The thing that was important to me was forcing SQL Server to see the new starting point. Caching is fine, I guess, if you are high-volume. This implementation isn't high-volume, so I set the TEST environment to use the sequence check and we'll see if it causes interminable delays. High-water mark of users is maybe 30 across two cluster members.
I know that rollover forces Maximo to start looking for open ranges in the sequences. I vaguely remember solving this for long descriptions back in v3. That's when my CompSci education still reminded me about hash collision solutions.
>>I wonder if DB2 has it's own variation - if anyone is actually using DB2...
>>I've yet to come across an actual client who went that way.
I think DB2 has sequence generators like Oracle. You know, what real database engines have.
-C