I heard a bad news from someone that one of his colleagues dropped an Oracle schema by mistake in Oracle Enterprise Manager (OEM), because the OEM seems in hang status, so they did some random mouse clicks or did some random key strikes. The whole database is 500GB, running in no archive log mode, almost all the data in this database is lost now.
This is not the first time of this kind of mistakes, someone dropped a tablespace in OEM by mistake because the OEM hang up. And somebody drop some tables in Toad and PL/SQL Developer by typing wrong key or wrong mouse click. In my tools design, I will not include this kind of features, as a matter of fact, the people who made the mistake may not know how to drop a schema with objects in command line tools, he may not know how to drop a tablespace with segments in it. But they made this kind of mistakes in GUI tool easily.
Of cause, OEM is not the root cause, they can control the access, they should take backup of their database. But I have heard at least 3 issues caused by OEM hang.
So create a read only account for OEM, do not make changes to database with OEM, and don't think that you will never make this kind of mistake. Good luck!
Comments (5)
This is a OLAP type database, contains 3 years of summarized data.
Finally they decided to rebuild the database, and reload the data from business database.
Posted by anysql | September 21, 2007 1:38 PM
This is a very useful advise!
However, would you like to explain more detail?
I think the only DBA use OEM, no one to do.
Posted by Tuan Anh Tran | September 27, 2007 8:06 PM
It's the DBA who drop the schema by mistake.
Posted by anysql | September 28, 2007 8:05 AM
How to create a read only account for OEM?
Posted by HausGeíst | February 11, 2008 9:43 PM
Create an account with select any table system access and select_catalog_role role, it should work.
Sorry, I have no OEM env to test it.
Posted by anysql | February 13, 2008 9:22 AM