A Troubleshooting

A.1.1 Changes Made Through opconfig Wizard Do Not Take Effect

Changes made using the opconfig wizard are not effected.

Problem

After using the opconfig wizard to change configuration settings, these settings do not take effect.

Solution

After running the opconfig wizard to create the database schemas, you must restart the OC4J instance named OC4J_BI_Forms in order for the configuration changes made to the web.xml file are recognized. You can restart OC4J_BI_Forms using the Application Server Control Console.

A.1.2 No Recommendations are Returned from the REAPI

If an application invokes recommendations through the REAPI, none may be returned.

Problem

There may be occasions when no recommendations are returned from the REAPI.

Solution

There are valid instances where no recommendations are returned by the REAPI. In such cases, you need to design your application accordingly.

A.1.3 Cross-sell Recommendations are Not Returned

Cross-sell recommendations are not returned.

Problem

Sometimes no cross-sell recommendations are returned.

Solution

When using cross-sell recommendations, the DataSourceType and InterestDimension tuning settings must have the same value. This value can only be "PURCHASING" or "NAVIGATION".

No cross-sell recommendations are returned if the DataSourceType is "ALL". This is because navigation events can only predict clicks, and purchase events can only predict purchases in the current predictive association rules model.

A.1.4 Unable to Determine the Rules Resulting from a Package Build

Rules cannot be determined from a package build.

Problem

Unable to determine rules that result from a package build.

Solution

The number of data mining rules that were generated when a package was last built can be seen by clicking the Result icon of the appropriate package in the Packages tab. The page that appears is the build results page, which shows the statistics for the aggregated model and cross-sell model builds. These statistics include the number of data mining rules generated for each model.

A.1.5 JSP Tags Return Tags that are Not Useful

JSP tags return tags that are not useful.

Problem

The JSP tags return the item ID JSP tags, which are not appropriate for rendering a page. The results from a JSP tag need to be wrapped in a scriptlet to do lookups of what to display. Also, Java FOR loops, which are used to iteratively return the tags, do not belong in a Web page.

Solution

The JSP tags for OracleAS Personalization in the JSP tag library were designed before the Model-View-Controller paradigm became popular and should be avoided. In the future, the REAPI will be integrated into the Oracle Application Development Framework Runtime Libraries.

A.1.6 Error 404 Encountered When Using Administration GUI

Error 404 encountered when using the OracleAS Personalization administration GUI.

Problem

HTTP error 404 is encountered when the browser's "Back" button is used or the browser is navigated away from an OracleAS Personalization administration UI page.

Solution

To avoid 404 errors when using the OracleAS Personalization administration UI, do not use the browser's "Back" button or navigate away from the administration UI Web pages unless you log out of your session. If you encounter 404 errors when returning to the administration UI, you must exit and restart your browser to create a new session.

A.1.7 Scheduled Build Does Not Start

A scheduled build does not start.

Problem

In the event that a scheduled build does not occur (as evidenced when the status of a package build does not change from "Not built" to "Running"), a possible cause could be due to the failure of the dbms_job process. This process checks the build schedule to see when build jobs are scheduled to run.

Solution

If a scheduled package build fails to run, you may need to have your DBA check the status of the dbms_job processes in the MOR and RE accounts. A dbms_job process sets a broken flag if it fails to run 16 times in a row. This failure can be caused by a lack of system resources such as shared memory or disk space. Once the underlying resource problem is resolved, a provided script can be run to assist in resetting the broken flag. The name of this script is:

<ORACLE_HOME>/mp/admin/runbrokenjobs.sql