+ Cannot get the result set metadata.
SQL statement does not return a ResultSet object.
SQL error #1: DB2 SQL error: SQLCODE: -206 SQLSTATE: 42703, SQLERRMC:
ASDF
SQL error #2: DB2 SQL error: SQLCODE: -727,SQLSTATE: 54098, SQLERRMC:
2:-200:42703:ASDF
SQL error #3: DB2 SQL error: SQLCODE: -727,SQLSTATE: 50098, SQLERRMC:
2:-200:42703:ASDF
Additional information about the error might be found in the SQLERRMC file.
If you experience SQL errors, try generating the report with a different set of
parameters. If all executions of the report generate SQL errors, it is likely that, for
some reason, the running report is not compatible with your database.
Message “SQL Statement does not return a ResultSet object”
displayed
In this scenario, the report generation process fails to produce a report and this
error message will be displayed:
SQL Statement does not return a ResultSet object
This message is followed by some SQL codes and the name of the table or view
that is absent.
This message is displayed when the tables and views from which data is to be
extracted do not exist in the database. To view the SQL query that generated this
problem and determine what historical data is not being collected, review the log
files. See “Locations of log files” on page 245 for the locations of log files.
Your report fails to generate with unexpected error messages
displayed
About this task
In this scenario, you have defined report parameters for an OMEGAMON XE or
NetView
®
for z/OS report and clicked Run. After a long wait, these messages are
displayed:
Processing has ended because of an unexpected error.
See the Tivoli Common Reporting log files for more information
Procedure
These error messages are generated by Tivoli Common Reporting and might
indicate that you need to increase the default heap size for the JVM on the java
command to start the Tivoli Common Reporting server. To confirm that this is the
problem, do the following:
1. Open the SystemOut.log file, found in this location: On Windows Systems:
<tcr_install_dir>/tcr/eWas61/profiles/tcrProfile/logs/tcrServer/
2. Confirm that this line can be found: An OutOfMemory error happened while
running the report. If you find this line, do the following to correct this
problem:
3. Stop Tivoli Common Reporting.
250 IBM Tivoli Monitoring: Troubleshooting Guide
To Next Page
Loading...
Need help?
General
