As you can see, when you click submit, Oracle identity will go to the reports.do URL though a blank screen will be repsented

DEBUG,21 Sep 2012 14:27:19,035,[XELLERATE.DATABASE],select * from lku where upper(lku_field) in ('USER_LOGIN', 'FIRST_NAME', 'LAST_NAME', 'ACCESS_LEVEL', 'RESOURCE_STATUS', 'RNUM') and lku_type='f'
DEBUG,21 Sep 2012 14:27:19,039,[XELLERATE.SERVER],Class/Method: tcDataBase/eventPreInsert entered.
DEBUG,21 Sep 2012 14:27:19,039,[XELLERATE.SERVER],Class/Method: tcDataBase/tcDataBase left.
DEBUG,21 Sep 2012 14:27:19,039,[XELLERATE.SERVER],Class/Method: tcDataBase/eventPreInsert entered.
DEBUG,21 Sep 2012 14:27:19,039,[XELLERATE.SERVER],Class/Method: tcDataBase/tcDataBase left.
ERROR,21 Sep 2012 14:27:19,043,[XELLERATE.WEBAPP],Class/Method: ReportAction/displayTabularReport encounter some problems: {1}
Thor.API.Exceptions.tcColumnNotFoundException
at Thor.API.tcMetaDataSet.getColumnType(Unknown Source)
at com.thortech.xl.webclient.util.ReportUtilities.populateTableDataForTabularDisplay(Unknown Source)

The error is not to do with the input, but in fact the return values of the query. I can think of 2 possible reasons:

1.Check if your SQL query is pulling the same number of columns as your return column.
If you carefully review this Oracle post, you can see the individual has Contractor_Id and USR_STATUS return values within his report though both are missing from his SQL query within his store procedure.

2. Make sure the naming convention of the return values EXACTLY matching your SQL query from within your store procedure
As you can see from this picture, I have taken a snippet of the SQL query and confirmed they match the returning report values.

If you review back to the logs, you will see something similar displaying a load of values

where upper(lku_field) in ('USER_LOGIN', 'FIRST_NAME', 'LAST_NAME', 'ACCESS_LEVEL', 'RESOURCE_STATUS', 'RNUM') and lku_type='f'

These values correspond to the return values from within the report, these values must also be within your store procedure, as demonstrated from the image.

This means that the user (xelsysadm) cannot see the store procedure. When you execute the 'create or replace' store procedure, make sure you are executing this as xelsysadm within the sqldeveloper, not with an individual like sys or sysadm.

About the author