OEM is not getting started after changing the Server name

Hello DBAs
Recently I installed Oracle database 10g on my a windows machine. It was working fine. Integrated OEM was also working fine.
But now I have changed the machine name. Now Oracle Database has come up after updating the listener.ora & tnsnames.ora files with new server name. But OEM page is not getting open now. I tried after updating the emd.properties and other related file on ORACLE_HOME\sysman folder with the new server name. But no luck.
In windows services one service named *"OracleDBConsoleDbname"* is not getting started, which could be the issue.
Can someone please guide me what can be done to fix this problem.
Thanks
-Naveen

Hi Naveen,
What you are doing is not supported by Oracle. From EM Database Console FAQ (863631.1):
What action needs to be taken if the hostname or SID of the database server is changed?
If there is a hostname or SID change for the database server then the database console needs to be recreated. There is no other solution if the hostname or SID is changed other that recreating the database console. All database console configuration files are created under the hostname_sid directory and the configuration files along with the repository keeps reference of the hostname, which is why dbconsole needs to be reconfigured if there is change in hostname/sid.
Refer : Note.293678.1 How To Reconfigure DB Control After a Hostname, Domain name or Listener Change Has Occurred On The Server
And take a look at note 278100.1: How To Drop, Create And Recreate DB Control In A 10g Database
Eric

Similar Messages

Services in JCo RFC not getting started after Changing the client from 001

Hi SAP Stars,
I have recently Installed Quality and Production servers with PI 7.1 on windows 2003, Sqlserver 2005, when I'm doing Post Activities(http://host:port/nwa) in which I try to change the client from 001 to 300(newly created) in JCo RFC(4 services) and start the service it is throwing error when I again change it to 001 client and start the service it is getting started, Could anyone help me in solving this issue same issue I facing in PI 7.1 Quality and Production
Thanks In Advance
Anil Kumar

Hi Anil,
All these JCo RFCs are client specific RFCs.
Please logon your PI NWA
Choose Configuration Management - Infrastructure- JCo RFC Provider
Then, Select the RFC
Under Details -> Choose Repository Configuraton
Change the client name to 300 (your new client)
Save
And repeat the same for all JCo RFC that you want to work for your newly created client.
Please ensure that you are using SAPJSF user & correct password for all these RFCs.
Ideally, these rfcs shuould work now if now please restart your PI (mostly Java alone also do)
I hope this helps you.
Regards
Sekhar
Edited by: sekhar on Dec 17, 2009 11:39 AM

OEM is not getting started after windows server name changed

Hello DBAs
Recently I installed Oracle database 10g on my a windows machine. It was working fine. Integrated OEM was also working fine.
But now I have changed the machine name. Now Oracle Database has come up after updating the listener.ora & tnsnames.ora files with new server name. But OEM page is not getting open now. I tried after updating the emd.properties and other related file on ORACLE_HOME\sysman folder with the new server name. But no luck.
In windows services one service named "OracleDBConsoleDbname" is not getting started, which could be the issue.
Can someone please guide me what can be done to fix this problem.
Thanks
-Naveen

This problem will happen when either changing the computer name or changing the domain name that the server belongs to.
First, verify that the new computer name contains DNS compatible characters - no spaces or underscore ( _ ) characters, for instance. Next, you will need to recreate the Enterprise Manager Database Control repository. Directions can be found on this page under the heading of "6.2.8.3 Using EMCA After Changing the Database Host Name or IP Address":
http://download.oracle.com/docs/cd/E11882_01/install.112/e10818/srvpool.htm#CHDEGDIJ
The above directions should work as shown with Oracle 10g R2 - and possibly 10g R1 also.
Charles Hooper
Co-author of "Expert Oracle Practices: Oracle Database Administration from the Oak Table"
http://hoopercharles.wordpress.com/
IT Manager/Oracle DBA
K&M Machine-Fabricating, Inc.

"disp+work" process in not getting started after kernel upgradation

Hello Experts,
Good day…..,
I am new to SAP. I installed SAP ECC6 EHP4 with default kernel version 701 and it was working fine.
I have upgraded kernel version from 701 to 741, but the “disp+work” process is not getting started after kernel upgrade.
I have posted “dev_W0” log &
“disp+work” command result obtained in CMD prompt of respective server.
Please help me out in this. Thanks all in advance.
“dev_w0” Log”
trc file: "dev_w0", trc level: 1, release: "741"
* ACTIVE TRACE LEVEL           1
* ACTIVE TRACE COMPONENTS      all, MJ
M sysno      55
M sid        TNG
M systemid   562 (PC with Windows NT)
M relno      7410
M patchlevel 0
M patchno    42
M intno      20020600
M make multithreaded, Unicode, 64 bit, optimized
M profile D:\usr\sap\TNG\SYS\profile\TNG_DVEBMGS55_ABTHMSSB01
M pid        2392
M
M
M Wed Jul 23 02:04:35 2014
M kernel runs with dp version 208000(ext=117000) (@(#) DPLIB-INT-VERSION-208000-UC)
M length of sys_adm_ext is 500 bytes
M ***LOG Q0Q=> tskh_init, WPStart (Workp. 0 2392) [dpInit.c 731]
M DpCommonParamInit: rdisp/core_file_size = default --> no change
I MtxInit: 30000 0 0
M
M Wed Jul 23 02:04:36 2014
M DpIPCInit2: read dp-profile-values from sys_adm_ext
M DpShMCreate: alloate/attach shared memory (mode=ATTACH)
M DpShMCreate: sizeof(wp_adm)                         24288    (1104)
M DpShMCreate: sizeof(tm_adm)                          51472080             (256080)
M DpShMCreate: sizeof(ca_adm)                           432000 (72)
M DpCommTableSize: max/headSize/ftSize/tableSize=500/16/7464064/7583152
M DpShMCreate: sizeof(comm_adm)                   7583152                (14904)
M DpSlockTableSize: max/headSize/ftSize/fiSize/tableSize=0/0/0/0/0
M DpShMCreate: sizeof(slock_adm)                      0              (296)
M DpFileTableSize: max/headSize/ftSize/tableSize=0/0/0/0
M DpShMCreate: sizeof(file_adm)                         0              (80)
M DpSockTableSize: max/headSize/ftSize/tableSize=500/16/520064/520080
M DpShMCreate: sizeof(sock_adm)                       520080 (1016)
M DpShMCreate: sizeof(vmc_adm)                       0              (3208)
M DpShMCreate: sizeof(wall_adm)                        (ft=41664/fi=67472/hd=64/rec=192)
M DpShMCreate: sizeof(amc_rec_adm)                              (ft=86464/fi=67472/hd=64/rec=416)
M DpShMCreate: sizeof(websocket_adm)                         (ft=28864/hd=64/rec=272)
M DpShMCreate: sizeof(gw_adm)          64
M DpShMCreate: sizeof(j2ee_adm)       3936
M DpShMCreate: SHM_DP_ADM_KEY                  (addr: 00000000103D0050, size: 60433936
M DpShMCreate: allocated sys_adm at 00000000103D0250
M DpShMCreate: allocated wp_adm_list at 00000000103E20F0
M DpShMCreate: allocated wp_adm at 00000000103E2410
M DpShMCreate: allocated tm_adm_list at 00000000103E84F0
M DpShMCreate: allocated tm_adm at 00000000103E8730
M DpShMCreate: allocated ca_adm at 00000000134FF000
M DpShMCreate: allocated comm_adm at 0000000013568980
M DpShMCreate: system runs without slock table
M DpShMCreate: allocated sock_adm at 0000000013CA4130
M DpShMCreate: allocated vmc_adm_list at 0000000013D232C0
M DpShMCreate: system runs without VMC
M DpShMCreate: allocated gw_adm at 0000000013D23560
M DpShMCreate: allocated j2ee_adm at 0000000013D237A0
M DpShMCreate: allocated ca_info at 0000000013D24900
M DpShMCreate: allocated wall_adm (ft) at 0000000013D24B40
M DpShMCreate: allocated wall_adm (fi) at 0000000013D2F000
M DpShMCreate: allocated wall_adm (head) at 0000000013D3F990
M DpShMCreate: allocated amc_rec_adm (ft) at 0000000013D3FBD0
M DpShMCreate: allocated amc_rec_adm (fi) at 0000000013D54F90
M DpShMCreate: allocated amc_rec_adm (head) at 0000000013D65920
M DpShMCreate: allocated websocket_adm (ft) at 0000000013D65B60
M DpShMCreate: allocated websocket_adm (head) at 0000000013D6CE20
M DpShMCreate: initialized 21 eyes
M DpCommAttachTable: attached comm table (header=0000000013568980/ft=0000000013568990/fi=0000000013C86E10)
M DpSockAttachTable: attached sock table (header=0000000013CA4130/ft=0000000013CA4140)
X EmInit: MmSetImplementation( 2 ).
X MM global diagnostic options set: 0
X <ES> client 0 initializing ....
X <ES> EsILock: use Semphore 33 for locking
X Using implementation view
X <EsNT> Using memory model view.
M <EsNT> Memory Reset disabled as NT default
X ES initialized.
X
X Wed Jul 23 02:04:37 2014
X mm.dump: set maximum dump mem to 96 MB
M ThStart: taskhandler started
M ThInit: initializing DIA work process W0
M
M Wed Jul 23 02:04:44 2014
M ThInit: running on host ABTHMSSB01
I MtxInit: 0 0 0
M
M Wed Jul 23 02:04:45 2014
M calling db_connect ...
B Loading DB library 'D:\usr\sap\TNG\DVEBMGS55\exe\dboraslib.dll' ...
B Library 'D:\usr\sap\TNG\DVEBMGS55\exe\dboraslib.dll' loaded
B Version of 'D:\usr\sap\TNG\DVEBMGS55\exe\dboraslib.dll' is "741.10", patchlevel (0.42)
C Prepending D:\usr\sap\TNG\DVEBMGS55\exe to Path.
C Register application info.
C
C Wed Jul 23 02:04:47 2014
C Oracle client version: 10.2.0.4.0, (dbsl 741 040714, UNICODE[2])
C Detailed Oracle client (patch) info not available.
C *** ERROR => Connect via SAPUSER not supported for kernel >= 740.
[dbsloci.c    2406]
C     Only Secure Connect method possible.
M ***LOG R19=> ThDbConnect, db_connect ( DB-Connect 000256) [thDatabase.c 76]
M in_ThErrHandle: 1
M *** ERROR => ThInit: db_connect (step TH_INIT, thRc ERROR-DB-CONNECT_ERROR, action STOP_WP, level 1) [thxxhead.c   2281]
M Wed Jul 23 02:04:48 2014
M
M Info for wp 0
M
M    pid = 2392
M    severity = 0
M    status = 0
M    stat = WP_NEW
M    waiting_for = NO_WAITING
M    workerType = DP_WORKER_DIAWP
M    act_cs_count = 0
M    csTrack = 0
M    csTrackRwExcl = 0
M    csTrackRwShrd = 0
M mode_cleaned_counter = 0
M    control_flag = 0
M    report = > <
M    action = 0
M    tab_name = >                              <
M
M ThIErrHandle: no current incoming request
M
M
M *****************************************************************************
M *
M * LOCATION SAP-Server ABTHMSSB01_TNG_55 on host ABTHMSSB01 (wp 0)
M * ERROR ThInit: db_connect
M *
M * TIME Wed Jul 23 02:04:48 2014
M * RELEASE 741
M * COMPONENT Taskhandler
M * VERSION 1
M * RC 16797709
M * MODULE D:/depot/bas/741_REL/src/krn/si/th/thxxhead.c
M * LINE 2470
M * COUNTER 1
M *
M *****************************************************************************
M
M PfRejectStatistic: clear statistic record
M PfClearAllRec: clear statistic area
M PfClearAllRec: statRecordAction = STAT_RECORD_ACTION_REJECT
M Entering TH_CALLHOOKS
M ThCallHooks: call hooks for event BEFORE_DUMP
M ThIErrHandle: entering ThSetStatError
M ThIErrHandle: do not call ThrCoreInfo (no_core_info=0, in_dynp_env=0)
M call ThrShutDown (1)...
M ***LOG Q02=> wp_halt, WPStop (Workp. 0 2392) [dpnttool.c 335]
“Desp+Work” Command result:
C:\Users\tngadm>disp+work
disp+work information
kernel release 741
kernel make variant 741_REL
compiled on NT 6.0 6002 x86 MS VC++ 16.00 for NTAMD64
compiled for                  64 BIT
compilation mode UNICODE
compile time Jul 9 2014 16:39:46
update level 0
patch number 42
source id 0.042
RKS compatibility level 0
supported environment
database (SAP, table SVERS) 700
710
701
702
703
                              711
720
730
731
732
738
740
operating system
Windows NT 5.1
Windows NT 5.2
Windows NT 6.0
Windows NT 6.1
Windows NT 6.2
Windows NT 6.3
C:\Users\tng

C *** ERROR => Connect via SAPUSER not supported for kernel >= 740.
[dbsloci.c    2406]
C     Only Secure Connect method possible.
For this issue you need to set up SSFS.
1639578 - SSFS as password storage for primary database connect
I am new to SAP. I installed SAP ECC6 EHP4 with default kernel version 701 and it was working fine.
I have upgraded kernel version from 701 to 741
Are you sure kernel 741 is compatible with an EHP 4 system ?
Read this SAP note
1969546 - Release Roadmap Kernel 740
Regards
RB

Interface getting failed after changing the Business system to that service

Hello All,
Our Env... is XI 3.0 and this is related to produciton env.
Based on our client requirment to change the business system from client 871 to 100 for one of the R3 system which is reciever type(rfc).
After doing all the necessary changes , that particular service is getting failed and in the CC monitoring for that service I can see the log as "RFC_ERROR_LOGIN_FAILURE" mandate 871 (earlier client) does not exist in the system.
The steps which I have followed to change the Business system.
1>I loged into the SLD of PRD system and clicked on businsess landscape .then i have clicked on the specified system to be changed (RY1 ) and then clicked on change mode and selected the required client (100) and saved the settings.
2>I have logged into ID(Integration Directory) and selected the service (RY1) which need to be changed .Under service -->Adaper specific -->compare sld configurations and then clicked on apply changes.
3>Now selected that communication channel of service (RY1) RFCRecieverR3 and changed the client 871 to 100 and the password of user XIRFCUSER ...
Then i saved the changes and after that i have activated that interface.
After that when i logged into CC monitoring and viewed that service channels and see the following errors:
Receiver channel 'RFCReceiverR3' for party '', service 'RY1'
Error can not instantiate RfcPool caused by:
com.sap.aii.af.rfc.RfcAdapterException: error initializing RfcClientPool:com.sap.aii.af.rfc.core.repository.RfcRepositoryException: can not connect to destination system due to: com.sap.mw.jco.JCO$Exception: (103) RFC_ERROR_LOGON_FAILURE: Mandante 871 não existente no sistema (selecionar mandante existente)
Can any one help me out of this situation , and i need to fix this ASAP as this is production system.
Awaiting for your reply.
Best Regards
Rakesh Reddy

Hello Nisar
Thanks for the update,
Let me say few points about this particular problem:
1>The interface "XX" from XI sends data to two systems( R3 -->RP1 & RY1), some thing like branched (same data is passed to both the reciever systems).
And the second RY1 is copy of First system RP1 (Production sys) which is used for data loading purpose and every week there will be a refresh from First sys (RP1) to Second(RY1).
2>Now the first sys(RP1) is recieving the data successfully from XI , and the second one (RY1) is getting failed .And this started after changing the Business system 871 to 100 .
3>As mentioned by you , I have checked all the points mentioned
    i)In SM59 for XI (ABAP part) two rfc's are maintained (LCRSAPRFC & SAPSLDAPI) and the test connection is also fine...But I did not find these two connections in reciever systems(RP1 & RY1 too).
   ii)In reciever system RY1 ,when i went to RZ70 , i did not noticed any special settings and SLD Bridge :Gateway Information is not maitained over there .and the same thing in other reciever system(RP1) , with this can we confirm that there is nothing wrong in RZ70 settings.
   iii)In SLDAPICUST at recievers end for both systems nothing is mantained , where as in XI system all the details are maintained(Host name,port, user & password).
I have translated the error log into english from the CC monitoring for this interface which is in portuguese language .
It says that:
RFC_ERROR_LOGON_FAILURE: 871 Mandante not in the system (select principal existing)
Kindly advise me what to do ..for fixing this problem(this is pretty urgent and it is production env...)..
If any information required , I can provide that.
Best Regards
Rakesh Reddy

While i was updating my iphone5, it showed that my sim card is not applicable. even after changing the sim card, i am not able to update or restore my iphone. what should be done?

while i was updating my iphone5, it showed that my sim card is not applicable. even after changing the sim card, i am not able to update or restore my iphone. what should be done?

Hi there aliyan,
I would recommend taking a look at the troubleshooting steps for "No SIM" found in the article below.
If you see 'No SIM' alert on iPhone
-Griff W.

ORA-12545 error after changing the host name as IP address in Tnsnames.ora

HI,
I tried to connect PHP and oracle in Red Hat linux. I got error ORA-12545 after changing the host name as IPAddress in Tnsnames.ora file. In sqlnet.ora file also i have entry for tnsnames in Directory_Path. I struggled so much but i couldnt solve that. Please give me ur valuable suggestions....

12545, 00000, "Connect failed because target host or object does not exist"
// *Cause: The address specified is not valid, or the program being
// connected to does not exist.
// *Action: Ensure the ADDRESS parameters have been entered correctly; the
// most likely incorrect parameter is the node name. Ensure that the
// executable for the server exists (perhaps "oracle" is missing.)
// If the protocol is TCP/IP, edit the TNSNAMES.ORA file to change the
// host name to a numeric IP address and try again.
Seems you specified wrong IP address.

What modifications to be done after changing the Computer name..?

Hi all...
What are the modifications to be done after changing the Computer name..(Hostname) to connect the oracle. When i am restarting the TNS Listener manually, it is giving Error 1067.
Please tell me, what are the modifications to be done, if i change the computer name.
Thanks in advance,
Pal

You need to change your hostname/ip in listener.ora

My iphone can not get in touch with the server. What can I do?

My Iphone can not get in touch with the server, when I am trying to accept terms and conditions. What can I do?

Possible causes:
1. Your antivirus is blocking access to gs.apple.com.
2. Your phone is jailbroken.
3. Your computer has been used at some time in the past to jaibreak some iOS device (not necessarily the phone with the problem), and its network database was corrupted by the hacking software that was used.
4. Apple's activation servers are down (very rare, and never for more than an hour or so).
For 1. try disabling your antivirus.
For 2. & 3. you need to go somewhere other than an apple forum for help. Although you can try deleting lines containing gs.apple.com from your "hosts" file on your computer.

What is this massage in the mail ( can not get mail, connection to the server faild ) ??

hello sir,
what is this massage in the my iphone mail ( can not get mail, connection to the server faild ) ??, why tis massage was showed to me and how to solve this problem because it is so annoying for me.
if this problem solved will showen for me again ?

Basically the message is saying the phone can't talk to the place where your email is stored for some reason. This could be an incorrect username/password, or some other issues. Follow the steps in this article and see if they help:
http://support.apple.com/kb/ts3899

How do I properly change the server name in mountain lion server?

I need to change my server name to a FQDN, but tried this with Lion server in the past without success. I know in lion you'd use server app, but that's no longer avaiable in mountain lion server and I want to make sure I get this right the first time.
Thanks!

I was able to get everything working with some assistance from Apple's enterprise support. After changing the host name, the DNS was still not resolving properly and I couldn't turn on open directory so that I'd be able to start profile manager. The DNS interface is considerably different than that in previous versions of server. The network was set to manual ip with dhcp, which was pulling back an external IP. Overriding the DNS info coming in via the dhcp, setting it to localhost, resolved the issue.
Thanks!

"Is it possible to hide/remove/change the server name/type and

Is it possible to change the server name/type and version number being sent in the http response header by iPlanet Web server so a hacker can't see what server and version I'm running? If yes, what is the procedure to do it?

Hi,
I have tried the ServerString none entry in magnus.conf but still it is showing the Server information in the header if you use telnet . Is there any other way to hide or to mask this information.
Thanks,
Ramki

Issues after changing the AP Name on Wireless LAN Controller

I recently changed the AP Name of all the Wireless Access Points in my branch office (which are all associated to the branch office Wireless LAN Controller(s)). After that I noticed that all branch office employees are unable to connect to the employee SSID. The employee SSID uses web authentication and employees are authenticated using Head Office AD via Cisco ACS, both located at the Head Office.
There are other SSID's on the WLC which all work fine, but only employee SSID which uses AD authentication does not work. AD authenticaion is working fine because employee's in HO are successfully able to connect to the employee SSID at HO.
The branch office is connected to the HO via a tunnel link. We noticed that if we restart both the ASA at either ends of the tunnel. The employee SSID starts working again but only temporarily for a day or so... what could be the issue? Can renaming the AP's cause issues? How can I fix this problem?
Thanks in advance

Thanks Elliott,
I did the debug like you said and I am getting the following debug messages:
*apfMsConnTask_0: Jun 20 08:18:14.580: Deleting the client immediatly since WLAN is changed
and also
*apfReceiveTask: Jun 20 05:25:11.857: 00:1f:3c:86:af:15 Orphan Packet from 192.168.52.34
The logging on the WLC shows
*apfReceiveTask: Jun 18 17:56:41.788: %MM-1-ANCHOR_UNAVAILABLE: mm_mobile.c:2155
All export anchors are down. Cannot anchor the client.00:c0:a8:f3:cd:ae
The DHCP pool for the employee users are configured on a guest WLC which sits behind an ASA

Probem after changing the system name of EP 6.0 SP9

Hi,
I have changed the system name of the EP 6.0 SP9 system and restarted it and after I again shifted back to the old system name and restarted the system.
Now the j2ee engine is not coming up ...
I am placing the developer trace.
Pl. suggest what might have went wrong.
Thanks & Regards
Mrutyunjay
trc file: "E:\usr\sap\D01\JC00\work\dev_jcontrol", trc level: 1, release: "640"
node name   : jcontrol
pid         : 5552
system name : D01
system nr. : 00
started at : Mon Dec 19 11:14:46 2005
arguments   :
    arg[00] : E:\usr\sap\D01\JC00\j2ee\os_libs\jcontrol.exe
    arg[01] : pf=E:\usr\sap\D01\SYS\profile\D01_JC00_portald
JStartupReadInstanceProperties: read instance properties [E:\usr\sap\D01\JC00\j2ee\cluster\instance.properties;E:\usr\sap\D01\JC00\SDM\program\config\sdm_jstartup.properties]
-> ms host    : portald
-> ms port    : 3601
-> OS libs    : E:\usr\sap\D01\JC00\j2ee\os_libs
-> Admin URL :
-> run mode   : NORMAL
-> run action : NONE
-> enabled    : yes
Used property files
-> files [00] : E:\usr\sap\D01\JC00\j2ee\cluster\instance.properties
-> files [01] : E:\usr\sap\D01\JC00\SDM\program\config\sdm_jstartup.properties
Instance properties
-> ms host    : portald
-> ms port    : 3601
-> os libs    : E:\usr\sap\D01\JC00\j2ee\os_libs
-> admin URL :
-> run mode   : NORMAL
-> run action : NONE
-> enabled    : yes
Bootstrap nodes
-> [00] bootstrap            : E:\usr\sap\D01\JC00\j2ee\cluster\instance.properties
-> [01] bootstrap_ID9391400 : E:\usr\sap\D01\JC00\j2ee\cluster\instance.properties
-> [02] bootstrap_ID9391450 : E:\usr\sap\D01\JC00\j2ee\cluster\instance.properties
Worker nodes
-> [00] ID9391400            : E:\usr\sap\D01\JC00\j2ee\cluster\instance.properties
-> [01] ID9391450            : E:\usr\sap\D01\JC00\j2ee\cluster\instance.properties
-> [02] sdm                  : E:\usr\sap\D01\JC00\SDM\program\config\sdm_jstartup.properties
[Thr 2144] Mon Dec 19 11:14:46 2005
[Thr 2144] JControlExecuteBootstrap: execute bootstrap process [bootstrap]
[Thr 2144] [Node: bootstrap] java home is set by profile parameter
     Java Home: c:\j2sdk1.4.2_08
JStartupIReadSection: read node properties [bootstrap]
-> node name       : bootstrap
-> node type       : bootstrap
-> java path       : c:\j2sdk1.4.2_08
-> java parameters : -Djco.jarm=1 -Djco.jarm=1
-> java vm version : 1.4.2_08-b03
-> java vm vendor : Java HotSpot(TM) Server VM (Sun Microsystems Inc.)
-> java vm type    : server
-> java vm cpu     : x86
-> heap size       : 128M
-> root path       : E:\usr\sap\D01\JC00\j2ee\cluster
-> class path      : .\bootstrap\launcher.jar
-> OS libs path    : E:\usr\sap\D01\JC00\j2ee\os_libs
-> main class      : com.sap.engine.offline.OfflineToolStart
-> framework class : com.sap.bc.proj.jstartup.JStartupFramework
-> registr. class : com.sap.bc.proj.jstartup.JStartupNatives
-> framework path : E:\usr\sap\D01\JC00\j2ee\os_libs\jstartup.jar
-> parameters      : com.sap.engine.bootstrap.Bootstrap ./bootstrap ID0093914
-> debuggable      : yes
-> debug mode      : no
-> debug port      : 60000
-> shutdown timeout: 120000
JStartupStartJLaunch: program = E:\usr\sap\D01\JC00/j2ee/os_libs/jlaunch.exe
-> arg[00] = E:\usr\sap\D01\JC00/j2ee/os_libs/jlaunch.exe
-> arg[01] = pf=E:\usr\sap\D01\SYS\profile\D01_JC00_portald
-> arg[02] = -DSAPINFO=D01_00_bootstrap
-> arg[03] = -file=E:\usr\sap\D01\JC00\j2ee\cluster\instance.properties
-> arg[04] = -nodeName=bootstrap
-> arg[05] = -nodeId=-1
-> arg[06] = -syncSem=JSTARTUP_WAIT_ON_5552
-> arg[07] = -jvmOutFile=E:\usr\sap\D01\JC00\work\jvm_bootstrap.out
-> arg[08] = -stdOutFile=E:\usr\sap\D01\JC00\work\std_bootstrap.out
-> arg[09] = -locOutFile=E:\usr\sap\D01\JC00\work\dev_bootstrap
-> arg[10] = -mode=BOOTSTRAP
-> arg[11] = pf=E:\usr\sap\D01\SYS\profile\D01_JC00_portald
-> lib path = PATH=c:\j2sdk1.4.2_08\jre\bin\server;c:\j2sdk1.4.2_08\jre\bin;D:\oracle\D01\920\jre\1.4.2\bin\client;D:\oracle\D01\920\jre\1.4.2\bin;D:\oracle\D01\920\bin;C:\Program Files\Oracle\jre\1.3.1\bin;C:\Program Files\Oracle\jre\1.1.8\bin;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;c:\j2sdk1.4.2_08\bin;E:\usr\sap\D01\SCS01\exe;E:\usr\sap\D01\JC00\exe;E:\usr\sap\D01\SYS\exe\run
-> exe path = PATH=c:\j2sdk1.4.2_08\bin;E:\usr\sap\D01\JC00\j2ee\os_libs;D:\oracle\D01\920\jre\1.4.2\bin\client;D:\oracle\D01\920\jre\1.4.2\bin;D:\oracle\D01\920\bin;C:\Program Files\Oracle\jre\1.3.1\bin;C:\Program Files\Oracle\jre\1.1.8\bin;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;c:\j2sdk1.4.2_08\bin;E:\usr\sap\D01\SCS01\exe;E:\usr\sap\D01\JC00\exe;E:\usr\sap\D01\SYS\exe\run
[Thr 2144] Mon Dec 19 11:14:52 2005
[Thr 2144] JControlExecuteBootstrap: read instance values after global bootstrap
JStartupReadInstanceProperties: read instance properties [E:\usr\sap\D01\JC00\j2ee\cluster\instance.properties;E:\usr\sap\D01\JC00\SDM\program\config\sdm_jstartup.properties]
-> ms host    : portald
-> ms port    : 3601
-> OS libs    : E:\usr\sap\D01\JC00\j2ee\os_libs
-> Admin URL :
-> run mode   : NORMAL
-> run action : NONE
-> enabled    : yes
[Thr 2144] JControlExecuteBootstrap: enumerate the nodes after global bootstrap
Used property files
-> files [00] : E:\usr\sap\D01\JC00\j2ee\cluster\instance.properties
-> files [01] : E:\usr\sap\D01\JC00\SDM\program\config\sdm_jstartup.properties
Instance properties
-> ms host    : portald
-> ms port    : 3601
-> os libs    : E:\usr\sap\D01\JC00\j2ee\os_libs
-> admin URL :
-> run mode   : NORMAL
-> run action : NONE
-> enabled    : yes
Bootstrap nodes
-> [00] bootstrap            : E:\usr\sap\D01\JC00\j2ee\cluster\instance.properties
-> [01] bootstrap_ID9391400 : E:\usr\sap\D01\JC00\j2ee\cluster\instance.properties
-> [02] bootstrap_ID9391450 : E:\usr\sap\D01\JC00\j2ee\cluster\instance.properties
Worker nodes
-> [00] ID9391400            : E:\usr\sap\D01\JC00\j2ee\cluster\instance.properties
-> [01] ID9391450            : E:\usr\sap\D01\JC00\j2ee\cluster\instance.properties
-> [02] sdm                  : E:\usr\sap\D01\JC00\SDM\program\config\sdm_jstartup.properties
[Thr 2144] JControlExecuteBootstrap: execute bootstrap process [bootstrap_ID9391400]
[Thr 2144] INFO: Invalid property value [JLaunchParameters/]
[Thr 2144] [Node: dispatcher bootstrap] java home is set by profile parameter
     Java Home: c:\j2sdk1.4.2_08
JStartupIReadSection: read node properties [bootstrap_ID9391400]
-> node name       : dispatcher bootstrap
-> node type       : bootstrap
-> java path       : c:\j2sdk1.4.2_08
-> java parameters : -Djco.jarm=1 -Djco.jarm=1
-> java vm version : 1.4.2_08-b03
-> java vm vendor : Java HotSpot(TM) Server VM (Sun Microsystems Inc.)
-> java vm type    : server
-> java vm cpu     : x86
-> heap size       : 170M
-> root path       : E:\usr\sap\D01\JC00\j2ee\cluster
-> class path      : .\bootstrap\launcher.jar
-> OS libs path    : E:\usr\sap\D01\JC00\j2ee\os_libs
-> main class      : com.sap.engine.offline.OfflineToolStart
-> framework class : com.sap.bc.proj.jstartup.JStartupFramework
-> registr. class : com.sap.bc.proj.jstartup.JStartupNatives
-> framework path : E:\usr\sap\D01\JC00\j2ee\os_libs\jstartup.jar
-> parameters      : com.sap.engine.bootstrap.Bootstrap ./bootstrap ID009391400
-> debuggable      : yes
-> debug mode      : no
-> debug port      : 60000
-> shutdown timeout: 120000
JStartupStartJLaunch: program = E:\usr\sap\D01\JC00/j2ee/os_libs/jlaunch.exe
-> arg[00] = E:\usr\sap\D01\JC00/j2ee/os_libs/jlaunch.exe
-> arg[01] = pf=E:\usr\sap\D01\SYS\profile\D01_JC00_portald
-> arg[02] = -DSAPINFO=D01_00_bootstrap
-> arg[03] = -file=E:\usr\sap\D01\JC00\j2ee\cluster\instance.properties
-> arg[04] = -nodeName=bootstrap_ID9391400
-> arg[05] = -nodeId=-1
-> arg[06] = -syncSem=JSTARTUP_WAIT_ON_5552
-> arg[07] = -jvmOutFile=E:\usr\sap\D01\JC00\work\jvm_bootstrap_ID9391400.out
-> arg[08] = -stdOutFile=E:\usr\sap\D01\JC00\work\std_bootstrap_ID9391400.out
-> arg[09] = -locOutFile=E:\usr\sap\D01\JC00\work\dev_bootstrap_ID9391400
-> arg[10] = -mode=BOOTSTRAP
-> arg[11] = pf=E:\usr\sap\D01\SYS\profile\D01_JC00_portald
-> lib path = PATH=c:\j2sdk1.4.2_08\jre\bin\server;c:\j2sdk1.4.2_08\jre\bin;D:\oracle\D01\920\jre\1.4.2\bin\client;D:\oracle\D01\920\jre\1.4.2\bin;D:\oracle\D01\920\bin;C:\Program Files\Oracle\jre\1.3.1\bin;C:\Program Files\Oracle\jre\1.1.8\bin;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;c:\j2sdk1.4.2_08\bin;E:\usr\sap\D01\SCS01\exe;E:\usr\sap\D01\JC00\exe;E:\usr\sap\D01\SYS\exe\run
-> exe path = PATH=c:\j2sdk1.4.2_08\bin;E:\usr\sap\D01\JC00\j2ee\os_libs;D:\oracle\D01\920\jre\1.4.2\bin\client;D:\oracle\D01\920\jre\1.4.2\bin;D:\oracle\D01\920\bin;C:\Program Files\Oracle\jre\1.3.1\bin;C:\Program Files\Oracle\jre\1.1.8\bin;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;c:\j2sdk1.4.2_08\bin;E:\usr\sap\D01\SCS01\exe;E:\usr\sap\D01\JC00\exe;E:\usr\sap\D01\SYS\exe\run
[Thr 2144] Mon Dec 19 11:14:58 2005
[Thr 2144] JControlExecuteBootstrap: execute bootstrap process [bootstrap_ID9391450]
[Thr 2144] INFO: Invalid property value [JLaunchParameters/]
[Thr 2144] [Node: server0 bootstrap] java home is set by profile parameter
     Java Home: c:\j2sdk1.4.2_08
JStartupIReadSection: read node properties [bootstrap_ID9391450]
-> node name       : server0 bootstrap
-> node type       : bootstrap
-> java path       : c:\j2sdk1.4.2_08
-> java parameters : -Djco.jarm=1 -Djco.jarm=1
-> java vm version : 1.4.2_08-b03
-> java vm vendor : Java HotSpot(TM) Server VM (Sun Microsystems Inc.)
-> java vm type    : server
-> java vm cpu     : x86
-> heap size       : 1024M
-> root path       : E:\usr\sap\D01\JC00\j2ee\cluster
-> class path      : .\bootstrap\launcher.jar
-> OS libs path    : E:\usr\sap\D01\JC00\j2ee\os_libs
-> main class      : com.sap.engine.offline.OfflineToolStart
-> framework class : com.sap.bc.proj.jstartup.JStartupFramework
-> registr. class : com.sap.bc.proj.jstartup.JStartupNatives
-> framework path : E:\usr\sap\D01\JC00\j2ee\os_libs\jstartup.jar
-> parameters      : com.sap.engine.bootstrap.Bootstrap ./bootstrap ID009391450
-> debuggable      : yes
-> debug mode      : no
-> debug port      : 60000
-> shutdown timeout: 120000
JStartupStartJLaunch: program = E:\usr\sap\D01\JC00/j2ee/os_libs/jlaunch.exe
-> arg[00] = E:\usr\sap\D01\JC00/j2ee/os_libs/jlaunch.exe
-> arg[01] = pf=E:\usr\sap\D01\SYS\profile\D01_JC00_portald
-> arg[02] = -DSAPINFO=D01_00_bootstrap
-> arg[03] = -file=E:\usr\sap\D01\JC00\j2ee\cluster\instance.properties
-> arg[04] = -nodeName=bootstrap_ID9391450
-> arg[05] = -nodeId=-1
-> arg[06] = -syncSem=JSTARTUP_WAIT_ON_5552
-> arg[07] = -jvmOutFile=E:\usr\sap\D01\JC00\work\jvm_bootstrap_ID9391450.out
-> arg[08] = -stdOutFile=E:\usr\sap\D01\JC00\work\std_bootstrap_ID9391450.out
-> arg[09] = -locOutFile=E:\usr\sap\D01\JC00\work\dev_bootstrap_ID9391450
-> arg[10] = -mode=BOOTSTRAP
-> arg[11] = pf=E:\usr\sap\D01\SYS\profile\D01_JC00_portald
-> lib path = PATH=c:\j2sdk1.4.2_08\jre\bin\server;c:\j2sdk1.4.2_08\jre\bin;D:\oracle\D01\920\jre\1.4.2\bin\client;D:\oracle\D01\920\jre\1.4.2\bin;D:\oracle\D01\920\bin;C:\Program Files\Oracle\jre\1.3.1\bin;C:\Program Files\Oracle\jre\1.1.8\bin;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;c:\j2sdk1.4.2_08\bin;E:\usr\sap\D01\SCS01\exe;E:\usr\sap\D01\JC00\exe;E:\usr\sap\D01\SYS\exe\run
-> exe path = PATH=c:\j2sdk1.4.2_08\bin;E:\usr\sap\D01\JC00\j2ee\os_libs;D:\oracle\D01\920\jre\1.4.2\bin\client;D:\oracle\D01\920\jre\1.4.2\bin;D:\oracle\D01\920\bin;C:\Program Files\Oracle\jre\1.3.1\bin;C:\Program Files\Oracle\jre\1.1.8\bin;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;c:\j2sdk1.4.2_08\bin;E:\usr\sap\D01\SCS01\exe;E:\usr\sap\D01\JC00\exe;E:\usr\sap\D01\SYS\exe\run
[Thr 2144] Mon Dec 19 11:15:05 2005
[Thr 2144] JControlIBuildProcessList: Maximum error count is set to 4
[Thr 1424] JControlRequestFunc: Thread 1424 started as listener thread for np messages.
[Thr 2144] INFO: Invalid property value [JLaunchParameters/]
[Thr 2144] [Node: dispatcher] java home is set by profile parameter
     Java Home: c:\j2sdk1.4.2_08
JStartupIReadSection: read node properties [ID9391400]
-> node name       : dispatcher
-> node type       : dispatcher
-> java path       : c:\j2sdk1.4.2_08
-> java parameters : -Djava.security.policy=./java.policy -Djava.security.egd=file:/dev/urandom -Djco.jarm=1 -XX:NewSize=28m -XX:MaxNewSize=28m -XX:+DisableExplicitGC -Drdbms.driverLocation=D:/oracle/D01/920/jdbc/lib/classes12.jar -Dsys.global.dir=E:/usr/sap/D01/SYS/global/
-> java vm version : 1.4.2_08-b03
-> java vm vendor : Java HotSpot(TM) Server VM (Sun Microsystems Inc.)
-> java vm type    : server
-> java vm cpu     : x86
-> heap size       : 170M
-> root path       : E:\usr\sap\D01\JC00\j2ee\cluster\dispatcher
-> class path      : .\bin\boot\boot.jar;.\bin\system\bytecode.jar;.
-> OS libs path    : E:\usr\sap\D01\JC00\j2ee\os_libs
-> main class      : com.sap.engine.boot.Start
-> framework class : com.sap.bc.proj.jstartup.JStartupFramework
-> registr. class : com.sap.bc.proj.jstartup.JStartupNatives
-> framework path : E:\usr\sap\D01\JC00\j2ee\os_libs\jstartup.jar
-> parameters      :
-> debuggable      : no
-> debug mode      : no
-> debug port      : 60000
-> shutdown timeout: 120000
[Thr 2144] INFO: Invalid property value [JLaunchParameters/]
[Thr 2144] *** WARNING => Maximum Java heap size specified twice (through maxHeapSize and in javaParameters) - using -Xmx512M [jstartxx.c   2282]
[Thr 2144] [Node: server0] java home is set by profile parameter
     Java Home: c:\j2sdk1.4.2_08
JStartupIReadSection: read node properties [ID9391450]
-> node name       : server0
-> node type       : server
-> java path       : c:\j2sdk1.4.2_08
-> java parameters : -Djava.security.policy=./java.policy -Djava.security.egd=file:/dev/urandom -Dorg.omg.CORBA.ORBClass=com.sap.engine.system.ORBProxy -Dorg.omg.CORBA.ORBSingletonClass=com.sap.engine.system.ORBSingletonProxy -Djavax.rmi.CORBA.PortableRemoteObjectClass=com.sap.engine.system.PortableRemoteObjectProxy -Djco.jarm=1 -Dsun.io.useCanonCaches=false -Djava.awt.headless=true -XX:SoftRefLRUPolicyMSPerMB=1 -verbose:gc -XX:PrintGCDetails -XX:PrintGCTimeStamps -XX:UseParNewGC -XX:MaxNewSize=85M -XX:NewSize=85M -XX:DisableExplicitGC -XX:MaxPermSize=192M -XX:PermSize=192M -XX:SurvivorRatio=2 -XX:TargetSurvivorRatio=90 -Drdbms.driverLocation=D:/oracle/D01/920/jdbc/lib/classes12.jar -Dsys.global.dir=E:/usr/sap/D01/SYS/global/
-> java vm version : 1.4.2_08-b03
-> java vm vendor : Java HotSpot(TM) Server VM (Sun Microsystems Inc.)
-> java vm type    : server
-> java vm cpu     : x86
-> heap size       : 512M
-> init heap size : 512M
-> root path       : E:\usr\sap\D01\JC00\j2ee\cluster\server0
-> class path      : .\bin\boot\boot.jar;.\bin\boot\jaas.jar;.\bin\system\bytecode.jar;.
-> OS libs path    : E:\usr\sap\D01\JC00\j2ee\os_libs
-> main class      : com.sap.engine.boot.Start
-> framework class : com.sap.bc.proj.jstartup.JStartupFramework
-> registr. class : com.sap.bc.proj.jstartup.JStartupNatives
-> framework path : E:\usr\sap\D01\JC00\j2ee\os_libs\jstartup.jar
-> parameters      :
-> debuggable      : no
-> debug mode      : no
-> debug port      : 50021
-> shutdown timeout: 120000
[Thr 2144] [Node: SDM] java home is set by profile parameter
     Java Home: c:\j2sdk1.4.2_08
JStartupIReadSection: read node properties [sdm]
-> node name       : SDM
-> node type       : sdm
-> java path       : c:\j2sdk1.4.2_08
-> java parameters :
-> java vm version : 1.4.2_08-b03
-> java vm vendor : Java HotSpot(TM) Server VM (Sun Microsystems Inc.)
-> java vm type    : server
-> java vm cpu     : x86
-> heap size       : 128M
-> root path       : E:\usr\sap\D01\JC00\SDM\program
-> class path      : E:\usr\sap\D01\JC00\SDM\program\bin\SDM.jar
-> OS libs path    : E:\usr\sap\D01\JC00\j2ee\os_libs
-> main class      : SDMInternal
-> framework class : com.sap.bc.proj.jstartup.JStartupFramework
-> registr. class : com.sap.bc.proj.jstartup.JStartupNatives
-> framework path : E:\usr\sap\D01\JC00\j2ee\os_libs\jstartup.jar
-> shutdown class : com.sap.sdm.jstartup.shutdown.InternalShutDown
-> parameters      : server sdmhome=E:\usr\sap/D01/JC00/SDM/program
-> debuggable      : yes
-> debug mode      : no
-> debug port      : 60000
-> shutdown timeout: 120000
[Thr 2144] JControlMSConnect: attached to message server (portald/3601)
[Thr 892] JControlMSMessageFunc: Thread 892 started as listener thread for ms messages.
JStartupStartJLaunch: program = E:\usr\sap\D01\JC00/j2ee/os_libs/jlaunch.exe
-> arg[00] = E:\usr\sap\D01\JC00/j2ee/os_libs/jlaunch.exe
-> arg[01] = pf=E:\usr\sap\D01\SYS\profile\D01_JC00_portald
-> arg[02] = -DSAPINFO=D01_00_dispatcher
-> arg[03] = -file=E:\usr\sap\D01\JC00\j2ee\cluster\instance.properties
-> arg[04] = -nodeName=ID9391400
-> arg[05] = -nodeId=0
-> arg[06] = -syncSem=JSTARTUP_WAIT_ON_5552
-> arg[07] = -jvmOutFile=E:\usr\sap\D01\JC00\work\jvm_dispatcher.out
-> arg[08] = -stdOutFile=E:\usr\sap\D01\JC00\work\std_dispatcher.out
-> arg[09] = -locOutFile=E:\usr\sap\D01\JC00\work\dev_dispatcher
-> arg[10] = -mode=JCONTROL
-> arg[11] = pf=E:\usr\sap\D01\SYS\profile\D01_JC00_portald
-> lib path = PATH=c:\j2sdk1.4.2_08\jre\bin\server;c:\j2sdk1.4.2_08\jre\bin;D:\oracle\D01\920\jre\1.4.2\bin\client;D:\oracle\D01\920\jre\1.4.2\bin;D:\oracle\D01\920\bin;C:\Program Files\Oracle\jre\1.3.1\bin;C:\Program Files\Oracle\jre\1.1.8\bin;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;c:\j2sdk1.4.2_08\bin;E:\usr\sap\D01\SCS01\exe;E:\usr\sap\D01\JC00\exe;E:\usr\sap\D01\SYS\exe\run
-> exe path = PATH=c:\j2sdk1.4.2_08\bin;E:\usr\sap\D01\JC00\j2ee\os_libs;D:\oracle\D01\920\jre\1.4.2\bin\client;D:\oracle\D01\920\jre\1.4.2\bin;D:\oracle\D01\920\bin;C:\Program Files\Oracle\jre\1.3.1\bin;C:\Program Files\Oracle\jre\1.1.8\bin;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;c:\j2sdk1.4.2_08\bin;E:\usr\sap\D01\SCS01\exe;E:\usr\sap\D01\JC00\exe;E:\usr\sap\D01\SYS\exe\run
[Thr 2144] JControlICheckProcessList: process dispatcher started (PID:1432)
JStartupStartJLaunch: program = E:\usr\sap\D01\JC00/j2ee/os_libs/jlaunch.exe
-> arg[00] = E:\usr\sap\D01\JC00/j2ee/os_libs/jlaunch.exe
-> arg[01] = pf=E:\usr\sap\D01\SYS\profile\D01_JC00_portald
-> arg[02] = -DSAPINFO=D01_00_server
-> arg[03] = -file=E:\usr\sap\D01\JC00\j2ee\cluster\instance.properties
-> arg[04] = -nodeName=ID9391450
-> arg[05] = -nodeId=1
-> arg[06] = -syncSem=JSTARTUP_WAIT_ON_5552
-> arg[07] = -jvmOutFile=E:\usr\sap\D01\JC00\work\jvm_server0.out
-> arg[08] = -stdOutFile=E:\usr\sap\D01\JC00\work\std_server0.out
-> arg[09] = -locOutFile=E:\usr\sap\D01\JC00\work\dev_server0
-> arg[10] = -mode=JCONTROL
-> arg[11] = pf=E:\usr\sap\D01\SYS\profile\D01_JC00_portald
-> lib path = PATH=c:\j2sdk1.4.2_08\jre\bin\server;c:\j2sdk1.4.2_08\jre\bin;D:\oracle\D01\920\jre\1.4.2\bin\client;D:\oracle\D01\920\jre\1.4.2\bin;D:\oracle\D01\920\bin;C:\Program Files\Oracle\jre\1.3.1\bin;C:\Program Files\Oracle\jre\1.1.8\bin;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;c:\j2sdk1.4.2_08\bin;E:\usr\sap\D01\SCS01\exe;E:\usr\sap\D01\JC00\exe;E:\usr\sap\D01\SYS\exe\run
-> exe path = PATH=c:\j2sdk1.4.2_08\bin;E:\usr\sap\D01\JC00\j2ee\os_libs;D:\oracle\D01\920\jre\1.4.2\bin\client;D:\oracle\D01\920\jre\1.4.2\bin;D:\oracle\D01\920\bin;C:\Program Files\Oracle\jre\1.3.1\bin;C:\Program Files\Oracle\jre\1.1.8\bin;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;c:\j2sdk1.4.2_08\bin;E:\usr\sap\D01\SCS01\exe;E:\usr\sap\D01\JC00\exe;E:\usr\sap\D01\SYS\exe\run
[Thr 2144] JControlICheckProcessList: process server0 started (PID:1436)
JStartupStartJLaunch: program = E:\usr\sap\D01\JC00/j2ee/os_libs/jlaunch.exe
-> arg[00] = E:\usr\sap\D01\JC00/j2ee/os_libs/jlaunch.exe
-> arg[01] = pf=E:\usr\sap\D01\SYS\profile\D01_JC00_portald
-> arg[02] = -DSAPINFO=D01_00_sdm
-> arg[03] = -file=E:\usr\sap\D01\JC00\SDM\program\config\sdm_jstartup.properties
-> arg[04] = -nodeName=sdm
-> arg[05] = -nodeId=2
-> arg[06] = -syncSem=JSTARTUP_WAIT_ON_5552
-> arg[07] = -jvmOutFile=E:\usr\sap\D01\JC00\work\jvm_sdm.out
-> arg[08] = -stdOutFile=E:\usr\sap\D01\JC00\work\std_sdm.out
-> arg[09] = -locOutFile=E:\usr\sap\D01\JC00\work\dev_sdm
-> arg[10] = -mode=JCONTROL
-> arg[11] = pf=E:\usr\sap\D01\SYS\profile\D01_JC00_portald
-> lib path = PATH=c:\j2sdk1.4.2_08\jre\bin\server;c:\j2sdk1.4.2_08\jre\bin;D:\oracle\D01\920\jre\1.4.2\bin\client;D:\oracle\D01\920\jre\1.4.2\bin;D:\oracle\D01\920\bin;C:\Program Files\Oracle\jre\1.3.1\bin;C:\Program Files\Oracle\jre\1.1.8\bin;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;c:\j2sdk1.4.2_08\bin;E:\usr\sap\D01\SCS01\exe;E:\usr\sap\D01\JC00\exe;E:\usr\sap\D01\SYS\exe\run
-> exe path = PATH=c:\j2sdk1.4.2_08\bin;E:\usr\sap\D01\JC00\j2ee\os_libs;D:\oracle\D01\920\jre\1.4.2\bin\client;D:\oracle\D01\920\jre\1.4.2\bin;D:\oracle\D01\920\bin;C:\Program Files\Oracle\jre\1.3.1\bin;C:\Program Files\Oracle\jre\1.1.8\bin;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;c:\j2sdk1.4.2_08\bin;E:\usr\sap\D01\SCS01\exe;E:\usr\sap\D01\JC00\exe;E:\usr\sap\D01\SYS\exe\run
[Thr 2144] JControlICheckProcessList: process SDM started (PID:1452)
[Thr 892] Mon Dec 19 11:15:35 2005
[Thr 892] JControlMSMessageFunc: receive command:6, argument:1213679940 from Message Server
[Thr 892] JControlMSMessageFunc: receive command:6, argument:1213679940 from Message Server
[Thr 892] JControlMSMessageFunc: receive command:6, argument:1213679940 from Message Server
[Thr 892] JControlMSMessageFunc: receive command:6, argument:1213679940 from Message Server
[Thr 892] JControlMSMessageFunc: receive command:6, argument:1213679940 from Message Server
[Thr 892] JControlMSMessageFunc: receive command:6, argument:1213679940 from Message Server
[Thr 892] JControlMSMessageFunc: receive command:6, argument:1213679940 from Message Server
[Thr 892] JControlMSMessageFunc: receive command:6, argument:1213679940 from Message Server
[Thr 2144] Mon Dec 19 11:16:00 2005
[Thr 2144] JControlICheckProcessList: process server0 (pid:1436) died (RUN-FLAG)
[Thr 2144] JControlIResetProcess: reset process server0
[Thr 2144] JControlIResetProcess: [server0] not running -> increase error count (1)
JStartupStartJLaunch: program = E:\usr\sap\D01\JC00/j2ee/os_libs/jlaunch.exe
-> arg[00] = E:\usr\sap\D01\JC00/j2ee/os_libs/jlaunch.exe
-> arg[01] = pf=E:\usr\sap\D01\SYS\profile\D01_JC00_portald
-> arg[02] = -DSAPINFO=D01_00_server
-> arg[03] = -file=E:\usr\sap\D01\JC00\j2ee\cluster\instance.properties
-> arg[04] = -nodeName=ID9391450
-> arg[05] = -nodeId=1
-> arg[06] = -syncSem=JSTARTUP_WAIT_ON_5552
-> arg[07] = -jvmOutFile=E:\usr\sap\D01\JC00\work\jvm_server0.out
-> arg[08] = -jvmOutMode=append
-> arg[09] = -stdOutFile=E:\usr\sap\D01\JC00\work\std_server0.out
-> arg[10] = -stdOutMode=append
-> arg[11] = -traceMode=append
-> arg[12] = -locOutFile=E:\usr\sap\D01\JC00\work\dev_server0
-> arg[13] = -mode=JCONTROL
-> arg[14] = pf=E:\usr\sap\D01\SYS\profile\D01_JC00_portald
-> lib path = PATH=c:\j2sdk1.4.2_08\jre\bin\server;c:\j2sdk1.4.2_08\jre\bin;D:\oracle\D01\920\jre\1.4.2\bin\client;D:\oracle\D01\920\jre\1.4.2\bin;D:\oracle\D01\920\bin;C:\Program Files\Oracle\jre\1.3.1\bin;C:\Program Files\Oracle\jre\1.1.8\bin;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;c:\j2sdk1.4.2_08\bin;E:\usr\sap\D01\SCS01\exe;E:\usr\sap\D01\JC00\exe;E:\usr\sap\D01\SYS\exe\run
-> exe path = PATH=c:\j2sdk1.4.2_08\bin;E:\usr\sap\D01\JC00\j2ee\os_libs;D:\oracle\D01\920\jre\1.4.2\bin\client;D:\oracle\D01\920\jre\1.4.2\bin;D:\oracle\D01\920\bin;C:\Program Files\Oracle\jre\1.3.1\bin;C:\Program Files\Oracle\jre\1.1.8\bin;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;c:\j2sdk1.4.2_08\bin;E:\usr\sap\D01\SCS01\exe;E:\usr\sap\D01\JC00\exe;E:\usr\sap\D01\SYS\exe\run
[Thr 2144] JControlICheckProcessList: process server0 started (PID:4092)
[Thr 2144] Mon Dec 19 11:16:40 2005
[Thr 2144] JControlICheckProcessList: process server0 (pid:4092) died (RUN-FLAG)
[Thr 2144] JControlIResetProcess: reset process server0
[Thr 2144] JControlIResetProcess: [server0] not running -> increase error count (2)
JStartupStartJLaunch: program = E:\usr\sap\D01\JC00/j2ee/os_libs/jlaunch.exe
-> arg[00] = E:\usr\sap\D01\JC00/j2ee/os_libs/jlaunch.exe
-> arg[01] = pf=E:\usr\sap\D01\SYS\profile\D01_JC00_portald
-> arg[02] = -DSAPINFO=D01_00_server
-> arg[03] = -file=E:\usr\sap\D01\JC00\j2ee\cluster\instance.properties
-> arg[04] = -nodeName=ID9391450
-> arg[05] = -nodeId=1
-> arg[06] = -syncSem=JSTARTUP_WAIT_ON_5552
-> arg[07] = -jvmOutFile=E:\usr\sap\D01\JC00\work\jvm_server0.out
-> arg[08] = -jvmOutMode=append
-> arg[09] = -stdOutFile=E:\usr\sap\D01\JC00\work\std_server0.out
-> arg[10] = -stdOutMode=append
-> arg[11] = -traceMode=append
-> arg[12] = -locOutFile=E:\usr\sap\D01\JC00\work\dev_server0
-> arg[13] = -mode=JCONTROL
-> arg[14] = pf=E:\usr\sap\D01\SYS\profile\D01_JC00_portald
-> lib path = PATH=c:\j2sdk1.4.2_08\jre\bin\server;c:\j2sdk1.4.2_08\jre\bin;D:\oracle\D01\920\jre\1.4.2\bin\client;D:\oracle\D01\920\jre\1.4.2\bin;D:\oracle\D01\920\bin;C:\Program Files\Oracle\jre\1.3.1\bin;C:\Program Files\Oracle\jre\1.1.8\bin;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;c:\j2sdk1.4.2_08\bin;E:\usr\sap\D01\SCS01\exe;E:\usr\sap\D01\JC00\exe;E:\usr\sap\D01\SYS\exe\run
-> exe path = PATH=c:\j2sdk1.4.2_08\bin;E:\usr\sap\D01\JC00\j2ee\os_libs;D:\oracle\D01\920\jre\1.4.2\bin\client;D:\oracle\D01\920\jre\1.4.2\bin;D:\oracle\D01\920\bin;C:\Program Files\Oracle\jre\1.3.1\bin;C:\Program Files\Oracle\jre\1.1.8\bin;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;c:\j2sdk1.4.2_08\bin;E:\usr\sap\D01\SCS01\exe;E:\usr\sap\D01\JC00\exe;E:\usr\sap\D01\SYS\exe\run
[Thr 2144] JControlICheckProcessList: process server0 started (PID:5456)
[Thr 2144] Mon Dec 19 11:17:25 2005
[Thr 2144] JControlICheckProcessList: process server0 (pid:5456) died (RUN-FLAG)
[Thr 2144] JControlIResetProcess: reset process server0
[Thr 2144] JControlIResetProcess: [server0] not running -> increase error count (3)
JStartupStartJLaunch: program = E:\usr\sap\D01\JC00/j2ee/os_libs/jlaunch.exe
-> arg[00] = E:\usr\sap\D01\JC00/j2ee/os_libs/jlaunch.exe
-> arg[01] = pf=E:\usr\sap\D01\SYS\profile\D01_JC00_portald
-> arg[02] = -DSAPINFO=D01_00_server
-> arg[03] = -file=E:\usr\sap\D01\JC00\j2ee\cluster\instance.properties
-> arg[04] = -nodeName=ID9391450
-> arg[05] = -nodeId=1
-> arg[06] = -syncSem=JSTARTUP_WAIT_ON_5552
-> arg[07] = -jvmOutFile=E:\usr\sap\D01\JC00\work\jvm_server0.out
-> arg[08] = -jvmOutMode=append
-> arg[09] = -stdOutFile=E:\usr\sap\D01\JC00\work\std_server0.out
-> arg[10] = -stdOutMode=append
-> arg[11] = -traceMode=append
-> arg[12] = -locOutFile=E:\usr\sap\D01\JC00\work\dev_server0
-> arg[13] = -mode=JCONTROL
-> arg[14] = pf=E:\usr\sap\D01\SYS\profile\D01_JC00_portald
-> lib path = PATH=c:\j2sdk1.4.2_08\jre\bin\server;c:\j2sdk1.4.2_08\jre\bin;D:\oracle\D01\920\jre\1.4.2\bin\client;D:\oracle\D01\920\jre\1.4.2\bin;D:\oracle\D01\920\bin;C:\Program Files\Oracle\jre\1.3.1\bin;C:\Program Files\Oracle\jre\1.1.8\bin;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;c:\j2sdk1.4.2_08\bin;E:\usr\sap\D01\SCS01\exe;E:\usr\sap\D01\JC00\exe;E:\usr\sap\D01\SYS\exe\run
-> exe path = PATH=c:\j2sdk1.4.2_08\bin;E:\usr\sap\D01\JC00\j2ee\os_libs;D:\oracle\D01\920\jre\1.4.2\bin\client;D:\oracle\D01\920\jre\1.4.2\bin;D:\oracle\D01\920\bin;C:\Program Files\Oracle\jre\1.3.1\bin;C:\Program Files\Oracle\jre\1.1.8\bin;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;c:\j2sdk1.4.2_08\bin;E:\usr\sap\D01\SCS01\exe;E:\usr\sap\D01\JC00\exe;E:\usr\sap\D01\SYS\exe\run
[Thr 2144] JControlICheckProcessList: process server0 started (PID:4948)
[Thr 2144] Mon Dec 19 11:18:10 2005
[Thr 2144] JControlICheckProcessList: process server0 (pid:4948) died (RUN-FLAG)
[Thr 2144] JControlIResetProcess: reset process server0
[Thr 2144] JControlIResetProcess: [server0] not running -> increase error count (4)

Dear Ashutosh,
Thanks for guiding us to correct location.
What we identified is we connected portal to the LDAP
of EP 5.0 while migrating the content.After migration we
have formatted the 5.0 system.
Now that portal is connected to that LDAP which is
not existing the problem is coming.
Is there any way through CONFIGURATION tool I can remove
that connectivity to LDAP?
I am trying to configure LDAP again on the same server
but before to that if some one can hint me how to
remove the LDAP configuration from the Portal I would
be very much thankful..
regards
Mrutyunjay

Aperture: After changed the file name in Finder Aperture can't load the referenced file anymore

After I've changed the file name/format in Finder Aperture can't load/relink to the referenced file anymore. For some reasons I don't like to reimport the file.

As you told, the command "Locate Referenced File" doesn't work, if the filename doen't match exactly. And the filenames should keep their new names.
"Locate Referenced File" will be able to reconnect one file at a time, if you direct Aperture to the matching file in the Loate Referenced File dialog, but it will not be able to recognise the other matching referenced files and to reconnect them all at once with the "Reconnect All" button.
It will be a lot of work to reconnect the one by one. Usually it is much easier to rename the original master files using Metadata > Batch change in Aperture than to try to do that in the Finder.

OEM is not getting started after changing the Server name

Similar Messages

Maybe you are looking for