Our customer tried to increase global_database_id option (in test DB for now), but it took more than 7 hours with no end until they restarted the server by force. After that I see that the global_database_id value has actually changed. But I guess that something could go wrong. So there are the questions:
- Are there any tricks to quickly change global_database_id, i. e. avoid such a huge hanging?
- What should be checked (if that occurs in production) to see if there is anything to fix after such unmanaged restart?
Maybe someone could list all the actions that are being performed when executing this statement (to understand what is really happening and what might not be finished):
SET OPTION public.global_database_id = '4';
One of ~350 tables with global autoincrement(50000000) columns has almost reached the top of the range.
The database size is >200 GB.
SQL Anywhere version: 184.108.40.20658.
18 Oct '16, 04:42