HELP! Restore DTS, Jobs, Etc.

crap! Any immediate help would be greatly appreciated!
Our sql 2000 database server crashed after installing MS's latest patches
and now we're having to rebuild the OS and all the configurations (we've
tried everything else - this is a last resort). The data for the server is
on a separate logical drive, so we should have all the data (also backed
up). The problem is, we have several DTS packages, Jobs, and linked servers
that I'm uncertain how we can "restore."
Is there any method of getting this information back, when we're going to
have to re-install SQL 2000?
Thanks, JordanAll this information is in your MSDB database. If it is part of your backup
and recovery plan, you will be OK. You may have noticed this during your
backup and recovery test. You did test your plan, didn't you?
--
Geoff N. Hiten
Microsoft SQL Server MVP
Senior Database Administrator
Careerbuilder.com
I support the Professional Association for SQL Server
www.sqlpass.org
"Jordan" <jfritts@.learn.colostate.edu> wrote in message
news:%23B45l$tDFHA.328@.tk2msftngp13.phx.gbl...
> crap! Any immediate help would be greatly appreciated!
> Our sql 2000 database server crashed after installing MS's latest patches
> and now we're having to rebuild the OS and all the configurations (we've
> tried everything else - this is a last resort). The data for the server is
> on a separate logical drive, so we should have all the data (also backed
> up). The problem is, we have several DTS packages, Jobs, and linked
servers
> that I'm uncertain how we can "restore."
> Is there any method of getting this information back, when we're going to
> have to re-install SQL 2000?
> Thanks, Jordan
>|||Yes - i do backup the MSDB. The issue now is, since this is the production
server, i needed to get things online ASAP. So, i tried the "rebuild master"
utility, but my versions of sql server were off a little (they both had sp3a
on them so I'm not sure why). Anyway, to restore services, I simply
attached all my databases and recreated the 6-7 logins that we use.
So, I don't think I can import the MSDB database from my "crashed" server
can I? Won't it overwrite everything I've just done. I'm thinking I may be
able to build another machine and restore the MSDB database to that one,
then move the files from server to server.
ideas?
thanks, j
"Geoff N. Hiten" <SRDBA@.Careerbuilder.com> wrote in message
news:O6NKzNvDFHA.2156@.TK2MSFTNGP10.phx.gbl...
> All this information is in your MSDB database. If it is part of your
backup
> and recovery plan, you will be OK. You may have noticed this during your
> backup and recovery test. You did test your plan, didn't you?
> --
> Geoff N. Hiten
> Microsoft SQL Server MVP
> Senior Database Administrator
> Careerbuilder.com
> I support the Professional Association for SQL Server
> www.sqlpass.org
> "Jordan" <jfritts@.learn.colostate.edu> wrote in message
> news:%23B45l$tDFHA.328@.tk2msftngp13.phx.gbl...
> > crap! Any immediate help would be greatly appreciated!
> >
> > Our sql 2000 database server crashed after installing MS's latest
patches
> > and now we're having to rebuild the OS and all the configurations (we've
> > tried everything else - this is a last resort). The data for the server
is
> > on a separate logical drive, so we should have all the data (also backed
> > up). The problem is, we have several DTS packages, Jobs, and linked
> servers
> > that I'm uncertain how we can "restore."
> >
> > Is there any method of getting this information back, when we're going
to
> > have to re-install SQL 2000?
> >
> > Thanks, Jordan
> >
> >
>|||Backup your existing msdb. Restore the 'old' one. If you have changed the
SQL instance (server) name, you will have to hack the tables to change the
system name in the job tables. If you are using the same server and
instance name, it should work. Master contains the database and login
information. Msdb contains the backup and restore records and the SQL agent
information along with DTS packages. Worst case, restore the 'new' msdb and
you are no worse off than right now.
--
Geoff N. Hiten
Microsoft SQL Server MVP
Senior Database Administrator
Careerbuilder.com
I support the Professional Association for SQL Server
www.sqlpass.org
"Jordan" <jfritts@.learn.colostate.edu> wrote in message
news:ObIymlwDFHA.1668@.TK2MSFTNGP10.phx.gbl...
> Yes - i do backup the MSDB. The issue now is, since this is the production
> server, i needed to get things online ASAP. So, i tried the "rebuild
master"
> utility, but my versions of sql server were off a little (they both had
sp3a
> on them so I'm not sure why). Anyway, to restore services, I simply
> attached all my databases and recreated the 6-7 logins that we use.
> So, I don't think I can import the MSDB database from my "crashed" server
> can I? Won't it overwrite everything I've just done. I'm thinking I may be
> able to build another machine and restore the MSDB database to that one,
> then move the files from server to server.
> ideas?
> thanks, j
> "Geoff N. Hiten" <SRDBA@.Careerbuilder.com> wrote in message
> news:O6NKzNvDFHA.2156@.TK2MSFTNGP10.phx.gbl...
> > All this information is in your MSDB database. If it is part of your
> backup
> > and recovery plan, you will be OK. You may have noticed this during
your
> > backup and recovery test. You did test your plan, didn't you?
> >
> > --
> > Geoff N. Hiten
> > Microsoft SQL Server MVP
> > Senior Database Administrator
> > Careerbuilder.com
> >
> > I support the Professional Association for SQL Server
> > www.sqlpass.org
> >
> > "Jordan" <jfritts@.learn.colostate.edu> wrote in message
> > news:%23B45l$tDFHA.328@.tk2msftngp13.phx.gbl...
> > > crap! Any immediate help would be greatly appreciated!
> > >
> > > Our sql 2000 database server crashed after installing MS's latest
> patches
> > > and now we're having to rebuild the OS and all the configurations
(we've
> > > tried everything else - this is a last resort). The data for the
server
> is
> > > on a separate logical drive, so we should have all the data (also
backed
> > > up). The problem is, we have several DTS packages, Jobs, and linked
> > servers
> > > that I'm uncertain how we can "restore."
> > >
> > > Is there any method of getting this information back, when we're going
> to
> > > have to re-install SQL 2000?
> > >
> > > Thanks, Jordan
> > >
> > >
> >
> >
>|||FYI: You must install MS03-031 after SP3a. I didn't see this mentioned,
but you are correct - the versions must match:
8.00.076 SQL Server 2000 SP3
8.00.818 SQL Server 2000 SP3 w/ Cumulative Patch MS03-031
I'm sure this is much after the fact, but worth mentioning for future
reference.
--
A McGuire
"Jordan" <jfritts@.learn.colostate.edu> wrote in message
news:ObIymlwDFHA.1668@.TK2MSFTNGP10.phx.gbl...
> Yes - i do backup the MSDB. The issue now is, since this is the production
> server, i needed to get things online ASAP. So, i tried the "rebuild
> master"
> utility, but my versions of sql server were off a little (they both had
> sp3a
> on them so I'm not sure why). Anyway, to restore services, I simply
> attached all my databases and recreated the 6-7 logins that we use.
> So, I don't think I can import the MSDB database from my "crashed" server
> can I? Won't it overwrite everything I've just done. I'm thinking I may be
> able to build another machine and restore the MSDB database to that one,
> then move the files from server to server.
> ideas?
> thanks, j
> "Geoff N. Hiten" <SRDBA@.Careerbuilder.com> wrote in message
> news:O6NKzNvDFHA.2156@.TK2MSFTNGP10.phx.gbl...
>> All this information is in your MSDB database. If it is part of your
> backup
>> and recovery plan, you will be OK. You may have noticed this during your
>> backup and recovery test. You did test your plan, didn't you?
>> --
>> Geoff N. Hiten
>> Microsoft SQL Server MVP
>> Senior Database Administrator
>> Careerbuilder.com
>> I support the Professional Association for SQL Server
>> www.sqlpass.org
>> "Jordan" <jfritts@.learn.colostate.edu> wrote in message
>> news:%23B45l$tDFHA.328@.tk2msftngp13.phx.gbl...
>> > crap! Any immediate help would be greatly appreciated!
>> >
>> > Our sql 2000 database server crashed after installing MS's latest
> patches
>> > and now we're having to rebuild the OS and all the configurations
>> > (we've
>> > tried everything else - this is a last resort). The data for the server
> is
>> > on a separate logical drive, so we should have all the data (also
>> > backed
>> > up). The problem is, we have several DTS packages, Jobs, and linked
>> servers
>> > that I'm uncertain how we can "restore."
>> >
>> > Is there any method of getting this information back, when we're going
> to
>> > have to re-install SQL 2000?
>> >
>> > Thanks, Jordan
>> >
>> >
>>
>

Help! Oracle linked server not working

we upgraded servers and now i can't link to an oracle server
old config:
windows2000
sql2000 sp4
mdac 2.8
oracle client 9.2 with latest patches
new config:
windows2003
sql2000 sp4
mdac 2.8
oracle client 9.2 with latest patches
the oracle db is 9.2.
i get the error 7399: OLE DB provider 'MSDAORA' reported an error.
OLE DB error trace [OLE/DB Provider 'MSDAORA' IDBInitialize::Initialize
returned 0x80004005:]
i've scoured the internet and found numerous solutions to this, none of
which work.
i found an article in oracle technet that said to redo all permissions
on the oraclehome
directory. that didn't work.
i made sure the registry entries pointed to the correct oracle dll's.
no help.
i tried the 10g client with latest patch. no help.
i deleted and readded the linked server. no help.
i can use sqlplus or netmanager and connect to the oracle db just fine
from the sql server.
i don't know what else to try.
i'm wondering if it's windows2003 that's screwing things up.
has anybody been able to link to an oracle server from a win2003 server
running sql server sp4?Some additional questions:
What platform is the Oracle database?
Is connection pooling being used?
What language is doing the call or are you doing linked servers (four level
table qualifier)?
That particular error has a lot of possibles, as you found. Don't want to
re-hash what you have already ruled out.
--
Joseph R.P. Maloney, CSP,CCP,CDP
"ch" wrote:
> we upgraded servers and now i can't link to an oracle server
> old config:
> windows2000
> sql2000 sp4
> mdac 2.8
> oracle client 9.2 with latest patches
>
> new config:
> windows2003
> sql2000 sp4
> mdac 2.8
> oracle client 9.2 with latest patches
>
> the oracle db is 9.2.
> i get the error 7399: OLE DB provider 'MSDAORA' reported an error.
> OLE DB error trace [OLE/DB Provider 'MSDAORA' IDBInitialize::Initialize
> returned 0x80004005:]
> i've scoured the internet and found numerous solutions to this, none of
> which work.
> i found an article in oracle technet that said to redo all permissions
> on the oraclehome
> directory. that didn't work.
> i made sure the registry entries pointed to the correct oracle dll's.
> no help.
> i tried the 10g client with latest patch. no help.
> i deleted and readded the linked server. no help.
> i can use sqlplus or netmanager and connect to the oracle db just fine
> from the sql server.
> i don't know what else to try.
> i'm wondering if it's windows2003 that's screwing things up.
> has anybody been able to link to an oracle server from a win2003 server
> running sql server sp4?
>