Data Protector Practitioners Forum
Showing results for 
Search instead for 
Do you mean 

Data Protector Restore Error SQL 6.21 Integration 'SQLSTATE [42000] CODE: (3234)

SOLVED
Go to Solution
Super Advisor

Data Protector Restore Error SQL 6.21 Integration 'SQLSTATE [42000] CODE: (3234)

Hi all, I have Data Protector 6.21 on Windows Server 2008 R2, I have configured integration with SQL Server.

 

DPWIN_00572  Core component

DPWIN_00572 Core integration

DPWIN_00575 Cell Manager Component

DPWIN_00577 Disk Agent

DPWIN_00578  Media Agent

DPWIN_00576 User Interface

DPWIN_00563 Documentation

DPWIN_00579 Virtual Enviroment



I have several integrations with SQL Server 2005 and 2008, before installing the version 6.21 I've done several restores of SQL Server and it's all right.

The backup session report no error.

When I try to restore a DB with a new name on the same server I get this error in the log of the session restore:



Error message: 'SQLSTATE [42000] CODE: (3234) MESSAGE: [Microsoft] [ODBC SQL Server Driver] [SQL Server] The logical file' xxxx 'is not part of database' xxxx '. Use RESTORE FILELISTONLY to list the logical file names


[Major] From: OB2BAR_Main @ xxxxxxxxx "(DEFAULT)" Time: 06/21/2012 13:19:26
Aborting connection to RSM. Abort code 8500.

Thanks for answering!

2 REPLIES
Valued Contributor

Re: Data Protector Restore Error SQL 6.21 Integration 'SQLSTATE [42000] CODE: (3234)

Hi,

 

Seems you have changed the logical file name in Advanced tab of the database restore properties. Only the target database name and the destination file name can be changed and the logical file name should remain the same; because the logical file name is part of database configuration and it should not be changed.

Regards,
Prakasam S
Highlighted
Super Advisor

Re: Data Protector Restore Error SQL 6.21 Integration 'SQLSTATE [42000] CODE: (3234)

Thanks Prakasam, you were absolutely right, I did a restore only changing the DB name and location of the files, but without changing the logical name and everything worked correctly.

Thank you very much!