maa best practices for siebel applications on oracle database

Real-World MAA Best Practices for Siebel Applications on Oracle Database

Floyd Manzara Technical Architect Kris Trzesicki Senior Database Specialist

Mehdi Gerami Siebel Product Management Richard Exley Siebel MAA and Exadata

Copyright © 2013, Oracle and/or its affiliates. All rights reserved. 2

Disclaimer

The following is intended to outline our general product direction. It is intended for information purposes only, and may not be incorporated into any contract. It is not a commitment to deliver any material, code, or functionality, and should not be relied upon in making purchasing decisions. The development, release, and timing of any features or functionality described for Oracle’s products remains at the sole discretion of Oracle.


Program Agenda

Siebel Maximum Availability Architecture

Siebel and Active Data Guard

Siebel Testing with Oracle Database Replay

WestJet: Siebel on Exadata

Siebel Performance

Siebel Workload Tagging



Primary Site

SiebelGatewayServer

SiebelFile

System

OracleRAC and

ASM

Secondary Site

SiebelGatewayServer

SiebelFile

System

Oracle Data Guard

OracleDatabase

OracleStandby

Database

DB Servers

File System Replication

OracleRAC and

ASM

Web Servers

Siebel Servers


Oracle RAC and Clusterware Oracle Data Guard Oracle ASM Oracle Flashback Database Oracle Recovery Manager

Best Practices

Database Maximum Availability Architecture

Primary Site Secondary Site

Real Application Clusters & Clusterware

Fault TolerantServer Scale-Out

Online UpgradeUpgrade Hardware and Software Online

Data GuardActive Failover Replica

FlashbackCorrect Errors by Moving Back in Time

Automatic Storage Management

Fault TolerantStorage Scale-Out

Recovery Manager & Oracle Secure BackupLow Cost High Performance Data Protection and Archival

Database Servers Database Servers

Storage Storage


HTTP Load BalancersRedundant Configuration

Web Servers

Siebel Servers

Web ServersLoad Balanced

Clustered Siebel ServersTypically hosting Gateway Server,

Siebel Remote, etc.

Load Balanced Siebel ServersTypically hosting Object Managers, Workflow, etc.

Load Balanced Web Servers Clustered or Load Balanced

Siebel Servers Clustered Gateway Server

Best Practices

Siebel High Availability Architecture


Siebel MAA on Exalogic and Exadata

F5 LTM 4200vF5 LTM 4200v

Primary Site (Site 1)

Siebel Gatewayvm02 and vm05

SiebelFile

System (ZFS)

Exadatadb07 and db08

Secondary Site (Site 2)

Gateway and Siebel Servercn23 and cn24

SiebelFile

System(ZFS)

Oracle Data Guard

OracleDatabase(Exadata)

OracleStandby

Database(Exadata)

DB Servers

File System Replication

Exadatadb01 and db02

Web Servers

Siebel Servers

vm36 vm52

Siebel Servervm47 and vm30

cn21 cn22

Case Study

Virtualized Exalogic X3-2

Bare Metal Exalogic X3-2

Exadata X3-2 Exadata X3-2


Unplanned Outage Testing Results Component Outage Type Outage

(seconds) Error Messages

(% Users) New Login (% users)

Failover Time (seconds)

Siebel Web Server

Instance Failure 0 0.3% 0%

Node Failure 25 2 (partial) 0.3% 0%

Siebel Server Node Failure 0 50% 50%

Gateway Server

Instance Failure 0 0% 0% 30 2

Node Failure 0 0% 0% 100 2

Database Server

Instance Failure 10 (partial) 2% 1 0%

Node Failure 45 (complete) 2% 1 0%

Primary Site Full Site Failure 77 (complete) 100% 100% 77

1 = Mostly addressed by a Siebel product enhancement in Siebel 8.1.1.11 2 = Can be tuned to a shorter time by configuring more frequent monitoring and shorter timeouts


Siebel MAA Best Practices

See “Siebel MAA on Exalogic and Exadata” New! – http://www.oracle.com/technetwork/database/availability/siebel-maa-

exalogic-exadata-2020333.pdf – Detailed steps to establish a Siebel MAA configuration on Exalogic and

Exadata – Detailed recovery steps for unplanned outages – Detailed outage test results – 30 best practices to achieve maximum Siebel availability, including several

new and improved recommendations

http://www.oracle.com/technetwork/database/availability/siebel-maa-exalogic-exadata-2020333.pdf�

http://www.oracle.com/technetwork/database/availability/siebel-maa-exalogic-exadata-2020333.pdf�



Physical standby database open for transactionally consistent read only access Real-time apply of redo from primary resulting in minimal lag Real-time block repair in the event of a block corruption on the

primary Incremental database backup support

Active Data Guard Features


Siebel and Active Data Guard Query Offload to Standby

Primary Site (Read Write)

SiebelGatewayServer

SiebelFile

System

OracleRAC and

ASM

Secondary Site (Read Only)

SiebelGatewayServer

Read OnlySiebel File

System Replica

Oracle Data Guard

OracleDatabase

Oracle Active Data Guard

StandbyDatabase

Database Servers

File Synchronization

OracleRAC and

ASM

Read/WriteSiebel Users

Read OnlySiebel Users

Siebel Servers

Web Servers

Real-time Redo Apply

Read Only Siebel App

Query Offload from Primary


Oracle Data GuardPrimary Site (Read/Write)

SiebelGatewayServer

OracleRAC and

ASM

OracleDatabase


SiebelGatewayServer


StandbyDatabase

OracleRAC and

ASM

Read/WriteSiebel UsersRead/Write

Siebel Users


San Francisco

Beijing

Siebel and Active Data Guard Faster Queries for Remote Users

Fast Queries for

Remote Users

Real-time Redo Apply



Would a read only Siebel application be useful for you? To offload work from the primary? To improve query performance for remote users? What else?

Opinion Poll

Oracle Data Guard

Primary Site (Read/Write)

SiebelGatewayServer

OracleRAC and

ASM

OracleDatabase


SiebelGatewayServer


StandbyDatabase

OracleRAC and

ASM




San Francisco

Beijing

Primary Site (Read Write)

SiebelGatewayServer

SiebelFile

System

OracleRAC and

ASM


SiebelGatewayServer

Read OnlySiebel File

System Replica

Oracle Data Guard

OracleDatabase


StandbyDatabase

Database Servers

File Synchronization

OracleRAC and

ASM



Siebel Servers

Web Servers

?



Challenge: The S_USER and S_SSA_ID tables are always updated by the Siebel, even when the users are only performing queries Solution:

1. Create a “dummy” read/write database for S_USER and S_SSA_ID 2. Create a separate “RO” table owner in the Siebel database:

S_SSA_ID and S_USER are database links to “dummy” All the other tables are synonyms of the real tables

3. When running against the Active Data Guard standby, Siebel configured to connect to the “RO” table owner

The Challenge and a Potential Solution Experimental and not currently supported!


Production

OracleDatabase

Test System

Replay Clients

Siebel Testing with Oracle Database Replay Oracle Database Replay Capture and Replay Workflow

Workload Capture

Pre-processing

Workload Replay

Analysis & Reporting

Real Production Workload

Cross Platform

Cross Version



Siebel 8.1.1.9 Oracle Database 11.2.0.3 33,000 concurrent simulated Siebel users 333 GB workload captured over a 4 hour period 350 million user calls, 19 million transactions Successfully replayed on test system

Results in Our Lab



See “Oracle Database Real Application Testing User's Guide” for more details on Oracle Database Replay:

– http://docs.oracle.com/cd/E11882_01/server.112/e41481/toc.htm See white paper “Siebel on Exadata” for best practice for running

Oracle Database Replay with a Siebel workload: – http://www.oracle.com/technetwork/database/features/availability/maa-wp-

siebel-exadata-177506.pdf

Best Practices

http://docs.oracle.com/cd/E11882_01/server.112/e41481/toc.htm�

http://www.oracle.com/technetwork/database/features/availability/maa-wp-siebel-exadata-177506.pdf�

http://www.oracle.com/technetwork/database/features/availability/maa-wp-siebel-exadata-177506.pdf�

Floyd Manzara [email protected]

Kris Trzesicki

[email protected]

WestJet: Siebel on Exadata

WestJet: Overview

THE AIRLINE INDUSTRY IS TOUGH “If I’d been at Kitty Hawk in 1903 when Orville Wright took off, I would have been farsighted enough, and public-spirited enough – I owed this to future capitalists – to shoot him down.”

- Warren Buffet

WestJet: Overview

Adler Aviation Aeropro Air Canada Air Canada Jazz Air Canada Jetz Air Creebec Air Express Ontario Air Georgian Air Inuit Air Labrador Air Mikisew Air North Air Nunavut Air Saguenay Air Satellite Air Southwest Air Tindi Air Transat

Aklak Air Alberta Citylink Aldair Aviation Alkan Air Alta Flights Arctic Sunwest Charters Bar XH Air BCWest Air Bearskin Airlines Brock Air Services Buffalo Airways Calm Air Canadian Air Taxi Canadian Metro Airlines Canadian North CanJet

Cargojet Airways Central Mountain Air CHC Helicopter Cloud Air Corporate Express Cougar Helicopters Craig Air Enerjet Enterprise Airlines First Air Flair Airlines Green Air Harbour Air Harv’s Air Service Hawkair Helijet Innu Mikun Airlines Integra Air

KD Air Keewatin Air Kelowna Flightcraft Kenn Borek Air Keystone Air Service Kivalliq Air Kootnay Direct Airlines Lakeland Aviation LR Helicopters Inc. Maritime Air Charter Morningstar Air Express Nolinor Aviation Nor-Alta Aviation North Cariboo Air Northern Thunderbird Air Northwestern Air

North-Wright Airways Orca Airways Pacific Coastal Airlines Pascan Aviation Perimeter Aviation Porter Airlines Prince Edward Air Pronto Airways Provincial Airlines Regional 1 Salt Spring Air SkyLink Aviation SkyNorth Air Skyservice Skyxpress Airline Stanton Airways Summit Air Sunwest Aviation

Sunwing Airlines Superior Airways Thunder Airlines Tofino Air Trans Capital Air Transwest Air Universal Helicopters Vancouver Island Air Voyageur Airways Wasaya Airways West Coast Air West Wind Aviation Westex Airlines WestJet White River Air Wilderness Air, ltd

Canadian airlines operating today

WestJet: Overview Canadian airlines graveyard 30000 Island Air Air Alliance Air Atlantic Air Baffin Air BC Air Canada Tango Air Club International Air Dawson Air Nova Air Ontario All Canada Express Austin Airways Baxter Aviation Canada 3000 Canada West Air Canada West Airlines Canadian Airlines Canadian Airways Canadian Colonial Airways Canadian Pacific Air Lines

Canadian Regional Airlines City Express Colonial Airlines Eastern Provincial Airways Fortunair Globemaster Air Cargo Great Lakes Airlines Greyhound Air Harmony Airways Ilford-Riverton Airways Inter-Canadien Jetsgo Knighthawk Air Express Lamb Air Maestro Maritime Central Airways Millardair NAC Airways Nationair Newfoundland Airways

Norcanair Nordair NorOntair North Canada Air NWT Air Odyssey International Ontario Express Pacific Western Airlines Peace Air Pem Air Quebecair Express Queen Charlotte Airlines QuikAir Regal Air Roots Air Royal Aviation Sonicblue Airways Southern Frontier Airlines Time Air Torontair

Transair Trans-Canada Air Lines Trans-Provincial Airlines Triton Airlines Val Air Vision Airways Corporation Vistajet Wardair Western Canada Airways Westex Airlines Wilderness Air LTD. Winnport Worldways Canada World-Wide Airways Zip Zoom Airlines

WestJet: Overview US airlines graveyard – “A” only page…

Air California, later AirCal (1967 - 87, to American) Air Carolina Air Central (Michigan) Air Central (Oklahoma) Air Chaparral (1980 - 82) Air Chico Air Colorado Air Cortez Air Florida (1972 - 84) Air Gemini Air General Air Great Lakes Air Hawaii (1960s) Air Hawaii (ceased Operations in 1986) Air Hyannix Air Idaho Air Illinois Air Iowa

AAXICO Airlines (1946-1965, to Saturn Airways) Access Air (1998 - 2001) ADI Domestic Airlines Aeroamerica (1974 – 1982) Aero Coach (1983 – 1991) Aero International Airlines Aeromech Airlines (1951 - 1983, to Wright Airlines) AeroSun International AFS Airlines Air America (operated by the CIA in SouthEast Asia) Air America (1980s) Air Astro Air Atlanta (1981 - 88) Air Atlantic Airlines Air Bama Air Berlin, Inc. (1978 – 1990) Airborne Express (1946 - 2003, to DHL)

Airlift International (1946 - 81) Air Kentucky Air LA Air-Lift Commuter Air Lincoln Air Link Airlines Air Link Airways Air Metro Air Miami Air Michigan Air Mid-America Air Midwest Air Missouri Air Molakai (1980) Air Molakai (1990) Air Molakai-Tropic Airlines Air Nebraska Air Nevada Air New England (1975 - 81)

WestJet: Overview

By the numbers 1996

5 destinations 1 country 3 aircraft

220 WestJetters

2013 87 destinations

18 countries 100+ 737 aircraft 9,600 WestJetters

10 code-share agreements 33 interline partnerships

1,300 resumes each week 432 marriage proposals

17 million guests Our new regional airline: WestJet Encore

WestJet: Business Case

• By 2016, to grow Guest Self Service to 60% – Multi-channel shopping and reservation features – Enhanced ancillary sales

• Implement a database platform that will provide WestJet’s exceptional Guest Experience

– Operational efficiency – Service availability – Performance consistency – Enhanced support – Efficiently utilize Oracle RDBMS licensing

Goals

WestJet: Process – Look to Book

Vacations Hosted

Data Stores

ESB – Web Services

Internet Booking

Guest Applications

Booking Notifications

Flight Stats Rewards Redemption Mobile Services Check-in Identity Vendor Files GDS Functions

Email Delivery

WestNet Employee Apps

Aviation MRO ENS Identity/

Profile Siebel Loyalty

Mobile Channels

Browser Channels

Kiosk Channels IVR

Channels

Other External Partners

westjet.com IVR WestJet Travel Profile Rewards Check-in Employee Self Serve

Reservation GDS

Reservation Applications

Core

Air Car Hotel

Change / Cancel

WestJet: Siebel

• Loyalty – Frequent flyer system - WestJet Dollar & Vouchers – Compensation – Price guarantees, irregular operations

• Guest Profiles • Guest Portal • Member Promotions – Giveaways, etc. • Member Statements • Marketing campaigns – Bulk Email, Vacation Deals • OBIEE

– Analytical reporting for marketing and loyalty programs – Financial reconciliation

Functionality

WestJet: Siebel

• Statistics – 1.2 million Loyalty member accounts – 2.4 million Profiles – 300 agents and 300 portal connections at any given time – 100,000/day batch transactions from 3rd parties

• Versions – 8.1.1.5

WestJet: Consolidation

12.37

10.09

10.09

5.47

3.95

4.06

3.73 3.57

3.05 2.77 2.56

2.48

2.45 2.23 2.02

1.94

57.30

• 25+ servers 2 Exadata • Consolidated 16 DBs

Server Memory

• Oracle Platinum Services • Reduced data center admin needs

WestJet: Siebel Performance

Siebel on HP-UX and EVA storage

• Expert application and database tuning • Customized database statistics • Frequent I/O performance issues • Long running backup • Overlap in heavy batch processing

Siebel on Exadata

• No tuning required post migration – 1 index added • Default Oracle Maintenance statistics used • No I/O performance issues • Faster backup • Batch jobs fit in the allocated windows

WestJet: Siebel Performance

Backup time: 5h (HP) 0.5h (Exadata + Data Domain)

Process HP Average Before Exadata

Average After Exadata

Improvement

Revenue Accounting –Corrections

13.5 min 5 sec 16,200%

Customer Profiles

33 minutes 13 minutes 253%

Revenue Accounting – Daily TX

174 minutes 9 minutes 1,900%

Response time: 0.01 centi-seconds

WestJet: Data Center Replication

Pre-Exadata (2012)

Picture From:

MAA Best Practices Replication Technologies for High Availability and

Disaster Recovery –A Technical Overview

Joseph Meeks, HA\MAA Product Management, Oracle Lawrence To, MAA Development, Oracle

WestJet: Data Center Replication

Western Data Centre

• DC Managed and owned by WestJet • Platinum support on hardware

VM Farm for Siebel

Consolidated Exadata

TAF Connection Pooling

Eastern Data Centre VM Farm for Siebel

Consolidated Exadata

TAF Connection Pooling

Physical Data Guard

DC rented from 3rd party • Platinum support on hardware •

3200 km - Asynchronous Fast Switchover or Failover Simplicity and Performance

Protection from Lost Writes and Corruption

WestJet: IBE - Hybrid Columnar Compression

March 2014 March

2013

April 2013

March 2014

+ 55 GB + 1.1 TB

RESVCOMPADDITINFO

1 2 3 4 …

Partition 1 Partition 2 Partition 3 Compress for archival

Compress for query No compression

X 170 X 50

WestJet: IBE - Hybrid Columnar Compression

• Technology is unique to Exadata • No additional license cost • Partitioned tables will guarantee performance • Delay additional storage purchases

• Decreased network requirements for replication

Hint 1: Find right data and partition by frequency of data updates 54 GB 0.32 GB Archive

34 GB 0.68 GB Query

Disk space saved : 87 GB

Hint 2: Use DBMS_REDEFINITION for partitioning

WestJet: Future

• Siebel 8.2.2.3 – 3rd Qtr. 2013 • Siebel HCC (1-2 Million/Week) – 4th Qtr. 2013 • Memory Optimization – September 2013 • Purchasing two additional ¼ Rack X3-2 – 1st Qtr. 2014

– Additional Siebel Functionality Travel Agent Commission – 2013 Call Center CTI integration and Case Management - 2014

– Revenue Management - 2013 – BI Analytics Initiative – 2014 – Other Tier 1 database consolidations … - 2013/2014

• Active Data Guard / Golden Gate - 2014

WestJet: Benefit Summary

• Exadata: A platform that enables WestJet’s exceptional Guest Experience – High Availability and Performance – Exceptional Oracle support

• Consistent patching practice and schedule

• Cost avoidance of additional hardware and software

• Time to Market benefits – Initial build and configuration – Performance Load testing

• Smaller Data Center footprint

WestJet: Resources

WestJet Oracle Exadata Technical Case Study http://www.oracle.com/technetwork/server-storage/engineered-systems/exadata/index.html

WestJet Video

http://medianetwork.oracle.com/media/ Search: WestJet

http://medianetwork.oracle.com/media/�


Siebel Performance


Siebel on Exalogic - Exadata Benchmark

Siebel benchmarks on Exalogic X3 – Exadata X3: – Call Center & Order Management Results are available and presented in

later slides Exalogic & Exadata provide an excellent scalable platform for all Siebel

tiers Note:

– Performed on Siebel Release 8.1.1.10 using Oracle 11.2.0.3 – Siebel preferred version is 8.1.1.5 onward (8.1.1.4 is also certified).


Exalogic X3 (Siebel App Server)

Exadata X3 (Siebel DB) OATS-OLT Web Server +

Siebel Gateway

IB Network

IP/IB

Dual CPU 8-Core 256 - 768 GB RAM

(16-48 cores - 1-3 nodes)

Dual CPU 8-Core 256 GB RAM

(16-core – 1 Node)

Dual CPU 8-Core 96 - 288 GB RAM

(16-48 cores - 1-3 nodes)

Siebel Performance Testing Architecture


Test Workloads – Call Center Call Center Use Case

– Siebel Finance used as Reference Application

– Benchmark simulates multi-user Call Center Agents

OATS-OLT Scripts – Sales:

Create Contact and Opportunity

Lookup Account, Associate Contact & Opportunity

Add products and create Quote and Order

– Create Service Request :

Lookup Contact

Create Service Request and add Entitlement

Lookup Account, associate contact & opportunity

Add products and create Quote and Order

– Update Service Request :

Lookup Service Request

Add Solution for the Service Request


Exa* 13k & 39k Users Call Center Benchmark2 Each Exalogic node can

host 13,000 Call Center users Exalogic and Exadata

demonstrate linear CPU and performance scalability

*13k Users benchmark 1 Siebel App Server 33k Users benchmark 3 Siebel App Server

2 Actual results may vary, based on a broad range of implementation-specific factors, such as transaction mix, hardware platform, network parameters, and database size. Oracle does not warrant or guarantee that customers will obtain the same or similar results, even if they use the same or similar equipment and/or software applications. Oracle does not warrant, endorse, or guarantee any performance of any products, any results desired or achieved, or any statements made within this document.

Number of Call Center Users 13,000 Users 39,000 Users

Siebel App Servers Avg. CPU* 72.56% 73.03% Siebel App Mem (MB) 105,636 108,821 DB Server CPU 9.51% 26.60% Web Servers Avg. CPU 19.02% 17.14% Avg RT (sec): 0.049 0.046

Entity1 Creation/hour Creation/day - 8 hours Contacts 113,124 904,992 Opportunities 113,244 905,952 Orders 113,016 904,128 Activities 742,170 5,937,360 Service Requests 148,436 1,187,488 Resolution Items 120,120 960,960

1 The total number of records created are ballpark figures. During the benchmark there are significant number of queries and updates that are not reflected in the table on the left.


Test Workloads – Order Management Order Management Use Case

– Siebel Communications used as Reference Application

– Benchmark simulates multi-user Call Center Agents

OATS-OLT Scripts

– Create Order:

Create Account and Address

Lookup Catalog and Price List

Create Order and Asset

– Modify Order:

Lookup Account and Asset

Lookup Catalog and Price List

Modify Order and Asset


Exa* 11k Users Order Management Benchmark2 One Exalogic node can host more than

7,000 Order Management users Siebel DB Server on Exadata

demonstrates 2 times better in CPU usage compared to standard HW

The Response Time (RT) is 2 times better compared to standard HW

Exalogic - Exadata provides an excellent scalable platform for all Siebel tiers

2 Actual results may vary, based on a broad range of implementation-specific factors, such as transaction mix, hardware platform, network parameters, and database size. Oracle does not warrant or guarantee that customers will obtain the same or similar results, even if they use the same or similar equipment and/or software applications. Oracle does not warrant, endorse, or guarantee any performance of any products, any results desired or achieved, or any statements made within this document.

No. of Users 7000 Exalogic/Exadata Siebel App Server Avg CPU 68.27% Siebel App Mem (MB) 94,179 DB Server CPU 7.04% Web Server Avg CPU 6.21% Avg RT (sec): 0.137

Entity 1 Creation/hour Creation/day (8 hours) ORDERS 49,000 392,000 ORDER ITEMS 285,000 2,282,000 ASSETS 255,000 2,040,000

1 The total number of records created are ballpark figures in 10k users benchmark. During the benchmark there are significant number of queries and updates that are not reflected in the table above.


Proven Best Practices for Scalable Deployment

Minimize scripting & customization – Stay close to the Out-Of-The-Box where feasible – Use Siebel features instead

Workflow can be used to encapsulate complicated business logic – Available from anywhere in the Siebel application – Available from outside application

Integration – Siebel is primarily a CRM system, not an integration hub – Best performance is always achieved by performing transformation and routing in

the middleware – Asynchronous messaging yields significant better performance


Proven Best Practices for Scalable Deployment

Siebel Gateway fix is a must for large scale deployments – Major improvement for Siebel Server start up and recycling – Please see the Alert (MOS - Doc Id 1450272.1) – Example: The first large customers using this fix see Siebel Enterprise Startup

from ~2 hrs 40 mins down to ~ 15 mins

Siebel Connection Pooling reduces number of database connections There are 2 important QF (See MOS)

– For majority of cases 1:2-5 ratio (1 connection for 2-5 users) The 1:1 ratio keeps the connections which reduces significantly the cost of

reconnection – For eAI, eProdCfg, and WFP 1:1-3

Siebel Infrastructure


Best Practices for Scalable Deployment

Eliminate or reduce the use of expensive queries: – Case-Insensitive queries – Sorting important data sets – Search specs generating large result sets

Tune the database – Please see Doc ID 781927.1 on MOS

Review and tune slow running queries – Siebel SQL Tagging in development – Workload Tagging in performance testing and in production

Database and Query Tuning


Best Practices for Scalable Deployment

Be prepared to handle ad-hoc queries in production Some long running queries are part of user transactions and must

not be killed – Otherwise, users will restart

Once a query is killed, it could restart depending on the OM settings Providing well-tuned PDQs could address certain of the above

challenges

Database and Query Tuning


Siebel Workload Tagging


Business Benefits Siebel Workload Tagging adds significant monitoring capability to track

SQL statements being issued by any Siebel OM-based component Provides significant visibility to DBAs and Siebel Administrators into

causes of poor performance through: – Oracle Enterprise Manager – Best way – V$SESSION and certain other V$ DB Views (using direct SQL queries against

Oracle DB) – Cumbersome and time-consuming

User tracking for auditing purposes User Name is maintained across all tiers even when using:

– LDAP – Connection Pooling


Workload Tagging for Production When workload tagging is enabled, SQL statements generated by any

Object Manager-based component are tagged with workload tagging attributes. The DML SQL statements options are:

– SELECT – INSERT, UPDATE, DELETE – SELECT, INSERT, UPDATE, DELETE

The values for these attributes are: ■ CLIENT_IDENTIFIER: Component Name, Server Name, Task ID, User ID, SARM ID ■ ACTION: Business Component Name [primary BC if more than 1] ■ MODULE: View Name NOTE: The length of the attribute values above is limited to 64 bytes for CLIENT_IDENTIFIER, 32 bytes for ACTION, and 48 bytes for MODULE.

Truncation occurs when the length exceeds these limitations.


Workload Tagging for Production Available in Siebel 8.1.1.9 & 8.2.2.3 onward

Currently available for Oracle Only

Lightweight:

– Our performance testing shows 2-3% of CPU overhead on the DB Server – The overhead on the Siebel Servers was found to be insignificant (< 1%)

Can be set dynamically at run-time


Enabling Workload Tagging

Description for OCI SQL Tagging Levels

0 Workload tagging is disabled.

1 Workload tagging is disabled. This is the default setting.

2 Workload tagging is enabled only for SELECT statements.

3 Workload tagging is enabled only for INSERT, UPDATE, and DELETE statements.

4 Workload tagging is enabled for SELECT, INSERT, UPDATE, and DELETE statements.


Workload Tagging for Production Oracle Enterprise Manager (OEM) is The best way to use Siebel

Workload Tagging: – On the Home page Scroll down and click on "Top Activity“ – Check the "Top Session" and click on "Session ID" corresponding to Siebel

application running tasks – It opens "Activity" page for this "Session ID". – Click on "General" tab and OCI attributes and values will be displayed.

Remark: Alternatively, you can use SQL Plus or similar tools to query the Oracle database

V$SESSION and certain other V$ DB views to look up the CLIENT_IDENTIFIER, ACTION, and MODULE attributes by using SQL_ID of the SQL statement


Finding the Source of BAD SQL in Siebel


Siebel SQL Tagging vs Workload Tagging

Piggyback extra column in queries that includes Siebel OM context SELECT T6.CONFLICT_ID, T6.LAST_UPD, …, :CONTEXT FROM … WHERE …

Turned on & off via a Siebel parameter Siebel OM Context Passed

Component Name, Server Name, Task Id, User Id, SARM Id, Business Component Name, Applet, View Name

Example: The following is written into Object Manager log file SCCObjMgr_enu,SDC78450svod,11534352, SADMIN, 0000022b4aaee054:0,Visible Contact List View

Siebel SQL Tagging is exclusively for development phase


Siebel SQL Tagging vs Workload Tagging

Exclusively for development phase – To troubleshoot customizations generating poor SQL statements – Could be combined with SQL log level to obtain the fetch time – Useless in production – Millions/Billions of log file entries

Significant overhead and log file size Advantages

– Cross DB Platform – Available since Siebel 8.1.1.2

Limitations – Bulks up every query result – Not always on – Not integrated into Oracle tools – Stored Outlines and SPM Plans will be affected by activating this features

Siebel SQL Tagging is exclusively for development phase


Summary of Oracle Database Best Practices

Deploy the Siebel Maximum Availability Architecture

Use Oracle Database Replay for Siebel Testing

Apply our Performance Tuning Best Practices

Use Siebel Workload Tagging


Graphic Section Divider

maa best practices for siebel applications on oracle database

Documents