Hi Sreeji,
You can also use an exception file to instruct the Verify utility to ignore the extra table. The procedure would be the following:
1. Copy the SchemaExceptions.xml file from the ALM installation directory. By default, the file is located in <ALM installation path>\data\sa\DomsInfo\MaintenanceData
2. In the ALM repository directory, under the customerData folder, create the sub-folders DomsInfo\MaintenanceData, if they do not already exist
3. Save a copy of SchemaExceptions.xml under <ALM repository path>\customerData\DomsInfo\MaintenanceData
4. Edit the file in the ALM repository directory, and define the exceptions. For example:
<ColumnMissing>
<object pattern="BUG.BG_LEGACY_ID" type="extra"/>
</ColumnMissing>|
5. Run the Server Deployment Wizard:
On Windows systems, choose one of the following:
- Start -> HP ALM Platform -> Server Deployment Wizard
- <ALM installation path>\bin\run_server_deploy_tool.bat
On Unix systems: <installation path>/bin/run_server_deploy_tool.sh
6. To set an exception file for a single project:
a. In ALM Site Administration, click the Site Projects tab
b. In the Projects list, select a project. In the right pane, select the Project Details tab
c. Under Project Database, click Exception File. The Edit Exception File dialog box opens.
d. Type the file location. The file is located under <ALM deployment path>\repository\sa\DomsInfo\MaintenanceData folder.
Hope this would help!
Thanks,
Hristo