/TMWFLOW/PHCNTRL in Solutionmanager 4.0 SP13 T:SCMA Problem
Hi Groupies,
I have a big problem. I would use the Change Request Management (CRM) in Solution Manager 4.0 SP13.
I did the the "Standard Installation" of the CRM in SPRO.
My Problem was that my Maintanance Cycle could not activated. After this I had no chance to do this an I used the note 93398 I would close the Maintanace Cycle. After the procedure die Cycle was closed. I created a new one. The same Incident but an other Problem. Now it could not change the phase in fact that he didnt found the phases. It gives back: "Exception NO_NEXT_PHASE_VALUE was captured" Change from Phase "" to Phase "" is not possible. The new Maintanance Cycle could not be closed. I have no idea....
Thanks
Nico
I was able to solve the issue "Change from Phase "" to Phase "" is not possible" I was facing myself.
Here it was related to a missing authorization object.
A Maintenance Cycle is a transaction type (SDMN) on itself. So changing the phase, has the result that also the user status of the transaction type will be changed. My role was missing the authobject B_USERSTAT for the needed statuses of transaction type SDMN.
Hope this helps you.
Roel
Similar Messages
-
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 -
NW04 EP6 Sp13 & ECC5.0 - Problem previewing MSS iviews
We have just completed an install of NW06 EP6 SP13 & ECC5.0 at the back-end and are looking to implement ESS and MSS. In trying to preview an MSS iview, I am getting errors with the connection. A pre-requisite may be missing. This is our landscape:
ECC5.0
Abap Stack
EP6 SP13
Java Stack
latest versions of MSS and ESS BPs
The system connectivity, aliase, SAP Logon Tickets have been configured. The test connection is working. The userids in Portal and ECC5.0 are the same. LDAP is being used for initial Portal authentication.
With EP6 SP2, a back-end plug-in was required and we are unable to find one for ECC5.0. What do we need on the back-end for the front-end and the back-end to communicate and allow us the capability of previewing the ESS and MSS iviews?
Any help on this will be greatly appreciated.
Thanks in advance.
Regards, NeetaHi,
Note that I am running EP6 SP13 in NW04 and our backend is ECC5.0. The link I am trying to preview/run is, per Ketuls suggestion :
http://sapptdapp1:50800/webdynpro/dispatcher/sap.com/pcui_gp~xssutils/XssMenu
The error message I get is (rather long....):
While processing the current request, an exception occured which could not be handled by the application or the framework.
If the information contained on this page doesn't help you to find and correct the cause of the problem, please contact your system administrator. To facilitate analysis of the problem, keep a copy of this error page. Hint: Most browsers allow to select all content, copy it and then paste it into an empty document (e.g. email or simple text file).
Root Cause
The initial exception that caused the request to fail, was:
com.sap.tc.webdynpro.services.exceptions.WDRuntimeException: Failed to resolve JCOClient name 'SAP_R3_SelfServiceGenerics_MetaData'. No such JCO destination is defined in the SLD
at com.sap.tc.webdynpro.serverimpl.wdc.sl.JCOClientConnection.resolveConnectionParameter(JCOClientConnection.java:493)
at com.sap.tc.webdynpro.serverimpl.core.sl.AbstractJCOClientConnection.init(AbstractJCOClientConnection.java:247)
at com.sap.tc.webdynpro.serverimpl.core.sl.AbstractJCOClientConnection.<init>(AbstractJCOClientConnection.java:221)
at com.sap.tc.webdynpro.serverimpl.wdc.sl.JCOClientConnection.<init>(JCOClientConnection.java:101)
at com.sap.tc.webdynpro.serverimpl.wdc.sl.SystemLandscapeFactory.getJCOClientConnection(SystemLandscapeFactory.java:144)
... 53 more
See full exception chain for details.
Correction Hints
Retrieving a JCO destination with name 'SAP_R3_SelfServiceGenerics_MetaData' from the System Landscape Directory (SLD) failed, as the destination could not be found in the SLD. The most probable reason for that is that the destination has not been maintained yet.
Use the preinstalled Web Dynpro Content Admin application to check/edit the destination. Use the Ping and Test functions of the Content Admin to verify that each destination is properly configured.
Additional information about the System Landscape Directory and the Web Dynpro Content Admin can be found in the SAP Developer Network (SDN) and in the Online Help for the SAP Web Application Server (installed with SAP NetWeaver Developer Studio and available online).
Note: the above hints are only a guess. They are automatically derived from the exception that occurred and therefore can't be guaranteed to address the original problem in all cases.
System Environment
Client
Web Dynpro Client Type HTML Client
User agent Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; SV1)
Version
DOM version
Client Type msie6
Client Type Profile ie6
ActiveX enabled
Cookies enabled
Frames enabled
Java Applets enabled
JavaScript enabled
Tables enabled
VB Script enabled
Server
Web Dynpro Runtime Vendor: SAP, Build ID: 6.4013.00.0000.20050628104636.0000 (release=630_VAL_REL, buildtime=2005-07-19:20:18:44[UTC], changelist=356134, host=PWDFM026)
J2EE Engine 6.40 patchlevel 95420.313
Java VM Java HotSpot(TM) 64-Bit Server VM, version:1.4.2_06-b03, vendor: Sun Microsystems Inc.
Operating system SunOS, version: 5.10, architecture: sparcv9
Other
Session Locale en_US
Time of Failure Wed Sep 28 08:42:46 EDT 2005 (Java Time: 1127911366734)
Web Dynpro Code Generation Infos
sap.com/pcui_gp~xssutils
SapDictionaryGenerationCore 6.4013.00.0000.20050606171348.0000 (release=630_VAL_REL, buildtime=2005-07-04:20:02:08[UTC], changelist=351717, host=PWDFM026.wdf.sap.corp)
SapDictionaryGenerationTemplates 6.4013.00.0000.20050606171348.0000 (release=630_VAL_REL, buildtime=2005-07-04:20:02:19[UTC], changelist=351717, host=PWDFM026.wdf.sap.corp)
SapGenerationFrameworkCore 6.4012.00.0000.20041104141254.0000 (release=630_VAL_REL, buildtime=2005-04-21:19:52:59[UTC], changelist=298452, host=PWDFM026.wdf.sap.corp)
SapIdeWebDynproCheckLayer 6.4013.00.0000.20050606172055.0000 (release=630_VAL_REL, buildtime=2005-07-04:20:08:32[UTC], changelist=351729, host=PWDFM026.wdf.sap.corp)
SapMetamodelCommon 6.4013.00.0000.20050606171700.0000 (release=630_VAL_REL, buildtime=2005-07-04:19:56:31[UTC], changelist=351724, host=PWDFM026.wdf.sap.corp)
SapMetamodelCore 6.4013.00.0000.20050606171700.0000 (release=630_VAL_REL, buildtime=2005-07-04:19:56:22[UTC], changelist=351724, host=PWDFM026.wdf.sap.corp)
SapMetamodelDictionary 6.4013.00.0000.20050606171352.0000 (release=630_VAL_REL, buildtime=2005-07-04:19:59:38[UTC], changelist=351719, host=PWDFM026.wdf.sap.corp)
SapMetamodelWebDynpro 6.4013.00.0000.20050609113138.0000 (release=630_VAL_REL, buildtime=2005-07-04:20:05:19[UTC], changelist=352442, host=PWDFM026.wdf.sap.corp)
SapWebDynproGenerationCTemplates 6.4013.00.0000.20050628104636.0000 (release=630_VAL_REL, buildtime=2005-07-04:20:19:30[UTC], changelist=356134, host=PWDFM026)
SapWebDynproGenerationCore 6.4013.00.0000.20050606172055.0000 (release=630_VAL_REL, buildtime=2005-07-04:20:09:01[UTC], changelist=351729, host=PWDFM026.wdf.sap.corp)
SapWebDynproGenerationTemplates 6.4013.00.0000.20050628104636.0000 (release=630_VAL_REL, buildtime=2005-07-04:20:19:30[UTC], changelist=356134, host=PWDFM026)
sap.com/tcwddispwda
No information available
sap.com/pcui_gp~xssfpm
SapDictionaryGenerationCore 6.4013.00.0000.20050606171348.0000 (release=630_VAL_REL, buildtime=2005-07-04:20:02:08[UTC], changelist=351717, host=PWDFM026.wdf.sap.corp)
SapDictionaryGenerationTemplates 6.4013.00.0000.20050606171348.0000 (release=630_VAL_REL, buildtime=2005-07-04:20:02:19[UTC], changelist=351717, host=PWDFM026.wdf.sap.corp)
SapGenerationFrameworkCore 6.4012.00.0000.20041104141254.0000 (release=630_VAL_REL, buildtime=2005-04-21:19:52:59[UTC], changelist=298452, host=PWDFM026.wdf.sap.corp)
SapIdeWebDynproCheckLayer 6.4013.00.0000.20050606172055.0000 (release=630_VAL_REL, buildtime=2005-07-04:20:08:32[UTC], changelist=351729, host=PWDFM026.wdf.sap.corp)
SapMetamodelCommon 6.4013.00.0000.20050606171700.0000 (release=630_VAL_REL, buildtime=2005-07-04:19:56:31[UTC], changelist=351724, host=PWDFM026.wdf.sap.corp)
SapMetamodelCore 6.4013.00.0000.20050606171700.0000 (release=630_VAL_REL, buildtime=2005-07-04:19:56:22[UTC], changelist=351724, host=PWDFM026.wdf.sap.corp)
SapMetamodelDictionary 6.4013.00.0000.20050606171352.0000 (release=630_VAL_REL, buildtime=2005-07-04:19:59:38[UTC], changelist=351719, host=PWDFM026.wdf.sap.corp)
SapMetamodelWebDynpro 6.4013.00.0000.20050609113138.0000 (release=630_VAL_REL, buildtime=2005-07-04:20:05:19[UTC], changelist=352442, host=PWDFM026.wdf.sap.corp)
SapWebDynproGenerationCTemplates 6.4013.00.0000.20050628104636.0000 (release=630_VAL_REL, buildtime=2005-07-04:20:19:30[UTC], changelist=356134, host=PWDFM026)
SapWebDynproGenerationCore 6.4013.00.0000.20050606172055.0000 (release=630_VAL_REL, buildtime=2005-07-04:20:09:01[UTC], changelist=351729, host=PWDFM026.wdf.sap.corp)
SapWebDynproGenerationTemplates 6.4013.00.0000.20050628104636.0000 (release=630_VAL_REL, buildtime=2005-07-04:20:19:30[UTC], changelist=356134, host=PWDFM026)
sap.com/tcwdcorecomp
No information available
Detailed Error Information
Detailed Exception Chain
com.sap.tc.webdynpro.services.exceptions.WDRuntimeException: Error while obtaining JCO connection.
at com.sap.tc.webdynpro.services.datatypes.core.DataTypeBroker$1.fillSldConnection(DataTypeBroker.java:90)
at com.sap.dictionary.runtime.ProviderFactory.internalResolveLogicalNameToJCODestination(ProviderFactory.java:408)
at com.sap.dictionary.runtime.ProviderFactory.resolveLogicalNameToJCODestination(ProviderFactory.java:354)
at com.sap.dictionary.runtime.ProviderFactory.internalGetProvider(ProviderFactory.java:215)
at com.sap.dictionary.runtime.ProviderFactory.getProvider(ProviderFactory.java:180)
at com.sap.dictionary.runtime.DdDictionaryPool.getProvider(DdDictionaryPool.java:87)
at com.sap.dictionary.runtime.DdDictionaryPool.getDictionary(DdDictionaryPool.java:73)
at com.sap.dictionary.runtime.DdDictionaryPool.getDictionary(DdDictionaryPool.java:48)
at com.sap.dictionary.runtime.DdBroker.getDataType(DdBroker.java:149)
at com.sap.dictionary.runtime.DdBroker.getSimpleType(DdBroker.java:170)
at com.sap.tc.webdynpro.services.datatypes.core.DataTypeBroker.getSimpleType(DataTypeBroker.java:242)
at com.sap.tc.webdynpro.services.datatypes.core.DataTypeBroker.getDataType(DataTypeBroker.java:213)
at com.sap.tc.webdynpro.progmodel.context.AttributeInfo.init(AttributeInfo.java:485)
at com.sap.tc.webdynpro.progmodel.context.NodeInfo.initAttributes(NodeInfo.java:771)
at com.sap.tc.webdynpro.progmodel.context.NodeInfo.init(NodeInfo.java:756)
at com.sap.tc.webdynpro.progmodel.context.NodeInfo.init(NodeInfo.java:761)
at com.sap.tc.webdynpro.progmodel.context.Context.init(Context.java:40)
at com.sap.tc.webdynpro.progmodel.controller.Controller.init(Controller.java:199)
at com.sap.tc.webdynpro.progmodel.controller.Component.getCustomControllerInternal(Component.java:436)
at com.sap.tc.webdynpro.progmodel.controller.Component.getController(Component.java:365)
at com.sap.tc.webdynpro.progmodel.generation.DelegatingComponent.getPublicInterface(DelegatingComponent.java:142)
at com.sap.pcuigp.xssfpm.wd.wdp.InternalFPMComponent.wdGetBackendConnectionsController(InternalFPMComponent.java:204)
at com.sap.pcuigp.xssfpm.wd.FPMComponent.wdDoInit(FPMComponent.java:170)
at com.sap.pcuigp.xssfpm.wd.wdp.InternalFPMComponent.wdDoInit(InternalFPMComponent.java:110)
at com.sap.tc.webdynpro.progmodel.generation.DelegatingComponent.doInit(DelegatingComponent.java:95)
at com.sap.tc.webdynpro.progmodel.controller.Controller.initController(Controller.java:215)
at com.sap.tc.webdynpro.progmodel.controller.Controller.init(Controller.java:200)
at com.sap.tc.webdynpro.clientserver.cal.ClientComponent.init(ClientComponent.java:346)
at com.sap.tc.webdynpro.clientserver.cal.ClientApplication.init(ClientApplication.java:370)
at com.sap.tc.webdynpro.clientserver.task.WebDynproMainTask.execute(WebDynproMainTask.java:608)
at com.sap.tc.webdynpro.clientserver.cal.AbstractClient.executeTasks(AbstractClient.java:59)
at com.sap.tc.webdynpro.clientserver.cal.ClientManager.doProcessing(ClientManager.java:248)
at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doWebDynproProcessing(DispatcherServlet.java:154)
at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doContent(DispatcherServlet.java:116)
at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doGet(DispatcherServlet.java:48)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:740)
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.tc.webdynpro.services.sal.sl.api.WDSystemLandscapeException: Error while obtaining JCO connection.
at com.sap.tc.webdynpro.serverimpl.wdc.sl.SystemLandscapeFactory.getJCOClientConnection(SystemLandscapeFactory.java:146)
at com.sap.tc.webdynpro.serverimpl.wdc.sl.SystemLandscapeFactory.getJCOClientConnectionUnMapped(SystemLandscapeFactory.java:172)
at com.sap.tc.webdynpro.services.sal.sl.core.SystemLandscapeInternal.getJCOClientConnectionUnMapped(SystemLandscapeInternal.java:83)
at com.sap.tc.webdynpro.services.datatypes.core.DataTypeBroker$1.fillSldConnection(DataTypeBroker.java:77)
... 50 more
Caused by: com.sap.tc.webdynpro.services.exceptions.WDRuntimeException: Failed to resolve JCOClient name 'SAP_R3_SelfServiceGenerics_MetaData'. No such JCO destination is defined in the SLD
at com.sap.tc.webdynpro.serverimpl.wdc.sl.JCOClientConnection.resolveConnectionParameter(JCOClientConnection.java:493)
at com.sap.tc.webdynpro.serverimpl.core.sl.AbstractJCOClientConnection.init(AbstractJCOClientConnection.java:247)
at com.sap.tc.webdynpro.serverimpl.core.sl.AbstractJCOClientConnection.<init>(AbstractJCOClientConnection.java:221)
at com.sap.tc.webdynpro.serverimpl.wdc.sl.JCOClientConnection.<init>(JCOClientConnection.java:101)
at com.sap.tc.webdynpro.serverimpl.wdc.sl.SystemLandscapeFactory.getJCOClientConnection(SystemLandscapeFactory.java:144)
... 53 more
Thanks, Neeta -
EP6 SP13 dispatcher performance problem?
Hello,
I'm currently experiencing a weird problem with the dispatcher of a SP13 installation.
When I run load tests on this system after upgrade to SP13 (or around there sometime), the dispatcher now uses more CPU than a server node (which we have 4 of). I've never seen, or at least noticed, that the dispatcher uses any CPU before... What could be wrong? The portal performance slows down way before the servers get to their top load for the most part.
Thanks!
Tarjei BitustøylJochen,
Thanks for the reply. Here is the "graphical" flow;
IE==>HW-LB==> 3 (Apache==>Reverse Proxy-->WebDisp) --> 2 (WAS 6.40 SP11 PL3)
(Legend ==> HTTPS --> HTTP)
At the risk of redundancy, there are 3 Linux SLES8 servers running Apache2 with Reverse Proxy, and the Web Dispatcher 6.40 PL90. Each of these servers are/should be distributing load to 2 WAS 6.40 SP11 PL3 Java-only servers running Windows 2003.
My assumption is that reverse proxy is sending HTTP to the dispatcher then on to WAS or at least pass thru. Should I setup a HTTPS terminate at the dispatcher?
Here's the sapwebdisp.pfl;
Profile generated by sapwebdisp bootstrap
unique instance number
SAPSYSTEM = 01
Accesssability of Message Servers
rdisp/mshost = msgserver.reinternal.com
ms/http_port = 8101
SAP Web Dispatcher Parameter
wdisp/auto_refresh = 120
wdisp/max_servers = 100
#maximum number of concurrent connections to one server
wdisp/HTTP/max_pooled_con = 8000
wdisp/HTTPS/max_pooled_con = 8000
SAP Web Dispatcher Ports
icm/server_port_0 = PROT=HTTP,PORT=8080
SAP Web Dispatcher Web Administration
icm/HTTP/admin_0 = PREFIX=/sap/wdisp/admin,DOCROOT=./admin, PORT=8080
icm/max_conn = 8192
icm/max_sockets = 16384
icm/min_threads = 100
icm/max_threads = 250
icm/req_queue_len = 6000
icm/conn_timeout = 90000
icm/keep_alive_timeout = 90
mpi/total_size_MB = 350
mpi/max_pipes = 13500
mpi/buffer_size = 32768
Any advice or suggested course of action would be appreciated.
Thanks,
Dan -
Unable to Activate Maintenance cycle /TMWFLOW/TASKLIST050
Hi!
I am about to work with ChaRM. When I go to maintenance cycle and try to activate them, I go the error /TMWFLOW/TASKLIST050.
The following errors are also there:
/TMWFLOW/PHCNTRL 54
/TMWFLOW/PHCNTRL 56
I closed this maintenance cycle and opened a new one, but still have the same error.
Can some one help me to solve this problem?
Thank you very much!
Regards
ThomI've got the same problem - except that the business partner looks OK to me. So actually it should work (created as a person incl. role employee, tab identification contains the user name etc.). Nevertheless I still get the message that it's not valid constantly. I'd really appreciate any idea.
Thanks!
Cheers,
Andy
Edited by: Andy Rohr on Dec 8, 2008 7:16 PM:
Business partner was double --> no clear determination possible that way - that couldn't work, of course )) -
Hi,
I've installed HH Mobile Service SP08 on MI Client SP09, WAS 6.4 SP13.
The problem was that after sync, the message was 'Data successfully received', I could not see anything in the application. The trace file however contained the data coming from backend(CRM4.0 SP07).
After having found an OSS Note (761419) that says that MSA + MSE are not supported by MI Client SP09 I've installed MI Client SP13. The message after sync is still the same, but no data are visible in the application. And even the trace doesn't contain data anymore.
Has anybody had the same problem?
thanks, tatjanaHello Tatjana,
have you done all the required Customizing as described in the Scenario Configuration Guide? Have you understand the Product Partner Range (PPR) customizing? How have you done it? Can you post a short description?
I would suggest to use Mobile Engine 2.1 if you have a WebAS ABAP 6.20 avaliable. Because this is the enviroment where MSA HH was developed for.
Regards
Gregor -
Issues changing Project Status in Solution Manager
Hello All;
I have a project in Solution Manager that is ready to be closed out. When I try to advance the status from 'TEST" to "Emergency Correction' I get the following messages
MsgType Message Class Msg.no. Message text
E /TMWFLOW/PHCNTRL 54 Change transaction is incorrect
E /TMWFLOW/PHCNTRL 56 Phase transition from 'Test' to 'Emergency Correction' is not possible
I have not been able to find any more information on these messages or how to correct the Change Transaction. I appreciate any and all help.
Thanks,
MikeHi,
R u changing from Task list
goto to ur project Maintenance cycle from System landscape tab
here click Action Tab ..for changing the next phase...
since currently u have already tried there wil be error so go to error tab it will be on the top right side...
here click on it and remove all the errors
once you have removed the error then only choose update maintenance cycle action and later move to next phase
Thus it will solve ur problem
Regards
Prakhar -
Maintenance Cycle Phase transistion
Hi,
We are using chaRM 4.0, in tx SCMA,we can not able to move the Phase Transistion from 'Created' to 'Development without Release'. When we click on the next phase it is giving the below error . kindly help us.
MsgType Message Class Msg.no. Message text
E /TMWFLOW/PHCNTRL 54 Change transaction
is incorrect
E /TMWFLOW/PHCNTRL 56 Phase transition
from 'Created'
to 'Development
without Release' is
not possible
Rgds,
Jeni.Please kindly check on the following notes
933986 Phase transition not possible
909236 No phase transition possible after Note 898168
902579 Maintenace cycle cannot progress to next phase
Prakash -
Hi,
We are using chaRM 4.0, in tx SCMA,we can not able to move the Phase Transistion from 'Created' to 'Development without Release'. When we click on the next phase it is giving the below error . kindly help us.
MsgType Message Class Msg.no. Message text
E /TMWFLOW/PHCNTRL 54 Change transaction
is incorrect
E /TMWFLOW/PHCNTRL 56 Phase transition
from 'Created'
to 'Development
without Release' is
not possible
Rgds,
Jeni.Hello Jenifer,
The problem usually is due to errors in the CRM transaction that represents the Maintenance Cycle. You can check it by calling transaction CRM_DNO_MONITOR and entering in the transaction type SDMN then process.
You will get a list of all Maintenance cycles, select the proper one and double click.
In the CRM Transaction in the upper/right side you should have a red button if you click it you can find out the reason for the error and correct it.
Then the Phase change can be performed.
Just a info for you, you can also perform the Phase Change throught the CRM transaction type SDMN, check the actions button and you will find it.
Regards,
Andreia -
Maintenance Cycle - ChaRM - Operation type SDMN
HI, Gurus.
I need to come back the status of the operation SDMN (Maintenance Cycle). The status was changed to "Being Completed" but this operation doesn't be closed. How i can change (rollback) the status
to "Go Live"?
Below, the error messagens:
"Phase change from 'Being Completed' to 'Go-Live' is not possible"
E /TMWFLOW/PHCNTRL 51 Change transaction is locked
E /TMWFLOW/PHCNTRL 56 Phase transition from 'Being Completed' to 'Go-Live' is not possible
Thanks for all help.
FS.Fabio,
goto solar_project_admin and choose maintenance transaction
You need to go to the sdmn transaction or the maintenance cycle transaction here click the error tab and check for errors
Also check the tast list if there is no lock in the Completion task
for e.g there is a lock Icon in front of task so if you hav to perform this then make it unlock for the go live task in the task list
hope it helps.
Regards
Prakhar
Edited by: Prakhar Saxena on Jun 3, 2009 10:03 AM -
Problem in tables of transport request !!!!
Hi all,
When i doing the Charm Process....nd during that when the developer generates the transport request....at that time that tp request appears in table /tmwflow/trordhc but it does not appear in /tmwflow/track .... nd after releasing the subtasks and then finally the whole transport request....at that point also it does not appear in /tmwflow/track ..... after this when the basis person pass that transport request to quality....then the /tmwflow/track shows 1 record for that transport request.....so finally after the whole flow /tmwflow/track will show 2 records for that transport request i.e 1 of quality and 1 of production....logically 'dev' record should also be there.....what i am noticing is after few hours like 2 or 3 hours that development record started appearing in table /tmwflow/track .... so is it a problem in configuration of solution manager or this sudden appearance of dev record is ok....coz ive to build a report in which it displays the tracking of tp requests....
Any suggestions would be helpful...
Regards,
DeadlocksHey deadlocks,
many ChaRM tables are updated as Fernando said when cmssyscol job finished.
I guess those 2/3 hours correspond to the time u waited before the job runned. The transaction solar_eval and a couple of others allow u updating data as well.
U have to know that this job may sometimes/quite often give unsupected/missing data; and also delayed. The best you can do is simply read the tr log using a function modul and interpretate info concerning the transport requests
CALL FUNCTION 'TRINT_TDR_USER_COMMAND'
EXPORTING
iv_object = lv_object
iv_type = ls_sel_node-type
iv_command = lv_command
IMPORTING
ev_exit = pv_exit.
LV_OBJECT SLMK900004
LS_SEL_NODE-TYPE REQU
LV_COMMAND TAST
for example.
You can debug log reading in SE01 and put a watchpoint on instruction 'CALL FUNCTION'. It is the second one.
This will display log on screen
Good luck
Khalil -
Can I use a normal wap enabled phone for MI
Suppose I have a simple wap enabled phone like sony erickson
K310i or nokia 6600 or any other normal wap enabled phone will it support MI application.I mean can I use MI application in a normal wap enabled phone or it is only possible in blackberry phones or some specific phone models?Ameer Bhai
I am getting the following error while synchronising MI2.5 SP13 Client
"Synchronisation problems: Format of the synchronization inbound file is not supported; Check sync gateway "
The servive pack of my WebAs and Server is SP13.
Is there any syncbo setting necessary If yes please specify.
Please help me with this .
Also tell me where we get MI server IP address
Edited by: anzar naik on May 12, 2008 3:46 PM -
Error within General Task: Register transport request in task list
Dear all,
I would like to register transports into a task list. When I try to do so I get the following error:
Error RFC destination SPROJECT_GET_SMI_DATA_R: Projekt: ZCHARM_DQ
Message no. /TMWFLOW/TASKLIST191
Some one got an idea where the problem might be?
Any help would be much appreciated.
Best regards
DanielHi Daniel,
This error is reported in SDN blog /people/dolores.correa/blog/2009/07/22/change-request-management-scenario-usual-questions-and-known-errors
in point 21
21. Missing authorization for READ RFC connections
Our default authorizations for remote READ RFC users (created in SMSY) do not allow us to read transport requests information. But READ RFC users are used extensively in Charm to get those information. It is a bug in SMSY which has not been fixed by now. So currently for such kind of messages we have to ask our customer to manually add appropriate authorizations (e.g. profile S_TMW_CREATE) to those READ RFC users.
- Open transport requests are not marked as red when release them from task list.
Note 1279558 - Red Question Mark Icon Missing from Charm Transport Release
- "Error RFC destination SPROJECT_GET_SMI_DATA_R" when register outside transport requests into Charm.
Please assign enough authorizations to all those READ RFC users on their DEV system (including client 000).
- Cannot complete maintenance cycle due to "Error RFC destination /TMWFLOW/TL_COMPL_CHK_TR_WO_TL"
Please assign enough authorizations to all those READ RFC users on their DEV system (including client 000).
- Transport request information is missing in the result of Charm Reporting.
Please assign enough authorizations to all those READ RFC users on their DEV system (including client 000). And after that they should re-execute background job SM:TMWFLOW_CMSSYSCOL to update those information on Solution Manager system again.
Hope this helps,
Dolores -
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
Maybe you are looking for
-
Excel file corrupt after saving to another disk
I have two PCs at home.: A laptop running Win-7 64-bit, and a desktop running Win-7 32-bit. Both are running Office 2010. Often, but not always, when I save an Excel workbook from one PC onto a shared hard drive on my home network and then try to o
-
I'm trying to install the Windows Phone 8.1 Preview for Devlopers but it won't install. I get x80188308. (I've tried 3 times) My Phone info: NOKIA Lumia 920 OS version 8.10.12400.899 Lumia Cyan RM-820_nam_canada_200, core build 3051.50009.1424.10362
-
No Sound from Adobe Read-Aloud
I have a PC running Windows 7. I have Adobe XI and Adobe Acrobat Pro intalled. I can turn on "Read-Aloud" in either but when "Read-Aloud" is turned on and I choose to read the page, the document or just a paragraph, no sound is produced. The sound ca
-
Hi All! Would you know guys how SAP sort vendor open items and how it allocates/assigns checks for each open item that will be paid? Thanks in advance.
-
Computer keeps asking to be restarted after update
Its an old G4 450mz that is running OSX and has been updated regularly with each patch that has come out. For some reason after todays update it keeps wanting to be restarted. The message I get after each restart is that its been updated and needs to