Hi List-Members,

after my server has been hacked, I had to install almost everything from
scratch and I'm still working to get the sapdb-archiv going again.

Right now, Im encountering a "table is read only" message after inserts or
delete statements. The table has been filled before so its not likely a
permission problem. Tablespace is filled 10% - it shouldnt be a tablespace
problem.

I generated a medium FILE for logsaving
medium_put logsave /tmp/autobackup FILE AUTO
and envoked a autolog_on which should take care of the logfiles ?

The problem does only occur on this specific table - other tables don't
have status "read only"

Any hints to get the archiv going again?

TIA
Andreas

_______________________________________________
sapdb.general mailing list
[EMAIL PROTECTED]
http://listserv.sap.com/mailman/listinfo/sapdb.general

Reply via email to