Hi @tsuji_ryusuke, I think you are right in that the main issue is that the FlexSim DateTime class isn't working correctly with Oracle's TIMESTAMP data type. This appears to be a bug, so I will add something to the developer's list.
For now, in order to get FlexSim to export something that can be imported correctly into Oracle, you can export the DateTime data from FlexSim in something else other than Model.dateTime, and/or you can import the data as something else other than the TIMESTAMP data type in Oracle, like string/text or number data. You can also manually export the data with the different Database classes in the FlexScript API, using a SQL syntax that will work with Oracle.
I am attaching an example model (TestDBTimestamp.fsm) to show a way to manually export to Oracle using FlexScript. The model was made in FlexSim 2025 Update 2 (version 25.2). You can see what kind of commands are needed to first connect to the database, then what kind of SQL text is needed to export the data to the database table. You will need to set up DatabaseConnector1 with the connection information for your Oracle database and then make the necessary FlexScript changes in the Script window to match the database table and column. In the example model, they are currently set as TEST and DATA, respectively. And for the sake of testing, the table in Oracle was made with
CREATE TABLE test (data TIMESTAMP);
Another option that might be possible, a way I haven't tried or seen tested, is to export the DateTime data from FlexSim as a string and then use something like the TO_TIMESTAMP function in Oracle to convert the string to a TIMESTAMP data type. Again, this is currently untested from the FlexSim side since it makes more sense to do it in Oracle. You can actually see the SQL being used in the example model has TO_TIMESTAMP. So instead of including it with the manual FlexSim export, there might be a way to execute something similar from the Oracle side as the data is being imported.
As for the error that you are getting when excluding the STime and ETime columns in your Statistics Collector, I'm not sure what is going on. I think we would need the model to troubleshoot it at all. The tree path points to code that is executed when the Export Now button is clicked, and it's just a function_s() command for the DatabaseConnector called exportSingle, but that code is not accessible from the tree. I would probably need to get a developer to help me take a look if we can recreate the error.
