No primary key value for foreign key 'ISYSTABCOL' in table 'ISYSCOLPERM'

[Volker Barth]

Hi all,

running SA 10.0.1.3686 and .3712 on Win 2003 Server SP1.

The above message appears when I try to add a column to a table.
It's just a simple one:
alter table dbo.T_MaZuGavAktion
add fkz_BeilageNrLautVersand int check (@Wert > 0) null;

There is a view based on this table, and several users have been granted
update column rights on this view.

It is only possible to execute the "ALTER TABLE ADD column null" statement
when I revoke the update column rights from the view before (and re-grant
them afterwards).

That happened once in the past weeks and again today. Adjusting the column
rights is easy to do (at least as soon as this workaround is known :)). The
worse part on it is that the server crashed several times during the attempt
to do the simple ALTER TABLE (before I revoked the column rights), so there
might be more to this.
I can reproduce the problem on a different (Win2K) box.

Is this a known problem?

The system is running, and backups are working, so fortunately I'm not in
need for tech support, but maybe iAnywhere is interested in more details?

Volker

[Glenn Paulley [iablog.sybase.com/paulley]]

Absolutely we are interested, Volker. If you can package up a simple
repro, my team will be happy to look at it in short order.

Glenn

--
Glenn Paulley
Director, Engineering (Query Processing)
Sybase iAnywhere

Blog: http://iablog.sybase.com/paulley

EBF's and Patches: http://downloads.sybase.com
choose SQL Anywhere Studio >> change 'time frame' to all

To Submit Bug Reports: http://case-express.sybase.com

SQL Anywhere Studio Supported Platforms and Support Status
http://my.sybase.com/detail?id=1002288

Whitepapers, TechDocs, and bug fixes are all available through the
Sybase iAnywhere pages at
http://www.sybase.com/products/databasemanagement/sqlanywhere/technicalsupport

[Volker Barth]

Well, I guess in the short term I can only offer the complete DB and the
accordings logs (about 2.5 GB). During my attempts, I had unloaded the DB
which reduced the size to about 1.4 GB but hasn't solved the problems. So
maybe the unloaded DB would do, too.

In the cases where the server crashed, in some cases (but not in all) that
lead to problems with later attempts to valid as stated in the server log:

I. 26.06 20:48:11. Maintenance plan MT_ValidateDb for Abgleich on GDV_Server
started on 2008-06-26 at 20:48:11.456
I. 26.06 20:48:11. Disabling new connections started on 2008-06-26 at
20:48:11.456
I. 26.06 20:48:11. Disabling new connections finished on 2008-06-26 at
20:48:11.456
I. 26.06 20:48:11. Validation started on 2008-06-26 at 20:48:11.456
I. 26.06 20:48:11. Validating database pages
I. 26.06 20:48:43. Cachegröße berichtigt auf 669708 KByte
I. 26.06 20:49:43. Cachegröße berichtigt auf 692864 KByte
I. 26.06 20:50:43. Cachegröße berichtigt auf 713020 KByte
I. 26.06 20:51:20. The maintenance plan has ended because of the following
error:
I. 26.06 20:51:20. Laufzeit-SQL-Fehler - Datenbankvalidierung für
Datenbankdatei "D:\DATA\Abgleich\Abgleich.db" fehlgeschlagen
I. 26.06 20:51:20. SQLSTATE: 40000
I. 26.06 20:51:20. SQLCODE: -300
I. 26.06 20:51:20. Re-enabling new connections started on 2008-06-26 at
20:51:20.806

As to a small repro, I don't feel able to check for one in the next days.

So please let me know if it makes sense for your team to look at the
complete db.

Volker

"Glenn Paulley [iablog.sybase.com/paulley]" <pau...@ianywhere.com> wrote in
news:4864e26b$1@forums-1-dub...

[Bruce Hay]

By coincidence, the same problem was reported separately earlier this week
(issue 534294). We already have a simple repro for it and are working on a
fix. Until the fix is available, the only known workaround is to drop the
column update permissions on the dependent view before altering the
underlying table.

SQL Anywhere Developer Community:
http://www.sybase.com/developer/library/sql-anywhere-techcorner
SQL Anywhere Blog Center: http://www.sybase.com/sqlanyblogs

"Volker Barth" <No_VBarth@Spam_GLOBAL-FINANZ.de> wrote in message
news:4864ebda@forums-1-dub...

[Volker Barth]

Bruce, thanks for the information.
Does your repro also lead to server crashes as I mentioned?
Or do I have to think that this is due to a different problem?

Volker

"Bruce Hay" <h_a_y~a_t~i_a_n_y_w_h_e_r_e~d_o_t~c_o_m> wrote in
news:4864fa80@forums-1-dub...

[Bruce Hay]

Yes, a server crash is possible after this error has been reported.

SQL Anywhere Developer Community:
http://www.sybase.com/developer/library/sql-anywhere-techcorner
SQL Anywhere Blog Center: http://www.sybase.com/sqlanyblogs

"Volker Barth" <No_VBarth@Spam_GLOBAL-FINANZ.de> wrote in message

news:4864fb88$1@forums-1-dub...

[Volker Barth]

Should I say "Glad to hear"? :)

So at the moment I will not prepare anything to upload.
Feel free to ask for more if this might help your investigations.

Best regards
Volker

"Bruce Hay" <h_a_y~a_t~i_a_n_y_w_h_e_r_e~d_o_t~c_o_m> wrote in

news:48650e0d$1@forums-1-dub...