I have inherited a Sql Server 2000 instance who's DTS accesses an Oracle 8
database. That Oracle 8 database is going to be upgraded to Oracle 9i soon,
and I was wondering what I have to do to keep this all running. I think I
have to upgrade the Oracle client on the Sql Server box to 9i (since the
Oracle 8 client can not talk to Oracle 9i). Other than that, I am not aware
of anything else I have to do.
Anyone done this before?
Thanks,
Michael
"Snake" wrote:
> I have inherited a Sql Server 2000 instance who's DTS accesses an Oracle 8
> database. That Oracle 8 database is going to be upgraded to Oracle 9i soon,
> and I was wondering what I have to do to keep this all running. I think I
> have to upgrade the Oracle client on the Sql Server box to 9i (since the
> Oracle 8 client can not talk to Oracle 9i). Other than that, I am not aware
> of anything else I have to do.
> Anyone done this before?
> Thanks,
> Michael
|||You should be able to upgrade the Oracle client from 8 to 9i on your side to
solve this problem. My suggestion is to install Oracle 9i on the SQL Server
machine in parallel with the Oracle 8 client. To do this, copy your DTS
package into a new one with a similar name. Create a new DSN that uses the
Oracle 9i client and then test it on the server to make sure the Oracle 9
install worked successfully. Since the Oracle 9i client can read an Oracle 8
database you can switch to this install early and then you'll be prepared
early for the production change on the source database. After the source
database is upgraded to Oracle 9i, you can safely remove the old Oracle 8i
components from your server.
"Snake" wrote:
> I have inherited a Sql Server 2000 instance who's DTS accesses an Oracle 8
> database. That Oracle 8 database is going to be upgraded to Oracle 9i soon,
> and I was wondering what I have to do to keep this all running. I think I
> have to upgrade the Oracle client on the Sql Server box to 9i (since the
> Oracle 8 client can not talk to Oracle 9i). Other than that, I am not aware
> of anything else I have to do.
> Anyone done this before?
> Thanks,
> Michael
|||Also, keep in mind that Oracle's new DATETIME data type has "known" issues
with respect to SQL Server.
Do a search on the net for issues and the workarounds.
Sincerely,
Anthony Thomas
"Amrith" <Amrith@.discussions.microsoft.com> wrote in message
news:5C126AC9-DF98-4B2A-8F8A-E5D887A502AB@.microsoft.com...
You should be able to upgrade the Oracle client from 8 to 9i on your side to
solve this problem. My suggestion is to install Oracle 9i on the SQL Server
machine in parallel with the Oracle 8 client. To do this, copy your DTS
package into a new one with a similar name. Create a new DSN that uses the
Oracle 9i client and then test it on the server to make sure the Oracle 9
install worked successfully. Since the Oracle 9i client can read an Oracle 8
database you can switch to this install early and then you'll be prepared
early for the production change on the source database. After the source
database is upgraded to Oracle 9i, you can safely remove the old Oracle 8i
components from your server.
"Snake" wrote:
> I have inherited a Sql Server 2000 instance who's DTS accesses an Oracle 8
> database. That Oracle 8 database is going to be upgraded to Oracle 9i
soon,
> and I was wondering what I have to do to keep this all running. I think I
> have to upgrade the Oracle client on the Sql Server box to 9i (since the
> Oracle 8 client can not talk to Oracle 9i). Other than that, I am not
aware
> of anything else I have to do.
> Anyone done this before?
> Thanks,
> Michael
Showing posts with label upgraded. Show all posts
Showing posts with label upgraded. Show all posts
Wednesday, March 21, 2012
DTS connection to Oracle 8; To be upgrated to Oracle 9i. Any guida
I have inherited a Sql Server 2000 instance who's DTS accesses an Oracle 8
database. That Oracle 8 database is going to be upgraded to Oracle 9i soon,
and I was wondering what I have to do to keep this all running. I think I
have to upgrade the Oracle client on the Sql Server box to 9i (since the
Oracle 8 client can not talk to Oracle 9i). Other than that, I am not aware
of anything else I have to do.
Anyone done this before?
Thanks,
MichaelYou should be able to upgrade the Oracle client from 8 to 9i on your side to
solve this problem. My suggestion is to install Oracle 9i on the SQL Server
machine in parallel with the Oracle 8 client. To do this, copy your DTS
package into a new one with a similar name. Create a new DSN that uses the
Oracle 9i client and then test it on the server to make sure the Oracle 9
install worked successfully. Since the Oracle 9i client can read an Oracle 8
database you can switch to this install early and then you'll be prepared
early for the production change on the source database. After the source
database is upgraded to Oracle 9i, you can safely remove the old Oracle 8i
components from your server.
"Snake" wrote:
> I have inherited a Sql Server 2000 instance who's DTS accesses an Oracle 8
> database. That Oracle 8 database is going to be upgraded to Oracle 9i soon,
> and I was wondering what I have to do to keep this all running. I think I
> have to upgrade the Oracle client on the Sql Server box to 9i (since the
> Oracle 8 client can not talk to Oracle 9i). Other than that, I am not aware
> of anything else I have to do.
> Anyone done this before?
> Thanks,
> Michael|||"Snake" wrote:
> I have inherited a Sql Server 2000 instance who's DTS accesses an Oracle 8
> database. That Oracle 8 database is going to be upgraded to Oracle 9i soon,
> and I was wondering what I have to do to keep this all running. I think I
> have to upgrade the Oracle client on the Sql Server box to 9i (since the
> Oracle 8 client can not talk to Oracle 9i). Other than that, I am not aware
> of anything else I have to do.
> Anyone done this before?
> Thanks,
> Michael|||Also, keep in mind that Oracle's new DATETIME data type has "known" issues
with respect to SQL Server.
Do a search on the net for issues and the workarounds.
Sincerely,
Anthony Thomas
"Amrith" <Amrith@.discussions.microsoft.com> wrote in message
news:5C126AC9-DF98-4B2A-8F8A-E5D887A502AB@.microsoft.com...
You should be able to upgrade the Oracle client from 8 to 9i on your side to
solve this problem. My suggestion is to install Oracle 9i on the SQL Server
machine in parallel with the Oracle 8 client. To do this, copy your DTS
package into a new one with a similar name. Create a new DSN that uses the
Oracle 9i client and then test it on the server to make sure the Oracle 9
install worked successfully. Since the Oracle 9i client can read an Oracle 8
database you can switch to this install early and then you'll be prepared
early for the production change on the source database. After the source
database is upgraded to Oracle 9i, you can safely remove the old Oracle 8i
components from your server.
"Snake" wrote:
> I have inherited a Sql Server 2000 instance who's DTS accesses an Oracle 8
> database. That Oracle 8 database is going to be upgraded to Oracle 9i
soon,
> and I was wondering what I have to do to keep this all running. I think I
> have to upgrade the Oracle client on the Sql Server box to 9i (since the
> Oracle 8 client can not talk to Oracle 9i). Other than that, I am not
aware
> of anything else I have to do.
> Anyone done this before?
> Thanks,
> Michael
database. That Oracle 8 database is going to be upgraded to Oracle 9i soon,
and I was wondering what I have to do to keep this all running. I think I
have to upgrade the Oracle client on the Sql Server box to 9i (since the
Oracle 8 client can not talk to Oracle 9i). Other than that, I am not aware
of anything else I have to do.
Anyone done this before?
Thanks,
MichaelYou should be able to upgrade the Oracle client from 8 to 9i on your side to
solve this problem. My suggestion is to install Oracle 9i on the SQL Server
machine in parallel with the Oracle 8 client. To do this, copy your DTS
package into a new one with a similar name. Create a new DSN that uses the
Oracle 9i client and then test it on the server to make sure the Oracle 9
install worked successfully. Since the Oracle 9i client can read an Oracle 8
database you can switch to this install early and then you'll be prepared
early for the production change on the source database. After the source
database is upgraded to Oracle 9i, you can safely remove the old Oracle 8i
components from your server.
"Snake" wrote:
> I have inherited a Sql Server 2000 instance who's DTS accesses an Oracle 8
> database. That Oracle 8 database is going to be upgraded to Oracle 9i soon,
> and I was wondering what I have to do to keep this all running. I think I
> have to upgrade the Oracle client on the Sql Server box to 9i (since the
> Oracle 8 client can not talk to Oracle 9i). Other than that, I am not aware
> of anything else I have to do.
> Anyone done this before?
> Thanks,
> Michael|||"Snake" wrote:
> I have inherited a Sql Server 2000 instance who's DTS accesses an Oracle 8
> database. That Oracle 8 database is going to be upgraded to Oracle 9i soon,
> and I was wondering what I have to do to keep this all running. I think I
> have to upgrade the Oracle client on the Sql Server box to 9i (since the
> Oracle 8 client can not talk to Oracle 9i). Other than that, I am not aware
> of anything else I have to do.
> Anyone done this before?
> Thanks,
> Michael|||Also, keep in mind that Oracle's new DATETIME data type has "known" issues
with respect to SQL Server.
Do a search on the net for issues and the workarounds.
Sincerely,
Anthony Thomas
"Amrith" <Amrith@.discussions.microsoft.com> wrote in message
news:5C126AC9-DF98-4B2A-8F8A-E5D887A502AB@.microsoft.com...
You should be able to upgrade the Oracle client from 8 to 9i on your side to
solve this problem. My suggestion is to install Oracle 9i on the SQL Server
machine in parallel with the Oracle 8 client. To do this, copy your DTS
package into a new one with a similar name. Create a new DSN that uses the
Oracle 9i client and then test it on the server to make sure the Oracle 9
install worked successfully. Since the Oracle 9i client can read an Oracle 8
database you can switch to this install early and then you'll be prepared
early for the production change on the source database. After the source
database is upgraded to Oracle 9i, you can safely remove the old Oracle 8i
components from your server.
"Snake" wrote:
> I have inherited a Sql Server 2000 instance who's DTS accesses an Oracle 8
> database. That Oracle 8 database is going to be upgraded to Oracle 9i
soon,
> and I was wondering what I have to do to keep this all running. I think I
> have to upgrade the Oracle client on the Sql Server box to 9i (since the
> Oracle 8 client can not talk to Oracle 9i). Other than that, I am not
aware
> of anything else I have to do.
> Anyone done this before?
> Thanks,
> Michael
Sunday, March 11, 2012
DTS and Excel 2003
We have a DTS package that imports data from a client's Excel file. Previously our client was using Excel 2000, but recently they upgraded to Office 2003, and now suddenly when I try to view the transformation task properties I get a Jet Database Engine error: "External table is not in the expected format".
Everything else with the file appears the same (layout, formatting, etc.).
Any suggestions?
I have the same problem. Did you ever received suggestions or a solution. I would be happy to have the answer.
Thanks
DTS and Excel 2003
We have a DTS package that imports data from a client's Excel file. Previously our client was using Excel 2000, but recently they upgraded to Office 2003, and now suddenly when I try to view the transformation task properties I get a Jet Database Engine error: "External table is not in the expected format".
Everything else with the file appears the same (layout, formatting, etc.).
Any suggestions?
I have the same problem. Did you ever received suggestions or a solution. I would be happy to have the answer.
Thanks
Wednesday, March 7, 2012
DTS oracle Jobs hang
hello:
My situation is
(1) I upgraded MS SQL 7.0 from original edition to SP 4
(2) DTS packages which download data from an oracle server work fine both on a remote machine and on the Server
(3) When these packages are scheduled to run as jobs they do not succeed and do not fail they just keep running e.g for 58 hours over the weekend
(4) even if I start the job on the server I still get the same behaviour:
Can anyone help please?I have lots of experience with running DTS packages to Oracle, but none in a SQL 7 SP4 environment. These are the things that I would do:
1. Check your application error log; look for any warnings and/or errors that are related to Oracle.
2. Open of SQL*Plus on the server; attempt to connect. Look for any error messages or warnings.
3. Delete and re-initialize the Oracle connection objects in your DTS packages; this can be a pain. Try creating the new connection first and then changing the connection name in the connection objects that are "in the flow".
4. Save the DTS package as a VB file and open (and execute) the package in VB. I dunno if this is an option with SQL 7.0 SP4; it is with 2000.
Sorry, that's not very much to go one for right now. I have seen this issue with AS/400 connections (frequently). It boiled down to an application pop-up window which was not visible when the DTS job ran as a job (but which was visible when executed from the DTS pacakge maintenance window).
Best of luck.
Regards,
hmscott|||Thank you HMScott
I've investigated these and still could'nt find the problem. Then I noticed that the jobs actually work but are not marked as finished. This seems identical to http://www.dbforums.com/t943042.html except that this SQL 7.0 and that was SQL 2000. I still cant get the jobs to mark themselves as finished. ??|||Out of curiousity, where are you seeing that the jobs are not marked "finished". If you are looking at the jobs through the job monitor (under Management/SQL Server Agent/Jobs), are you remembering to periodically refresh the screen (press F5)?
Regards,
hmscott|||I sure do HM (F5 that is) The jobs normally take a minute but when I cancelled them they had been running for 58 hours plus. I'm begining to wonder if it's something to do with the mail client. This machine was also hit by the Lovebug virus which is mail related I believe.
I'm no expert but I was wondering if there was anyway I could get a hint as to whats wrong. I looked in sqlagent.out but could see nothing.
I ran a trace and then started the job. Could'nt see anything obvious but to be honest was a bit lost in there in Trace World.|||Can take help of this KBA (http://support.microsoft.com/default.aspx?scid=kb;EN-US;Q269074) to schedule dts as a job.
And also this Winnet mag article (http://www.winnetmag.com/Article/ArticleID/14399/Windows_14399.html) for reference.
HTH|||Thanks to all for their input:
Current situation
The jobs are now working.
I went into the Package properties and disabled the "USE OLE DB service components" and now the jobs work and mark themselves as completed. If I enable this then the Oracle jobs wont mark themselves as completed.
This weird as the connection still uses the "Oracle provider for OLE DB"
Nevertheless it is progress
My situation is
(1) I upgraded MS SQL 7.0 from original edition to SP 4
(2) DTS packages which download data from an oracle server work fine both on a remote machine and on the Server
(3) When these packages are scheduled to run as jobs they do not succeed and do not fail they just keep running e.g for 58 hours over the weekend
(4) even if I start the job on the server I still get the same behaviour:
Can anyone help please?I have lots of experience with running DTS packages to Oracle, but none in a SQL 7 SP4 environment. These are the things that I would do:
1. Check your application error log; look for any warnings and/or errors that are related to Oracle.
2. Open of SQL*Plus on the server; attempt to connect. Look for any error messages or warnings.
3. Delete and re-initialize the Oracle connection objects in your DTS packages; this can be a pain. Try creating the new connection first and then changing the connection name in the connection objects that are "in the flow".
4. Save the DTS package as a VB file and open (and execute) the package in VB. I dunno if this is an option with SQL 7.0 SP4; it is with 2000.
Sorry, that's not very much to go one for right now. I have seen this issue with AS/400 connections (frequently). It boiled down to an application pop-up window which was not visible when the DTS job ran as a job (but which was visible when executed from the DTS pacakge maintenance window).
Best of luck.
Regards,
hmscott|||Thank you HMScott
I've investigated these and still could'nt find the problem. Then I noticed that the jobs actually work but are not marked as finished. This seems identical to http://www.dbforums.com/t943042.html except that this SQL 7.0 and that was SQL 2000. I still cant get the jobs to mark themselves as finished. ??|||Out of curiousity, where are you seeing that the jobs are not marked "finished". If you are looking at the jobs through the job monitor (under Management/SQL Server Agent/Jobs), are you remembering to periodically refresh the screen (press F5)?
Regards,
hmscott|||I sure do HM (F5 that is) The jobs normally take a minute but when I cancelled them they had been running for 58 hours plus. I'm begining to wonder if it's something to do with the mail client. This machine was also hit by the Lovebug virus which is mail related I believe.
I'm no expert but I was wondering if there was anyway I could get a hint as to whats wrong. I looked in sqlagent.out but could see nothing.
I ran a trace and then started the job. Could'nt see anything obvious but to be honest was a bit lost in there in Trace World.|||Can take help of this KBA (http://support.microsoft.com/default.aspx?scid=kb;EN-US;Q269074) to schedule dts as a job.
And also this Winnet mag article (http://www.winnetmag.com/Article/ArticleID/14399/Windows_14399.html) for reference.
HTH|||Thanks to all for their input:
Current situation
The jobs are now working.
I went into the Package properties and disabled the "USE OLE DB service components" and now the jobs work and mark themselves as completed. If I enable this then the Oracle jobs wont mark themselves as completed.
This weird as the connection still uses the "Oracle provider for OLE DB"
Nevertheless it is progress
Subscribe to:
Posts (Atom)