OAT Tables???

Good Morning Informix-people, We are running 11.50.FC5 on AIX 5.3. WE recently upgraded to OAT version 2.70. Since then, I have some new sysadmin tables that are owned by the guy who initially installed and configured the new OAT. He then went into each system to test the connectivity but claims not to have done anything. However, we now have new tables in the sysadmin database (background_task, job_status, mon_compression_estimates). Did these tables get created automatically with the new version of OAT? Also, we do not want any database entities owned by individuals here, can I drop the tables? Is there a preferred way to make Informix own them? Incidently I am RTFMing now but still wanted to pose the qwuestion in case someone has more intimate knowledge here. Thanx, Dan

Hi Dan, Yes, these tables are created automatically by OAT. You can drop the tables; there is no adverse impact to doing that, except just be aware that OAT will create them again if it finds that they are not there. The only way to stop OAT from creating them is to run OAT in read-only mode, but then you lose the ability to do actions in OAT. Since it seems that you don't mind that the tables are there, you just want them owned by informix, I would recommend the following. Drop the tables and then login to OAT as informix. Then go to the OAT > Storage page which is where these tables are deployed. Since you are logged into OAT as informix, the tables will be created with informix as the owner. After this, you can log out as informix and then continue to use OAT with whatever other users you have been using it with. Here is the full list of tables and procedures that you'll need to drop from the sysadmin database: DROP FUNCTION admin_async; DROP TABLE job_status; DROP FUNCTION mon_estimate_compression; DROP FUNCTION get_compression_estimate; DROP FUNCTION admin_async_estimates; DROP TABLE mon_compression_estimates; DELETE FROM ph_task where tk_name = "mon_compression_estimates"; Regards, Erika

Thank You Erika. Dan