Description of problem: As part of installation, a number SQL schemas are run against database account. As these SQL files come from different projects and share some common tables they must not drop tables and also must be guarded against creating tables that already exist. Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. Run an installation and view sqlresults.log for sqlexceptions caused by multiple table creates and for the existence of drop table statements. 2. 3. Actual results: Expected results: That no sqlexceptions exist due to multiple table creates or that no drop table statements have been run. Additional info:
*** Bug 1014562 has been marked as a duplicate of this bug. ***
Verified in ER7