The main aims of this paper survey the types of conflicts that occur in multidatabase and concentrate on naming conflict and presents a new method depending on bridge design to resolve all types of naming conflicts and it provides examples for each type. Government units and large companies have different branches scattered over a wide area; each branch has its own database, these databases may be homogeneous or heterogeneous depending on the data itself, these branches need to integrate these databases to provide a unifor8m view of the data. In some organizations there may be legacy systems that can’t interact with each other, so these organizations can’t make use of these systems unless they are integrated together in one global database, here also comes the need for integrating already existing databases in one global database, due to the lack of integrated database many organizations make use of only a few parts of the collected data, since the data is coming from different sources and designers, so data collection and integration is now becoming the most important one of the information system area. There could be many conflicts which could make the integration very difficult.

Conflict Mulidatabase Integration Schema Bridge .