For Office 2010, the following update will correct this issue.
https://www.microsoft.com/en-us/download/details.aspx?id=39664
For Office 365 (please note, by default Office365 installs the 32-bit version regardless of your system), use:
https://www.microsoft.com/en-us/download/details.aspx?id=54920
OAS version 12.00.0043 now uses OracleManagedDataAccess assembly. If you are using an older version of OAS we recommend to update to the latest version. If you have upgraded from a previous version and using TNSNAMES.ORA name in the Database file please see the FAQ on TNSNAMES.ORA.
The cause of this error is one or more of the database table columns has been modified to not allow null values. OAS creates the columns in the table to allow null values so when the data quality is bad for a tag value a null value will be inserted into the table. The only column that should be set to not allow null values is the DateAndTime column. There are 2 solutions to this error:
In an effort to help you decide which database engine to choose in your implementation, and how you can boost performance with an existing OAS configuration, we’ve performed extensive testing. On each of the database engines listed, we configured our Data Historian to log Tag Data in 3 different ways.
Narrow
In this configuration, a single value is written per table along with a timestamp for the logged value. This means each OAS Tag logged will result in a single database table.
Wide 10
Each table contains 10 OAS Tags arranged in a single row for each given timestamp. In this test we logged 10 OAS Tag values in a single table.
Wide 990
Using the same configuration as Wide 10, but logging 990 OAS Tags per timestamp.
From our testing, we’ve determined that the fastest overall DB engine is Microsoft SQL Server, even though it performed only slightly slower in the Narrow table test than the next fastest engine Oracle. But because of its dramatically superior performance in all other tests (>2M values per second!), we recommend using MS SQL Server for data logging where possible. Oracle and mySQL are the next fastest engines, and have similar performance numbers to each other, but are also extremely quick when using a Wide logging format.
Efficiency is boosted with logging multiple values per table in the Wide formats, and the fastest speeds can be achieved when increasing the number of values per record. Yet, because we log to an open format, you can still perform post-processing or data archiving that transforms this wide format into a normalized configuration for your own internal usage, while still getting the benefits of high-speed logging.
View the Database Security Login topic on how to setup security logins and access writes to create, open, and read and write to the database.
View the Data Logging Errors troubleshooting guide for a complete list of error causes and solutions.
View the source of the problem under Configure-System Errors.
The complete history of errors can be viewed under C:\Program Files\Open Automation Software\OAS\Log or the path that is set under Configure-Options-System Logging.
Enable Log Data Logging Transactions under Configure-Options-System Logging to see the details of each transaction and error returned from the database engine.
Either enable the SYSTEM account to have read and write access to the mapped drive and directory, or set the OAS Engine Service LogOn to a user account that would have access to the remote mapped drive using these steps in setting the OAS Engine Service LogOn.
Either enable the SYSTEM account to have read and write access to the mapped drive and directory, or set the OAS Reports Service LogOn to a user account that would have read and write access to the remote mapped drive.
View the following video on how to setup security in the database engine:
Direct link: /videos/#troubleshoot-connection-login
Go to Configure-Options-History and Enable History Date Format.
Examples:
yyyy-MM-dd HH:mm:ss
MM/dd/yyyy HH:mm:ss
