Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Upgrade to the latest JDBC driver available

In general, this is the first thing you should attempt to solve your db problems: get the latest JDBC driver available and install it in the framework/entity/lib/jdbc folder.
Many issues will disappear if you use a recent driver.

How to set the format of Timestamps

If you are getting errors about "ORA-01843: not a valid month" for example when OFBiz tries to update the JobSandbox entity, this is caused by the default format Oracle uses for Timestamp fields; unfortunately there is not a way (that I'm aware of) to pass the Java Timestamp format (that is the one used by OFBiz) to the JDBC driver.

...

Thanks to Giorgio Tomaselli for this script.

How to set the format of Dates

If you are getting errors about "ORA-01861: literal does not match format string", this is caused by the default format Oracle uses for Timestamp fields; this is a problem with the date conversion.

...

You would also be interested in OFBIZ-1001.

How to avoid NLS related errors

By default the OFBiz's startup scripts only set the user.language JVM property; however if you are getting errors by the Oracle driver about unknown locale (NLS), it can be fixed by setting the user.country JVM property (you can do this in the OFBiz start script):

-Duser.language=en -Duser.country=US

How to deal with startup warnings about missing tables/columns/keys

You can safely ignore the warning messages.

...