Big difference in RAW converter between Aperture and Nikon Capture NX

hi
here's a quick photo for comparing (hosted on my site since it's huge):
http://www.raffaz.net/stuff/nx_aperture.png (4.4mb uncompressed PNG file)
I'm quite disappointed by some aspects of Aperture's RAW handling... or at least, by comparing it to Capture NX.
by looking at the picture, you can instantly see that NX raw photo is much sharper, and it is nearly perfect (apart from the not-perfect photo itself).
by looking at Aperture's shot, you can see that it's blurry, with moirè and noise-like problems..
the screenshots are 100% crops from the latest versions of the applications, using flat settings as you can see (just import, deselect everything the app will do), the camera is a Nikon D70, the lens is a 18-70 f3.5 and the file is a .NEF (nikon raw). settings for the photo are ISO200, f8, 1/15, 50mm on tripod.
I admit I'm very surprised by this difference. I'm using the trial of NX (just wanted to test it since it's brand new) and when I noticed all these differences I was shocked. I'm not saying that NX is better than Aperture, I think that Aperture is still unbeaten in a lot of fields, but could someone please explain me this huge difference in quality?
if needed, I can provide more screenshots with other photos

hi
here's a quick photo for comparing (hosted on my site
since it's huge):
http://www.raffaz.net/stuff/nx_aperture.png (4.4mb
uncompressed PNG file)
I'm quite disappointed by some aspects of Aperture's
RAW handling... or at least, by comparing it to
Capture NX.
by looking at the picture, you can instantly see that
NX raw photo is much sharper, and it is nearly
perfect (apart from the not-perfect photo itself).
by looking at Aperture's shot, you can see that it's
blurry, with moirè and noise-like problems..
the screenshots are 100% crops from the latest
versions of the applications, using flat settings as
you can see (just import, deselect everything the app
will do), the camera is a Nikon D70, the lens is a
18-70 f3.5 and the file is a .NEF (nikon raw).
settings for the photo are ISO200, f8, 1/15, 50mm on
tripod.
I admit I'm very surprised by this difference. I'm
using the trial of NX (just wanted to test it since
it's brand new) and when I noticed all these
differences I was shocked. I'm not saying that NX is
better than Aperture, I think that Aperture is still
unbeaten in a lot of fields, but could someone please
explain me this huge difference in quality?
if needed, I can provide more screenshots with other
photos
I dont like Capture NX one bit, its just as slow and sluggish as the previous version. The reason why pics often look better in Capture is becuase Nikon wrote it, after all the NEF format is theres.
To be honest Capture NX cannot be compared to Aperure there not in the same league, and you can pick up Aperture for the Same price as Capture NX on ebay brand new i would alwasy go for aperture far better value for money IMHO.

Similar Messages

Difference in RAW reading between Photoshop and Lightroom

Hi All
I have today noticed that Photoshop and Lightroom does nor read a RAW file the same way. Both running the 4.4.1 engine.
Here is a screen dump from PS, showing quite a lot of Highlight clipping.
http://picasaweb.google.dk/taasti/PSVsLG/photo?authkey=1J4sXZ_SvZw#5191662550019326466
And here is the same picture shown in Lightroom:
http://picasaweb.google.dk/taasti/PSVsLG/photo?authkey=1J4sXZ_SvZw#5191662618738803218

ACR will show clipping relative to the chosen color space, while (correct me if I'm wrong) Lr will always show clipping relative to ProProtoRGB.
You might want to convert a raw to DNG so that ACR settings will be embedded, then develope in either (choosing PpRGB as a pref in ACR), and then inspect in the other. It may even be useful to first make a copy of the DNG, name one Lr, the other ACR, and do the same thing going both directions. [Edit: The final test would be to open both in Ps ... and report back.]
What's your OS platform, and with what method have you calibrated your display? Are you using dual monitors? (none of these ?s will affect the degree of clipping, but might affect the brightness)
It's a fetch, but is there any chance the clipping level can be set as a preference? (ie, '252') Or is clipping simply defined to be off the histogram. (ie, '255')

Difference in the Balance between FS10N and Customer Balances in Local Curr

Hi,
When i am trying to match the Balances between FS10N and Customer Balances in Local Currency for the Period 8, we are getting the difference, The reconcilliaton Account was changed on 30.08.2010.
Please help Us in tracing the differences between FS10N and Customer Balances in Local Currency.
What could be the possible reasons for the differences..
Thanks

Hi Varshani,
Please use the program/report SAPF070 to compare or reconcile your AR with GL balances. You can use SAPF071 to correct any inconsistencies. Provided below documentation for these programs.
SAPF070 - Compare Documents and Account Transaction Figures
Description
This program compares debit and credit transaction figures in customer, vendor, and G/L accounts with the debit and credit totals from documents posted in the corresponding posting period (accounting reconciliation). The sales totals are also compared for customer and vendor accounts. There is no separate comparison for special G/L transactions.
A comparison for G/L accounts can be made in company code currency and in parallel currencies (such as group currency). A comparison for customer and vendor accounts can only be made in company code currency.
After the program has finished, a message is issued to the user that started the program. This message summarizes the results of the reconciliation.
Output
The program compares the totals of an account on a periodic basis. If the debit and credit total differs between account and documents, the account is printed with the debit and credit totals and the difference.
Differences in G/L accounts are shown per transaction currency. The first line shows the amount in local currency, the second line shows the amounts in transaction currency.
If a document which falls within the selection range is posted during the program run, the program is terminated since a reliable result can no longer be delivered.
SAPF071 - Adjust Balances after Comparing Documents/Transaction Figures
Description
If a financial accounting comparative analysis (SAPF190) or a comparison of documents and transaction figures (SAPF070) shows that there are differences between documents and transaction figures, you can use this program to make an adjustment. The documents form the basis for this adjustment. The program adjusts the (redundant) transaction figures, which are only totals of amounts from documents.
Requirements
All of the following listed requirements must be fulfilled:
1. A financial accounting comparative analysis (SAPF190) or a comparison of documents and transaction figures (SAPF070) must be made, and differences must be found between documents and transaction figures.
2. There must not be any inconsistent documents found. These are listed in both SAPF070 and SAPF190 as well as in this program.
3. There cannot be any problems in the other modules. Caution: You have to check this yourself. Financial Accounting may be correct but the other modules may not be, and this will adversely affect the program run.
4. You can only make the adjustment in the ledgers which are compared by program SAPF070. This is ledger 00 or a user-defined ledger for all parallel local currencies except the group currency. (The program displays these ledgers). You have to adjust any additional ledgers as well as average balance ledgers yourself.
5. No documents during the period in which you are adjusting transaction figures can be archived. Caution: You must ensure that these documents are not archived by establishing appropriate organizational rules and procedures.
Only use this program after consulting with SAP or after checking the prerequisites thoroughly.
You should adjust all differences together for a single company code. By setting the program parameters you can limit the adjustment to G/L currency types or to balances in subledgers.
It is advisable to execute a test run first, which will list any differences that are found.
Further notes - Authorizations
Repair program authorization group (F_005)
Company code authorization (F_BKPF_BUK)
Thanks
Venkata Ganesh Perumalla
Edited by: Venkata Ganesh Perumalla on Sep 28, 2010 1:30 PM

Fail to convert between UTF8 and UCS2

: java.sql.SQLException: Fail to convert between UTF8 and UCS2: failUTF8Conv
(BC4J throws that exception)
I got that error message when try to show the table's content in uix page.
I use varchar2(40). the error occurs, when i set special characters like õ,ü,Ü.. and so on.
This affects only UTF encoded database.
We use: 9.0.2.5, Jdev9.0.3.3., UIX, iAS 9.4.2??(i dont'know)
As i know the problem is when there is 40 letters in the column and it contains "special character" it can't convert it, because the neccessary space requered to store values is much more.
If i use nvarchar, i don't think it fix this problem.
And as i know, all sql constant must use where coulmn=N'constans value' format.
Q:
How can i set the UTF database and BC4J to run correctly.
I mean... what type to use, what is the column size to set.
Thanks in advice,
Viktor

I had the same problem using Oracle 9i. The problem lied within the Oracle JDBC driver itself! --;
If you're using JDBC driver from Oracle 9i, stop using it!
You should download JDBC driver of Oracle 10g from Oracle site and use that driver instead.
After I changed the driver, I now have no problem of getting Korean characters from the database.
Hope this would solve your problem too.

Fail to convert between UTF8 and UCS2: failUTF8Conv

We need to store possibly all UTF8 chararacter in his database
especially $ & ( 4 8 < = > from WE8ISO8859P1 and from WE8ISO8859P15.
So we install an UTF8 instance and set NLS_LANG to UTF8.
We have to do select/update from a java client and sqlplus(like).
When we insert with java client it's unreadable from sqlplus and
when whe insert from sqlplus we've got 'Fail to convert between UTF8 and UCS2: failUTF8Conv '
here the code made in sqlplus
update CPW_TEST set lb_comportement='$ & ( 4 8 < = > ' WHERE ID_TEST=14805;
here the code made in java
update CPW_TEST set lb_comportement='$ & ( 4 8 < = > ' WHERE ID_TEST=14804;
and then the result in database
SELECT id_test,LB_COMPORTEMENT FROM CPW_TEST WHERE ID_TEST=14804 or ID_TEST=14805
ID_TEST LB_COMPORTEMENT
14804 B$ B& B( B4 B8 B< B= B> B
14805 $ & ( 4 8 < = >
2 rows selected
and the dump
SELECT id_test,dump(LB_COMPORTEMENT) FROM CPW_TEST WHERE ID_TEST=14804 or ID_TEST=14805
ID_TEST DUMP(LB_COMPORTEMENT)
14804 Typ=1 Len=26: 194,164,32,194,166,32,194,168,32,194,180,32,194,184,32,194,188,32,194,189,32,194,190,32,194,128
14805 Typ=1 Len=17: 164,32,166,32,168,32,180,32,184,32,188,32,189,32,190,32,128
2 rows selected
I'm not sure, but it seems that sqlplus uses true UTF8 (variable length codes) and java client uses UCS-2 (2 bytes)
How can I solve my problem?
Our configuration
javaclient (both thin and oci jdbc driver 8.1.7), sqlplus client and database Oracle 8.1.7.0.0 on the same computer (W2000 or NT4)
Thank you for yoru attention.

Hi Luis, thanks for your suggestions. You're right that problem was in JServ and his JVM.
There was conflict between different versions of Java. While iFS was using JRE 1.3.1, JServ was configured to use JRE 1.1.8. As soon as I corrected link to the right Java, problem disappears.
Radek

Java.sql.SQLException: Fail to convert between UTF8 and UCS2: failUTF8Conv

Hi all,
I am writing a servlet that connects to Oracle 8.0.6 through jdbc for jdk1.2 on NT 4.0
English version and it works fine.
But when the servlet is deployed to a solaris with Oracle 8.0.5 (not a typo, the oracle on
NT is 8.0.6 and oracle on solaris is 8.0.5) and jdbc for jdk1.2 (of course, for Solaris),
the servlet failed with the Exception:
java.sql.SQLException: Fail to convert between UTF8 and UCS2: failUTF8Conv
(I am using JRun 3.0 as the application and web server for both NT and Solaris)
(The database in both the NT and solaris platform are using UTF8 charset)
My servlet looks like this: (dbConn is a Connection object proved to be connected to Oracle
in previous segment of the same method):
String strSQL = "SELECT * FROM test";
try { Statement stmt = dbConn.createStatement();
ResultSet rs = stmt.execute(strSQL);
while (rs.next()) {
out.println("id = " + rs.getInt("id"));
System.out.println("id written");
out.println("name = " + rs.getString("name")); // <-- this is the line the
exception is thrown
System.out.println("name written");
} catch (java.sql.SQLException e) {
System.out.println("SQL Exception");
System.out.println(e);
The definition of the "test" table is:
create table test(
id number(10,0),
name varchar2(30));
There are about 10 rows exists in the table "test", in which all rows contains ONLY chinese
characters in the "name" field.
And when I view the System log, the string "id written" is shown EXACTLY ONCE and then there
is:
SQL Exception
java.sql.SQLException: Fail to convert between UTF8 and UCS2: failUTF8Conv
That means the resultset is fetch back from the database correctly. The problem arise only
during the getString("name") method.
Again, this problem only happens when the servlet is run on the solaris platform.
At first I would expect there are some strange code shown on the web page rather than having
an exception. I know that I should use getBytes to convert between different encodings, but
that's another story.
One more piece of information: When all the rows contains ascii characters in their "name"
field, the servlet works perfectly even in solaris.
If anyone knows why and how to tackle the problem please let me know. You can feel free to
send email to me at [email protected]
Many thanks,
Ben
null

Hi all,
For the problem I previously posted, I found that Oracle had had such bug filed before in Oracle 7.3.2 (something like that) and is classified to be NOT A BUG.
A further research leads me to the document of Oracle that the error message:
"java.sql.SQLException: Fail to convert between UTF8 and UCS2: failUTF8Conv"
is a JDBC driver error message of error number ORA-17037.
I'm still wondering why this behaviour will happen only in Solaris platform. The servlet on an NT machine I am using (which has an Oracle 8.0.6 and jdbc for jdk 1.2 running) is working just fine. I also suspect that this may be some sort of mistakes from jdbc driver.
Nevertheless, I have found a way to work around the problem that I cannot get non-English string from Oracle in Solaris and I would like to share it with you all here.
Before I go on, I found that there are many people out there on the web that encounter the same problem. (Some of which said s/he has been working on this problem for a month). As a result, if you find this way of working around the problem does help you, please tell those who have the same problem but don't know how to tackle. Thanks very much.
Here's the way I work it out. It's kinda simple, but it does work:
Instead of using:
String abc = rs.getString("SomeColumnContainsNonEnglishCharacters");
I used this:
String abc = new String(rs.getBytes("SomeColumnContainsNonEnglishCharacters"));
This will give you a string WITH YOUR DEFAULT CHARSET (or ENCODING) from your system.
If you want to convert the string read to some other encoding type, say Big5, you can do it like this:
String abc = new String(rs.getBytes("SomeColumneContainsNonEnglishCharacters"), "BIG5");
Again, it's simple, but it works.
Finally, if anyone knows why the fail to convert problem happens, please kindly let me know by leaving a word in [email protected]
Again, thanks to those of you who had tried to help me out.
Creambun
<BLOCKQUOTE><font size="1" face="Verdana, Arial">quote:</font><HR>Originally posted by creambun creambun ([email protected]):
Hi all,
I am writing a servlet that connects to Oracle 8.0.6 through jdbc for jdk1.2 on NT 4.0
English version and it works fine.
But when the servlet is deployed to a solaris with Oracle 8.0.5 (not a typo, the oracle on
NT is 8.0.6 and oracle on solaris is 8.0.5) and jdbc for jdk1.2 (of course, for Solaris),
the servlet failed with the Exception:
java.sql.SQLException: Fail to convert between UTF8 and UCS2: failUTF8Conv
(I am using JRun 3.0 as the application and web server for both NT and Solaris)
(The database in both the NT and solaris platform are using UTF8 charset)
My servlet looks like this: (dbConn is a Connection object proved to be connected to Oracle
in previous segment of the same method):
String strSQL = "SELECT * FROM test";
try { Statement stmt = dbConn.createStatement();
ResultSet rs = stmt.execute(strSQL);
while (rs.next()) {
out.println("id = " + rs.getInt("id"));
System.out.println("id written");
out.println("name = " + rs.getString("name")); // <-- this is the line the
exception is thrown
System.out.println("name written");
} catch (java.sql.SQLException e) {
System.out.println("SQL Exception");
System.out.println(e);
The definition of the "test" table is:
create table test(
id number(10,0),
name varchar2(30));
There are about 10 rows exists in the table "test", in which all rows contains ONLY chinese
characters in the "name" field.
And when I view the System log, the string "id written" is shown EXACTLY ONCE and then there
is:
SQL Exception
java.sql.SQLException: Fail to convert between UTF8 and UCS2: failUTF8Conv
That means the resultset is fetch back from the database correctly. The problem arise only
during the getString("name") method.
Again, this problem only happens when the servlet is run on the solaris platform.
At first I would expect there are some strange code shown on the web page rather than having
an exception. I know that I should use getBytes to convert between different encodings, but
that's another story.
One more piece of information: When all the rows contains ascii characters in their "name"
field, the servlet works perfectly even in solaris.
If anyone knows why and how to tackle the problem please let me know. You can feel free to
send email to me at [email protected]
Many thanks,
Ben<HR></BLOCKQUOTE>
null

Cannot convert between unicode and non-unicode string datatypes

My source is having 3 fields :
ItemCode nvarchar(50)
DivisionCode nvarchar(50)
Salesplan (float)
My destination is :
ItemCode nvarchar(50)
DivisionCode nvarchar(50)
Salesplan (float)
But still I am getting this error :
Column ItemCode cannot convert between unicode and non-unicode string datatypes.
As I am new to SSIS , please show me step by step.
Thanks In Advance.

My source is having 3 fields :
ItemCode nvarchar(50)
DivisionCode nvarchar(50)
Salesplan (float)
My destination is :
ItemCode nvarchar(50)
DivisionCode nvarchar(50)
Salesplan (float)
But still I am getting this error :
Column ItemCode cannot convert between unicode and non-unicode string datatypes.
As I am new to SSIS , please show me step by step.
Thanks In Advance.
HI Subu ,
there is some information gap , what is your source ? are there any transformation in between ?
If its SQL server source and destination and the datatype is as you have mentioned I dont think you should be getting such errors ... to be sure check advance properties of your source and check metada of your source columns
just check simple oledb source as
SELECT TOP 1 ItemCode = cast('111' as nvarchar(50)),DivisionCode = cast('222' AS nvarchar(50)), Salesplan = cast(3.3 As float) FROM sys.sysobjects
and destination as you mentioned ... it should work ...
somewher in your package the source columns metadata is not right .. and you need to convert it or fix the source.
Hope that helps
-- Kunal
Hope that helps ... Kunal

Reference Library for Converting Between LabVIEW and XML Data (GXML)

Please provide feedback, comments and questions on the Reference Library for Converting Between LabVIEW and XML Data (GXML) in this thread.
The latest version of the NI GXML Library is availble in VIPM on the NI LabVIEW Tools Network repository.

Francesco, Thank you for the feedback. With this component it was my intention to make a more "terse" version of the LabVIEW Flatten to XML VI that was also supported on RT and that gave the user more flexbility regarding the structure of the parsing type definition. I think you are right that the XML parser is not compliant to section 2.11 of the XML spec. The parser does specifically looking for a #D#A and this appears to be an oversight on my part. Please confirm for me, the specifcation is saying that the XML parser should be able to recognize three possibilities as an "end of line" character: #D#A, #D, or #A. Am I reading this right?There are more efficient (and in some cases much more efficient) ways of sharing data between LabVIEW and LabVIEW: some examples are flattened binary strings and the datalog binary format. XML is slower than these optons but the upside is that it is human readable. Furthermore XML is inherently hierarchical which is convenient for complex data structures like clusters of arrays of clusters, etc. If you don't care about human readability then you are correct XML doesn't make as much sense.I will return to the GXML source code and try to fix this in the near future but I would hope that instead of creating yet another custom VI from scratch that you could reuse what I have provided for you. I included enough documentation in the source code so that users could make some modificiations themselves. The target application for this reference library was LabVIEW to LabVIEW communication. As such I documented the schema on the dev zone document from a LabVIEW perspective. It includes all the supported datatypes and all the supported data structures (cluters, arrays, multidimensional arrays, clusters of multidimensional arrays, etc.) I do see some value in making a more conventional XML spec but the time investment required didn't really line up with my intended use case. Were there any other downsides to GXML that I have missed? Best Regards, Jeff TippsSystems Engineer - Sound and VibrationMessage Edited by Jeff T. on 04-21-2010 10:09 AM

SQL Exception: Fail to convert between UTF8 and UCS2: failUTF8Conv

Hi,
I am trying to use the DBMS_OBFUSCATION_TOOLKIT to encrypt/decrypt some strings through JDBC, but I am getting the following exception:
SQL Exception: Fail to convert between UTF8 and UCS2: failUTF8Conv
The input and output parameters for the encryption/decryption functions are VarChar2.
Our database is using UTF8.
I will be glad if someone can help me on this.
Thanks,
Cenk

Susi,
This is just a wild guess, but your java client is on a different computer to your Oracle 9.2 server, and the locale (or encodings) on the two computers is different. Am I correct? If so, then I guess you need to change the locales (or encodings) so that they match.
Have you tried printing out the "System" properties for the two JVMs (Oracle's and your client's)? Something simple like this:
System.getProperties().list()Good Luck,
Avi.

Fail to Convert between UTF8 and UCS2: fail UTF Conversion

I'm using the JReport software, a product which generates java reports based on a jdbc datasource.
during installation the JReport installation program located Microsoft java VM installed on my PC and I accepted this option to be working JVM for JReport.
This worked very well. I have installed jdbc driver for Oracle 8.1.5 that worked fine as well on the design time (I have connected to Oracle, I have seen my tables and other information on my DB).
But when I switched the run-time view (when real data is going to load) then the following exception message appeared :
"Fail to Convert between UTF8 and UCS2: fail UTF Conversion" .
if there is anybody who understood my problem any kind of help will be appreceated
It will be helpfull to receive any suggestions made to this matter.
Anything relative help will be welcome.
thanks in advance.

I had the same problem using Oracle 9i. The problem lied within the Oracle JDBC driver itself! --;
If you're using JDBC driver from Oracle 9i, stop using it!
You should download JDBC driver of Oracle 10g from Oracle site and use that driver instead.
After I changed the driver, I now have no problem of getting Korean characters from the database.
Hope this would solve your problem too.

SSIS Package : While Extracting Sharepoint Lookup column, getting error 'Cannnot convert between unicode and non-unicode string data types'

Hello,
I am working on one project and there is need to extract Sharepoint list data and import them to SQL Server table. I have few lookup columns in the list.
Steps in my Data Flow :
Sharepoint List Source
Derived Column
its formula : SUBSTRING([BusinessUnit],FINDSTRING([BusinessUnit],"#",1)+1,LEN([BusinessUnit])-FINDSTRING([BusinessUnit],"#",1))
Data Conversion
OLE DB Destination
But I am getting the error of not converting between unicode and non-unicode string data types.
I am not sure what I am missing here.
In Data Conversion, what should be the Data Type for the Look up column?
Please suggest here.
Thank you,
Mittal.

You have a data conversion transformation. Now, in the destination are you assigning the results of the derived column transformation or the data conversion transformation. To avoid this error you need use the data conversion output.
You can eliminate the need for the data conversion with the following in the derived column (creating a new column):
(DT_STR,100,1252)(SUBSTRING([BusinessUnit],FINDSTRING([BusinessUnit],"#",1)+1,LEN([BusinessUnit])-FINDSTRING([BusinessUnit],"#",1)))
The 100 is the length and 1252 is the code page (I almost always use 1252) for interpreting the string.
Russel Loski, MCT, MCSE Data Platform/Business Intelligence. Twitter: @sqlmovers; blog: www.sqlmovers.com

Column "A" cannot convert between unicode and non-unicode string data types

I am following the SSIS overview video-
https://secure.cbtnuggets.com/it-training-videos/series/microsoft-sql-server-2008-business-development/6143?autostart=true
I have a flat file that i want to import the contents onto a SQL database.
I created a Dataflow task, source file and oledb destination.
I am getting the folliwung error -
"column "A" cannot convert between unicode and non-unicode string data types"
in the origin file the data type is coming as string[DT_STR] and in the destination object it is coming as "Unicode string [DT_WSTR]"
I used a data conversion object in between, dosent works very well
Please help what to do

I see this often.
Right Click on FlatFileSource --> Show Advanced Editor --> 'Input and Output Properties' tab --> Expand 'Flat File Source Output' --> Expand 'Output Columns' --> Select your field and set the datatype to DT_WSTR.
Let me know if you still have issues.
Thank You,
Jay

Column cannot convert between unicode and non-unicode string data types

I am converting SSIS jobs from SQL Server 2005 running on a Windows 2003 server to 2008R2 running on a Windows 2008 server.  I have a dataflow with an OLE DB Source which is selecting from an Oracle view.  This of course worked fine in
2005.   This OLE DB Source will not even read the data from Oracle without the error "Column "UWI" cannot convert between unicode and non-unicode. The select is:
SELECT SOME_VIEW.UWI AS UWI,
CAST(SOME_VIEW.OIL_NET AS NUMERIC(9,8)) AS OIL_NET
FROM SOME_SCHEMA.SOME_VIEW
WHERE OIL_NET IS NOT NULL AND UWI IS NOT NULL
ORDER BY UWI
When I do "Show Advanced Editor" on this component, in the Input and Output Properties, I show the OLE DB External Column as DT_STR length 40 for the UWI column and for the Output Columns I see the UWI as the same DT_STR.
How can I get past this? I have tried doing a cast...cast(SOME_VIEW.UWI AS VARCHAR(40)) AS UWI and this gives the same error. The column in Oracle is a varchar2(40).
Any help is greatly appreciated. Thanks.

Please check the data type for UWI using advanced editor for Oledb Source under
external columns and output columns. Are the data types same?
If not, try changing the data type (underoutput columns) same as data type shown under
external columns
Nitesh Rai- Please mark the post as answered if it answers your question

Cannot convert between unicode and non-unicode string data types.

I'm trying to copy the data from 21 tables in a SQL 2005 database to a MS Access database using SSIS. Before converting the SQL database from 2000 to 2005 we had this process set up as a DTS package that ran every month for years with no problem. The only way I can get it to work now is to delete all of the tables from the Access DB and have SSIS create new tables each time. But when I try to create an SSIS package using the SSIS Import and Export Wizard to copy the SQL 2005 data to the same tables that SSIS itself created in Access I get the "cannot convert between unicode and non-unicode string data types" error message. The first few columns I hit this problem on were created by SSIS as the Memo datatype in Access and when I changed them to Text in Access they started to work. The column I'm stuck on now is defined as Text in the SQL 2005 DB and in Access, but it still gives me the "cannot convert" error.

I was getting same error while tranfering data from SQL 2005 to Excel , but using following method i was able to tranfer data. Hopefully it may also help you.
1) Using Data Conversion transformation
data types you need to select is DT_WSTR (unicode in terms of SQL: 2005)
2) derived coloumn transformation
expression you need to use is :
(DT_WSTR, 20) (note : 20 can be replace by your character size)
Note:
Above teo method create replica of your esting coloumn (default name will be copy of <coloumn name>).
while mapping data do not map actual coloumn to the destination but select the coloumn that were created by any of above data transformer (replicated coloumn).

How to fix "cannot convert between unicode and non-unicode string data types" :/

Environment: SQL Server 2008 R2
Introduction:Staging_table is a table where data is being stored from source file. Individual and ind_subject_scores are destination tables.
Purpose: To load the data from a source file .csv while SSIS define table fields with 50 varchar, I can still transfer the data to the entity table/ destination and keeping the table definition.
I'm getting validation error "Cannot convert between a unicode and a non-unicode string data types" for all the columns.
Please help

Hi ,
NVARCHAR = DT_WSTR
VARCHAR = DT_STR
Try below links:
http://social.msdn.microsoft.com/Forums/sqlserver/en-US/ed1caf36-7a62-44c8-9b67-127cb4a7b747/error-on-package-can-not-convert-from-unicode-to-non-unicode-string-type?forum=sqlintegrationservices
http://social.msdn.microsoft.com/Forums/en-US/eb0d1519-4be3-427d-bd30-ae4004ea9e8d/data-conversion-error-how-to-fix-this
http://technet.microsoft.com/en-us/library/aa337316(v=sql.105).aspx
http://social.technet.microsoft.com/wiki/contents/articles/19612.ssis-import-excel-to-table-cannot-convert-between-unicode-and-non-unicode-string-data-types.aspx
sathya - www.allaboutmssql.com ** Mark as answered if my post solved your problem and Vote as helpful if my post was useful **.

Big difference in RAW converter between Aperture and Nikon Capture NX

Similar Messages

Maybe you are looking for