Cannot edit strategy or save new one

[superman]

Hello,

strange thing hapenned. I just found out that I cannot edit or save a new strategy. Errors like [b]cannot write to configuration database[/b] (its not in read only mode) - [b]operation cancelled[/b], or [b]cannot read from the .lst file[/b] are showing up.

Has anyone encountered such an issue?

[terry]

Anything n IRD log (assuming max log details are enabled, like level of diagnostic 4, IRD, config server event sources, all event types)?

[vmc]

Shared install of IRD?

Sent from my Redmi Note 3 using Tapatalk

[cavagnaro]

Check database access to the strategies DB is ok. Find the DAP and verify settings


Enviado de meu E6633 usando Tapatalk

[superman]

Examining the configServer logs seems that the configDB is the issue. Tables cfg_max_dbid and cfg_flex_prop are out of sync... Issue with the configurtion database.. Rather disturbing. Do you know if there are any integrity check tools/scripts?

[vmc]

Seem to recall there is a fix script for that particular db issue.  May need to ask Genesys for it.

Sent from my Redmi Note 3 using Tapatalk

[superman]

Yes vmc, I have found one but need to check with genesys if its up to date because there are some inconsistencies with the schema

[hsujdik]

[quote author=superman link=topic=10601.msg48205#msg48205 date=1505385925]
Yes vmc, I have found one but need to check with genesys if its up to date because there are some inconsistencies with the schema
[/quote]
Just as a side note, this usually happens when you start two config servers as primary

[superman]

[quote author=hsujdik link=topic=10601.msg48212#msg48212 date=1505400035]
[quote author=superman link=topic=10601.msg48205#msg48205 date=1505385925]
Yes vmc, I have found one but need to check with genesys if its up to date because there are some inconsistencies with the schema
[/quote]
Just as a side note, this usually happens when you start two config servers as primary
[/quote]Thank you for your contribution hsujdik. Although I cannot eliminate the posibility, I do not think that this was the issue. Because there was a db migration, I believe  that maybe during the configuration after db migration one of the confServers was writing to the old db and after the switchover mixed things up. We have 2 confServers and 2 confServer Proxies so I believe that this increases the posibility.
Do you know if the script that I have found in Genesys Knowlege database which updates dbids will address the issue? Any prior experience with this problem?

[genesianonano]

We have had this problem, due there were not space in the tablespace

Check the configuration server logs for the message "ORA-01653 unable to extend table".