Troubleshooting
Problem
When the WebSphere Adapter for JDBC retrieveAll operation is not able to retrieve the record for a child business object from the database, warning messages get logged in the trace file.
Symptom
If the business object contains a large number of child business objects, warning messages are logged for every missing record for a child business object. As a result, a large number of warning messages may get logged if the parent business object contains a large number of child business objects, and the JDBC Adapter is not able to retrieve the corresponding records from the database.
Below is a sample warning message that gets logged in the trace file:
-------------------------------------------------------------------------------------------------------------------------------------
[20.3.2013 8:39:26:977 CET] 00000087 JDBCRAResourc W
com.ibm.j2ca.jdbc.commands.JDBCRetrieveCommand doContainerRetrieve No
records were retrieved for the Table_Jdbc_key
[20.3.2013 8:39:27:039 CET] 00000087 JDBCRAResourc W
com.ibm.j2ca.jdbc.commands.JDBCRetrieveCommand doContainerRetrieve
CWYDB0806W: The Retrieve operation found no matches in the database for
the child business object, Jdbc_key, with the given key value or
values. Explanation=No matching rows were detected in the database for
the child business object with the given key values. This is not an
error condition. The message indicates that there are no child objects
matching the key values provided. UserAction=This warning can generally
be ignored. However, if you expect child objects to be retrieved, check
the database rows to ensure that the keys match and that records exist
in the appropriate tables.
Resolving The Problem
Warning messages are getting logged in the trace file to inform the user that a child business object record is missing in the database. In some scenarios, it is very important for the user to know that the Adapter was not able to retrieve the record from the database for a child business object. If, in your environment the absence of a child business object record is a normal scenario, and you do not want the messages to get logged in the trace file, and increase its size, you can change the trace level to "SEVERE". For this you will have to set the trace string to "com.ibm.j2ca.*=SEVERE". This will prevent any warning messages from getting logged.
Was this topic helpful?
Document Information
Modified date:
15 June 2018
UID
swg21634479