We're having some issues when addresses are being sent into OTM. Basically, it throws the error seen below stating that the address is longer than 50 characters. What I don't understand is it looks as if when an address is too long, it wraps it and adds sequence numbers in the table.
In table location_address the location gid will have 3 records with line_sequence 1-3. Why does it appear that some addresses wrap automatically, and some throw this error? What steps can we take to prevent the error?
CAUGHT THE FOLLOWING EXCEPTION WHILE PROCESSING TRANSACTION: glog.util.exception.CreateExceptionWrapper java.sql.SQLException: ORA-12899: value too large for column "GLOGOWNER"."LOCATION_ADDRESS"."ADDRESS_LINE" (actual: 61, maximum: 55) java.sql.SQLException: ORA-12899: value too large for column "GLOGOWNER"."LOCATION_ADDRESS"."ADDRESS_LINE" (actual: 61, maximum: 55)
In table location_address the location gid will have 3 records with line_sequence 1-3. Why does it appear that some addresses wrap automatically, and some throw this error? What steps can we take to prevent the error?
CAUGHT THE FOLLOWING EXCEPTION WHILE PROCESSING TRANSACTION: glog.util.exception.CreateExceptionWrapper java.sql.SQLException: ORA-12899: value too large for column "GLOGOWNER"."LOCATION_ADDRESS"."ADDRESS_LINE" (actual: 61, maximum: 55) java.sql.SQLException: ORA-12899: value too large for column "GLOGOWNER"."LOCATION_ADDRESS"."ADDRESS_LINE" (actual: 61, maximum: 55)
Comment