[ClearCase] Type manager "_xml2" failed create_version operation.

에러증상 : 

 1. update와 checkout은 정상적으로 동작

 2. check in 동작시 오류 발생

Error checking in '..........................................'

Type manager "_xml2" failed create_version opertation.

Unable to check in '........................................'

해당 파일 ElementType 확인하기

ClearCase element type

All elements in a ClearCase VOB have an element type associated with them. This type lets ClearCase know how to handle the different operations (such as creating a new version, or reading a specific version).

The following is example output for the syntax shown in the first line below:

>cleartool describe -long catalog.bin

version "catalog.bin@@\main\1"

created 08-Mar-05.16:10:47 by Marechal Laurent (HOST1)

  Element Protection:

    User : IBM \nlxxxx : r--

Group: IBM \yyyy : r--

Other:          : r--

  element type: compressed_file

predecessor version: \main\0

Element types can be created by any user. They are primarily used to assign a customized type to specific files for example, c_source to all .c or .cpp file). This allows particular ClearCase commands to be run against these element types (such as a cleartool find restricted by element type).

Creation of custom element types is supported and even required sometimes (for example, the nomerge type for UCM in ClearCase version before v2003.06.00)

Type Manager

현재 Clearcase에서 사용되어지고 있는 type들과 관련된 정보들. 그리고 해당 Type들을 관리하는 manager에 대한 정보를 확인한다. 

ClearCase type manager

Each element type is bound to a type manager. There are several predefined element types provided by default (number depends on the ClearCase release) like file, text_file, compressed_file. A full list of the existing types can be retrieved with a single cleartool command. On ClearCase 8.0.0.0  it returns the following:

>cleartool lstype -s -kind eltype

binary_delta_file

compressed_file

compressed_text_file

directory

file

file_system_object

html

ms_word

rose

rosert

text_file

utf16be_file

utf16le_file

utf32be_file

utf32le_file

utf8_file

xde

xml

Each of these element types has an associated type manager. This can be seen when you describe any of these element types.

>cleartool describe -long eltype:compressed_file

element type "compressed_file"

  created 08-Mar-05.14:26:49 by Marechal Laurent (HOST1)

"Predefined element type used to represent a file in

compressed format."

owner: IBM \nlxxx

group: IBM \yyyy

scope: this VOB (ordinary type)

type manager: z_whole_copy

supertype: file

meta-type of element: file element

The last three lines contain the type manager information.. These line define the type manager used for this element type (z_whole_copy) and the supertype used (file). For more information review the ClearCase reference guide on the topic of mkeltype (cleartool man mkeltype) for more information.

순서대로 문제가 되었던 파일은 element type이 xml이었고 cleartool describe -long eltype:xml을 실행시킨 결과는 다음과 같았다. 

element type "xml"

  created 2006-10-12T16:16:32+09 by OOO (XXXXXXXXX)

  "Predefined element type used to represent an XML file."

  owner: NT: XXXXXXXXXXX

  group: XXXXXXXXXXXXX

  scope: this VOB (ordinary type)

  type manager: _xml2

  supertype: binary_delta_file

  meta-type of element: file element

해당 파일의 type manager가 _xml2라는걸 확인할 수 있었다. 이제 해당 오류메시지의 근원을 알아냈다. 

자 그럼 저 메시지의 내용은 _xml2 라는 type manager가 create_version에 실패했다는 말인데.. 즉, 해당 하나의 파일이 문제가 아니라 type manager가 _xml2로 지정된 모든 형상관리 항목들이 check in이 안될거라는 말이 된다. 

다음으로 check in을 할 때 무슨일이 벌어지는지 찾아보아야겠다. 

To be Continue........................insert coin????? .... plz!!!!!!!!!!