Error 15262 - Requested schema change not allowed on-line, aborting the change

[Toomas Kask]

Hi!

What might trigger such error?
>> Requested schema change not allowed on-line, aborting the change (15262)

Tried to add some new fields into existing DB.
Loading same .df into production failed but loading into development DB succeeded.
Both DB's were in use.

OS: OpenEdge 11.3.2 @ Solaris
Didn't find anything useful from KB.

Ideas?


Regards,
Toomas

[Chris Ruprecht]

how many users do you have in the dev database when you load it?
how many do you have in the prod database?

[Toomas Kask]

Hi!

Production - 600+
Development - 200+
Only major difference I see is that in production we have 30-35 self-service clients connected and in development we have none.
KB says nothing about this that I cannot have self-service users connected.

I tried to add total 24 new fields to 4 different tables.
No indices, no sequences, no blobs, only char/integer/logical/date-time fields.
And we have done this before without any problems, at least adding new table(s) is always succeeded.

Regards,
Toomas

[Dmitri Levin]

Tere Toomas

> I tried to add total 24 new fields to 4 different tables.

Could you try to split the .df into 24 .dfs. One field addition in each .df and try to add them into production, until you get the one that does not work. Then post the .df with the table.df that you are adding it to. That may help to get to the bottom.

Adding new tables and sequences has never been a problem and works 100% fine. Adding new fields also worked for me, but occasionally users get CRC errors afterwords until we restart the db. The whole so called "Online schema change" need to be revisited by PSC.

Dmitri Levin
alphabroder Co.



----------------------------------------
> From: Tooma...@seb.ee
> To: crup...@progress.com
> CC: d...@peg.com
> Subject: RE: Error 15262 - Requested schema change not allowed on-line, aborting the change
> Date: Wed, 22 Apr 2015 07:27:15 +0000