DB Restore problem

Hello all,

I've been reading this thread http://forums.microsoft.com/msdn/ShowPost.aspx?postid=1494867&siteid=1 because I've been having a similar problem.

I wanted to post a new thread to make sure that people have an opportunity to see it and, hopefully, give me some help.

I have a backup of my production database and want to restore it over my development database (using Enterprise Manager). When I first tried the restoration it worked but the application (Siebel) using the database wouldn't log in. Stupidly, instead of reading the log files for the application I panicked and restored the dev database with an old copy of the dev database. Unfortunately this backup was either not complete or had some other problem because that restore failed.

I then tried running the restore (again from Enterprise Manager) of the dev database with my production backup and began receiving the MOVE FILE error discussed in the abovementioned thread.

So, following the instructions in that thread, I attempted to run the RESTORE FILELISTONLY command from SQL Query analyzer and get this message:

"Could not locate entry in sysdatabases for database 'siebel_prod.' No entry found with that name. Make sure the name is entered correctly."

Can anyone help me with the above issue? This is extremely time critical and I need to get a resolution ASAP.

Thanks in advance.

|||You should not need to include the database name n the RESTORE FILELISTONLY syntax.|||

generally , with the Move option the very common mistake is , you change the logical file name also , ie

Step 1 -- Run the below statement to see the LOGICAL FIle name in the backup set

RESTORE FILELISTONLY FROM DISK = 'D:\yourbackupfile.bak'

RESTORE DATABASE GPx FROM DISK = 'D:\yourbackupfile.bak'

WITH MOVE 'Your_Source_Datbase_Logical_Data_Filename' TO 'D:\TargetDatabae.mdf',

MOVE Your_Source_Datbase_Logical_Log_Filename' TO 'D:\TargetDatabase_log.ldf'

Your_Source_Datbase_Logical_Data_Filename' -- THis should be the source database (not the target) logical filename which can get by RESTORE FILELISTONLY

Your_Source_Datbase_Logical_Log_Filename' -- THis should be the source database logical filename

when you restore a database with move option , your source and target database will have same logical name. This you need to change ALTER DATABASE statemetn after restoration

Madhu

|||

You wrote this:

"RESTORE DATABASE GPx FROM DISK = 'D:\yourbackupfile.bak'"

What is "GPx"?

I'm assuming it is the name of the database to be restored. Right?

|||

i just cut paste from my enviornment man... yes its database name

Madhu

DB Restore problem

Hello all,

I've been reading this thread http://forums.microsoft.com/msdn/ShowPost.aspx?postid=1494867&siteid=1 because I've been having a similar problem.

I wanted to post a new thread to make sure that people have an opportunity to see it and, hopefully, give me some help.

I have a backup of my production database and want to restore it over my development database (using Enterprise Manager). When I first tried the restoration it worked but the application (Siebel) using the database wouldn't log in. Stupidly, instead of reading the log files for the application I panicked and restored the dev database with an old copy of the dev database. Unfortunately this backup was either not complete or had some other problem because that restore failed.

I then tried running the restore (again from Enterprise Manager) of the dev database with my production backup and began receiving the MOVE FILE error discussed in the abovementioned thread.

So, following the instructions in that thread, I attempted to run the RESTORE FILELISTONLY command from SQL Query analyzer and get this message:

"Could not locate entry in sysdatabases for database 'siebel_prod.' No entry found with that name. Make sure the name is entered correctly."

Can anyone help me with the above issue? This is extremely time critical and I need to get a resolution ASAP.

Thanks in advance.

|||You should not need to include the database name n the RESTORE FILELISTONLY syntax.|||

generally , with the Move option the very common mistake is , you change the logical file name also , ie

Step 1 -- Run the below statement to see the LOGICAL FIle name in the backup set

RESTORE FILELISTONLY FROM DISK = 'D:\yourbackupfile.bak'

RESTORE DATABASE GPx FROM DISK = 'D:\yourbackupfile.bak'

WITH MOVE 'Your_Source_Datbase_Logical_Data_Filename' TO 'D:\TargetDatabae.mdf',

MOVE Your_Source_Datbase_Logical_Log_Filename' TO 'D:\TargetDatabase_log.ldf'

Your_Source_Datbase_Logical_Data_Filename' -- THis should be the source database (not the target) logical filename which can get by RESTORE FILELISTONLY

Your_Source_Datbase_Logical_Log_Filename' -- THis should be the source database logical filename

when you restore a database with move option , your source and target database will have same logical name. This you need to change ALTER DATABASE statemetn after restoration

Madhu

|||

You wrote this:

"RESTORE DATABASE GPx FROM DISK = 'D:\yourbackupfile.bak'"

What is "GPx"?

I'm assuming it is the name of the database to be restored. Right?

|||

i just cut paste from my enviornment man... yes its database name

Madhu

DB Restore problem

Hello all,

I've been reading this thread http://forums.microsoft.com/msdn/ShowPost.aspx?postid=1494867&siteid=1 because I've been having a similar problem.

I wanted to post a new thread to make sure that people have an opportunity to see it and, hopefully, give me some help.

I have a backup of my production database and want to restore it over my development database (using Enterprise Manager). When I first tried the restoration it worked but the application (Siebel) using the database wouldn't log in. Stupidly, instead of reading the log files for the application I panicked and restored the dev database with an old copy of the dev database. Unfortunately this backup was either not complete or had some other problem because that restore failed.

I then tried running the restore (again from Enterprise Manager) of the dev database with my production backup and began receiving the MOVE FILE error discussed in the abovementioned thread.

So, following the instructions in that thread, I attempted to run the RESTORE FILELISTONLY command from SQL Query analyzer and get this message:

"Could not locate entry in sysdatabases for database 'siebel_prod.' No entry found with that name. Make sure the name is entered correctly."

Can anyone help me with the above issue? This is extremely time critical and I need to get a resolution ASAP.

Thanks in advance.

|||You should not need to include the database name n the RESTORE FILELISTONLY syntax.|||

generally , with the Move option the very common mistake is , you change the logical file name also , ie

Step 1 -- Run the below statement to see the LOGICAL FIle name in the backup set

RESTORE FILELISTONLY FROM DISK = 'D:\yourbackupfile.bak'

RESTORE DATABASE GPx FROM DISK = 'D:\yourbackupfile.bak'

WITH MOVE 'Your_Source_Datbase_Logical_Data_Filename' TO 'D:\TargetDatabae.mdf',

MOVE Your_Source_Datbase_Logical_Log_Filename' TO 'D:\TargetDatabase_log.ldf'

Your_Source_Datbase_Logical_Data_Filename' -- THis should be the source database (not the target) logical filename which can get by RESTORE FILELISTONLY

Your_Source_Datbase_Logical_Log_Filename' -- THis should be the source database logical filename

when you restore a database with move option , your source and target database will have same logical name. This you need to change ALTER DATABASE statemetn after restoration

Madhu

|||

You wrote this:

"RESTORE DATABASE GPx FROM DISK = 'D:\yourbackupfile.bak'"

What is "GPx"?

I'm assuming it is the name of the database to be restored. Right?

|||

i just cut paste from my enviornment man... yes its database name

Madhu

DB Restore problem

Hello all,

I've been reading this thread http://forums.microsoft.com/msdn/ShowPost.aspx?postid=1494867&siteid=1 because I've been having a similar problem.

I wanted to post a new thread to make sure that people have an opportunity to see it and, hopefully, give me some help.

I have a backup of my production database and want to restore it over my development database (using Enterprise Manager). When I first tried the restoration it worked but the application (Siebel) using the database wouldn't log in. Stupidly, instead of reading the log files for the application I panicked and restored the dev database with an old copy of the dev database. Unfortunately this backup was either not complete or had some other problem because that restore failed.

I then tried running the restore (again from Enterprise Manager) of the dev database with my production backup and began receiving the MOVE FILE error discussed in the abovementioned thread.

So, following the instructions in that thread, I attempted to run the RESTORE FILELISTONLY command from SQL Query analyzer and get this message:

"Could not locate entry in sysdatabases for database 'siebel_prod.' No entry found with that name. Make sure the name is entered correctly."

Can anyone help me with the above issue? This is extremely time critical and I need to get a resolution ASAP.

Thanks in advance.

|||You should not need to include the database name n the RESTORE FILELISTONLY syntax.|||

generally , with the Move option the very common mistake is , you change the logical file name also , ie

Step 1 -- Run the below statement to see the LOGICAL FIle name in the backup set

RESTORE FILELISTONLY FROM DISK = 'D:\yourbackupfile.bak'

RESTORE DATABASE GPx FROM DISK = 'D:\yourbackupfile.bak'

WITH MOVE 'Your_Source_Datbase_Logical_Data_Filename' TO 'D:\TargetDatabae.mdf',

MOVE Your_Source_Datbase_Logical_Log_Filename' TO 'D:\TargetDatabase_log.ldf'

Your_Source_Datbase_Logical_Data_Filename' -- THis should be the source database (not the target) logical filename which can get by RESTORE FILELISTONLY

Your_Source_Datbase_Logical_Log_Filename' -- THis should be the source database logical filename

when you restore a database with move option , your source and target database will have same logical name. This you need to change ALTER DATABASE statemetn after restoration

Madhu

|||

You wrote this:

"RESTORE DATABASE GPx FROM DISK = 'D:\yourbackupfile.bak'"

What is "GPx"?

I'm assuming it is the name of the database to be restored. Right?

|||

i just cut paste from my enviornment man... yes its database name

Madhu

|||

>>

RESTORE DATABASE GPx FROM DISK = 'D:\yourbackupfile.bak'

WITH MOVE 'Your_Source_Datbase_Logical_Data_Filename' TO 'D:\TargetDatabae.mdf',

MOVE Your_Source_Datbase_Logical_Log_Filename' TO 'D:\TargetDatabase_log.ldf'

Your_Source_Datbase_Logical_Data_Filename' -- THis should be the source database (not the target) logical filename which can get by RESTORE FILELISTONLY

Your_Source_Datbase_Logical_Log_Filename' -- THis should be the source database logical filename

<<

I just got around to trying to do this. When I do it tells me that my target database doesn't exist and terminates. So I created a new instance of the database, ran it again and it tells me the target database exists and to use the "WITH REPLACE" command. I then changed the command to:

RESTORE DATABASE GPx FROM DISK = 'D:\yourbackupfile.bak'

WITH REPLACE 'Your_Source_Datbase_Logical_Data_Filename' TO 'D:\TargetDatabae.mdf',

MOVE Your_Source_Datbase_Logical_Log_Filename' TO 'D:\TargetDatabase_log.ldf'

And it tells me that 'REPLACE' is an unrecognized restore option. WTF? This shouldn't be that hard.

|||You're not far off Steve, just a slight syntax issue:

RESTORE DATABASE GPx FROM DISK = 'D:\yourbackupfile.bak'

WITH MOVE 'Your_Source_Datbase_Logical_Data_Filename' TO 'D:\TargetDatabae.mdf',

MOVE Your_Source_Datbase_Logical_Log_Filename' TO 'D:\TargetDatabase_log.ldf',

REPLACE,

STATS = 5

I often add in the STATS keyword too, just to show the progress of the RESTORE. For a full list of commands and examples can be found in Books Online.

HTH!
|||Thanks for your response. I'd already figured it out, but I appreciate your effort.

db restoration via shared folder

I was reading the article on the subject above at the
http://examnotes.net/arch/178/2002/3/329543
The question here is:-
Testing was done and I was able to restore db using EM on
a Standard Edition (SP3) and mapped drive to another
server. Unlike I was unable to do that from a Enterprise
Edtion (SP3). Why is that so?
Thanks.So, you made certain that the SQL Server service has permissions on the
share and it still didn't work? What error message did you get?
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
"NG" <angiecmf@.hotmail.com> wrote in message
news:1101001c40fc1$4ab1af40$a501280a@.phx
.gbl...
> I was reading the article on the subject above at the
> http://examnotes.net/arch/178/2002/3/329543
> The question here is:-
> Testing was done and I was able to restore db using EM on
> a Standard Edition (SP3) and mapped drive to another
> server. Unlike I was unable to do that from a Enterprise
> Edtion (SP3). Why is that so?
> Thanks.|||Let me rephrase my question here, Sorry if my explaination
was not clear earlier.
Based on the article, I was able to backup/restore db
without any problem in MSSQL standard/enterprise edition.
The point here is the article stated that backup/restore
can't be done using Enterprise Manager. But I was able to
backup/restore db using Enterprise Manager in Standard
Edition but NOT Enterprise Edition. I was able to see the
mapped drive in the Standard Edition. Why I unable to
view the mapped drive in Enterprise Edition using the
Enterprise Manager? Is this a special feature in Standard
Edition or other setting need to be done here in order to
do so in the Enterprise Edition? Currently I am using
MSSQL 7 with sp(3) on NT4 (sp6).
Your help is much appreciated.

>--Original Message--
>So, you made certain that the SQL Server service has
permissions on the
>share and it still didn't work? What error message did
you get?
>--
>Tibor Karaszi, SQL Server MVP
>http://www.karaszi.com/sqlserver/default.asp
>
>"NG" <angiecmf@.hotmail.com> wrote in message
> news:1101001c40fc1$4ab1af40$a501280a@.phx
.gbl...
on
Enterprise
>
>.
>|||> Based on the article, I was able to backup/restore db
> without any problem in MSSQL standard/enterprise edition.
I assume that you used Query Analyzer for this, is that what you mean?

> The point here is the article stated that backup/restore
> can't be done using Enterprise Manager. But I was able to
> backup/restore db using Enterprise Manager in Standard
> Edition but NOT Enterprise Edition. I was able to see the
> mapped drive in the Standard Edition. Why I unable to
> view the mapped drive in Enterprise Edition using the
> Enterprise Manager? Is this a special feature in Standard
> Edition or other setting need to be done here in order to
> do so in the Enterprise Edition?
I won't read the article, but just be aware that it might be incorrect. Back
to the problem. Here's what I think is going on:
On one installation, the service account is the same as the one you are
logged in as. Hence, the mapped drives are the same. On the other, you are
using different accounts. The key point here is that mapped drives are per
user. And typically, you are not logged in using the same account as the SQL
Server service account. So what you perceive as a mapped drive is different
to what SQL Server does.
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
"NG" <angiecmf@.hotmail.com> wrote in message
news:11e7e01c4107a$848e7680$a101280a@.phx
.gbl...
> Let me rephrase my question here, Sorry if my explaination
> was not clear earlier.
> Based on the article, I was able to backup/restore db
> without any problem in MSSQL standard/enterprise edition.
> The point here is the article stated that backup/restore
> can't be done using Enterprise Manager. But I was able to
> backup/restore db using Enterprise Manager in Standard
> Edition but NOT Enterprise Edition. I was able to see the
> mapped drive in the Standard Edition. Why I unable to
> view the mapped drive in Enterprise Edition using the
> Enterprise Manager? Is this a special feature in Standard
> Edition or other setting need to be done here in order to
> do so in the Enterprise Edition? Currently I am using
> MSSQL 7 with sp(3) on NT4 (sp6).
> Your help is much appreciated.
>
> permissions on the
> you get?
> on
> Enterprise