This content has been marked as final. Show 4 replies
This maybe helpful to trace the error:
I checked this but the problem is only in reports 6i and not in TOAD or SQL. Reports trace gave me the same error in the trace file nothing in detail which could be useful.
Any ideas why this error is only on reports builder?
I had the same issue few years back, query was woking in toad but not in Oracle Reports. A ticket was raised for the DBAs and they fixed the issue. How? I don't have any clue. Maybe they fixed the policy function. On my side i just gave them the table name which was raising this error. If you have any other enviroment like Development, Test, etc, log in to that environment and check if report still raises this error. When i had this issue, only one database was raising this error, all others were fine (by using report builder).
Thank you for your response. As you said it worked in other Dev and Test environments and problem was only in Prod environment. My DBA's didn't fix the problem, but I made the changes in Dev instance and ran the complied version on PROD. IT WORKED!!!!!
Thank you so much for your help !!!!