It does indeed Marcin - thanks!
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.
/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 :)))
>
> Marcin Pytel
> Talex S.A. Pozna�
>
>
> U�ytkownik "Alix Jermyn" <[EMAIL PROTECTED]> napisa� w wiadomo�ci
> 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
>
###########################################
This message has been scanned by F-Secure Anti-Virus for Microsoft Exchange.
For more information, connect to http://www.F-Secure.com/
This does NOT guarantee that the mail is completely virusfree!
Treat ALL E-mails with caution!!!
