Siebel Pharma Call Center - Version: 8.0.0.3 SIA [20416] and later [Release: V8 and later ]
Information in this document applies to any platform.
Symptoms
From time to time it is not possible to create large amount of documents using EAI.
Steps:
---------
The error occurs at customer site when trying to create documents during intensively tests with a few dozen to >100 calls per few minutes. It happens sometimes only.
New documents are created in Siebel by sending inbound webservices from external application to Siebel.
Error:
-------
(filetransport.cpp (344)) SBL-EAI-04224: Cannot open file C:\Siebel\siebsrvr\temp\
(eaiobjinst.cpp (3418)) SBL-EAI-04224: Cannot open file
Cause
The cause of this behaivor was due to special characters like brackets [ ... ] or forward slash / being used in document names like this:
new document name like this : Massenmailing [hier nicht klicken]_eBus_POINT Plus_Anmeldung_NK /Signatur_20101028-144045484
Solution
Advise users to avoid special characters in document names being sent to Siebel.
Applies to:
Siebel CRM - Version: 7.8.2 SIA [19213] to 8.0 SIA [20405] - Release: V7 to V8
Sun Solaris SPARC (64-bit)
Sun Solaris SPARC (32-bit)
Solaris Operating System (SPARC 64-bit)Solaris Operating System (SPARC 32-bit)
Area(s):System Administration, Siebel EAI
Release(s):V7 (Enterprise), V7 (MidMarket), V7 (Professional)
Database(s):All Supported Databases
App Server OS(s):Solaris
Latest release tested against:V7 (Enterprise)
Keywords:fopen, cannot open file, unable to open file, zero, empty
This document was previously published as Siebel Alert 1025.
Description
While running the Siebel server on the Solaris platform, Siebel server components such as the Siebel Object Manager might encounter behaviors when writing or opening files. The Siebel process is attempting to write data to a file, the process will create the file, but the file will be zero bytes in size even though there is enough disk space available on the disk drive.
The root cause of these behaviors is that the Solaris fopen call will only allow a maximum of 256 open files per process. Sun Microsystems has stated they cannot fix this limitation as it will break their backward compatibility guarantee.
Review the following document located on Sun Microsystems "Sunsolve" website for details:
#01406 - Maximum number of open files
Likelihood of Occurrence
This behavior only occurs on a Siebel server running on the Solaris platform. Frequency of occurrence varies depending on the type and frequency of file operations used. This behavior appears randomly or sporadically but is more likely to occur with a higher volume of users.
Possible Symptoms
Symptoms of this behavior may occur in any operation in the Siebel application that reads or writes to a file. These include but are not limited to the tasks listed below:
Invoke the "EAI File Transport" business service.
Invoke the "EAI XML Write to File" or "EAI XML Read from File" business services.
In the Siebel UI, use the File > Export or File > Import utilities.
Use a custom business service with Clib.fopen, Clib.fclose or Clib.fprintf routines.
Open web templates (*.swt files).
Additionally, the following errors have been reported in the Siebel Object Manager log files:
SBL-UIF-00276: Cannot open file: %1
SBL-EAI-04224: Unable to open file '%1'
If the same Siebel process is attempting to write data to a file, it may create the file but the file itself will be empty, or in other words, 0 bytes in size. The Siebel server component's log file may be empty as well.
To look for empty files in a directory, use the find command below:
find . -size 0c
Workaround or Resolution
Below are some workarounds that you can implement to reduce the likelihood of encountering this behavior:
Turn off all extra logging for this Siebel Object Manager component (if possible, back to the default settings). This will reduce the number of log files opened and written by this component.
Decrease the number of tasks for each Siebel Object Manager process by increasing the number of MaxMTServers. For example, if you currently have MaxTasks=600 and MaxMTServers=6, you may want to change those values to MaxTasks=600 and MaxMTServers=10. This will reduce the ratio of tasks from 100 to 60 tasks per Siebel Object Manager process, which in turn will reduce the number of log files opened and written by this process.
NOTE: The numbers listed above are for demonstration purposes and you must adjust your own values based on your Siebel environment. Generally, increasing the number of MTServers per Siebel Object Manager component will result in more memory used by the Siebel server. This workaround should be thoroughly tested in a Test environment before implemented in a Production environment.
For Solaris 10 update 4 or above, the problem can be resolved by performing following steps:
1. Update .profile on Siebel Application Server as follows:
ulimit -n 2048
export LD_PRELOAD_32=/usr/lib/extendedFILE.so.1:$LD_PRELOAD_32
2. Restart Siebel Servers
The extendedFILE.so.1 is not a library but an enabler of the extended FILE facility. Preloading extendedFILE.so.1 is the right solution for the 32-bit file descriptors limitation. Please check the following technical article for detailed information: http://developers.sun.com/solaris/articles/stdio_256.html.
Once extendedFILE library is preloaded, the number of OM processes can be reduced to 10.
Applies to:
Product Release: V7 (Professional)
Version: 7.8.2.4 [19224] FRA
Database: Oracle 10.2.0.1
Application Server OS: IBM AIX 5L 5.3
Database Server OS: IBM AIX 5L 5.3
This document was previously published as Siebel SR 38-3336702721.
Symptoms
Hi,
I'm trying to import admin data (PDQ, views, state-models) with the ADM. But I get the following errors.
(filetransport.cpp (461)) SBL-EAI-04224: Impossible d'ouvrir le fichier '/script/siebint3/livraison/rt-data/ADM/1-1TQBO_LOV.xml
SBL-EAI-04261: Erreur lors de l'obtention XML du fichier '/script/siebint3/livraison/rt-data/ADM/1-1TQBO_LOV.xml
(stepexec.cpp (803)) SBL-BPR-00162: Erreur de mise en œuvre du service 'EAI XML Read from File', méthode 'ReadXMLHier' à l"étape 'Read from File'.
Erreur de mise en œuvre du service 'EAI XML Read from File', méthode 'ReadXMLHier' à l"étape 'Read from File'.(SBL-BPR-00162)
(stepexec.cpp (803)) SBL-BPR-00162: Erreur de mise en œuvre du service 'UDA Service', méthode 'Import File' à l"étape 'Import File'.
Erreur resignalisée depuis le gestionnaire d'objets: ([1] Erreur lors de l'obtention XML du fichier '/script/siebint3/livraison/rt-data/ADM/1-1TQBO_LOV.xml'.(SBL-EAI-04261) (IDS_EAI_ERR_XMLPRT_FILE_READ_ERR))
Erreur resignalisée depuis le gestionnaire d'objets: ([2] Impossible d'ouvrir le fichier '/script/siebint3/livraison/rt-data/ADM/1-1TQBO_LOV.xml
'(SBL-EAI-04224) (0x8085))
( (0) err=4300107 sys=32901) SBL-OMS-00107: Erreur resignalisée depuis le gestionnaire d'objets: ([2] Impossible d'ouvrir le fichier '/script/siebint3/livraison/rt-data/ADM/1-1TQBO_LOV.xml
'(SBL-EAI-04224) (0x8085))
( (0) err=4300107 sys=33405) SBL-OMS-00107: Erreur resignalisée depuis le gestionnaire d'objets: ([1] Erreur lors de l'obtention XML du fichier '/script/siebint3/livraison/rt-data/ADM/1-1TQBO_LOV.xml
'.(SBL-EAI-04261) (IDS_EAI_ERR_XMLPRT_FILE_READ_ERR))
( (0) err=4300107 sys=32984) SBL-OMS-00107: Erreur resignalisée depuis le gestionnaire d'objets: ([0] Erreur de mise en œuvre du service 'EAI XML Read from File', méthode 'ReadXMLHier' à l"étape 'Read from File'.(SBL-BPR-00162) (0x80d8))
(bsvcmgr.cpp (364) err=4300203 sys=0) SBL-OMS-00203: Erreur 32984 d'appel de la méthode "RunProcess" pour le service commercial "Wor...
Solution
Message 1
Customer was imporgting data with ADM but was encountering various errors indicating file access issues..
Such as
SBL-EAI-04224, SBL-EAI-0426, SBL-BPR-00162
Customer found hat the issue was caused due to control character " ^M" at the end of of lines in the .ini files. Typically occurs when transfer files from windows to unix
keywords:
SBL-EAI-04224, SBL-EAI-0426, SBL-BPR-00162,filetransport.cpp,ADM,import,unix,control,character
אין תגובות:
הוסף רשומת תגובה