SQL Server ODBC connector Exception
Moderators: chulett, rschirm, roy
SQL Server ODBC connector Exception
I am having an issue with following select statement when running a DS job
Strange thing is that it works from ODBC stage when I cut and paste this statement interactively in ODBC stage
Select
LocateRef,
PlaceRef,
REPLACE(REPLACE(REPLACE(TheAddress, CHAR(10), ' '), CHAR(13), ' '), CHAR(9), ' ') AS TheAddress,
SysUser,
RecType,
RecStat,
SysVersion,
SeqNum FROM Address;
When I run the DS job to transfer data for Address table I get the following error messages in the parallel job
ODBC_Connector_52: Unrecognized argument: ), CHAR(13),
ODBC_Connector_52: SAX parser exception thrown: The input ended before all started tags were ended. Last tag started was 'SelectStatement' (CC_PropertySet::fatalError, file CC_PropertySet.cpp, line 2,205)
Any idea what may be the problem?
Strange thing is that it works from ODBC stage when I cut and paste this statement interactively in ODBC stage
Select
LocateRef,
PlaceRef,
REPLACE(REPLACE(REPLACE(TheAddress, CHAR(10), ' '), CHAR(13), ' '), CHAR(9), ' ') AS TheAddress,
SysUser,
RecType,
RecStat,
SysVersion,
SeqNum FROM Address;
When I run the DS job to transfer data for Address table I get the following error messages in the parallel job
ODBC_Connector_52: Unrecognized argument: ), CHAR(13),
ODBC_Connector_52: SAX parser exception thrown: The input ended before all started tags were ended. Last tag started was 'SelectStatement' (CC_PropertySet::fatalError, file CC_PropertySet.cpp, line 2,205)
Any idea what may be the problem?
dj
-
- Participant
- Posts: 54607
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact:
- same problem with DB2 connector
Had a similar problem
DB2_Connector_0: SAX parser exception thrown: A leading surrogate character was not followed by a legal second character (CC_PropertySet::fatalError, file CC_PropertySet.cpp, line 2,146)
Problem does not occur with other DB2 sources. Could it be that the problem has something to do with the character set of the input source?
DB2_Connector_0: SAX parser exception thrown: A leading surrogate character was not followed by a legal second character (CC_PropertySet::fatalError, file CC_PropertySet.cpp, line 2,146)
Problem does not occur with other DB2 sources. Could it be that the problem has something to do with the character set of the input source?
-
- Premium Member
- Posts: 138
- Joined: Wed Jul 16, 2008 9:51 pm
- Location: Kolkata
Hi,
SAX Parser is used to process XML files. If by any chance your file is XML then there's a missing or invalid character in the file.
In your case the error is at line 2146.
Remove these errors using a XML Document handler and re run the job.
SAX Parser is used to process XML files. If by any chance your file is XML then there's a missing or invalid character in the file.
Theerens,ODBC_Connector_52: SAX parser exception thrown: The input ended before all started tags were ended. Last tag started was 'SelectStatement' (CC_PropertySet::fatalError, file CC_PropertySet.cpp, line 2,205)
In your case the error is at line 2146.
Remove these errors using a XML Document handler and re run the job.
TONY
ETL Manager
Infotrellis India
"Do what you can, with what you have, from where you are and to the best of your abilities."
ETL Manager
Infotrellis India
"Do what you can, with what you have, from where you are and to the best of your abilities."
-
- Premium Member
- Posts: 138
- Joined: Wed Jul 16, 2008 9:51 pm
- Location: Kolkata
-
- Participant
- Posts: 54607
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact:
-
- Premium Member
- Posts: 138
- Joined: Wed Jul 16, 2008 9:51 pm
- Location: Kolkata
-
- Participant
- Posts: 26
- Joined: Wed Jul 17, 2013 9:00 am
I came across this error and found where the problem is. I used a parmeter set variable directly in the job without including the paramter set itself in the job parameters (job properties). While this may be only one of many reasons why this could occur, I am posting it here so that it is beneficial for others. In case you hit this eerror, check that you have all the parameters in order .
Thanks
SB
Thanks
SB