Applies to:
Siebel Tools - Version: 7.7.1 [18306] to 8.1.1.2 - Release: V7 to V8z*OBSOLETE: Microsoft Windows 2000
Product Release: V7 (Enterprise)
Version: 7.7.1 [18306]
Database: Oracle 9.2.0.4
Application Server OS: Microsoft Windows 2000 Server SP 3
Database Server OS: Sun Solaris 2.8
This document was previously published as Siebel SR 38-1380480982.
***Checked for relevance on 06-May-2010***
Symptoms
SBL-DAT-00385, SBL-DAT-00509We are upgrading our Dev environment from 6.2.1.30 to 7.7.1. After completing all the Post
Upgrade tasks, we compiled a custom SRF and tried logging using dedicated client. On some of the
screens we seem to run into the following error message (screen shot attached):
Definition
for table '' does not exist.(SBL-DAT-00509)
The siebel.log file shows errors about
multiple definitions for various Business Comps such as:
ObjMgrSRFLog Error 1 0 2004-07-07
14:14:17 (objdef.cpp (559)) SBL-DAT-00385: Multiple definitions exist for business component
'Contact - Sales Rep - VisMvgSqlBCDef'.
siebel.log file is also attached. We have searched
the Bookshelf and Support Web but did not find anything that would be helpful. Please review the
files and let us know how to proceed further. Thanks.
Cause
Originally thought to be a product defect after this behaviour was reviewed by Siebel Engineering it was established that this was not the caseSolution
After further research it has been determined that this error can be caused by an inactive business component referred to by one or more multi value links. The business component may have been manually inactivated or automatically inactivated by the upgrade process due to the fact it has now been made obsolete.
Run the Tools validate on the business components indicated in the error message to help you identify the links that need to be fixed.
Change Request 12-PKC6CT had been raised with Siebel Engineering to address this behaviour as a product defect but was reviewed and it was established that this was not the case
There is no error in the upgrade. If a business component is inactive by Siebel, it will be inactive after an upgrade. That's expected behavior for upgrade. If the inactive business component causes other objects(referring to the business component) to be invalid due to this inactive, a developer need to correct them during post merge. This is true for other object types too besides business components
Applies to:
Siebel Tools - Version: 7.7.1 [18306] - Release: V7z*OBSOLETE: Microsoft Windows Server 2003
Product Release: V7 (Enterprise)
Version: 7.7.1 [18306] DEU
Database: IBM DB2 8.1 FixPack 3
Application Server OS: Microsoft Windows 2003 Server
Database Server OS: Microsoft Windows 2003 Server
This document was previously published as Siebel SR 38-1459241015.
Symptoms
SBL-DAT-00556, SBL-DAT-00546, SBL-DAT-00560Follow-up from SR 38-1453099441
1. Starting Siebel via web client fails. Please see the attached log-files for error messages.
(For translation see Siebel Error Messages > Siebel 7.7).
SBL-DAT-00560, SBL-DAT-00556, SBL-DAT-00546, SBL-SVC-00208, SBL-DAT-00385
2. Doing a full compile on the extracted local developer database fails:
Displayed error messages:
An error message has occured executing a Sql statement.
Please continue or ask your systems administrator to check your application configuration if the problem persists.(SBL-DBC-00105)
Internal database error *** ERROR *** Assertion failed: 102300 (8.0.2.4361)
File associated with given page id is invalid or not open -- transaction rolled back
According to SR 38-1371657223 we regenerate db template, extracted db again, initialize it, perform a full get but the error still remains.
Compiling a new SRF connected to the server succeded.
3. The error messages described in the attached log files do not appear using a standard SRF.
We are able to connect successfully via Web Client.
4. We are able to connect successfully using the Siebel Dedicated Web Client. The same error messages are logged in local siebel.log while using compiled new SRF.
5. We renamed the Siebel_Server/bin/diccache.dat, but errors still remain.
Thank you for your quick response.
Henrik
Cause
The cause for the assertion failed error message sometimes occurs when the local db needs to allocate temporary files and does not have enough space.Solution
Message 1
DESCRIPTION:Tools stops during full compile on local db.
SYMPTOMS:
Doing a full compile on the extracted local developer database fails:
Displayed error messages:
An error message has occured executing a Sql statement.
Please continue or ask your systems administrator to check your application configuration if the problem persists.(SBL-DBC-00105)
Internal database error *** ERROR *** Assertion failed: 102300 (8.0.2.4361)
File associated with given page id is invalid or not open -- transaction rolled back
When using the unfinished srf file the following errors are shown in the client log file:
SBL-DAT-00560
SBL-DAT-00556
SBL-DAT-00546
SBL-SVC-00208
SBL-DAT-00385
SOLUTION:
The assertion failed error message sometimes occurs when the local db needs to allocate temporary files. This files are usual stored in the path of the TEMP system variable which usual points to C:\temp. As the temporary files can grow up to 500 MB the C hard disk sometimes has no free space for the temporary files.
In this case the issue has been resolved by deleting the TEMP system variable and recreating it new.
Siebel Technical Support
Applies to:
Product Release: V7 (Enterprise)Version: 7.5.3 [16157] DEU Fin Svcs
Database: IBM DB2/UDB 8.1 FixPack 1S
Application Server OS: Microsoft Windows 2000 Advanced Server SP 3
Database Server OS: Microsoft Windows 2000 Advanced Server SP 3
This document was previously published as Siebel SR 38-1165879168.
Symptoms
SBL-DAT-00385, SBL-DAT-00398, SBL-DAT-00462Hi, after setting up all developer environments and doing a full get/full compile without any
problems, we are now experiencing problems with the check-in/check-out routines.
Whatever
project we are trying to check out, the error message reads as follows:
"You have attempted to
denormalize calculated field 'Done Flag' in business component 'Action' into column 'DONE_FLG'.
Donormalized calculations are not allowed (SBL-DAT-00462)"
I then went ahead with Tools,
connected to the Server and checked the properties of this field. It was in fact not correctly
defined, as it had a column property attached to it. I then removed this property, so that it was
a calculated field (the flag and the calculation expression set as it used to be in our V6
environment). Did another full compile server based, which completed without errors.
When
trying to check-out projects after this modification, we are running into the same error message
again. After this first error message, we are getting another one which points to a field called
'Audit Flag', which sits on a custom extension to S_EVT_ACT, claiming it to be defined twice
(which, of course, is not correct).
Other symptoms, which we think are related to this
problem are the unability to create sif-files locally.
Please advise, how we can fix this.
Kind regards,
Solution
Message 1
DESCRIPTION:Problems during Check-Out of Siebel Projects
SYMPTOMS:
Whatever project we are trying to check out, the error message reads as follows:
"You have attempted to denormalize calculated field 'Done Flag' in business component 'Action' into column 'DONE_FLG'. Donormalized calculations are not allowed (SBL-DAT-00462)"
SOLUTION:
The properties of the directories where Siebel was installed have been checked and it turned out, that the user didn't had the right permissions to write files to that directory (write protection on the windows directories). After resetting these, the user could check in /out and create sif-files without any error messages.
Thank you
Siebel Technical Support
No comments:
Post a Comment