Sunday, March 11, 2012

Error in OLE DB Command task

Hi all,

After applying the SP2 for Korean - we are getting the following error in the above task.

Transfer Fact Data From StagingDB to Presentation DB: Insert Update MetricFact [1021]: An OLE DB error has occurred. Error code: 0x80004005. An OLE DB record is available. Source: "Microsoft OLE DB Provider for SQL Server" Hresult: 0x80004005 Description: "'OPTIMIZE' ? ? ?.".

Not sure what the problem is. The same task was running properly before applying the SP2.

For other language SP2 (on other languages) the same task runs correctly and without any error.

sachin.dubey wrote:

Hi all,

After applying the SP2 for Korean - we are getting the following error in the above task.

Transfer Fact Data From StagingDB to Presentation DB: Insert Update MetricFact [1021]: An OLE DB error has occurred. Error code: 0x80004005. An OLE DB record is available. Source: "Microsoft OLE DB Provider for SQL Server" Hresult: 0x80004005 Description: "'OPTIMIZE' ? ? ?.".

Not sure what the problem is. The same task was running properly before applying the SP2.

For other language SP2 (on other languages) the same task runs correctly and without any error.

Hmmm... strange.

Can you run SQL Server Profiler to see what is getting executed against SQL Server?

-Jamie

|||

I m getting the error at design time also when the Package is opened in BI studio

when i tried using Profiler

it executes exec sp_procedure_params_rowset in backend

and throws following error

???102, ??15, ??1, ????sp_procedure_params_rowset, ?151

'OPTIMIZE' ?????????????.

|||

sachin.dubey wrote:

I m getting the error at design time also when the Package is opened in BI studio

when i tried using Profiler

it executes exec sp_procedure_params_rowset in backend

and throws following error

???102, ??15, ??1, ????sp_procedure_params_rowset, ?151

'OPTIMIZE' ?????????????.

It sounds as though the problem might be outside of SSIS. Try and isolate the problem in SQL Server.

-Jamie

|||

Hmm Thanks Jamie.

I will try there.

No comments:

Post a Comment