Is this during an upgrade or have you recently performed an upgrade? The error is similar to an infinite nested group error that I got when upgrading to 5.2.5.
Joe
On Wednesday 08 March 2006 02:18 pm, ask me wrote:> Hi,>
I am getting this error while starting docbase.,>
Wed Mar 8 15:09:52 2006 109412 [DM_SESSION_I_INIT_BEGIN]> info: "Initialize dmGroup."> Wed Mar 8 15:09:52 2006 143222 [DM_SESSION_I_INIT_BEGIN]> info: "Initialize dmSysObject."> Wed Mar 8 15:09:52 2006 149394 [DM_SYSOBJECT_F_INIT2]fatal: "Version> stamp 37 was expected to be 36."> Wed Mar 8 15:09:52 2006 149581 [DM_SESSION_E_INIT_FAILURE1]> error: "Failure to complete dmSysObject initialization."> Wed Mar 8 15:09:52 2006 153113 [DM_SERVER_I_START_ID]info: "Docbase> myradianidm was not successfully opened. Docbase id: (15525)"> ...>
please guide me as to how to solve this. Urgent>
James>
Yahoo! Groups Links>
-- Microsoft (MS), like the disease it shares the acronym with, is a gradual loss of primary functions augmented with spastic jerks. Penguin: Linux version 2.6.13, 7951.42 BogoMips Skype: joebacom AOL: joeb1002 Yahoo: joebacom Jabber: bacomj
fatal: "Version> > stamp 37 was expected to be 36."> > Wed Mar 8 15:09:52 2006 149581 [DM_SESSION_E_INIT_FAILURE1]> > error: "Failure to complete dmSysObject initialization."> > Wed Mar 8 15:09:52 2006 153113 [DM_SERVER_I_START_ID] info: "Docbase> > myradianidm was not successfully opened. Docbase id: (15525)"> > ...> >
please guide me as to how to solve this. Urgent> >
James> >
Yahoo! Groups Links> >
-- > Microsoft (MS), like the disease it shares the acronym with, is a
gradual loss > of primary functions augmented with spastic jerks.> Penguin: Linux version 2.6.13, 7951.42 BogoMips> Skype: joebacom> AOL: joeb1002> Yahoo: joebacom> Jabber: bacomj>
This error is covered by Support Note 26425. Here's what you need to do.
<snip> These errors indicate that you cannot connect to the docbase and you want to check a few things in the database (SQL). For example, in this instance you would check the table called dmi_vstamp_s in the RDBMS and find the value 36 for the record "dm_sysobject". You may have to change several values to correct their value (dm_server_config, dm_policy, dmi_registry and dm_activity) in order for the docbase starts, but this should be straightforward to notice and find. <snip>
BTW, I've had this one too. It occurred after an upgrade from a 4.x to a 5.x docbase. The error did not show up until the docbase had been running for awhile (second cycle after upgrade).
Joe
On Thursday 09 March 2006 07:59 am, ask me wrote:> No.. its not during an upgrade. Just a startup created this issue.> The upgrade with SP4 was done a few months ago.>
-- In documentum-users-hHKSG33TihhbjbujkaE4pw@public.gmane.org, Joe Bacom <joe@...> wrote:> > Is this during an upgrade or have you recently performed an>
upgrade? The>
error is similar to an infinite nested group error that I got when>
upgrading>
to 5.2.5.> >
On Wednesday 08 March 2006 02:18 pm, ask me wrote:> > > Hi,> > >
I am getting this error while starting docbase.,> > >
stamp 37 was expected to be 36."> > > Wed Mar 8 15:09:52 2006 149581 [DM_SESSION_E_INIT_FAILURE1]> > > error: "Failure to complete dmSysObject initialization."> > > Wed Mar 8 15:09:52 2006 153113 [DM_SERVER_I_START_ID]>
info: "Docbase>
myradianidm was not successfully opened. Docbase id: (15525)"> > > ...> > >
please guide me as to how to solve this. Urgent> > >
James> > >
Yahoo! Groups Links> >
--> > Microsoft (MS), like the disease it shares the acronym with, is a>
gradual loss>
of primary functions augmented with spastic jerks.> > Penguin: Linux version 2.6.13, 7951.42 BogoMips> > Skype: joebacom> > AOL: joeb1002> > Yahoo: joebacom> > Jabber: bacomj>
Yahoo! Groups Links>
-- Microsoft (MS), like the disease it shares the acronym with, is a gradual loss of primary functions augmented with spastic jerks. Penguin: Linux version 2.6.13, 7951.42 BogoMips Skype: joebacom AOL: joeb1002 Yahoo: joebacom Jabber: bacomj
Apparently, they were doing environmental changes for the last week. DBA is reluctant to make changes in the DB.. Could it be that documentum is connecting to wrong DB?
--- In documentum-users-hHKSG33TihhbjbujkaE4pw@public.gmane.org, Joe Bacom <joe@...> wrote:>
This error is covered by Support Note 26425. Here's what you need
to do.>
<snip>> These errors indicate that you cannot connect to the docbase and
you want to > check a few things in the database (SQL). For example, in this instance you > would check the table called dmi_vstamp_s in the RDBMS and find the value 36 > for the record "dm_sysobject". You may have to change several values to > correct their value > (dm_server_config, dm_policy, dmi_registry and dm_activity) in order for the > docbase starts, but this should be straightforward to notice and find. > <snip>>
BTW, I've had this one too. It occurred after an upgrade from a
4.x to a 5.x > docbase. The error did not show up until the docbase had been running for > awhile (second cycle after upgrade).>
On Thursday 09 March 2006 07:59 am, ask me wrote:> > No.. its not during an upgrade. Just a startup created this
issue.> > The upgrade with SP4 was done a few months ago.> >
-- In documentum-users-hHKSG33TihhbjbujkaE4pw@public.gmane.org, Joe Bacom <joe@> wrote:> > > Is this during an upgrade or have you recently performed an> >
upgrade? The> >
error is similar to an infinite nested group error that I got
when> >
upgrading> >
to 5.2.5.> > >
On Wednesday 08 March 2006 02:18 pm, ask me wrote:> > > > Hi,> > > >
I am getting this error while starting docbase.,> > > >
stamp 37 was expected to be 36."> > > > Wed Mar 8 15:09:52 2006 149581 [DM_SESSION_E_INIT_FAILURE1]> > > > error: "Failure to complete dmSysObject initialization."> > > > Wed Mar 8 15:09:52 2006 153113 [DM_SERVER_I_START_ID]> >
info: "Docbase> >
myradianidm was not successfully opened. Docbase id: (15525)"> > > > ...> > > >
please guide me as to how to solve this. Urgent> > > >
James> > > >
Yahoo! Groups Links> > >
--> > > Microsoft (MS), like the disease it shares the acronym with,
is a> >
gradual loss> >
of primary functions augmented with spastic jerks.> > > Penguin: Linux version 2.6.13, 7951.42 BogoMips> > > Skype: joebacom> > > AOL: joeb1002> > > Yahoo: joebacom> > > Jabber: bacomj> >
Yahoo! Groups Links> >
-- > Microsoft (MS), like the disease it shares the acronym with, is a
gradual loss > of primary functions augmented with spastic jerks.> Penguin: Linux version 2.6.13, 7951.42 BogoMips> Skype: joebacom> AOL: joeb1002> Yahoo: joebacom> Jabber: bacomj>
It's unlikely that you're connecting to the wrong docbase unless your server.ini file has been modified. Additionally, you would get a bunch of error messages about bad id's. It's a good thing that your DBA is reluctant to make changes in the DB, however, in this case, it's the only way.
Joe
On Thursday 09 March 2006 09:08 am, ask me wrote:> Apparently, they were doing environmental changes for the last week.> DBA is reluctant to make changes in the DB.. Could it be that> documentum is connecting to wrong DB?>
--- In documentum-users-hHKSG33TihhbjbujkaE4pw@public.gmane.org, Joe Bacom <joe@...> wrote:> > This error is covered by Support Note 26425. Here's what you need>
to do.>
<snip>> > These errors indicate that you cannot connect to the docbase and>
you want to>
check a few things in the database (SQL). For example, in this>
instance you>
would check the table called dmi_vstamp_s in the RDBMS and find>
the value 36>
for the record "dm_sysobject". You may have to change several>
values to>
correct their value> > (dm_server_config, dm_policy, dmi_registry and dm_activity) in>
order for the>
docbase starts, but this should be straightforward to notice and>
find.>
<snip>> >
BTW, I've had this one too. It occurred after an upgrade from a>
4.x to a 5.x>
docbase. The error did not show up until the docbase had been>
running for>
awhile (second cycle after upgrade).> >
On Thursday 09 March 2006 07:59 am, ask me wrote:> > > No.. its not during an upgrade. Just a startup created this>
issue.>
The upgrade with SP4 was done a few months ago.> > >
-- In documentum-users-hHKSG33TihhbjbujkaE4pw@public.gmane.org, Joe Bacom <joe@> wrote:> > > > Is this during an upgrade or have you recently performed an> > >
upgrade? The> > >
error is similar to an infinite nested group error that I got>
when>
upgrading> > >
to 5.2.5.> > > >
On Wednesday 08 March 2006 02:18 pm, ask me wrote:> > > > > Hi,> > > > >
I am getting this error while starting docbase.,> > > > >
stamp 37 was expected to be 36."> > > > > Wed Mar 8 15:09:52 2006 149581 [DM_SESSION_E_INIT_FAILURE1]> > > > > error: "Failure to complete dmSysObject initialization."> > > > > Wed Mar 8 15:09:52 2006 153113 [DM_SERVER_I_START_ID]> > >
info: "Docbase> > >
myradianidm was not successfully opened. Docbase id: (15525)"> > > > > ...> > > > >
please guide me as to how to solve this. Urgent> > > > >
James> > > > >
Yahoo! Groups Links> > > >
--> > > > Microsoft (MS), like the disease it shares the acronym with,>
is a>
gradual loss> > >
of primary functions augmented with spastic jerks.> > > > Penguin: Linux version 2.6.13, 7951.42 BogoMips> > > > Skype: joebacom> > > > AOL: joeb1002> > > > Yahoo: joebacom> > > > Jabber: bacomj> > >
Yahoo! Groups Links> >
--> > Microsoft (MS), like the disease it shares the acronym with, is a>
gradual loss>
of primary functions augmented with spastic jerks.> > Penguin: Linux version 2.6.13, 7951.42 BogoMips> > Skype: joebacom> > AOL: joeb1002> > Yahoo: joebacom> > Jabber: bacomj>
Yahoo! Groups Links>
-- Microsoft (MS), like the disease it shares the acronym with, is a gradual loss of primary functions augmented with spastic jerks. Penguin: Linux version 2.6.13, 7951.42 BogoMips Skype: joebacom AOL: joeb1002 Yahoo: joebacom Jabber: bacomj
Thanks.. One more question. The upgrade to SP4 was done before me by someone else. But now, the server log says version SP1. How can this happen?
--- In documentum-users-hHKSG33TihhbjbujkaE4pw@public.gmane.org, Joe Bacom <joe@...> wrote:>
It's unlikely that you're connecting to the wrong docbase unless
your > server.ini file has been modified. Additionally, you would get a bunch of > error messages about bad id's. It's a good thing that your DBA is reluctant > to make changes in the DB, however, in this case, it's the only way.>
On Thursday 09 March 2006 09:08 am, ask me wrote:> > Apparently, they were doing environmental changes for the last
week.> > DBA is reluctant to make changes in the DB.. Could it be that> > documentum is connecting to wrong DB?> >
--- In documentum-users-hHKSG33TihhbjbujkaE4pw@public.gmane.org, Joe Bacom <joe@> wrote:> > > This error is covered by Support Note 26425. Here's what you
need> >
to do.> >
<snip>> > > These errors indicate that you cannot connect to the docbase
you want to> >
check a few things in the database (SQL). For example, in this> >
instance you> >
would check the table called dmi_vstamp_s in the RDBMS and find> >
the value 36> >
for the record "dm_sysobject". You may have to change several> >
values to> >
correct their value> > > (dm_server_config, dm_policy, dmi_registry and dm_activity) in> >
order for the> >
docbase starts, but this should be straightforward to notice
find.> >
<snip>> > >
BTW, I've had this one too. It occurred after an upgrade from
4.x to a 5.x> >
docbase. The error did not show up until the docbase had been> >
running for> >
awhile (second cycle after upgrade).> > >
On Thursday 09 March 2006 07:59 am, ask me wrote:> > > > No.. its not during an upgrade. Just a startup created this> >
issue.> >
The upgrade with SP4 was done a few months ago.> > > >
-- In documentum-users-hHKSG33TihhbjbujkaE4pw@public.gmane.org, Joe Bacom <joe@>
wrote:> > > > > Is this during an upgrade or have you recently performed an> > > >
upgrade? The> > > >
error is similar to an infinite nested group error that I
when> >
upgrading> > > >
to 5.2.5.> > > > >
On Wednesday 08 March 2006 02:18 pm, ask me wrote:> > > > > > Hi,> > > > > >
I am getting this error while starting docbase.,> > > > > >
--> > > Microsoft (MS), like the disease it shares the acronym with,
is a> >
gradual loss> >
of primary functions augmented with spastic jerks.> > > Penguin: Linux version 2.6.13, 7951.42 BogoMips> > > Skype: joebacom> > > AOL: joeb1002> > > Yahoo: joebacom> > > Jabber: bacomj> >
Yahoo! Groups Links> >
-- > Microsoft (MS), like the disease it shares the acronym with, is a
gradual loss > of primary functions augmented with spastic jerks.> Penguin: Linux version 2.6.13, 7951.42 BogoMips> Skype: joebacom> AOL: joeb1002> Yahoo: joebacom> Jabber: bacomj>
What does it say when you connect through an iapi session?
Joe On Thursday 09 March 2006 10:10 am, ask me wrote:> Thanks.. One more question. The upgrade to SP4 was done before me by> someone else. But now, the server log says version SP1. How can this> happen?>
--- In documentum-users-hHKSG33TihhbjbujkaE4pw@public.gmane.org, Joe Bacom <joe@...> wrote:> > It's unlikely that you're connecting to the wrong docbase unless>
your>
server.ini file has been modified. Additionally, you would get a>
bunch of>
error messages about bad id's. It's a good thing that your DBA is>
reluctant>
to make changes in the DB, however, in this case, it's the only>
way.>
On Thursday 09 March 2006 09:08 am, ask me wrote:> > > Apparently, they were doing environmental changes for the last>
week.>
DBA is reluctant to make changes in the DB.. Could it be that> > > documentum is connecting to wrong DB?> > >
--- In documentum-users-hHKSG33TihhbjbujkaE4pw@public.gmane.org, Joe Bacom <joe@> wrote:> > > > This error is covered by Support Note 26425. Here's what you>
need>
to do.> > >
<snip>> > > > These errors indicate that you cannot connect to the docbase>
you want to> > >
check a few things in the database (SQL). For example, in this> > >
instance you> > >
would check the table called dmi_vstamp_s in the RDBMS and find> > >
the value 36> > >
for the record "dm_sysobject". You may have to change several> > >
values to> > >
correct their value> > > > (dm_server_config, dm_policy, dmi_registry and dm_activity) in> > >
order for the> > >
docbase starts, but this should be straightforward to notice>
find.> > >
<snip>> > > >
BTW, I've had this one too. It occurred after an upgrade from>
4.x to a 5.x> > >
docbase. The error did not show up until the docbase had been> > >
running for> > >
awhile (second cycle after upgrade).> > > >
On Thursday 09 March 2006 07:59 am, ask me wrote:> > > > > No.. its not during an upgrade. Just a startup created this> > >
issue.> > >
The upgrade with SP4 was done a few months ago.> > > > >
-- In documentum-users-hHKSG33TihhbjbujkaE4pw@public.gmane.org, Joe Bacom <joe@>>
wrote:> > > > > > Is this during an upgrade or have you recently performed an> > > > >
upgrade? The> > > > >
error is similar to an infinite nested group error that I>
when> > >
upgrading> > > > >
to 5.2.5.> > > > > >
On Wednesday 08 March 2006 02:18 pm, ask me wrote:> > > > > > > Hi,> > > > > > >
I am getting this error while starting docbase.,> > > > > > >
--> > > > Microsoft (MS), like the disease it shares the acronym with,>
is a>
gradual loss> > >
of primary functions augmented with spastic jerks.> > > > Penguin: Linux version 2.6.13, 7951.42 BogoMips> > > > Skype: joebacom> > > > AOL: joeb1002> > > > Yahoo: joebacom> > > > Jabber: bacomj> > >
Yahoo! Groups Links> >
--> > Microsoft (MS), like the disease it shares the acronym with, is a>
gradual loss>
of primary functions augmented with spastic jerks.> > Penguin: Linux version 2.6.13, 7951.42 BogoMips> > Skype: joebacom> > AOL: joeb1002> > Yahoo: joebacom> > Jabber: bacomj>
Yahoo! Groups Links>
-- Microsoft (MS), like the disease it shares the acronym with, is a gradual loss of primary functions augmented with spastic jerks. Penguin: Linux version 2.6.13, 7951.42 BogoMips Skype: joebacom AOL: joeb1002 Yahoo: joebacom Jabber: bacomj
Tried iapi.. My manager is sure that SP4 upgrade was done.
Documentum iapi - Interactive API interface (c) Copyright Documentum, Inc., 1992 - 2004 All rights reserved. Client Library Release 5.2.5.125 SP1 HPUX
-- In documentum-users-hHKSG33TihhbjbujkaE4pw@public.gmane.org, Joe Bacom <joe@...> wrote:>
What does it say when you connect through an iapi session?>
On Thursday 09 March 2006 10:10 am, ask me wrote:> > Thanks.. One more question. The upgrade to SP4 was done before
me by> > someone else. But now, the server log says version SP1. How can this> > happen?> >
--- In documentum-users-hHKSG33TihhbjbujkaE4pw@public.gmane.org, Joe Bacom <joe@> wrote:> > > It's unlikely that you're connecting to the wrong docbase
unless> >
your> >
server.ini file has been modified. Additionally, you would
get a> >
bunch of> >
error messages about bad id's. It's a good thing that your
DBA is> >
reluctant> >
to make changes in the DB, however, in this case, it's the only> >
way.> >
On Thursday 09 March 2006 09:08 am, ask me wrote:> > > > Apparently, they were doing environmental changes for the
last> >
week.> >
DBA is reluctant to make changes in the DB.. Could it be that> > > > documentum is connecting to wrong DB?> > > >
--- In documentum-users-hHKSG33TihhbjbujkaE4pw@public.gmane.org, Joe Bacom <joe@>
wrote:> > > > > This error is covered by Support Note 26425. Here's what
need> >
to do.> > > >
<snip>> > > > > These errors indicate that you cannot connect to the
docbase> >
you want to> > > >
check a few things in the database (SQL). For example, in
this> > > >
instance you> > > >
would check the table called dmi_vstamp_s in the RDBMS and
find> > > >
the value 36> > > >
for the record "dm_sysobject". You may have to change
several> > > >
values to> > > >
correct their value> > > > > (dm_server_config, dm_policy, dmi_registry and
dm_activity) in> > > >
order for the> > > >
docbase starts, but this should be straightforward to
notice> >
find.> > > >
<snip>> > > > >
BTW, I've had this one too. It occurred after an upgrade
from> >
4.x to a 5.x> > > >
docbase. The error did not show up until the docbase had
been> > > >
running for> > > >
awhile (second cycle after upgrade).> > > > >
On Thursday 09 March 2006 07:59 am, ask me wrote:> > > > > > No.. its not during an upgrade. Just a startup created
this> > > >
issue.> > > >
The upgrade with SP4 was done a few months ago.> > > > > >
-- In documentum-users-hHKSG33TihhbjbujkaE4pw@public.gmane.org, Joe Bacom <joe@>> >
wrote:> > > > > > > Is this during an upgrade or have you recently
performed an> > > > > >
upgrade? The> > > > > >
error is similar to an infinite nested group error
that I> >
when> > > >
upgrading> > > > > >
to 5.2.5.> > > > > > >
On Wednesday 08 March 2006 02:18 pm, ask me wrote:> > > > > > > > Hi,> > > > > > > >
I am getting this error while starting docbase.,> > > > > > > >
--> > > Microsoft (MS), like the disease it shares the acronym with,
is a> >
gradual loss> >
of primary functions augmented with spastic jerks.> > > Penguin: Linux version 2.6.13, 7951.42 BogoMips> > > Skype: joebacom> > > AOL: joeb1002> > > Yahoo: joebacom> > > Jabber: bacomj> >
Yahoo! Groups Links> >
-- > Microsoft (MS), like the disease it shares the acronym with, is a
gradual loss > of primary functions augmented with spastic jerks.> Penguin: Linux version 2.6.13, 7951.42 BogoMips> Skype: joebacom> AOL: joeb1002> Yahoo: joebacom> Jabber: bacomj>
Well, if it was done, then somebody has rolled the changes back (restore from backup). With the client library saying it's SP1, you can count it being SP1. I'm also assuming you ran iapi on the server and not some other client.
I would reapply SP4 (it won't hurt anything if it's already been done) or go ahead and apply SP5.
Joe
On Thursday 09 March 2006 10:53 am, ask me wrote:> Tried iapi.. My manager is sure that SP4 upgrade was done.>
Documentum iapi - Interactive API interface> (c) Copyright Documentum, Inc., 1992 - 2004> All rights reserved.> Client Library Release 5.2.5.125 SP1 HPUX>
-- In documentum-users-hHKSG33TihhbjbujkaE4pw@public.gmane.org, Joe Bacom <joe@...> wrote:> > What does it say when you connect through an iapi session?> >
On Thursday 09 March 2006 10:10 am, ask me wrote:> > > Thanks.. One more question. The upgrade to SP4 was done before>
me by>
someone else. But now, the server log says version SP1. How can>
this>
happen?> > >
--- In documentum-users-hHKSG33TihhbjbujkaE4pw@public.gmane.org, Joe Bacom <joe@> wrote:> > > > It's unlikely that you're connecting to the wrong docbase>
unless>
your> > >
server.ini file has been modified. Additionally, you would>
get a>
bunch of> > >
error messages about bad id's. It's a good thing that your>
DBA is>
reluctant> > >
to make changes in the DB, however, in this case, it's the only> > >
way.> > >
On Thursday 09 March 2006 09:08 am, ask me wrote:> > > > > Apparently, they were doing environmental changes for the>
last>
week.> > >
DBA is reluctant to make changes in the DB.. Could it be that> > > > > documentum is connecting to wrong DB?> > > > >
--- In documentum-users-hHKSG33TihhbjbujkaE4pw@public.gmane.org, Joe Bacom <joe@>>
wrote:> > > > > > This error is covered by Support Note 26425. Here's what>
need> > >
to do.> > > > >
<snip>> > > > > > These errors indicate that you cannot connect to the>
docbase>
you want to> > > > >
check a few things in the database (SQL). For example, in>
this>
instance you> > > > >
would check the table called dmi_vstamp_s in the RDBMS and>
find>
the value 36> > > > >
for the record "dm_sysobject". You may have to change>
--> > > > Microsoft (MS), like the disease it shares the acronym with,>
is a>
gradual loss> > >
of primary functions augmented with spastic jerks.> > > > Penguin: Linux version 2.6.13, 7951.42 BogoMips> > > > Skype: joebacom> > > > AOL: joeb1002> > > > Yahoo: joebacom> > > > Jabber: bacomj> > >
Yahoo! Groups Links> >
--> > Microsoft (MS), like the disease it shares the acronym with, is a>
gradual loss>
of primary functions augmented with spastic jerks.> > Penguin: Linux version 2.6.13, 7951.42 BogoMips> > Skype: joebacom> > AOL: joeb1002> > Yahoo: joebacom> > Jabber: bacomj>
Yahoo! Groups Links>
-- Microsoft (MS), like the disease it shares the acronym with, is a gradual loss of primary functions augmented with spastic jerks. Penguin: Linux version 2.6.13, 7951.42 BogoMips Skype: joebacom AOL: joeb1002 Yahoo: joebacom Jabber: bacomj
Thanks Joe, I really appreciate your help. I wish I could award you points.
James
--- In documentum-users-hHKSG33TihhbjbujkaE4pw@public.gmane.org, Joe Bacom <joe@...> wrote:>
Well, if it was done, then somebody has rolled the changes back
(restore from > backup). With the client library saying it's SP1, you can count it being > SP1. I'm also assuming you ran iapi on the server and not some other client.>
I would reapply SP4 (it won't hurt anything if it's already been
done) or go > ahead and apply SP5.>
On Thursday 09 March 2006 10:53 am, ask me wrote:> > Tried iapi.. My manager is sure that SP4 upgrade was done.> >
Documentum iapi - Interactive API interface> > (c) Copyright Documentum, Inc., 1992 - 2004> > All rights reserved.> > Client Library Release 5.2.5.125 SP1 HPUX> >
-- In documentum-users-hHKSG33TihhbjbujkaE4pw@public.gmane.org, Joe Bacom <joe@> wrote:> > > What does it say when you connect through an iapi session?> > >
On Thursday 09 March 2006 10:10 am, ask me wrote:> > > > Thanks.. One more question. The upgrade to SP4 was done
before> >
me by> >
someone else. But now, the server log says version SP1. How
this> >
happen?> > > >
--- In documentum-users-hHKSG33TihhbjbujkaE4pw@public.gmane.org, Joe Bacom <joe@>
wrote:> > > > > It's unlikely that you're connecting to the wrong docbase> >
unless> >
your> > > >
server.ini file has been modified. Additionally, you would> >
get a> >
bunch of> > > >
error messages about bad id's. It's a good thing that your> >
DBA is> >
reluctant> > > >
to make changes in the DB, however, in this case, it's the
only> > > >
way.> > > >
On Thursday 09 March 2006 09:08 am, ask me wrote:> > > > > > Apparently, they were doing environmental changes for the> >
last> >
week.> > > >
DBA is reluctant to make changes in the DB.. Could it be
that> > > > > > documentum is connecting to wrong DB?> > > > > >
--- In documentum-users-hHKSG33TihhbjbujkaE4pw@public.gmane.org, Joe Bacom <joe@>> >
wrote:> > > > > > > This error is covered by Support Note 26425. Here's
what> >
need> > > >
to do.> > > > > >
<snip>> > > > > > > These errors indicate that you cannot connect to the> >
docbase> >
you want to> > > > > >
check a few things in the database (SQL). For example,
this> >
instance you> > > > > >
would check the table called dmi_vstamp_s in the RDBMS
find> >
the value 36> > > > > >
for the record "dm_sysobject". You may have to change> >
--> > > Microsoft (MS), like the disease it shares the acronym with,
is a> >
gradual loss> >
of primary functions augmented with spastic jerks.> > > Penguin: Linux version 2.6.13, 7951.42 BogoMips> > > Skype: joebacom> > > AOL: joeb1002> > > Yahoo: joebacom> > > Jabber: bacomj> >
Yahoo! Groups Links> >
-- > Microsoft (MS), like the disease it shares the acronym with, is a
gradual loss > of primary functions augmented with spastic jerks.> Penguin: Linux version 2.6.13, 7951.42 BogoMips> Skype: joebacom> AOL: joeb1002> Yahoo: joebacom> Jabber: bacomj>
wei-chu li-Izg6Ufzl9FU 9 March 2006 21:58:04 [ permanent link ]
Could you please tell me what are the benefits to upgrade content server from version 5.2.5 sp2 to sp4 or sp5.
Thanks,
liwc
Joe Bacom <joe-P6su6aJo9I9l57MIdRCFDg@public.gmane.org> To: documentum-users-hHKSG33TihhbjbujkaE4pw@public.gmane.org Sent by: cc: documentum-users@yaho Subject: Re: [documentum-users] Re: DM_SYSOBJECT_F_INIT2]fatal: "Version stamp 37 ogroups.com was expected to be 36."
03/09/2006 12:17 PM Please respond to documentum-users
Well, if it was done, then somebody has rolled the changes back (restore from backup). With the client library saying it's SP1, you can count it being SP1. I'm also assuming you ran iapi on the server and not some other client.
I would reapply SP4 (it won't hurt anything if it's already been done) or go ahead and apply SP5.
Joe
On Thursday 09 March 2006 10:53 am, ask me wrote:> Tried iapi.. My manager is sure that SP4 upgrade was done.>
Documentum iapi - Interactive API interface> (c) Copyright Documentum, Inc., 1992 - 2004> All rights reserved.> Client Library Release 5.2.5.125 SP1 HPUX>
-- In documentum-users-hHKSG33TihhbjbujkaE4pw@public.gmane.org, Joe Bacom <joe@...> wrote:> > What does it say when you connect through an iapi session?> >
On Thursday 09 March 2006 10:10 am, ask me wrote:> > > Thanks.. One more question. The upgrade to SP4 was done before>
me by>
someone else. But now, the server log says version SP1. How can>
this>
happen?> > >
--- In documentum-users-hHKSG33TihhbjbujkaE4pw@public.gmane.org, Joe Bacom <joe@> wrote:> > > > It's unlikely that you're connecting to the wrong docbase>
unless>
your> > >
server.ini file has been modified. Additionally, you would>
get a>
bunch of> > >
error messages about bad id's. It's a good thing that your>
DBA is>
reluctant> > >
to make changes in the DB, however, in this case, it's the only> > >
way.> > >
On Thursday 09 March 2006 09:08 am, ask me wrote:> > > > > Apparently, they were doing environmental changes for the>
last>
week.> > >
DBA is reluctant to make changes in the DB.. Could it be that> > > > > documentum is connecting to wrong DB?> > > > >
--- In documentum-users-hHKSG33TihhbjbujkaE4pw@public.gmane.org, Joe Bacom <joe@>>
wrote:> > > > > > This error is covered by Support Note 26425. Here's what>
need> > >
to do.> > > > >
<snip>> > > > > > These errors indicate that you cannot connect to the>
docbase>
you want to> > > > >
check a few things in the database (SQL). For example, in>
this>
instance you> > > > >
would check the table called dmi_vstamp_s in the RDBMS and>
find>
the value 36> > > > >
for the record "dm_sysobject". You may have to change>
--> > > > Microsoft (MS), like the disease it shares the acronym with,>
is a>
gradual loss> > >
of primary functions augmented with spastic jerks.> > > > Penguin: Linux version 2.6.13, 7951.42 BogoMips> > > > Skype: joebacom> > > > AOL: joeb1002> > > > Yahoo: joebacom> > > > Jabber: bacomj> > >
Yahoo! Groups Links> >
--> > Microsoft (MS), like the disease it shares the acronym with, is a>
gradual loss>
of primary functions augmented with spastic jerks.> > Penguin: Linux version 2.6.13, 7951.42 BogoMips> > Skype: joebacom> > AOL: joeb1002> > Yahoo: joebacom> > Jabber: bacomj>
Yahoo! Groups Links>
-- Microsoft (MS), like the disease it shares the acronym with, is a gradual loss of primary functions augmented with spastic jerks. Penguin: Linux version 2.6.13, 7951.42 BogoMips Skype: joebacom AOL: joeb1002 Yahoo: joebacom Jabber: bacomj (See attached file: attumv4r.dat)
----------------------------------------- CONFIDENTIALITY NOTICE: This electronic message contains information which may be legally confidential and/or privileged and does not in any case represent a firm ENERGY COMMODITY bid or offer relating thereto which binds the sender without an additional express written confirmation to that effect. The information is intended solely for the individual or entity named above and access by anyone else is unauthorized. If you are not the intended recipient, any disclosure, copying, distribution, or use of the contents of this information is prohibited and may be unlawful. If you have received this electronic transmission in error, please reply immediately to the sender that you have received the message in error, and delete it. Thank you.
On Thursday 09 March 2006 11:51 am, ask me wrote:> Thanks Joe, I really appreciate your help. I wish I could award you> points.>
James>
--- In documentum-users-hHKSG33TihhbjbujkaE4pw@public.gmane.org, Joe Bacom <joe@...> wrote:> > Well, if it was done, then somebody has rolled the changes back>
(restore from>
backup). With the client library saying it's SP1, you can count>
it being>
SP1. I'm also assuming you ran iapi on the server and not some>
other client.>
I would reapply SP4 (it won't hurt anything if it's already been>
done) or go>
ahead and apply SP5.> >
On Thursday 09 March 2006 10:53 am, ask me wrote:> > > Tried iapi.. My manager is sure that SP4 upgrade was done.> > >
Documentum iapi - Interactive API interface> > > (c) Copyright Documentum, Inc., 1992 - 2004> > > All rights reserved.> > > Client Library Release 5.2.5.125 SP1 HPUX> > >
-- In documentum-users-hHKSG33TihhbjbujkaE4pw@public.gmane.org, Joe Bacom <joe@> wrote:> > > > What does it say when you connect through an iapi session?> > > >
On Thursday 09 March 2006 10:10 am, ask me wrote:> > > > > Thanks.. One more question. The upgrade to SP4 was done>
before>
me by> > >
someone else. But now, the server log says version SP1. How>
this> > >
happen?> > > > >
--- In documentum-users-hHKSG33TihhbjbujkaE4pw@public.gmane.org, Joe Bacom <joe@>>
wrote:> > > > > > It's unlikely that you're connecting to the wrong docbase> > >
unless> > >
your> > > > >
server.ini file has been modified. Additionally, you would> > >
get a> > >
bunch of> > > > >
error messages about bad id's. It's a good thing that your> > >
DBA is> > >
reluctant> > > > >
to make changes in the DB, however, in this case, it's the>
only>
way.> > > > >
On Thursday 09 March 2006 09:08 am, ask me wrote:> > > > > > > Apparently, they were doing environmental changes for the> > >
last> > >
week.> > > > >
DBA is reluctant to make changes in the DB.. Could it be>
that>
documentum is connecting to wrong DB?> > > > > > >
--- In documentum-users-hHKSG33TihhbjbujkaE4pw@public.gmane.org, Joe Bacom <joe@>> > >
wrote:> > > > > > > > This error is covered by Support Note 26425. Here's>
what>
need> > > > >
to do.> > > > > > >
<snip>> > > > > > > > These errors indicate that you cannot connect to the> > >
docbase> > >
you want to> > > > > > >
check a few things in the database (SQL). For example,>
this> > >
instance you> > > > > > >
would check the table called dmi_vstamp_s in the RDBMS>
find> > >
the value 36> > > > > > >
for the record "dm_sysobject". You may have to change> > >
--> > > > Microsoft (MS), like the disease it shares the acronym with,>
is a>
gradual loss> > >
of primary functions augmented with spastic jerks.> > > > Penguin: Linux version 2.6.13, 7951.42 BogoMips> > > > Skype: joebacom> > > > AOL: joeb1002> > > > Yahoo: joebacom> > > > Jabber: bacomj> > >
Yahoo! Groups Links> >
--> > Microsoft (MS), like the disease it shares the acronym with, is a>
gradual loss>
of primary functions augmented with spastic jerks.> > Penguin: Linux version 2.6.13, 7951.42 BogoMips> > Skype: joebacom> > AOL: joeb1002> > Yahoo: joebacom> > Jabber: bacomj>
Yahoo! Groups Links>
-- Microsoft (MS), like the disease it shares the acronym with, is a gradual loss of primary functions augmented with spastic jerks. Penguin: Linux version 2.6.13, 7951.42 BogoMips Skype: joebacom AOL: joeb1002 Yahoo: joebacom Jabber: bacomj
Joe, Have to bother you again.. We changed the value for sysobject in the table dmi_vstamp and it initialized. But for dm_server_config, the value change doesnot seems to work.
Fri Mar 10 09:00:07 2006 456787 [DM_SESSION_I_INIT_BEGIN] info: "Initialize dmLocation." Fri Mar 10 09:00:07 2006 528737 [DM_SESSION_I_INIT_BEGIN] info: "Initialize Server Configuration." Fri Mar 10 09:00:07 2006 537237 [DM_DCNFG_F_INIT2]fatal: "Version stamp 12 was expected to be 11." Fri Mar 10 09:00:07 2006 552672 [DM_SESSION_E_INIT_FAILURE1] error: "Failure to complete Server Configuration initialization."
This is the value in the DB
The value is 11 in the database В– here's the data in the table:
R_OBJECT_ID I_APPLICATION I_STAMP I_VSTAMP
1e003ca58000012e dm_server_config 11 0
what am i doing wrong? Did I make a wrong change.
Thanks --- In documentum-users-hHKSG33TihhbjbujkaE4pw@public.gmane.org, Joe Bacom <joe@...> wrote:>
No worries, I'm not after points. >
Glad I could help.>
On Thursday 09 March 2006 11:51 am, ask me wrote:> > Thanks Joe, I really appreciate your help. I wish I could award
points.> >
James> >
--- In documentum-users-hHKSG33TihhbjbujkaE4pw@public.gmane.org, Joe Bacom <joe@> wrote:> > > Well, if it was done, then somebody has rolled the changes back> >
(restore from> >
backup). With the client library saying it's SP1, you can
count> >
it being> >
SP1. I'm also assuming you ran iapi on the server and not some> >
other client.> >
I would reapply SP4 (it won't hurt anything if it's already
been> >
done) or go> >
ahead and apply SP5.> > >
On Thursday 09 March 2006 10:53 am, ask me wrote:> > > > Tried iapi.. My manager is sure that SP4 upgrade was done.> > > >
I have to ask the obvious first, did you commit your changes? Also, you probably want to delete all of the cache files. These are under $DM_HOME/bin/dmcl
You can either delete them or move them somewhere else. Documentum will recreate the folders on startup
Joe
On Friday 10 March 2006 08:42 am, ask me wrote:> Joe, Have to bother you again.. We changed the value for sysobject> in the table dmi_vstamp and it initialized. But for> dm_server_config, the value change doesnot seems to work.>
Fri Mar 10 09:00:07 2006 456787 [DM_SESSION_I_INIT_BEGIN]> info: "Initialize dmLocation."> Fri Mar 10 09:00:07 2006 528737 [DM_SESSION_I_INIT_BEGIN]> info: "Initialize Server Configuration."> Fri Mar 10 09:00:07 2006 537237 [DM_DCNFG_F_INIT2]fatal: "Version> stamp 12 was expected to be 11."> Fri Mar 10 09:00:07 2006 552672 [DM_SESSION_E_INIT_FAILURE1]> error: "Failure to complete Server Configuration initialization.">
This is the value in the DB>
The value is 11 in the database – here's the data in the table:>
R_OBJECT_ID I_APPLICATION I_STAMP I_VSTAMP>
1e003ca58000012e dm_server_config 11 0>
what am i doing wrong? Did I make a wrong change.>
Thanks>
--- In documentum-users-hHKSG33TihhbjbujkaE4pw@public.gmane.org, Joe Bacom <joe@...> wrote:> > No worries, I'm not after points. > >
Glad I could help.> >
On Thursday 09 March 2006 11:51 am, ask me wrote:> > > Thanks Joe, I really appreciate your help. I wish I could award>
points.> > >
James> > >
--- In documentum-users-hHKSG33TihhbjbujkaE4pw@public.gmane.org, Joe Bacom <joe@> wrote:> > > > Well, if it was done, then somebody has rolled the changes back> > >
(restore from> > >
backup). With the client library saying it's SP1, you can>
count>
it being> > >
SP1. I'm also assuming you ran iapi on the server and not some> > >
other client.> > >
I would reapply SP4 (it won't hurt anything if it's already>
been>
done) or go> > >
ahead and apply SP5.> > > >
On Thursday 09 March 2006 10:53 am, ask me wrote:> > > > > Tried iapi.. My manager is sure that SP4 upgrade was done.> > > > >
- Hey joe, I opened a case with DCTM. They are helping me out with this. Thanks again for your help.
James
-- In documentum-users-hHKSG33TihhbjbujkaE4pw@public.gmane.org, Joe Bacom <joe@...> wrote:>
I have to ask the obvious first, did you commit your changes?
Also, you > probably want to delete all of the cache files. These are under > $DM_HOME/bin/dmcl>
You can either delete them or move them somewhere else.
Documentum will > recreate the folders on startup>
On Friday 10 March 2006 08:42 am, ask me wrote:> > Joe, Have to bother you again.. We changed the value for
sysobject> > in the table dmi_vstamp and it initialized. But for> > dm_server_config, the value change doesnot seems to work.> >
Fri Mar 10 09:00:07 2006 456787 [DM_SESSION_I_INIT_BEGIN]> > info: "Initialize dmLocation."> > Fri Mar 10 09:00:07 2006 528737 [DM_SESSION_I_INIT_BEGIN]> > info: "Initialize Server Configuration."> > Fri Mar 10 09:00:07 2006 537237 [DM_DCNFG_F_INIT2]
fatal: "Version> > stamp 12 was expected to be 11."> > Fri Mar 10 09:00:07 2006 552672 [DM_SESSION_E_INIT_FAILURE1]> > error: "Failure to complete Server Configuration initialization."> >
This is the value in the DB> >
The value is 11 in the database В– here's the data in the table:> >
R_OBJECT_ID I_APPLICATION I_STAMP
I_VSTAMP> >
1e003ca58000012e dm_server_config 11 0> >
what am i doing wrong? Did I make a wrong change.> >
Thanks> >
--- In documentum-users-hHKSG33TihhbjbujkaE4pw@public.gmane.org, Joe Bacom <joe@> wrote:> > > No worries, I'm not after points. > > >
Glad I could help.> > >
On Thursday 09 March 2006 11:51 am, ask me wrote:> > > > Thanks Joe, I really appreciate your help. I wish I could
award> >
points.> > > >
James> > > >
--- In documentum-users-hHKSG33TihhbjbujkaE4pw@public.gmane.org, Joe Bacom <joe@>
wrote:> > > > > Well, if it was done, then somebody has rolled the changes back> > > >
(restore from> > > >
backup). With the client library saying it's SP1, you can> >
count> >
it being> > > >
SP1. I'm also assuming you ran iapi on the server and not
some> > > >
other client.> > > >
I would reapply SP4 (it won't hurt anything if it's already> >
been> >
done) or go> > > >
ahead and apply SP5.> > > > >
On Thursday 09 March 2006 10:53 am, ask me wrote:> > > > > > Tried iapi.. My manager is sure that SP4 upgrade was
Please post the solution (when you get it) back to the group so everybody can benefit from your misfortune
Joe
On Friday 10 March 2006 11:30 am, ask me wrote:> -> Hey joe, I opened a case with DCTM. They are helping me out with> this. Thanks again for your help.>
James>
-- In documentum-users-hHKSG33TihhbjbujkaE4pw@public.gmane.org, Joe Bacom <joe@...> wrote:> > I have to ask the obvious first, did you commit your changes?>
Also, you>
probably want to delete all of the cache files. These are under> > $DM_HOME/bin/dmcl> >
You can either delete them or move them somewhere else.>
Documentum will>
recreate the folders on startup> >
On Friday 10 March 2006 08:42 am, ask me wrote:> > > Joe, Have to bother you again.. We changed the value for>
sysobject>
in the table dmi_vstamp and it initialized. But for> > > dm_server_config, the value change doesnot seems to work.> > >
Fri Mar 10 09:00:07 2006 456787 [DM_SESSION_I_INIT_BEGIN]> > > info: "Initialize dmLocation."> > > Fri Mar 10 09:00:07 2006 528737 [DM_SESSION_I_INIT_BEGIN]> > > info: "Initialize Server Configuration."> > > Fri Mar 10 09:00:07 2006 537237 [DM_DCNFG_F_INIT2]>
fatal: "Version>
stamp 12 was expected to be 11."> > > Fri Mar 10 09:00:07 2006 552672 [DM_SESSION_E_INIT_FAILURE1]> > > error: "Failure to complete Server Configuration>
initialization.">
This is the value in the DB> > >
The value is 11 in the database – here's the data in the table:> > >
R_OBJECT_ID I_APPLICATION I_STAMP>
I_VSTAMP>
1e003ca58000012e dm_server_config 11 0> > >
what am i doing wrong? Did I make a wrong change.> > >
Thanks> > >
--- In documentum-users-hHKSG33TihhbjbujkaE4pw@public.gmane.org, Joe Bacom <joe@> wrote:> > > > No worries, I'm not after points. > > > >
Glad I could help.> > > >
On Thursday 09 March 2006 11:51 am, ask me wrote:> > > > > Thanks Joe, I really appreciate your help. I wish I could>
award>
points.> > > > >
James> > > > >
--- In documentum-users-hHKSG33TihhbjbujkaE4pw@public.gmane.org, Joe Bacom <joe@>>
wrote:> > > > > > Well, if it was done, then somebody has rolled the changes>
back>
(restore from> > > > >
backup). With the client library saying it's SP1, you can> > >
count> > >
it being> > > > >
SP1. I'm also assuming you ran iapi on the server and not>
some>
other client.> > > > >
I would reapply SP4 (it won't hurt anything if it's already> > >
been> > >
done) or go> > > > >
ahead and apply SP5.> > > > > >
On Thursday 09 March 2006 10:53 am, ask me wrote:> > > > > > > Tried iapi.. My manager is sure that SP4 upgrade was>
ok.. We got it solved last friday. Yes it did took us that long, thankfully it was not PROD and I had a family emergency and was not present. Our Tech lead took over the case with DCTM. Anyways, the server log was misleading,
docbase started up after updating the dmi_vstamp_s table with the expected versions for the serverconfig and the docbase config. Errors in the logfile were misleading as after the update of the version stamp for the serverconfig the error message was not quite clear that the version mismatch was for the docbase config object.
Thanks,
James
--- In documentum-users-hHKSG33TihhbjbujkaE4pw@public.gmane.org, Joe Bacom <joe@...> wrote:>
Hi James;>
Please post the solution (when you get it) back to the group so
everybody can > benefit from your misfortune >
On Friday 10 March 2006 11:30 am, ask me wrote:> > -> > Hey joe, I opened a case with DCTM. They are helping me out with> > this. Thanks again for your help.> >
James> >
-- In documentum-users-hHKSG33TihhbjbujkaE4pw@public.gmane.org, Joe Bacom <joe@> wrote:> > > I have to ask the obvious first, did you commit your changes?> >
Also, you> >
probably want to delete all of the cache files. These are
under> > > $DM_HOME/bin/dmcl> > >
You can either delete them or move them somewhere else.> >
Documentum will> >
recreate the folders on startup> > >
On Friday 10 March 2006 08:42 am, ask me wrote:> > > > Joe, Have to bother you again.. We changed the value for> >
sysobject> >
in the table dmi_vstamp and it initialized. But for> > > > dm_server_config, the value change doesnot seems to work.> > > >
stamp 12 was expected to be 11."> > > > Fri Mar 10 09:00:07 2006 552672 [DM_SESSION_E_INIT_FAILURE1]> > > > error: "Failure to complete Server Configuration> >
initialization."> >
This is the value in the DB> > > >
The value is 11 in the database В– here's the data in the
table:> > > >
R_OBJECT_ID I_APPLICATION I_STAMP> >
I_VSTAMP> >
1e003ca58000012e dm_server_config
11 0> > > >
what am i doing wrong? Did I make a wrong change.> > > >
Thanks> > > >
--- In documentum-users-hHKSG33TihhbjbujkaE4pw@public.gmane.org, Joe Bacom <joe@>
wrote:> > > > > No worries, I'm not after points. > > > > >
Glad I could help.> > > > >
On Thursday 09 March 2006 11:51 am, ask me wrote:> > > > > > Thanks Joe, I really appreciate your help. I wish I could> >
award> >
points.> > > > > >
James> > > > > >
--- In documentum-users-hHKSG33TihhbjbujkaE4pw@public.gmane.org, Joe Bacom <joe@>> >
wrote:> > > > > > > Well, if it was done, then somebody has rolled the
changes> >
back> >
(restore from> > > > > >
backup). With the client library saying it's SP1, you
count> > > >
it being> > > > > >
SP1. I'm also assuming you ran iapi on the server and
some> >
other client.> > > > > >
I would reapply SP4 (it won't hurt anything if it's
already> > > >
been> > > >
done) or go> > > > > >
ahead and apply SP5.> > > > > > >
On Thursday 09 March 2006 10:53 am, ask me wrote:> > > > > > > > Tried iapi.. My manager is sure that SP4 upgrade was> >
If you would like to report an abuse of our service, such as a spam message, please . Если Вы хотите пожаловаться на содержимое этой страницы, пожалуйста .
![DM_SYSOBJECT_F_INIT2]fatal:](http://qaix.com/i/logo_new.gif){kind=logo}
