Status for Andrew DeFaria

• Attended meeting regarding SJ/Irvine Vob move. Shivdutt is investigating doing vob moves instead of replication. Briefly discussed Disaster Recover options.
• Got Chris' scripts that check for invalid characters in string data for the ASCII character set to work on our test PQA database. Found invalid characters.

Invalid ASCII Characters in Clearquest databases

With Clearquest 2003.06.15 there is more support for internationalization. This means that Clearquest now implements a Code Page which essentially defines the valid character set for data. If it encounters invalid characters the user must correct them.

Question is do we have invalid characters in the current database. Chris Rump had found such invalid characters when performing his Clearquest migration from Irvine -> San Diego. I've quickly adapted his scripts to check a few fields in the TO database and found some. So far all I've found are non ASCII characters for the apostrophe. We think this happens when a user copies and pastes text from Microsoft Word into Clearquest (Thanks Microsoft! :-()

In any event I still need to update the script to check all string oriented fields. If only a few isolated cases can be identified (e.g. Apostrophes, perhaps soft carriage returns, etc.) then perhaps this could be made into a function that will check for invalid ASCII characters and fix them

Posted by at 5:16 PM | Permalink

• Set up CQ Web Server on p4test. Web client has been updated. Seems a little sluggish
• Investigated CQ Web Performance tweaking
• Looked into Chris's scripts for handling CQ code page problems

Posted by at 2:26 PM | Permalink

• Tried to help Arun in Bangalore to be able to create views
• Investigated trigger set up for SJ/Irvine
• Investigated relocate sync_locked problem

rgy_backup

There's bad news then worse news WRT rgy_backup.

First the bad news:

It was hoped that when rgy_backup was run on each of the clients - i.e. any machine that is not designated as a backup registry server - it would contact the primary registry server and ask "Who's the backup registry server?" then check to verify that the client was proper configured. If not, that it would update the client's notion of who is the designated backup registry server. Turns out this is not the case! So we would have an issue of how do we properly configure all the clients.

Now the worse news (AKA Why that CC Doctor warning about running Clearcase on a machine that uses DCHP is important):

When I tested rgy_switchover I was surprised that it was unable to switch over any Windows desktop! Here's the output:

    Wizard ccase-sj1-3:rgy_switchover ccase-sj1-4 ccase-sj1-3
    Registry switchover started at 20-Sep-05.16:56:33
    ccase-sj1-3: OK
    ccase-sj1-4: OK
    rgy_switchover: Error: Switchover for client LTSJCA-ADEFARIA failed
    rgy_switchover: Warning: LTSJCA-ADEFARIA: Unable to reconfigure - rgy_switchover: Warning: could not find host, please check hostname
    rgy_switchover: Error: Unknown host 'LTSJCA-ADEFARIA': Host not found
    rgy_switchover: Error: Switchover for client LTSJCA-ADEFARIA failed
    LTSJCA-ADEFARIA: FAILED
    rgy_switchover: Error: Switchover for client PCSJCA-SHIVJHA failed
    rgy_switchover: Warning: PCSJCA-SHIVJHA: Unable to reconfigure - rgy_switchover: Warning: could not find host, please check hostname
    rgy_switchover: Error: Unknown host 'PCSJCA-SHIVJHA': Host not found
    rgy_switchover: Error: Switchover for client PCSJCA-SHIVJHA failed
    PCSJCA-SHIVJHA: FAILED
    rgy_switchover: Error: Switchover for client lbsjca-nnalluri failed
    rgy_switchover: Warning: lbsjca-nnalluri: Unable to reconfigure - rgy_switchover: Warning: could not find host, please check hostname
    rgy_switchover: Error: Unknown host 'lbsjca-nnalluri': Host not found
    rgy_switchover: Error: Switchover for client lbsjca-nnalluri failed
    lbsjca-nnalluri: FAILED
    Registry switchover finished at 20-Sep-05.16:56:34
    

I suspect that the problem is that the Windows machine name does not resolve to an IP address:

    Local:ping ltsjca-adefaria 64 2
    PING LTSJCA-ADEFARIA.corp.ad.broadcom.com (10.16.65.94): 64 data bytes
    72 bytes from 10.16.65.94: icmp_seq=0 ttl=64 time=2 ms
    72 bytes from 10.16.65.94: icmp_seq=1 ttl=64 time=0 ms

    ----LTSJCA-ADEFARIA.corp.ad.broadcom.com PING Statistics----
    2 packets transmitted, 2 packets received, 0.0% packet loss
    round-trip (ms)  min/avg/max/med = 0/1/2/1
    

However:

    Local:nslookup 10.16.65.94
    Server:  dns-sj1-1b.sj.broadcom.com
    Address:  10.16.64.11

    Name:    dhcpe1-sj1-094.sj.broadcom.com
    Address:  10.16.65.94