19 May 2010 09:40:39,332 [SEVERE] USERNAME - [BASE] com.jdedwards.database.base.JDBException: [INCORRECT_CONVERSION_TO_DBFORMAT] Formatting error on converting AN8 of Everest type 9 from OneWorld to database format. com.jdedwards.database.base.JDBException: [INCORRECT_CONVERSION_TO_DBFORMAT] Formatting error on converting AN8 of Everest type 9 from OneWorld to database format.
java.lang.NumberFormatException: Invalid string input - COVENTRY G
Every seen a bunch of these in you JAS logs and wondered what they are about? Well, this is where JDE uses some special logic on a numeric field to do lookups on address book. Some AN8 fields allow you to enter a client name, and it will get converted (like the send message when you can type AN8 or username).
It's a lot of logs for something that should not be an error!!
Subscribe to:
Post Comments (Atom)
-
I’ve enabled auditing many times before. Everytime has been a nightmare. You need lots of space for big tables, this could be done MUCH bet...
-
I’m running windows 7 virtual on OVM with office 2010. Have E1 fat boy and oracle 11G client. I’m using this machine for some BIP prototyp...
-
This is a really handy tool for working out what DD items and tables are in use in JDE. This is a complete cross reference of JDE DD items,...
1 comment:
The amount of stuff in the JDE JAS logs that are marked as [severe] but are normal occurances is silly. Oracle has a list of errors which it considers "normal" or at least you don't have to fix them... makes it tough to dig thru logs for the stuff you want... my personal favorite.
SELInputProcessor.processInput() - Unknown command, null. Ignoring command.
Post a Comment