 | |
SSIS Import Job
microsoft.public.sqlserver.dts microsoft.public.sqlserver.dts
 |
| | Thread Tools | Display Modes |
#11
 
| |||
| |||
|
Re: SSIS Import Job -
09-17-2008
, 12:18 PM
|
Hello Darryl: Yes, it sure sounds like an Oracle issue. When you say you can run it manually, and yet it fails when schedulsed, can you give us more details as to what machine each of these operations is performed on? By "manually" do you mean your local development desktop, running in the BIDS Development Environment? Does "scheduled" mean it is trying to run on a server? Have you tried executing the package from the server by using SSMS connected to the SSIS instance on the server? (Right-click the package and select Execute). What kind of info are you seeing in the error messages and logs? HTH -- Todd C [If this response was helpful, please indicate by clicking the appropriate answer at the bottom] "DB" wrote: I have an SSIS job, SQL 2005 SP2, Windows Server 2003, that imports data from multiple databases into local SQL tables. *The job imports data from multiple tables, from 4 Oracle 9i *databases, and 1 Oracle 10g database. *The job runs via job scheduler, and fails when it comes to the last job, which is to import the data from the Oracle 10g database. *I can run this job manually, and it works. The first 4 steps import the data from the 9i databases, and runs fine. *I cannot figure out why the last job fails. *The first thingI thought was that it might be a permissions issue on the SQL server, but all the jobs run under the same ID. *At this point the only thing I can think of is it a 9i / 10g problem? *If it is, why then would I be able to run the job manually, and the data is imported without any errors. I appreciate any ideas. Regards, Darryl. |
I ended up creating a new Business Intelligence project, and imported
a single table from the Oracle database. This worked fine, so it
ruled out Oracle as being the issue.
I then again created a new project, and imported the existing SSIS job
from the dtsx file. This job also ran fine after setting it up on a
schedule. The only difference I could see is that the job that failed
was referencing the package from a SQL repository, not a file system,
like mine.
Either way, it now works.
Darryl.
#12
| |||
| |||
|
|
Hello Darryl: Yes, it sure sounds like an Oracle issue. When you say you can run it manually, and yet it fails when schedulsed, can you give us more details as to what machine each of these operations is performed on? By "manually" do you mean your local development desktop, running in the BIDS Development Environment? Does "scheduled" mean it is trying to run on a server? Have you tried executing the package from the server by using SSMS connected to the SSIS instance on the server? (Right-click the package and select Execute). What kind of info are you seeing in the error messages and logs? HTH -- Todd C [If this response was helpful, please indicate by clicking the appropriate answer at the bottom] "DB" wrote: I have an SSIS job, SQL 2005 SP2, Windows Server 2003, that imports data from multiple databases into local SQL tables. *The job imports data from multiple tables, from 4 Oracle 9i *databases, and 1 Oracle 10g database. *The job runs via job scheduler, and fails when it comes to the last job, which is to import the data from the Oracle 10g database. *I can run this job manually, and it works. The first 4 steps import the data from the 9i databases, and runs fine. *I cannot figure out why the last job fails. *The first thingI thought was that it might be a permissions issue on the SQL server, but all the jobs run under the same ID. *At this point the only thing I can think of is it a 9i / 10g problem? *If it is, why then would I be able to run the job manually, and the data is imported without any errors. I appreciate any ideas. Regards, Darryl. |
I ended up creating a new Business Intelligence project, and imported
a single table from the Oracle database. This worked fine, so it
ruled out Oracle as being the issue.
I then again created a new project, and imported the existing SSIS job
from the dtsx file. This job also ran fine after setting it up on a
schedule. The only difference I could see is that the job that failed
was referencing the package from a SQL repository, not a file system,
like mine.
Either way, it now works.
Darryl.
#13
| |||
| |||
|
|
Hello Darryl: Yes, it sure sounds like an Oracle issue. When you say you can run it manually, and yet it fails when schedulsed, can you give us more details as to what machine each of these operations is performed on? By "manually" do you mean your local development desktop, running in the BIDS Development Environment? Does "scheduled" mean it is trying to run on a server? Have you tried executing the package from the server by using SSMS connected to the SSIS instance on the server? (Right-click the package and select Execute). What kind of info are you seeing in the error messages and logs? HTH -- Todd C [If this response was helpful, please indicate by clicking the appropriate answer at the bottom] "DB" wrote: I have an SSIS job, SQL 2005 SP2, Windows Server 2003, that imports data from multiple databases into local SQL tables. *The job imports data from multiple tables, from 4 Oracle 9i *databases, and 1 Oracle 10g database. *The job runs via job scheduler, and fails when it comes to the last job, which is to import the data from the Oracle 10g database. *I can run this job manually, and it works. The first 4 steps import the data from the 9i databases, and runs fine. *I cannot figure out why the last job fails. *The first thingI thought was that it might be a permissions issue on the SQL server, but all the jobs run under the same ID. *At this point the only thing I can think of is it a 9i / 10g problem? *If it is, why then would I be able to run the job manually, and the data is imported without any errors. I appreciate any ideas. Regards, Darryl. |
I ended up creating a new Business Intelligence project, and imported
a single table from the Oracle database. This worked fine, so it
ruled out Oracle as being the issue.
I then again created a new project, and imported the existing SSIS job
from the dtsx file. This job also ran fine after setting it up on a
schedule. The only difference I could see is that the job that failed
was referencing the package from a SQL repository, not a file system,
like mine.
Either way, it now works.
Darryl.
#14
| |||
| |||
|
|
Hello Darryl: Yes, it sure sounds like an Oracle issue. When you say you can run it manually, and yet it fails when schedulsed, can you give us more details as to what machine each of these operations is performed on? By "manually" do you mean your local development desktop, running in the BIDS Development Environment? Does "scheduled" mean it is trying to run on a server? Have you tried executing the package from the server by using SSMS connected to the SSIS instance on the server? (Right-click the package and select Execute). What kind of info are you seeing in the error messages and logs? HTH -- Todd C [If this response was helpful, please indicate by clicking the appropriate answer at the bottom] "DB" wrote: I have an SSIS job, SQL 2005 SP2, Windows Server 2003, that imports data from multiple databases into local SQL tables. *The job imports data from multiple tables, from 4 Oracle 9i *databases, and 1 Oracle 10g database. *The job runs via job scheduler, and fails when it comes to the last job, which is to import the data from the Oracle 10g database. *I can run this job manually, and it works. The first 4 steps import the data from the 9i databases, and runs fine. *I cannot figure out why the last job fails. *The first thingI thought was that it might be a permissions issue on the SQL server, but all the jobs run under the same ID. *At this point the only thing I can think of is it a 9i / 10g problem? *If it is, why then would I be able to run the job manually, and the data is imported without any errors. I appreciate any ideas. Regards, Darryl. |
I ended up creating a new Business Intelligence project, and imported
a single table from the Oracle database. This worked fine, so it
ruled out Oracle as being the issue.
I then again created a new project, and imported the existing SSIS job
from the dtsx file. This job also ran fine after setting it up on a
schedule. The only difference I could see is that the job that failed
was referencing the package from a SQL repository, not a file system,
like mine.
Either way, it now works.
Darryl.
#15
| |||
| |||
|
|
Hello Darryl: Yes, it sure sounds like an Oracle issue. When you say you can run it manually, and yet it fails when schedulsed, can you give us more details as to what machine each of these operations is performed on? By "manually" do you mean your local development desktop, running in the BIDS Development Environment? Does "scheduled" mean it is trying to run on a server? Have you tried executing the package from the server by using SSMS connected to the SSIS instance on the server? (Right-click the package and select Execute). What kind of info are you seeing in the error messages and logs? HTH -- Todd C [If this response was helpful, please indicate by clicking the appropriate answer at the bottom] "DB" wrote: I have an SSIS job, SQL 2005 SP2, Windows Server 2003, that imports data from multiple databases into local SQL tables. *The job imports data from multiple tables, from 4 Oracle 9i *databases, and 1 Oracle 10g database. *The job runs via job scheduler, and fails when it comes to the last job, which is to import the data from the Oracle 10g database. *I can run this job manually, and it works. The first 4 steps import the data from the 9i databases, and runs fine. *I cannot figure out why the last job fails. *The first thingI thought was that it might be a permissions issue on the SQL server, but all the jobs run under the same ID. *At this point the only thing I can think of is it a 9i / 10g problem? *If it is, why then would I be able to run the job manually, and the data is imported without any errors. I appreciate any ideas. Regards, Darryl. |
I ended up creating a new Business Intelligence project, and imported
a single table from the Oracle database. This worked fine, so it
ruled out Oracle as being the issue.
I then again created a new project, and imported the existing SSIS job
from the dtsx file. This job also ran fine after setting it up on a
schedule. The only difference I could see is that the job that failed
was referencing the package from a SQL repository, not a file system,
like mine.
Either way, it now works.
Darryl.
#16
| |||
| |||
|
|
Hello Darryl: Yes, it sure sounds like an Oracle issue. When you say you can run it manually, and yet it fails when schedulsed, can you give us more details as to what machine each of these operations is performed on? By "manually" do you mean your local development desktop, running in the BIDS Development Environment? Does "scheduled" mean it is trying to run on a server? Have you tried executing the package from the server by using SSMS connected to the SSIS instance on the server? (Right-click the package and select Execute). What kind of info are you seeing in the error messages and logs? HTH -- Todd C [If this response was helpful, please indicate by clicking the appropriate answer at the bottom] "DB" wrote: I have an SSIS job, SQL 2005 SP2, Windows Server 2003, that imports data from multiple databases into local SQL tables. *The job imports data from multiple tables, from 4 Oracle 9i *databases, and 1 Oracle 10g database. *The job runs via job scheduler, and fails when it comes to the last job, which is to import the data from the Oracle 10g database. *I can run this job manually, and it works. The first 4 steps import the data from the 9i databases, and runs fine. *I cannot figure out why the last job fails. *The first thingI thought was that it might be a permissions issue on the SQL server, but all the jobs run under the same ID. *At this point the only thing I can think of is it a 9i / 10g problem? *If it is, why then would I be able to run the job manually, and the data is imported without any errors. I appreciate any ideas. Regards, Darryl. |
I ended up creating a new Business Intelligence project, and imported
a single table from the Oracle database. This worked fine, so it
ruled out Oracle as being the issue.
I then again created a new project, and imported the existing SSIS job
from the dtsx file. This job also ran fine after setting it up on a
schedule. The only difference I could see is that the job that failed
was referencing the package from a SQL repository, not a file system,
like mine.
Either way, it now works.
Darryl.
#17
| |||
| |||
|
|
Hello Darryl: Yes, it sure sounds like an Oracle issue. When you say you can run it manually, and yet it fails when schedulsed, can you give us more details as to what machine each of these operations is performed on? By "manually" do you mean your local development desktop, running in the BIDS Development Environment? Does "scheduled" mean it is trying to run on a server? Have you tried executing the package from the server by using SSMS connected to the SSIS instance on the server? (Right-click the package and select Execute). What kind of info are you seeing in the error messages and logs? HTH -- Todd C [If this response was helpful, please indicate by clicking the appropriate answer at the bottom] "DB" wrote: I have an SSIS job, SQL 2005 SP2, Windows Server 2003, that imports data from multiple databases into local SQL tables. *The job imports data from multiple tables, from 4 Oracle 9i *databases, and 1 Oracle 10g database. *The job runs via job scheduler, and fails when it comes to the last job, which is to import the data from the Oracle 10g database. *I can run this job manually, and it works. The first 4 steps import the data from the 9i databases, and runs fine. *I cannot figure out why the last job fails. *The first thingI thought was that it might be a permissions issue on the SQL server, but all the jobs run under the same ID. *At this point the only thing I can think of is it a 9i / 10g problem? *If it is, why then would I be able to run the job manually, and the data is imported without any errors. I appreciate any ideas. Regards, Darryl. |
I ended up creating a new Business Intelligence project, and imported
a single table from the Oracle database. This worked fine, so it
ruled out Oracle as being the issue.
I then again created a new project, and imported the existing SSIS job
from the dtsx file. This job also ran fine after setting it up on a
schedule. The only difference I could see is that the job that failed
was referencing the package from a SQL repository, not a file system,
like mine.
Either way, it now works.
Darryl.
|
« Previous Thread
|
Next Thread »
| Thread Tools | |
| Display Modes | |
Linear Mode
| |
Powered by vBulletin Version 3.5.3
Copyright ©2000 - 2012, Jelsoft Enterprises Ltd.
Copyright ©2000 - 2012, Jelsoft Enterprises Ltd.