Search This Blog

SBL-DAT-00283: An internal error, invalid notification information object, has occurred. Please continue or ask your systems administrator to check yo

Applies to:

Product Release: V7 (Enterprise)
Version: 7.5.3.4 [16180]
Database: IBM DB2 8.1 FixPack 7a
Application Server OS: Sun Solaris 8
Database Server OS: Sun Solaris 8

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

Symptoms

SBL-DAT-00283

Our DBA created new index on S_COMM_POSTN via tools on our testing environment (db2 vers 8.2. – application ver 7.5.3.4)

Column   Sequence    Sort Order
COMM_ID    2    Asc
POSITION_ID    1    Asc
ROW_ID    3    Asc
.
After he applied the changes it took 6 hrs to complete the process. Please see attached log file and advice.
He was able to create the same index in few minutes on another environment where we already upgraded to 7.5.3.11.

Solution

Message 1

For the benefits of the others:
Optimization level on the database customer was using was set to 2. Once they changed that to 3, they were able to create an index in short time.





Keywords: DB2, Default Opt Level, DFT_QUERYOPT


Applies to:

Product Release: V7 (Enterprise)
Version: 7.8.2 [19213]
Database: Oracle 10.2.0.2
Application Server OS: Sun Solaris 9
Database Server OS: Sun Solaris 9

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

Symptoms

SBL-DAT-00283

We enabled object level check-in/check-out. We have found that the LAST_UPD_BY column on S_PROJECT is now being updated with the developer's login instead of the ROW_ID of their user record. There doesn't seem to be an immediate issue except for the column length does not allow more than 15 characters. We have some developers that have logins greater than the restriction.

Solution

Message 1

For the benefit of other readers,

Resolution:

Technical Support was able to replicate the issue after locking activity project

Steps to reproduce
Enable Single Object Locking
Check out Object e.g. Activity
Check Back in Object Activity

You will see the Row id is updated with user name on S_PROJECT table.... Attaching the SQL statement output

1* select ROW_ID,name,LAST_UPD_BY,LAST_UPD from o78hor01.S_PROJECT WHERE ROW_ID = '42-8OS-25V'
SQL> /

ROW_ID
---------------
NAME
---------------------------------------------------------------------------
LAST_UPD_BY     LAST_UPD
--------------- ---------
42-8OS-25V
Activity
0-1             24-JAN-07

Output of SQL statement after Test from Server

42-8OS-25V
Activity
SADMIN          01-MAR-07

LAST_UPD_BY column on S_PROJECT being updated with login name instead of ROW_IDs on Server database when Single Object Locking Feature is enabled

Change Request 12-1IEP866 has been logged to address this product defect; In general, when a product defect/enhancement is logged, it is reviewed, prioritized, and then fixed in a future release

Muneer Uddin
Oracle Technical Support

Keywords: LAST_UPD_BY,S_PROJECT,Single Object Locking


No comments:

Post a Comment