How to solve unexpected characters in export package

How to solve unexpected characters in export package

In the clearquest, user can not input non-support characters in ClearQuest UI since the code page settings. But with a uncertain reason, we will meet sometimes error when export package and it says like

 
Fri Jun 20 15:46:02 2008 -- Job started
Multiutil: Found unexpected characters outside ASCII range.
Offending characters were found at:
line 2
column 0
byte 50

The packlet being exported was oplog serial number 116298 of database 'CSEDI', replica 'HKG' (UUID = 587CB952-6052-4D32-8D7E-3B70222438F3).

Here is the steps to fix the problem with MS-SQL backend db servers
1.  using below command to dump the binary file from ratal_oplog table
    pdsql -v  ss -s dbserver -u dbo_userid -p dbo_user_password -db dbname
    >dump_longbinary c:\temp\serical_116298.txt select packlet from ratl_oplog where serial_no=116298;
    >commit;
    >quit;
   You can access below URL for the pdsql usage. In this case, the dbname is physical database name for CSEDI project
   http://www-1.ibm.com/support/docview.wss?uid=swg21145079

2. open the dump file ,which was generated by step 1 and named serical_116298 for example, with notepad and save the file using ANSI format and do not update/change anything in the file.

3. check the exact size. This can be done using Windows Explorer by right-clicking on the file and choosing Properties.

4. Run pdsql again against the dbname in step 1 using below command
   pdsql -v ss -s dbserver -u dbo_userid -p dbo_user_password -db dbname
   >insert_file binary c:\temp serical_116298.txt update ratl_oplog set packlet=? Where serial_no=116298
   >update ratl_oplog set packlet_len=2088 where serial_no=116298
   >commit;
   >quit;
  pls note, a. there are no space between path(c:\temp) and filename(serical_116298.txt). b. do not replace the question mark after "packlet=". c. 2088 is the exact file size of serical_116298 after step 3 and it is 2088 bytes.

5. Run the export job/command against CSEDI project again and make sure the package can be exported and imported in its destination sites

Before doing step 4, you are strongly recommended to backup all your database in case of any unexpected failure.

沉痛悼念5.12汶川大地震遇难同胞

How to import defects attachments using Import Tool

How to Import Defects Attachments using Import Tool

Here are the steps to import defect attachments using import tool
A. Using export tool to export the defects you want to import.
B. Change the fields value in the exported file to match those in destination project userdb.
C. Using import tool to import defect record data first and pls be noted do not import at_field_history field and map the old_id to any field like old_id_record

D Import attachments and select old_id_record as field Name and select display_name as Source_Field_Label and add those attachments to the defects which have been imported in step C.

Apply ifix and fix package to ClearQuest

Apply ifix and fix package to ClearQuest

Use the following format to apply a product ifix or fix pack to an existing release area
1. Download the appropriate ifix or fix pack and store it on the host where the release area is located.
2. Open a command prompt on the host used for the release area.
3. Run the following msiexe command to apply the package from the command line directly to the release area
msiexec /a <complete path to the msi in the release area> /p <complete path to the msp file> <UI switch> /lv* <complete path to the log file>

For the UI swith, it should be one of followings,
    /qb: provides basic user interface
    /qn: provides no interface at all

For example
msiexec /a c:\release_area\Setup\1033_ClearQuest.msi /p c:\temp\1033_clearquest.msp /qb /lv* c:\temp\install.log

You can find a whole technote in below link,
http://www-1.ibm.com/support/docview.wss?&uid=swg21242322

New Features in IBM Rational ClearQuest 7.0

New Features in CQ 7.0

1. Platform-independent client
2. Enhancements to existing clients
3. Enhancements to Rational Web Platform
4. Rational ClearQuest Test Manager
5. Deployment tracking packages

This release includes a Deployment tracking feature, which enables you to use Rational CC and CQ to track software assets in your specific software testing environment throughout the deployment lifecycle. Highlights of deployment tracking,

. Rational CC deployment units that track which versioned artifacts in your VOB are being deployed

. Rational CQ deployment tracking records that implement a role-based approval process for your deployment

. Traceability between build artifacts and deployment records which provides audit trails for your artifacts that satisfy regulatory compliance requirement

                    Three new packages enable deployment tracking: 

                   . DeploymentTracking

                   . BuildTracking

                   . IBM Tivoli Provisioning Manager

          f. Enhancements to Record ID limitation

In previous release, the maximum number of database records IDs was approximately 16 million. For stateless records, the new limit is approximately 2 billion, for stateful records, it is approximately 100 million.

g.      SSL support for LDAP authentication
h.      Rational ClearQuest Web request manager recycling
i.      Rational ClearQuest Diagnostics utility
j.      Extended code page support

New Features in CQ 7.0.1

Briefing New Features in CQ 7.0.1

Below info are abstracted from IBM Rational ClearQuest 7.0.1  release notes.

        a. Support feature lever 5 and 6

Feature 6 enables several new features by default,

• Workspace folder permissions
• Storing history time stamps in UTC
• Increased number of record IDs for the user db

b.      Support workspace permissions

In previous version, all users can view public folders and all its queries. In the release 7.0.1, workspace folder permissions allow administrator to control which folders (only folder lever) users can see and modify.

c.      Enhancements to Rational CQ client and Rational ClearQuest client for Eclipse
d.      Enhancements to Rational CQ Test Manager
e.      Control of case-sensitivity for queries of multiline test fields on Oracle databases
f.      Storing history dates in Universal Coordinated Time
g.      Enhancements to Rational ClearQuest Web

h. Restricted mode enhancement. When enabled by an administrator, the restricted mode enhancement feature allows users working in restricted mode to modify record types

i. Support for multiple request managers

j. Global script cloning

Purge deleted user db in ClearQuest

In ClearQuest designer, admin user can delete one user database and undelete to use again. Sometimes, we do not want to see the deleted user db in CQ designer, for example, the user db is not used any more.Here is the steps to do

In Non-Multisite env

1. In ClearQuest designer, click Delete Databases manu under Database and delete the db you want.
   
2. Run below command
   Installutil purgedeleteduserdb dbsetname admin_user admin_pwd db_name
   
3. Remove the physical db

After the command in step b is executed, the deleted userdb can not be viewed in the ClearQuest designer any more.

In Multisite env
Suppose we have one family named Test in sites Q3 (master site) and ZL with clan name OL. Now we want to purge the user db in both of the sites. Here are the steps,

1. In the ZL site, change master ship of all entities from ZL to Q3 site with below command.
   Multiutil chmaster -cl ol -site ZL -family Test -u admin_user -p admin_pwd Q3 -all
   
2. Synchronize the changes from ZL to Q3 site and other sites if any
   
3. In the master site Q3, remove the Test replica in ZL with below command
   Multiutil rmreplica -cl ol -site Q3 -family Test - u admin_user -p admin_pwd ZL
   
4. Synchronize the changes from Q3 to ZL site and other sites if any
   
5. Delete the Test user db in ZL site with following command.(The step can not do in ClearQuest designer in ZL site since the manu is disabled)
   Installutil disconnectuserdb -dbset CQMS.OL.ZL admin_user admin_pwd Test
   
6. Purge deleted Test user db in ZL site with following command
   Installutil purgedeleteduserdb CQMS.OL.ZL admin_user admin_pwd
   
7. Synchronize the changes from ZL to Q3 site and other sites if any
   
8. Deactivate the Tester user db in master site Q3 with following command
   Multiutil deactivate -cl ol -site Q3 -family Test -u admin_user -p admin_pwd
   
9. Delete the Test user db in Q3 site in ClearQuest designer or below command
   Installutil disconnectuserdb -dbset CQMS.OL.Q3 admin_user admin_pwd Test
   
10. Purge the delted Test userdb in Q3 with below command
    Installutil purgedelteduserdb  CQMS.OL.Q3 admin_user admin_pwd Test
    
11. Remove the physical db

Somtimes, the step h and j will result error.  But it works well if delete the records related Test userdb from master_dbs, master_id_blocks, master_replicas directly in master db.