DB2 uses a name generation algorithm to enforce uniqueness if it is attempted. The second potential problem area poses quite a bit of trouble. The primary key is dropped. A foreign key is dropped. This is not a good idea either.
Misconceptions can occur.
For example, in DB2, if no clustering index is explicitly defined, DB2 will use the first index created as a clustering index. Let's look at one final example from the real world to better illustrate why it is a bad idea to embed specialized meaning into names. Consider what would happen if we named corporations based upon what they produce. When IBM began, they produced typewriters. If we named corporation like we name database objects, the company could have been named based upon the fact that they manufactured typewriters when they began.