Background
Reports having large number of records might not print successfully when the user clicks on print button in PDF format.
Solution
Go to “SiebelAnalyticsData\web\config\instanceconfig.xml” file. Put in the following tags after Javahome tag (JavaHost)
(PDF)
(InputStreamLimitInKB) 0 (/InputStreamLimitInKB)
(/PDF)
(/JavaHost)
Please replace ( with < and ) with > in the above solution
The default value for the InputStreamLimitInKB is 1024. This limit puts a restriction in printing a report (which has a very large number of records) in PDF format. By setting it to 0, the limit can be deactivated and so all the records can be printed. http://www.siebeldigest.com/
Background
In an environment where the Siebel Analytics Server (SAS) connects to an Oracle 9i database, the SAS stops responding and may also crash after some time, in any one of the following ways:
Siebel Analytics Web starts hanging after a few hours and new users are unable to login into Siebel Analytics Web.
Administrators cannot log into the Siebel Analytics Administration Tool in online mode.
The Siebel Analytics Server may crash. This is a random crash and happens when multiple threads are doing OCILogon() simultaneously. It is not always reproducible; you may run the test case multiple times before the crash occurs.
The only workaround is to restart the Siebel Analytics service.
This behavior is related to Oracle 9i versions and not to Siebel Analytics. Therefore, this behavior is observed on all versions of Siebel Analytics where Oracle client 9i is used.
Oracle has identified an issue with the Oracle OCI client which may cause the SAS to crash; the Oracle client which resides on the same machine as the SAS is unable to handle a number of concurrent threads to the backend Oracle database. Oracle has isolated the problem within the network layer of the client, and this behavior is fixed in the Oracle client 10g.
Solution
To resolve this behavior, here are the different options:
Use Oracle client version 10g on the SAS machine. NOTE: Oracle supports Oracle client 10g with Oracle 9.2.0x RDBMS. Also note that Oci 10g has not been certified with Analytics 7.7.x, only with Analytics 7.8 but this should not cause any issues, although Oracle recommends that you upgrade Analytics to the latest 7.8 release at your earliest convenience.
Use Oracle client version 8.1.7.4 with its latest fix pack on the SAS machine (8.1.7.4.6 for Windows, and 8.1.7.4 for UNIX).
If neither of the options 1 or 2 is feasible, and you are using Oracle client version 9i, use the following workaround:
In the Oracle database client version that has the behavior, explicitly set the following parameter in the sqlnet.ora file, located in the %ORACLE HOME%\ora92\network\admin directory:
SQLNET.AUTHENTICATION_SERVICES=(NONE)
If this entry does not exist in the sqlnet.ora file, you will need to create it. Please ensure that there are no typographical errors in the sqlnet.ora file after you have added the specified parameter setting. This workaround does not have a performance impact. http://www.siebeldigest.com/
Background
Implementing Usage tracking, using direct insertion method
SolutionSiebel Configuration
If data insertion process does not work properly for Usage Tracking, do the following:
1. In the RPD, make a separate database object with a dedicated connection pool for insertion into S_NQ_ACCT table, i.e. only S_NQ_ACCT physical table will exist under this database object.
2. Check the connection pool properties, the 'Data source name' should be the TSN name, and the call interface is specified as OCI (in case of oracle db).
Note that the error details are recorded in NQServer.log, this would help in tracking the cause of the insertion failure.
Some of the Object types and properties are not listed in web client mode i.e. they are hidden in Tools.
Example for Object Type Applet the properties like Background Bitmap Background Bitmap Style Browser Class Height HTML Popup Dimension Popup Dimension Text Style Width are hidden and cannot be viewed. WORKAROUND:
In Tools.cfg for parameter ClientConfigurationMode set the value to All.
By default it is web, by changing the value to all we can view hidden object type and hidden properties. http://www.siebeldigest.com/
i) In Siebel Tools, select Applet in the Object Explorer (OE). ii) Select the desired list applet in the Object List Editor (OBLE). iii) Select Control in the OE. iv) In the Controls pane of the OBLE, configure the ToggleListRowCount control as follows:
Field
Parameter
Control
ToggleListRowCount
HTML BitMap
BTTNS_MORE
HTML Display Mode
EncodeData
HTML Type
Link
Method Invoked
ToggleListRowCount
Sort
TRUE
v) Select Applet Web Template in the OE. vi) Perform these steps for both the Base and Edit List mode in the OBLE. vii) Select Applet Web Template Item in the OE. In the Applet Web Template Items pane of the OBLE, configure the ToggleListRowCount control as follows: