Livelink's module has downgraded

[lg1234]

Hi

We got a very strange problem. The version of the OTEMAIL has 4.7.0 in the database but should have 4.7.1.
This problem has happened twice. And all I have to do is updating the database.

We are running LL 9.7.1 on windows 2003/Oracle.

Is there anybody got this problem before ?

I need help.

Thanks.

 

[appnair]

I would check all the different instances of livelink has been upgraded if it is in a cluster.Sometimes people upgrade a module in a single instance leaving out others thinking that that is only necessary.

Here's the practice I make for clarity.

Livelink A instance,Livelink B instance,Livelink C instance
running mod_1_1_0 and this is recorded in DB as the version.

I put the shrinkwrapped mod_1_1_1 into Livelink A and use module Upgrade version.I do not restart the server when indicated.
I follow same path on Livelink B and Livelink C
When all servers connected to the same database has been upgraded Re-start one by one.

You can also manually comment out the old module but that is for advanced LL admins(u need to be extremely patient with that) and most times when possible I use the easy way.





Well, if I called the wrong number, why did you answer the phone?
James Thurber, New Yorker cartoon caption, June 5, 1937
Certified OT Developer and probably certfiable,Livelink ECM Champion 2008

http://www.linkedin.com/in/appunair

 

[lg1234]

we do not have cluster..

But you gave me a clue, maybe I should look about the procedure of upgrading Explorer Pro.. I think OTEMAIL is related to Explorer Pro ..?

 

[ggriffit]

OTEMAIL as a module is part of Livelink Explorer and appears as "Livelink E-mail Services" in the Admin.InstallModules list.

Can you post the actual error you are getting and the situation that you are getting it in as there are a few situations that can cause this error.

Greg Griffiths
Livelink Certified Developer & ECM Global Star Champion 2005 & 2006

http://www.greggriffiths.org/livelink/

 

[lg1234]

it said:

the actual version of OTEMAIL is 4.7.0 but the database has 4.7.1

We got this error two times, they happened both on monday morning, no updates were done in that weekend.

 

[ggriffit]

I'd check what is in the [MODULE] section of your OpenText.ini files on all of your servers and make sure they are the same.

Additionally you could remove any earlier versions of OTEMAIL from the MODULE directory.

Greg Griffiths
Livelink Certified Developer & ECM Global Star Champion 2005 & 2006

http://www.greggriffiths.org/livelink/

 

[lg1234]

hi ggriffit,

The opentext.ini files on production and development are similar. And there's only one version of OTEMAIL from module directory..

Do you have any idea?

 

[ggriffit]

You say that the opentext.ini file's are similar, can you let me know what the differences are ?

You should have a line in the [module] section as follows :

otemail=_4_8_5

can you confirm what you have and what the version of the otemail folder has in the MODULE folder ?

Can you provide some more information about what you are trying to do / have done so that we get a better idea of what you are doing ?

Greg Griffiths
Livelink Certified Developer & ECM Global Star Champion 2005 & 2006

http://www.greggriffiths.org/livelink/

 

[lg1234]

In the opentext.ini:
otemailexp=4_8_2

In the module directory, I have:

otemail_4_8_2 and otemailexp_4_8_2

I called the Opentext support center since last week, here is what he said:
The root cause of your problem is that you’re connecting to the wrong database when you see the error you see. This means that there is a problem with the db user or with the db tablespace owned/assigned to the user. If you DBA is able to find the database that has Livelink Explorer 4.7.0 installed, we’ll know which database LL is connecting to and can work backwards from there.

Identify which database has schema for Livelink Explorer 4.7.0.

Unfortunately, my dba doesn't know what to look about and me neither..

now I'm waiting about Opentext for the next step ..

 

[ggriffit]

Locating the database should be simple enough, the OpenText.ini file as well as the following URL on the server :

http://localhost/Livelink/livelink.exe?func=admin.dbedit

this will give you the information about which database you are connected to.

You will then need to confirm if this is the correct database or not and go from there.

Greg Griffiths
Livelink Certified Developer & ECM Global Star Champion 2005 & 2006

http://www.greggriffiths.org/livelink/

 

[lg1234]

The database connected is correct. We only have one database mounted on the server, I think we need to look inside the db to see about the schema or something like that.
I'm really lost when it is question about oracle..