Skip to main content

Clearcase undelete file

Suppose user has mistakenly deleted file /org/projects/rahul/data.xml.
To get back the file in clearcase revision, do following steps:
  1. From a dynamic view, go to /org/projects/ folder.
  2. /org/projects$ cleartool desc rahul
    This will print information like,
    directory version "rahul@@/main/3"
    created 2009-12-30T04:02:42-05:00 by Rahul Singhai (singrahu@gmail.com)
    "Version created by Namespace modification subsystem
    Uncataloged file element "data.xml"."
    Element Protection:
    User : rahul    : rwx
    Group: singhai  : rwx
    Other:          : ---
    element type: directory
    predecessor version: /main/2
    
  3. Get lastest version of affected folder and type
    /org/projects$ cleartool rmver -ver /main/3 rahul
    This will remove latest version from clearcase, and folder will rollback to previous version.


Comments

Andrew said…
I wish IBM support was this coherent! Thank you for this, you saved the day!
Mike said…
Thanks for the instructions. Worked perfectly.
Anonymous said…
You saved my day..Thanks
Tim said…
Worked perfectly, thanks

Popular posts from this blog

MPlayer subtitle font problem in Windows

While playing a video with subtitles in mplayer, I was getting the following problem: New_Face failed. Maybe the font path is wrong. Please supply the text font file (~/.mplayer/subfont.ttf). Solution is as follows: Right click on "My Computer". Select "Properties". Go to "Advanced" tab. Click on "Environment Variables". Delete "HOME" variable from User / System variables.

wget and curl behind corporate proxy throws certificate is not trusted or certificate doesn't have a known issuer

If you try to run wget or curl in Ununtu/Debian behind corporate proxy, you might receive errors like: ERROR: The certificate of 'apertium.projectjj.com' is not trusted. ERROR: The certificate of 'apertium.projectjj.com' doesn't have a known issuer. wget https://apertium.projectjj.com/apt/apertium-packaging.public.gpg ERROR: cannot verify apertium.projectjj.com's certificate, issued by 'emailAddress=proxyteam@corporate.proxy.com,CN=diassl.corporate.proxy.com,OU=Division UK,O=Group name,L=Company,ST=GB,C=UK': Unable to locally verify the issuer's authority. To connect to apertium.projectjj.com insecurely, use `--no-check-certificate'. To solution is to install your company's CA certificate in Ubuntu. In Windows, open the first part of URL in your web browser. e.g. open https://apertium.projectjj.com in web browser. If you inspect the certifcate, you will see the same CN (diassl.corporate.proxy.com), as reported by the error above

Kafka performance tuning

Performance Tuning of Kafka is critical when your cluster grow in size. Below are few points to consider to improve Kafka performance: Consumer group ID : Never use same exact consumer group ID for dozens of machines consuming from different topics. All of those commits will end up on the same exact partition of __consumer_offsets , hence the same broker, and this might in turn cause performance problems. Choose the consumer group ID to group_id+topic_name . Skewed : A broker is skewed if its number of partitions is greater that the average of partitions per broker on the given topic. Example: 2 brokers share 4 partitions, if one of them has 3 partitions, it is skewed (3 > 2). Try to make sure that none of the brokers is skewed. Spread : Brokers spread is the percentage of brokers in the cluster that has partitions for the given topic. Example: 3 brokers share a topic that has 2 partitions, so 66% of the brokers have partitions for this topic. Try to achieve 100% broker spread