Copying 10.0 projects from prod server to test server with ALM 11.52

  • Questions
  • Copying 10.0 projects from prod server to test server with ALM 11.52
Question ID: 105610

We are upgrading from QC 10 to ALM 11.52.
We have installed ALM 11.52 on test servers (both application and DB), and have been able to create new projects that look OK. We would like to copy existing production projects to the test server, but we are running into problems.
This is what we have done so far:
Copy the repository file for a production project onto the test APP server
Copy the project schema for that production project onto the test DB server
Added new empty project to the test ALM 11.52 installation
Made a copy of the new empty project DBID file
Rename the DBID file in the repository folder of the copied prod project
Copied the DBID file from the new empty project into the copied prod project repository folder
Edited the copied DBID file as follows:
Change the project name to the copied prod project name
Change the schema name (DB name) to the copied prod schema name
Change the physical directory to the copied prod repository folder name
Changed the last 3 digits of the project UID to make it unique
Changed "pr smart repository enabled" from Y to N
Copy the modified DBID file to my desktop, and in SA attempt to restore the project using the modified DBID from my desktop.

I get "failed to restore project", no other explanation or logs.

Is there anything in my steps above that that I'm not doing right, and/or can anyone give me any other steps to help resolve this?


Marked as spam
Posted by (Questions: 4, Answers: 5)
Asked on September 30, 2014 7:12 pm
Answers (3)
Private answer

I checked the QC SA logs, this problem is that I'm getting an ''invalid userid/password'' message when it tries to log on to the DB schema. I tried running the restore from the ALM server but get the same results.
The DBID file that I am using to perform the restore is a copy of one created when I created a new empty project. I changed the project_name, db_name, and physical_directory to match the names and location of the repository folder and DB schema copied over from the production system.
Frankly I am baffled by why I am getting an ''invalid userid/password'' message.

Marked as spam
Posted by (Questions: 4, Answers: 5)
Answered on October 1, 2014 5:58 pm
Private answer

When you restore the project DB backup to the SQL DB server instance, it is recommended to drop the td user that the back up is currently attached to and re-attach the new td user from the current DB instance (this is in case the user or password is different in the system it is coming from).

Run the two SQL queries within this green highlighted answer in this post (they are exec statements to drop and re-add the td user):

Hope this helps.

Marked as spam
Posted by (Questions: 0, Answers: 771)
Answered on October 2, 2014 1:04 pm
Private answer

You can find more information in the Site Administration log. In ALM in the Site Admin UI go to the Servers tab and click on your ALM server. This will display the location of the SA log and Client logs (created on the ALM server). Go to the specified location for the SA log and review the most recent log file. It is formatted as HTML so will open in a browser.

I always run project restores logged in to the ALM server itself to ensure access to the physical repository directory. Is the physical repository directory path specified in the dbid file accessible directly from your workstation? If you are running the restore from there, then that path must be accessible from the workstation.

What are you using for database management? I use MS SQL. When I transfer a project database from one db server to another, I have to run a query against that database to ''fix'' the ALM/QC SQL user ''td''. That could be another problem.

Marked as spam
Posted by (Questions: 1, Answers: 101)
Answered on September 30, 2014 8:45 pm