Showing posts with label source. Show all posts
Showing posts with label source. Show all posts

Thursday, March 29, 2012

Error loading report

I have created many crystal reports within VB.Net that are based upon an *.xsd file as the report source is dynamic. This works fine on the machine they were developed on. However I now wish to roll out the final solution and store the reports on a shared network drive whilst the VB app is on each desktop. I have tried copying the *.rpt file to the shared drive along with the *.xsd files. I even changed each report to now look at the *.xsd in the new location. However when I try to open a report I get the following error:

Error in file e:\directory\report.rpt.
Failed to load database information.

Any ideas.?

ThanksMake sure it is pointing the correct database|||Check if proper DSN is created and Verify the Database in the report at design time.|||With e:\ being the network drive my report e:\myreport.rpt is pointing to e:\myreport.xsd

which is correct as far as I know.|||Have ttried changing network paths to UNC, no joy.

Strangely, if I load the project within VB.Net, the app and the reports run fine. But when I run the installed package I get this error. This makes me think that maybe I need to package up some additional files with the app.?

Monday, March 26, 2012

Error Including null value in a Numeric field

Hi All,

I'm migrating some SQL 2000 DTS to SSIS.

I am transfering data from a DB2 table to a SQL 2005 table using the OLE DB Source, Data Converstion then the OLE DB Destionation.

So, I have a numeric (Precision 3, Scale 2) field with NULL value in the DB2 table.

I'm trying to transfer these data to a SQL2005 table and I am receiving this error message below:

"[Destination Table TFACIL [18]] Error: There was an error with input column "COMB_OPPT_PRCT" (2865) on input "OLE DB Destination Input" (31). The column status returned was: "The value violated the integrity constraints for the column.". "

The field must accept null because of the APPLICATION ( i can't change it, im not the owner ).

Could someone help me?

Thanks in advance.

Regards,

Thiago

Check that the SQL table TFACIL.COMB_OPPT_PRCT

1) Has no CHECK constraints on it that would prevent NULL being loaded

2) is not defined as NOT NULL

Wednesday, March 21, 2012

error in ssis package!

Hi,

[OLE DB Destination [1146]] Error: An OLE DB error has occurred. Error code: 0x80040E23. An OLE DB record is available. Source: "Microsoft OLE DB Provider for SQL Server" Hresult: 0x80040E23 Description: "Cursor operation conflict".

[DTS.Pipeline] Error: The ProcessInput method on component "OLE DB Destination" (1146) failed with error code 0xC0202009. The identified component returned an error from the ProcessInput method. The error is specific to the component, but the error is fatal and will cause the Data Flow task to stop running.

[DTS.Pipeline] Error: Thread "WorkThread0" has exited with error code 0xC0202009.

have any of u encountered this error?

package is working good on source side but destination is indicated in red with the above error,it was working good yesterday,not sure what happened today all of a sudden.

pls help!

Regards,

sg

That's an error returned from SQL Server so I would suggest the problem is in SQL Server rather than SSIS. That's not much help I know but hopefully it gives you some pointes about where to to investigate.

Google turned these up:

http://blogs.conchango.com/kristianwedberg/archive/2006/03/08/3045.aspx (from my friend and fellow Conchango-ite Kristian Wedberg)

http://support.microsoft.com/default.aspx/kb/324900

-Jmie

|||

Hi jamie,

Thanks a lot,ur information was valuable.The package is working.

|||

Cool. If it proved to answer your problem, please could you mark it as an answer.

Thanks.

sql

Wednesday, March 7, 2012

Error in inserting value by trigger in linked server

Hi Pls help me
I have 2 db servers and its a lnked server
while am inserting value in source table (table having a trigger to raise ti
other table in defferent server) i am facing this error and Data is not
getting inserted.
error is
- Unable to preserve trigger 'InsertIntoHPD_HelpDesk'.
ODBC error: [Microsoft][ODBC SQL Server Driver][SQL Server]The operation
could not be performed because the OLE DB provider 'SQLOLEDB' was unable to
begin a distributed transaction.
[Microsoft][ODBC SQL Server Driver][SQL Server][OLE/DB provider returned
message: New transaction cannot enlist in the specified transaction
coordinator. ]
regards
KRP
Do you have the Distributed Transaction Coordinator running? On SQL Server
2000 it is one of the services in the SQL Server suite along with SQL Server
and SQL Agent.
RLF
"KRP" <KRP @.discussions.microsoft.com> wrote in message
news:8C37B85A-951E-414C-A6BA-9D7BBFC039D0@.microsoft.com...
> Hi Pls help me
> I have 2 db servers and its a lnked server
> while am inserting value in source table (table having a trigger to raise
> ti
> other table in defferent server) i am facing this error and Data is not
> getting inserted.
> error is
> - Unable to preserve trigger 'InsertIntoHPD_HelpDesk'.
> ODBC error: [Microsoft][ODBC SQL Server Driver][SQL Server]The operation
> could not be performed because the OLE DB provider 'SQLOLEDB' was unable
> to
> begin a distributed transaction.
> [Microsoft][ODBC SQL Server Driver][SQL Server][OLE/DB provider returned
> message: New transaction cannot enlist in the specified transaction
> coordinator. ]
> regards
> KRP
|||Yes,
Its already started and every pre conf hasbeen done..
Please Can you send me a steps of creating a linked server?
Thanks
KRp
"Russell Fields" wrote:

> Do you have the Distributed Transaction Coordinator running? On SQL Server
> 2000 it is one of the services in the SQL Server suite along with SQL Server
> and SQL Agent.
> RLF
> "KRP" <KRP @.discussions.microsoft.com> wrote in message
> news:8C37B85A-951E-414C-A6BA-9D7BBFC039D0@.microsoft.com...
>
>

Error in inserting value by trigger in linked server

Hi Pls help me
I have 2 db servers and its a lnked server
while am inserting value in source table (table having a trigger to raise ti
other table in defferent server) i am facing this error and Data is not
getting inserted.
error is
- Unable to preserve trigger 'InsertIntoHPD_HelpDesk'.
ODBC error: [Microsoft][ODBC SQL Server Driver][SQL Server]The o
peration
could not be performed because the OLE DB provider 'SQLOLEDB' was unable to
begin a distributed transaction.
[Microsoft][ODBC SQL Server Driver][SQL Server][OLE/DB provi
der returned
message: New transaction cannot enlist in the specified transaction
coordinator. ]
regards
KRPDo you have the Distributed Transaction Coordinator running? On SQL Server
2000 it is one of the services in the SQL Server suite along with SQL Server
and SQL Agent.
RLF
"KRP" <KRP @.discussions.microsoft.com> wrote in message
news:8C37B85A-951E-414C-A6BA-9D7BBFC039D0@.microsoft.com...
> Hi Pls help me
> I have 2 db servers and its a lnked server
> while am inserting value in source table (table having a trigger to raise
> ti
> other table in defferent server) i am facing this error and Data is not
> getting inserted.
> error is
> - Unable to preserve trigger 'InsertIntoHPD_HelpDesk'.
> ODBC error: [Microsoft][ODBC SQL Server Driver][SQL Server]The
operation
> could not be performed because the OLE DB provider 'SQLOLEDB' was unable
> to
> begin a distributed transaction.
> [Microsoft][ODBC SQL Server Driver][SQL Server][OLE/DB pro
vider returned
> message: New transaction cannot enlist in the specified transaction
> coordinator. ]
> regards
> KRP|||Yes,
Its already started and every pre conf hasbeen done..
Please Can you send me a steps of creating a linked server?
Thanks
KRp
"Russell Fields" wrote:

> Do you have the Distributed Transaction Coordinator running? On SQL Serve
r
> 2000 it is one of the services in the SQL Server suite along with SQL Serv
er
> and SQL Agent.
> RLF
> "KRP" <KRP @.discussions.microsoft.com> wrote in message
> news:8C37B85A-951E-414C-A6BA-9D7BBFC039D0@.microsoft.com...
>
>

Error in inserting value by trigger in linked server

Hi Pls help me
I have 2 db servers and its a lnked server
while am inserting value in source table (table having a trigger to raise ti
other table in defferent server) i am facing this error and Data is not
getting inserted.
error is
- Unable to preserve trigger 'InsertIntoHPD_HelpDesk'.
ODBC error: [Microsoft][ODBC SQL Server Driver][SQL Server]The operation
could not be performed because the OLE DB provider 'SQLOLEDB' was unable to
begin a distributed transaction.
[Microsoft][ODBC SQL Server Driver][SQL Server][OLE/DB provider returned
message: New transaction cannot enlist in the specified transaction
coordinator. ]
regards
KRPDo you have the Distributed Transaction Coordinator running? On SQL Server
2000 it is one of the services in the SQL Server suite along with SQL Server
and SQL Agent.
RLF
"KRP" <KRP @.discussions.microsoft.com> wrote in message
news:8C37B85A-951E-414C-A6BA-9D7BBFC039D0@.microsoft.com...
> Hi Pls help me
> I have 2 db servers and its a lnked server
> while am inserting value in source table (table having a trigger to raise
> ti
> other table in defferent server) i am facing this error and Data is not
> getting inserted.
> error is
> - Unable to preserve trigger 'InsertIntoHPD_HelpDesk'.
> ODBC error: [Microsoft][ODBC SQL Server Driver][SQL Server]The operation
> could not be performed because the OLE DB provider 'SQLOLEDB' was unable
> to
> begin a distributed transaction.
> [Microsoft][ODBC SQL Server Driver][SQL Server][OLE/DB provider returned
> message: New transaction cannot enlist in the specified transaction
> coordinator. ]
> regards
> KRP|||Yes,
Its already started and every pre conf hasbeen done..
Please Can you send me a steps of creating a linked server?
Thanks
KRp
"Russell Fields" wrote:
> Do you have the Distributed Transaction Coordinator running? On SQL Server
> 2000 it is one of the services in the SQL Server suite along with SQL Server
> and SQL Agent.
> RLF
> "KRP" <KRP @.discussions.microsoft.com> wrote in message
> news:8C37B85A-951E-414C-A6BA-9D7BBFC039D0@.microsoft.com...
> > Hi Pls help me
> >
> > I have 2 db servers and its a lnked server
> > while am inserting value in source table (table having a trigger to raise
> > ti
> > other table in defferent server) i am facing this error and Data is not
> > getting inserted.
> > error is
> > - Unable to preserve trigger 'InsertIntoHPD_HelpDesk'.
> > ODBC error: [Microsoft][ODBC SQL Server Driver][SQL Server]The operation
> > could not be performed because the OLE DB provider 'SQLOLEDB' was unable
> > to
> > begin a distributed transaction.
> > [Microsoft][ODBC SQL Server Driver][SQL Server][OLE/DB provider returned
> > message: New transaction cannot enlist in the specified transaction
> > coordinator. ]
> >
> > regards
> > KRP
>
>

Sunday, February 26, 2012

Error in execute a scheduled package

I'm learning SSIS and ran into this error...

I have a package that has its source as an Oracle DB on another server. This package will feed data from that source to a SQL Server 2005 DB. So far, the package works fine if it is executed manually even in SQL Mgmt Studio. It's only failed when I tried it as a scheduled job. I guess I need to do "Package Configurations" which includes the UserID and password for accessing Oracle DB ... but I don't know how. Please help.

Regards,

dnncpt

-

Here is the error message:

Date,Source,Severity,Step ID,Server,Job Name,Step Name,Notifications,Message,Duration,Sql Severity,Sql Message ID,Operator Emailed,Operator Net sent,Operator Paged,Retries Attempted
05/08/2007 09:49:00,DataFeed,Error,0,<MyDBServer>,DataFeed,(Job outcome),,The job failed. The Job was invoked by Schedule 8 (Schedule DataFeed Grant Tables). The last step to run was step 1 (DataFeed Grant Tables).,00:00:02,0,0,,,,0
05/08/2007 09:49:00,DataFeed,Error,1,<MyDBServer>,DataFeed,DataFeed Grant Tables,,Executed as user: <MyDBServer>\SYSTEM. ....3042.00 for 32-bit Copyright (C) Microsoft Corp 1984-2005. All rights reserved. Started: 9:49:00 AM Error: 2007-05-08 09:49:00.81 Code: 0xC0016016 Source: Description: Failed to decrypt protected XML node "DTSStick out tongueassword" with error 0x8009000B "Key not valid for use in specified state.". You may not be authorized to access this information. This error occurs when there is a cryptographic error. Verify that the correct key is available. End Error Error: 2007-05-08 09:49:01.86 Code: 0xC0202009 Source: AWARDS Connection manager "SourceConnectionOLEDB" Description: SSIS Error Code DTS_E_OLEDBERROR. An OLE DB error has occurred. Error code: 0x80004005. An OLE DB record is available. Source: "OraOLEDB" Hresult: 0x80004005 Description: "ORA-01005: null password given; logon denied". End Error Error: 2007-05-08 09:49:01.86 Code: 0xC020801C Source: Feed data t... The package execution fa... The step failed.,00:00:02,0,0,,,,0

For the error, I think this link may be the answer:

http://support.microsoft.com/default.aspx?scid=kb%3ben-us%3b904800

So the protection level is the reason.

I really love the Microsoft technologies but if MS could provide such a nice software like SQL Server and SSIS why its tech teams don't go a further step as to provide a good how-to document for each application. This could benefit for both MS and its customers. (hope Mr. Gates or Mr. Ballmer read this)

Regards,

dnncpt

Error In Event Viewer

Hi I am getting the following error:

Event Type: Error
Event Source: MSSQLSERVER
Event Category: (2)
Event ID: 17052
Date: 4/14/2004
Time: 09:32:05 AM
User: SYSTEM
Computer: BSEW2k01
Description:
Error: 50000, Severity: 5, State: 1
Error Calling StatusToStreet In DCS0 Code 7202

Please help.

ThanksThe error doesn't seems to be a system generated as its a user-defined from the application, check the vendor for that application.|||And I would venture to say that

StatusToStreet

Is the sproc and

DCS0

Is the database

Sunday, February 19, 2012

Error In Application Logs

hii...
I am using SQL 2000 With sp3a on win200server.
i am getting following error in application log.
Event Type: Error
Event Source: MSSQLSERVER
Event Category: (2)
Event ID: 17052
Date: 10/31/2003
Time: 3:52:54 PM
User: N/A
Computer: BNET8
Description:
Error: 17832, Severity: 20, State: 8
Connection opened but invalid login packet(s) sent. Connection closed. Data:
0000: a8 45 00 00 14 00 00 00 =A8E.....
0008: 06 00 00 00 42 00 4e 00 ...B.N.
0010: 45 00 54 00 38 00 00 00 E.T.8...
0018: 00 00 00 00 ...
Please explain? what is this and solution.
Thanks in advanceHi ,
The error (17832) do not indicate a problem with SQL Server, but rather a
network failure, or client application problem.
17832 can happen if a client starts to connect, but never successfully
completes the attempt.
Normally this error is caused by the network failing between the time a
connection attempt is initiated, and when it completes.
You can just ignore this error incase the occurance of this error is
limited. Incase if the occurance is higher please check with your network
services.
Thanks
Hari
MCDBA
"sandi" <anonymous@.discussions.microsoft.com> wrote in message
news:057a01c3a026$9171c6a0$a301280a@.phx.gbl...
hii...
I am using SQL 2000 With sp3a on win200server.
i am getting following error in application log.
Event Type: Error
Event Source: MSSQLSERVER
Event Category: (2)
Event ID: 17052
Date: 10/31/2003
Time: 3:52:54 PM
User: N/A
Computer: BNET8
Description:
Error: 17832, Severity: 20, State: 8
Connection opened but invalid login packet(s) sent.
Connection closed.
Data:
0000: a8 45 00 00 14 00 00 00 ¨E.....
0008: 06 00 00 00 42 00 4e 00 ...B.N.
0010: 45 00 54 00 38 00 00 00 E.T.8...
0018: 00 00 00 00 ...
Please explain? what is this and solution.
Thanks in advance|||Dear Hari,
Thanks for your help.
sandi
>--Original Message--
>Hi ,
>The error (17832) do not indicate a problem with SQL Server, but rather a
>network failure, or client application problem.
>17832 can happen if a client starts to connect, but never successfully
>completes the attempt.
>Normally this error is caused by the network failing between the time a
>connection attempt is initiated, and when it completes.
>You can just ignore this error incase the occurance of this error is
>limited. Incase if the occurance is higher please check with your network
>services.
>Thanks
>Hari
>MCDBA
>"sandi" <anonymous@.discussions.microsoft.com> wrote in message
>news:057a01c3a026$9171c6a0$a301280a@.phx.gbl...
>hii...
>I am using SQL 2000 With sp3a on win200server.
>i am getting following error in application log.
>Event Type: Error
>Event Source: MSSQLSERVER
>Event Category: (2)
>Event ID: 17052
>Date: 10/31/2003
>Time: 3:52:54 PM
>User: N/A
>Computer: BNET8
>Description:
>Error: 17832, Severity: 20, State: 8
>Connection opened but invalid login packet(s) sent.
>Connection closed.
>Data:
>0000: a8 45 00 00 14 00 00 00 =A8E.....
>0008: 06 00 00 00 42 00 4e 00 ...B.N.
>0010: 45 00 54 00 38 00 00 00 E.T.8...
>0018: 00 00 00 00 ...
>Please explain? what is this and solution.
>Thanks in advance
>
>.
>

Friday, February 17, 2012

Error importing data from oracle database to an SQL database

Hi!

When i was importing a database table from an Oracle Database to a SQL database table, the wizard returns this error:

Could not connect source component.

Warning 0x80202066: Source - VB_PERMISSIONS [1]: Cannot retrieve the column code page info from the OLE DB provider. If the component supports the "DefaultCodePage" property, the code page from that property will be used. Change the value of the property if the current string code page values are incorrect. If the component does not support the property, the code page from the component's locale ID will be used.

Error 0xc0204018: DTS.Pipeline: The "output column "PE_ACTIVE" (34)" has a precision that is not valid. The precision must be between 1 and 38.
(SQL Server Import and Export Wizard)

I tried to change the destination type field to others than the default (decimal), but noting works.

Anyone can help me please?

Thx a lot

Cristovao

I'm currently working on a project that pull data from an Oracle DB and have had not problems pulling data and loading it into SQL 2005.
As far as the codepage error, this occurs when you are pulling non-unicode string values from Oracle(and other DBs as well). SSIS cannot retrieve the CodePage (character set) used on the Oracle DB. To eliminate the warning (assuming Western Alphabet) just set the OLE DB Source to AlwaysUseDefaultCodePage to True. The DefaultCodePage should be set to 1252 which is correct for Western Alphabet. If Oracle is not using the Western Alphabet, you'll need to determine the charset used and use http://msdn.microsoft.com/library/default.asp?url=/workshop/database/tdc/reference/CharSet.asp to correctly set the default code page.
As far as the PE_ACTIVE output column error, I can't tell what the error is. If you let me know how field is defined in Oracle, I may be able to help you. Also what version of Oracle are you using?
Larry
|||Cristovao,

Could you tell us what is the source (Oracle) data type and precision and what is the suggested destination (SQL Server) type and precision?

Thanks.|||

Hi

Thx a lot for your answer.

I am sending to you the data that you asked me:

Type of the source fied: Number (1)
Suggested destination : Decimal (1)
Oracle version: 8.1.7
Best Regards,
Cristovao

|||The value 1 should be a valid precision.

Could you do another check for me? Please select the failing table on the Select Source Tables and Views" page and click "Edit..." on it. In the grid that shows up, find your "PE_ACTIVE" column and take a look at the values for Size, Precision and Scale.
There should be only the precision with the value 1.|||Hi Bob!

Thx again for your interest...

Yes, i have checked and in fact there are only the precision with the value 1, but the error occurs... Sad|||Well, it sounds intriguing.

Can you tell me what OLE DB driver you used; Microsoft OLE DB for Oracle or Oracle OLE DB?

I was able to copy a Number(1) column without any problem, using the MS driver.

Also, what version of SSIS do you have installed?
Thanks.|||

Hi Bob!

Well, i used the Oracle Provider For OLE DB... After have read your post i tried the Microsoft OLEDB Provider For Oracle, and the data have been imported, returning this warning:
TITLE: SQL Server Import and Export Wizard

Warning 0x80202066: Source - VB_PERMISSIONS [1]: Cannot retrieve the column code page info from the OLE DB provider. If the component supports the "DefaultCodePage" property, the code page from that property will be used. Change the value of the property if the current string code page values are incorrect. If the component does not support the property, the code page from the component's locale ID will be used.



BUTTONS:

OK
I suppose it is normal.

Thanks a lot for your help.

Best Regards,
Cristovao

|||I am glad you were able to make it work.

Yes, I believe this warning can be safely ignored in this case.|||Hi all!

Same problem that I had, but the problem was that Oracle did not have a size or scale specified. SSIS automatically treats all of there as numerics, and with no specification on the precision or scale, it blows up. I have found no way to set it, and have tried both the Microsoft and Oracle drivers. Nada!

The good news....just use a Data Reader connection with the .Net Oracle Client. Works like a champ!!!!!!!!

Scott|||

Larry_Pope wrote:


As far as the codepage error, this occurs when you are pulling non-unicode string values from Oracle(and other DBs as well). SSIS cannot retrieve the CodePage (character set) used on the Oracle DB. To eliminate the warning (assuming Western Alphabet) just set the OLE DB Source to AlwaysUseDefaultCodePage to True. The DefaultCodePage should be set to 1252 which is correct for Western Alphabet. If Oracle is not using the Western Alphabet, you'll need to determine the charset used and use http://msdn.microsoft.com/library/default.asp?url=/workshop/database/tdc/reference/CharSet.asp to correctly set the default code page.

Thanks for this Larry - AlwaysUseDefaultCodePage=TRUE worked a treat!

-Jamie|||Here is the latest issue I found. Some Oracle tables do not have a precision or scale assigned to the column when the type is set to NUMBER. This causes an error when using an OLEDB connection. Has anyone found a way to get around this? The DataReader does it fine, but I don't think it is as fast as the DataReader.

Thanks!

Scott Barrett|||Any luck on thos problem, Scott?|||Here is the issue. When using SSIS against Oracle 8i or any database imported from 8i, when a column was meant to be what we call an INT, they call NUMBER and do not set the precision or scale. Oracle 9i and up does this by default. This will cause SSIS to not be able to bring in data from those columns. So we now have two solutions: Use the Data Reader Source and your done, or use the OLE DB Source and only using the Advanced Editor, enter the source and manually create each output column manually. If you are pulling from a complete table instead of a query, you can manually change the datatype in the advanced editor to a DT_I4 and it will then work.

Hope this helps you out!

Scott Barrett
Moffitt Cancer Center
|||I have installed sql server 2005 evaluation version and have oracle 8i.
But I can't find OLE DB Source property of AlwaysUseDefaultCodePage to set it to True.
Can someone help me and show me directions.

Thanks,
Mitja

Error importing data from oracle database to an SQL database

Hi!

When i was importing a database table from an Oracle Database to a SQL database table, the wizard returns this error:

Could not connect source component.

Warning 0x80202066: Source - VB_PERMISSIONS [1]: Cannot retrieve the column code page info from the OLE DB provider. If the component supports the "DefaultCodePage" property, the code page from that property will be used. Change the value of the property if the current string code page values are incorrect. If the component does not support the property, the code page from the component's locale ID will be used.

Error 0xc0204018: DTS.Pipeline: The "output column "PE_ACTIVE" (34)" has a precision that is not valid. The precision must be between 1 and 38.
(SQL Server Import and Export Wizard)

I tried to change the destination type field to others than the default (decimal), but noting works.

Anyone can help me please?

Thx a lot

Cristovao

I'm currently working on a project that pull data from an Oracle DB and have had not problems pulling data and loading it into SQL 2005.
As far as the codepage error, this occurs when you are pulling non-unicode string values from Oracle(and other DBs as well). SSIS cannot retrieve the CodePage (character set) used on the Oracle DB. To eliminate the warning (assuming Western Alphabet) just set the OLE DB Source to AlwaysUseDefaultCodePage to True. The DefaultCodePage should be set to 1252 which is correct for Western Alphabet. If Oracle is not using the Western Alphabet, you'll need to determine the charset used and use http://msdn.microsoft.com/library/default.asp?url=/workshop/database/tdc/reference/CharSet.asp to correctly set the default code page.
As far as the PE_ACTIVE output column error, I can't tell what the error is. If you let me know how field is defined in Oracle, I may be able to help you. Also what version of Oracle are you using?
Larry|||Cristovao,

Could you tell us what is the source (Oracle) data type and precision and what is the suggested destination (SQL Server) type and precision?

Thanks.|||

Hi

Thx a lot for your answer.

I am sending to you the data that you asked me:

Type of the source fied: Number (1)
Suggested destination : Decimal (1)
Oracle version: 8.1.7
Best Regards,
Cristovao

|||The value 1 should be a valid precision.

Could you do another check for me? Please select the failing table on the Select Source Tables and Views" page and click "Edit..." on it. In the grid that shows up, find your "PE_ACTIVE" column and take a look at the values for Size, Precision and Scale.
There should be only the precision with the value 1.|||Hi Bob!

Thx again for your interest...

Yes, i have checked and in fact there are only the precision with the value 1, but the error occurs... Sad

|||Well, it sounds intriguing.

Can you tell me what OLE DB driver you used; Microsoft OLE DB for Oracle or Oracle OLE DB?

I was able to copy a Number(1) column without any problem, using the MS driver.

Also, what version of SSIS do you have installed?
Thanks.|||

Hi Bob!

Well, i used the Oracle Provider For OLE DB... After have read your post i tried the Microsoft OLEDB Provider For Oracle, and the data have been imported, returning this warning:
TITLE: SQL Server Import and Export Wizard

Warning 0x80202066: Source - VB_PERMISSIONS [1]: Cannot retrieve the column code page info from the OLE DB provider. If the component supports the "DefaultCodePage" property, the code page from that property will be used. Change the value of the property if the current string code page values are incorrect. If the component does not support the property, the code page from the component's locale ID will be used.



BUTTONS:

OK
I suppose it is normal.

Thanks a lot for your help.

Best Regards,
Cristovao

|||I am glad you were able to make it work.

Yes, I believe this warning can be safely ignored in this case.|||Hi all!

Same problem that I had, but the problem was that Oracle did not have a size or scale specified. SSIS automatically treats all of there as numerics, and with no specification on the precision or scale, it blows up. I have found no way to set it, and have tried both the Microsoft and Oracle drivers. Nada!

The good news....just use a Data Reader connection with the .Net Oracle Client. Works like a champ!!!!!!!!

Scott|||

Larry_Pope wrote:


As far as the codepage error, this occurs when you are pulling non-unicode string values from Oracle(and other DBs as well). SSIS cannot retrieve the CodePage (character set) used on the Oracle DB. To eliminate the warning (assuming Western Alphabet) just set the OLE DB Source to AlwaysUseDefaultCodePage to True. The DefaultCodePage should be set to 1252 which is correct for Western Alphabet. If Oracle is not using the Western Alphabet, you'll need to determine the charset used and use http://msdn.microsoft.com/library/default.asp?url=/workshop/database/tdc/reference/CharSet.asp to correctly set the default code page.

Thanks for this Larry - AlwaysUseDefaultCodePage=TRUE worked a treat!

-Jamie|||Here is the latest issue I found. Some Oracle tables do not have a precision or scale assigned to the column when the type is set to NUMBER. This causes an error when using an OLEDB connection. Has anyone found a way to get around this? The DataReader does it fine, but I don't think it is as fast as the DataReader.

Thanks!

Scott Barrett|||Any luck on thos problem, Scott?|||Here is the issue. When using SSIS against Oracle 8i or any database imported from 8i, when a column was meant to be what we call an INT, they call NUMBER and do not set the precision or scale. Oracle 9i and up does this by default. This will cause SSIS to not be able to bring in data from those columns. So we now have two solutions: Use the Data Reader Source and your done, or use the OLE DB Source and only using the Advanced Editor, enter the source and manually create each output column manually. If you are pulling from a complete table instead of a query, you can manually change the datatype in the advanced editor to a DT_I4 and it will then work.

Hope this helps you out!

Scott Barrett
Moffitt Cancer Center|||I have installed sql server 2005 evaluation version and have oracle 8i.
But I can't find OLE DB Source property of AlwaysUseDefaultCodePage to set it to True.
Can someone help me and show me directions.

Thanks,
Mitja

Error importing data from oracle database to an SQL database

Hi!

When i was importing a database table from an Oracle Database to a SQL database table, the wizard returns this error:

Could not connect source component.

Warning 0x80202066: Source - VB_PERMISSIONS [1]: Cannot retrieve the column code page info from the OLE DB provider. If the component supports the "DefaultCodePage" property, the code page from that property will be used. Change the value of the property if the current string code page values are incorrect. If the component does not support the property, the code page from the component's locale ID will be used.

Error 0xc0204018: DTS.Pipeline: The "output column "PE_ACTIVE" (34)" has a precision that is not valid. The precision must be between 1 and 38.
(SQL Server Import and Export Wizard)

I tried to change the destination type field to others than the default (decimal), but noting works.

Anyone can help me please?

Thx a lot

Cristovao

I'm currently working on a project that pull data from an Oracle DB and have had not problems pulling data and loading it into SQL 2005.
As far as the codepage error, this occurs when you are pulling non-unicode string values from Oracle(and other DBs as well). SSIS cannot retrieve the CodePage (character set) used on the Oracle DB. To eliminate the warning (assuming Western Alphabet) just set the OLE DB Source to AlwaysUseDefaultCodePage to True. The DefaultCodePage should be set to 1252 which is correct for Western Alphabet. If Oracle is not using the Western Alphabet, you'll need to determine the charset used and use http://msdn.microsoft.com/library/default.asp?url=/workshop/database/tdc/reference/CharSet.asp to correctly set the default code page.
As far as the PE_ACTIVE output column error, I can't tell what the error is. If you let me know how field is defined in Oracle, I may be able to help you. Also what version of Oracle are you using?
Larry|||Cristovao,

Could you tell us what is the source (Oracle) data type and precision and what is the suggested destination (SQL Server) type and precision?

Thanks.|||

Hi

Thx a lot for your answer.

I am sending to you the data that you asked me:

Type of the source fied: Number (1)
Suggested destination : Decimal (1)
Oracle version: 8.1.7
Best Regards,
Cristovao

|||The value 1 should be a valid precision.

Could you do another check for me? Please select the failing table on the Select Source Tables and Views" page and click "Edit..." on it. In the grid that shows up, find your "PE_ACTIVE" column and take a look at the values for Size, Precision and Scale.
There should be only the precision with the value 1.|||Hi Bob!

Thx again for your interest...

Yes, i have checked and in fact there are only the precision with the value 1, but the error occurs... Sad

|||Well, it sounds intriguing.

Can you tell me what OLE DB driver you used; Microsoft OLE DB for Oracle or Oracle OLE DB?

I was able to copy a Number(1) column without any problem, using the MS driver.

Also, what version of SSIS do you have installed?
Thanks.|||

Hi Bob!

Well, i used the Oracle Provider For OLE DB... After have read your post i tried the Microsoft OLEDB Provider For Oracle, and the data have been imported, returning this warning:
TITLE: SQL Server Import and Export Wizard

Warning 0x80202066: Source - VB_PERMISSIONS [1]: Cannot retrieve the column code page info from the OLE DB provider. If the component supports the "DefaultCodePage" property, the code page from that property will be used. Change the value of the property if the current string code page values are incorrect. If the component does not support the property, the code page from the component's locale ID will be used.



BUTTONS:

OK
I suppose it is normal.

Thanks a lot for your help.

Best Regards,
Cristovao

|||I am glad you were able to make it work.

Yes, I believe this warning can be safely ignored in this case.|||Hi all!

Same problem that I had, but the problem was that Oracle did not have a size or scale specified. SSIS automatically treats all of there as numerics, and with no specification on the precision or scale, it blows up. I have found no way to set it, and have tried both the Microsoft and Oracle drivers. Nada!

The good news....just use a Data Reader connection with the .Net Oracle Client. Works like a champ!!!!!!!!

Scott|||

Larry_Pope wrote:


As far as the codepage error, this occurs when you are pulling non-unicode string values from Oracle(and other DBs as well). SSIS cannot retrieve the CodePage (character set) used on the Oracle DB. To eliminate the warning (assuming Western Alphabet) just set the OLE DB Source to AlwaysUseDefaultCodePage to True. The DefaultCodePage should be set to 1252 which is correct for Western Alphabet. If Oracle is not using the Western Alphabet, you'll need to determine the charset used and use http://msdn.microsoft.com/library/default.asp?url=/workshop/database/tdc/reference/CharSet.asp to correctly set the default code page.

Thanks for this Larry - AlwaysUseDefaultCodePage=TRUE worked a treat!

-Jamie|||Here is the latest issue I found. Some Oracle tables do not have a precision or scale assigned to the column when the type is set to NUMBER. This causes an error when using an OLEDB connection. Has anyone found a way to get around this? The DataReader does it fine, but I don't think it is as fast as the DataReader.

Thanks!

Scott Barrett|||Any luck on thos problem, Scott?|||Here is the issue. When using SSIS against Oracle 8i or any database imported from 8i, when a column was meant to be what we call an INT, they call NUMBER and do not set the precision or scale. Oracle 9i and up does this by default. This will cause SSIS to not be able to bring in data from those columns. So we now have two solutions: Use the Data Reader Source and your done, or use the OLE DB Source and only using the Advanced Editor, enter the source and manually create each output column manually. If you are pulling from a complete table instead of a query, you can manually change the datatype in the advanced editor to a DT_I4 and it will then work.

Hope this helps you out!

Scott Barrett
Moffitt Cancer Center|||I have installed sql server 2005 evaluation version and have oracle 8i.
But I can't find OLE DB Source property of AlwaysUseDefaultCodePage to set it to True.
Can someone help me and show me directions.

Thanks,
Mitja

Error importing data from oracle database to an SQL database

Hi!

When i was importing a database table from an Oracle Database to a SQL database table, the wizard returns this error:

Could not connect source component.

Warning 0x80202066: Source - VB_PERMISSIONS [1]: Cannot retrieve the column code page info from the OLE DB provider. If the component supports the "DefaultCodePage" property, the code page from that property will be used. Change the value of the property if the current string code page values are incorrect. If the component does not support the property, the code page from the component's locale ID will be used.

Error 0xc0204018: DTS.Pipeline: The "output column "PE_ACTIVE" (34)" has a precision that is not valid. The precision must be between 1 and 38.
(SQL Server Import and Export Wizard)

I tried to change the destination type field to others than the default (decimal), but noting works.

Anyone can help me please?

Thx a lot

Cristovao

I'm currently working on a project that pull data from an Oracle DB and have had not problems pulling data and loading it into SQL 2005.
As far as the codepage error, this occurs when you are pulling non-unicode string values from Oracle(and other DBs as well). SSIS cannot retrieve the CodePage (character set) used on the Oracle DB. To eliminate the warning (assuming Western Alphabet) just set the OLE DB Source to AlwaysUseDefaultCodePage to True. The DefaultCodePage should be set to 1252 which is correct for Western Alphabet. If Oracle is not using the Western Alphabet, you'll need to determine the charset used and use http://msdn.microsoft.com/library/default.asp?url=/workshop/database/tdc/reference/CharSet.asp to correctly set the default code page.
As far as the PE_ACTIVE output column error, I can't tell what the error is. If you let me know how field is defined in Oracle, I may be able to help you. Also what version of Oracle are you using?
Larry|||Cristovao,

Could you tell us what is the source (Oracle) data type and precision and what is the suggested destination (SQL Server) type and precision?

Thanks.|||

Hi

Thx a lot for your answer.

I am sending to you the data that you asked me:

Type of the source fied: Number (1)
Suggested destination : Decimal (1)
Oracle version: 8.1.7
Best Regards,
Cristovao

|||The value 1 should be a valid precision.

Could you do another check for me? Please select the failing table on the Select Source Tables and Views" page and click "Edit..." on it. In the grid that shows up, find your "PE_ACTIVE" column and take a look at the values for Size, Precision and Scale.
There should be only the precision with the value 1.|||Hi Bob!

Thx again for your interest...

Yes, i have checked and in fact there are only the precision with the value 1, but the error occurs... Sad

|||Well, it sounds intriguing.

Can you tell me what OLE DB driver you used; Microsoft OLE DB for Oracle or Oracle OLE DB?

I was able to copy a Number(1) column without any problem, using the MS driver.

Also, what version of SSIS do you have installed?
Thanks.|||

Hi Bob!

Well, i used the Oracle Provider For OLE DB... After have read your post i tried the Microsoft OLEDB Provider For Oracle, and the data have been imported, returning this warning:
TITLE: SQL Server Import and Export Wizard

Warning 0x80202066: Source - VB_PERMISSIONS [1]: Cannot retrieve the column code page info from the OLE DB provider. If the component supports the "DefaultCodePage" property, the code page from that property will be used. Change the value of the property if the current string code page values are incorrect. If the component does not support the property, the code page from the component's locale ID will be used.



BUTTONS:

OK
I suppose it is normal.

Thanks a lot for your help.

Best Regards,
Cristovao

|||I am glad you were able to make it work.

Yes, I believe this warning can be safely ignored in this case.|||Hi all!

Same problem that I had, but the problem was that Oracle did not have a size or scale specified. SSIS automatically treats all of there as numerics, and with no specification on the precision or scale, it blows up. I have found no way to set it, and have tried both the Microsoft and Oracle drivers. Nada!

The good news....just use a Data Reader connection with the .Net Oracle Client. Works like a champ!!!!!!!!

Scott|||

Larry_Pope wrote:


As far as the codepage error, this occurs when you are pulling non-unicode string values from Oracle(and other DBs as well). SSIS cannot retrieve the CodePage (character set) used on the Oracle DB. To eliminate the warning (assuming Western Alphabet) just set the OLE DB Source to AlwaysUseDefaultCodePage to True. The DefaultCodePage should be set to 1252 which is correct for Western Alphabet. If Oracle is not using the Western Alphabet, you'll need to determine the charset used and use http://msdn.microsoft.com/library/default.asp?url=/workshop/database/tdc/reference/CharSet.asp to correctly set the default code page.

Thanks for this Larry - AlwaysUseDefaultCodePage=TRUE worked a treat!

-Jamie|||Here is the latest issue I found. Some Oracle tables do not have a precision or scale assigned to the column when the type is set to NUMBER. This causes an error when using an OLEDB connection. Has anyone found a way to get around this? The DataReader does it fine, but I don't think it is as fast as the DataReader.

Thanks!

Scott Barrett|||Any luck on thos problem, Scott?|||Here is the issue. When using SSIS against Oracle 8i or any database imported from 8i, when a column was meant to be what we call an INT, they call NUMBER and do not set the precision or scale. Oracle 9i and up does this by default. This will cause SSIS to not be able to bring in data from those columns. So we now have two solutions: Use the Data Reader Source and your done, or use the OLE DB Source and only using the Advanced Editor, enter the source and manually create each output column manually. If you are pulling from a complete table instead of a query, you can manually change the datatype in the advanced editor to a DT_I4 and it will then work.

Hope this helps you out!

Scott Barrett
Moffitt Cancer Center|||I have installed sql server 2005 evaluation version and have oracle 8i.
But I can't find OLE DB Source property of AlwaysUseDefaultCodePage to set it to True.
Can someone help me and show me directions.

Thanks,
Mitja

Error importing data from oracle database to an SQL database

Hi!

When i was importing a database table from an Oracle Database to a SQL database table, the wizard returns this error:

Could not connect source component.

Warning 0x80202066: Source - VB_PERMISSIONS [1]: Cannot retrieve the column code page info from the OLE DB provider. If the component supports the "DefaultCodePage" property, the code page from that property will be used. Change the value of the property if the current string code page values are incorrect. If the component does not support the property, the code page from the component's locale ID will be used.

Error 0xc0204018: DTS.Pipeline: The "output column "PE_ACTIVE" (34)" has a precision that is not valid. The precision must be between 1 and 38.
(SQL Server Import and Export Wizard)

I tried to change the destination type field to others than the default (decimal), but noting works.

Anyone can help me please?

Thx a lot

Cristovao

I'm currently working on a project that pull data from an Oracle DB and have had not problems pulling data and loading it into SQL 2005.
As far as the codepage error, this occurs when you are pulling non-unicode string values from Oracle(and other DBs as well). SSIS cannot retrieve the CodePage (character set) used on the Oracle DB. To eliminate the warning (assuming Western Alphabet) just set the OLE DB Source to AlwaysUseDefaultCodePage to True. The DefaultCodePage should be set to 1252 which is correct for Western Alphabet. If Oracle is not using the Western Alphabet, you'll need to determine the charset used and use http://msdn.microsoft.com/library/default.asp?url=/workshop/database/tdc/reference/CharSet.asp to correctly set the default code page.
As far as the PE_ACTIVE output column error, I can't tell what the error is. If you let me know how field is defined in Oracle, I may be able to help you. Also what version of Oracle are you using?
Larry|||Cristovao,

Could you tell us what is the source (Oracle) data type and precision and what is the suggested destination (SQL Server) type and precision?

Thanks.|||

Hi

Thx a lot for your answer.

I am sending to you the data that you asked me:

Type of the source fied: Number (1)
Suggested destination : Decimal (1)
Oracle version: 8.1.7
Best Regards,
Cristovao

|||The value 1 should be a valid precision.

Could you do another check for me? Please select the failing table on the Select Source Tables and Views" page and click "Edit..." on it. In the grid that shows up, find your "PE_ACTIVE" column and take a look at the values for Size, Precision and Scale.
There should be only the precision with the value 1.|||Hi Bob!

Thx again for your interest...

Yes, i have checked and in fact there are only the precision with the value 1, but the error occurs... Sad

|||Well, it sounds intriguing.

Can you tell me what OLE DB driver you used; Microsoft OLE DB for Oracle or Oracle OLE DB?

I was able to copy a Number(1) column without any problem, using the MS driver.

Also, what version of SSIS do you have installed?
Thanks.|||

Hi Bob!

Well, i used the Oracle Provider For OLE DB... After have read your post i tried the Microsoft OLEDB Provider For Oracle, and the data have been imported, returning this warning:
TITLE: SQL Server Import and Export Wizard

Warning 0x80202066: Source - VB_PERMISSIONS [1]: Cannot retrieve the column code page info from the OLE DB provider. If the component supports the "DefaultCodePage" property, the code page from that property will be used. Change the value of the property if the current string code page values are incorrect. If the component does not support the property, the code page from the component's locale ID will be used.



BUTTONS:

OK
I suppose it is normal.

Thanks a lot for your help.

Best Regards,
Cristovao

|||I am glad you were able to make it work.

Yes, I believe this warning can be safely ignored in this case.|||Hi all!

Same problem that I had, but the problem was that Oracle did not have a size or scale specified. SSIS automatically treats all of there as numerics, and with no specification on the precision or scale, it blows up. I have found no way to set it, and have tried both the Microsoft and Oracle drivers. Nada!

The good news....just use a Data Reader connection with the .Net Oracle Client. Works like a champ!!!!!!!!

Scott|||

Larry_Pope wrote:


As far as the codepage error, this occurs when you are pulling non-unicode string values from Oracle(and other DBs as well). SSIS cannot retrieve the CodePage (character set) used on the Oracle DB. To eliminate the warning (assuming Western Alphabet) just set the OLE DB Source to AlwaysUseDefaultCodePage to True. The DefaultCodePage should be set to 1252 which is correct for Western Alphabet. If Oracle is not using the Western Alphabet, you'll need to determine the charset used and use http://msdn.microsoft.com/library/default.asp?url=/workshop/database/tdc/reference/CharSet.asp to correctly set the default code page.

Thanks for this Larry - AlwaysUseDefaultCodePage=TRUE worked a treat!

-Jamie|||Here is the latest issue I found. Some Oracle tables do not have a precision or scale assigned to the column when the type is set to NUMBER. This causes an error when using an OLEDB connection. Has anyone found a way to get around this? The DataReader does it fine, but I don't think it is as fast as the DataReader.

Thanks!

Scott Barrett|||Any luck on thos problem, Scott?|||Here is the issue. When using SSIS against Oracle 8i or any database imported from 8i, when a column was meant to be what we call an INT, they call NUMBER and do not set the precision or scale. Oracle 9i and up does this by default. This will cause SSIS to not be able to bring in data from those columns. So we now have two solutions: Use the Data Reader Source and your done, or use the OLE DB Source and only using the Advanced Editor, enter the source and manually create each output column manually. If you are pulling from a complete table instead of a query, you can manually change the datatype in the advanced editor to a DT_I4 and it will then work.

Hope this helps you out!

Scott Barrett
Moffitt Cancer Center|||I have installed sql server 2005 evaluation version and have oracle 8i.
But I can't find OLE DB Source property of AlwaysUseDefaultCodePage to set it to True.
Can someone help me and show me directions.

Thanks,
Mitja

Error importing data from oracle database to an SQL database

Hi!

When i was importing a database table from an Oracle Database to a SQL database table, the wizard returns this error:

Could not connect source component.

Warning 0x80202066: Source - VB_PERMISSIONS [1]: Cannot retrieve the column code page info from the OLE DB provider. If the component supports the "DefaultCodePage" property, the code page from that property will be used. Change the value of the property if the current string code page values are incorrect. If the component does not support the property, the code page from the component's locale ID will be used.

Error 0xc0204018: DTS.Pipeline: The "output column "PE_ACTIVE" (34)" has a precision that is not valid. The precision must be between 1 and 38.
(SQL Server Import and Export Wizard)

I tried to change the destination type field to others than the default (decimal), but noting works.

Anyone can help me please?

Thx a lot

Cristovao

I'm currently working on a project that pull data from an Oracle DB and have had not problems pulling data and loading it into SQL 2005.
As far as the codepage error, this occurs when you are pulling non-unicode string values from Oracle(and other DBs as well). SSIS cannot retrieve the CodePage (character set) used on the Oracle DB. To eliminate the warning (assuming Western Alphabet) just set the OLE DB Source to AlwaysUseDefaultCodePage to True. The DefaultCodePage should be set to 1252 which is correct for Western Alphabet. If Oracle is not using the Western Alphabet, you'll need to determine the charset used and use http://msdn.microsoft.com/library/default.asp?url=/workshop/database/tdc/reference/CharSet.asp to correctly set the default code page.
As far as the PE_ACTIVE output column error, I can't tell what the error is. If you let me know how field is defined in Oracle, I may be able to help you. Also what version of Oracle are you using?
Larry|||Cristovao,

Could you tell us what is the source (Oracle) data type and precision and what is the suggested destination (SQL Server) type and precision?

Thanks.|||

Hi

Thx a lot for your answer.

I am sending to you the data that you asked me:

Type of the source fied: Number (1)
Suggested destination : Decimal (1)
Oracle version: 8.1.7
Best Regards,
Cristovao

|||The value 1 should be a valid precision.

Could you do another check for me? Please select the failing table on the Select Source Tables and Views" page and click "Edit..." on it. In the grid that shows up, find your "PE_ACTIVE" column and take a look at the values for Size, Precision and Scale.
There should be only the precision with the value 1.|||Hi Bob!

Thx again for your interest...

Yes, i have checked and in fact there are only the precision with the value 1, but the error occurs... Sad

|||Well, it sounds intriguing.

Can you tell me what OLE DB driver you used; Microsoft OLE DB for Oracle or Oracle OLE DB?

I was able to copy a Number(1) column without any problem, using the MS driver.

Also, what version of SSIS do you have installed?
Thanks.|||

Hi Bob!

Well, i used the Oracle Provider For OLE DB... After have read your post i tried the Microsoft OLEDB Provider For Oracle, and the data have been imported, returning this warning:
TITLE: SQL Server Import and Export Wizard

Warning 0x80202066: Source - VB_PERMISSIONS [1]: Cannot retrieve the column code page info from the OLE DB provider. If the component supports the "DefaultCodePage" property, the code page from that property will be used. Change the value of the property if the current string code page values are incorrect. If the component does not support the property, the code page from the component's locale ID will be used.



BUTTONS:

OK
I suppose it is normal.

Thanks a lot for your help.

Best Regards,
Cristovao

|||I am glad you were able to make it work.

Yes, I believe this warning can be safely ignored in this case.|||Hi all!

Same problem that I had, but the problem was that Oracle did not have a size or scale specified. SSIS automatically treats all of there as numerics, and with no specification on the precision or scale, it blows up. I have found no way to set it, and have tried both the Microsoft and Oracle drivers. Nada!

The good news....just use a Data Reader connection with the .Net Oracle Client. Works like a champ!!!!!!!!

Scott|||

Larry_Pope wrote:


As far as the codepage error, this occurs when you are pulling non-unicode string values from Oracle(and other DBs as well). SSIS cannot retrieve the CodePage (character set) used on the Oracle DB. To eliminate the warning (assuming Western Alphabet) just set the OLE DB Source to AlwaysUseDefaultCodePage to True. The DefaultCodePage should be set to 1252 which is correct for Western Alphabet. If Oracle is not using the Western Alphabet, you'll need to determine the charset used and use http://msdn.microsoft.com/library/default.asp?url=/workshop/database/tdc/reference/CharSet.asp to correctly set the default code page.

Thanks for this Larry - AlwaysUseDefaultCodePage=TRUE worked a treat!

-Jamie|||Here is the latest issue I found. Some Oracle tables do not have a precision or scale assigned to the column when the type is set to NUMBER. This causes an error when using an OLEDB connection. Has anyone found a way to get around this? The DataReader does it fine, but I don't think it is as fast as the DataReader.

Thanks!

Scott Barrett|||Any luck on thos problem, Scott?|||Here is the issue. When using SSIS against Oracle 8i or any database imported from 8i, when a column was meant to be what we call an INT, they call NUMBER and do not set the precision or scale. Oracle 9i and up does this by default. This will cause SSIS to not be able to bring in data from those columns. So we now have two solutions: Use the Data Reader Source and your done, or use the OLE DB Source and only using the Advanced Editor, enter the source and manually create each output column manually. If you are pulling from a complete table instead of a query, you can manually change the datatype in the advanced editor to a DT_I4 and it will then work.

Hope this helps you out!

Scott Barrett
Moffitt Cancer Center|||I have installed sql server 2005 evaluation version and have oracle 8i.
But I can't find OLE DB Source property of AlwaysUseDefaultCodePage to set it to True.
Can someone help me and show me directions.

Thanks,
Mitja

Wednesday, February 15, 2012

Error Handling-- no connection

I have a package that connects to remote AS400. I am wondering what is the best way to handle situation if my package could not connect to source.

-kushpaw

kushpaw wrote:

I have a package that connects to remote AS400. I am wondering what is the best way to handle situation if my package could not connect to source.

-kushpaw

There is no best way but here's a suggestion:

Verify a data source before using it
(http://blogs.conchango.com/jamiethomson/archive/2005/10/10/2253.aspx)

-Jamie

|||thanks, that ' a good start.

error handling in OLEDB source in data flow

I am trying to execute a SP like below in OLEDB source in data flow... and this statement include the insert stament ( row by row transaction).. I would like to creat an error hadling logic so that if the trasaction fail to insert the row then ignore that particular row then, move to the next row without stopping the whole process.. how can i do this?

exec usp_Inert_Registration_Episodes_Assessments

@.Unique_ID=?,

@.Gender_Cd=?,

@.Birth_Date=?,

@.Race_Ind=?,

@.Ethnicity_Cd=?,

@.Registration_Dt=? ,

--

--@.Object_Key

Recently i was working on similar thing.

To do this in SSIS the following article will be handy

1) http://www.whiteknighttechnology.com/cs/blogs/brian_knight/archive/2006/03/03/126.aspx

2) http://www.sqlis.com/55.aspx

3) http://www.sqlis.com/58.aspx

4) http://blogs.conchango.com/jamiethomson/archive/2005/07/04/SSIS-Nugget_3A00_-Execute-SQL-Task-into-an-object-variable-_2D00_-Shred-it-with-a-Foreach-loop.aspx?CommentPosted=true#commentmessage

Regarding error handling thats very much possible

Say for instance you getting data through OLE DB source. Then in the editor window, you can find "Error Output". here you can specify what to do with your error set. You can "Fail the component"/ ' Re Direct the row / ' Ignore Failure'

In case you want to redirect the row, then by setting the proper output to the error(Red Line) you can do as you want.

I hope this solves your problem.

|||

thanks,.. but

problem is my oledb source is a SP that execute insert statment.. so there are no output columns that i can map it to are available.. how can i solve this problem?

|||Why are you using an OLE DB source to insert data via a stored procedure? An Execute SQL task in the control flow would be a much better idea.|||

I agree with Phil

1) If you need to Insert with same datbase, use Execute SQl task

2) If in different database, use data flow task in which you can specify the source and destination.

secondly if you have some queries running bnefore running and this all is happening in a sproc then you can run that Sproc using Execute SQL task- Simple!!!

|||

thanks.. but if i use SQLTASK , i don;t have the option to use "Error Output" in data flow which i can specify what to do with the error row. in my case skip that row ( put that row in the error log table) and go to the next row..

how to handle the error row in the SQLTask if i want to redirect that row and go to the next row without stopping the whole process?

|||You can use an OLE DB Command component in the data flow to call the procedure. That will let you redirect error rows. However, you still need a source component to feed rows to the OLE DB Command.

Where were you planning on getting the data to feed into the procedure?

|||

Thanks jwelch -

"That will let you redirect error rows"

--Do i have to do something inside OLEDB command to be able to do that? or is it going to automatically redirect the row and move to the next row?

|||

If you drag and drop the red output arrow from the OLEDB command to another component, it will prompt you to configure it.

|||

ok.. in the data flow, i am using OLE DB source ( SQL command variable) and pass them to the OLE DB command to execute the insert statment ( by passing variables ).. I changed the error output to redirect rows to skip the row which didn't get inserted( because of an error) and move to the next row( it works)...

I drag and drop the red output arrow from the OLEDB command to another OLE DB command which will execute the insert statment to insert the failed row to Error_Log table...however, even though the row which has an error got skipped , that row didn;t get inserted to the error table.. i am not sure what i am doing wrong..

i am trying to insert the error row with the error description to a table.. what is the best way to do this?

|||

When you run it in the debugger, is a row count displayed on the red arrow?

|||

do i have to put a data viewer to be able to see it? i dont see it

but i see the color of insert to error table OLEDB command task turn to green for a sec

|||

If you are not seeing a number, it sounds like no rows are being sent to the error output. You can add a data viewer to confirm this. That indicates that the error output is not configured properly, or that the OLE DB Command is not failing on any rows.

|||but only one row out of two got inserted.. how to insert that failed row to a table?|||

safddddddddddddddddddddd wrote:

but only one row out of two got inserted.. how to insert that failed row to a table?

Hook the error output to a second OLE DB Destination.

error handling in OLEDB source in data flow

I am trying to execute a SP like below in OLEDB source in data flow... and this statement include the insert stament ( row by row transaction).. I would like to creat an error hadling logic so that if the trasaction fail to insert the row then ignore that particular row then, move to the next row without stopping the whole process.. how can i do this?

exec usp_Inert_Registration_Episodes_Assessments

@.Unique_ID=?,

@.Gender_Cd=?,

@.Birth_Date=?,

@.Race_Ind=?,

@.Ethnicity_Cd=?,

@.Registration_Dt=? ,

--

--@.Object_Key

Recently i was working on similar thing.

To do this in SSIS the following article will be handy

1) http://www.whiteknighttechnology.com/cs/blogs/brian_knight/archive/2006/03/03/126.aspx

2) http://www.sqlis.com/55.aspx

3) http://www.sqlis.com/58.aspx

4) http://blogs.conchango.com/jamiethomson/archive/2005/07/04/SSIS-Nugget_3A00_-Execute-SQL-Task-into-an-object-variable-_2D00_-Shred-it-with-a-Foreach-loop.aspx?CommentPosted=true#commentmessage

Regarding error handling thats very much possible

Say for instance you getting data through OLE DB source. Then in the editor window, you can find "Error Output". here you can specify what to do with your error set. You can "Fail the component"/ ' Re Direct the row / ' Ignore Failure'

In case you want to redirect the row, then by setting the proper output to the error(Red Line) you can do as you want.

I hope this solves your problem.

|||

thanks,.. but

problem is my oledb source is a SP that execute insert statment.. so there are no output columns that i can map it to are available.. how can i solve this problem?

|||Why are you using an OLE DB source to insert data via a stored procedure? An Execute SQL task in the control flow would be a much better idea.|||

I agree with Phil

1) If you need to Insert with same datbase, use Execute SQl task

2) If in different database, use data flow task in which you can specify the source and destination.

secondly if you have some queries running bnefore running and this all is happening in a sproc then you can run that Sproc using Execute SQL task- Simple!!!

|||

thanks.. but if i use SQLTASK , i don;t have the option to use "Error Output" in data flow which i can specify what to do with the error row. in my case skip that row ( put that row in the error log table) and go to the next row..

how to handle the error row in the SQLTask if i want to redirect that row and go to the next row without stopping the whole process?

|||You can use an OLE DB Command component in the data flow to call the procedure. That will let you redirect error rows. However, you still need a source component to feed rows to the OLE DB Command.

Where were you planning on getting the data to feed into the procedure?

|||

Thanks jwelch -

"That will let you redirect error rows"

--Do i have to do something inside OLEDB command to be able to do that? or is it going to automatically redirect the row and move to the next row?

|||

If you drag and drop the red output arrow from the OLEDB command to another component, it will prompt you to configure it.

|||

ok.. in the data flow, i am using OLE DB source ( SQL command variable) and pass them to the OLE DB command to execute the insert statment ( by passing variables ).. I changed the error output to redirect rows to skip the row which didn't get inserted( because of an error) and move to the next row( it works)...

I drag and drop the red output arrow from the OLEDB command to another OLE DB command which will execute the insert statment to insert the failed row to Error_Log table...however, even though the row which has an error got skipped , that row didn;t get inserted to the error table.. i am not sure what i am doing wrong..

i am trying to insert the error row with the error description to a table.. what is the best way to do this?

|||

When you run it in the debugger, is a row count displayed on the red arrow?

|||

do i have to put a data viewer to be able to see it? i dont see it

but i see the color of insert to error table OLEDB command task turn to green for a sec

|||

If you are not seeing a number, it sounds like no rows are being sent to the error output. You can add a data viewer to confirm this. That indicates that the error output is not configured properly, or that the OLE DB Command is not failing on any rows.

|||but only one row out of two got inserted.. how to insert that failed row to a table?|||

safddddddddddddddddddddd wrote:

but only one row out of two got inserted.. how to insert that failed row to a table?

Hook the error output to a second OLE DB Destination.

error handling in OLEDB source in data flow

I am trying to execute a SP like below in OLEDB source in data flow... and this statement include the insert stament ( row by row transaction).. I would like to creat an error hadling logic so that if the trasaction fail to insert the row then ignore that particular row then, move to the next row without stopping the whole process.. how can i do this?

exec usp_Inert_Registration_Episodes_Assessments

@.Unique_ID=?,

@.Gender_Cd=?,

@.Birth_Date=?,

@.Race_Ind=?,

@.Ethnicity_Cd=?,

@.Registration_Dt=? ,

--

--@.Object_Key

Recently i was working on similar thing.

To do this in SSIS the following article will be handy

1) http://www.whiteknighttechnology.com/cs/blogs/brian_knight/archive/2006/03/03/126.aspx

2) http://www.sqlis.com/55.aspx

3) http://www.sqlis.com/58.aspx

4) http://blogs.conchango.com/jamiethomson/archive/2005/07/04/SSIS-Nugget_3A00_-Execute-SQL-Task-into-an-object-variable-_2D00_-Shred-it-with-a-Foreach-loop.aspx?CommentPosted=true#commentmessage

Regarding error handling thats very much possible

Say for instance you getting data through OLE DB source. Then in the editor window, you can find "Error Output". here you can specify what to do with your error set. You can "Fail the component"/ ' Re Direct the row / ' Ignore Failure'

In case you want to redirect the row, then by setting the proper output to the error(Red Line) you can do as you want.

I hope this solves your problem.

|||

thanks,.. but

problem is my oledb source is a SP that execute insert statment.. so there are no output columns that i can map it to are available.. how can i solve this problem?

|||Why are you using an OLE DB source to insert data via a stored procedure? An Execute SQL task in the control flow would be a much better idea.|||

I agree with Phil

1) If you need to Insert with same datbase, use Execute SQl task

2) If in different database, use data flow task in which you can specify the source and destination.

secondly if you have some queries running bnefore running and this all is happening in a sproc then you can run that Sproc using Execute SQL task- Simple!!!

|||

thanks.. but if i use SQLTASK , i don;t have the option to use "Error Output" in data flow which i can specify what to do with the error row. in my case skip that row ( put that row in the error log table) and go to the next row..

how to handle the error row in the SQLTask if i want to redirect that row and go to the next row without stopping the whole process?

|||You can use an OLE DB Command component in the data flow to call the procedure. That will let you redirect error rows. However, you still need a source component to feed rows to the OLE DB Command.

Where were you planning on getting the data to feed into the procedure?

|||

Thanks jwelch -

"That will let you redirect error rows"

--Do i have to do something inside OLEDB command to be able to do that? or is it going to automatically redirect the row and move to the next row?

|||

If you drag and drop the red output arrow from the OLEDB command to another component, it will prompt you to configure it.

|||

ok.. in the data flow, i am using OLE DB source ( SQL command variable) and pass them to the OLE DB command to execute the insert statment ( by passing variables ).. I changed the error output to redirect rows to skip the row which didn't get inserted( because of an error) and move to the next row( it works)...

I drag and drop the red output arrow from the OLEDB command to another OLE DB command which will execute the insert statment to insert the failed row to Error_Log table...however, even though the row which has an error got skipped , that row didn;t get inserted to the error table.. i am not sure what i am doing wrong..

i am trying to insert the error row with the error description to a table.. what is the best way to do this?

|||

When you run it in the debugger, is a row count displayed on the red arrow?

|||

do i have to put a data viewer to be able to see it? i dont see it

but i see the color of insert to error table OLEDB command task turn to green for a sec

|||

If you are not seeing a number, it sounds like no rows are being sent to the error output. You can add a data viewer to confirm this. That indicates that the error output is not configured properly, or that the OLE DB Command is not failing on any rows.

|||but only one row out of two got inserted.. how to insert that failed row to a table?|||

safddddddddddddddddddddd wrote:

but only one row out of two got inserted.. how to insert that failed row to a table?

Hook the error output to a second OLE DB Destination.