Hi all,
How to check whether a table is in read-only mode or read-write mode and how to convert a table in the read-only mode to read-write mode.
Thanks and Regards;
K.Diwakar
Printable View
Hi all,
How to check whether a table is in read-only mode or read-write mode and how to convert a table in the read-only mode to read-write mode.
Thanks and Regards;
K.Diwakar
Check the status of the tablespace this table belongs to. Only tablespace (or a whole database) can be set to read-only or read-write. You can't apply read-only status to a table.
Hi Modic,
Assuming the concerned tablespace in read-only mode, I gave the command:
alter tablespace tablespace-name read write;
and Oracle says:
tablespace 'tablespace-name' is not read only - cannot make read write.
I think this makes things clear that the tablespace is in read-write mode. Also the database is found to be in the read-write mode.
The problem started when we had to move the particular table to another tablespace and we also dropped a few indexes and recreated them. After that we could not delete the records through the application. Could any one suggest any possible solutions??
Regards,
K.Diwakar
[Edited by diwakar on 10-07-2002 at 12:47 AM]
What is the error you get? Have you tried deleting from sqlplus?Quote:
Originally posted by diwakar
After that we could not delete the records through the application. Could any one suggest any possible solutions??
Sanjay
[Edited by SANJAY_G on 10-07-2002 at 01:28 AM]
Yes..the problem is solved. Actualy through the application, the records are deleted with the the help of the delete command on the primary key. After moving the table to another tablespace, all the indexes were recreated. And the error we got on the application was that the delete command was not getting executed(we did not have the oracle error). The problem was solved by executing the same command on the sql prompt as rightly prompted by Sanjay. One of the indexes was found to be in an unstable state.:
ora-01502
and after the index was re-created, the command works.
What is not clear is we got this error after recreating the concerned index for the second time and only after recreating this for the third time the error disappeard.
Anyway the problem is solved and thanks to everyone.