Unable to upgrade a project due to extra tables in the projects database
« Back
Tags:
Question ID: 108765
▲
1
▼
♥ 0

We just recently upgraded our ALM, and when run a verify on one of the projects we are upgrading, we are receiving an error indicating that there are errors found that can't be fixed using the repair process. We were then pointed to the qcverify report, which indicated that there are extra tables in the project database that are keeping the project from passing the verify process. We need to have these extra tables in the project database, because our UFT scripts store the test results in these tables, which are in turn used for reporting purposes. If we run the same UFT test against a project that is missing the extra tables, we receive the following error message.

Run Error:

[Microsoft][SQL Server Native Client 11.0][SQL Server]Invalid object name ‘td.AutoResultsLog’.
Function file: S:\\QTP_Main_Dir\\Function_Libraries\\SqlReporting.qfl
Line (139): " Connection.Execute(SqlStr)".

How can we upgrade our project and keep the additional tables? I appreciate any information you can provide.

Marked as spam
Posted by (Questions: 239, Answers: 31)
Asked on December 14, 2018 8:55 pm
52 views
Answers (2)
▲
1
▼
✔
Private answer

@Coleslaw Or you could just define an exception file. Check your documentation.

Marked as spam
Posted by (Questions: 0, Answers: 8)
Answered on January 15, 2019 3:22 am
▲
1
▼
✔
Private answer

Hello. I have run across a situtation such as this in the past, and I used the following steps to get the extra tables restored back into the project database after it was upgraded and restored in ALM. Be sure to have a backup copy of the project repository and database, in case any unforeseen issue occurs.

- Create a Temp Database in SQL Server
- Select the project database, right-click and select ''Tasks'' then select ''Export Data''
- Click 'Next'
- 'Data Source' field - Select ''SQL Server Native Client 11.0'' from the drop-down list
- 'Server Name' field - Enter the name of the database server
- Ensure the project database is displayed in the 'Database' field
- Click 'Next'
- 'Destination' field - Select ''SQL Server Native Client 11.0'' from the drop-down list
- 'Server Name' field - Enter the name of the database server
- 'Database' field - Select the temp db previously created from the drop down list
- Click 'Next'
- Leave the 'Copy data from one or more tables or views' radio button selected
- Click 'Next'
- Select the extra columns
- Click 'Next'
- Leave the 'Run immediately' checkbox selected
- Click 'Next'
- Click 'Finish'
- Click 'Close'
- Refresh the databases, and make sure the extra tables were added to the Temp table
- Delete the extra tables from the affected project database
- Restore the affected project into ALM and test to ensure everything functions correctly
- Ensure you have an extra backup of the affected project database
- Access Site Admin in ALM and deactivate the affected project
- REMOVE the affected project from the projects list in ALM
- Perform the data transfer from the Temp database back to the affected project database
- Select the affected project database, right-click and select ''Tasks'' then select ''Import Data''
- Click 'Next'
- 'Data Source' field - Select ''SQL Server Native Client 11.0'' from the drop-down list
- 'Server Name' field - Enter the name of the database server
- 'Database' field - Select the temp db previously created from the drop down list
- Click 'Next'
- 'Destination' field - Select ''SQL Server Native Client 11.0'' from the drop-down list
- 'Server Name' field - Enter the name of the database server
- Ensure that the affected project database is displayed in the 'Database' field
- Click 'Next'
- Leave the 'Copy data from one or more tables or views' radio button selected
- Click 'Next'
- Select the extra columns you want to add back to the affected project
- Click 'Next'
- Leave the 'Run immediately' checkbox selected
- Click 'Next'
- Click 'Finish'
- Click 'Close'
- Refresh the database and check to make sure the extra tables have been added back to the affected database
- Access Site Admin, restore and re-activate the affected project
- Expand the project in Site Admin and verify that the additional tables are displayed
- Access the desktop client, and make sure everything still looks and functions correctly
- Retest the automation tests to see if the results are posted into the extra tables

Marked as spam
Posted by (Questions: 2, Answers: 300)
Answered on December 14, 2018 8:57 pm
▲
0
▼
We have restored the deleted tables back into the project database using the steps you provided. We ran a couple of our tests today, and the automation code is writing the execution results to the extra tables as expected. Thank you!
( at December 14, 2018 9:14 pm)
« Back
EyeOnTesting

Welcome back to "EyeOnTesting" brought to you by Orasi Software, Inc.

Got it!
X
Scroll to Top