[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference utrop1::linkworks_v3

Title:LinkWorks V3.0 Notes Conference
Notice:LNX_APO = APO issues, LINKWORKS_V3 = V3.0 issues
Moderator:tacklr.apd.dec.com::TACK_Lm::TACK_L
Created:Tue Jun 28 1994
Last Modified:Fri Jun 06 1997
Last Successful Update:Fri Jun 06 1997
Number of topics:2269
Total number of notes:8338

2240.0. "sql-Error on T table with a 2 server's cluster" by TAV02::SHAPIRA () Tue May 20 1997 13:08

We have a LinkWorks cluster, based on Windows NT. The DB is Sql-Server v6.5.
LinkWorks 3.0.8, december release.

A software componnet was installed. The installation was successfull. In this
copmonent a new Object class is defined, including some attribute assignment.

The cluster consist of 2 servers. When a user has a desk in server B (a cell
server) a creates an instance of the new class with no problems.
When a user has a desk in server A (the managment server) creation of an
instance of the class results in sql-error. The error is that table T5... does
not exist.

Compering the sql server celldb in both servers, we have found that indeed,
table T5... exists only on server B. We know that the T tables represents the
values of user-defined attributes assigned to a class.

Question:

Should the T table exist in both servers?
If yes - why it is created only on one?
If no - how does it work?

In any case - how to procede?

Thanks,
Yariv
T.RTitleUserPersonal
Name		DateLines
2240.1maandajr.apd.dec.com::maandag_jWed May 21 1997 10:4219
Yariv,

>Should the T table exist in both servers?
yes
>If yes - why it is created only on one?
on the Commit Changes after the assignment, these tables are created.
I guess soemthing went wrong in the creation process on the management
server. In that case there must be an error reported in the ER-*-* file
somewhere under %OPROOT%\cell.
>If no - how does it work?

In any case - how to procede?
Did you try to restart LNX on the management server? Maybe that helps because
also when a cell is down during the commit, the T.. tables are created at the
first startcell.
If that does not work, you probably have to unassign and reassign the
attributes and Commit the changes.

Jos
2240.2Problem solution ...TAV02::CHAIMSemper ubi Sub ubi .....Thu May 29 1997 10:4625
I believe that we have discovered why the problem occurred and with the help of
Jos Maandag we have a solution:

We went on-site to take a closer look at things and during our investigation we
discovered an ER-18-97 file from two weeks ago when the SWC was originally
installed. Thie ER-18-97 showed "permission debied" errors on each attempt to
create a T... table. Inspection of the SQL database showed SA as the owner of
the celldb database and NOT omdba. We reset the ownership to be omdba.

Now it all became clear; since the T... tables were NOT created, then an
invalid error would be generated every time a user attempted to create a new
object of this object class. Reinstalling the SWC doesn't solve the problem
immediately since LINKworks thinks that these tables already exist and makes no
attempt to recerate them. This is due to the fact that two system tables,
ATTRTAB & ATTRFELD, contain rows referrencing these T... tables. 

The way to solve this problem is to delete the rows which referrence these
tables from both the ATTRTAB and ATTRFELD tables and then "commit changes".

We haven't yet implemented this at the customer site, but we did successfully
test this method on a test SWC which we installed and then dropped the T table. 

Thanks to Jos Maandag for his undevoted assistance.

Cb.