Showing posts with label Technical. Show all posts
Showing posts with label Technical. Show all posts

Thursday, December 11, 2008

The procedure of the deliver operation

The procedure of the deliver operation

 

The deliver operation proceeds in the following order:

 

  1. When you start the deliver operation, your development stream is placed in the deliver-in-progress state.  
  2. Dependencies between versions in the change sets of the activities that are as yet undelivered in the target stream are checked.  
  3. Each directory in your development stream is evaluated sequentially. Versions are checked out and changes are merged to the target stream when needed. If a reserved directory checkout is encountered in the target stream, the deliver operation stops. Any successful directory merges are retained.  
  4. An attempt is made to check out each element that requires a merge. If an element that cannot be checked out is encountered (for example because another team member’s deliver operation has already checked out the element), the element is skipped and more attempts are made to check out the remaining elements.  
  5. If an element cannot be checked out, the deliver operation does not proceed to the following step. In this case, you have two options:  
    • Wait until the other developer completes or cancels the deliver operation, and then restart your deliver operation. However, with a deliver operation in progress, any new versions you create in your development stream are not delivered until the next deliver operation.
    • Undo your deliver operation and continue working on your activities. 
  6. After all elements that can be checked out are successfully checked out, each element is merged. Diff Merge starts and requests your input when merge conflicts are encountered.  
  7. When all merges are finished, you are prompted to build and test the work in your integration view.  
  8. The deliver operation stays in the deliver-in-progress state until you formally complete the operation (issue the complete command). To complete the deliver, the following is done:  
    • The merge results in the target stream are checked in.
    • The state of the stream is changed to Complete.

 

Delete activities when ClearQuest Record is linked with a UCM activity

Delete activities when ClearQuest Record is linked with a UCM activity
 
You can enable ClearQuest and ClearCase integration to manage the developement process. ClearQuest is used as a defect tracking tool and ClearCase is used as source control repository. If a Rational ClearQuest record is linked with a UCM activity and you want to delete the activity, you should do:
  • Remove the link between UCM activity and ClearQuest records (In ClearCase side)
  • Delete ClearQuest records(in ClearQuest side)
Before you remove the link between UCM activity and ClearQuest records, below requisiton must be fulfilled:
  • no changeset in that activity. If yes, move the change sets to other activity
  • the operator to do this must be the owner of the ClearQuest record. Not the submitter but the owner
Then you can use below command to remove the link
cleartool rmactivity clearquest_record_id
 
executing above command does not delete the ClearQuest record. So you must login the ClearQuest and do the Delete action then. The access control of the Deletion is defined in the ClearQuest schema. You should ask the ClearQuest admin to confirm if you have the right to delete the record.
 
 

How file/directory checkouts are canceled

 
How file/directory checkouts are canceled
How file checkouts are canceled
  • When you cancel the checkout of a file element, the request is handled as follows:
  • You have prompted to rename the fie in your view to filename.keep
  • The VOB is notified that you no longer have the version checked out in your view
  • In a snapshot view, the version that was in your view when you performed the checkout operation is copied from the VOB
  • In a dynamic view, the version-selection rules in the config spec are used to select a version.
 
How directory checkouts are canceled
  • When you cancel a directory checkout, the VOB is notified that you no longer have the version of the directory checked out to your view. But you are not prompted to rename a canceled directory checkout to directory-name.keep.
  • If you cancel a directory checkout after any changes you made to rename,move, create link will lost. Any new elements you created (with mkelem or mkdir) become orphaned. But pls note that if you just only modify the content (add/remove/update lines) in the file and check in the file, the file version and its content is still there although you undo check out against that folder.
 
Orphaned elements are moved to the VOB lost+found directory under names of this form:
element-anme.UUID
 
In a snapshot view, view-private objects are not removed nor is the update operation for the directory in the view started. To return the directory in your view to its state before you checked it out, you must start the Update Tool.
Action Result after undo checkout its parent directory Input into lost+found
rename element stay in the view but the Kind is view-private No
create dir and add to source control stay in the view but the Kind is view-private Yes
create element and add to source control stay in the view but the Kind is view-private Yes
create link and add to source control stay in the view but the Kind is view-private No
delete element can not show again until you update the view No
 
 
In a dynamic view, view-private objects are not removed, but the view does revert to its previous state.
Action Result after undo checkout its parent directory Input into lost+found
rename element recover the name to its previous one No
create dir and add to source control dispear Yes
create element and add to source control dispear Yes
create link and add to source control dispare No
delete element show again No
 
To move the elements from the lost+found directory
  • To move an element from the lost+found directory to another dirctory within the VOB, use the cleartool mv command.
  • To move an element from the lost+found directory to another VOB, use the relocate command.
 
To delete an element in the lost+found directory
  • To delete an element in the lost+found directory permanently, use rmelem command.
 

Checking out directory

Checking out directory
Directories and files under Rational ClearCase source control. Having versions of directories can be helpful if, for example,you rename a source file used in a particular release and then modify your makefile to reflect this change. If you need to rebuild a previous release, you can set up your view to sleect the version of the directory that contains the file under its previous name.
 
On Unix system
To add a file or subdirectory to Rational ClearCase control, you must first check out the parent directory. It is common mistake that, after checking out a parent directry and adding elements to it, users forget to check in the directory. If you check out a directory, you can see its modified contents form your view, but other users can not see the modifications until you check in it.
 
On Windows system
You rarely need to check out a directory explicitly. The parent directory of a file is checked out and checked in when you add the file to source control. in a directory under version control, a new version of the directory is created when you add or rename a file element under source control. Before you modify the contend in the view, if you check out the parent directory explicitly, you can see its modified contents from your view, but other users can not see the modifications until you check in it.
 
Modifications here means the operations of mkdir,mkelement,rename,ln and exclude the operations that only update the contents in the source files
 

Tuesday, December 9, 2008

Reserved and Unreserved Checkouts

Reserved and Unreserved Checkouts
In some version control systems, only one user at a time can reserve the right to create a new version on a branch or in a stream. In other systems, many users can compete to create the same new version.Both models are supported by allowing tow kinds of checkouts: reserved and unreserved.
 
The view with a reserved checkout has the exclusive right to check in a new version for a branch or stream. Many views can have unreserved checkouts. A unreserved checkout does not guarantee the right to create the successor version. If several views have unreserved checkouts, the first view to check in the element on a branch or stream creates the successor; developers who arew working in other views must merge the check-in changes into their own work before they can check in.
 
For example, one file in view A is checked out with Reserved option. The file is checked out in view B with Unreserved option too ( only can be checked out with Unreserved option since it has been Reserved by view A). That means the file in view B can not be checked in unless the files in View A has been checked-in.
 
In above example, if the file is checked out in View A and B with Unreserved option, it can be checked in at any time without considering the check-in sequence. The first check-in makes the successor version and later one will create antoher version after merge operation.
 
The status of a checkout can be changed from reserved to unreserved or from unreserved to reserved. Users can not change an unresearved checkout to a reserved checkout if the version is checked out as reserved in another view. Here are the 2 ways to do this
    • Using cleartool command

    Cleartool reserve element-name

    Cleartool unreserved element-name

    • Using the GUI

    In Rational ClearCase Explorer, select the checked-out version and click either Tools->Reserve or Tools->Unreserve

    In Windows Explorer, right-click a checked-out version. Then click ClearCase->Properties of Version.

Monday, December 8, 2008

Text Mode in ClearCase

Text Mode in ClearCase
 
Text modes in Rational ClearCase views are necessary because lines in text files are terminated differently on different platform types. The text mode of a view determines how lines in text files under Rational ClearCase control are processed, independent of the platform that the view storage, the VOB server, or the client runs on.
 
Linux and the UNIX system and Windows observe different conventions for terminating lines in text files. Typically, Linux and the UNIX system terminate lines with a single <LF> character and Windows systems terminate lines with a two-character sequence <CR><LF>.
 
To better support parallel development in mixed operationg system environments,a text mode setting for views in provided that controls how line terminators are handled when text files are presented to applications.This setting applies only to file elements whose element type is text_file or a subtype of type text_file. You determine a view text mode when you create the view. You can not change the text mode fo a view after the view has been created.
 
Text Modes
transparent (formerly unix) No line terminator processing is done.
insert_cr (formerly msdos) A <CR> character is inserted before every <LF> character.
strip_cr The <CR> character is stripped from every <CR><LF> sequence.
 
Sitewide property and Rational ClearCase user option for text mode on Windows computers
On windows computers, the sitewide property view_interop_text_mode in a Rational ClearCase registry determines the default text mode when you create a view with the GUI. If view_interop_text_mode is set to True, insert_cr text mode is the default. If view_interop_text_mode is set to False, transparent text mode is the default. The cleartool lssite -inquire command lists the current value.
 
On windows computers, in the View Options page in the ClearCase User Options window, you can specify a preference that determines the default text mode when you create a view with the GUI. if you set interop text mode, insert_cr text mode is the default. If you clear interop text mode, transparent text mode is the default. The preference can override the default for the site-wide property view_interop_text_mode.
 
In a snapshot view created in either insert_cr or strip_cr text mode, the <CR> characters are added or removed whenever the view is updated. In a dynamic view, the <CR> characters are added or removed as you open and read files. For both snapshot views and dynamic views, the <CR> manipulation is reversed (<CR> characters being added or removed as appropriate) during the checkin process.
 
If most users are developing software on UNIX systems:
  • UNIX clients should use views created in transparent text mode.
  • Windows clients should use views created in insert_cr text mode.
If most users are developing software on Windows systems:
  • Windows clients should use views created in transparent text mode.
  • UNIX clients should use views created in strip_cr text mode.

Wednesday, November 12, 2008

Increase Record ID Limit in ClearQuest 7.0 or later

Record ID Limit

From ClearQuest 7.0,  the record ID(DBID) limit from 16 million records to 100 million stateful and 2 billion stateless records.

 

Ensure to upgrade ClearQuest synchronization servers to 7.0 or above before you increase the record limit. Once you increate the record limit, the format of the oplog and the export packages will change a bit. Synchronization server from earlier versions can not work with packets with the changed format.

 

 

To check whether the user db has enabled the high record ID limit, you can use installutil getrecordlimits  on each user database or –all for all databases which are associated with a schema repository

 

How to increase the record ID limit

For nonreplicated databases, the installutil sethighrecordlimit command is run on each user database that needs the higher record limit. The command can also run on all user databases associated with a schema repository by using the –all option

 

For replicated databases, the installutil sethighrecordlimit command is used with the –for replication option. This option can be used only at the working master site and the changes will sync to other sites. To increase the record ID limit in an environment with replicated databases:

  1. Stop sync jobs
  2. Ship all outstanding synchronization packets
  3. Import all outstanding synchronization packets
  4. At the working master site, run the installutil sethighrecordlimit command with the –for replication options
  5. Start sync jobs

 

For working master sites that also have non-replicated user databases, run the installutil sethighrecordlimit command on those databases individually or use the –all option. The –all option does not apply to replicated databases or affect them in any way.

 

Notice

All new schema repositories and its associated databases created in version 7.0 or later will be set to the higher record ID limit by default.

 

Databases created with version 7.0 and later in a clan use the record limit specified by the clan, which depends on whether the clan has been enabled for high record limits or not.

Tuesday, November 11, 2008

UTC Time in ClearQuest 7.0.1

UTC Time in ClearQuest 7.0.1

 

Before CQ 7.0.1, time stamp are stored using local time of  the database server. With CQ 7.0.1, time stamp can be stored using Coordinated Universal Time (UTC) so that times always can be compared accurately across time zones.

 

New user databases created with CQ 7.0.1 on feature lever 6 always use UTC to store history dates.

 

To concert history time stamps to UTC for existing databases either at feature lever 5 or 6, you must use the installutil –please setutchistorytimestamps. If you have a MultiSite environment, you must also run the timechange.pl script at each replica to update the data to UTC format

 

2 API in ResultSet object methods

  • GetConvertToLocalTime
  • SetConvertToLocalTime

 

For detail API usage, pls reference the online help

Feature Lever 6 in ClearQuest 7.0.1

Procedures to upgrade to feature level 6 from 5 in ClearQuest multisite

  • Upgrade all multisite synchronization servers to version 7.0.1
  • Upgrade all Rational ClearQuest clients to version 7.0.1
  • Upgrade schema repositories and user database and user databases to feature level 6. Upgrading the schema repositories and user database can be done in phases

 

Notes: If you have updated the Rational Shipping Server to version 7.0, and the Shpping Server resides on a computer with other Rational Software on the same computer, you do not need to upgrade it to 7.0.1 Version 7.0 of this component is compatible with other Rational ClearQuest components in 7.0.1

 

 

 

The rules about which user databases can receive packets from other user databases are as follows:

  • Schema repositories on feature level 6 can work with associated user databases on feature level 5 and 6
  • Sites with schema repositories and user databases on feature level 5 can only accept packets from other sites with the same feature levels
  • Sites with schema repositories on feature level 6 and user databases on feature 5 can accept packets from other sites with the same feature levels and also from sites with schema repositories and user databases on feature level 5
  • Sites with schema repositories and user databases on feature level 6 can accept packets from all sites with schema repositories and user databases on feature level 5 or feature level 6

 

In summary, feature level are backward compatible with lower levels but not forward compatible with higher levels.

 

 

Verify the feature level and metaschema version

  1. c:\> pdsql
  2. >select feature_level,metaschema_version from master_global;
  3. >quit;

 

 

Steps to upgrade to feature level 6 from 5

  1. Backup all schema repositories and user dbs
  2. Stop synchronization scripts
  3. Import all pending packages
  4. Start the Maintenance Tool
  5. From the Existing Connections list, select the connection to the schema repository that you want to upgrade
  6. On the Maintenance Tool menu, click Schema Repository > Upgrade > Selected Connection
  7. At the prompt to upgrade user databases, click Yes to continue
  8. Log in with Super User privileges
  9. Select the feature lever and enter the properties of the schema repository to which you are upgrading. To perform an in-place upgrade, specify the properties of the Source Schema Repository in the New Schema Repository area. Then click Next
  10. At the prompt to upgrade the schema repository, click Yes to continue
  11. Enter the properties for the first user database to which you are upgrading and click Next. Repeat until you have associated all the user databases. Click Finish.
  12. Verify the upgrade result
  13. Start synchronization scripts
 

Features in ClearQuest 7.0

Features in ClearQuest 7.0

 

  • The multiutil renamesite command, which allows you to change the database set name of master sites and replica sites in a MultiSite environment (useful)

 

  • The ability for MultiSite to synchronize null value fields

 

  • Support for LDAP using SSL

 

  • The option to increase the record ID limit

 

  • Support for new languages and other features for new code pages

 

  • Translation of packages and schemas into Japanese and Simplified Chinese

 

  • Support for mixed character set deployments and the ability to use non-ASCII data on Linux and the UNIX system

 

 

Features in ClearQuest 7.0.1

 

  • Enhancements to Rational ClearQuest clients

 

  • Enhancements to Rational ClearQuest Test Manager

 

  • Support for DB2 version 9.1 database management system

 

  • The ability to run case-insensitive queries for user databases running Oracle version 10

 

  • Multiple request managers for Rational ClearQuest Web

 

  • New or updated 7.0.1 packages that include fixes and performance enhancements

 

  • The ability to store history dates in Rational ClearQuest records in a UTC

 

  • Workspace security permissions for folders (requires feature level 6)

 

  • Product documentation available online in the Rational ClearQuest Information Center

 

Pls note that UTC and workspace security feature are only available in feature level 6

 

Tuesday, July 8, 2008

Solutions for the SQL Server Driver Error in ClearQuest

Here is some cases happened these days caused by the SQL Server Driver for ODBC

1. When import CQ profile using IBM Rational ClearQuest Maintenance Tool, user encountered error message as below,
Unable to login to the database using the following connection information:Driver= {SQL Server};UID=xxx;DataBase=xxx;PWD=xxx;SERVER=XXXVerify that the information used matches the way the database was set up
The error message was: SQLDriverConnect:RETCODE=-1,State=08001,Native Error=52
[Microsoft][ODBC SQL Server Driver][dbnmpntw]ConnectionOpen(CreateFile())
[Microsoft][ODBC SQL Server Driver][dbnmpntw]ConnectionOpen(CreateFile())
[Microsoft][ODBC Driver Manager]Driver's SQLSetConnectAttr failed

2. When users login CQ using CQ native client, below error massage happens,
Unable to logon to the SQL_SERVER database xxx
The vendor error message was:
SQLDriverConnect: RETCODE=-1, State=IM003, Native Error=160
pecified driver could not be loaded due to system error 126 (SQL Server).

Here are the steps to diagnose the cause,
1. Open ODBC Data Source Administrator
2. Enter the Drivers tab to check the version of SQL Server
3. Check your CQ product version and get the supported SQL Server version in CQ release notes
4. In most cases, the version is not the correct one to match the CQ products
5. Login microsoft to download the right MDAC(Microsoft Data Accessing Components) version to install and correct the version.





Best Regards
Oliver Zheng
Tel: 86-756-3398810

Monday, June 30, 2008

ClearQuest API ListSelection method is not available from ClearQuest Web interface

ClearQuest API ListSelection method is not available from ClearQuest Web interface

Just as the subject, you can not use ListSelection in CQ web or you may encounter error.  Here is the IBM notes to explain this issue

http://www-1.ibm.com/support/docview.wss?uid=swg21304656

Wednesday, June 25, 2008

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.


Monday, May 12, 2008

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.

Friday, May 9, 2008

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

Tuesday, May 6, 2008

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
    6. 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



Wednesday, January 9, 2008

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.










Tuesday, December 11, 2007

How to get the db connection string with CQ admin user


How to get the db connection string with CQ admin user

We can get the dbo userid, pwd, physical database name via some database object description  API. Here is the perl sample,

# Perl begins
#!C:\Program Files\Rational\ClearQuest\cqperl.exe

use CQPerlExt;

# create user session
my $userSession=CQSession::Build();
     $userSession->UserLogon("userid","pwd","userdb_name","schema_repository_name");
my $dbObjDes=$userSession->GetSessionDatabase()
print $dbObjDes->GetDatabaseConnectString();

# End

After run above pl file agaist MSSQL server, you can get the output like:

DRIVER={SQL Server};UID=dboname;DATABASE=physical_dbs;PWD=pwdabc;SERVER=db_servername

Friday, November 30, 2007

Login CQ Testing DB with CQ web

Login CQ Testing DB with CQ web

Normally, when we login CQ using WEB client, only production dbs will be listed out and can not manual input  the database name as well(Desktop client can manual input).  Hence if you want to login testing db with web client, the flowing url should be used.

 http://hostname/cqweb/login?test=1
And then you can input the test db name in the Database fields.