*Here is the description for **Crystal reports Developer with Banking Exp **Position in NY&CHICAGO.*
** *ITS A ONE MONTH PROJECT * ** *RATE :DOE * *SEND THE RESUME TO [email protected] ONLY* Role Description: Crystal Reports Developer Two Locations (NY and Chicago) Language(s): English *******ASSIGNMENT DETAIL***************************************************************** Days per Week: 5 Remote possible: No *******CUSTOMER RELATED INFORMATION****************************************************** Role Location: Chicago, New York, United States Customer Industry: BANKING System/Release/Platform: *******OTHER***************************************************************************** Scope of Tasks: Anyone good in SQLs and knowledge of Crystal Reports/Oracle VPDs will suffice. The client has developed Crystal Reports connecting to VPDs (Virtual Private Database) and regular databases. They want confirmation of VPD SQL commands execution before regular SQL commands. This is not related to custom portal and happens when you schedule the Crystal Report from anywhere (InfoView, portal, etc). Comments: This is some detailed info that i have found out during the debug if this issue and the details. All the Crystal Reports are being developed in Dev and then getting deployed in to DevInt, after the reports are deployed the connection is updated as a `Custom Connection`. As the option for the custom connection is selected for the report, it is assumed that the costume connection is being used to run the report. When we schedule a report as `Run Now` the report fails either with the error message `Information is needed before this report can be processed` or ` Failed to retrieve data from the database`. After doing some research and looking in to some document i came to know this is a known bug based on SAP note: 1207347 for the reports that are having `Custom DB` Detail set in the report. At the same time based on the info that is provided with ADAPT00330091 i tried to update the command properties file with a string `-procReportOptions __forceApplyParamsAfterDBL` and restarted the server to test the reports again. I see some reports refresh and then some still fail with the same error. Our system details are Solaris10, Oracle11 DB with BOEXI3.1(12.1.0.882) We don't have any fix-packs or any other service packs installed. -- You received this message because you are subscribed to the Google Groups "oraapps" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/oraapps?hl=en.
