Abstract the source of a SSIS package

Good morning.
We are studying SQL Server Integration Services to populate (some tables of) the database of our application from an external source. We successfully created some examples that connect to specific databases and write to a specific location. Now, I have been
asked to create an ETL project that works with any source (?)... Indeed, our application can theoretically works with a wide variety of ERP. Unfortunately, it's not quite clear to me how to achieve this result... As far as I understood, the customer should
only indicate the source table and the source column to copy in the destination table and column. The transformations and the load should be performed by the ETL we provide (?)...
I don't have any knowledge of SSIS, indeed I've tested it for only one week or a little more... I don't even know any other ETL solution. I'm really confused with the request I received, but I've been granted that ETLs can just work in that way, easily. For
now, I haven't found any easy solution with SSIS... Maybe are there other products providing this functionality? How? If SSIS can deal with this requirements, can you guide me to examples and tutorials that can help me understand how to proceed?
Thank you very much.

SSIS can work with different kind of sources and destination; below is the snapshot of sources and destination available in SSIS 2012 (By default)
There are also third parties which provides different components if you have other requirements or you can
create your source transformation at your own.
Some third party sources
Salesforce.com source
Oracle upsert
SharePoint Documents
Twitter Source
Hadoop Source
SharePoint Source (&
destination)
Email Source
XML
Disclaimer: I don't work for the third party company which I have mentioned in my answer. This list is just to make you feel comfortable about the flexibility of SSIS.
You can also take advantage of .NET framework to connect through different ERP like
SAP and fetch the data to SQL server directly. With sql server LINKED server you can query almost every famous RDBMS available in the market.
In short, you can trust SSIS to deal with different sources and destinations.
I would recommend you to use SSIS over other ETL solutions because of the level of customization, flexibility and easy to use framework.
Hope this will help... let us know if you need more information.
Glad to help! Please remember to accept the answer if you found it helpful. It will be useful for future readers having same issue.
My Profile on Microsoft ASP.NET forum

Similar Messages

Can't change the connection string of SSIS package with derived columns?

We upgraded SQL server 2008 to 2012, copied and converted all SSIS packages from Visual Studio 2008 to 2010. When I opened a package in VS 2010 and tried to change the connection string, in the local connection managers, if the data source is another
SSIS package B(.dtsx file) with derived columns, I can't change the connection string of package B. When I opened the file connection manager editor for package B and tried to locate a dtsx file in another location, saved the change, reopened the project.
Package B still pointed to previous file. Other packages without derived columns work fine. Any thoughts?

We are using the package deployment model and refer to other packages in the same project. If
we changed the path of package B (with derived columns) to "D:\Visual Studio 2010\xxxx", and refer it in package A, in the A's connection manager, the connection string of package B is still its previous location "D:\Visual
Studio 2008\xxxx". When we ran the package A in the SQL server agent, the data source is still
"D:\Visual
Studio 2008\xxxx", so how can I change it to "D:\Visual
Studio 2010\xxxx"? Why has the package C (without derived columns) no such problem? thanks.

How to pull a Specific files from the local path using SSIS package

Hi Friends,
I have 15 Dealers files .With the Files name as follows
1. ''ACTEST00001_20141112_0408_INV.TXT''
2. ''ACTEST00002_20141112_0408_INV.TXT''
I will get these files through FTP on Daily basis with changes on date alone.
I will have 4 files for each dealers.like INV,SERVICE,SALES,APPOINTMENT.
SO i need to fetch a particular dealer with particular date.
I need to create this scenario in SSIS package.Please suggest me how to create this and what are all the Tasks i need to use to implement this process.
Arunraj Kumar

http://microsoft-ssis.blogspot.jp/2011/08/foreach-ftp-file-enumerator.html
http://www.bidn.com/blogs/MikeDavis/ssis/559/ssis-skip-certain-files-in-a-for-each-loop
http://www.sqlis.com/sqlis/post/Looping-over-files-with-the-Foreach-Loop.aspx
http://www.rad.pasfu.com/index.php?/archives/22-Looping-through-specific-files-SSIS.html
http://www.mssqltips.com/sqlservertip/1641/get-list-of-files-from-an-ftp-server-in-sql-server-integration-services/

Is it possible to get the source code of sun package in JDK1.4?

If i want to review the code of the HTTP protocol handler and some other things.
how can i get the source. or is it possible?
thank you.

See this post if you can figure out something out of it ....
http://forum.java.sun.com/thread.jsp?forum=31&thread=391451

Problem in viewing the source code of a package using all_source

I have created a package and compiled it in schema1.I have created public synonym of the package.Now I am logged in some ohter schema say schema2. If I am using TOAD, I can see the body of the package from schma2 but if I am using sqlplus and using all_source data dictionary I can get only the spec of the package.
Could you please tell me how to get the whole package body using all_source data dictionary from other schema?

This is the query that I am executing from other schema
select TEXT from all_source where NAME = 'P_PACKAGE';
SQL> select OBJECT_NAME ,OBJECT_TYPE from all_objects where OBJECT_NAME = ''P_PACKAGE';
OBJECT_NAME OBJECT_TYPE
'P_PACKAGE SYNONYM
'P_PACKAGE PACKAGE

Getting error after enabling the Transaction in SSIS package in Windows Server 2008 R2 Standard machine

Hi,
I created a package with "Execute SQL Task and Data Flow Task". I am able to execute successfully in my server having
"Windows Server 2008 R2 Standard" Operating System.
But after enabling the Transaction in my SSIS Package I am not able to execute it. It is giving error. The same package is running in my local machine with Transaction enabled on
Windows 7 Operation System.
The error which I got in my server after enabling the Transaction is
"The SSIS Runtime has failed to enlist the OLE DB connection in a distributed transaction with error 0x8004D025
"The partner transaction manager has disabled its support for remote/network transactions.". End Error "
I search with this error message in google and found some solutions in the following links
http://social.msdn.microsoft.com/Forums/en-US/7172223f-acbe-4472-8cdf-feec80fd2e64/the-partner-transaction-manager-has-disabled-its-support-for-remotenetwork-transactions
http://technet.microsoft.com/en-us/library/cc753510(WS.10).aspx
http://support.microsoft.com/kb/817064
But none of the above solution is not working. Kindly help me to resolve this issue.
Thanks in Advance.
Sridhar

Hi Sridhar,
Please compare the DTS settings on the Windows 7 computer and the Windows Server 2008 R2 computer and make sure they are identical. Make sure the “Allow Inbound” and “Allow Outbound” options are check, and pay attention to the authentication mode as
well.
Besides, make sure both Distributed Transaction Coordinator (TCP-In) and Distributed Transaction Coordinator (TCP-Out) rules in Firewall are enabled.
If the issue persists and there are any security/anti-virus software, temporarily disable the security/anti-virus software and check the issue again.
Regards,
Mike Yin
TechNet Community Support

SSIS package with OData connection - can't connect

I need to read some data from a SP list. I have the OData connection manager setup. When I test the connection to my sharepoint site, it says it's successful. I added in a data flow task and then an OData Source. In the OData Source editor, I select the
Odata connection manager. I want to use a collection. However, it says "Unable to load collection for the connection Odata Source, reason: Cannot open this connection"
Anybody know how to resolve this?

Hi kayla,
Just as you said, the current
SharePoint List Adapter that extracting and loading SharePoint Data in SQL Server Integration Services supports x86/x64 systems using SQL 2005 / SQL 2008 / SQL 2008 R2/ SQL 2012. It doesn’t support SQL 2014. Maybe we need waiting the update.
The
OData Source component can be used to read data from SharePoint lists in SSIS 2014. Please download and install the 64 bit ODataSourceForSQLServer2014-amd64.msi or 32 bit ODataSourceForSQLServer2014-x86.msi from the
Microsoft® SQL Server® 2014 Feature Pack.
Reference:
Tutorial: Using the OData Source
Using the SSIS OData Source Connector to read data from SharePoint lists
If there are any other questions, please feel free to ask.
Thanks,
Katherine Xiong
If you have any feedback on our support, please click
here.
Katherine Xiong
TechNet Community Support
Hi Katherine,
I did install that already. I added the OData source to my SSIS package. The odata connection manager successfully connects to the sharepoint site. However, when I use the data source in the Odata Source within the Data Flow, it gives me the "cannot
open this connection" in the Collection list within the Odata source editor. I'm stumped as to why the connection manager has a successful test connection, but the collections don't pull up. Does the list need some special permissions? I'm able to access
it directly on the sharepoint site and add items (the odata connection manager is running with my windows credentials)

SSIS package issue

I need to schedule job to run through a package.
for that i imported SSIS package by connecting Integration services after import done it showing there in MSDB.
Now i connected to SQL DB engine to see and schedule asa job for the imported package but i am not able to see the imported package in maintenance plans. so totally confused with this behavior of package.
I have alternate for schedule this package through new job steps so i done it and then when i run the job it getting error as "login failure for user", here the user is service account, so please help in this issue.
Thanks,
Janardhan

Hi Janardhan,
According to the error message that “login failure for user”, it seems that SQL Agent Service account does not have required privileges to access the data sources in your SSIS package. Please check if the service account has enough permissions.
Please note that to configure a user to execute Microsoft SQL Server Agent jobs, we should grant the user with the following SQL Server Agent fixed database roles in the msdb database:
SQLAgentUserRole, SQLAgentReaderRole, or SQLAgentOperatorRole. Just as SequelMate suggested, If the user is non-administrative user that want to run jobs to execute SSIS packages, they will need to have access to a proxy account that has the
required privileges and then run the SSIS package under this account. Please check the issue again.
Reference:
Configure a User to Create and Manage SQL Server Agent Jobs
Thanks,
Katherine Xiong
Katherine Xiong
TechNet Community Support

How to insert CLEAR SSIS Package in another SSIS Package

Hi All,
We have a requirement to run CLEAR SSIS Package in another SSIS Package whish extracts data from Oracle database system. Needed to run CLEAR SSIS Package if data exists in BPC application else run extract to Oracle system. Basically continue with SSIS Package and extract to Oracle system.
In Outlooksoft 4.2 we didn't have any issue, since all evModify is going to be in DTS Package and we didn't have any issues in placing a condition connection to CLEAR Package. Basically we were running CLEAR Package inside anther DTS Package twice successfully.
When we tried to create same functionality in SAP BPC 5.1, the code from EVMODIFY not doing correctly in executing the CLEAR inside another SSIS Package.
If any body knows how to create SSIS Package with a combination of 2 or more SSIS Packages by taking above scenario, please let me know.
The basic requirement is, how do we include a SSIS Package in another SSIS Package and use EVMODIFY to run this meta package in SAP BPC 5.1 environment.
Any information would be appreciated.
Regards,
Sreekanth.

Yes, I have the job , and tried running this, Looks like it started executing. Will update in next 5 mins if it runs fine.
Looking at the command it generated, it looks like it is setting few more parameters like LoggingLevel, Synchronized , callerInfo etc.. I believe these should be optional right?
Also now I have to set two Parameters out of 10 parameters the project takes, If I add additional /Par Project.starttime , will the package pick the values passed from this prompt?
/ISSERVER "\"\SSISDB\FFF\PPP\Xpackage2.dtsx\"" /SERVER "\".\"" /Par "\"$ServerOption::LOGGING_LEVEL(Int16)\"";1 /Par "\"$ServerOption::SYNCHRONIZED(Boolean)\"";True /CALLERINFO SQLAGENT /REPORTING E

Why is the LookUp object in the Flow Task of my SSIS package going red (and not working) ? Sql Server 2008 R2

I have been working with the Sql Server 2008 R2 SSIS Tutorial at
https://msdn.microsoft.com/en-us/library/ms170419(v=sql.105).aspx
--specifically -- Lesson 1. I have been having some problems with this lesson where the source data from the samples download doesn’t exactly match the data described in the tutorial, and the tables in the tutorial are different from what
is contained in AdventureWorksDW (tutorial refers to DimTime – AdventureWorksDW contains DimDate and no DimTime).
So, after futzing in BI with this tutorial so that I can at least get it to run in Debug – it errors out on the 2nd LookUp object.
Rather than looking for a fix to the problem(s) that I am having between the tutorial and the stuff I downloaded in the samples --
I want “Adapt” the tutorial so I can use the stuff I downloaded and hopefully learn how to use SSIS with the elements (source data and tables) that are present on my workstation.
Here is a description of what is going on for me – which I really don’t understand what is going on in BI – based on the images below – like what columns (from what tables) are they associating to in the OleDB Destination?
Note: the sql in the LookUps here is the sql that I copied from the tutorial.
I probably need to modify these sql statements – so -- the help I am requesting is to make the required modifications/changes
so that I can adapt this tutorial with the stuff that’s on my workstation.
I downloaded the samples and the AdventureWorksDW mdf for Sql Server 2008 R2.
It turns out that in the tutorial it wants me to select a DimTime table, but the version of the AdventureWorksDW db does not contain a DimTime table.
Instead, it contains a DimDate table. So I tried adapting DimDate for the tutorial.
Additionally, the sample data file -- SampleCurrencyData.txt -- has slightly different data types than the types described in the tutorial, so I selected data types for the columns in the datasource text file that would work in BI would to
connect column from source data file to the table.
After finishing all the steps for Lesson 1 -- when I tried debugging the package – and it error'd out on the 2nd Lookup object whichwent red.
 I edited the lookups and the sample Ole DB Destination to "ignore on fail” and I did all
green but the FactCurrencyRate table is not being populated -- as described in the tutorial, so I reset the on error back to default (Fail on error option). And based on this tutorial -- I believe FactCurrencyRate
table is the table which is supposed to be populated with the data from SampleCurrencyData.txt?
In the sample data file that downloaded with all the samples I removed all the data from the text file except for 6 rows, so instead of the original 1100 or so rows, I have only 6 rows of data in the source data file (just to keep things
simple for debugging for now). I did not modify the data itself.
Here is what the (raw) data contained in SampleCurrencyData.txt looks like (from the samples that I downloaded from codeplex) – it’s supposed to be 4 columns of data – float, nvarchar, datetime, float:
0.281690141 USD
6/26/2004 0:00 0.281713948
0.281690141 USD
6/27/2004 0:00 0.281642539
0.281690141 USD
6/28/2004 0:00 0.281761573
0.283286119 USD
6/29/2004 0:00 0.283221933
0.283286119 USD
6/30/2004 0:00 0.283358363
0.281690141 USD
7/1/2004 0:00 0.281682206
Below are images of my BI Layout for Lesson 1 from this tutorial -- the FlatFile and configurations for On Fail Error, A Flow task, the 2 LookUps (CurrencyKey and DataKey), the OleDB Destination configuration, the Design view of the associated tables and
the Debug Run of Lesson 1, and the following error messages. My goal is to figure out what is going on in BI for this tutorial.
Error: 0xC020901E at Extract Sample Currency Data, Lookup Datakey [51]: Row yielded no match during lookup.
Error: 0xC0209029 at Extract Sample Currency Data, Lookup Datakey [51]: SSIS Error Code DTS_E_INDUCEDTRANSFORMFAILUREONERROR.
The "component "Lookup Datakey" (51)" failed because error code 0xC020901E occurred, and the error row disposition on "output "Lookup Match Output" (53)" specifies failure on error. An error occurred on the specified
object of the specified component. There may be error messages posted before this with more information about the failure.
Error: 0xC0047022 at Extract Sample Currency Data, SSIS.Pipeline: SSIS Error Code DTS_E_PROCESSINPUTFAILED.
The ProcessInput method on component "Lookup Datakey" (51) failed with error code 0xC0209029 while processing input "Lookup Input" (52). 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.
There may be error messages posted before this with more information about the failure.
--this is the flat file
-- SampleCurrencyData.txt (which only contains 6 data rows for my purposes)
--and here is where I assign the data types for the colums of -- SampleCurrencyData.txt
This is the first LookUp Object -- LookUp Currency Key – The DB contains DimCurrency table.
I copied the sql from the tutorial here.
I actually have a DimCurrency table in my copy of AdventureWorksDW.
Here’s the design view of DimCurrency and a sample of the data contained in DimCurrency and the On Fail configuration
I actually have a DimCurrency table in my copy of AdventureWorksDW.
Here’s the design view of DimCurrency and a sample of the data contained in DimCurrency and the On Fail configuration
--Here is what the data looks like in the DimCurrency table
--2nd LookUp object -- LookUp Data Key – this is the LookUp
where BI errors out on Debug
--it appears this lookup is referencing the DimDate table – which I DO have in the DB.
--I can’t find the following sql in the tutorial, so I suppose BI added the sql (did it?)
--Here's how I configured for On Error
--Here is DimDate table in Design view
--Here is a sample of the original data contained in DimData
OleDB Destination
--Here is where I get lost a bit – what is going on in the destination here?
--Here's my On Error configuraino
--and here is the FactCurrencyRate table
--and here is a sample of the data contained in FactCurrencyRate
Rich P

Thank you for your reply. I changed the error handling as you suggested on the 2nd lookup to redirect to unmatched rows. Now I get all greet. I don't have the conditional split as in your diagram. But also, nothing appears to have
happened in the DB. Aren't the rows in my text file supposed to be added to the FactCurrencyRate table?
How do I get a conditional split?
Rich P
OK, sorry I forgot to reply you back.
Conditional Split was just dummy task. Ignore it.
Manipulate the data in such way that you get matching records.
Inside Source, for first 2 rows I put the dates which are available in DimDate.
1.00010001,ARS,7/1/2005 0:00,0.99960016
1.00010001,ARS,2/5/2006 0:00,1.001001001
1.00020004,ARS,9/5/2001 0:00,0.99990001
1.00020004,ARS,9/6/2001 0:00,1.00040016
1.00050025,ARS,9/7/2001 0:00,0.99990001
1.00050025,ARS,9/8/2001 0:00,1.001001001
Then in OLE DB Destination, I loaded the rows to TestFactTable.
(Now, you don't even need NO MATCH OUTPUT as there are matching records here)
Cheers,
Vaibhav Chaudhari
[MCTS],
[MCP]

SSIS package fails with the error as given below. But its warning messages are incorrect.

My SSIS package loads data from access database to SQL Server database.
It's a straight copy. It fails with the below warnings and error message as shown below:
Error messages:
[OLE DB Source [113]] Error: There was an error with OLE DB Source.Outputs[OLE DB Source Output].Columns[RetentionID] on OLE DB Source.Outputs[OLE DB Source Output]. The column status returned was: "Text was truncated or one or more characters had no
match in the target code page.".
[OLE DB Source [113]] Error: The "OLE DB Source.Outputs[OLE DB Source Output].Columns[RetentionID]" failed because truncation occurred, and the truncation row disposition on "OLE DB Source.Outputs[OLE DB Source Output].Columns[RetentionID]"
specifies failure on truncation. A truncation error occurred on the specified object of the specified component.
[SSIS.Pipeline] Error: SSIS Error Code DTS_E_PRIMEOUTPUTFAILED. The PrimeOutput method on OLE DB Source returned error code 0xC020902A. The component returned a failure code when the pipeline engine called PrimeOutput(). The meaning of the failure
code is defined by the component, but the error is fatal and the pipeline stopped executing. There may be error messages posted before this with more information about the failure.
There are 3 warning messages even before I run the package. Warnings are all about the mismatch between the source and destination column sizes.
I cross checked the source and destination column sizes. The destination column sizes are fairly high than the source column sizes.
It worked well all the while and when we are going to pre-prod it is throwing errors. Any help is highly appreciated.
Thank you.

It worked well all the while and when we are going to pre-prod it is throwing errors. Any help is highly appreciated.
Please check if the dev destination table has same column data types and size as compared with pre prod table
Thanks, hsbal

Getting error while trying to upload the data in excel from SSIS package through sql agent job

We are getting below errors.
Error:
The Microsoft Jet database engine cannot open the file '\\serversdev\Documents\QC Files\Prod.xls'. It is already opened exclusively by another
user, or you need permission to view its data.
Please suggest ASAP
Regards,
Ramu
Ramu Gade

Hi Dikshan Gade,
According to your description, you want to upload data from excel to database, when you call ssis package through SQL Server Agent job, you got the error message.
To troubleshoot the problem, please refer to the following steps:
Validate that the account has permissions on the file and the folder.
Verify that the file and the data source name (DSN) are not marked as Exclusive.
Make sure SQL Server Agent Services service account has the permission to access the database.
We can check SQL Server Agent’s activity logs, Windows Event logs and SSIS logs to get more clues. Also the tool Process Monitor is helpful to track the cause of registry or file access related issues. For more information about the issue, please refer to
the following KB article:
http://support.microsoft.com/kb/306269
If you have any more questions, please feel free to ask.
Thanks,
Wendy Fu
Wendy Fu
TechNet Community Support

Error while running the SSIS package from SQL DB to excel file - export option

hi all,
I have 4.6 million records in my sql db and i want to copy this into a excel file. for this i went to the db and rt click and export to command and started the ssis package running. but after
few minutes, it throws me an error that "error in transferring data into excel file."
Can anyone help me why this happened and the resolution ?
help is appreciated!
Copying to `excel1_Wbook` (Error)
Messages
Error 0xc0202009: Data Flow Task 1: SSIS Error Code DTS_E_OLEDBERROR. An OLE DB error has occurred. Error code: 0x8007000E.
(SQL Server Import and Export Wizard)
Error 0xc0047022: Data Flow Task 1: SSIS Error Code DTS_E_PROCESSINPUTFAILED. The ProcessInput method on component "Destination - excel1_Wbook" (217) failed with error code 0xC0202009 while processing input "Destination Input" (228).
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. There may be error messages posted before this with more information
about the failure.
(SQL Server Import and Export Wizard)
Error 0xc02020c4: Data Flow Task 1: The attempt to add a row to the Data Flow task buffer failed with error code 0xC0047020.
(SQL Server Import and Export Wizard)
Error 0xc0047038: Data Flow Task 1: SSIS Error Code DTS_E_PRIMEOUTPUTFAILED. The PrimeOutput method on Source - excel1_Wbook returned error code 0xC02020C4. The component returned a failure code when the pipeline engine called PrimeOutput(). The
meaning of the failure code is defined by the component, but the error is fatal and the pipeline stopped executing. There may be error messages posted before this with more information about the failure.
(SQL Server Import and Export Wizard)

You need to split your data and create (at least 5) worksheet targets.
For example if you have a ROW_NUMBER column you can use for instance a
Conditional Split for something like:
ROW_NUMBER % 5 == 0 for Case 1 (excel 1)
ROW_NUMBER % 5 == 1 for Case 2 (excel 2)
ROW_NUMBER % 5 == 2 for Case 3 (excel 3)
ROW_NUMBER % 5 == 3 for Case 4 (excel 4)
ROW_NUMBER % 5 == 4 for Case 5 (excel 5)

Error while executing SSIS package - Error: 4014, Severity:20, State: 11. A fatal error occurred while reading the input stream from the network. The session will be terminated (input error: 109, output error: 0)

Hi,
We are getting the following error when running our SSIS packages on Microsoft SQL Server 2012 R2 on Windows Server 2008 R2 SP1:
Error: 4014, Severity:20, State: 11. A fatal error occurred while reading the input stream from the network. The session will be terminated (input error: 109, output error: 0)
SQL Server Data Tools and SQL Server Database Engine reside on the same server.
We tried the following:
Disabling TCP Chimney Offload
Installed Windows Server 2008 SP1
Splitting our SSIS code into multiple steps so it is not all one large continuous operation
The error occurs during a BulkDataLoad task.
Other options we are investigating with the engineering team (out-sourced, so delayed responses):
Firewall configurations (everything is local, so this should not make a difference)
Disabling the anti-virus scanner
Are there other things we can try?
Any insight is greatly appreciated.
Thanks!

Hi HenryKwan,
Based on the current information, the issue can be caused by many reasons. Please refer to the following tips:
Install the latest hotfix based on your SQL Server version. Ps: there is no SQL Server 2012 R2 version.
Change the MaxConcurrentExecutables property from -1 to another one based on the MAXDOP. For example, 8.
Set "RetainSameConnection" Property to FALSE on the all the connection managers.
Reference:
https://connect.microsoft.com/SQLServer/feedback/details/774370/ssis-packages-abort-with-unexpected-termination-message
If the issue is still existed, as Jakub suggested, please provide us more information about this issue.
Thanks,
Katherine Xiong
Katherine Xiong
TechNet Community Support

Error while executing SSIS Package after upgrading the Oracle Client

Hello,
I am running to the below error after we upgraded the Oracle client to 11g from 10g. The source of the Data is Oracle database . Looked online but each error is pointing towards different route, Confused here any help is very much appreciated. Have to say
I am not a pro with SSIS.
SSIS package "Bentek_ISO_Package (2).dtsx" starting.
Information: 0x4004300A at Temp_tbl Injection Data Flow Task, SSIS.Pipeline: Validation phase is beginning.
Information: 0x4004300A at Temp_tbl Injection Data Flow Task, SSIS.Pipeline: Validation phase is beginning.
Warning: 0x80049304 at Temp_tbl Injection Data Flow Task, SSIS.Pipeline: Warning: Could not open global shared memory to communicate with performance DLL; data flow performance counters are not available. To resolve, run this package as an administrator,
or on the system's console.
Information: 0x40043006 at Temp_tbl Injection Data Flow Task, SSIS.Pipeline: Prepare for Execute phase is beginning.
Information: 0x40043007 at Temp_tbl Injection Data Flow Task, SSIS.Pipeline: Pre-Execute phase is beginning.
Error: 0xC0202009 at Temp_tbl Injection Data Flow Task, OLE DB Source [1]: SSIS Error Code DTS_E_OLEDBERROR. An OLE DB error has occurred. Error code: 0x80040E14.
An OLE DB record is available. Source: "OraOLEDB" Hresult: 0x80040E14 Description: "ORA-12801: error signaled in parallel query server P183, instance *****:qrmgmt2 (2)
ORA-01861: literal does not match format string".
An OLE DB record is available. Source: "OraOLEDB" Hresult: 0x80004005 Description: "ORA-12801: error signaled in parallel query server P183, instance ****:qrmgmt2 (2)
ORA-01861: literal does not match format string".
Error: 0xC004701A at Temp_tbl Injection Data Flow Task, SSIS.Pipeline: component "OLE DB Source" (1) failed the pre-execute phase and returned error code 0xC0202009.
Information: 0x4004300B at Temp_tbl Injection Data Flow Task, SSIS.Pipeline: "component "OLE DB Destination" (52)" wrote 0 rows.
Information: 0x40043009 at Temp_tbl Injection Data Flow Task, SSIS.Pipeline: Cleanup phase is beginning.
Task failed: Temp_tbl Injection Data Flow Task
Warning: 0x80019002 at *******: SSIS Warning Code DTS_W_MAXIMUMERRORCOUNTREACHED. The Execution method succeeded, but the number of errors raised (2) reached the maximum allowed (1); resulting in failure. This occurs when the number of errors reaches
the number specified in MaximumErrorCount. Change the MaximumErrorCount or fix the errors.
SSIS package "****** (2).dtsx" finished: Failure.

Do you have any Date conversion functions in your Oracle datetime fields? I did run into a similar issue when we upgraded the oracle client and the provider started to decipher the metadata of the date columns. The SSIS metadata conversion for the date
columns yielded dates that were not valid. I had to update my queries to use the TO_CHAR conversion to bring it out as a string and then save it to the date field.
TO_CHAR (DATE, 'MM/DD/YYYY HH24:MI:SS')
Regards, Dinesh

Abstract the source of a SSIS package

Similar Messages

Maybe you are looking for