SBL-DAT-00395: This operation is not valid when executed in setup only mode.

Applies to:

Siebel Campaigns - Version: 7.7.2.2 SIA [18356] and later   [Release: V7 and later ]
Siebel Marketing - Version: 7.7.2.2 SIA [18356] and later    [Release: V7 and later]
z*OBSOLETE: Microsoft Windows 2000
***Checked for relevance on 29-Nov-2010***
Product Release: V7 (Enterprise)
Version: 7.7.2.2 [18356] Fin Svcs
Database: Microsoft SQL Server 2000 SP3
Application Server OS: Microsoft Windows 2000 Server SP 3
Database Server OS: Microsoft Windows 2000 Server SP 3

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

Symptoms

SBL-DAT-00395, SBL-DBC-00111, SBL-OMS-00203, SBL-MKT-00280

Customer is observing the following behavior when importing a List with over 10,000 records.

1) Performance Degradation
- For an import of 28000 records, the first 10000 records are imported within 4 minutes. The remaining 18000 records are imported in 33 minutes.

2) Memory Leak
- For an import of 20,000 records, memory for the MTS process grows to 2gb. After the task is completed, the memory is not released.
- When performing another list import again, the memory is not released and continue to grow.

Cause

This was determined to be a defective behavior when the "Assign to Campaigns" in the "Additional Actions" drop down is chosen.

Solution

Message 1

The above behavior is happening only when the "Assign to Campaigns" in the "Additional Actions" drop down is chosen.

The behavior is reproducible in Siebel Standard Configuration and there is Change Request (CR) 12-WIJ0UR already logged to address this behavior.

The CR has been fixed on 7.7.2 QF1016 Quickfix, 7.7.2.5 Fix Pack, and 7.8.2.

References

BUG:12-WIJ0UR - RELEASE SQLOBJ FOR POTENTIAL MEMORY LEAK

Applies to:

Product Release: V7 (Enterprise)
Version: 7.7.2.1 [18353]
Database: Oracle 9.2.0.4
Application Server OS: Microsoft Windows 2000 Server SP 4
Database Server OS: HP-UX 11i

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

Symptoms

SBL-DAT-00225, SBL-DAT-00395, SBL-DAT-00498

Hi,

    Whenever we are importing a Multi Byte List (Korean Lists) file through List Management -> List Import, the first record is getting rejected.

We have taken a look at the log files and got the following error:

'Country' is a required field. Please enter a value for the field. (SBL-DAT-00498)

But all the records are having a value for the Country field in the imported file. Also “Country” field is a required field and is mapped with the First column of the file.

To confirm this behaviour, we’ve reimported the same list after removing the first record, then also got the same error in logs and rejected the first record.

Hence we interchanged the "SMCC Cell Phone Number" column with "Country" in .CSV file, and reimported the list, list got imported successfully. And First record is not rejected by Siebel this time.

From this testing, we came to a conclusion that for some reason, first column of the first row is ignored always and record is getting rejected.

After interchanging the ‘Country’ column with the "SMCC Cell Phone Number” which is not a required field, the first record is not getting rejected.

And also Rejection of first record in list is happening for Multibyte lists only, not for single byte lists. For the time being we requested user to place a non required field in the first column of .CSV file.

Please let us know if this is a known Siebel functionality.

Thanks in advance

Solution

Message 1

For the benefit of other readers:

In Siebel Standard Configuration environment, we are not observing the first record being rejected when importing a list file with multi-bytes characters and having Country field as the first column. The observation is that all records are being imported but the first record does not have Country field populated (that is blank). This is due to the error being reported in the list import log file:

" The value entered in field Country of buscomp List Mgmt Prospective Contact does not match any value in the bounded pick list PickList Country.(SBL-DAT-00225) "

We have confirmed that eventhough the Country field value imported is a valid/matching value in the COUNTRY LOV, the error message is still being shown in the log file when the list file involved multi-btyes characters.

I have logged a Change Request 12-12O1L19 to address this behavior.

As for the behavior observed in customer environment, where the first record is not being imported. We have investigated and concluded that it was due to the Country field not being populated (due to the defect mentioned above) and in customer environment, they have added validation check to reject record when mandatory field is blank. The Country field in customer environment has been made a mandatory field while it is optional field in Siebel Standard Configuration.

<continue...>

Message 2

<continue from previous activity>

For the customer, the workaround is to put optional column as the first column in the list file instead of a mandatory column.

Thank you.
Siebel Technical Support