Applies to:Product Release: V7 (Enterprise)
Version: 188.8.131.52 
Database: Oracle 184.108.40.206
Application Server OS: Sun Solaris 9
Database Server OS: Sun Solaris 2.8
This document was previously published as Siebel SR 38-3413239318.
After applying Siebel 220.127.116.11 Fix Pack, the application crashes whenever a user retrieves a Payment record with Credit Card information.
We also tried to create a new Credit Card Payment record, and the application is crashing.
Credit Card number is encrypted in our application.
Customer applied Fix Pack 18.104.22.168 on top of Siebel Version 22.214.171.124, and immediately started experiencing crashes whenever using encrypted data.
This stops happening after rolling back the 126.96.36.199 Fix Pack.
The Call Stack they are getting is the following:
This customer is using AES as the encryption type, with encryption level (key length or strength) of 256 bit.
The same behavior was reproduced in-house on an internal test environment.
We could locate a known Product Defect which has been recently reported in our Knowledge Base:
- Change Request # 12-1J1ZOUE: After upgrading to 188.8.131.52 SIA, AES 256 encryption causes object manager to crash.
This behavior had been reported by CR # 12-1J1ZOUE on Siebel Version 184.108.40.206.
We logged Fix Request # 12-1KIOH3E requesting for a Quick Fix to be released on top of 220.127.116.11 Fix Pack.
Quickfix 18.104.22.168  QF0821 is being released by Siebel Engineering to address this issue.