Problem starting package using the Agent

Question

Post reply

Problem starting package using the Agent

Viewing 11 posts - 1 through 12 (of 12 total)

You must be logged in to reply to this topic. Login to reply

Koen Verbeeck SSC Guru Points: 259197 More actions · Answer 1

I'm certainly not an Oracle expert, but I have found the following topic:

http://forums.oracle.com/forums/thread.jspa?threadID=327112

Maybe the last reply can be useful?

Need an answer? No, you need a question
My blog at https://sqlkover.com.
MCSE Business Intelligence - Microsoft Data Platform MVP

cgrigolini Mr or Mrs. 500 Points: 595 More actions · Answer 2

Thank you, but it doesn't help.

My package is a very simple one, only for architecture test purpose.

So there's no functional problem, and it actually works if I launch it manually (in BIDS and in SSIS).

The problem arises when I schedule it in the Sql Server Agent.

I have tried changing the Agent service account, but it doesn't help.

Desesperating...

Thank you in advance for any new idea

carlo

Koen Verbeeck SSC Guru Points: 259197 More actions · Answer 3

Are you 100% sure that all the configurations come through correctly when executed from SQL Server Agent?

Maybe you can quickly add a task in the package that writes all the configuration settings to a file, so that you can manually check if everything is configured OK.

Need an answer? No, you need a question
My blog at https://sqlkover.com.
MCSE Business Intelligence - Microsoft Data Platform MVP

cgrigolini Mr or Mrs. 500 Points: 595 More actions · Answer 4

I agree, that could be the point. Could you explain me how to write to a file the configuration details?

Thank you very much

carlo

Koen Verbeeck SSC Guru Points: 259197 More actions · Answer 5

Well, you could store the used configurations in string variables and then write the values of those variables to a text file using a script task.

Or, you can store the values of those variables in a temporary table using an Execute SQL Task.

Need an answer? No, you need a question
My blog at https://sqlkover.com.
MCSE Business Intelligence - Microsoft Data Platform MVP

cgrigolini Mr or Mrs. 500 Points: 595 More actions · Answer 6

cgrigolini

Mr or Mrs. 500

Points: 595

November 16, 2010 at 11:29 pm

#1251697

I'll go throw it today an tell you...

cgrigolini Mr or Mrs. 500 Points: 595 More actions · Answer 7

I wrote the username variable (executing the package) into a table, and it shows: ada\administrator

Which other information would I need to know?

No idea at the moment

thank you

carlo

cgrigolini Mr or Mrs. 500 Points: 595 More actions · Answer 8

I'm realizing this section is on sql server 2005, but I'm actually using sql server 2008 R2 64 bits

cgrigolini Mr or Mrs. 500 Points: 595 More actions · Answer 9

Ok, solved in two steps:

- use "Ole BD for Oracle" instead of "ODBC"

- check “Use 32 bit runtime” in step execution option

Thank you

Carlo

Koen Verbeeck SSC Guru Points: 259197 More actions · Answer 10

Glad that you solved the problem.

Why was the 32-bit option necessary?

Need an answer? No, you need a question
My blog at https://sqlkover.com.
MCSE Business Intelligence - Microsoft Data Platform MVP

cgrigolini Mr or Mrs. 500 Points: 595 More actions · Answer 11

The Oracle DB is 32 bit.

When I was using ODBC, I was able to choose for the 32bit System DSN (with odbcad32.exe located in %Windows%\SystemWOW64\ ).

And, anyway, checking that option didn't solve the problem.

Now, using OLE DB, I can't choose betwen 32 or 64. So I thought again about checking that option. And that made it work.

Carlo