How is the Loyalty Batch Engine (LoyEngineBatch) Invoked? [ID 1066396.

1]
Modified 20-MAY-2010 Type BULLETIN Status MODERATED

In this Document
Purpose
Scope and Application
How is the Loyalty Batch Engine (LoyEngineBatch) Invoked?
What are the basic setup tasks required for the Batch Engine
How is the Batch Engine started
What are the commonly faced issues with the Batch Engine
Customization Recommendations
Known Issues

Platforms: 1-914CU;
This document is being delivered to you via Oracle Support's Rapid Visibility (RaV) process and therefore has not
been subject to an independent technical review.

Applies to:

Siebel Loyalty Engine - Version: 8.0 [20405] to 8.1.1 [21112] - Release: V8 to V8

Information in this document applies to any platform.

Purpose

This document provides technical details on how is the Loyalty Batch engine is invoked. It covers
the basic setup of the engine, basic troubleshooting steps and a reference to a number of known
issues.

Scope and Application

Basic setups / checklist required for batch engine

How is the Loyalty Batch Engine (LoyEngineBatch) Invoked?

What are the basic setup tasks required for the Batch Engine

1 Define Server key maps under Program->Server Keys

2. Make sure members are assigned a server key before initiating batch processing.
3. Set Min/Max MT servers parameter for component LoyEngineBatch. This should correspond to
the server key mappings definition.
4. Ensure promotion definitions are in place, activated and the program is activated.

5. Point block updates can be optimized to minimize database hits.

Note: For more details, please refer - Siebel Loyalty Administration Guide 8.1 > Getting Started
with Siebel Loyalty >Setting Parameters for the Siebel Loyalty Engine
How is the Batch Engine started

The following steps need to be done to start the batch engine:

• Specify the parameters for batch engine to enable/disable auto start of the batch engine
as mentioned in the Loyalty admin guide.
• Specify the parameter LOYEngineQueueObjects objects to be picked up for processing
and also the duration for which the engine should run.

• Make sure there are at least 2 threads running for each of the processes to ensure batch
processing. More threads can be started depending on the CPU performance and usage.
• To start the threads, you can either use the srvrmgr command line ' Start task for comp
LoyEngineBatch ' or submit a request for the job from the Administration-Server->Jobs
screen.

Note: For more details, please refer - Siebel Loyalty Administration Guide 8.1 > Getting Started
with Siebel Loyalty >Setting Parameters for the Siebel Loyalty Engine

Please refer Following Doc id - How is the LoyEngineBatch Automatically Starting the Desired
Number of Tasks? (Doc ID 874062.1)

What are the commonly faced issues with the Batch Engine

Objects are not being picked up by the batch engine

• Check if the Program is active.

• Check for server key definitions for the members.
• Check for any customizations done on the search specification for the corresponding
business components like LOY Engine Transaction, LOY Engine Member, LOY Engine
Member Tier, LOY Engine Point Block, LOY Engine Bucket
• Check for real-time processing e.g. check processing of the transaction after submitting
the same from the UI. There is a possibility that some setup issue could cause this. If
real-time processing goes through fine, the issue is with server key mappings

Points are not being awarded to processed transactions

• Check the promotion definitions, dates, the criteria expression setups and other
inclusion/ exclusion defined in the promotions.

Threads not starting or die down after starting

This could be a hardware issue with the CPU maxing out. This could also occur with wrong
server key mappings. Check the log files for the particular task to zero down to the error.

Analyzing log files

 • Set the event log level for the Loyalty component to 5.
• In the task logs, search for the messages LPE_Message, ObjectProcessingBegin to
identify the spools for object processing.
• Follow the log from the tags ObjectProcessingBegin to ObjectProcessingEnd to validate
any errors during processing.
• Look for strings Error if the task has crashed
• Loyalty error codes start with "SBL-LTY-.."

Customization Recommendations

For any new field added to the * Engine * BC, make sure the user properties LOY Engine
Activate Field are defined in the corresponding business components.
In case the original search specification has been modified, spool the query and confirm that the
new search spec returns the desired result set.

If the user wants to import the data into loyalty transaction table and then do the validation, it is
suggested that user to create their own BC with the same fields as that of LOY Transaction BC
on S_LOY_TXN or else look for other BC's which are based on transaction table.

Known Issues

• Duplicate transaction processing and incorrect points assignment

Please refer to the Alert 'Loyalty Batch Engine may process Transactions twice and additionally
assign points incorrectly' ( Doc ID 754157.1 ) and CR 12-1R8LQY9.

• Loyalty batch engine processing records twice due to Partial Commit of a Transaction

1. Partial Commit on the Database: This is seen only with Oracle databases. Any failure in the
sequence of the SQL statements executed at the end of transaction processing doesn't rollback
the entire transaction.
2. DB latency issues: This is not platform centric. The symptoms are that the database commit
isn't reflected on the query. That is a query on the database doesn't take into consideration some
database updates that have been recently made.

Please refer to CR 12-1P2S23P

• High concurrency environment numbers are getting corrupted, insert/update fails

Hi-concurrency string corruption: This issue is specific to Linux platforms alone. High
concurrency string to number conversion might not be thread safe. This results in various errors
involving numeric values during transaction processing. Please refer to CR 12-1QD8NXW

• Issues with points Expiry and Cancellation

Please refer to CRs 12-18C53LY, 12-1N22WVZ and 12-1Q5L7UL.

Other Related Documents

• Loyalty Batch Engine task exited with ORA-01000: maximum open cursors exceeded
(Doc ID 1061602.1)
• Crash of Loyalty Real Time Engine and Batch engine while processing Bukets (Doc ID
981622.1)

Attachments

File1 (265.05 KB)

File2 (1,378.08 KB)
Promotion (800.91 KB)
untitled.bmp (1,166.12 KB)
Related

Products

• Siebel > Customer Relationship Management > CRM - Enterprise Edition > Siebel
Loyalty Engine

Back to top
Article Rating Comments
Rate this document Provide feedback for this article. Please use 'Contact Us' for other feedba

Excellent

Good

Poor

Did this document help you?

Yes

No

Just browsing

How easy was it to find this document?

Important Note: this feedback is anonymously visible to other
customers until processed by Oracle Support.
Very easy

Somewhat easy

Not easy
Cancel