SBL-DAT-00175: Database connection was lost, please retry.

Applies to:

Siebel Campaigns - Version: 7.7.2 [18325] to 8.1.1.3[21219] - Release: V7 to V8
Information in this document applies to any platform.
This document was previously published as Siebel SR 38-3056714371.

Symptoms

SBL-DAT-00175, SBL-EAI-04376, SBL-MKT-00453, SBL-BPR-00162

We executed our first email program in Production this past weekend. To do so, we scheduled the program stage to automatically load and launch 11 campaigns. During the loading of the 6th campaign, we encountered the following errors:


Method 'Execute' of business component 'Marketing Camp Con' (integration component 'Campaign Contact') returned the following error:
Database connection was lost, please retry.(SBL-DAT-00175) (SBL-EAI-04376)

Error invoking service 'EAI Siebel Adapter', method 'Upsert' at step 'Update Camp Con'.(SBL-BPR-00162)

Error/Warning : The SRM request '1-AUK-BXL' failed during parallel import for the Campaign Load/Analytics Data Load.   One or more of the parallel tasks may have encountered an error. Any queued tasks that were scheduled to follow the failed task have been cancelled.(SBL-MKT-00453)

Error invoking service 'Mktg Data Load Service', method 'CampaignLoad' at step 'Load Analytics Segment'.(SBL-BPR-00162)

We had run into the SRM error in our test environment when executing a program stage that would load and launch a much higher number of emails than this past weekend. Because of this as a precautionary measure, we set the Max # of Records value on the Campaign Load Format to 250.

What causes this error and what steps can we take to fix it?

Cause

.

Solution

It was found that the errors were caused by a maintenance process that was kicked off in the morning on the OLAP database. At the end of the procedure, the process was configured to close all connections to the database. The errors observed were a direct result of this process closing open connections on the database.

Related

---

Products

---

• Siebel > Customer Relationship Management > CRM - Enterprise Edition > Siebel Campaigns

Errors

---

SBL-EAI-04376; SBL-DAT-00175; SBL-BPR-00162; SBL-MKT-00453

Applies to:

Product Release: V7 (Enterprise)
Version: 7.7.2.6 [18372] Com/Med
Database: Oracle 9.2.0.7
Application Server OS: Microsoft Windows 2003 Server
Database Server OS: Compaq Tru64 UNIX

This document was previously published as Siebel SR 38-3354957703.

Symptoms

We had Start/Stop flag errors during optimization. Here are the steps

1 Optimization ran on Sat, but in the middle of running, the database was disconnected.
2 The Optimizer Component was not re-cycled.
3 The next day when Optimizer Load ran. This error appeared in the Optimizer Load log - SBL-DAT-00523. See log file Optimizer_75305.log. The Optimizer Load process ran anyway and reported success.
4 Optimizer also detected this error. see log Optimizer_76676.log

Why did this error occur? I think the DB Crash was why, can you confirm. Also, why didn'toptmizer load and optimize exit and say they failed when this occurred?

Thanks

Solution

Message 1

For the benefit of other users, in customer's case, it is the following scenario:

1. Optimization ran on Sat, but in the middle of running, the database was disconnected.

2. The Optimizer Component was not restarted.

3. The next day click on "Load Optimizer" button. This error appeared in the Optimizer Load log - SBL-DAT-00523:
ObjMgrLog    Error    1    0    2007-05-06 13:07:30    (oracon.cpp (3037)) SBL-DAT-00523: The selected record has been modified by another user since it was retrieved. Please continue.

The Optimizer Load process ran anyway and reported success:
Execution    Trace    3    0    2007-05-06 13:09:15    Method 'ReloadServiceRegion ( 1-9JHS-1 )' succeeded.

4. Then click on "Optimize" button, Optimizer also detected this error and other additional errors:

ObjMgrBusCompLog    Error    1    0    2007-05-06 13:23:17    (oracon.cpp (3037)) SBL-DAT-00523: The selected record has been modified by another user since it was retrieved. Please continue.
ObjMgrSessionLog    Error    1    0    2007-05-06 13:23:17    (physmod.cpp (4661)) SBL-DAT-00175: Database connection was lost, please retry.
Execution    Error    1    0    2007-05-06 13:23:17    Optimization 'Start/Stop' flag update failed
Execution    Trace    3    0    2007-05-06 13:23:17    Method: 'Optimize' End
Execution    Error    1    0    2007-05-06 13:23:17    Error occurred when optimizing the service region.
Execution    Error    1    0    2007-05-06 13:23:17    Method 'Optimize ( 1-9JHS-1 )' failed

...continued...

Message 2

The “Optimization 'Start/Stop' flag update failed” error can also be reproduced in a different way, here are the steps:

1. Click on "Load Optimizer" for the service region; wait until it finishes by checking the Optimizer log to see it is completed.

2. Click on "Optimize" for the service region. An Optimizer task is queued for this, status = QUEUED.

3. Shutdown database server. Wait a minute, and start up database server.

4. The queued Optimizer task now gets executed, and it has the Start/Stop flag error.

Execution    Error    1    0    2007-06-07 15:48:53    Optimization 'Start/Stop' flag update failed

Execution    Trace    3    0    2007-06-07 15:48:53    Method: 'Optimize' End

Execution    Error    1    0    2007-06-07 15:48:53    Error occurred when optimizing the service region.

Execution    Trace    3    0    2007-06-07 15:48:53    Method 'Optimize ( 1-23M9 )' succeeded.

Regardless the behavioral differences, "Optimize" method indeed has a problem with database reconnection when Optimizer component is online, regardless the db connection is lost during or before Optimize method is being executed. The Change Request CR# 12-1K1FVCU has been raised to address this error for Optimizer.