Timestamp format must be yyyy-mm-dd hh:mm:ss[.fffffffff]

Nick shared this question 2 months ago
Awaiting Reply

Hi,

Application Version:8.0.4Build:20200121

I am getting the above error when importing a report into the production environment. Below is the debug log stack just before the error:

2020-08-20 11:03:25:DEBUG (MIReportExportImportProcess:loadUploadFileModel) - Entering parseImportFile()2020-08-20 11:03:25:ERROR (V4ImportProcess:parseImportFile) - Error: com.thoughtworks.xstream.converters.ConversionException: Timestamp format must be yyyy-mm-dd hh:mm:ss[.fffffffff]

From the tests that I've done, I can safely say that there's nothing wrong with the export file as I'm able to import them into another system without any issue that is exactly on the same version, so my guess here would be something to do with the DB config?

Please let me know what other information you need.

Thanks,

Nick

Comments (13)

photo
1

Hi Nick,

I have a few questions for you:

Are you trying to import a .yfx file exported from Yellowfin? Are the export and import systems running on different databases?

Is the other system you're using running on a different database?

It does look like it's trying to convert the timestamp from yyyy-mm-dd hh:mm:ss[.fffffffff] but is unable to do so.

I look forward to your response.

Kind regards,

Chris

photo
1

Hi Chris,

Answers in line below.

Are you trying to import a .yfx file - Yes

Are the export and import systems running on different databases? - The issue happens at the time of loading the file into the browser (Click on Open file > Select File) and then the error shows straight away on the screen, so we don't actually go/finish into the import process

Is the other system you're using running on a different database? - This shouldn't be the issue. I have a TEST and PROD environment with Oracle DB, and another environment with MS SQL DB. The issue happens if we try import an export file from TEST Oracle DB to PROD Oracle DB, but not vice versa. The same export file works when I try to import it in my other environment with MS SQL DB though.

As mentioned, I think the issue is due to the PROD Oracle DB environment. If you try to import any file into your environment with debug on, you can see the stack trace for yourself. In a successful import, the stack trace is as below:

BMC:SR:2020-08-18 16:44:33:DEBUG (MIReportExportImportProcess:loadUploadFileModel) - Entering parseImportFile()BMC:SR:2020-08-18 16:44:36:DEBUG (DBAction:E) - Establishing database connection for sourceId null

What I don't know is what happens in the backend relating to com.thoughtworks.xstream.converters.ConversionException ? Does it have any interaction with the DB at this point since it appears there is nothing wrong with the export file based on my testing.

Also, the java version is 1.8.0_121 and Tomcat 8.5.40.

Let me me know what other information you need.

Thanks,

Nick

photo
1

Hi Chris,

Any update on this?

Thanks,

Nick

photo
1

Hi Chris,

Are you able to share an update regarding this?

Thanks,

Nick

photo
1

Hi Nick,

Apologies in the delay getting back to you.

What are the differences between the PROD and TEST environments? Are they on the same or difference versions of Java, Tomcat, the JDBC driver and Yellowfin?

Have you got a copy of the .yfx file you are trying to import? Could you please also attach the log file with the stack trace.

We've had a couple of reports of this error from other clients but it would be great to gather some more information to see if they are related.

Kind regards,

Chris

photo
1

Hi Chris,

No problem.

Sure, I'll see if I can get the info.

I've also collected the thread dumps but haven't had a chance to analyse it.

I'll try put everything together before uploading them to you.

Thanks,

Nick

photo
1

Hi Chris,

Attached:

  • export files from test/prod (can export from prod, import in test; but not from test to prod; can import both files in a totally different environment I have setup - also, when I say import, I mean select file > open without going into the import process)
  • info_thread
  • debug log showing stack trace from BMC:SR:2020-08-20 11:03:25:DEBUG (MIReportExportImportProcess:loadUploadFileModel) - Entering parseImportFile()

Finally, TEST vs PROD comparison:

  • there are differences in the version of tomcat of Smart Reporting. The tomcat of the production environment is apache-tomcat-8.5.40, and the test environment is tomcat-8.5.
  • The java version is consistent with jdk1.8
  • the database version is 12c
  • the other environment where I am able to import both export files has apache tomcat 8.5.55

Thanks,


Nick

Files: logs.zip
photo
1

Hi Nick,

Thanks for the attached files. I can see there is a difference between the format of the timestamps used to describe the publish times of the views contained in the exports. E.g. PROD using 2014-04-25 14:58:12.0 and the other stored as 2020-08-18 03:26:43 - it being that ".0" making the difference.

Did you say both TEST and PROD are on the same version of Yellowfin? It seems they are connecting to different config databases, I imagine that timestamps are being stored differently between the two.

I'll submit your files to the devs as we have an existing but older ticket open for this issue and see what they come back with.

Kind regards,

Chris

photo
1

Hi Chris,

Thanks for your reply.

Yes, same version but different config db.

Let me know if there's anything else you need.

Thanks,

Nick

photo
1

Hi Chris,

Any luck?

Let me know if you need anything else.

Thanks,

Nick

photo
1

Hi Nick,

Still waiting to get an update on this one and I'll follow up again on it this week, apologies for the delay.

Kind regards,

Chris

photo
1

Thanks for letting me know Chris.

Regards,

Nick

photo
1

Hi Nick,

Finally getting some movement on this one. If you're still encountering this issue, would it be possible to get a DDL dump of your Yellowfin repository database, or just the ReportView table, and the driver that you're using to try to connect?

Kind regards,

Chris