Applies to:
Product Release: V7 (Enterprise)Version: 7.7.2 [18325]
Database: IBM DB2 7.1 FixPack 5se
Application Server OS: Microsoft Windows 2003 Server
Database Server OS: IBM AIX 5L 5.2
This document was previously published as Siebel SR 38-1874173270.
Symptoms
SBL-DAT-00446, SBL-DAT-00468Hi,
I have successfully ran the Siebel 77 Db Install and found no errors in the log files,
but I can not access the application with the Siebel 77 client or Siebel 77 tools.
When I
start tools I get the error message:
-No records exist for the current
query.(SBL-DAT-00468)
The fat Client returns -. The user ID or password that you entered
is incorrect. Please check the spelling and try again.
I can connect fine using DB2 CAE or
WINSQL.
I will attach the Install logs ... when I get some time.
Solution
Message 1
For the benefit of others:Description:
New 7.7 database server was installed but neither Tools nor Dedicated Client can login.
Accessing Tools displays the message:
No records exist for the current query.(SBL-DAT-00468)
In the \web client\log\siebel.log we see the following errors:
7.7.2 [18325] ENU
GenericLog GenericError 1 0 2005-03-30 09:21:08 (secclnt.cpp (256) err=7010002 sys=0) SBL-SEC-10002: Cannot perform the requested operation due to an invalid security context. If you have already logged in, please try to log in again or contact your system administrator for assistance.
DBCLog DBCLogError 1 0 2005-03-30 09:21:08 SQLDriverConnect: DSN=kagpro, UID=sadmin
ObjMgrLog Error 1 0 2005-03-30 09:21:08 (clicon.cpp (3383)) SBL-DAT-00446: You have entered an invalid set of logon parameters. Please type in your logon parameters again.
DBCLog DBCLogError 1 0 2005-03-30 09:21:08 SQLError: sqlstate 08001: [IBM][CLI Driver] SQL30082N Attempt to establish connection failed with security reason "24" ("USERNAME AND/OR PASSWORD INVALID"). SQLSTATE=08001
GenericLog GenericError 1 0 2005-03-30 09:21:08 (secmgr.cpp (2265) err=7010018 sys=0) SBL-SEC-10018: You have entered an invalid set of logon parameters. Please type in your logon parameters again.(SBL-DAT-00446)
[IBM][CLI Driver] SQL30082N Attempt to establish connection failed with security reason "24" ("USERNAME AND/OR PASSWORD INVALID"). SQLSTATE=08001
(cont)
Message 2
(cont)Resolution:
Customer realized the pre-installation task of running GRANTUSR.SQL had not been run prior.
Applies to:
Siebel System Software - Version: 8.0.0.6 [20423] - Release: V8Information in this document applies to any platform.
Symptoms
When running a query under Quality
Quering for Status: "Open or Error" Product Line: SimXpert, All CRs, the query finds a bunch.
When record count is selected I get this error.
Error: No Record exist for the current query SBL-DAT-00468
I searched support web and tried a few suggestions to capture log info. In the dedicated client I have logs with scripting turned on and off. From the web client I got OM logs for the time period I received the error.
I set event logging per the FAQ 1322 and 2116. I can't recycle my Siebel service until Friday since this is a production machine. So the OM logs may not be complete.
From my analysis this seems to be related to the Status field when using the value "Error". The status field has a state model associated to it as well. I can get the correct record count when using only "Open" or another value like Test in the Status Field.
The database has been getting a lot of ORA-07445 errors.
There is an Oracle bug with no patch available. You cannot search on the Status field of CR’s or SR’s with a case insensitive search, or the Oracle process will die.
Do not search for:
Status: error or open
Instead, search for:
Status: =Error or =Open
If you use the equal sign and the correct capitalization, then you will not get the error.
Does Oracle have a patch available yet to address the error.
Cause
Customer logged SR 7452658.992 with “regular” MetaLink, and they were able to reproduce the error when I provided them with dumps of our table data and a SQL statement. They logged bug.8391879 for this issue. I was also given the suggestion to run this command:
alter session set events '10338 trace name context forever, level 1';
but it gives an error:
SQL> alter session set events '10338 trace name context forever, level 1';
Session altered.
SQL> @test.sql
ERROR:
ORA-03113: end-of-file on communication channel
Instead, I monitor the Oracle Alert Log carefully, and when I see an ORA-07445 error, I send an email to the user with the suggestion that he or she should use the equal sign (=) in the Status field when querying Service Requests or Product Defects.
Solution
This behavior is due to Oracle DB bug 8391879 identified in Oracle DB 10.2.0.4 version.
There is a workaround to inform user to search using Status: =Error or =Open
And do not search for Status: error or open
Customer will use the workaround as there are only few identified users who run this query and are aware of the workaround and they will also wait for Oracle DB patch.
Thank you and kind regards,
Siebel Technical Support
Oracle Corporation.
Applies to:
Siebel Tools - Version: 7.8.2.4 [19224] - Release: V7Information in this document applies to any platform.
Symptoms
After upgrading the production database to Oracle 10.2.0.4, we became unable to import or export to archive using Siebel Tools. It gives the following error:
No records exist for the current query.(SBL-DAT-00468)
Cause
Comments
--------
It was found from log file that the problem was related to employee initialization process and the employee flag for SADMIN was re-set to N in s_contact table leading to not recognize SADMIN as an employee and hence to fail the initialization process in Tools.
Solution
Solution was to Set the employee flag of SADMIN
Applies to:
Siebel Financial Accounts, SPE - Version: 8.1.1 SIA [21111] - Release: V8Information in this document applies to any platform.
Symptoms
We cannot revise Commercial Loan in All Requests View that are not owned by current user.
Detailed steps:
1. Log in as AWONG.
2. Go to Commercial Loan - > My Requests ("FINS cBanking Request View - My" view)
3. Create new record "SR Test Loan 04102009 01"
4. Save the record.
5. Log in as DBERRYMA
6. Go to Commercial Loan - > All Requests ("FINS cBanking Request View - All" view)
7. Query for "SR Test Loan 04102009 01" record
8. Pick "Loans Over $100M" value for "Approval Level" field
9. Save the record
==> ERROR "No records exist for the current query.(SBL-DAT-00468)" appears
10. Undo the changes by pressing Esc
11. Add DBERRYMA to the Sales Team
12. Log out and back in again
13. Go to Commercial Loan - > All Requests ("FINS cBanking Request View - All" view)
14. Query for "SR Test Loan 04102009 01" record
15. Pick "Loans Over $100M" value for "Approval Level" field
16. Save the record - OK
Cause
The behavior is caused by Bug 12-1TK6K55
Solution
The behavior is caused by Bug 12-1TK6K55. It is targeted to be fixed in a future release. This bug has not been fixed so far.
Workaournd:
=========
Solution is either to change the class of the applet or to inactivate the user property "Save and Refresh Child.
In this case the applet's class change means to set the class property of the applets to a "base" class, for example CSSFrameBase or CSSFrameListBase. This is at the applet level, not the BC level.
Note that the "Save and Refresh Child" user property is not documented and therefore not supported for customer use
(its exact role and possible usage restrictions are unknown).
Either suggestion used would require intensive testing to see if these changes cause any side effects.
References
BUG:12-1TK6K55 - CANNOT SET APPROVAL LEVEL FOR COMMERCIAL LOAN ON ALL REQUESTS VIEWApplies to:
Error Message Area:Data Manager - DATVersion:Siebel 7.7
Purpose
This document is intended to provide cause and corrective action information about Siebel Error Message SBL-DAT-00468: No records exist for the current query.
Scope
This document is informational and intended for any user.
SBL-DAT-00468: No records exist for the current query.
Explanation
Below are some known causes for this error and you should confirm you are not encountering these behaviors:1. The error is reported when the user tries to log into Siebel Tools or the Siebel Client after an install or upgrade against a Siebel DB2 database. This error may occur either because the DB2 Fixpak installation was not successful or an unsupported Fixpak version was installed on the client machine.
2. You may encounter this error when running a workflow process invoked by MSMQ or SAP with persistence enabled (Persistence Frequency = Every Step, Persistence Level = All Steps).
For more information about enabling persistence in a workflow process, refer to Siebel Bookshelf version 7.5 Rev A > Siebel Business Process Designer Administration Guide > Designing Workflow Processes > Using Workflow Persistence > Enabling Workflow Persistence.
For Siebel version 7.7, refer to Siebel Bookshelf > Siebel Business Process Designer Administration Guide > For Developers: Understanding How Workflow Processes Are Designed > Using Workflow Persistence > About Workflow Persistence.
3. Data in the application may cause this error. In this example, the customer configured Contact Us account records to populate the "TO:" field on the eService contact us email form. However, when choosing any of the records other than the first record in the drop down field, the error appeared. The error was caused by the Account name that was designated as a contact us account, had two spaces and a hyphen in the name. The white space was not being properly accounted for in the SQL statement.
To determine if you are encountering a similar behavior caused by the data, if you are using a Siebel Dedicated Web client, enable SQL spooling by following the instructions in FAQ 1322. If you are using the Siebel Web client and object managers, follow the instructions in FAQ 2116.
4. Custom scripting in the application can cause this error. To determine if the error is being caused by scripting, set the Enable Scripting parameter in your configuration (cfg) file to FALSE and try to reproduce the behavior.
Corrective Action
Below are the corrective actions to try to resolve the behaviors above:1. Verify that the same DB2 Fixpak version is installed on both the DB2 server products and DB2 clients as well as ensure the DB2 Fixpak version is supported against the appropriate Siebel environment. Use the db2level command to determine what DB2 Fixpak version you have installed. Install the appropriate DB2 Fixpak version on the client machine and server machine and try to connect to the Siebel application.
For more information about the db2level command and how to determine if the DB2 Fixpak version is supported, refer to FAQ 2207.
2. As a workaround, try running the workflow process with persistence disabled by setting the persistence fields, Persistence Frequency and Persistence Level to null.
Change Requests 12-JOYHRS and 12-KUCUSL have been logged to address this product defect. The change requests have been resolved in Siebel version 7.7.
3. Review the log files that were generated by enabling tracing on the client application. Base your corrective action on the cause identified in the log file. In this case, the customer resolved the problem by renaming the Account Name and removing the white space in the name.
4. If you are not able to reproduce the problem after disabling scripting in the cfg file, then most likely the cause is due to the custom scripting. Further test and correct the problems in your custom script file. If you are unable to resolve the error, then log a new service request and provide the scripts to Siebel Technical Support for further assistance.
Applies to:
Siebel eCommunications - Version: 8.1.1.3 SIA[21219]Information in this document applies to any platform.
Symptoms
After Installing 8.1.1.3 and ACR 500, modification of multiple assets by a different position causes the following error:
[1] Error invoking service 'SIS OM PMT Service', method 'Iterate Process For Selected Rows' at step 'Edit Asset Selections'.(SBL-BPR-00162)
[2] No records exist for the current query.(SBL-DAT-00468)
Steps to reproduce:
1) Log onto application as user SADMIN\SADMIN
2) Edit the "Administration - Group > Positions" such that the "Proxy Employee" position now also has SADMIN listed as the assigned employees using the Last Name field.
3) Navigate to "Accounts > Accounts List" and query for an account that has Installed Assets. (Ensure assets are created by SADMIN)
4) Select one asset and hit the Modify button and note that there is no error message
5) Select two assets and hit the Modify button and note that there is no error message
6) Open "Tools - User Preferences > Change Position"
7) Change position to the new Position of Proxy Employee
8) Navigate to "Accounts > Accounts List" and query for the same account that has Installed Assets.
9) Select one asset and hit the 'Modify' button and note that there is no error message
10) Select two assets and hit the 'Modify' button and the above error messages appear.
Note: Issue is also reproducible when you select a promotion with at least one asset under promotion. So select promotion and one of it's items that is also an asset.
Cause
This issue is due to a new product defect.
Solution
CR 12-1ZQFKSL has been logged for this issue.
The Quickfix is now available for product version 8.1.1.3. This patch can be downloaded using the following patch 10182534
When available, download 8.1.1.5 Fix Pack to resolve this issue.
Note that this patch was not available at the time of writing this document (October 2010).
References
BUG:12-1ZQFKSL - ACR500 - ERRORS SBL-BPR-00162,SBL-DAT-00468 WHEN DIFFERENT POSITION USED TO MODIFY MULTIPLE ASSETSPATCH:10182534 - 8.1.1.3 21219 SBA QF0335 SEBL_ARU
No comments:
Post a Comment