BIP Troubleshooting Steps

Process behind execution of Reports
Purpose: The Reports Business Service enables BI Publisher reports to be executed from the Siebel application via a Workflow Process, or through scripting. The report is generated in the background by connecting to the BI Publisher server. The report output is stored in the Siebel File System and accessed from the My BI Publisher Reports view. The Reports Business Service can not be executed on the Mobile Web Client.
Vanilla Siebel Report Business Service was not configured properly. We had issue in seeing Reports from Siebel UI. This issue is also for Vanilla Reports. When we check in Support Web found an SR which is reconfiguring Report business Services and performed the steps specified in the link below.
https://support.oracle.com/CSP/ui/flash.html#tab=KBHome(page=KBHome&id=()),(page=KBNavigator&id=(bmDocDsrc=DOCUMENT&bmDocTitle=Siebel%20BI%20Publisher%20Reports%20Business%20Service&viewingMode=1143&bmDocID=823360.1&from=BOOKMARK&bmDocType=BULLETIN))

Troubleshooting Errors While Running Siebel Reports (SBL-OMS-
00203)



To troubleshoot errors while generating Siebel Reports
1. Make sure the XMLP Report Server server component is enabled.
2. Increase the XMLP Report Server server component log level to 5 to create a more detailed log file.
3. Copy the xdodebug.log file to the jre\lib directory.

Additionally, you might encounter an instance where a layout template was registered with one database, but you generated it with a different database, and the generation fails. If this error happens, you must complete the following task.

To regenerate and rerun the report
1. Regenerate the XML data.
2. Reregister the layout template.
3. Regenerate the report.






Troubleshooting Errors while Uploading reports.



The above error may cause for two reasons:
Reason 1: Check for BI Publisher Server with administrator privileges as below

1. Log in to the Oracle BI Publisher Server with administrator privileges
2. Click the Admin tab, and then select Security Configuration (under Security Center).
3. In the Security Model section, check the following
o Model: Siebel Security
o Check the host name and port as the Web Service Endpoint.
o Chesk the Siebel administrator credentials

Reason 2: If the Report Uploaded for second time

Need to delete the report from BI Repository, re-register the report after deleting it from repository and the upload the file.

Resolving Class Not Found Errors




1. Navigate to the Administration - Server Configuration screen, Enterprises, and then the Profile Configuration view.
2. Select the XMLPJvmSubsys profile.
3. For the JVM Classpath profile parameter value in the Profile Parameters subview, Provide a reference to each of the JAR files in the CLASSES directory in the Siebel application root directory (SIEBSRVR_ROOT/CLASSES).

For example, you might enter the following value:

\siebsrvr\CLASSES\bicmn.jar;\siebsrvr\CLASSES\bipres.jar;\siebsrvr\CLASSES\collections.jar;\siebsrvr\CLASSES\fix6312772.jar;\siebsrvr\CLASSES\i18nAPI_v3.jar;\siebsrvr\CLASSES\jdbc12.jar;\siebsrvr\CLASSES\jewt4.jar;\siebsrvr\CLASSES\MQeBase.jar;\siebsrvr\CLASSES\MQeSecurity.jar;\siebsrvr\CLASSES\share.jar;\siebsrvr\CLASSES\Siebel.jar;\siebsrvr\CLASSES\Siebel_JavaDoc.jar;\siebsrvr\CLASSES\SiebelCustomXMLP.jar;\siebsrvr\CLASSES\SiebelJI_enu.jar;\siebsrvr\CLASSES\SiebelSMQ.jar;\siebsrvr\CLASSES\SiebelXMLP.jar;\siebsrvr\CLASSES\versioninfo.jar;\siebsrvr\CLASSES\xdocore.jar;
\siebsrvr\CLASSES\xdoparser.jar;\siebsrvr\CLASSES\xmlparserv2-904.jar;\siebsrvr\CLASSES\XSLFunctions.jar;.


Troubleshooting Errors while applying fix pack.



Make sure that the Siebel repository pointing to single repository.

Process of Optimizing the Generation Performance of Siebel Reports for Large Data Volumes

Note: This task is applicable only to connected mode.

1. Navigate to the Administration - Server Configuration screen, Enterprises, and then Profile Configuration view.
2. In the Profile Configuration view list, select Server Datasource (alias ServerDataSrc).
3. Scroll down to the Profile Parameters, and then click Advanced.
4. In the Profile Parameters list, select Datasource maximum fetch array size (alias DSMaxFetchArraySize), and then change the value to -1.
5. Restart the Siebel Server.

Create Separate Named Datasource For Siebel BI Publisher Reports With Large Data Volumes

1. Create a new Profile (Named Subsystem) by cloning the existing 'Server DataSource' Profile. You would need to use the Copy Record feature to do that.
2. The new profile can be named as 'Reports DataSource' (Alias RptDataSrc).
3. In the 'Profile Parameters' specify all the parameters same as the 'Server Datasource' profile. Make sure you set the Datasource maximum fetch array size 'DSMaxFetchArraySize = -1'.

NOTE: Match up all the parameters (including Hidden and Advanced)
4. Navigate to the Administration - Server Configuration > Enterprises > Component Definitions view. Query for 'XMLP Report Server' component.
5. Click the drop down Menu and select 'Start Reconfiguration'.
6. In the 'Component Parameters’ list applet query for '*Data Source'.
7. Set the value of the following parameters:
a) OM - Data Source = RptDataSrc
b) OM - Named Data Source name = RptDataSrc,GatewayDataSrc
c) Application Datasource = ServerDataSrc
8. Click the drop down menu in the 'Component Definitions' applet and select 'Commit Configuration'.
9. Hit the 'Synchronize' button under the 'Component Definitions'
10. Restart Siebel Server and Gateway Services.
11. Log into the Siebel Application as Siebel Administrator and ensure that the XMLP Report Server component is 'Online'.
12. To ensure that the new parameters are in effect:
- Navigate to Site Map > Administration - Server Configuration > Servers >Components
- In the Component Parameters list applet query for '*Datasource'
- Verify the following parameter values:
a) OM - Data Source = RptDataSrc
b) OM - Named Data Source name = RptDataSrc,GatewayDataSrc
c) Application Datasource = ServerDataSrc