Guides for ClearCase Best Use Practices
ClearCase is using a database that is mapped into a file system defined by the view configuration rules. Databases keep object identification information unlike normal file systems. If you copy a file to a new name and create a new element it will have a different object identification and thus a different history and you would not be able to use ClearCase to merge the two files.
Common opportunities where object identification problems can occur during development are when a file is copied as was described above or if a directory is branched to two different branches and a file is added to each branch directory with the same name. This is termed the "evil twin" as there are now two different database objects with the same name that have different version histories and can not be merged through the normal ClearCase merge process.
Finally this can also occur when a file or directory is removed and a decided that they are still needed so they are copied from another view and added back to source control again. This is another way to create the evil twin situation.
Use the defined procedures below to properly use the ClearCase configuration management system. If you are in doubt as to the correct way to accomplish a change that needs to be done please ask for guidance.