Alix Jermyn wrote: > But, could you tell me why I get this error. We installed another SAP DB instance >on another server, successfully created the same table via the same script, and ran >into the same problem (and fixed it as below). In neither case has the problem >reappeared after the inital setup.
> I am just a little worried that a production server should should so easily get >corrupted indexes, or if we are doing something that causes this. > This causes us a particular problem in that inserts to the affected table inside a >dbproc return with $rc = 0, and so further processing occurs, ending with a >successful subtrans end, commiting it all and leaving us with a non-existent row. >>"Marcin P" <[EMAIL PROTECTED]> wrote in message >atkprq$6t6$[EMAIL PROTECTED]">news:atkprq$6t6$[EMAIL PROTECTED]... >> MeddelandeHi, Alix >> It is of course possible. >> You have to repair (or let's say - create once again) this index. >> The easiest way us to use DBM GUI ->Recovery -> Index >> select this index, and then Recover. >> And it works perfectly :))) >> >>> >>> U�ytkownik "Alix Jermyn" <[EMAIL PROTECTED]> napisa� w wiadomo�ci >>> [EMAIL PROTECTED]">news:[EMAIL PROTECTED]... >>> Using SAP DB v7.3 via Sql Studio I get the following error when trying the >>> simple insert below: >>> >>> insert into country(ISO_CODE) values ('QQQ') >>> >>> -9041 General error;-9041 POS(1) System error: BD Index not accessible. >>> [ODBC] [S1000] General error If you stop your database without a normal shoutdown indexes may become "not accessible" in SAP DB. To speed up the restart SAP DB doesn't recreate indexes at restart time if a create index is found in the log. Instead the administartor could recreate these indexes via DBM GUI or dbmcli when the database is idle. Kind regards, Holger _______________________________________________ sapdb.general mailing list [EMAIL PROTECTED] http://listserv.sap.com/mailman/listinfo/sapdb.general
