Getting errors when adding fields in the table cmn_cost_center and importing the update set to PROD

Nesrine1
Tera Expert

Hello everyone,

 

I had to add 3 fields in the table "cmn_cost_center", while in development and test instances i didn't had any issue, I got errors when committing update set to PROD instance.
I got these errors :

Nesrine1_0-1705943312069.png

It created me the fields but the column label where empty, when i try to fill them it delete what I put automatically.
I deleted the fields and created them, I got these errors

Nesrine1_0-1705998510024.png

Nesrine1_1-1705998525071.png

when i look for the label active, and I do "show matching" it finds it and in the filter we can see the name of the field

Nesrine1_2-1705998545927.png

when I export the fields with xml getting same errors 

Nesrine1_3-1705998663476.png

Did anyone got these kind of errors, any help would be welcome

 

Thank you all

 

Best regards

 

1 ACCEPTED SOLUTION

Nesrine1
Tera Expert

For information,

my team raised a case for servicenow and the solution was this :


Issue:
You are unable to create a new dictionary entry in the “cmn_cost_center” table.
When you attempt to add the column you get the below error:
(conn=136513) ALGORITHM=INSTANT is not supported. Reason: Cannot change column type. Try ALGORITHM=COPY”
Most Probable Cause:
You are running into this issue because your instance is attempting to use ‘instant alter’ to modify the table when adding the column.
The ‘instant alter’ feature was recently enabled on all eligible instances where the previous default for the property was ‘false’.
However, not all tables can be modified by using the ‘instant alter’ method and there is currently a known issue where the system does not fall back to the ‘online alter’ method when this occurs.
The issue has been recorded through PRB1672320 and is listed to be fixed in the following versions:
  • Vancouver Patch 6
  • Washington DC
Solution Proposed:
As a workaround, kindly change the value from ‘true’ to ‘false’ for the ‘glide.db.instant_alter.enabled’ system property and retry adding the column.

View solution in original post

1 REPLY 1

Nesrine1
Tera Expert

For information,

my team raised a case for servicenow and the solution was this :


Issue:
You are unable to create a new dictionary entry in the “cmn_cost_center” table.
When you attempt to add the column you get the below error:
(conn=136513) ALGORITHM=INSTANT is not supported. Reason: Cannot change column type. Try ALGORITHM=COPY”
Most Probable Cause:
You are running into this issue because your instance is attempting to use ‘instant alter’ to modify the table when adding the column.
The ‘instant alter’ feature was recently enabled on all eligible instances where the previous default for the property was ‘false’.
However, not all tables can be modified by using the ‘instant alter’ method and there is currently a known issue where the system does not fall back to the ‘online alter’ method when this occurs.
The issue has been recorded through PRB1672320 and is listed to be fixed in the following versions:
  • Vancouver Patch 6
  • Washington DC
Solution Proposed:
As a workaround, kindly change the value from ‘true’ to ‘false’ for the ‘glide.db.instant_alter.enabled’ system property and retry adding the column.