While the message does not impact functionality, if you have to read the logs it becomes tedious to scroll past the following over and over:
<BEA-403302> <An unexpected SQL exception occured java.sql.SQLException: ORA-00001:
unique constraint (PORTAL.PK_LEASE) violated.
java.sql.SQLException: ORA-00001: unique constraint (PORTAL.PK_LEASE) violated
at oracle.jdbc.driver.DatabaseError.throwSqlException(DatabaseError.java:112)
at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:331)
Not to mention how the fun of having every person who hasn’t looked at your application before reporting it as a problem or insisting it is the root of a bug you are chasing (it isn’t).
If you have a support account, you can surpress this with the following WLP 10.2 patch:
VZGR | 9AS6D7D9
