This question arised while discussion of CORE-5242. Vlad recommended me to ask this here:
===
SQL> select rdb$index_name from rdb$indices where rdb$relation_name='RDB$DEPENDENCIES';
RDB$INDEX_NAME
===============================
RDB$INDEX_27
RDB$INDEX_28
SQL> ALTER INDEX RDB$INDEX_27 ACTIVE;
Statement failed, SQLSTATE = 28000
unsuccessful metadata update
-ALTER INDEX RDB$INDEX_27 failed
RDB$INDEX_NAME
===============================
RDB$INDEX_27
RDB$INDEX_28
SQL> ALTER INDEX RDB$INDEX_27 ACTIVE;
Statement failed, SQLSTATE = 28000
unsuccessful metadata update
-ALTER INDEX RDB$INDEX_27 failed
===
So, how can some RDB$-index be repaired in 3.0 if this annoyance will occur ?
------------------------------------------------------------------------------ Mobile security can be enabling, not merely restricting. Employees who bring their own devices (BYOD) to work are irked by the imposition of MDM restrictions. Mobile Device Manager Plus allows you to control only the apps on BYO-devices by containerizing them, leaving personal data untouched! https://ad.doubleclick.net/ddm/clk/304595813;131938128;j
Firebird-Devel mailing list, web interface at https://lists.sourceforge.net/lists/listinfo/firebird-devel
