ReportServer fails to obtain the target procedure's schema from an Oracle package under the "SYSTEM" user

Hi Kim,
Just to be absolutely sure, would you please clarify if your question is related to the MessageBox text formatting only and you do understand the cause of those reported Oracle errors? I am asking this because we do not really handle such exceptions - almost everything you see in the text box is an exception's original message, the one returned by the Oracle .NET provider, not by us. Of course, we're aware that a procedure name might be preceded by a package name, and we always use the dot "." to separate them in our internal code. Moreover, I don't really understand how you managed to create a report in the first place. I mean, when you run through the data source wizard, all the stored procedures you select are executed in the background. Unless your data source schema has been modified, I don't see a way of accomplishing a wizard without stumbling on the same error. If, however, you think my explanation is entirely correct and the issue is related to the way how we handle those routines, please don't hesitate to provide us with the screenshot of your Oracle data model so we can clearly see all the packages/stored procedures defined. The ReportServer logs will be also greatly appreciated. To record any actions before reproducing the issue, stop the Report Server services (a worker and task scheduler) and then make the following changes to the DevExpress.ReportServer.v15.1.TaskScheduler.exe.config and DevExpress.ReportServer.v15.1.Worker.exe.config files:

Code
<rules>  
        <logger name="*" minlevel="Warn" writeTo="file" />  
</rules>  

change to

Code
<rules>  
        <logger name="*" minlevel="Info" writeTo="file" />  
</rules>  

[Posted by Seongjung Kim]
I attached files about my datamodel .
I drew yello line to clarify my package name and procedure name.
And I also attached my Report Server log. There ardWorker and task scheduler log files in zip file .
Please check and let me know what can I do .

Hi Kim,
Thank you very much for the detailed information and provided server logs. I managed to reproduce this behavior on my side. It appears that locating a stored procedure in an Oracle package alters the name of that stored procedure if you're using the  "SYSTEM" account to log into the server, not the account of a user who actually owns this procedure (like 'TW_MIS_EXAM' in your case). I've notified our R&D team of this issue and forwarded this ticket to them for further research. Please bear with us. We'll reply here once we have any results.