Re: Copy database fails - failed to copy file .. OMWWIZC ..

#1

Tell you the truth i do not use the task myself. If I want to COPY a
database from A --> B I use BACKUP and RESTORE. I personally think its much
faster.

Have you seen the KB?

http://support.microsoft.com/default...NoWebContent=1

--
--

Allan Mitchell MCSE,MCDBA, (Microsoft SQL Server MVP)
www.SQLDTS.com - The site for all your DTS needs.
I support PASS - the definitive, global community
for SQL Server professionals - http://www.sqlpass.org

"Danny Falkirk Council" <anonymous (AT) discussions (DOT) microsoft.com> wrote in
message news:1C62D72A-ECF8-4FAE-8CCE-6E696C9748E4 (AT) microsoft (DOT) com...

Quote:

We have SQL 2000 on 3 servers - test, prod and buscon. Domain user
SQLService is the account for both Service accounts on all 3 servers and is

a member of the local administrators group on all 3 servers.

Quote:

We are trying to use DTS to copy databases from one server to another.
Because of the problems and confusion encountered, we ran some simple tests

where (a) we set up a new database "dbtest", accepting all defaults, on the
prod server (b) when copying we only attempt to copy the database and not
logins, etc.

Quote:

1. I can successfully copy dbtest from one instance to another on the prod
server.
2. If I set up a local package and run it, it fails with "Failed to copy
file .. OMWWIZC .."
N.B. It successfully sets up the OMWWIZC share.
3. If I use the Copy Database Wizard I have some limited success.
(a) If I use the Copy Database Wizard and run it immediately then I can
successfully copy dbtest from prod to test, from test to prod and from prod

to buscon (but not from buscon to another server). If I delete dbtest (and
restart my Enterprise Manager) and run the generated local package it fails
with the same error as in 2 above!

Quote:

(b) If I use the Copy Database Wizard for copying from prod to test and
schedule it to run later then I get a job (waiting to be run) and a local

package "pkg1". If I run the package it fails with the same error as in 2
above. If I run the job or if the job runs at it's scheduled time then it
successfully copies from prod to test. If I delete dbtest prior to the next
scheduled run of the job, it successfully copies from prod to test.

Quote:

This looks like a bug to me - has anyone experienced anything similar and
found a solution?

#2

Thanks Allan - I had read the KB article prior to posting, but it wasn't helfpul for my problem. Like you, I was using BACKUP and RESTORE when COPYING a database (managing to find ways around problems with "user permissions on the database on the target SQL Instance"). A colleague attended a training course and the trainer strongly recommended not using BACKUP/RESTORE when MOVING a database and we assumed the same held true for COPYING a database. We have quite a number of databases we intend moving, so we feel we have to get the recommended method working

----- Allan Mitchell wrote: ----

Tell you the truth i do not use the task myself. If I want to COPY
database from A --> B I use BACKUP and RESTORE. I personally think its muc
faster

Have you seen the KB

http://support.microsoft.com/default...&NoWebContent=

--
--

Allan Mitchell MCSE,MCDBA, (Microsoft SQL Server MVP
www.SQLDTS.com - The site for all your DTS needs
I support PASS - the definitive, global communit
for SQL Server professionals - http://www.sqlpass.or

"Danny Falkirk Council" <anonymous (AT) discussions (DOT) microsoft.com> wrote i
message news:1C62D72A-ECF8-4FAE-8CCE-6E696C9748E4 (AT) microsoft (DOT) com..

Quote:

We have SQL 2000 on 3 servers - test, prod and buscon. Domain use
SQLService is the account for both Service accounts on all 3 servers and i

a member of the local administrators group on all 3 servers

Quote:

We are trying to use DTS to copy databases from one server to another
Because of the problems and confusion encountered, we ran some simple test

where (a) we set up a new database "dbtest", accepting all defaults, on th
prod server (b) when copying we only attempt to copy the database and no
logins, etc

Quote:

1. I can successfully copy dbtest from one instance to another on the pro
server
2. If I set up a local package and run it, it fails with "Failed to cop
file .. OMWWIZC ..
N.B. It successfully sets up the OMWWIZC share
3. If I use the Copy Database Wizard I have some limited success
(a) If I use the Copy Database Wizard and run it immediately then I ca
successfully copy dbtest from prod to test, from test to prod and from pro

to buscon (but not from buscon to another server). If I delete dbtest (an
restart my Enterprise Manager) and run the generated local package it fail
with the same error as in 2 above

Quote:

(b) If I use the Copy Database Wizard for copying from prod to test an
schedule it to run later then I get a job (waiting to be run) and a loca

package "pkg1". If I run the package it fails with the same error as in
above. If I run the job or if the job runs at it's scheduled time then i
successfully copies from prod to test. If I delete dbtest prior to the nex
scheduled run of the job, it successfully copies from prod to test

Quote:

This looks like a bug to me - has anyone experienced anything similar an
found a solution

#3

I do not know why the trainer would not recommend BACKUP/RESTORE. It is
perfectly Valid/Quick/Easy

Things that may go awry

Users being orphaned (sp_change_users_login)
File Locations not being the same on the destination - (MOVE clause to
RESTORE)

Moving simply means delete the source after the move whereas copy means
leave the source.

Moving requires that no users are in the DB to do the delete.

--
--

Allan Mitchell MCSE,MCDBA, (Microsoft SQL Server MVP)
www.SQLDTS.com - The site for all your DTS needs.
I support PASS - the definitive, global community
for SQL Server professionals - http://www.sqlpass.org

"Danny Falkirk Council" <anonymous (AT) discussions (DOT) microsoft.com> wrote in
message news:72B323A4-E273-483B-9C97-EA2F5A4A31F6 (AT) microsoft (DOT) com...

Quote:

Thanks Allan - I had read the KB article prior to posting, but it wasn't
helfpul for my problem. Like you, I was using BACKUP and RESTORE when

COPYING a database (managing to find ways around problems with "user
permissions on the database on the target SQL Instance"). A colleague
attended a training course and the trainer strongly recommended not using
BACKUP/RESTORE when MOVING a database and we assumed the same held true for
COPYING a database. We have quite a number of databases we intend moving,
so we feel we have to get the recommended method working.

Quote:

----- Allan Mitchell wrote: -----

Tell you the truth i do not use the task myself. If I want to COPY a
database from A --> B I use BACKUP and RESTORE. I personally think
its much
faster.

Have you seen the KB?

http://support.microsoft.com/default...NoWebContent=1

--
--

Allan Mitchell MCSE,MCDBA, (Microsoft SQL Server MVP)
www.SQLDTS.com - The site for all your DTS needs.
I support PASS - the definitive, global community
for SQL Server professionals - http://www.sqlpass.org

"Danny Falkirk Council" <anonymous (AT) discussions (DOT) microsoft.com> wrote
in
message news:1C62D72A-ECF8-4FAE-8CCE-6E696C9748E4 (AT) microsoft (DOT) com...
We have SQL 2000 on 3 servers - test, prod and buscon. Domain user
SQLService is the account for both Service accounts on all 3 servers
and is
a member of the local administrators group on all 3 servers.
We are trying to use DTS to copy databases from one server to
another.
Because of the problems and confusion encountered, we ran some simple
tests
where (a) we set up a new database "dbtest", accepting all defaults,
on the
prod server (b) when copying we only attempt to copy the database and
not
logins, etc.
1. I can successfully copy dbtest from one instance to another on
the prod
server.
2. If I set up a local package and run it, it fails with "Failed to
copy
file .. OMWWIZC .."
N.B. It successfully sets up the OMWWIZC share.
3. If I use the Copy Database Wizard I have some limited success.
(a) If I use the Copy Database Wizard and run it immediately then I
can
successfully copy dbtest from prod to test, from test to prod and
from prod
to buscon (but not from buscon to another server). If I delete
dbtest (and
restart my Enterprise Manager) and run the generated local package it
fails
with the same error as in 2 above!
(b) If I use the Copy Database Wizard for copying from prod to test
and
schedule it to run later then I get a job (waiting to be run) and a
local
package "pkg1". If I run the package it fails with the same error as
in 2
above. If I run the job or if the job runs at it's scheduled time
then it
successfully copies from prod to test. If I delete dbtest prior to
the next
scheduled run of the job, it successfully copies from prod to test.
This looks like a bug to me - has anyone experienced anything
similar and
found a solution?

#4

Hi Allan
While my original problems still exist and annoy me - your solution was spot on. I had used Backup and Restore in the past but because of the problems encountered (orphan users and changed file locations) and because I am relatively new to SQL administration, I assumed that the trainers recommendations were valid and should be followed. Your reassurances left me secure enough to Restore the database and deal with the 2 minor irritants quickly and easily

Thanks again for your help.

Thread Tools
Show Printable Version Email this Page
Display Modes
Linear Mode Switch to Hybrid Mode Switch to Threaded Mode

Re: Copy database fails - failed to copy file .. OMWWIZC ..

microsoft.public.sqlserver.dts microsoft.public.sqlserver.dts

Re: Copy database fails - failed to copy file .. OMWWIZC .. - 04-08-2004 , 02:07 PM

Re: Copy database fails - failed to copy file .. OMWWIZC .. - 04-13-2004 , 05:16 AM

Re: Copy database fails - failed to copy file .. OMWWIZC .. - 04-13-2004 , 05:38 AM

Re: Copy database fails - failed to copy file .. OMWWIZC .. - 04-14-2004 , 09:36 AM