Error in OLTP 2.0 extractor during init. selection

During 0FIAR_O03 Init package load on PRD system I got thousands of errors with the same message:
*Error in OLTP 2.0 extractor during init. selection
What's wrong with these selections?
My data load is 3.x type
I'm loading into BI for SAP Netweaver 2004s

I get error while trying INIT LOAD by RSA3:
"Could not determine BW release of logical system ''
I get no errors if i'm trying FULL LOAD

Similar Messages

[Solved] 'New' error messages during init after updating initscripts

After updating to the latest initscripts, I got some error messages during init that I hadn't seen before. They occurred during one of the UDev steps, and were caused by an attempt to load an IDE module despite the controller being disabled. The controller shows up in Windows devmgr too, so I guess it's a failing of the mobo or BIOS.
In any case, I downgraded and found that the errors were nothing new. I'm just curious if the appearance of the errors during init was by design or a happy accident.
Last edited by alphaniner (2011-08-01 17:07:30)

alphaniner wrote:
karol wrote:If you have the new (i.e. current) initscripts, you should be fine:
http://projects.archlinux.org/initscrip … 328fbaf2e7
http://projects.archlinux.org/initscrip … 42dfeca8c2
I had never noticed the file before yesterday, actually. And I'm up-to-date, yet it's still full of 'em.
You need to reboot.
After you do, run
tail /var/log/boot
Mine isn't perfect, but I've already sent an e-mail to the dev (it's a matter of just a sed oneliner)
[karol@black ~]$ tail /var/log/boot
Tue Aug 2 05:03:01 2011: :: Setting Hostname: black ^[[171G [BUSY] ^[[171G [DONE]
Tue Aug 2 05:03:01 2011: :: Setting Locale: pl_PL.UTF-8 ^[[171G [BUSY] ^[[171G [DONE]
Tue Aug 2 05:03:01 2011: :: Setting Consoles to UTF-8 mode ^[[171G [BUSY] ^[[171G [DONE]
Tue Aug 2 05:03:01 2011: :: Loading Keyboard Map: pl ^[[171G [BUSY] ^[[171G [DONE]
Tue Aug 2 05:03:02 2011: :: Loading Console Font: Lat2-Terminus16 ^[[171G [BUSY] ^[[171G [DONE]
Tue Aug 2 05:03:02 2011: :: Saving dmesg Log ^[[171G [BUSY] ^[[171G [DONE]
Tue Aug 2 05:03:02 2011: INIT: Entering runlevel: 3
Tue Aug 2 05:03:02 2011: :: Starting Syslog-NG ^[[171G [BUSY] ^[[171G [DONE]
Tue Aug 2 05:03:03 2011: :: Starting D-BUS system messagebus ^[[171G [BUSY] ^[[171G [DONE]
Tue Aug 2 05:03:04 2011: :: Starting acpid ^[[171G [BKGD] :: Starting gpm ^[[171G [BKGD^[[0;1

[SOLVED] alsa daemon error during init with Thinkpad X220

Hi,
I just updated my system (including a kernel update). After reboot, I found alsa daemon, which is used to restore previous volume level, failed to start. I tried to start that daemon manually after the boot process is completed, and that produced an error message
sudo rc.d start alsa
:: Restoring ALSA Levels [BUSY]
Found hardware: "HDA-Intel" "Intel CougarPoint HDMI" "HDA:14f1506e,17aa21da,00100000 HDA:80862805,80860101,00100000" "0x17aa" "0x21da"
Hardware is initialized using a generic method
[FAIL]
However, the volume level restored successfully. It seems that recent Intel plantform provides two soundcard, and that error only affected the secondary card, which has nothing to do about system volume level.
Anyway, I hate to have a ``[FAIL]'' During init process. Any suggesting to get rid of that problem? Thanks
System Info: (I use linux-ck as my kernel with modified config)
uname -a
Linux Thomas 3.2.1-2-ck #1 SMP PREEMPT Sun Jan 15 00:16:41 CST 2012 x86_64 Intel(R) Core(TM) i7-2620M CPU @ 2.70GHz GenuineIntel GNU/Linux
lspci
00:00.0 Host bridge: Intel Corporation 2nd Generation Core Processor Family DRAM Controller (rev 09)
00:02.0 VGA compatible controller: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller (rev 09)
00:16.0 Communication controller: Intel Corporation 6 Series/C200 Series Chipset Family MEI Controller #1 (rev 04)
00:19.0 Ethernet controller: Intel Corporation 82579LM Gigabit Network Connection (rev 04)
00:1a.0 USB controller: Intel Corporation 6 Series/C200 Series Chipset Family USB Enhanced Host Controller #2 (rev 04)
00:1b.0 Audio device: Intel Corporation 6 Series/C200 Series Chipset Family High Definition Audio Controller (rev 04)
00:1c.0 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI Express Root Port 1 (rev b4)
00:1c.1 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI Express Root Port 2 (rev b4)
00:1c.3 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI Express Root Port 4 (rev b4)
00:1c.4 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI Express Root Port 5 (rev b4)
00:1c.6 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI Express Root Port 7 (rev b4)
00:1d.0 USB controller: Intel Corporation 6 Series/C200 Series Chipset Family USB Enhanced Host Controller #1 (rev 04)
00:1f.0 ISA bridge: Intel Corporation QM67 Express Chipset Family LPC Controller (rev 04)
00:1f.2 SATA controller: Intel Corporation 6 Series/C200 Series Chipset Family 6 port SATA AHCI Controller (rev 04)
00:1f.3 SMBus: Intel Corporation 6 Series/C200 Series Chipset Family SMBus Controller (rev 04)
03:00.0 Network controller: Intel Corporation Centrino Advanced-N + WiMAX 6250 (rev 5e)
0d:00.0 System peripheral: Ricoh Co Ltd Device e823 (rev 07)
0e:00.0 USB controller: NEC Corporation uPD720200 USB 3.0 Host Controller (rev 04)
config.gz:
http://codepad.org/XtUSbtdw
(Edit typo)
Last edited by cap_sensitive (2012-01-17 06:12:01)

This morning, I performed a system update and I did not see any errors with alsa when I rebooted. Audio hardware is:
00:1b.0 Audio device: Intel Corporation 5 Series/3400 Series Chipset High Definition Audio (rev 05)
Have you tried manually restarting alsa after the system boots up to see if you get the same error? You can restart alsa with the following command:
sudo /etc/rc.d/alsa force-restart
Post your results. If the error occurs during the manual restart, it should also include some details about what caused the error

0FI_AR_4 datasource is extraction 0 records during Init

Hi,
0FI_AR_4 datasource is extraction 0 records during Init. But if I run the Full-load I can get the data.
I am not sure whether our extractors are uncoupled.
Currently we are using GL and AP extractors as well.
We are on EEC6 and PI_BASIS 2005_1_700
There were no selection fields defined 0FI_AR_4 to restrict the Init on Fiscal year period/ Company code.
Not sure whether this note 551044 is applicable for the currect vesion of the component.
Reagards
Ajay
Points will be assigned to all answers.

Hi Anil,
Thanks this is useful I have checked TPS31 Table the entry is maintained as described in your link.
this table doesn't have any entries in it BWOM_SETTINGS ( Do we have entries only after running delta infopackage?
When I tey to instral the datasource from RSA5
The get the following error message.
Units field HWAE2 for field H2STE of DataSource 0FI_AR_4 is hidden
Units field HWAE3 for field H3STE of DataSource 0FI_AR_4 is hidden
Units field HWAE2 for field ZLOCAL2 of DataSource 0FI_AR_4 is hidden
Units field HWAE3 for field ZLOCAL3 of DataSource 0FI_AR_4 is hidden
it will be great if you can help me out.
Regards
Ajay

Error Occured During Data Selection

Hi Community,
                       I got "Error Occured During Data Selection" when loading data from ODS to Info Cube. This info cube already contained data before but first time I didnt get complete records (both in ODS and Info Cube) so I deleted the request and load the data in both ODS and Info cube.
                      I got the records in ODS but when I am loading data from ODS to Info Cube then error displayed in Monitor display called "Error Occured During Data Selection"
                      I am working on BI 7.0. Please help me
Regds
Robbie.

Hi,
Have you deleted the <i>Delta inti info</i> available in the info package which is used to upload the data from ODS to Cube . Here you have to make it red and then delete it.
Other wise delete the row available in RSA7( in BIW) which was created at the time od the delta init from ODS to CUBE upload.
and aslo check the following link is relevent to your problem?
/message/2922612#2922612 [original link is broken]
With rgds,
Anil Kumar Sharma .P

Posssible to redirect the content of SCREEN during init/userspace?

I went to IRC the other day and asked where the userspace errors are usually located, a lot of users pointed me in the /var/log direction. But I can't for the life of me find anything that's related to userspace, only kernel errors.
Example: (sorted by now) netcfg complains during init theres a profile error bla bla, naturally I try to grep "Profile x error" in every log from /var/log but the result gives me nothing.
Where do we locate standard userspace errors? if there's no way other than using scroll lock, can't we take the output and direct it to a log instead?
Thank You

bender02 wrote:
greenfish wrote:Where do we locate standard userspace errors? if there's no way other than using scroll lock, can't we take the output and direct it to a log instead?
I think it's the matter of each "userspace" program to allow and arrange for logging of its output, via the config file and/or by command line switches, or automatically. If you need to capture output of a particular program/daemon run during the startup, you can always restart it (sudo /etc/rc.d/<daemon_name> restart) to get its output again, or better, take a look at how is the program actually run by looking at the script /etc/rc.d/<daemon_name> and try to run it from command line manually (especially if it doesn't allow reasonably logging its output).
sorry for the delay guys, I guess you have to manually subscribe to each thread in order to recieve an update.
bender02 hmm I see, I guess that makes sence but still it's gonna be a whole mess going through the entire daemon path just to see which one is causing the errors, and those are just daemons, what about standard errors in userspace? Your idea is sound though, now I only need to find out exactly what process/daemon is causing my mess and write the output > file. Thanks dude!
@sjovan problem resolved, but most of the errors I get in userspace isn't visible with "dmesg" thanks anyways!

Error no. 4 in SAPGUI during graphic call or file transfer.

Hi,
In the landscape there are still 46b sap version, i have some functional queries that when i executes go to the sap graphic screen and it throws with no output. I understand that that it works in ECC version but not for 46b.
This issue is related to SAPGUI, as i have the latest sapgui installed 710 that works well for ECC.
But if i input the parameter in sap 46b system , and execute to get the graphic chart i get this:
The Generation of Graphs for Stock Movements in the MC49 Transaction.
When you call a hierarchy graphic, the following error messages are displayed
1. 'Too much data in a table or too many tables defined
2. E4: error writing to XC pipe: child #1 ( id: STAT ); reclen12
3. Error no. 4 in SAPGUI during graphic call or file transfer.
I have also look in to note 316232, 361222, 96885. for this but this says to upgrade the sapgui,which is already in.
What is the solution for this.
Regards,
Chetan.

Take a look at this thread. This may provide you some guidance as it appears that Error has been encountered before.
[Link Here|Error no. 4 in SAPGUI with Graphics call or file transfer;
Regards,
Zecher

Error when extracting data with extractor 2lis_04_matnr - NEED HELP ASAP !!

Hi experts!
Got an error when extracting data with extractor 2lis_04_matnr.
System says (short dump):
DUMP TEXT START----
Runtime error:    CONNE_IMPORT_WRONG_COMP_TYPE
Exception:   CX_SY_IMPORT_MISMATCH_ERROR
Error when attempting to import object "MC04P_0MAT_TAB".
The current ABAP program "SAPLMCEX" had to be terminated because one of the statements could not be executed. This is probably due to an error in the ABAP program. When attempting to import data, it was discovered that the data type of the stored data was not the same as that specified in the program.
An exception occurred. This exception is dealt with in more detail below. The exception, which is assigned to the class 'CX_SY_IMPORT_MISMATCH_ERROR', was neither caught nor passed along using a RAISING clause, in the procedure "MCEX_BW_LO_API" "(FUNCTION)".
Since the caller of the procedure could not have expected this exception
to occur, the running program was terminated.
The reason for the exception is: When importing the object "MC04P_0MAT_TAB", the component no. 5 in the dataset has a different type from the corresponding component of the target object in the program "SAPLMCEX". <b>The data type is "D" in the dataset, but "C" in the program.</b>
DUMP TEXT END----
Please, can someone explain me how to solve it?
Really need help ASAP!
Thanks in advance,
Jaume
Message was edited by:
        Jaume Saumell
Message was edited by:
        Jaume Saumell

Hi,
Check this note: 328181
So you need to delete entries in SM13/LBWQ for application and also detup table content.
And then refill teh set up table.
If you are in production clear the entries by running collective run no of times for this application 04.
With rgds,
Anil Kumar Sharma .P

A fatal error occured in the PD Layer during create Supplier RFx response

Dear SRM 7 Experts,
I am implementing SRM 7. I can successfully create a Supplier RFx Response on behalf of a supplier using the Surrogate Bid functionality. However, if I log on as a supplier contact person and try to create a Supplier RFx Response, I get error u201D A fatal error occured in the PD Layer. The transaction needs to be terminatedu201D.
Number ranges for Supplier RFx response (BUS2202) are maintained and assigned to the transaction type correctly.
What could be the problem?
Kind regards
Pedzi

Hi
Here is the thread which solved the same problem:
Re: A fatal error occured in the PD Layer during RFx response
with regards
Manjunath

Error: Action "Install_WatsonX86_Cpu32_Action" threw an exception during execution

During install of SqlServer Express 2008 (also I tried Developer Edition 2008 R2 with same error) I have error:
2014-05-01 17:13:52 Slp: Running Action: Install_WatsonX86_Cpu32_Action
2014-05-01 17:13:52 Slp: Error: Action "Install_WatsonX86_Cpu32_Action" threw an exception during execution.
2014-05-01 17:13:52 Slp: Microsoft.SqlServer.Setup.Chainer.Workflow.ActionExecutionException: C:\WINDOWS\Installer\7affd.msi ---> System.IO.FileNotFoundException: C:\WINDOWS\Installer\7affd.msi
2014-05-01 17:13:52 Slp:    в Microsoft.SqlServer.Chainer.Infrastructure.MsiNativeMethodHelpers.GetSummaryInformationStringProperty(ServiceContainer context, String pathToMsi, SummaryInformationStreamPropertySet propertyId)
2014-05-01 17:13:52 Slp:    в Microsoft.SqlServer.Chainer.Infrastructure.MsiNativeMethodHelpers.GetInstalledSummaryInformationStringProperty(ServiceContainer context, String productCode, SummaryInformationStreamPropertySet propertyId)
2014-05-01 17:13:52 Slp:    в Microsoft.SqlServer.Configuration.SetupExtension.MsiInstallEngineActionBehavior.ModifyAction(String installedProductCode, String installedProductVersion, String pathOfPackageOnMedia, InstallAction pkgAction)
2014-05-01 17:13:52 Slp:    в Microsoft.SqlServer.Configuration.SetupExtension.MSIInstallerEngine.InstallPackage(PackageId pkg, InstallAction pkgAction)
2014-05-01 17:13:52 Slp:    в Microsoft.SqlServer.Configuration.MsiExtension.PackageInstallAction.Execute(String actionId, TextWriter errorStream)
2014-05-01 17:13:52 Slp:    в Microsoft.SqlServer.Setup.Chainer.Workflow.ActionInvocation.InvokeAction(WorkflowObject metabase, TextWriter statusStream)
2014-05-01 17:13:52 Slp:    в Microsoft.SqlServer.Setup.Chainer.Workflow.PendingActions.InvokeActions(WorkflowObject metaDb, TextWriter loggingStream)
2014-05-01 17:13:52 Slp:    --- Конец трассировки внутреннего стека исключений ---
2014-05-01 17:13:52 Slp:    в Microsoft.SqlServer.Setup.Chainer.Workflow.PendingActions.InvokeActions(WorkflowObject metaDb, TextWriter loggingStream)
2014-05-01 17:13:52 Slp:    в Microsoft.SqlServer.Setup.Chainer.Workflow.ActionEngine.RunActionQueue()Error: Action "MsiTimingAction" threw an exception during execution.
2014-05-01 17:13:52 Slp: Microsoft.SqlServer.Setup.Chainer.Workflow.ActionExecutionException: C:\WINDOWS\Installer\7affd.msi ---> System.IO.FileNotFoundException: C:\WINDOWS\Installer\7affd.msi
2014-05-01 17:13:52 Slp:    в Microsoft.SqlServer.Chainer.Infrastructure.MsiNativeMethodHelpers.GetSummaryInformationStringProperty(ServiceContainer context, String pathToMsi, SummaryInformationStreamPropertySet propertyId)
2014-05-01 17:13:52 Slp:    в Microsoft.SqlServer.Chainer.Infrastructure.MsiNativeMethodHelpers.GetInstalledSummaryInformationStringProperty(ServiceContainer context, String productCode, SummaryInformationStreamPropertySet propertyId)
2014-05-01 17:13:52 Slp:    в Microsoft.SqlServer.Configuration.SetupExtension.MsiInstallEngineActionBehavior.ModifyAction(String installedProductCode, String installedProductVersion, String pathOfPackageOnMedia, InstallAction pkgAction)
2014-05-01 17:13:52 Slp:    в Microsoft.SqlServer.Configuration.SetupExtension.MSIInstallerEngine.InstallPackage(PackageId pkg, InstallAction pkgAction)
2014-05-01 17:13:52 Slp:    в Microsoft.SqlServer.Configuration.MsiExtension.PackageInstallAction.Execute(String actionId, TextWriter errorStream)
2014-05-01 17:13:52 Slp:    в Microsoft.SqlServer.Setup.Chainer.Workflow.ActionInvocation.InvokeAction(WorkflowObject metabase, TextWriter statusStream)
2014-05-01 17:13:52 Slp:    в Microsoft.SqlServer.Setup.Chainer.Workflow.PendingActions.InvokeActions(WorkflowObject metaDb, TextWriter loggingStream)
2014-05-01 17:13:52 Slp:    --- Конец трассировки внутреннего стека исключений ---
2014-05-01 17:13:52 Slp:    в Microsoft.SqlServer.Setup.Chainer.Workflow.PendingActions.InvokeActions(WorkflowObject metaDb, TextWriter loggingStream)
2014-05-01 17:13:52 Slp: Received request to add the following file to Watson reporting: C:\Documents and Settings\me\Local Settings\Temp\tmp1C4.tmp
2014-05-01 17:13:52 Slp: The following is an exception stack listing the exceptions in outermost to innermost order
2014-05-01 17:13:52 Slp: Inner exceptions are being indented
2014-05-01 17:13:52 Slp:
2014-05-01 17:13:52 Slp: Exception type: System.IO.FileNotFoundException
2014-05-01 17:13:52 Slp:     Message:
2014-05-01 17:13:52 Slp:         C:\WINDOWS\Installer\7affd.msi
2014-05-01 17:13:52 Slp:     Stack:
2014-05-01 17:13:52 Slp:         в Microsoft.SqlServer.Chainer.Infrastructure.MsiNativeMethodHelpers.GetSummaryInformationStringProperty(ServiceContainer context, String pathToMsi, SummaryInformationStreamPropertySet
propertyId)
2014-05-01 17:13:52 Slp:         в Microsoft.SqlServer.Chainer.Infrastructure.MsiNativeMethodHelpers.GetInstalledSummaryInformationStringProperty(ServiceContainer context, String productCode, SummaryInformationStreamPropertySet
propertyId)
2014-05-01 17:13:52 Slp:         в Microsoft.SqlServer.Configuration.SetupExtension.MsiInstallEngineActionBehavior.ModifyAction(String installedProductCode, String installedProductVersion, String pathOfPackageOnMedia,
InstallAction pkgAction)
2014-05-01 17:13:52 Slp:         в Microsoft.SqlServer.Configuration.SetupExtension.MSIInstallerEngine.InstallPackage(PackageId pkg, InstallAction pkgAction)
2014-05-01 17:13:52 Slp:         в Microsoft.SqlServer.Configuration.MsiExtension.PackageInstallAction.Execute(String actionId, TextWriter errorStream)
2014-05-01 17:13:52 Slp:         в Microsoft.SqlServer.Setup.Chainer.Workflow.ActionInvocation.InvokeAction(WorkflowObject metabase, TextWriter statusStream)
2014-05-01 17:13:52 Slp:         в Microsoft.SqlServer.Setup.Chainer.Workflow.PendingActions.InvokeActions(WorkflowObject metaDb, TextWriter loggingStream)
2014-05-01 17:13:56 Slp: Sco: Attempting to write hklm registry key SOFTWARE\Microsoft\Microsoft SQL Server to file C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20140501_171325\Registry_SOFTWARE_Microsoft_Microsoft SQL Server.reg_
2014-05-01 17:13:56 Slp: Sco: Unable to write hklm registry key SOFTWARE\Microsoft\Microsoft SQL Server to file C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20140501_171325\Registry_SOFTWARE_Microsoft_Microsoft SQL Server.reg_, Win32 error
2
2014-05-01 17:13:56 Slp: Sco: Attempting to write hklm registry key SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall to file C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20140501_171325\Registry_SOFTWARE_Microsoft_Windows_CurrentVersion_Uninstall.reg_
2014-05-01 17:13:56 Slp: Sco: Attempting to write hklm registry key SOFTWARE\Microsoft\MSSQLServer to file C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20140501_171325\Registry_SOFTWARE_Microsoft_MSSQLServer.reg_
2014-05-01 17:13:56 Slp: Sco: Unable to write hklm registry key SOFTWARE\Microsoft\MSSQLServer to file C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20140501_171325\Registry_SOFTWARE_Microsoft_MSSQLServer.reg_, Win32 error 2
I checked C:\WINDOWS\Installer\ for "7affd.msi" - there is no such file. Also I checked same folder on Win7-64 machine and Notebook WinXP-Pro - there is no such file. I was able to install Express on both Win7-64 and Notebook, but not on this machine.
I've tried searching for "7affd.msi" on internet without luck. Also I removed all Visual Studio Express 2010 and used any "Fix-It" utilities to check files and registry. And still have same error.
How to fix it?

Overall summary:
Final result:                  Failed: see details below
Exit code (Decimal):           -819060177
Exit facility code:            1838
Exit error code:               8751
Exit message:                  C:\WINDOWS\Installer\7affd.msi
Start time:                    2014-05-01 21:16:41
End time:                      2014-05-01 21:17:00
Requested action:              ComponentUpdate
Log with failure:              C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20140501_211629\Detail_ComponentUpdate.txt
Exception help link:           http%3a%2f%2fgo.microsoft.com%2ffwlink%3fLinkId%3d20476%26ProdName%3dMicrosoft%2bSQL%2bServer%26EvtSrc%3dsetup.rll%26EvtID%3d50000%26ProdVer%3d10.0.1600.22%26EvtType%3d0xCF2E222F
Machine Properties:
Machine name:                  3R-XP
Machine processor count:       4
OS version:                    Windows XP
OS service pack:               Service Pack 3
OS region:                     Россия
OS language:                   русский (Россия)
OS architecture:               x86
Process architecture:          32 Bit
OS clustered:                  No
Package properties:
Description:                   SQL Server Database Services 2008
SQLProductFamilyCode:          {628F8F38-600E-493D-9946-F4178F20A8A9}
ProductName:                   SQL2008
Type:                          RTM
Version:                       10
SPLevel:                       0
Installation location:         j:\85c0db9df26d4ae0b40b522d393a\x86\setup\
Installation edition:          EXPRESS
User Input Settings:
ACTION:                        ComponentUpdate
CONFIGURATIONFILE:
HELP:                          False
INDICATEPROGRESS:              False
MEDIASOURCE:                   j:\85c0db9df26d4ae0b40b522d393a\
PID:                           *****
QUIET:                         False
QUIETSIMPLE:                   False
X86:                           False
Configuration file:            C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20140501_211629\ConfigurationFile.ini
Detailed results:
Rules with failures:
Global rules:
There are no scenario-specific rules.
Rules report file:               C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20140501_211629\SystemConfigurationCheck_Report.htm
Exception summary:
The following is an exception stack listing the exceptions in outermost to innermost order
Inner exceptions are being indented
Exception type: System.IO.FileNotFoundException
    Message:
        C:\WINDOWS\Installer\7affd.msi
    Data:
      DisableWatson = true
    Stack:
        в Microsoft.SqlServer.Chainer.Infrastructure.MsiNativeMethodHelpers.GetSummaryInformationStringProperty(ServiceContainer context, String pathToMsi, SummaryInformationStreamPropertySet propertyId)
        в Microsoft.SqlServer.Chainer.Infrastructure.MsiNativeMethodHelpers.GetInstalledSummaryInformationStringProperty(ServiceContainer context, String productCode, SummaryInformationStreamPropertySet propertyId)
        в Microsoft.SqlServer.Configuration.SetupExtension.MsiInstallEngineActionBehavior.ModifyAction(String installedProductCode, String installedProductVersion, String pathOfPackageOnMedia, InstallAction pkgAction)
        в Microsoft.SqlServer.Configuration.SetupExtension.MSIInstallerEngine.InstallPackage(PackageId pkg, InstallAction pkgAction)
        в Microsoft.SqlServer.Configuration.MsiExtension.PackageInstallAction.Execute(String actionId, TextWriter errorStream)
        в Microsoft.SqlServer.Setup.Chainer.Workflow.ActionInvocation.InvokeAction(WorkflowObject metabase, TextWriter statusStream)
        в Microsoft.SqlServer.Setup.Chainer.Workflow.PendingActions.InvokeActions(WorkflowObject metaDb, TextWriter loggingStream)

There is error 'No such file or directory' during loading custom authentica

Hi,
I am working on OBIEE authentication using Hyperion shared services. I did the necessary changes in config file, like modifying config.xml to enable HSSauthenticator and enabling external authentication to instanceconfig.xml. However BI Server is unable to load the driver file for the Hyperion custom authenticator. Here is the error message.
There is error 'No such file or directory' during loading custom authentication module '/opt/local/usr/home/Oracle/OracleBI/web/bin64/libsawobisauthenticatorproxy643r.so'.
2011-06-26 21:04:05
[nQSError: 13011] Query for Initialization Block 'Hyperion EPM' has failed.
I have set the env variable LD_LIBRARY_PATH to this path but still I am getting the same error msg. I also have full previleges on this file. Would be really great if anyone can tell me why I am unable to load this driver file on to server. Thanks in advance

I think I figured out. Instead of giving path thru bin64 , I gave it thru bin folder, which is a 32bit file. I think they installled a 32bit OBIEE.

Curve 9300 error message: there was a problem during installation. Please try again when using app world

hi
I have a curve 9300 using os 6 and the latest app world 2.1.1.. something
when i try to download apps it initiates the download then after a couple of seconds after starting it shows the error message "there was a problem during installation. Please try again"
i have tried ALL the suppourt forums (KB26671 and KB30074) and suggestions/threads and called my network but none have worked.
these were reinstallign app world, making a new blackberry id as the other email address was associated with an old blackberry, security wiping the phone then restoring it and entering the new bb id, changing the date to 2014 and then hard wiping the phone and restoring it
i have twitter, facebook and bbm ect apps but these are RIM made i think and already preinstalled. everything else on the phone works fine
i have tried both wifi and network internet and battery pull
i really dont know what else to try or who else to contact to fix it. very annoying paying for a service you cant even use!
any help or more ideas would be great!
thanks

Hello carckberrypie,
In this case i would recommend wiping the BlackBerry smartphone. To do this we would need to back up the BlackBerry smartphone http://bit.ly/aSediX
Once backed up please follow the link below to perform a security wipe of your BlackBerry smartphone.
Link: http://www.blackberry.com/btsc/KB14058
Test the BlackBerry smartphone and proceed with a selective restore as outlined below.
Link: http://www.blackberry.com/btsc/KB10339
Thank you
-DrP
Come follow your BlackBerry Technical Team on Twitter! @BlackBerryHelp
Be sure to click Kudos! for those who have helped you.
Click Solution? for posts that have solved your issue(s)!

A fatal error was reported by SAR firmware during initialization

Dears,
After upgrading the SMU to one of our IOS XR GSR, we got the following error:
g_spa_2[173]: SPA ATM1/2 SAR: A fatal error was reported by SAR firmware during initialization: Firmware version mismatch [Error code 2002]. SPA will reset
The line card went into constant reload.
I could not locate any bug related.
Could it be hardware issue ?
Thanks,
Michel.

it could be the wrong hw rev for the atm spa is used (I thought you needed a V2).
that could be part of the problem.
alternatively, I would let the SIP boot without the SPA, invoke a fpd update, insert the SPA, try to update the fpd of the SPA, if that still fails, I think you need to open a tac case.
doesnt look like a hw failure to me, but this is a hw issue (fw revision situation)
regards
xander
Xander Thuijs CCIE #6775
Principal Engineer
ASR9000, CRS, NCS6000 & IOS-XR

Freezes computer during inital plug in

freezes computer during inital plug in. Windows ZP, reinstalled drivers, newest ITUNES downloaded. bottom right of my screen says new hardware found. Ipod beeps once and computer freezes. Ipod nano works fine. What will fix this?

These may help. The Vita/Win& one gives a link for XP.
iTunes for Windows Vista or Windows 7: Troubleshooting unexpected quits, freezes, or launch issues
iPhone, iPad, or iPod touch: Windows displays a blue screen message or restarts when connecting your device

Performance optimization during database selection.

hi gurus,
pls any explain about this...
Strong knowledge of performance optimization during database selection.
regards,
praveen

Hi Praveen,
Performance Notes
1.Keep the Result Set Small
You should aim to keep the result set small. This reduces both the amount of memory used in the database system and the network load when transferring data to the application server. To reduce the size of your result sets, use the WHERE and HAVING clauses.
Using the WHERE Clause
Whenever you access a database table, you should use a WHERE clause in the corresponding Open SQL statement. Even if a program containing a SELECT statement with no WHERE clause performs well in tests, it may slow down rapidly in your production system, where the data volume increases daily. You should only dispense with the WHERE clause in exceptional cases where you really need the entire contents of the database table every time the statement is executed.
When you use the WHERE clause, the database system optimizes the access and only transfers the required data. You should never transfer unwanted data to the application server and then filter it using ABAP statements.
Using the HAVING Clause
After selecting the required lines in the WHERE clause, the system then processes the GROUP BY clause, if one exists, and summarizes the database lines selected. The HAVING clause allows you to restrict the grouped lines, and in particular, the aggregate expressions, by applying further conditions.
Effect
If you use the WHERE and HAVING clauses correctly:
     There are no more physical I/Os in the database than necessary
     No unwanted data is stored in the database cache (it could otherwise displace data that is actually required)
     The CPU usage of the database host is minimize
     The network load is reduced, since only the data that is required by the application is transferred to the application server.
Minimize the Amount of Data Transferred
Data is transferred between the database system and the application server in blocks. Each block is up to 32 KB in size (the precise size depends on your network communication hardware). Administration information is transported in the blocks as well as the data.
To minimize the network load, you should transfer as few blocks as possible. Open SQL allows you to do this as follows:
Restrict the Number of Lines
If you only want to read a certain number of lines in a SELECT statement, use the UP TO <n> ROWS addition in the FROM clause. This tells the database system only to transfer <n> lines back to the application server. This is more efficient than transferring more lines than necessary back to the application server and then discarding them in your ABAP program.
If you expect your WHERE clause to return a large number of duplicate entries, you can use the DISTINCT addition in the SELECT clause.
Restrict the Number of Columns
You should only read the columns from a database table that you actually need in the program. To do this, list the columns in the SELECT clause. Note here that the INTO CORRESPONDING FIELDS addition in the INTO clause is only efficient with large volumes of data, otherwise the runtime required to compare the names is too great. For small amounts of data, use a list of variables in the INTO clause.
Do not use * to select all columns unless you really need them. However, if you list individual columns, you may have to adjust the program if the structure of the database table is changed in the ABAP Dictionary. If you specify the database table dynamically, you must always read all of its columns.
Use Aggregate Functions
If you only want to use data for calculations, it is often more efficient to use the aggregate functions of the SELECT clause than to read the individual entries from the database and perform the calculations in the ABAP program.
Aggregate functions allow you to find out the number of values and find the sum, average, minimum, and maximum values.
Following an aggregate expression, only its result is transferred from the database.
Data Transfer when Changing Table Lines
When you use the UPDATE statement to change lines in the table, you should use the WHERE clause to specify the relevant lines, and then SET statements to change only the required columns.
When you use a work area to overwrite table lines, too much data is often transferred. Furthermore, this method requires an extra SELECT statement to fill the work area. Minimize the Number of Data Transfers
In every Open SQL statement, data is transferred between the application server and the database system. Furthermore, the database system has to construct or reopen the appropriate administration data for each database access. You can therefore minimize the load on the network and the database system by minimizing the number of times you access the database.
Multiple Operations Instead of Single Operations
When you change data using INSERT, UPDATE, and DELETE, use internal tables instead of single entries. If you read data using SELECT, it is worth using multiple operations if you want to process the data more than once, other wise, a simple select loop is more efficient.
Avoid Repeated Access
As a rule you should read a given set of data once only in your program, and using a single access. Avoid accessing the same data more than once (for example, SELECT before an UPDATE).
Avoid Nested SELECT Loops
A simple SELECT loop is a single database access whose result is passed to the ABAP program line by line. Nested SELECT loops mean that the number of accesses in the inner loop is multiplied by the number of accesses in the outer loop. You should therefore only use nested SELECT loops if the selection in the outer loop contains very few lines.
However, using combinations of data from different database tables is more the rule than the exception in the relational data model. You can use the following techniques to avoid nested SELECT statements:
ABAP Dictionary Views
You can define joins between database tables statically and systemwide as views in the ABAP Dictionary. ABAP Dictionary views can be used by all ABAP programs. One of their advantages is that fields that are common to both tables (join fields) are only transferred once from the database to the application server.
Views in the ABAP Dictionary are implemented as inner joins. If the inner table contains no lines that correspond to lines in the outer table, no data is transferred. This is not always the desired result. For example, when you read data from a text table, you want to include lines in the selection even if the corresponding text does not exist in the required language. If you want to include all of the data from the outer table, you can program a left outer join in ABAP.
The links between the tables in the view are created and optimized by the database system. Like database tables, you can buffer views on the application server. The same buffering rules apply to views as to tables. In other words, it is most appropriate for views that you use mostly to read data. This reduces the network load and the amount of physical I/O in the database.
Joins in the FROM Clause
You can read data from more than one database table in a single SELECT statement by using inner or left outer joins in the FROM clause.
The disadvantage of using joins is that redundant data is read from the hierarchically-superior table if there is a 1:N relationship between the outer and inner tables. This can considerably increase the amount of data transferred from the database to the application server. Therefore, when you program a join, you should ensure that the SELECT clause contains a list of only the columns that you really need. Furthermore, joins bypass the table buffer and read directly from the database. For this reason, you should use an ABAP Dictionary view instead of a join if you only want to read the data.
The runtime of a join statement is heavily dependent on the database optimizer, especially when it contains more than two database tables. However, joins are nearly always quicker than using nested SELECT statements.
Subqueries in the WHERE and HAVING Clauses
Another way of accessing more than one database table in the same Open SQL statement is to use subqueries in the WHERE or HAVING clause. The data from a subquery is not transferred to the application server. Instead, it is used to evaluate conditions in the database system. This is a simple and effective way of programming complex database operations.
Using Internal Tables
It is also possible to avoid nested SELECT loops by placing the selection from the outer loop in an internal table and then running the inner selection once only using the FOR ALL ENTRIES addition. This technique stems from the time before joins were allowed in the FROM clause. On the other hand, it does prevent redundant data from being transferred from the database.
Using a Cursor to Read Data
A further method is to decouple the INTO clause from the SELECT statement by opening a cursor using OPEN CURSOR and reading data line by line using FETCH NEXT CURSOR. You must open a new cursor for each nested loop. In this case, you must ensure yourself that the correct lines are read from the database tables in the correct order. This usually requires a foreign key relationship between the database tables, and that they are sorted by the foreign key. Minimize the Search Overhead
You minimize the size of the result set by using the WHERE and HAVING clauses. To increase the efficiency of these clauses, you should formulate them to fit with the database table indexes.
Database Indexes
Indexes speed up data selection from the database. They consist of selected fields of a table, of which a copy is then made in sorted order. If you specify the index fields correctly in a condition in the WHERE or HAVING clause, the system only searches part of the index (index range scan).
The primary index is always created automatically in the R/3 System. It consists of the primary key fields of the database table. This means that for each combination of fields in the index, there is a maximum of one line in the table. This kind of index is also known as UNIQUE.
If you cannot use the primary index to determine the result set because, for example, none of the primary index fields occur in the WHERE or HAVING clause, the system searches through the entire table (full table scan). For this case, you can create secondary indexes, which can restrict the number of table entries searched to form the result set.
You specify the fields of secondary indexes using the ABAP Dictionary. You can also determine whether the index is unique or not. However, you should not create secondary indexes to cover all possible combinations of fields.
Only create one if you select data by fields that are not contained in another index, and the performance is very poor. Furthermore, you should only create secondary indexes for database tables from which you mainly read, since indexes have to be updated each time the database table is changed. As a rule, secondary indexes should not contain more than four fields, and you should not have more than five indexes for a single database table.
If a table has more than five indexes, you run the risk of the optimizer choosing the wrong one for a particular operation. For this reason, you should avoid indexes with overlapping contents.
Secondary indexes should contain columns that you use frequently in a selection, and that are as highly selective as possible. The fewer table entries that can be selected by a certain column, the higher that columns selectivity. Place the most selective fields at the beginning of the index. Your secondary index should be so selective that each index entry corresponds to at most five percent of the table entries. If this is not the case, it is not worth creating the index. You should also avoid creating indexes for fields that are not always filled, where their value is initial for most entries in the table.
If all of the columns in the SELECT clause are contained in the index, the system does not have to search the actual table data after reading from the index. If you have a SELECT clause with very few columns, you can improve performance dramatically by including these columns in a secondary index.
Formulating Conditions for Indexes
You should bear in mind the following when formulating conditions for the WHERE and HAVING clauses so that the system can use a database index and does not have to use a full table scan.
Check for Equality and Link Using AND
The database index search is particularly efficient if you check all index fields for equality (= or EQ) and link the expressions using AND.
Use Positive Conditions
The database system only supports queries that describe the result in positive terms, for example, EQ or LIKE. It does not support negative expressions like NE or NOT LIKE.
If possible, avoid using the NOT operator in the WHERE clause, because it is not supported by database indexes; invert the logical expression instead.
Using OR
The optimizer usually stops working when an OR expression occurs in the condition. This means that the columns checked using OR are not included in the index search. An exception to this are OR expressions at the outside of conditions. You should try to reformulate conditions that apply OR expressions to columns relevant to the index, for example, into an IN condition.
Using Part of the Index
If you construct an index from several columns, the system can still use it even if you only specify a few of the columns in a condition. However, in this case, the sequence of the columns in the index is important. A column can only be used in the index search if all of the columns before it in the index definition have also been specified in the condition.
Checking for Null Values
The IS NULL condition can cause problems with indexes. Some database systems do not store null values in the index structure. Consequently, this field cannot be used in the index.
Avoid Complex Conditions
Avoid complex conditions, since the statements have to be broken down into their individual components by the database system.
Reduce the Database Load
Unlike application servers and presentation servers, there is only one database server in your system. You should therefore aim to reduce the database load as much as possible. You can use the following methods:
Buffer Tables on the Application Server
You can considerably reduce the time required to access data by buffering it in the application server table buffer. Reading a single entry from table T001 can take between 8 and 600 milliseconds, while reading it from the table buffer takes 0.2 - 1 milliseconds.
Whether a table can be buffered or not depends its technical attributes in the ABAP Dictionary. There are three buffering types:
     Resident buffering (100%) The first time the table is accessed, its entire contents are loaded in the table buffer.
     Generic buffering In this case, you need to specify a generic key (some of the key fields) in the technical settings of the table in the ABAP Dictionary. The table contents are then divided into generic areas. When you access data with one of the generic keys, the whole generic area is loaded into the table buffer. Client-specific tables are often buffered generically by client.
     Partial buffering (single entry) Only single entries are read from the database and stored in the table buffer.
When you read from buffered tables, the following happens:
1.     An ABAP program requests data from a buffered table.
2.     The ABAP processor interprets the Open SQL statement. If the table is defined as a buffered table in the ABAP Dictionary, the ABAP processor checks in the local buffer on the application server to see if the table (or part of it) has already been buffered.
3.     If the table has not yet been buffered, the request is passed on to the database. If the data exists in the buffer, it is sent to the program.
4.     The database server passes the data to the application server, which places it in the table buffer.
5.     The data is passed to the program.
When you change a buffered table, the following happens:
1.     The database table is changed and the buffer on the application server is updated. The database interface logs the update statement in the table DDLOG. If the system has more than one application server, the buffer on the other servers is not updated at once.
2.     All application servers periodically read the contents of table DDLOG, and delete the corresponding contents from their buffers where necessary. The granularity depends on the buffering type. The table buffers in a distributed system are generally synchronized every 60 seconds (parameter: rsdisp/bufreftime).
3.     Within this period, users on non-synchronized application servers will read old data. The data is not recognized as obsolete until the next buffer synchronization. The next time it is accessed, it is re-read from the database.
You should buffer the following types of tables:
     Tables that are read very frequently
     Tables that are changed very infrequently
     Relatively small tables (few lines, few columns, or short columns)
     Tables where delayed update is acceptable.
Once you have buffered a table, take care not to use any Open SQL statements that bypass the buffer.
The SELECT statement bypasses the buffer when you use any of the following:
     The BYPASSING BUFFER addition in the FROM clause
     The DISTINCT addition in the SELECT clause
     Aggregate expressions in the SELECT clause
     Joins in the FROM clause
     The IS NULL condition in the WHERE clause
     Subqueries in the WHERE clause
     The ORDER BY clause
     The GROUP BY clause
     The FOR UPDATE addition
Furthermore, all Native SQL statements bypass the buffer.
Avoid Reading Data Repeatedly
If you avoid reading the same data repeatedly, you both reduce the number of database accesses and reduce the load on the database. Furthermore, a "dirty read" may occur with database tables other than Oracle. This means that the second time you read data from a database table, it may be different from the data read the first time. To ensure that the data in your program is consistent, you should read it once only and then store it in an internal table.
Sort Data in Your ABAP Programs
The ORDER BY clause in the SELECT statement is not necessarily optimized by the database system or executed with the correct index. This can result in increased runtime costs. You should only use ORDER BY if the database sort uses the same index with which the table is read. To find out which index the system uses, use SQL Trace in the ABAP Workbench Performance Trace. If the indexes are not the same, it is more efficient to read the data into an internal table or extract and sort it in the ABAP program using the SORT statement.
Use Logical Databases
SAP supplies logical databases for all applications. A logical database is an ABAP program that decouples Open SQL statements from application programs. They are optimized for the best possible database performance. However, it is important that you use the right logical database. The hierarchy of the data you want to read must reflect the structure of the logical database, otherwise, they can have a negative effect on performance. For example, if you want to read data from a table right at the bottom of the hierarchy of the logical database, it has to read at least the key fields of all tables above it in the hierarchy. In this case, it is more efficient to use a SELECT statement.
Work Processes
Work processes execute the individual dialog steps in R/3 applications. The next two sections describe firstly the structure of a work process, and secondly the different types of work process in the R/3 System.
Structure of a Work Process
Work processes execute the dialog steps of application programs. They are components of an application server. The following diagram shows the components of a work process:
Each work process contains two software processors and a database interface.
Screen Processor
In R/3 application programming, there is a difference between user interaction and processing logic. From a programming point of view, user interaction is controlled by screens. As well as the actual input mask, a screen also consists of flow logic. The screen flow logic controls a large part of the user interaction. The R/3 Basis system contains a special language for programming screen flow logic. The screen processor executes the screen flow logic. Via the dispatcher, it takes over the responsibility for communication between the work process and the SAPgui, calls modules in the flow logic, and ensures that the field contents are transferred from the screen to the flow logic.
ABAP Processor
The actual processing logic of an application program is written in ABAP - SAPs own programming language. The ABAP processor executes the processing logic of the application program, and communicates with the database interface. The screen processor tells the ABAP processor which module of the screen flow logic should be processed next. The following screen illustrates the interaction between the screen and the ABAP processors when an application program is running.
Database Interface
The database interface provides the following services:
     Establishing and terminating connections between the work process and the database.
     Access to database tables
     Access to R/3 Repository objects (ABAP programs, screens and so on)
     Access to catalog information (ABAP Dictionary)
     Controlling transactions (commit and rollback handling)
     Table buffer administration on the application server.
The following diagram shows the individual components of the database interface:
The diagram shows that there are two different ways of accessing databases: Open SQL and Native SQL.
Open SQL statements are a subset of Standard SQL that is fully integrated in ABAP. They allow you to access data irrespective of the database system that the R/3 installation is using. Open SQL consists of the Data Manipulation Language (DML) part of Standard SQL; in other words, it allows you to read (SELECT) and change (INSERT, UPDATE, DELETE) data. The tasks of the Data Definition Language (DDL) and Data Control Language (DCL) parts of Standard SQL are performed in the R/3 System by the ABAP Dictionary and the authorization system. These provide a unified range of functions, irrespective of database, and also contain functions beyond those offered by the various database systems.
Open SQL also goes beyond Standard SQL to provide statements that, in conjunction with other ABAP constructions, can simplify or speed up database access. It also allows you to buffer certain tables on the application server, saving excessive database access. In this case, the database interface is responsible for comparing the buffer with the database. Buffers are partly stored in the working memory of the current work process, and partly in the shared memory for all work processes on an application server. Where an R/3 System is distributed across more than one application server, the data in the various buffers is synchronized at set intervals by the buffer management. When buffering the database, you must remember that data in the buffer is not always up to date. For this reason, you should only use the buffer for data which does not often change.
Native SQL is only loosely integrated into ABAP, and allows access to all of the functions contained in the programming interface of the respective database system. Unlike Open SQL statements, Native SQL statements are not checked and converted, but instead are sent directly to the database system. Programs that use Native SQL are specific to the database system for which they were written. R/3 applications contain as little Native SQL as possible. In fact, it is only used in a few Basis components (for example, to create or change table definitions in the ABAP Dictionary).
The database-dependent layer in the diagram serves to hide the differences between database systems from the rest of the database interface. You choose the appropriate layer when you install the Basis system. Thanks to the standardization of SQL, the differences in the syntax of statements are very slight. However, the semantics and behavior of the statements have not been fully standardized, and the differences in these areas can be greater. When you use Native SQL, the function of the database-dependent layer is minimal.
Types of Work Process
Although all work processes contain the components described above, they can still be divided into different types. The type of a work process determines the kind of task for which it is responsible in the application server. It does not specify a particular set of technical attributes. The individual tasks are distributed to the work processes by the dispatcher.
Before you start your R/3 System, you determine how many work processes it will have, and what their types will be. The dispatcher starts the work processes and only assigns them tasks that correspond to their type. This means that you can distribute work process types to optimize the use of the resources on your application servers.
The following diagram shows again the structure of an application server, but this time, includes the various possible work process types:
The various work processes are described briefly below. Other parts of this documentation describe the individual components of the application server and the R/3 System in more detail.
Dialog Work Process
Dialog work processes deal with requests from an active user to execute dialog steps.
Update Work Process
Update work processes execute database update requests. Update requests are part of an SAP LUW that bundle the database operations resulting from the dialog in a database LUW for processing in the background.
Background Work Process
Background work processes process programs that can be executed without user interaction (background jobs).
Enqueue Work Process
The enqueue work process administers a lock table in the shared memory area. The lock table contains the logical database locks for the R/3 System and is an important part of the SAP LUW concept. In an R/3 System, you may only have one lock table. You may therefore also only have one application server with enqueue work processes.
Spool Work Process
The spool work process passes sequential datasets to a printer or to optical archiving. Each application server may contain several spool work process.
The services offered by an application server are determined by the types of its work processes. One application server may, of course, have more than one function. For example, it may be both a dialog server and the enqueue server, if it has several dialog work processes and an enqueue work process.
You can use the system administration functions to switch a work process between dialog and background modes while the system is still running. This allows you, for example, to switch an R/3 System between day and night operation, where you have more dialog than background work processes during the day, and the other way around during the night.
ABAP Application Server
R/3 programs run on application servers. They are an important component of the R/3 System. The following sections describe application servers in more detail.
Structure of an ABAP Application Server
The application layer of an R/3 System is made up of the application servers and the message server. Application programs in an R/3 System are run on application servers. The application servers communicate with the presentation components, the database, and also with each other, using the message server.
The following diagram shows the structure of an application server:
The individual components are:
Work Processes
An application server contains work processes, which are components that can run an application. Work processes are components that are able to execute an application (that is, one dialog step each). Each work process is linked to a memory area containing the context of the application being run. The context contains the current data for the application program. This needs to be available in each dialog step. Further information about the different types of work process is contained later on in this documentation.
Dispatcher
Each application server contains a dispatcher. The dispatcher is the link between the work processes and the users logged onto the application server. Its task is to receive requests for dialog steps from the SAP GUI and direct them to a free work process. In the same way, it directs screen output resulting from the dialog step back to the appropriate user.
Gateway
Each application server contains a gateway. This is the interface for the R/3 communication protocols (RFC, CPI/C). It can communicate with other application servers in the same R/3 System, with other R/3 Systems, with R/2 Systems, or with non-SAP systems.
The application server structure as described here aids the performance and scalability of the entire R/3 System. The fixed number of work processes and dispatching of dialog steps leads to optimal memory use, since it means that certain components and the memory areas of a work process are application-independent and reusable. The fact that the individual work processes work independently makes them suitable for a multi-processor architecture. The methods used in the dispatcher to distribute tasks to work processes are discussed more closely in the section Dispatching Dialog Steps.
Shared Memory
All of the work processes on an application server use a common main memory area called shared memory to save contexts or to buffer constant data locally.
The resources that all work processes use (such as programs and table contents) are contained in shared memory. Memory management in the R/3 System ensures that the work processes always address the correct context, that is the data relevant to the current state of the program that is running. A mapping process projects the required context for a dialog step from shared memory into the address of the relevant work process. This reduces the actual copying to a minimum.
Local buffering of data in the shared memory of the application server reduces the number of database reads required. This reduces access times for application programs considerably. For optimal use of the buffer, you can concentrate individual applications (financial accounting, logistics, human resources) into separate application server groups.
Database Connection
When you start up an R/3 System, each application server registers its work processes with the database layer, and receives a single dedicated channel for each. While the system is running, each work process is a user (client) of the database system (server). You cannot change the work process registration while the system is running. Neither can you reassign a database channel from one work process to another. For this reason, a work process can only make database changes within a single database logical unit of work (LUW). A database LUW is an inseparable sequence of database operations. This has important consequences for the programming model explained below.
Dispatching Dialog Steps
The number of users logged onto an application server is often many times greater than the number of available work processes. Furthermore, it is not restricted by the R/3 system architecture. Furthermore, each user can run several applications at once. The dispatcher has the important task of distributing all dialog steps among the work processes on the application server.
The following diagram is an example of how this might happen:
       1.      The dispatcher receives the request to execute a dialog step from user 1 and directs it to work process 1, which happens to be free. The work process addresses the context of the application program (in shared memory) and executes the dialog step. It then becomes free again.
       2.      The dispatcher receives the request to execute a dialog step from user 2 and directs it to work process 1, which is now free again. The work process executes the dialog step as in step 1.
       3.      While work process 1 is still working, the dispatcher receives a further request from user 1 and directs it to work process 2, which is free.
       4.      After work processes 1 and 2 have finished processing their dialog steps, the dispatcher receives another request from user 1 and directs it to work process 1, which is free again.
       5.      While work process 1 is still working, the dispatcher receives a further request from user 2 and directs it to work process 2, which is free.
From this example, we can see that:
        A dialog step from a program is assigned to a single work process for execution.
        The individual dialog steps of a program can be executed on different work processes, and the program context must be addressed for each new work process.
        A work process can execute dialog steps of different programs from different users.
The example does not show that the dispatcher tries to distribute the requests to the work processes such that the same work process is used as often as possible for the successive dialog steps in an application. This is useful, since it saves the program context having to be addressed each time a dialog step is executed.
Dispatching and the Programming Model
The separation of application and presentation layer made it necessary to split up application programs into dialog steps. This, and the fact that dialog steps are dispatched to individual work processes, has had important consequences for the programming model.
As mentioned above, a work process can only make database changes within a single database logical unit of work (LUW). A database LUW is an inseparable sequence of database operations. The contents of the database must be consistent at its beginning and end. The beginning and end of a database LUW are defined by a commit command to the database system (database commit). During a database LUW, that is, between two database commits, the database system itself ensures consistency within the database. In other words, it takes over tasks such as locking database entries while they are being edited, or restoring the old data (rollback) if a step terminates in an error.
A typical SAP application program extends over several screens and the corresponding dialog steps. The user requests database changes on the individual screens that should lead to the database being consistent once the screens have all been processed. However, the individual dialog steps run on different work processes, and a single work process can process dialog steps from other applications. It is clear that two or more independent applications whose dialog steps happen to be processed on the same work process cannot be allowed to work with the same database LUW.
Consequently, a work process must open a separate database LUW for each dialog step. The work process sends a commit command (database commit) to the database at the end of each dialog step in which it makes database changes. These commit commands are called implicit database commits, since they are not explicitly written into the application program.
These implicit database commits mean that a database LUW can be kept open for a maximum of one dialog step. This leads to a considerable reduction in database load, serialization, and deadlocks, and enables a large number of users to use the same system.
However, the question now arises of how this method (1 dialog step = 1 database LUW) can be reconciled with the demand to make commits and rollbacks dependent on the logical flow of the application program instead of the technical distribution of dialog steps. Database update requests that depend on one another form logical units in the program that extend over more than one dialog step. The database changes associated with these logical units must be executed together and must also be able to be undone together.
The SAP programming model contains a series of bundling techniques that allow you to group database updates together in logical units. The section of an R/3 application program that bundles a set of logically-associated database operations is called an SAP LUW. Unlike a database LUW, a SAP LUW includes all of the dialog steps in a logical unit, including the database update.
Happy Reading...
shibu

Error in OLTP 2.0 extractor during init. selection

Similar Messages

Maybe you are looking for