Patch has failed to fix BEDB data(schema). Rolling back patch process.

Article:TECH212637  |  Created: 2013-11-20  |  Updated: 2014-02-20  |  Article URL http://www.symantec.com/docs/TECH212637
Article Type
Technical Solution

Product(s)

Issue



Backup Exec service pack or hotfix fails to install with an error Patch has failed to fix BEDB data schema.


Error



V-225-1000: Patch has failed to fix BEDB data(schema). Rolling back patch process.
Connected to SQL Server SERVERNAME\BKUPEXEC.
V-225-205: ERROR -1: Login failed for user ''. The user is not associated with a trusted SQL Server connection. ***To search for information about this error, click here
CREATE PROCEDURE [dbo].[ReportDailyDedupJobs] ( @numhours_before int = -1 ) AS SET NOCOUNT ON DECLAR
ERROR: -1 - Failed to execute dbupgradebuildtobuild.sql.
dbupgradebuildtobuild.sql changes did not complete successfully. Database schema may have been modified by this patch.
V-225-1000: Patch has failed to fix BEDB data(schema). Rolling back patch process. ***To search for information about this error, click here


-------------------------------------------------

V-225-1000: Patch has failed to fix BEDB data(schema). Rolling back patch process.
Connected to SQL Server SERVERNAME\BKUPEXEC.
V-225-205: ERROR -1: The OLE DB provider "SQLNCLI" for linked server "BESERVER_DB" does not contain the table ""BEDB"."dbo"."vwGetJobHistoryResourceContainerMapping"". The table either does not exist or the current user does not have permissions on that table.
CREATE PROCEDURE [dbo].[ReportFailedJobs] ( @protected_srv_names nvarchar(4000) = '', @numdays_befor
ERROR: -1 - Failed to execute dbupgradebuildtobuild.sql.
dbupgradebuildtobuild.sql changes did not complete successfully. Database schema may have been modified by this patch.
V-225-1000: Patch has failed to fix BEDB data(schema). Rolling back patch process.

-------------------------------------------------

 


Environment



Backup Exec 2012


Cause



Backup Exec Media Server was renamed after Backup Exec was installed and the configuration for the new server name was NOT updated. 

Backup Exec Hotfix or Service Pack Scripts not executed correctly.

 


Solution



 

Symantec Corporation has acknowledged that the above-mentioned issue is present in the current version(s) of the product(s) mentioned in this article. Symantec Corporation is committed to product quality and satisfied customers.

 

This issue is currently under investigation by Symantec Corporation. Pending the outcome of the investigation, this issue may be resolved by way of a patch or hotfix in current or future revisions of the software. However, this particular issue is not currently scheduled for any release. If you feel this issue has a direct business impact for you and your continued use of the product, please contact your Symantec Sales representative or the Symantec Sales group to discuss these concerns. For information on how to contact Symantec Sales, please see http://www.Symantec.com Please be sure to refer back to this document periodically as any changes to the status of the issue will be reflected here.


NOTE: Customers experiencing this issue are encouraged to contact Symantec Technical Support as data is still being collected to assist in resolving this issue.

 

WORKAROUND:

Use the Backup Exec Utility (BEUTILITY) to update the Backup Exec media server configuration information.
How to update Backup Exec media server configuration information, including server name and domain name changes. (SeeTECH38988)
 

Reboot Backup Exec Server

Retry the the Service Pack or hotfix installation.

  

If the previous name of the media server is not known or to check if the media server has been renamed, use the SQL queries below to locate the old server name.

To locate the old server name, run the following SQL queries from SQL Management Studio:

select srvname from master.dbo.sysservers where srvid = 0
select @@servername

 

To run the queries via command line OSQL on the media server, open a elevated command prompt and execute the following commands:

osql -E -S localhost\BKUPEXEC -dbedb -Q"select srvname from master.dbo.sysservers where srvid = 0"
osql -E -S localhost\BKUPEXEC -dbedb -Q"select @@servername"

In most cases, the query results will return different server names.

 

 

NOTE: If Backup Exec UTILITY (BEUTILITY) fails to update the server name the follwing SQL Query can be executed:

    

sp_dropserver '<oldservername\instance>'
go
sp_addserver '<newservername\instance>', local
go
 
The following is an example output of running these commands (Figure 1):
 
sp_dropserver 'OLDSERVERNAME\BKUPEXEC'
go
sp_addserver 'NEWSERVERNAME\BKUPEXEC', local
go
 
 
Figure 1
 
 
Reboot the Backup Exec server if any change is made.
 
 
------------------------------------------------------------------------------------------
NOTE: If the installation log reports the error:
 
"The OLE DB provider "SQLNCLI" for linked server "BESERVER_DB" does not contain the table ""BEDB"."dbo"."vwGetJobHistoryResourceContainerMapping"". The table either does not exist or the current user does not have permissions on that table" 
 
Open a command prompt to the Backup Exec installation folder (Default:  C:\Program Files\Symantec\Backup Exec\) and run BEMIG.EXE
 
Retry the Service Pack or Hotfix installation.
 
 
NOTE: After running BEMIG and the Service Pack or Hotfix installation fails please see Technote (TECH215215) in the Related Documents.
 
 
 
 

Supplemental Materials

SourceUMI
ValueV-225-1000
Description

V-225-1000: Patch has failed to fix BEDB data(schema). Rolling back patch process.


SourceETrack
Value3328659
Description

Patch has failed to fix BEDB data. Continuing with patch process


SourceETrack
Value3398592
Description

BE 2012 SP3 fails to install The OLE DB provider "SQLNCLI" for linked server "BESERVER_DB" does not contain the table ""BEDB"."dbo"."vwGetJobHistoryResourceContainerMapping"".


SourceETrack
Value3415725
Description

Error during install of Service Pack 3 on Backup Exec 2012: Patch has failed to fix BEDB data(schema). Rolling back patch process.




Article URL http://www.symantec.com/docs/TECH212637


Terms of use for this information are found in Legal Notices