ABBYY Flexicapture ODBC export date field to DATE type column - abbyy

In ABBYY Flexicapture, I use the ODBC-Compatible database option to export to my SQL Server database. Several of my columns in the database are DATETIME, but I recently realized, we don't need (nor have) the time, and would like to export only the date. So I changed the database column to a DATE type. Now I'm getting this error:
Failed when converting date and/or time from character string
I am not providing it with a time, only a date. Historically, these have gone into the database with 00:00:00 as the time associated with the date.
How can I export to DATE column?

Have never faced such issue in FC. First make sure that ODBC driver is from the drivers list they recommend
For SQL 2000, 2005, 2008, 2008R2, 2012 database:
Provider - OLE DB Provider for ODBC Drivers;
Note: Selecting "OLE DB Provider for SQL Server" may cause problems when working with certain data types and long fields.
Driver - SQL Server.
For Access 2003, 2007, 2010 database:
Provider - OLE DB Provider for ODBC Drivers; Driver - Microsoft Access Driver (Driver do Microsoft Access or Microsoft Access-Treiber).
For Oracle 9g, 10g, 11g database:
Provider - Oracle Provider for OLE DB;
Selecting the driver is not required.
Second try to reset the export destination. Select the ODBC source and map fields again

Related

I am in need of connecting to DB2 AS/400 database from Oracle Apex.

Is there any feasibility from Oracle to have a connection established to DB2 database so that I can query on DB2 database and generate reports from Oracle Apex?
OR
Is it possible to create a View in Oracle from a remote DB2 database?
OR
What options do i have in order to develop reports in Oracle Apex from the data i have in DB2 database?
(I know, this is an old question and you've already found a workaround. Anyway,) the keyword you might be interested in is gateway. This is Oracle 10g Database Gateway for DB2/400 Installation and User's Guide. I don't know which database you use, but - if 10g is not the one, I hope you'll manage to find the right documentation.
Shortly: after installing the gateway between Oracle and DB2, you'd create a database link. Then, in your Oracle schema, create a view that selects data over that database link from DB2 database. Finally, fetch data in Apex from the view.
As i didn't find a way to directly connect to DB2 from Oracle PL/SQL, i used a work-around. As this is a reporting tool, we are ok to have this tool running with the data which is 1 day off, we did the following:
1) Extract the data required from DB2 database to CSV files. We used a DB2 command which can be run at command line to extract the data into a CSV
2) Then we imported the data into Oracle tables using sqlldr

SQL Server 2005 to 2012 com.microsoft.sqlserver.jdbc.SQLServerException: Implicit conversion from data type varbinary to datetime2 is not allowed

We are migrating from SQL Server 2005 to 2012. One of the functionality is failing with this error
com.microsoft.sqlserver.jdbc.SQLServerException: Implicit conversion from data type varbinary to datetime2 is not allowed. Use the CONVERT function to run this query.
We use SQLJDBC driver 3.0 to communicate with SQL Server 2012. I see this issue is happening when we try to insert NULL value into a DATETIME column (nullable). Same however works in 2005. Any help with this issue is appreciated.
It's a simple INSERT statement that fails from Java to SQL server 2012 using MyBatis ORM:
Insert into temp_test (date1, name, date2) values ('2010-10-10 00:00:00.0','test',null)
This insert fails when we try from our app (using SQL JDBC driver)... However same code base works without any issue in SQL 2005.
I can recommend the following read on migrating from to SQL Server 2012, written by Thomas LaRock (SolarWinds).
Relevant quotes from the article:
Using the SQL 2012 Upgrade Advisor
Review the Breaking Changes
Reviewing the Behavioral Changes
Executing DBCC CHECKDB WITH DATA_PURITY (will check your data for values that are no longer valid)
Further, it is hard to say more specific things about your issue without seeing the table definition. I would however suggest the following things:
DATE/TIME strings should be formatted in ISO 8601 format as much as possible: eg '2010-10-10T00:00:00.0'
If you still experience issues, try inserting with CAST('2010-10-10T00:00:00.0' AS DATETIME) or CONVERT(DATETIME,datetimecolumn,<format>)
Reset the compatibility level of your database to the appropriate version for SQL Server 2012: ALTER DATABASE <database_name> SET COMPATIBILITY_LEVEL=110;
Upgrade your SQLJDBC driver to the latest version (current version is 6.0)
Use a different driver eg JTDS JDBC Driver (open source 100% pure Java (type 4) JDBC 3.0 driver for Microsoft SQL Server, 2012 supported)
Install the latest Service Pack for SQL Server 2012 (latest is Service Pack 3; overview).
Review MyBatis for any incompatibilities with SQL Server 2012.
I just ran into this error with MyBatis and SQL Server 2012 when attempting to do an insert where a DATETIME2 column could be null. The solution to my issue was specifying the JDBC type in my mapper file as specified in the MyBatis documentation.
From: http://www.mybatis.org/mybatis-3/sqlmap-xml.html#Parameters
The JDBC Type is required by JDBC for all nullable columns, if null is
passed as a value. You can investigate this yourself by reading the
JavaDocs for the PreparedStatement.setNull() method.
On the insert statement in the mapper file, the value for the date2 column would have "jdbctype = TIMESTAMP" added to it, like so:
<insert id="testInsert" parameterType="com.example.object">
INSERT INTO tempt_test
(date1, name, date2)
VALUES
(#{date1}, #{name}, #{date2, jdbcType = TIMESTAMP})
</insert>

ODBC Linked server in sql 2005 doesn’t work from remote box

I have a dev workstation with sql 2005 installed and in it I created a linked server to a odbc connection to a clarion database. I can run select statements against it inside sql Mgt studio. When I take a second workstation and connect to the sql on the first box using sql mgt studio, then try the exact same query I get
OLE DB provider "MSDASQL" for linked server "liveclarion" returned message "[SoftVelocity Inc.][TopSpeed ODBC Driver][ISAM]ISAM Table Not Found".
Any thoughts? It appears to have the same functionality on a second sql server. No remote sql mgt studio connect success in queries against my linked ODBC clarion DB.
All done with windows authentication and the same AD user.
The error returned by the ODBC driver is "SAM table not found".
So I'm assuming you have a table called SAM - presumably in a table called Sam.Tps?
I'm wondering if you need to set a path to that file - ie if there's some difference in path or file name validity between your two tests. One assumes not, but I'd look in that direction first.

Crystal Reports against OLAP / XMLA / SimbaO2X-server

I'm trying to convert some old Excel-reports to Crystal Reports. The excel sheets uses OLAP-cubes and connects to a database using a XMLA connection over a SimbaO2X driver.
I just can't figure out which connection settings to use in Crystal Reports to be able to connect to the database.
I've tried both XML and OLAP connections, but just can't get a database connection.
Any help with the connection setting would be appreciated!
Edit: The database is a bit of a black box; it's probably an Oracle database (it was an Oracle database before the end user frontend was rewritten in java. They could have changed the database as well.) I have however no success with neither the Oracle Server nor the Microsoft OLE DB for Oracle connection method.
I have also this morning found a SimbaO2X provider under the OLE DB folder. While not working it's the best so far -- it accepts the username and password and lets me select which database to connect to but then fails with ADO Error Code: 0x80040e73 (Format of the initialization string does not conform to the OLE DB specification.) At least I have something to go on.
I'm running Crystal Reports XI if someone needs to know.
Partial solution:
Upgrade Crystal Reports XI to Release 2, service pack 4.
Update from service pack 4 to service pack 6.
Upgrades and updates can be downloaded from the SAP Community Network
A connection can now be made with the SimbaO2X OLE DB driver. This solution should also resolve connection problems with some other databases as well.
However, adding a table to the report results in a 0x800a0cc1 error (Item cannot be found in the collection corresponding to the requested name or ordinal)

Sybase ASE OLE DB Connection in SQL Server Integration Services 2005

I am building a SQL Server 2005 Integration Services package to migrate data from a Sybase Adaptive Server Enterprise 12.5.4 database to a SQL Server 2005 Database. The Sybase Database is the backend for a vendor product which our team does not have the authority to change or manage.
In my initial stages of development, to access the Sybase database, I created a SQL Server Linked Server utilizing the Microsoft OLE DB Provider for ODBC Drivers on my destination database server. With this linked server created, I created my SSIS package with a single Data Source - connecting to the MS SQL Server "Destination" Database. Next, in my SSIS package data flow tasks, I configured the OLE DB Source to access single Data Source defined in the package, using SQL commands to access the source linked server (simply using SELECT col1, col2, col3 FROM [SybaseLinkedServer].[Database].dbo.[Table]). The OLE DB Destination within the data flow task utilizes the same connection manager as the OLE DB Source, but makes use of the Table or view - fast load Data access mode.
Later, in the project, I obtained the Sybase ASE OLE DB Provider (The v12.5.4 OLE DB Provider was no longer available, we had to purchase the v15.7 ASE SDK). Thinking that removing the Linked Server from the solution would improve performance, I modified the SSIS package to include a new OLE DB Data Source utilizing the Sybase ASE OLE DB Provider to access the Sybase Database directly, and modified the OLE DB Source to use the new ASE OLE DB Data Source with the Table or View Data access mode.
To my surprise, switching the solution from the Linked Server using the OLEDB Provider for ODBC Drivers to the direct OLEDB connection using the Sybase ASE OLEDB Provider produced significantly poorer results, far from my expectations. The results from test runs using each method are available at this hyperlink.
Has anyone experienced this type of issue and/or is this behavior to be expected? Is there a better way to configure this to extract data from Sybase ASE to MS SQL Server 2005?
i had the exact same issue and i ended up using linked server to connect to sybase because it was the fastest way and most reliable, i had great difficulty trying to connect to sybase using SSIS sql 2008 directly.
even though i was able to connect to sybase using Sql 2000 DTSs.
but there is a very interesting driver provided by datadirect
http://www.datadirect.com/products/other/ssis/index.html
i downloaded it and tried it for 30 days, and it was amazing fast and very easy
its very light when comparing it with sybase drivers, i mean not much to install and it works very good with SSIS.

Resources