XI on sp13?
Hi
We are currently trying to install XI SR1 on AIX64/ORACLE, and the XI installation is failing. We have installed Central Instance, DB and Java add-in, but patched BASIS to sp13, before the XI installation, was this a mistake? sapinst for XI is now chucking us out immediately after first screen where we select XI as what we want to install, with the error message:
"CJS-20063 No appropriate Instance found. DIAGNOSIS: No locally installed Central Instance at all detected, or Instance not of current version. SOLUTION: Restart installation after fulfilling all installation prerequisites."
We have tried running another sapinst from a different place on the filesytem and referncing catalog.properties but get the same error message. And the ABAP and Java stacks seemingly work okay and we can log into both.
So I was wondering if this is because BASIS has been patched to sp13? - could this cause the above error? Has anyone done this successfully, or is the only option to not patch basis until after XI is successfully installed?
Cheers,
Chris
Hi Chris,
When you patched, did you patch (stack) you're entire installation? So you brought the system up to basis stack 13, but did you also goto ABA stack 13? How about J2EE stack 13? At a minumum, your Basis and J2EE stacks should always match. If you aren't there yet, get your XI box to stack 13 all around before moving forward. You should, in the course of the patching, remember to update your kernel patch level as well.
It should not be a problem to go your route, but a best practices approach would always be: install the product completly, then perform your patching.
Hope this helps.
-Tim
Similar Messages
-
Error Updating WAS SP13 -- SPS18, Phase Deploy Online: SAPJTECHS18_0.SCA
hello,
I can not update SAP WAS Java SP13 to SPS18. I get an error message during phase "deploy online" (18 of 24). see the error message and log below.
Previous to running the update I successfully run the WAS SP18 Prerequisite Check based on "WAS-PREREQUISITE_CHECK_DATA_640.XML" downloaded at 2006-08-24 without any warnings or errors.
I used sapcar 6.40 patchlevel 4, I extracted the following downloaded files in this order:
sapcar -xvf SAPINST18_0-20000118.SAR -R NW04-WebASJava-18
sapcar -xvf CTRLMSS18_0-20000118.SAR -R NW04-WebASJava-18
sapcar -xvf J2EERT18_0-10001982.SAR -R NW04-WebASJava-18
sapcar -xvf J2EERTOS18_0-20000118.SAR -R NW04-WebASJava-18
for any help I would be very greatful.
thanks, volker.
WARNING 2006-08-25 01:42:13
Execution of the command "C:\j2sdk1.4.2_12/bin/java.exe '-Xmx256M' '-jar' 'C:\usr\sap/J2E/JC00/SDM/program/bin/SDM.jar' 'deploy' 'list=C:\Program Files\sapinst_instdir\PATCH\MSS/SDAS_TO_BE_DEPLOYED.LST' 'onerror=stop' 'sdmhome=C:\usr\sap/J2E/JC00/SDM/program' 'logfile=C:\Program Files\sapinst_instdir\PATCH\MSS/callSdmViaSapinst.log' 'logtoconsole=true'" finished with return code 4. Output: Info: Info: ============================================Info: = Starting to execute command 'deploy' =Info: ============================================Info: Starting SDM - Software Deployment Manager...Starting SDM - Software Deployment Manager...Info: tc/SL/SDM/SDM/sap.com/SAP AG/6.4018.00.0000.20060706111659.0000tc/SL/SDM/SDM/sap.com/SAP AG/6.4018.00.0000.20060706111659.0000Info: SDM operation mode successfully set to: StandaloneInitializing Network Manager (50017)Info: Initializing Network Manager (50017)Checking if another SDM is running on port 50018Info: Checking if another SDM is running on port 50018Info: -
Starting deployment -
Info: Error handling strategy: OnErrorStopInfo: Prerequisite error handling strategy: OnPrerequisiteErrorStopInfo: Update strategy: UpdateLowerVersionsInfo: Starting deployment prerequisites:Info: Loading selected archives...Info: Loading archive 'S:\SAP\Downloads\200608\NW04-WebASJava-18\J2EE-RUNT-CD\J2EE-ENG\ONLINE\SAPJTECHS18_0.SCA'Info: Selected archives successfully loaded.Info: Actions per selected component:Info: Update: Selected development component 'com.sap.security.core.admin'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060706111713.0000'/'0' updates currently deployed development component 'com.sap.security.core.admin'/'sap.com'/'SAP AG'/'6.4013.00.0000.20050621161034.0000'/'0'.Info: Update: Selected development component 'com.sap.aii.ibtranslationclient'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060413102101.0000'/'0' updates currently deployed development component 'com.sap.aii.ibtranslationclient'/'sap.com'/'SAP AG'/'6.4013.00.0000.20050331133226.0000'/'0'.Info: Update: Selected development component 'com.sap.rprof.jddschema'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060413101559.0000'/'0' updates currently deployed development component 'com.sap.rprof.jddschema'/'sap.com'/'SAP AG'/'6.4013.00.0000.20040609162409.0000'/'0'.Info: Initial deployment: Selected development component 'tc/wd/wslib'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060726153907.0000'/'0' will be deployed.Info: Update: Selected development component 'tc/workflowmodeler'/'sap.com'/'SAP AG'/'6.4018.00.0000.20050606172955.0000'/'0' updates currently deployed development component 'tc/workflowmodeler'/'sap.com'/'SAP AG'/'6.4013.00.0000.20050606172955.0000'/'0'.Info: Update: Selected development component 'com.sap.lcr.saprfc'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060706111625.0000'/'0' updates currently deployed development component 'com.sap.lcr.saprfc'/'sap.com'/'SAP AG'/'6.4013.00.0000.20050629160141.0000'/'0'.Info: Update: Selected development component 'tc/wd/pdfsvrchal'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060706112627.0000'/'0' updates currently deployed development component 'tc/wd/pdfsvrchal'/'sap.com'/'SAP AG'/'6.4013.00.0000.20050606171958.0000'/'0'.Info: Update: Selected development component 'com.sap.aii.util.rb'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060413102101.0000'/'0' updates currently deployed development component 'com.sap.aii.util.rb'/'sap.com'/'SAP AG'/'6.4013.00.0000.20050331133226.0000'/'0'.Info: Update: Selected development component 'com.sapportals.supportplatform.dbschema'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060706111519.0000'/'0' updates currently deployed development component 'com.sapportals.supportplatform.dbschema'/'sap.com'/'SAP AG'/'6.4013.00.0000.20050719155812.0000'/'0'.Info: Update: Selected development component 'com.sap.util.monitor.grmg'/'sap.com'/'SAP AG'/'6.4018.00.0000.20050818153022.0000'/'0' updates currently deployed development component 'com.sap.util.monitor.grmg'/'sap.com'/'SAP AG'/'6.4013.00.0000.20050621154902.0000'/'0'.Info: Update: Selected development component 'com.sap.engine.customizing.ccms'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060814115206.0000'/'0' updates currently deployed development component 'com.sap.engine.customizing.ccms'/'sap.com'/'SAP AG'/'6.4013.00.0000.20050712155016.0000'/'0'.Info: Update: Selected development component 'tc/supportplatform/engine'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060706111519.0000'/'0' updates currently deployed development component 'tc/supportplatform/engine'/'sap.com'/'SAP AG'/'6.4013.00.0000.20050719155812.0000'/'0'.Info: Initial deployment: Selected development component 'tc/SL/utility/wsear'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060119145451.0000'/'0' will be deployed.Info: Update: Selected development component 'com.sap.lcr.namealloc'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060706111625.0000'/'0' updates currently deployed development component 'com.sap.lcr.namealloc'/'sap.com'/'SAP AG'/'6.4013.00.0000.20050629160141.0000'/'0'.Info: Update: Selected development component 'SQLTrace'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060706112013.0000'/'0' updates currently deployed development component 'SQLTrace'/'sap.com'/'SAP AG'/'6.4013.00.0000.20050623162450.0000'/'0'.Info: Update: Selected development component 'tc/bcb/api'/'sap.com'/'SAP AG'/'6.4018.00.0000.20050606172625.0000'/'0' updates currently deployed development component 'tc/bcb/api'/'sap.com'/'SAP AG'/'6.4013.00.0000.20050606172625.0000'/'0'.Info: Update: Selected development component 'com.sap.lcr'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060706111625.0000'/'0' updates currently deployed development component 'com.sap.lcr'/'sap.com'/'SAP AG'/'6.4013.00.0000.20050629160141.0000'/'0'.Info: Update: Selected development component 'com.sap.rprof.remoteProfile'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060413101559.0000'/'0' updates currently deployed development component 'com.sap.rprof.remoteProfile'/'sap.com'/'SAP AG'/'6.4013.00.0000.20040609162409.0000'/'0'.Info: Update: Selected development component 'com.sapmarkets.mesyncjco'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060413101332.0000'/'0' updates currently deployed development component 'com.sapmarkets.mesyncjco'/'sap.com'/'SAP AG'/'6.4013.00.0000.20050617154156.0000'/'0'.Info: Update: Selected development component 'tc/TechSrv/xml_das_connector_init'/'sap.com'/'SAP AG'/'6.4018.00.0000.20051027101045.0000'/'0' updates currently deployed development component 'tc/TechSrv/xml_das_connector_init'/'sap.com'/'SAP AG'/'6.4013.00.0000.20041104140052.0000'/'0'.Info: Update: Selected development component 'tc/uddi/dbschema'/'sap.com'/'SAP AG'/'6.4018.00.0000.20050606164207.0000'/'0' updates currently deployed development component 'tc/uddi/dbschema'/'sap.com'/'SAP AG'/'6.4013.00.0000.20050606164207.0000'/'0'.Info: Update: Selected development component 'tc/sec/wssec/app'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060706111002.0000'/'0' updates currently deployed development component 'tc/sec/wssec/app'/'sap.com'/'SAP AG'/'6.4013.00.0000.20050609111110.0000'/'0'.Info: Update: Selected development component 'tc/TechSrv/XML_DAS_Connector_Schema'/'sap.com'/'SAP AG'/'6.4018.00.0000.20051027101045.0000'/'0' updates currently deployed development component 'tc/TechSrv/XML_DAS_Connector_Schema'/'sap.com'/'SAP AG'/'6.4013.00.0000.20041104140052.0000'/'0'.Info: Update: Selected development component 'tc/wd/tools'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060706112627.0000'/'0' updates currently deployed development component 'tc/wd/tools'/'sap.com'/'SAP AG'/'6.4013.00.0000.20050606171958.0000'/'0'.Info: Update: Selected development component 'com.sap.util.monitor.jarm.j2ee'/'sap.com'/'SAP AG'/'6.4018.00.0000.20051027104030.0000'/'0' updates currently deployed development component 'com.sap.util.monitor.jarm.j2ee'/'sap.com'/'SAP AG'/'6.4013.00.0000.20050606163854.0000'/'0'.Info: Update: Selected development component 'tc/wd/dispwda'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060726153907.0000'/'0' updates currently deployed development component 'tc/wd/dispwda'/'sap.com'/'SAP AG'/'6.4013.00.0000.20050628104636.0000'/'0'.Info: Update: Selected development component 'tc/bcb/ici'/'sap.com'/'SAP AG'/'6.4018.00.0000.20050606172625.0000'/'0' updates currently deployed development component 'tc/bcb/ici'/'sap.com'/'SAP AG'/'6.4013.00.0000.20050606172625.0000'/'0'.Info: Update: Selected development component 'com.sapportals.htmlb'/'sap.com'/'SAP AG'/'6.4018.00.0000.20050121164722.0000'/'0' updates currently deployed development component 'com.sapportals.htmlb'/'sap.com'/'SAP AG'/'6.4013.00.0000.20050121164722.0000'/'0'.Info: No action: Selected development component 'synclog'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060706112013.0000'/'1' will not update currently deployed development component 'synclog'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060706112013.0000'/'0'.Info: Update: Selected development component 'tc/monitoring/systeminfo'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060814115206.0000'/'0' updates currently deployed development component 'tc/monitoring/systeminfo'/'sap.com'/'SAP AG'/'6.4013.00.0000.20050712155016.0000'/'0'.Info: Update: Selected development component 'com.sap.aii.util.misc'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060413102101.0000'/'0' updates currently deployed development component 'com.sap.aii.util.misc'/'sap.com'/'SAP AG'/'6.4013.00.0000.20050331133226.0000'/'0'.Info: Update: Selected development component 'tc/sld/data'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060706111625.0000'/'0' updates currently deployed development component 'tc/sld/data'/'sap.com'/'SAP AG'/'6.4013.00.0000.20050629160141.0000'/'0'.Info: Update: Selected development component 'tc/TechSrv/XML_DAS_Connector'/'sap.com'/'SAP AG'/'6.4018.00.0000.20051027101045.0000'/'0' updates currently deployed development component 'tc/TechSrv/XML_DAS_Connector'/'sap.com'/'SAP AG'/'6.4013.00.0000.20041104140052.0000'/'0'.Info: Update: Selected development component 'com.sap.aii.proxy.framework'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060413102101.0000'/'0' updates currently deployed development component 'com.sap.aii.proxy.framework'/'sap.com'/'SAP AG'/'6.4013.00.0000.20050331133226.0000'/'0'.Info: Update: Selected development component 'com.sapportals.supportplatform'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060706111519.0000'/'0' updates currently deployed development component 'com.sapportals.supportplatform'/'sap.com'/'SAP AG'/'6.4013.00.0000.20050719155812.0000'/'0'.Info: Update: Selected software component 'SAP_JTECHS'/'sap.com'/'SAP AG'/'1000.6. ...
ERROR 2006-08-25 01:42:13
MUT-02041 SDM call of deploySdaList ends with returncode 4. See output of logfile C:\Program Files\sapinst_instdir\PATCH\MSS\callSdmViaSapinst.log.
ERROR 2006-08-25 01:42:13
MUT-03025 Caught ESAPinstException in Modulecall: ESAPinstException: error text undefined.
this is the contents of callSdmViaSapinst.log:
Aug 25, 2006 12:30:06... Info: Start logging to console
Aug 25, 2006 12:30:06... Info:
Aug 25, 2006 12:30:06... Info: ============================================
Aug 25, 2006 12:30:06... Info: = Starting to execute command 'deploy' =
Aug 25, 2006 12:30:06... Info: ============================================
Aug 25, 2006 12:30:06... Info: Starting SDM - Software Deployment Manager...
Aug 25, 2006 12:30:06... Info: tc/SL/SDM/SDM/sap.com/SAP AG/6.4018.00.0000.20060706111659.0000
Aug 25, 2006 12:30:08... Info: SDM operation mode successfully set to: Standalone
Aug 25, 2006 12:30:08... Info: Initializing Network Manager (50017)
Aug 25, 2006 12:30:08... Info: Checking if another SDM is running on port 50018
Aug 25, 2006 12:30:08... Info: -
Starting deployment -
Aug 25, 2006 12:30:08... Info: Error handling strategy: OnErrorStop
Aug 25, 2006 12:30:08... Info: Prerequisite error handling strategy: OnPrerequisiteErrorStop
Aug 25, 2006 12:30:08... Info: Update strategy: UpdateLowerVersions
Aug 25, 2006 12:30:08... Info: Starting deployment prerequisites:
Aug 25, 2006 12:30:11... Info: Loading selected archives...
Aug 25, 2006 12:30:11... Info: Loading archive 'S:\SAP\Downloads\200608\NW04-WebASJava-18\J2EE-RUNT-CD\J2EE-ENG\ONLINE\SAPJTECHS18_0.SCA'
Aug 25, 2006 12:30:16... Info: Selected archives successfully loaded.
Aug 25, 2006 12:30:18... Info: Actions per selected component:
Aug 25, 2006 12:30:18... Info: Update: Selected development component 'com.sap.security.core.admin'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060706111713.0000'/'0' updates currently deployed development component 'com.sap.security.core.admin'/'sap.com'/'SAP AG'/'6.4013.00.0000.20050621161034.0000'/'0'.
Aug 25, 2006 12:30:18... Info: Update: Selected development component 'com.sap.aii.ibtranslationclient'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060413102101.0000'/'0' updates currently deployed development component 'com.sap.aii.ibtranslationclient'/'sap.com'/'SAP AG'/'6.4013.00.0000.20050331133226.0000'/'0'.
Aug 25, 2006 12:30:18... Info: Update: Selected development component 'com.sap.rprof.jddschema'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060413101559.0000'/'0' updates currently deployed development component 'com.sap.rprof.jddschema'/'sap.com'/'SAP AG'/'6.4013.00.0000.20040609162409.0000'/'0'.
Aug 25, 2006 12:30:18... Info: Initial deployment: Selected development component 'tc/wd/wslib'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060726153907.0000'/'0' will be deployed.
Aug 25, 2006 12:30:18... Info: Update: Selected development component 'tc/workflowmodeler'/'sap.com'/'SAP AG'/'6.4018.00.0000.20050606172955.0000'/'0' updates currently deployed development component 'tc/workflowmodeler'/'sap.com'/'SAP AG'/'6.4013.00.0000.20050606172955.0000'/'0'.
Aug 25, 2006 12:30:18... Info: Update: Selected development component 'com.sap.lcr.saprfc'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060706111625.0000'/'0' updates currently deployed development component 'com.sap.lcr.saprfc'/'sap.com'/'SAP AG'/'6.4013.00.0000.20050629160141.0000'/'0'.
Aug 25, 2006 12:30:18... Info: Update: Selected development component 'tc/wd/pdfsvrchal'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060706112627.0000'/'0' updates currently deployed development component 'tc/wd/pdfsvrchal'/'sap.com'/'SAP AG'/'6.4013.00.0000.20050606171958.0000'/'0'.
Aug 25, 2006 12:30:18... Info: Update: Selected development component 'com.sap.aii.util.rb'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060413102101.0000'/'0' updates currently deployed development component 'com.sap.aii.util.rb'/'sap.com'/'SAP AG'/'6.4013.00.0000.20050331133226.0000'/'0'.
Aug 25, 2006 12:30:18... Info: Update: Selected development component 'com.sapportals.supportplatform.dbschema'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060706111519.0000'/'0' updates currently deployed development component 'com.sapportals.supportplatform.dbschema'/'sap.com'/'SAP AG'/'6.4013.00.0000.20050719155812.0000'/'0'.
Aug 25, 2006 12:30:18... Info: Update: Selected development component 'com.sap.util.monitor.grmg'/'sap.com'/'SAP AG'/'6.4018.00.0000.20050818153022.0000'/'0' updates currently deployed development component 'com.sap.util.monitor.grmg'/'sap.com'/'SAP AG'/'6.4013.00.0000.20050621154902.0000'/'0'.
Aug 25, 2006 12:30:18... Info: Update: Selected development component 'com.sap.engine.customizing.ccms'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060814115206.0000'/'0' updates currently deployed development component 'com.sap.engine.customizing.ccms'/'sap.com'/'SAP AG'/'6.4013.00.0000.20050712155016.0000'/'0'.
Aug 25, 2006 12:30:18... Info: Update: Selected development component 'tc/supportplatform/engine'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060706111519.0000'/'0' updates currently deployed development component 'tc/supportplatform/engine'/'sap.com'/'SAP AG'/'6.4013.00.0000.20050719155812.0000'/'0'.
Aug 25, 2006 12:30:18... Info: Initial deployment: Selected development component 'tc/SL/utility/wsear'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060119145451.0000'/'0' will be deployed.
Aug 25, 2006 12:30:18... Info: Update: Selected development component 'com.sap.lcr.namealloc'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060706111625.0000'/'0' updates currently deployed development component 'com.sap.lcr.namealloc'/'sap.com'/'SAP AG'/'6.4013.00.0000.20050629160141.0000'/'0'.
Aug 25, 2006 12:30:18... Info: Update: Selected development component 'SQLTrace'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060706112013.0000'/'0' updates currently deployed development component 'SQLTrace'/'sap.com'/'SAP AG'/'6.4013.00.0000.20050623162450.0000'/'0'.
Aug 25, 2006 12:30:18... Info: Update: Selected development component 'tc/bcb/api'/'sap.com'/'SAP AG'/'6.4018.00.0000.20050606172625.0000'/'0' updates currently deployed development component 'tc/bcb/api'/'sap.com'/'SAP AG'/'6.4013.00.0000.20050606172625.0000'/'0'.
Aug 25, 2006 12:30:18... Info: Update: Selected development component 'com.sap.lcr'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060706111625.0000'/'0' updates currently deployed development component 'com.sap.lcr'/'sap.com'/'SAP AG'/'6.4013.00.0000.20050629160141.0000'/'0'.
Aug 25, 2006 12:30:18... Info: Update: Selected development component 'com.sap.rprof.remoteProfile'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060413101559.0000'/'0' updates currently deployed development component 'com.sap.rprof.remoteProfile'/'sap.com'/'SAP AG'/'6.4013.00.0000.20040609162409.0000'/'0'.
Aug 25, 2006 12:30:18... Info: Update: Selected development component 'com.sapmarkets.mesyncjco'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060413101332.0000'/'0' updates currently deployed development component 'com.sapmarkets.mesyncjco'/'sap.com'/'SAP AG'/'6.4013.00.0000.20050617154156.0000'/'0'.
Aug 25, 2006 12:30:18... Info: Update: Selected development component 'tc/TechSrv/xml_das_connector_init'/'sap.com'/'SAP AG'/'6.4018.00.0000.20051027101045.0000'/'0' updates currently deployed development component 'tc/TechSrv/xml_das_connector_init'/'sap.com'/'SAP AG'/'6.4013.00.0000.20041104140052.0000'/'0'.
Aug 25, 2006 12:30:18... Info: Update: Selected development component 'tc/uddi/dbschema'/'sap.com'/'SAP AG'/'6.4018.00.0000.20050606164207.0000'/'0' updates currently deployed development component 'tc/uddi/dbschema'/'sap.com'/'SAP AG'/'6.4013.00.0000.20050606164207.0000'/'0'.
Aug 25, 2006 12:30:18... Info: Update: Selected development component 'tc/sec/wssec/app'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060706111002.0000'/'0' updates currently deployed development component 'tc/sec/wssec/app'/'sap.com'/'SAP AG'/'6.4013.00.0000.20050609111110.0000'/'0'.
Aug 25, 2006 12:30:18... Info: Update: Selected development component 'tc/TechSrv/XML_DAS_Connector_Schema'/'sap.com'/'SAP AG'/'6.4018.00.0000.20051027101045.0000'/'0' updates currently deployed development component 'tc/TechSrv/XML_DAS_Connector_Schema'/'sap.com'/'SAP AG'/'6.4013.00.0000.20041104140052.0000'/'0'.
Aug 25, 2006 12:30:18... Info: Update: Selected development component 'tc/wd/tools'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060706112627.0000'/'0' updates currently deployed development component 'tc/wd/tools'/'sap.com'/'SAP AG'/'6.4013.00.0000.20050606171958.0000'/'0'.
Aug 25, 2006 12:30:18... Info: Update: Selected development component 'com.sap.util.monitor.jarm.j2ee'/'sap.com'/'SAP AG'/'6.4018.00.0000.20051027104030.0000'/'0' updates currently deployed development component 'com.sap.util.monitor.jarm.j2ee'/'sap.com'/'SAP AG'/'6.4013.00.0000.20050606163854.0000'/'0'.
Aug 25, 2006 12:30:18... Info: Update: Selected development component 'tc/wd/dispwda'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060726153907.0000'/'0' updates currently deployed development component 'tc/wd/dispwda'/'sap.com'/'SAP AG'/'6.4013.00.0000.20050628104636.0000'/'0'.
Aug 25, 2006 12:30:18... Info: Update: Selected development component 'tc/bcb/ici'/'sap.com'/'SAP AG'/'6.4018.00.0000.20050606172625.0000'/'0' updates currently deployed development component 'tc/bcb/ici'/'sap.com'/'SAP AG'/'6.4013.00.0000.20050606172625.0000'/'0'.
Aug 25, 2006 12:30:18... Info: Update: Selected development component 'com.sapportals.htmlb'/'sap.com'/'SAP AG'/'6.4018.00.0000.20050121164722.0000'/'0' updates currently deployed development component 'com.sapportals.htmlb'/'sap.com'/'SAP AG'/'6.4013.00.0000.20050121164722.0000'/'0'.
Aug 25, 2006 12:30:18... Info: No action: Selected development component 'synclog'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060706112013.0000'/'1' will not update currently deployed development component 'synclog'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060706112013.0000'/'0'.
Aug 25, 2006 12:30:18... Info: Update: Selected development component 'tc/monitoring/systeminfo'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060814115206.0000'/'0' updates currently deployed development component 'tc/monitoring/systeminfo'/'sap.com'/'SAP AG'/'6.4013.00.0000.20050712155016.0000'/'0'.
Aug 25, 2006 12:30:18... Info: Update: Selected development component 'com.sap.aii.util.misc'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060413102101.0000'/'0' updates currently deployed development component 'com.sap.aii.util.misc'/'sap.com'/'SAP AG'/'6.4013.00.0000.20050331133226.0000'/'0'.
Aug 25, 2006 12:30:18... Info: Update: Selected development component 'tc/sld/data'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060706111625.0000'/'0' updates currently deployed development component 'tc/sld/data'/'sap.com'/'SAP AG'/'6.4013.00.0000.20050629160141.0000'/'0'.
Aug 25, 2006 12:30:18... Info: Update: Selected development component 'tc/TechSrv/XML_DAS_Connector'/'sap.com'/'SAP AG'/'6.4018.00.0000.20051027101045.0000'/'0' updates currently deployed development component 'tc/TechSrv/XML_DAS_Connector'/'sap.com'/'SAP AG'/'6.4013.00.0000.20041104140052.0000'/'0'.
Aug 25, 2006 12:30:18... Info: Update: Selected development component 'com.sap.aii.proxy.framework'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060413102101.0000'/'0' updates currently deployed development component 'com.sap.aii.proxy.framework'/'sap.com'/'SAP AG'/'6.4013.00.0000.20050331133226.0000'/'0'.
Aug 25, 2006 12:30:18... Info: Update: Selected development component 'com.sapportals.supportplatform'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060706111519.0000'/'0' updates currently deployed development component 'com.sapportals.supportplatform'/'sap.com'/'SAP AG'/'6.4013.00.0000.20050719155812.0000'/'0'.
Aug 25, 2006 12:30:18... Info: Update: Selected software component 'SAP_JTECHS'/'sap.com'/'SAP AG'/'1000.6.40.18.0.20060816080857''/'0' updates currently deployed software component 'SAP_JTECHS'/'sap.com'/'SAP AG'/'1000.6.40.13.0.20050720034335''/'0'.
Aug 25, 2006 12:30:18... Info: Update: Selected development component 'com.sap.engine.docs.examples'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060814115206.0000'/'0' updates currently deployed development component 'com.sap.engine.docs.examples'/'sap.com'/'SAP AG'/'6.4013.00.0000.20050712155016.0000'/'0'.
Aug 25, 2006 12:30:18... Info: Update: Selected development component 'com.sap.lcr.jddschema'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060706111625.0000'/'0' updates currently deployed development component 'com.sap.lcr.jddschema'/'sap.com'/'SAP AG'/'6.4013.00.0000.20050629160141.0000'/'0'.
Aug 25, 2006 12:30:18... Info: Update: Selected development component 'com.sap.engine.class.download'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060814115206.0000'/'0' updates currently deployed development component 'com.sap.engine.class.download'/'sap.com'/'SAP AG'/'6.4013.00.0000.20050712155016.0000'/'0'.
Aug 25, 2006 12:30:18... Info: Update: Selected development component 'com.sap.util.monitor.jarm.ccms'/'sap.com'/'SAP AG'/'6.4018.00.0000.20051027104030.0000'/'0' updates currently deployed development component 'com.sap.util.monitor.jarm.ccms'/'sap.com'/'SAP AG'/'6.4013.00.0000.20050606163854.0000'/'0'.
Aug 25, 2006 12:30:18... Info: Update: Selected development component 'tc/sec/vsi/app'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060706111002.0000'/'0' updates currently deployed development component 'tc/sec/vsi/app'/'sap.com'/'SAP AG'/'6.4013.00.0000.20050609111110.0000'/'0'.
Aug 25, 2006 12:30:18... Info: Update: Selected development component 'tc/uddi'/'sap.com'/'SAP AG'/'6.4018.00.0000.20050606164207.0000'/'0' updates currently deployed development component 'tc/uddi'/'sap.com'/'SAP AG'/'6.4013.00.0000.20050606164207.0000'/'0'.
Aug 25, 2006 12:30:18... Info: Update: Selected development component 'com.sap.pmi.adm'/'sap.com'/'SAP AG'/'6.4018.00.0000.20050818152118.0000'/'0' updates currently deployed development component 'com.sap.pmi.adm'/'sap.com'/'SAP AG'/'6.4013.00.0000.20050606163602.0000'/'0'.
Aug 25, 2006 12:30:18... Info: Update: Selected development component 'com.sap.jdo'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060706112029.0000'/'0' updates currently deployed development component 'com.sap.jdo'/'sap.com'/'SAP AG'/'6.4013.00.0000.20050719161053.0000'/'0'.
Aug 25, 2006 12:30:18... Info: Update: Selected development component 'tc/SL/CMS/Util'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060413101532.0000'/'0' updates currently deployed development component 'tc/SL/CMS/Util'/'sap.com'/'SAP AG'/'6.4013.00.0000.20050630075426.0000'/'0'.
Aug 25, 2006 12:30:18... Info: Update: Selected development component 'com.sap.mobile.clientinfo'/'sap.com'/'SAP AG'/'6.4018.00.0000.20050331133205.0000'/'0' updates currently deployed development component 'com.sap.mobile.clientinfo'/'sap.com'/'SAP AG'/'6.4013.00.0000.20050331133205.0000'/'0'.
Aug 25, 2006 12:30:18... Info: Update: Selected development component 'tc/conn/connectorframework'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060413100235.0000'/'0' updates currently deployed development component 'tc/conn/connectorframework'/'sap.com'/'SAP AG'/'6.4013.00.0000.20041104140206.0000'/'0'.
Aug 25, 2006 12:30:18... Info: Update: Selected development component 'tc/SL/CMS/IDEClient'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060413101532.0000'/'0' updates currently deployed development component 'tc/SL/CMS/IDEClient'/'sap.com'/'SAP AG'/'6.4013.00.0000.20050630075426.0000'/'0'.
Aug 25, 2006 12:30:18... Info: Update: Selected development component 'com.sap.ip.me.insttool'/'sap.com'/'SAP AG'/'6.4018.00.0000.20050818150135.0000'/'0' updates currently deployed development component 'com.sap.ip.me.insttool'/'sap.com'/'SAP AG'/'6.4013.00.0000.20050617154449.0000'/'0'.
Aug 25, 2006 12:30:18... Info: Update: Selected development component 'com.sap.aii.ibtransportclient'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060413102101.0000'/'0' updates currently deployed development component 'com.sap.aii.ibtransportclient'/'sap.com'/'SAP AG'/'6.4013.00.0000.20050331133226.0000'/'0'.
Aug 25, 2006 12:30:18... Info: Update: Selected development component 'com.sap.ip.me.webconsole'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060706111540.0000'/'0' updates currently deployed development component 'com.sap.ip.me.webconsole'/'sap.com'/'SAP AG'/'6.4013.00.0000.20050624161235.0000'/'0'.
Aug 25, 2006 12:30:18... Info: Update: Selected development component 'tc/wd/pdfobject'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060726153907.0000'/'0' updates currently deployed development component 'tc/wd/pdfobject'/'sap.com'/'SAP AG'/'6.4013.00.0000.20050628104636.0000'/'0'.
Aug 25, 2006 12:30:18... Info: Update: Selected development component 'com.sap.lcrabapapi'/'sap.com'/'SAP AG'/'6.4018.00.0000.20050606164103.0000'/'0' updates currently deployed development component 'com.sap.lcrabapapi'/'sap.com'/'SAP AG'/'6.4013.00.0000.20050606164103.0000'/'0'.
Aug 25, 2006 12:30:18... Info: Update: Selected development component 'tc/sec/app'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060706111002.0000'/'0' updates currently deployed development component 'tc/sec/app'/'sap.com'/'SAP AG'/'6.4013.00.0000.20050609111110.0000'/'0'.
Aug 25, 2006 12:30:18... Info: Update: Selected development component 'com.sapportals.htmlb.ear'/'sap.com'/'SAP AG'/'6.4018.00.0000.20050121164722.0000'/'0' updates currently deployed development component 'com.sapportals.htmlb.ear'/'sap.com'/'SAP AG'/'6.4013.00.0000.20050121164722.0000'/'0'.
Aug 25, 2006 12:30:18... Info: Update: Selected development component 'tc/wd/corecomp'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060706112627.0000'/'0' updates currently deployed development component 'tc/wd/corecomp'/'sap.com'/'SAP AG'/'6.4013.00.0000.20050606171958.0000'/'0'.
Aug 25, 2006 12:30:18... Info: Update: Selected development component 'tc/TechSrv/XML_DAS'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060119123705.0000'/'0' updates currently deployed development component 'tc/TechSrv/XML_DAS'/'sap.com'/'SAP AG'/'6.4013.00.0000.20050628142849.0000'/'0'.
Aug 25, 2006 12:30:18... Info: Update: Selected development component 'com.sap.aii.util.xml'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060413102101.0000'/'0' updates currently deployed development component 'com.sap.aii.util.xml'/'sap.com'/'SAP AG'/'6.4013.00.0000.20050331133226.0000'/'0'.
Aug 25, 2006 12:30:18... Info: Update: Selected development component 'tc/eCATTPing'/'sap.com'/'SAP AG'/'6.4018.00.0000.20041104140331.0000'/'0' updates currently deployed development component 'tc/eCATTPing'/'sap.com'/'SAP AG'/'6.4013.00.0000.20041104140331.0000'/'0'.
Aug 25, 2006 12:30:18... Info: Update: Selected development component 'com.sap.rprof.dbprofiles'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060413101559.0000'/'0' updates currently deployed development component 'com.sap.rprof.dbprofiles'/'sap.com'/'SAP AG'/'6.4013.00.0000.20040609162409.0000'/'0'.
Aug 25, 2006 12:30:18... Info: Update: Selected development component 'com.sap.engine.services.webservices.tool'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060814115206.0000'/'0' updates currently deployed development component 'com.sap.engine.services.webservices.tool'/'sap.com'/'SAP AG'/'6.4013.00.0000.20050712155016.0000'/'0'.
Aug 25, 2006 12:30:18... Info: Update: Selected development component 'com.sap.engine.heartbeat'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060814115206.0000'/'0' updates currently deployed development component 'com.sap.engine.heartbeat'/'sap.com'/'SAP AG'/'6.4013.00.0000.20050712155016.0000'/'0'.
Aug 25, 2006 12:30:20... Info: Ending deployment prerequisites. All items are correct.
Aug 25, 2006 12:30:20... Info: Saved current Engine state.
Aug 25, 2006 12:30:20... Info: Starting: Update: Selected development component 'com.sap.lcr.jddschema'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060706111625.0000'/'0' updates currently deployed development component 'com.sap.lcr.jddschema'/'sap.com'/'SAP AG'/'6.4013.00.0000.20050629160141.0000'/'0'.
Aug 25, 2006 12:30:20... Info: Creating connections to database "J2E".
Aug 25, 2006 12:30:20... Info: Creating vendor connection to database.
Aug 25, 2006 12:30:20... Info: Vendor connection created successfully.
Aug 25, 2006 12:30:20... Info: Creating openSQL connection to database.
Aug 25, 2006 12:30:21... Info: OpenSQL connection created successfully.
Aug 25, 2006 12:30:25... Info: <!LOGHEADER[START]/>
Aug 25, 2006 12:30:25... Info: <!HELP[Manual modification of the header may cause parsing problem!]/>
Aug 25, 2006 12:30:25... Info: <!LOGGINGVERSION[1.5.3.7186 - 630]/>
Aug 25, 2006 12:30:25... Info: <!NAME[C:\usr\sap\J2E\JC00\SDM\program\log\jddilog20060825003021.log]/>
Aug 25, 2006 12:30:25... Info: <!PATTERN[jddilog20060825003021.log]/>
Aug 25, 2006 12:30:25... Info: <!FORMATTER[com.sap.dictionary.database.dbs.DbTraceFormatter(%s %m %-30l %24d)]/>
Aug 25, 2006 12:30:25... Info: <!ENCODING[Cp1252]/>
Aug 25, 2006 12:30:25... Info: <!LOGHEADER[END]/>
Aug 25, 2006 12:30:25... Info: 0:30:21 2006-08-25 dbs-Info: $Id: //tc/DictionaryDatabase/630_VAL_REL/src/_dictionary_database_dbs/java/com/sap/dictionary/database/dbs/DbModificationManager.java#4 $
Aug 25, 2006 12:30:25... Info: 0:30:21 2006-08-25 dbs-Info: <<<<<<<<<<<<<< Tabellen-Deployment >>>>>>>>>>>>>
Aug 25, 2006 12:30:25... Info: 0:30:21 2006-08-25 dbs-Info: <<<<<<<<<<<<<< Tabellen-Deployment >>>>>>>>>>>>>
Aug 25, 2006 12:30:25... Info: 0:30:21 2006-08-25 dbs-Info:
Aug 25, 2006 12:30:25... Info: 0:30:21 2006-08-25 dbs-Info:
Aug 25, 2006 12:30:25... Info: 0:30:21 2006-08-25 dbs-Info: <<< Analysiere Tabelle BC_DDDBRTH >>>
Aug 25, 2006 12:30:25... Info: 0:30:21 2006-08-25 dbs-Info: <<< Analysiere Tabelle BC_DDDBRTH >>>
Aug 25, 2006 12:30:25... Info: 0:30:21 2006-08-25 dbs-Info: predefined action is: >>>null<<<
Aug 25, 2006 12:30:25... Info: 0:30:21 2006-08-25 dbs-Info: predefined action is: >>>null<<<
Aug 25, 2006 12:30:25... Info: 0:30:21 2006-08-25 dbs-Info: Keine Aktion fuer die Tabelle notwendig
Aug 25, 2006 12:30:25... Info: 0:30:21 2006-08-25 dbs-Info: Keine Aktion fuer die Tabelle notwendig
Aug 25, 2006 12:30:25... Info: 0:30:21 2006-08-25 dbs-Info: <<< Analysiere Tabelle BC_DDDBTABLERT >>>
Aug 25, 2006 12:30:25... Info: 0:30:21 2006-08-25 dbs-Info: <<< Analysiere Tabelle BC_DDDBTABLERT >>>
Aug 25, 2006 12:30:25... Info: 0:30:21 2006-08-25 dbs-Info: predefined action is: >>>null<<<
Aug 25, 2006 12:30:25... Info: 0:30:21 2006-08-25 dbs-Info: predefined action is: >>>null<<<
Aug 25, 2006 12:30:25... Info: 0:30:21 2006-08-25 dbs-Info: Keine Aktion fuer die Tabelle notwendig
Aug 25, 2006 12:30:25... Info: 0:30:21 2006-08-25 dbs-Info: Keine Aktion fuer die Tabelle notwendig
Aug 25, 2006 12:30:25... Info: 0:30:21 2006-08-25 dbs-Info: <<< Analysiere Tabelle BC_DDDBRTH >>>
Aug 25, 2006 12:30:25... Info: 0:30:21 2006-08-25 dbs-Info: <<< Analysiere Tabelle BC_DDDBRTH >>>
Aug 25, 2006 12:30:25... Info: 0:30:21 2006-08-25 dbs-Info: predefined action is: >>>null<<<
Aug 25, 2006 12:30:25... Info: 0:30:21 2006-08-25 dbs-Info: predefined action is: >>>null<<<
Aug 25, 2006 12:30:25... Info: 0:30:21 2006-08-25 dbs-Info: Keine Aktion fuer die Tabelle notwendig
Aug 25, 2006 12:30:25... Info: 0:30:21 2006-08-25 dbs-Info: Keine Aktion fuer die Tabelle notwendig
Aug 25, 2006 12:30:25... Info: 0:30:21 2006-08-25 dbs-Info: <<< Analysiere Tabelle BC_DDDBRTX >>>
Aug 25, 2006 12:30:25... Info: 0:30:21 2006-08-25 dbs-Info: <<< Analysiere Tabelle BC_DDDBRTX >>>
Aug 25, 2006 12:30:25... Info: 0:30:21 2006-08-25 dbs-Info: predefined action is: >>>null<<<
Aug 25, 2006 12:30:25... Info: 0:30:21 2006-08-25 dbs-Info: predefined action is: >>>null<<<
Aug 25, 2006 12:30:25... Info: 0:30:21 2006-08-25 dbs-Info: Keine Aktion fuer die Tabelle notwendig
Aug 25, 2006 12:30:25... Info: 0:30:21 2006-08-25 dbs-Info: Keine Aktion fuer die Tabelle notwendig
Aug 25, 2006 12:30:25... Info: 0:30:21 2006-08-25 dbs-Info: >>> Analysiere Tabellen aus dem Archiv auf Datenbank MSSQL
Aug 25, 2006 12:30:25... Info: 0:30:21 2006-08-25 dbs-Info: >>> Analysiere Tabellen aus dem Archiv auf Datenbank MSSQL
Aug 25, 2006 12:30:25... Info: 0:30:21 2006-08-25 dbs-Info: Naechstes Archive-Objekt : BC_SLD_ASSINST.gdbtable
Aug 25, 2006 12:30:25... Info: 0:30:21 2006-08-25 dbs-Info: Naechstes Archive-Objekt : BC_SLD_ASSINST.gdbtable
Aug 25, 2006 12:30:25... Info: 0:30:21 2006-08-25 dbs-Info: <<< Analysiere Tabelle BC_SLD_ASSINST >>>
Aug 25, 2006 12:30:25... Info: 0:30:21 2006-08-25 dbs-Info: <<< Analysiere Tabelle BC_SLD_ASSINST >>>
Aug 25, 2006 12:30:25... Info: 0:30:21 2006-08-25 dbs-Info: predefined action is: >>>null<<<
Aug 25, 2006 12:30:25... Info: 0:30:21 2006-08-25 dbs-Info: predefined action is: >>>null<<<
Aug 25, 2006 12:30:25... Info: 0:30:22 2006-08-25 dbs-Info: Keine Aktion fuer die Tabelle notwendig
Aug 25, 2006 12:30:25... Info: 0:30:22 2006-08-25 dbs-Info: Keine Aktion fuer die Tabelle notwendig
Aug 25, 2006 12:30:25... Info: 0:30:22 2006-08-25 dbs-Info: Laufzeit-xml von BC_SLD_ASSINST erfolgreich geschrieben
Aug 25, 2006 12:30:25... Info: 0:30:22 2006-08-25 dbs-Info: Laufzeit-xml von BC_SLD_ASSINST erfolgreich geschrieben
Aug 25, 2006 12:30:25... Info: 0:30:22 2006-08-25 dbs-Info: Laufzeit-xml von BC_SLD_ASSINST erfolgreich geschrieben
Aug 25, 2006 12:30:25... Info: 0:30:22 2006-08-25 dbs-Info: Laufzeit-xml von BC_SLD_ASSINST erfolgreich geschrieben
Aug 25, 2006 12:30:25... Info: 0:30:22 2006-08-25 dbs-Info: Naechstes Archive-Objekt : BC_SLD_ASSOC.gdbtable
Aug 25, 2006 12:30:25... Info: 0:30:22 2006-08-25 dbs-Info: Naechstes Archive-Objekt : BC_SLD_ASSOC.gdbtable
Aug 25, 2006 12:30:25... Info: 0:30:22 2006-08-25 dbs-Info: <<< Analysiere Tabelle BC_SLD_ASSOC >>>
Aug 25, 2006 12:30:25... Info: 0:30:22 2006-08-25 dbs-Info: <<< Analysiere Tabelle BC_SLD_ASSOC >>>
Aug 25, 2006 12:30:25... Info: 0:30:22 2006-08-25 dbs-Info: predefined action is: >>>null<<<
Aug 25, 2006 12:30:25... Info: 0:30:22 2006-08-25 dbs-Info: predefined action is: >>>null<<<
Aug 25, 2006 12:30:25... Info: 0:30:22 2006-08-25 dbs-Info: Keine Aktion fuer die Tabelle notwendig
Aug 25, 2006 12:30:25... Info: 0:30:22 2006-08-25 dbs-Info: Keine Aktion fuer die Tabelle notwendig
Aug 25, 2006 12:30:25... Info: 0:30:22 2006-08-25 dbs-Info: Laufzeit-xml von BC_SLD_ASSOC erfolgreich geschrieben
Aug 25, 2006 12:30:25... Info: 0:30:22 2006-08-25 dbs-Info: Laufzeit-xml von BC_SLD_ASSOC erfolgreich geschrieben
Aug 25, 2006 12:30:25... Info: 0:30:22 2006-08-25 dbs-Info: Laufzeit-xml von BC_SLD_ASSOC erfolgreich geschrieben
Aug 25, 2006 12:30:25... Info: 0:30:22 2006-08-25 dbs-Info: Laufzeit-xml von BC_SLD_ASSOC erfolgreich geschrieben
Aug 25, 2006 12:30:25... Info: 0:30:22 2006-08-25 dbs-Info: Naechstes Archive-Objekt : BC_SLD_CHANGELOG.gdbtable
Aug 25, 2006 12:30:25... Info: 0:30:22 2006-08-25 dbs-Info: Naechstes Archive-Objekt : BC_SLD_CHANGELOG.gdbtable
Aug 25, 2006 12:30:25... Info: 0:30:22 2006-08-25 dbs-Info: <<< Analysiere Tabelle BC_SLD_CHANGELOG >>>
Aug 25, 2006 12:30:25... Info: 0:30:22 2006-08-25 dbs-Info: <<< Analysiere Tabelle BC_SLD_CHANGELOG >>>
Aug 25, 2006 12:30:25... Info: 0:30:22 2006-08-25 dbs-Info: predefined action is: >>>null<<<
Aug 25, 2006 12:30:25... Info: 0:30:22 2006-08-25 dbs-Info: predefined action is: >>>null<<<
Aug 25, 2006 12:30:25... Info: 0:30:22 2006-08-25 dbs-Info: Keine Aktion fuer die Tabelle notwendig
Aug 25, 2006 12:30:25... Info: 0:30:22 2006-08-25 dbs-Info: Keine Aktion fuer die Tabelle notwendig
Aug 25, 2006 12:30:25... Info: 0:30:22 2006-08-25 dbs-Info: Laufzeit-xml von BC_SLD_CHANGELOG erfolgreich geschrieben
Aug 25, 2006 12:30:25... Info: 0:30:22 2006-08-25 dbs-Info: Laufzeit-xml von BC_SLD_CHANGELOG erfolgreich geschrieben
Aug 25, 2006 12:30:25... Info: 0:30:22 2006-08-25 dbs-Info: Laufzeit-xml von BC_SLD_CHANGELOG erfolgreich geschrieben
Aug 25, 2006 12:30:25... Info: 0:30:22 2006-08-25 dbs-Info: Laufzeit-xml von BC_SLD_CHANGELOG erfolgreich geschrieben
Aug 25, 2006 12:30:25... Info: 0:30:22 2006-08-25 dbs-Info: Naechstes Archive-Objekt : BC_SLD_CLASS.gdbtable
Aug 25, 2006 12:30:25... Info: 0:30:22 2006-08-25 dbs-Info: Naechstes Archive-Objekt : BC_SLD_CLASS.gdbtable
Aug 25, 2006 12:30:25... Info: 0:30:22 2006-08-25 dbs-Info: <<< Analysiere Tabelle BC_SLD_CLASS >>>
Aug 25, 2006 12:30:25... Info: 0:30:22 2006-08-25 dbs-Info: <<< Analysiere Tabelle BC_SLD_CLASS >>>
Aug 25, 2006 12:30:25... Info: 0:30:22 2006-08-25 dbs-Info: predefined action is: >>>null<<<
Aug 25, 2006 12:30:25... Info: 0:30:22 2006-08-25 dbs-Info: predefined action is: >>>null<<<
Aug 25, 2006 12:30:25... Info: 0:30:22 2006-08-25 dbs-Info: Keine Aktion fuer die Tabelle notwendig
Aug 25, 2006 12:30:25... Info: 0:30:22 2006-08-25 dbs-Info: Keine Aktion fuer die Tabelle notwendig
Aug 25, 2006 12:30:25... Info: 0:30:22 2006-08-25 dbs-Info: Laufzeit-xml von BC_SLD_CLASS erfolgreich geschrieben
Aug 25, 2006 12:30:25... Info: 0:30:22 2006-08-25 dbs-Info: Laufzeit-xml von BC_SLD_CLASS erfolgreich geschrieben
Aug 25, 2006 12:30:25... Info: 0:30:23 2006-08-25 dbs-Info: Laufzeit-xml von BC_SLD_CLASS erfolgreich geschrieben
Aug 25, 2006 12:30:25... Info: 0:30:23 2006-08-25 dbs-Info: Laufzeit-xml von BC_SLD_CLASS erfolgreich geschrieben
Aug 25, 2006 12:30:25... Info: 0:30:23 2006-08-25 dbs-Info: Naechstes Archive-Objekt : BC_SLD_DELTAEXPORT.gdbtable
Aug 25, 2006 12:30:25... Info: 0:30:23 2006-08-25 dbs-Info: Naechstes Archive-Objekt : BC_SLD_DELTAEXPORT.gdbtable
Aug 25, 2006 12:30:25... Info: 0:30:23 2006-08-25 dbs-Info: <<< Analysiere Tabelle BC_SLD_DELTAEXPORT >>>
Aug 25, 2006 12:30:25... Info: 0:30:23 2006-08-25 dbs-Info: <<< Analysiere Tabelle BC_SLD_DELTAEXPORT >>>
Aug 25, 2006 12:30:25... Info: 0:30:23 2006-08-25 dbs-Info: predefined action is: >>>null<<<
Aug 25, 2006 12:30:25... Info: 0:30:23 2006-08-25 dbs-Info: predefined action is: >>>null<<<
Aug 25, 2006 12:30:25... Info: 0:30:23 2006-08-25 dbs-Info: Keine Aktion fuer die Tabelle notwendig
Aug 25, 2006 12:30:25... Info: 0:30:23 2006-08-25 dbs-Info: Keine Aktion fuer die Tabelle notwendig
Aug 25, 2006 12:30:25... Info: 0:30:23 2006-08-25 dbs-Info: Laufzeit-xml von BC_SLD_DELTAEXPORT erfolgreich geschrieben
Aug 25, 2006 12:30:25... Info: 0:30:23 2006-08-25 dbs-Info: Laufzeit-xml von BC_SLD_DELTAEXPORT erfolgreich geschrieben
Aug 25, 2006 12:30:25... Info: 0:30:23 2006-08-25 dbs-Info: Laufzeit-xml von BC_SLD_DELTAEXPORT erfolgreich geschrieben
Aug 25, 2006 12:30:25... Info: 0:30:23 2006-08-25 dbs-Info: Laufzeit-xml von BC_SLD_DELTAEXPORT erfolgreich geschrieben
Aug 25, 2006 12:30:25... Info: 0:30:23 2006-08-25 dbs-Info: Naechstes Archive-Objekt : BC_SLD_INST.gdbtable
Aug 25, 2006 12:30:25... Info: 0:30:23 2006-08-25 dbs-Info: Naechstes Archive-Objekt : BC_SLD_INST.gdbtable
Aug 25, 2006 12:30:25... Info: 0:30:23 2006-08-25 dbs-Info: <<< Analysiere Tabelle BC_SLD_INST >>>
Aug 25, 2006 12:30:25... Info: 0:30:23 2006-08-25 dbs-Info: <<< Analysiere Tabelle BC_SLD_INST >>>
Aug 25, 2006 12:30:25... Info: 0:30:23 2006-08-25 dbs-Info: predefined action is: >>>null<<<
Aug 25, 2006 12:30:25... Info: 0:30:23 2006-08-25 dbs-Info: predefined action is: >>>null<<<
Aug 25, 2006 12:30:25... Info: 0:30:23 2006-08-25 dbs-Info: Keine Aktion fuer die Tabelle notwendig
Aug 25, 2006 12:30:25... Info: 0:30:23 2006-08-25 dbs-Info: Keine Aktion fuer die Tabelle notwendig
Aug 25, 2006 12:30:25... Info: 0:30:23 2006-08-25 dbs-Info: Laufzeit-xml von BC_SLD_INST erfolgreich geschrieben
Aug 25, 2006 12:30:25... Info: 0:30:23 2006-08-25 dbs-Info: Laufzeit-xml von BC_SLD_INST erfolgreich geschrieben
Aug 25, 2006 12:30:25... Info: 0:30:23 2006-08-25 dbs-Info: Laufzeit-xml von BC_SLD_INST erfolgreich geschrieben
Aug 25, 2006 12:30:25... Info: 0:30:23 2006-08-25 dbs-Info: Laufzeit-xml von BC_SLD_INST erfolgreich geschrieben
Aug 25, 2006 12:30:25... Info: 0:30:23 2006-08-25 dbs-Info: Naechstes Archive-Objekt : BC_SLD_INSTANCES.gdbtable
Aug 25, 2006 12:30:25... Info: 0:30:23 2006-08-25 dbs-Info: Naechstes Archive-Objekt : BC_SLD_INSTANCES.gdbtable
Aug 25, 2006 12:30:25... Info: 0:30:23 2006-08-25 dbs-Info: <<< Analysiere Tabelle BC_SLD_INSTANCES >>>
Aug 25, 2006 12:30:25... Info: 0:30:23 2006-08-25 dbs-Info: <<< Analysiere Tabelle BC_SLD_INSTANCES >>>
Aug 25, 2006 12:30:25... Info: 0:30:23 2006-08-25 dbs-Info: predefined action is: >>>null<<<
Aug 25, 2006 12:30:25... Info: 0:30:23 2006-08-25 dbs-Info: predefined action is: >>>null<<<
Aug 25, 2006 12:30:25... Info: 0:30:23 2006-08-25 dbs-Info: Keine Aktion fuer die Tabelle notwendig
Aug 25, 2006 12:30:25... Info: 0:30:23 2006-08-25 dbs-Info: Keine Aktion fuer die Tabelle notwendig
Aug 25, 2006 12:30:25... Info: 0:30:23 2006-08-25 dbs-Info: Laufzeit-xml von BC_SLD_INSTANCES erfolgreich geschrieben
Aug 25, 2006 12:30:25... Info: 0:30:23 2006-08-25 dbs-Info: Laufzeit-xml von BC_SLD_INSTANCES erfolgreich geschrieben
Aug 25, 2006 12:30:25... Info: 0:30:23 2006-08-25 dbs-Info: Laufzeit-xml von BC_SLD_INSTANCES erfolgreich geschrieben
Aug 25, 2006 12:30:25... Info: 0:30:23 2006-08-25 dbs-Info: Laufzeit-xml von BC_SLD_INSTANCES erfolgreich geschrieben
Aug 25, 2006 12:30:25... Info: 0:30:23 2006-08-25 dbs-Info: Naechstes Archive-Objekt : BC_SLD_LONGVALUES.gdbtable
Aug 25, 2006 12:30:25... Info: 0:30:23 2006-08-25 dbs-Info: Naechstes Archive-Objekt : BC_SLD_LONGVALUES.gdbtable
Aug 25, 2006 12:30:25... Info: 0:30:23 2006-08-25 dbs-Info: <<< Analysiere Tabelle BC_SLD_LONGVALUES >>>
Aug 25, 2006 12:30:25... Info: 0:30:23 2006-08-25 dbs-Info: <<< Analysiere Tabelle BC_SLD_LONGVALUES >>>
Aug 25, 2006 12:30:25... Info: 0:30:23 2006-08-25 dbs-Info: predefined action is: >>>null<<<
Aug 25, 2006 12:30:25... Info: 0:30:23 2006-08-25 dbs-Info: predefined action is: >>>null<<<
Aug 25, 2006 12:30:25... Info: 0:30:23 2006-08-25 dbs-Info: Keine Aktion fuer die Tabelle notwendig
Aug 25, 2006 12:30:25... Info: 0:30:23 2006-08-25 dbs-Info: Keine Aktion fuer die Tabelle notwendig
Aug 25, 2006 12:30:25... Info: 0:30:23 2006-08-25 dbs-Info: Laufzeit-xml von BC_SLD_LONGVALUES erfolgreich geschrieben
Aug 25, 2006 12:30:25... Info: 0:30:23 2006-08-25 dbs-Info: Laufzeit-xml von BC_SLD_LONGVALUES erfolgreich geschrieben
Aug 25, 2006 12:30:25... Info: 0:30:23 2006-08-25 dbs-Info: Laufzeit-xml von BC_SLD_LONGVALUES erfolgreich geschrieben
Aug 25, 2006 12:30:25... Info: 0:30:23 2006-08-25 dbs-Info: Laufzeit-xml von BC_SLD_LONGVALUES erfolgreich geschrieben
Aug 25, 2006 12:30:25... Info: 0:30:23 2006-08-25 dbs-Info: Naechstes Archive-Objekt : BC_SLD_NAMESP.gdbtable
Aug 25, 2006 12:30:25... Info: 0:30:23 2006-08-25 dbs-Info: Naechstes Archive-Objekt : BC_SLD_NAMESP.gdbtable
Aug 25, 2006 12:30:25... Info: 0:30:23 2006-08-25 dbs-Info: <<< Analysiere Tabelle BC_SLD_NAMESP >>>
Aug 25, 2006 12:30:25... Info: 0:30:23 2006-08-25 dbs-Info: <<< Analysiere Tabelle BC_SLD_NAMESP >>>
Aug 25, 2006 12:30:25... Info: 0:30:23 2006-08-25 dbs-Info: predefined action is: >>>null<<<
Aug 25, 2006 12:30:25... Info: 0:30:23 2006-08-25 dbs-Info: predefined action is: >>>null<<<
Aug 25, 2006 12:30:25... Info: 0:30:23 2006-08-25 dbs-Info: Keine Aktion fuer die Tabelle notwendig
Aug 25, 2006 12:30:25... Info: 0:30:23 2006-08-25 dbs-Info: Keine Aktion fuer die Tabelle notwendig
Aug 25, 2006 12:30:25... Info: 0:30:23 2006-08-25 dbs-Info: Laufzeit-xml von BC_SLD_NAMESP erfolgreich geschrieben
Aug 25, 2006 12:30:25... Info: 0:30:23 2006-08-25 dbs-Info: Laufzeit-xml von BC_SLD_NAMESP erfolgreich geschrieben
Aug 25, 2006 12:30:25... Info: 0:30:23 2006-08-25 dbs-Info: Laufzeit-xml von BC_SLD_NAMESP erfolgreich geschrieben
Aug 25, 2006 12:30:25... Info: 0:30:23 2006-08-25 dbs-Info: Laufzeit-xml von BC_SLD_NAMESP erfolgreich geschrieben
Aug 25, 2006 12:30:25... Info: 0:30:23 2006-08-25 dbs-Info: Naechstes Archive-Objekt : BC_SLD_NAMESPACES.gdbtable
Aug 25, 2006 12:30:25... Info: 0:30:23 2006-08-25 dbs-Info: Naechstes Archive-Objekt : BC_SLD_NAMESPACES.gdbtable
Aug 25, 2006 12:30:25... Info: 0:30:23 2006-08-25 dbs-Info: <<< Analysiere Tabelle BC_SLD_NAMESPACES >>>
Aug 25, 2006 12:30:25... Info: 0:30:23 2006-08-25 dbs-Info: <<< Analysiere Tabelle BC_SLD_NAMESPACES >>>
Aug 25, 2006 12:30:25... Info: 0:30:23 2006-08-25 dbs-Info: predefined action is: >>>null<<<
Aug 25, 2006 12:30:25... Info: 0:30:23 2006-08-25 dbs-Info: predefined action is: >>>null<<<
Aug 25, 2006 12:30:25... Info: 0:30:24 2006-08-25 dbs-Info: Keine Aktion fuer die Tabelle notwendig
Aug 25, 2006 12:30:25... Info: 0:30:24 2006-08-25 dbs-Info: Keine Aktion fuer die Tabelle notwendig
Aug 25, 2006 12:30:25... Info: 0:30:24 2006-08-25 dbs-Info: Laufzeit-xml von BC_SLD_NAMESPACES erfolgreich geschrieben
Aug 25, 2006 12:30:25... Info: 0:30:24 2006-08-25 dbs-Info: Laufzeit-xml von BC_SLD_NAMESPACES erfolgreich geschrieben
Aug 25, 2006 12:30:25... Info: 0:30:24 2006-08-25 dbs-Info: Laufzeit-xml von BC_SLD_NAMESPACES erfolgreich geschrieben
Aug 25, 2006 12:30:25... Info: 0:30:24 2006-08-25 dbs-Info: Laufzeit-xml von BC_SLD_NAMESPACES erfolgreich geschrieben
Aug 25, 2006 12:30:25... Info: 0:30:24 2006-08-25 dbs-Info: Naechstes Archive-Objekt : BC_SLD_PROPARRAYS.gdbtable
Aug 25, 2006 12:30:25... Info: 0:30:24 2006-08-25 dbs-Info: Naechstes Archive-Objekt : BC_SLD_PROPARRAYS.gdbtable
Aug 25, 2006 12:30:25... Info: 0:30:24 2006-08-25 dbs-Info: <<< Analysiere Tabelle BC_SLD_PROPARRAYS >>>
Aug 25, 2006 12:30:25... Info: 0:30:24 2006-08-25 dbs-Info: <<< Analysiere Tabelle BC_SLD_PROPARRAYS >>>
Aug 25, 2006 12:30:25... Info: 0:30:24 2006-08-25 dbs-Info: predefined action is: >>>null<<<
Aug 25, 2006 12:30:25... Info: 0:30:24 2006-08-25 dbs-Info: predefined action is: >>>null<<<
Aug 25, 2006 12:30:25... Info: 0:30:24 2006-08-25 dbs-Info: Keine Aktion fuer die Tabelle notwendig
Aug 25, 2006 12:30:25... Info: 0:30:24 2006-08-25 dbs-Info: Keine Aktion fuer die Tabelle notwendig
Aug 25, 2006 12:30:25... Info: 0:30:24 2006-08-25 dbs-Info: Laufzeit-xml von BC_SLD_PROPARRAYS erfolgreich geschrieben
Aug 25, 2006 12:30:25... Info: 0:30:24 2006-08-25 dbs-Info: Laufzeit-xml von BC_SLD_PROPARRAYS erfolgreich geschrieben
Aug 25, 2006 12:30:25... Info: 0:30:24 2006-08-25 dbs-Info: Laufzeit-xml von BC_SLD_PROPARRAYS erfolgreich geschrieben
Aug 25, 2006 12:30:25... Info: 0:30:24 2006-08-25 dbs-Info: Laufzeit-xml von BC_SLD_PROPARRAYS erfolgreich geschrieben
Aug 25, 2006 12:30:25... Info: 0:30:24 2006-08-25 dbs-Info: Naechstes Archive-Objekt : BC_SLD_PROPERTIES.gdbtable
Aug 25, 2006 12:30:25... Info: 0:30:24 2006-08-25 dbs-Info: Naechstes Archive-Objekt : BC_SLD_PROPERTIES.gdbtable
Aug 25, 2006 12:30:25... Info: 0:30:24 2006-08-25 dbs-Info: <<< Analysiere Tabelle BC_SLD_PROPERTIES >>>
Aug 25, 2006 12:30:25... Info: 0:30:24 2006-08-25 dbs-Info: <<< Analysiere Tabelle BC_SLD_PROPERTIES >>>
Aug 25, 2006 12:30:25... Info: 0:30:24 2006-08-25 dbs-Info: predefined action is: >>>null<<<
Aug 25, 2006 12:30:25... Info: 0:30:24 2006-08-25 dbs-Info: predefined action is: >>>null<<<
Aug 25, 2006 12:30:25... Info: 0:30:24 2006-08-25 dbs-Info: Keine Aktion fuer die Tabelle notwendig
Aug 25, 2006 12:30:25... Info: 0:30:24 2006-08-25 dbs-Info: Keine Aktion fuer die Tabelle notwendig
Aug 25, 2006 12:30:25... Info: 0:30:24 2006-08-25 dbs-Info: Laufzeit-xml von BC_SLD_PROPERTIES erfolgreich geschrieben
Aug 25, 2006 12:30:25... Info: 0:30:24 2006-08-25 dbs-Info: Laufzeit-xml von BC_SLD_PROPERTIES erfolgreich geschrieben
Aug 25, 2006 12:30:25... Info: 0:30:24 2006-08-25 dbs-Info: Laufzeit-xml von BC_SLD_PROPERTIES erfolgreich geschrieben
Aug 25, 2006 12:30:25... Info: 0:30:24 2006-08-25 dbs-Info: Laufzeit-xml von BC_SLD_PROPERTIES erfolgreich geschrieben
Aug 25, 2006 12:30:25... Info: 0:30:24 2006-08-25 dbs-Info: Naechstes Archive-Objekt : BC_SLD_PROPERTYREF.gdbtable
Aug 25, 2006 12:30:25... Info: 0:30:24 2006-08-25 dbs-Info: Naechstes Archive-Objekt : BC_SLD_PROPERTYREF.gdbtable
Aug 25, 2006 12:30:25... Info: 0:30:24 2006-08-25 dbs-Info: <<< Analysiere Tabelle BC_SLD_PROPERTYREF >>>
Aug 25, 2006 12:30:25... Info: 0:30:24 2006-08-25 dbs-Info: <<< Analysiere Tabelle BC_SLD_PROPERTYREF >>>
Aug 25, 2006 12:30:25... Info: 0:30:24 2006-08-25 dbs-Info: predefined action is: >>>null<<<
Aug 25, 2006 12:30:25... Info: 0:30:24 2006-08-25 dbs-Info: predefined action is: >>>null<<<
Aug 25, 2006 12:30:25... Info: 0:30:24 2006-08-25 dbs-Info: Keine Aktion fuer die Tabelle notwendig
Aug 25, 2006 12:30:25... Info: 0:30:24 2006-08-25 dbs-Info: Keine Aktion fuer die Tabelle notwendig
Aug 25, 2006 12:30:25... Info: 0:30:24 2006-08-25 dbs-Info: Laufzeit-xml von BC_SLD_PROPERTYREF erfolgreich geschrieben
Aug 25, 2006 12:30:25... Info: 0:30:24 2006-08-25 dbs-Info: Laufzeit-xml von BC_SLD_PROPERTYREF erfolgreich geschrieben
Aug 25, 2006 12:30:25... Info: 0:30:24 2006-08-25 dbs-Info: Laufzeit-xml von BC_SLD_PROPERTYREF erfolgreich geschrieben
Aug 25, 2006 12:30:25... Info: 0:30:24 2006-08-25 dbs-Info: Laufzeit-xml von BC_SLD_PROPERTYREF erfolgreich geschrieben
Aug 25, 2006 12:30:25... Info: 0:30:24 2006-08-25 dbs-Info: Naechstes Archive-Objekt : BC_SLD_QUAL.gdbtable
Aug 25, 2006 12:30:25... Info: 0:30:24 2006-08-25 dbs-Info: Naechstes Archive-Objekt : BC_SLD_QUAL.gdbtable
Aug 25, 2006 12:30:25... Info: 0:30:24 2006-08-25 dbs-Info: <<< Analysiere Tabelle BC_SLD_QUAL >>>
Aug 25, 2006 12:30:25... Info: 0:30:24 2006-08-25 dbs-Info: <<< Analysiere Tabelle BC_SLD_QUAL >>>
Aug 25, 2006 12:30:25... Info: 0:30:24 2006-08-25 dbs-Info: predefined action is: >>>null<<<
Aug 25, 2006 12:30:25... Info: 0:30:24 2006-08-25 dbs-Info: predefined action is: >>>null<<<
Aug 25, 2006 12:30:25... Info: 0:30:24 2006-08-25 dbs-Info: Keine Aktion fuer die Tabelle notwendig
Aug 25, 2006 12:30:25... Info: 0:30:24 2006-08-25 dbs-Info: Keine Aktion fuer die Tabelle notwendig
Aug 25, 2006 12:30:25... Info: 0:30:24 2006-08-25 dbs-Info: Laufzeit-xml von BC_SLD_QUAL erfolgreich geschrieben
Aug 25, 2006 12:30:25... Info: 0:30:24 2006-08-25 dbs-Info: Laufzeit-xml von BC_SLD_QUAL erfolgreich geschrieben
Aug 25, 2006 12:30:25... Info: 0:30:24 2006-08-25 dbs-Info: Laufzeit-xml von BC_SLD_QUAL erfolgreich geschrieben
Aug 25, 2006 12:30:25... Info: 0:30:24 2006-08-25 dbs-Info: Laufzeit-xml von BC_SLD_QUAL erfolgreich geschrieben
Aug 25, 2006 12:30:25... Info: 0:30:24 2006-08-25 dbs-Info: Naechstes Archive-Objekt : BC_SLD_QUALIFIERS.gdbtable
Aug 25, 2006 12:30:25... Info: 0:30:24 2006-08-25 dbs-Info: Naechstes Archive-Objekt : BC_SLD_QUALIFIERS.gdbtable
Aug 25, 2006 12:30:25... Info: 0:30:24 2006-08-25 dbs-Info: <<< Analysiere Tabelle BC_SLD_QUALIFIERS >>>
Aug 25, 2006 12:30:25... Info: 0:30:24 2006-08-25 dbs-Info: <<< Analysiere Tabelle BC_SLD_QUALIFIERS >>>
Aug 25, 2006 12:30:25... Info: 0:30:24 2006-08-25 dbs-Info: predefined action is: >>>null<<<
Aug 25, 2006 12:30:25... Info: 0:30:24 2006-08-25 dbs-Info: predefined action is: >>>null<<<
Aug 25, 2006 12:30:25... Info: 0:30:25 2006-08-25 dbs-Info: Keine Aktion fuer die Tabelle notwendig
Aug 25, 2006 12:30:25... Info: 0:30:25 2006-08-25 dbs-Info: Keine Aktion fuer die Tabelle notwendig
Aug 25, 2006 12:30:25... Info: 0:30:25 2006-08-25 dbs-Info: Laufzeit-xml von BC_SLD_QUALIFIERS erfolgreich geschrieben
Aug 25, 2006 12:30:25... Info: 0:30:25 2006-08-25 dbs-Info: Laufzeit-xml von BC_SLD_QUALIFIERS erfolgreich geschrieben
Aug 25, 2006 12:30:25... Info: 0:30:25 2006-08-25 dbs-Info: Laufzeit-xml von BC_SLD_QUALIFIERS erfolgreich geschrieben
Aug 25, 2006 12:30:25... Info: 0:30:25 2006-08-25 dbs-Info: Laufzeit-xml von BC_SLD_QUALIFIERS erfolgreich geschrieben
Aug 25, 2006 12:30:25... Info: 0:30:25 2006-08-25 dbs-Info: Naechstes Archive-Objekt : BC_SLD_ROLE.gdbtable
Aug 25, 2006 12:30:25... Info: 0:30:25 2006-08-25 dbs-Info: Naechstes Archive-Objekt : BC_SLD_ROLE.gdbtable
Aug 25, 2006 12:30:25... Info: 0:30:25 2006-08-25 dbs-Info: <<< Analysiere Tabelle BC_SLD_ROLE >>>
Aug 25, 2006 12:30:25... Info: 0:30:25 2006-08-25 dbs-Info: <<< Analysiere Tabelle BC_SLD_ROLE >>>
Aug 25, 2006 12:30:25... Info: 0:30:25 2006-08-25 dbs-Info: predefined action is: >>>null<<<
Aug 25, 2006 12:30:25... Info: 0:30:25 2006-08-25 dbs-Info: predefined action is: >>>null<<<
Aug 25, 2006 12:30:25... Info: 0:30:25 2006-08-25 dbs-Info: Keine Aktion fuer die Tabelle notwendig
Aug 25, 2006 12:30:25... Info: 0:30:25 2006-08-25 dbs-Info: Keine Aktion fuer die Tabelle notwendig
Aug 25, 2006 12:30:25... Info: 0:30:25 2006-08-25 dbs-Info: Laufzeit-xml von BC_SLD_ROLE erfolgreich geschrieben
Aug 25, 2006 12:30:25... Info: 0:30:25 2006-08-25 dbs-Info: Laufzeit-xml von BC_SLD_ROLE erfolgreich geschrieben
Aug 25, 2006 12:30:25... Info: 0:30:25 2006-08-25 dbs-Info: Laufzeit-xml von BC_SLD_ROLE erfolgreich geschrieben
Aug 25, 2006 12:30:25... Info: 0:30:25 2006-08-25 dbs-Info: Laufzeit-xml von BC_SLD_ROLE erfolgreich geschrieben
Aug 25, 2006 12:30:25... Info: 0:30:25 2006-08-25 dbs-Info: Analyse und Anpassung von Tabellen erfolgreich ausgefuehrt
Aug 25, 2006 12:30:25... Info: 0:30:25 2006-08-25 dbs-Info: Analyse und Anpassung von Tabellen erfolgreich ausgefuehrt
Aug 25, 2006 12:30:25... Info: Finished successfully: development component 'com.sap.lcr.jddschema'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060706111625.0000'/'0', grouped by software component 'SAP_JTECHS'/'sap.com'/'SAP AG'/'1000.6.40.18.0.20060816080857''/'0'
Aug 25, 2006 12:30:25... Info: Starting to save the repository
Aug 25, 2006 12:30:26... Info: Finished saving the repository
Aug 25, 2006 12:30:26... Info: Starting: Update: Selected development component 'com.sap.rprof.jddschema'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060413101559.0000'/'0' updates currently deployed development component 'com.sap.rprof.jddschema'/'sap.com'/'SAP AG'/'6.4013.00.0000.20040609162409.0000'/'0'.
Aug 25, 2006 12:30:27... Info: <!LOGHEADER[START]/>
Aug 25, 2006 12:30:27... Info: <!HELP[Manual modification of the header may cause parsing problem!]/>
Aug 25, 2006 12:30:27... Info: <!LOGGINGVERSION[1.5.3.7186 - 630]/>
Aug 25, 2006 12:30:27... Info: <!NAME[C:\usr\sap\J2E\JC00\SDM\program\log\jddilog20060825003026.log]/>
Aug 25, 2006 12:30:27... Info: <!PATTERN[jddilog20060825003026.log]/>
Aug 25, 2006 12:30:27... Info: <!FORMATTER[com.sap.dictionary.database.dbs.DbTraceFormatter(%s %m %-30l %24d)]/>
Aug 25, 2006 12:30:27... Info: <!ENCODING[Cp1252]/>
Aug 25, 2006 12:30:27... Info: <!LOGHEADER[END]/>
Aug 25, 2006 12:30:27... Info: 0:30:26 2006-08-25 dbs-Info: $Id: //tc/DictionaryDatabase/630_VAL_REL/src/_dictionary_database_dbs/java/com/sap/dictionary/database/dbs/DbModificationManager.java#4 $
Aug 25, 2006 12:30:27... Info: 0:30:26 2006-08-25 dbs-Info: <<<<<<<<<<<<<< Tabellen-Deployment >>>>>>>>>>>>>
Aug 25, 2006 12:30:27... Info: 0:30:26 2006-08-25 dbs-Info: <<<<<<<<<<<<<< Tabellen-Deployment >>>>>>>>>>>>>
Aug 25, 2006 12:30:27... Info: 0:30:26 2006-08-25 dbs-Info:
Aug 25, 2006 12:30:27... Info: 0:30:26 2006-08-25 dbs-Info:
Aug 25, 2006 12:30:27... Info: 0:30:26 2006-08-25 dbs-Info: <<< Analysiere Tabelle BC_DDDBRTH >>>
Aug 25, 2006 12:30:27... Info: 0:30:26 2006-08-25 dbs-Info: <<< Analysiere Tabelle BC_DDDBRTH >>>
Aug 25, 2006 12:30:27... Info: 0:30:26 2006-08-25 dbs-Info: predefined action is: >>>null<<<
Aug 25, 2006 12:30:27... Info: 0:30:26 2006-08-25 dbs-Info: predefined action is: >>>null<<<
Aug 25, 2006 12:30:27... Info: 0:30:26 2006-08-25 dbs-Info: Keine Aktion fuer die Tabelle notwendig
Aug 25, 2006 12:30:27... Info: 0:30:26 2006-08-25 dbs-Info: Keine Aktion fuer die Tabelle notwendig
Aug 25, 2006 12:30:27... Info: 0:30:26 2006-08-25 dbs-Info: <<< Analysiere Tabelle BC_DDDBTABLERT >>>
Aug 25, 2006 12:30:27... Info: 0:30:26 2006-08-25 dbs-Info: <<< Analysiere Tabelle BC_DDDBTABLERT >>>
Aug 25, 2006 12:30:27... Info: 0:30:26 2006-08-25 dbs-Info: predefined action is: >>>null<<<
Aug 25, 2006 12:30:27... Info: 0:30:26 2006-08-25 dbs-Info:It looks like you need to make sure server0 is running before trying to deploy the AutoID (AII) components; from your SDM log:
ERROR: Cannot perform action deploy on component library C:\usr\sap\J2E\JC00\SDM\root\origin\sap.com\com.sap.aii.ibtransportclient\SAP AG\0\6.4018.00.0000.20060413102101.0000\aii_ibtransportclient.sda. Reason:
com.sap.engine.services.rmi_p4.P4ConnectionException: <b>Possible problem: no available running server node. Check your running servers.</b>
The SDM can't connect to the P4 service of the instance; make sure it's started and then try deploying the package again.
Rich -
Problem with Apache reverse proxy after applying SP13 NW
Hello,
we have a NW04 EP Portal and a Apache reverse proxy in the DMZ. After applying SP 13 for the portal we get the following error from the reverse proxy:
Proxy Error
The proxy server received an invalid response from an upstream server.
The proxy server could not handle the request GET /irj/.
Reason: Error reading from remote server
Apache/2.0.52 (Win32) mod_ssl/2.0.52 OpenSSL/0.9.7e Server at servername.company.de Port 443
Is is it possible, that there is a problem with sp13?
Best regards
Daniel HolsteinHi Daniel,
ok I`ll try to find a solution in parallel and keep you up to date.
In the following my settings in case I missed something:
<VirtualHost test.firma.de:443>
SSLEngine on
SSLProxyEngine on
SSLCertificateFile /apache/keys/pac_ssl_qep_dmz_server.crt
SSLCertificateKeyFile /apache/keys/pac_ssl_qep_dmz_server.key
ServerName test.firma.de:443
ServerAdmin [email protected]
LogLevel debug
ErrorLog logs/ssl_443_error
CustomLog logs/ssl_443_access_log common
ProxyVia Off
ProxyPreserveHost On
ReWriteEngine on
ReWriteLogLevel 0
ReWriteLog logs//ssl_443_rewrite_http.log
ProxyPass / https://backend.firma.de:50001/
ProxyPassReverse / https://backend.firma.de:50001/
</VirtualHost>
Regards, Jens -
Problem with local editing after update to SP13
Hallo,
we have updated our Enterprise Portla 7.00 to SP13. Now many user have Problem with local editing. The error message is "The download of the document fail".
I know that every PC needs the "Docservice" Active X component installed. The "Docservice" is also installed.
At my PC theres only this problem with "html" documents.
What could be the problem. ?
Please help.
Many thanks
RonaldWe found that there is a problem with the Docservice Active X Component.
If we work in a deeper folder there is a problem with the length of the url. I changed the TEMP Setting
"Setting a different TEMP directory:
In cases that it is problematic to use the standard %TEMP% directory,
setting the environment variable SAPKM_USER_TEMP pinpointing to a
corresponding directory path (e.g.
X:\SHARES\USERS\xxx\CheckedOutDocuments) will be also supported. If the
access to that directory fails the standard %TEMP% directory will be
used as fallback."
I used "C:\TEMP" and now it works....... but this cant be the solution....
thans Ronald -
CUP Issue in workflow - Approver not found after SP13
Dear All,
We are facing an issue after upgrade to SP13 in CUP. The request is not getting saved and throwing an error - Approver not Found.
We uploaded the xml files also of SP13 after upgrade has completed.
We have not changed the workflow after upgrade and verified all the attributes of Initiator, CAD and approver is already available in CAD - but still we are receiving the error "Approver Not Found"
The same workflow is working succesfully in Production system which is under SP9.
Is this an issue with SP13. If any body has encountered please let us know how to resolve.
Thanks and Best Regards,
Srihari.KDear Chinmaya,
Below is the error log
Log :
2011-05-09 08:13:17,375 [SAPEngine_Application_Thread[impl:3]_25] ERROR NoApproverFoundException in Save request
com.virsa.ae.workflow.NoApproverFoundException: No approvers found for req no : 135, for reqPathId, 209, for path, CHNG_ANZ_Z6 and approver determinator : ANZ_LAC
Also, we tried with simple workflow as well with just 2 attribute logic. Still we received the same error
Thanks and Best Regards,
Srihari.K -
Solution Manager 4.0 BI Reporting Content for SP13
Hi,
I'm looking for a listing of BI Reporting Content for Solution Manager 4.0 SP13. I've heard rumors that standard BI Reporting content exists for the Change Request Management and Service Desk domains, but all I can find are references for system and performance report content for SP12.
See the matrix of content listed in help.sap.com at this url... <a href="http://help.sap.com/saphelp_sm40/helpdata/en/44/1ed74368b66491e10000000a1553f7/content.htm">SP12 SolMan BI Reporting Content from help.sap.com</a>
Any guidance for standard BI reporting content for SolMan Change Request Management or Service Desk domains would be appreciated.
Thanks,
JoshI was on session LCM264 - Reporting and Performance Analysis Using SAP NetWeaver BI at TechED and there was no talking about Change Request Management or Service Desk reporting.... This doesn't mean it's not available but I have never heard about it...
I'm setting up Performance Analysis right now and it is working really fine.
/Mikael -
Mapping using substing is not working after upgrade to PI SP13
Hi all,
In XI SP 14 we had a mapping that used a lot of substing commands to switch around a data time stamp. It basically said, if the node was not blank(its is being passed as blank on occasion instead of null) then run all the substing commands to move the date and time around. Now in PI SP13 it is still trying to run the substing mappings for the records with blank values coming in, even though the IF statment acknowledges that it should be suppressed. This is causing a java exception for the command since the field is not long enough for the substing. Has anyone else run into this problem?
Regards,
ChrisHI,
Before the If condition just try to add the API SplitByVlaue or maybe concat the field with balnk spaces.
If you could give the exact details of the applied condition then it will be easy to give you the proper way that could achieve with mapping.
Its surprising that if the same mapping is working out for old SP and now its creating problem for the PI SP13.
Thanks
Swarup -
Error in Sender SOAP Adapter on XI 3.0 SP13
Hi All.
I have an application that sends a SOAP message to XI SOAP Adapter, to reach a synchronous interface. I've generated the .wsdl file from the Integration Directory, within the URL:
http://sapbox:59800/XISOAPAdapter/MessageServlet?channel=:BS_PORTAL:CC_S_SOAP_CREDITO
When I try to reach this URL, I get the successful response:
<i>Message Servlet is in Status OK</i>
I've also created the sender SOAP communication channel, fullfilling the default namespace and default interface correctly.
However, when I use wsnavigator client provided by SAP to prove the scenario, the SOAP message doesn't achieve XI, as the XISOAPAdapter EJB throws some exceptions:
<i>HTTP/1.1 500 Internal Server Error
Connection: close
Server: SAP J2EE Engine/6.40
Content-Type: text/xml; charset=utf-8
Date: Sat, 17 Sep 2005 02:59:12 GMT
<?xml version='1.0'?>
<!-- see the documentation -->
<SOAP:Envelope xmlns:SOAP='http://schemas.xmlsoap.org/soap/envelope/'>
<SOAP:Body>
<SOAP:Fault>
<faultcode>SOAP:Server</faultcode>
<faultstring>Server Error</faultstring>
<detail>
<s:SystemError xmlns:s='http://sap.com/xi/WebService/xi2.0'>
<context>XIAdapter</context>
<code>BaseEJBException</code>
<text><![CDATA[
com.sap.aii.af.mp.processor.ModuleProcessorException
at com.sap.aii.af.mp.ejb.ModuleProcessorBean.process(ModuleProcessorBean.java:278)
at com.sap.aii.af.mp.processor.ModuleProcessorLocalLocalObjectImpl0.process(ModuleProcessorLocalLocalObjectImpl0.java:103)
at com.sap.aii.af.mp.soap.web.MessageServlet.callModuleProcessor(MessageServlet.java:162)
at com.sap.aii.af.mp.soap.web.MessageServlet.doPost(MessageServlet.java:508)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:390)
at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:264)
at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:347)
at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:325)
at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:887)
at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:241)
at com.sap.engine.services.httpserver.server.Client.handle(Client.java:92)
at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:148)
at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
at java.security.AccessController.doPrivileged(Native Method)
at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:95)
at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:159)
Caused by: com.sap.engine.services.ejb.exceptions.BaseEJBException: Exception in method process.
at com.sap.aii.af.mp.module.ModuleLocalLocalObjectImpl3.process(ModuleLocalLocalObjectImpl3.java:121)
at com.sap.aii.af.mp.ejb.ModuleProcessorBean.process(ModuleProcessorBean.java:227)
... 19 more
Caused by: java.lang.NoSuchMethodError: com.sap.aii.messaging.srt.xmb.XMBWebServiceExtension.setDynamicConfigurationMode(I)V
at com.sap.aii.af.mp.soap.ejb.XISOAPAdapterBean.createXMBWSBubble(XISOAPAdapterBean.java:1129)
at com.sap.aii.af.mp.soap.ejb.XISOAPAdapterBean.setup(XISOAPAdapterBean.java:265)
at com.sap.aii.af.mp.soap.ejb.XISOAPAdapterBean.process(XISOAPAdapterBean.java:562)
at com.sap.aii.af.mp.module.ModuleLocalLocalObjectImpl3.process(ModuleLocalLocalObjectImpl3.java:103)
... 20 more
]]></text>
</s:SystemError>
</detail>
</SOAP:Fault>
</SOAP:Body>
</SOAP:Envelope></i>
I've already done something really similar on SP 9. Can it be a new problem from SP13? Does anyone has any idea?
Thanks in advance.
Deise Lima.Hi Naveen,
I have configured a SOAP sender adapter in XI 3.0 and is using the URL
http://host:port/XISOAPAdapter/MessageServlet?channel=:BS_WEBSERVICE:CC_WEBSERVICE_SOAP to post the messages. When I open the URL in the browser I am getting the error.
Message Servlet is in Status ERROR
Status information:
Servlet com.sap.aii.af.mp.soap.web.MessageServlet (Version $Id: //tc/aii/30_VAL_REL/src/_adapters/_soap/java/com/sap/aii/af/mp/soap/web/MessageServlet.java#5 $) bound to /MessageServlet
Classname ModuleProcessor: null
Lookupname for localModuleProcessorLookupName: localejbs/ModuleProcessorBean
Lookupname for remoteModuleProcessorLookupName: null
ModuleProcessorClass not instantiated
ModuleProcessorLocal not instantiated
ModuleProcessorRemote not instantiated
But when I test the URL http://host:port/XISOAPAdapter/HelperServlet?action=FindChannel&channel=:BS_WEBSERVICE:CC_WEBSERVICE_SOAP to check the communication channel I am getting the right response as below.
<?xml version="1.0" ?>
http://host:port/XISOAPAdapter/HelperServlet?action=FindChannel&channel=:BS_WEBSERVICE:CC_WEBSERVICE_SOAP <s:ChannelInfo xmlns:s="http://sap.com/xi/WebService/xi30">
<channelID>e7ac884596ea3d088cbfd8b434f942f2</channelID>
<name>CC_WEBSERVICE_SOAP</name>
<type xmlns:st="http://sap.com/xi/XI/System">st:SOAP</type>
<direction>INBOUND</direction>
<party />
<service>BS_WEBSERVICE</service>
</s:ChannelInfo
I used the http capture to debug, In the 1st case though I am getting "Message Servlet in status error" I am seeing a 200 OK code in the http capture tool. When the message is posted from .net client proxy or Altova XML Spy we are getting a 500 internal server error.
Am not sure what causes the error -
XI3.0 SP13 doesn't like BuiltInType tag in OAGIS 9.0 QualifiedDataTypes.xsd
I am on XI 3.0 SP13.
I am not able to activate the OAGIS 9.0 QualifiedDataTypes.xsd after I imported it into integration builder. Integration builder is poping up Internal Problem -java.lang.NullPointerException.
The processing log reads:
Activation of the change list canceled Check result for External Definition QualifiedDataTypes | http://xyz.com/xi/OAG/90/: Document check found errors Cause: Unable to recognize the loaded document as valid XSD Error when parsing XSD document com.sap.aii.utilxi.xsd.api.XsdException: Document is not valid xsd since it contains the <BuiltInType> tag
The steps to recreated this problems:
1. download OAGIS 9.0 schemas from http://www.openapplications.org/. It is in a zip file. Unzip it somewhere in your PC.
2. Find <your folder>\9.0\Resources\Components\CoreComponents\QualifiedDataTypes.xsd.
3. Import this QualifiedDataTypes.xsd into Integration Builder as an External Defininition.
4. Try to activate it. You will get the error.
Tips appreciated. I have downloaded the exception log and can post it here if needed.
Eddy
[email protected]I found answer from Yahoo Group oagis-users. I should reward myself some points. lol.
Here's the link. You may need to join the group first in order to see more.
<a href="http://tech.groups.yahoo.com/group/oagis-users/message/1918">http://tech.groups.yahoo.com/group/oagis-users/message/1918</a>
Here's part of the message:
RE: [oagis-users] Re: OAG 8.0 is not valid as far as XmlSpy 2006 is c oncerned.
This message is for OAGIS 9.
I did some investigation and the problem Spy 2006 has turns out to be an issue
with the original (UNCEFACT) QualifiedDataTypes.xsd and UnQualifiedDataTypes.xsd
Schemas which, according to the OAG namespace declarations are based on Version
1.1 and therefore I assume based on "XML Naming and Design Rules Draft 1.1, 14
January 2005".
First off the problem is only in the annotations/documentation and not with the
content model. The NDR uses ccts:BuiltInType within the body of the document,
but the Appendices (Schema Modules) use xsd:BuiltInType and xsd:BuiltinType. I
changed these to be ccst:BuiltInType in the OAG Schemas and Spy 2006 is happy. I
downloaded an eval version to check this out.
Attached are the updated Schemas, unofficial of course. Note that I copied the
Architecture Team.
Regards,
Kurt Kanaskie
IT Application Architecture
Lucent Technologies
work: (908) 582-5883
cell: (484) 695-1106
Original Message-----
From: [email protected] [mailto:[email protected]] On Behalf
Of thom_at_work
Sent: Sunday, October 30, 2005 8:21 PM -
Advantages of SP13 for PI 7.0
Hi,
can any body give me the documenation about Support Pack13 for PI 7.0 ... because i need to give a demo on this SP13 .. what are the advantages of SP13 .. and what are the new features.. these all thing i want to know... so, can any body provide me a brief idea abt that..
i gone through this link but i was unable to find the documenation .. so, plz provide me the helpful information..
https://websmp130.sap-ag.de/sap(bD1lbiZjPTAwMQ==)/bc/bsp/spn/sps/index.do?pvnr=01200615320900001250
any help ... plz...
Thanks
BabuHi Babu,
Apart from the links provided these are also additions for sp13
3.1 SP 13
Some mapping programs require additional data from an application system to map messages to each other. Furthermore, you may want to reuse existing mapping routines from an application system.
It was previously only possible to read values for/while executing message, Java, or XSLT mapping programs from a global value-mapping table. Also, If you wanted to execute calls to an application system during a mapping, you could use the Java Connector (JCo), for example. Calls of this kind are known as lookups, and were previously only visible in the program code of the mapping program. This Support Package Stack contains a new API for the mapping runtime that enables you to execute lookups for message mappings, Java mappings, and XSLT mappings (J2EE Engine).
The lookup API contains methods for generically accessing application systems by using the RFC, JDBC, and SOAP adapters. Also included is a special API for the JDBC adapter, which simplifies the procedure for accessing application systems.
You configure the access procedure by using a communication channel in the Integration Directory.
When configuration is complete and the runtime is active, you can test lookups that are part of a mapping program by using the test environment of an interface mapping.
See also: Mapping Lookups
Reward points if found useful. -
Trapping AF errors using Alert framework in XI 3.0 SP13
Hi
I am trying to setup alert categories and rules to trap AF related errors - like a SOAP receiver adapter failing to call a webservice etc...
I came across earlier threads that mentioned, alerts will not be triggered involving AF in SP13 - in other words, one has to be on SP14 inorder for the alerts involving AF to be triggered - irrespective of all the settings being done to trigger alerts in SP13 ( End-to-End monitoring, SXMSALERT_PROCESS_DATA_GET etc )
Is the above statement true ??
Thanks for your time in advance.here is an extract on how to do
http://help.sap.com/saphelp_nw04/helpdata/en/e5/5d1741b393f26fe10000000a1550b0/content.htm
Configuring CCMS Alerts for the Adapter Engine
If processing of a message on the Adapter Engine fails, the message state is changed to faulty. To notify administrators immediately of such processing failures, they can be propagated as alerts to CCMS. As CCMS is the SAP standard interface to third-party monitoring tools, these failure events may also become visible in non-SAP monitoring tools.
Configuration Steps
To make use of Adapter Engine alerts, you must configure the connection to CCMS as follows:
1. Make sure that the J2EE engine on which the Adapter Engine is running is configured to be monitored by the central CCMS system.
To do so, execute transaction RZ20 on your central monitor server. There, the J2EE engine should be visible in the CCMS monitor under SAP J2EE Monitor Templates ® All Systems. If not, follow the steps described in the Supportability Setup Guide for SAP NetWeaver 04 on SAP Service Marketplace at service.sap.com/nw04operation ® Cross-NW.
2. Check whether the Adapter Engine is configured to report errors to CCMS.
To do so, start the Visual Administrator and select service SAP XI AF Core. The value of property CCMSEnabled must be set to true (in lower case letters). If it is not, change the property value to true and restart the service.
To verify that the setting is effective, select the Visual Administrator Monitoring service. Under Root ® Applications, you should see a node for the Adapter Engine.
cheers,
Naveen -
After patching Portal 7.31 SP9 - SP13, CM BW reports fail
Our links to the BI credit reports (like Early Warning Risk) stopped working after patching the NW Portal 7.31 from SP9 to SP13. No other changes were made, and the reports worked prior to the patching.
The child window for the report opens, but then comes back with error:
com.sap.portal.appintegrator.sap.BWReport::BWReport/AskForReport
And then it asks for a BEx Web Application Query String.
I would put this in the portal/netweaver forum, but this error seems strictly related to the CM delivered content (we are on the most current 1.41 BP). We've validated that that the SSO tickets from portal to back end ERP and BI are working properly. Has anyone had this kind of issue after a patch (while staying on same portal release)? We didn't make any changes/patches to the back end ERP and BI systems either.Yes we have experienced the same thing. We upgraded from 30 to 353 and now we are getting the BW logon prompt. It is very frustrating. I have been searching these message boards for help.
Brien -
Very disapointed, SP13 doesn't runs on SUN Cluster!!
Hello, this is the 3rd time that we tried to install a support package in our productive SAP Enterprise Portal (SP10, SP12, SP13), and fails again.
We restore the SP09 backup, and doesn't work also, and now we haven't portal!
How is possible this? We are very disapointed, SAP support can't solve the problem.
I have a published blog with more comments about this:
http://rafaelco.blogspot.comI have succefully installed SP 9, SP 12 and SP 13 in SUN Solaris 9, with many problems as well but It worked at the end.
If you tell me what kind of problems do you are you facing, maybe I can help.
Regards -
Cannot map control record values from payload w/XSLT after SP13 upgrade
Hi!
Since we upgraded to SP13, the mapping of control record values form the XML payload to the IDOC control record (File->XI->IDOC scenario) no longer works if the mapping is done via XSLT. It works if the XI graphical mapper is used. The XSLT used is the same pre and post upgrade, but worked fine previously.
[ Apply Control Record Values from Payload is checked in the IDOC adapter comm channel. ]
Has anyone else experienced this? Am looking for any inspiration
Cheers
DuncanAre you sure the xslt file is still there?
Maybe some non-compliance was corrected in later SP and your XSLT was using that non-compliance.
If you post the XSLT we could try to point out any possible errors.
Regards,
Henrique. -
SP13 : SOAP Adapter Problem
Hi All,
Recently we upgraded from SP9 to SP13. Every since we upgraded to SP13 we are experiencing weird problem with Outbound SOAP adapter.
We have exposed an outbound interface as a webservice, which is consumed by a .Net application. When the .Net application try's to call the webservice, we get soap exception "Server Error".
To make sure the call is reaching XI, we put in wrong credentials and we got authorization error. So the call is getting to XI.
Has anyone encountered this weird problem? Any thoughts or suggestions will be very much appreciated.
Thanks,
naveenHi,
There is a tool called SOAPScope from www.Mindreef.com
Its a webservices diagnostic tool. Use this to troubleshoot.you can get a evaluation for 4 days i guess.
Regards,
Sridhar -
Order Detail Enhancement on MAM 2.5 SP13
Hi,
I am trying to do some enhancement on the order detail in MAM 2.5 SR2. I have imported the .war file into Eclipse, but there is a problem with order detail in MAM 2.5 SR2 using MI 2.5 SP13 that is solved by applying an Add-On into MAM. I downloaded the Add-On and applied it, which makes the standard MAM work correctly, but when making enhancements I must apply the Add-On again.
This Add-On has two classes files: OrderDetail.class and OrderHelper.class, but the source code isn't available (no .java files).
How can I make enhancements into Order Detail in MAM (I want to add fields with information to be entered on the mobile device and updated into a Z table in the backend) without losing them when applying the Add-On?
Regards,
DanielWhen you download the MAM25.ZIP archive from the SAP Market place, there are two .war files in the subfolders (mam25.war and mam25_eclipse.war). I think you have imported some of these in the eclipse.
But there's also a subfolder named <i>Client_Source</i> with a jar archive in it (<i>MAM25.src.jar</i>). Extract its content and you will receive all of the MAM25 source in .java files.
Cheers,
Todor
Maybe you are looking for
-
ITunes saves everything to the wrong location
In my preferences I have it set so that everything saves to my music library, however, everything gets saved to my photo's library. Multiple times, I have closed iTunes and deleted everything in the iTunes folder in my folder library, but that accomp
-
ICloud's mail page doesn't display .mac & .me mail that Thunderbird captures
Greetings: I recently discovered after weeks of experiments and combing my iCloud trash and junk folders that if your Thunderbird Server settings is set for imap.mail.me.com or imap.mail.mac.com instead of imap.mail.icloud.com that iCloud will let Th
-
hello, i am getting a problem with my Nokia 5800. when i type *#0000# and see the version i have, and i click check for updates, it says that i need to create a server profile. i dont know what to do? i thought all u needed was a wifi connection? whi
-
Why are my iPhone photos not appearing in photo stream?
When I first downloaded iCloud photos taken on my iphone automatically apeared in photo stream on my macbook. This is not happening anymore. I have automatic photo steam enabled in settings and iphoto preferences.
-
I keep getting an error message 4002...it is not downloading my games. What am i suppose to do?