What are the reasons why oracle can still read and write tables after deleting tablespaces?
This article shares with you about the reasons why oracle can still read and write tables after deleting tablespaces. The editor thinks it is very practical, so share it with you as a reference and follow the editor to have a look.
Background: tablespace=my_01, table=class
After deleting the my_01.dbf file in linux, the first two insert and select operations reported errors, but after the second insert, it was successful, and the commit was successful, and then the read and write were normal. Why?
Thank you for reading! What are the reasons why oracle can still read and write tables after deleting tablespaces? I hope the above content can be of some help to you, so that you can learn more knowledge. if you think the article is good, you can share it for more people to see!