Sap not starting during manual failover testing

Dera friends,
We are performing manual failover testing between CI(sap central instance) and DB(oracle database)
the environment is ECC6.0 on AIX server
CI is running on one server and DB is running on another, during manual testing we have failed the DB, so now DB file systems has got mounted on CI server.
So when i log into CI with user as shown below (sid-irp)
su - irpadm
and the execute the command as shown below
irpadm 6> startsap
i get the following message
PRDCIXI:irpadm 6> startsap
tee: 0652-044 Cannot open /home/irpadm/startsap_.log.
Checking IRP Database
tee: 0652-044 Cannot open /home/irpadm/startsap_.log.
tee: 0652-044 Cannot open /home/irpadm/startsap_.log.
ABAP Database is not available via R3trans
tee: 0652-044 Cannot open /home/irpadm/startsap_.log.
Starting SAP-Collector Daemon
tee: 0652-044 Cannot open /home/irpadm/startsap_.log.
15:03:05 26.09.2008   LOG: Effective User Id is root
This is Saposcol Version COLL 20.94 700 - AIX v10.35 5L-64 bit 070123
Usage: saposcol -l: Start OS Collector
        saposcol -k: Stop OS Collector
        saposcol -d: OS Collector Dialog Mode
        saposcol -s: OS Collector Status
The OS Collector (PID 1101932) is already running .....
tee: 0652-044 Cannot open /home/irpadm/startsap_.log.
saposcol already running
tee: 0652-044 Cannot open /home/irpadm/startsap_.log.
ABAP Database IRP must be started on remote server
===============================================
why am i getting this "ABAP Database IRP must be started on remote server" message.
What could be the cause for my database not comming up & why is it looking for remote server, when all the DB filesystems have got mounted on CI server (the server that has CI installed)
We are in a bad shape and the issue is quite crticial.
Your reply would be highly appreciated.
Regards
Ayush

> how can i check wether the directories are missing or not...
mount?
> Also how can i check it wether they are assigned to failover group or not.
Ayush, no offense, but I suggest you contact your AIX guy and check with him together. It's very cumbersome to write down command by command, get the outpu t back and you have no clue what you are doing. Again, no offense.
Markus

Similar Messages

Dispacher and server0 is not started during NW2004s installation

Hi,
Dispacher and server0 is not started during NW2004s installation. SAPInst is stopped on the step of the 'Start java instance'. SDM is 'running' but dispacher and server0 is 'Starting framwork'. So I configured the some parameters via configtool but I can't solve this probelm. I found the some error logs as the followings.
(22503) Starting local Command:
Command: en.sapMPP_SCS33 pf=/usr/sap/MPP/SYS/profile/MPP_SCS33_spdeai01
listen failed on port/service sapdp33
initialize_global: another instance of the enque server seems to be running. EXIT
***LOG Q01=> MsSInit, MSStart (Msg Server 1 22502) [msxxserv_mt. 1818]
[Thr 1] SigISetDefaultAction : default handling for signal 18
[Thr 1] load acl file = /usr/sap/MPP/SYS/global/ms_acl_info
[Thr 1] MsGetOwnIpAddr: my host addresses are :
[Thr 1]   1 : [10.223.50.15] spdeai01 (HOSTNAME)
[Thr 1]   2 : [127.0.0.1] localhost (LOCALHOST)
[Thr 1]   3 : [10.223.50.215] 10.223.50.215 (NILIST)
[Thr 1]   4 : [10.223.50.115] 10.223.50.115 (NILIST)
[Thr 1] MsHttpInit: full qualified hostname = spdeai01
[Thr 1] HTTP logging is switch off
[Thr 1] set HTTP state to LISTEN
[Thr 1] ms/icf_info_server : deleted
[Thr 1] *** I listen to internal port 3933 (3933) ***
[Thr 1] *** HTTP port 8133 state LISTEN ***
[Thr 1] CUSTOMER KEY: >Q0820898445<
[Thr 1] Wed Oct 24 18:28:11 2007
[Thr 1] MsJ2EE_AddLoggedInNode: add node [305110500] into logged in list
[Thr 1] Wed Oct 24 18:28:21 2007
[Thr 1] MsJ2EE_AddLoggedInNode: add node [305110550] into logged in list
Our JDK version is '1.4.2_11' and We are installing on the HA environment.
How can I solve this problem? or What should I check about it?
Best Regards,
David.

Check if the Database serivice is up and running. If this is not so.. you might have to start all over again..!!
VJ

J2EE Does Not Start During JAVA Add-In Installation

I'm installing Java Add-In onto ERP 2004 (Windows 2000, Oracle 9.2, Java 2 SDK 1.4.2_08).
The J2EE does not start during the installation. It gives up after some time. java -version shows the correct path.
dev_jcontrol shows the following:
[Thr 2624] Tue Aug 02 09:49:32 2005
[Thr 2624] JControlExecuteBootstrap: execute bootstrap process [bootstrap]
[Thr 2624] [Node: bootstrap] java home is set by profile parameter
Java Home: C:\j2sdk1.4.2_08
[Thr 2624] *** ERROR => JStartupIGetJDKInfo: Cannot find Java class file [./JdkDetection_3516.class]. [jstartxxi.c 899]
[Thr 2624] *** ERROR => can't get JDK information (rc=-1) [jstartxxi.c 1096]
[Thr 2624] *** ERROR => node [bootstrap] not found [jstartxx.c 1388]
[Thr 2624] JControlExecuteBootstrap: error executing bootstrap node [bootstrap] (rc=-18)
[Thr 2624] JControlCloseProgram: started (exitcode = -18)
[Thr 2624] JControlCloseProgram: good bye... (exitcode=-18)

In that case, do u have multiple versions of JDKs installed ?
Maybe some earlier version is installed too ! In that case there is a program that comes along with the JDK to choose the version of the JDK that needs to be loaded into memory.
We faced this problem when we were doing our stints with JAVA Add-In wherein the system required the newest version of java where as some tool which was installed on the system required the older version.
So we used the java program to select the version to be loaded whenever the operating system tried loading the jdk.

J2EE server does not start during installation

Hi,
I am installing WebAS JAVA 640 (NW04 SR1) on a Windows 2003/MSSQL server. I am using JAVA SDK 1.4.2_9. The installation stops at step 24/25 whereby the installer waits for the J2EE engine to start. After making 3 attempts to start the J2EE server, the installation process just hangs and I have to Cancel the installation.
BTW, I am specifying a heap size of 1024 MB and using the "Database Only" option as UME data store during installation.
Having checked the trace and log files, it seems the UME service fails to start, throws an exception and the message "the start of a core service failed, Web AS will not start".
According to the information available <a href="http://help.sap.com/saphelp_nw2004s/helpdata/en/20/361941edd5ef23e10000000a155106/content.htm">here</a>, I have checked the settings and it seems that option 2, <b>"User or group data is missing"</b> is causing the problem since database content of UME is missing. I have tried selecting entries from table UME_STRINGS but this table is empty.
Now, the same link says that I should login to UME web application as SAP* but the problem is that without the J2EE engine starting up, I cannot login and create missing users/groups.
Any ideas???
Regards
Shehryar

Thanks to all who replied. I have actually tried all options suggested like waiting for retries until the box appears, trying to manually start the server, and reducing heap size. None worked for me. For your information, I have a 2.4 GHz machine with 4GB RAM so I think heap size should not be an issue. I checked SAP Note regarding heap size issues in Win 2003 but that does not seem to apply in my case since my system does not behave abnormally with JVM settings.
Thanks again and I'll give it another shot.
Regards
Shehryar

MSCS for ECC 6.00 - Service settings, SAP not starting reliably

I have an ECC 6.00 installation on Windows 2008/SQL*Server in an MSCS environment that I'm trying to validate. (I didn't
install it so I don't know what was down as part of the install, and what was done after.)
On Node 1 currently, the SAP MMC shows FIVE instances running:
- PSAPERPPROD1 (02) - Local Central Instance
- PSAPERPPROD1 (10) - EnqueueReplicationServer
- PSAPERPPROD1 (11) - EnqueueReplicationServer
- SAPECCPRD (00) - ASCS
- SAPECCPRD (01) - ASCS
On Node 2 I see the following:
- PSAPERPPROD2 (02) - Local Dialog Instance
- PSAPERPPROD2 (10) - EnqueueReplicationServer
- PSAPERPPROD2 (11) - EnqueueReplicationServer
PSAPERPPROD1 and PSAPERPPROD2 are the physical names of Node 1 and 2 while the SAPECCPRD name is the logical name of the SAP
Cluster Service. Users signon to SAPGui using SAPECCPRD(02)
If I look in the Services Manager of both Node 1 and 2 I see that the SAPMEP_xx services are set as follows:
- SAPMEP_02 - Manual
- SAPMEP_10 - Automatic
- SAPMEP_11 - Automatic
What I'm experiencing is that if the three cluster services ("SAP MEP", "SAP_ERPDtc", and "SQL Server (MSSQLSERVER)") are all
running on Node 1, and Node 2 is rebooted, when Node 2 restarts, and I go into the Failover Cluster Manager and move the
resources from Node 1 to Node 2 (without signing onto Node 2), the SAP system does not start as the 02 instance on Node 2
hasn't started yet. IF I go into Node 2 and open the SAP MMC then the 02 instance will start and then the failover to
Node 2 will work correctly and the SAP system starts. If I don't go into the MMC first, then the 02 instance is down and
while the cluster appears to be started correctly you cannot sign onto SAP as there is no CI or Dialog instance running.
My questions are as follows:
1) Is this setup right? - something seems wrong, as I have to start the MMC before things work correctly
2) Should the 02 instances be set to automatic? - what other implications would this have in the case that this service
starts without the database started on the cluster.
3) Should the 02 instance somehow be added to the Cluster Service.
Comments would be appreciated.

Be sure that you have the "TSW Active" flag set in IMG node:
Industry Solutions Oil & Gas (Downstream)
>TSW (Trader's and Scheduler's Workbench
>Basic Functions
>Specify TSW Control Parameters

Application does not start during the engine restart.

Hello all,
after deploying a custom developed application to the engine the application works fine. However, when the J2EE is restarted the application page is not available with the following message:
Application error occurred during request processing. Details:Error
[javax.servlet.ServletException: Spo object was not created during the
startup], with root cause [com.appname.exception.SevereException:
Spo object was not created during the startup].
Exception id: [0013729689A200590000009D00000D90000446937D1802B7]
The application is shown running from visual administrator.
The application page is again available when we restart the application
manually from visual admin.
SO everytime we restart the engine we need to restart the application
too in order to get back the application page back.
There are many errors in the SPO log like the following:
ERROR [SAPEngine_Application_Thread[impl:3]_25] - Failed to set up connection pool: com.sap.engine.services.jndi.persistent.exceptions.NameNotFoundException: Path to object does not exist at java:comp, the whole lookup name is java:comp/env/jdbc/qaht6114.
Can anyone please advice us on what could be the problem here?
Thanks a lot in advance!
Edited by: Rodrigo Castilhos on Mar 21, 2008 6:21 PM
Edited by: Rodrigo Castilhos on Mar 25, 2008 6:48 PM

Hi Parvez and Ivaylo,
Has any of you used the startup mode setting? I tried using it and set it to always but the application still won't start. Is there anything I'm missing?
My application-j2ee-engine.xml looks like this:
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE application-j2ee-engine SYSTEM "application-j2ee-engine.dtd">
<application-j2ee-engine>
     <provider-name>nexeninc.com</provider-name>
     <fail-over-enable
          mode="disable"/>
     <start-up
          mode="always"/>
</application-j2ee-engine>

SAP not started on CI node thru Cluster Script

Hi
We have installed the PI 7.1 on HP Unix 11v3 and oracle conbination. We have done the cluster package failover
of CI to DB system and done the complete installation on DB with high availability option. Let on we have splited
the CI to CI and keep the DB to DB note. The installation happend successfully and system started successfully on
both node.
Now we are doing the HP-UNIX cluster configuration and integration. But we have found that the DB services are
starting up successfully on DB node but the CI services are not starting up on CI node. The cluster error file
are attached for your reference. Since the project golive is left just 20 day . Request you to provide solution
on the same. Please also let us know if any further log is required.
Regards
Vimal Pathak

Oct 6 16:16:13 root@htlxici: (start_app ciPP9 01 pp9adm): P: Start
Oct 6 16:16:13 root@htlxici: (start_app ciPP9 01 pp9adm): P: FAIL: NIECONN_REFUSED (Connection refused), NiRawConnect failed in plugin_fopen()
Oct 6 16:16:13 root@htlxici sapinstance.sh[29446]: (watchdog): wait for PID 356 returns 0
Oct 6 16:16:13 root@htlxici sapinstance.sh[29446]: (start_app ciPP9 01 pp9adm): Finishing startup attempt
Oct 6 16:16:13 root@htlxici sapinstance.sh[29446]: (wait_pidlist): Killed the wait_pidlist background shell. PID: 29953
Oct 6 16:16:13 root@htlxici sapinstance.sh[29446]: (start_d): Leaving parallel dialog instance startup delay
Oct 6 16:16:13 root@htlxici sapinstance.sh[29446]: (find_sap_binary): found location: "/usr/sap/PP9/DVEBMGS01/exe/sapcontrol" owner: "pp9adm"
Oct 6 16:16:14 root@htlxici sapinstance.sh[29446]: (is_ip_local): ciPP9 is local
Oct 6 16:16:14 root@htlxici sapinstance.sh[29446]: (crit_test_app): Trying to connect local dispatcher of instance DVEBMGS01 ...
Oct 6 16:16:14 root@htlxici sapinstance.sh[29446]: (find_sap_binary): found location: "/usr/sap/PP9/DVEBMGS01/exe/dpmon" owner: "pp9adm"
Oct 6 16:16:16 root@htlxici sapinstance.sh[29446]: (crit_test_app): dpmon: /usr/sap/PP9/DVEBMGS01/exe/dpmon=>sapparam: SAPSYSTEMNAME neither in Profile nor in Commandline
Oct 6 16:16:16 root@htlxici sapinstance.sh[29446]: (crit_test_app): Trying to connect via RFC to host ciPP9 instance DVEBMGS01 ...
Oct 6 16:16:16 root@htlxici sapinstance.sh[29446]: (find_sap_binary): found location: "/usr/sap/PP9/DVEBMGS01/exe/startrfc" owner: "pp9adm"
Oct 6 16:16:16 root@htlxici sapinstance.sh[29446]: (watchdog): Watchdog initiated (PIDs: 1016 for 1015 - Timeout: 100 secs)
Oct 6 16:16:17 root@htlxici sapinstance.sh[29446]: (watchdog): wait for PID 1015 returns 1
Oct 6 16:16:17 root@htlxici sapinstance.sh[29446]: (crit_test_app): No connection to instance DVEBMGS01
Oct 6 16:16:17 root@htlxici sapinstance.sh[29446]: (crit_test_app): Delaying 5 secs to allow instance DVEBMGS01 startup/recover
Oct 6 16:16:22 root@htlxici sapinstance.sh[29446]: (is_ip_local): ciPP9 is local
Oct 6 16:16:22 root@htlxici sapinstance.sh[29446]: (crit_test_app): Trying to connect local dispatcher of instance DVEBMGS01 ...
Oct 6 16:16:22 root@htlxici sapinstance.sh[29446]: (find_sap_binary): found location: "/usr/sap/PP9/DVEBMGS01/exe/dpmon" owner: "pp9adm"
Oct 6 16:16:23 root@htlxici sapinstance.sh[29446]: (crit_test_app): dpmon: /usr/sap/PP9/DVEBMGS01/exe/dpmon=>sapparam: SAPSYSTEMNAME neither in Profile nor in Commandline
Oct 6 16:16:24 root@htlxici sapinstance.sh[29446]: (crit_test_app): Trying to connect via RFC to host ciPP9 instance DVEBMGS01 ...
Oct 6 16:16:24 root@htlxici sapinstance.sh[29446]: (find_sap_binary): found location: "/usr/sap/PP9/DVEBMGS01/exe/startrfc" owner: "pp9adm"
Oct 6 16:16:24 root@htlxici sapinstance.sh[29446]: (watchdog): Watchdog initiated (PIDs: 1466 for 1464 - Timeout: 100 secs)
Oct 6 16:16:25 root@htlxici sapinstance.sh[29446]: (watchdog): wait for PID 1464 returns 1
Oct 6 16:16:25 root@htlxici sapinstance.sh[29446]: (crit_test_app): No connection to instance DVEBMGS01
Oct 6 16:16:25 root@htlxici sapinstance.sh[29446]: (crit_test_app): Delaying 10 secs to allow instance DVEBMGS01 startup/recover
Oct 6 16:16:35 root@htlxici sapinstance.sh[29446]: (is_ip_local): ciPP9 is local
Oct 6 16:16:35 root@htlxici sapinstance.sh[29446]: (crit_test_app): Trying to connect local dispatcher of instance DVEBMGS01 ...
Oct 6 16:16:35 root@htlxici sapinstance.sh[29446]: (find_sap_binary): found location: "/usr/sap/PP9/DVEBMGS01/exe/dpmon" owner: "pp9adm"
Oct 6 16:16:36 root@htlxici sapinstance.sh[29446]: (crit_test_app): dpmon: /usr/sap/PP9/DVEBMGS01/exe/dpmon=>sapparam: SAPSYSTEMNAME neither in Profile nor in Commandline
Oct 6 16:16:36 root@htlxici sapinstance.sh[29446]: (crit_test_app): Trying to connect via RFC to host ciPP9 instance DVEBMGS01 ...
Oct 6 16:16:36 root@htlxici sapinstance.sh[29446]: (find_sap_binary): found location: "/usr/sap/PP9/DVEBMGS01/exe/startrfc" owner: "pp9adm"
Oct 6 16:16:36 root@htlxici sapinstance.sh[29446]: (watchdog): Watchdog initiated (PIDs: 1919 for 1917 - Timeout: 100 secs)
Oct 6 16:16:37 root@htlxici sapinstance.sh[29446]: (watchdog): wait for PID 1917 returns 1
Oct 6 16:16:37 root@htlxici sapinstance.sh[29446]: (crit_test_app): No connection to instance DVEBMGS01
Oct 6 16:16:37 root@htlxici sapinstance.sh[29446]: (crit_test_app): Delaying 15 secs to allow instance DVEBMGS01 startup/recover
Oct 6 16:16:52 root@htlxici sapinstance.sh[29446]: (is_ip_local): ciPP9 is local
Oct 6 16:16:52 root@htlxici sapinstance.sh[29446]: (crit_test_app): Trying to connect local dispatcher of instance DVEBMGS01 ...
Oct 6 16:16:53 root@htlxici sapinstance.sh[29446]: (find_sap_binary): found location: "/usr/sap/PP9/DVEBMGS01/exe/dpmon" owner: "pp9adm"
Oct 6 16:16:54 root@htlxici sapinstance.sh[29446]: (crit_test_app): dpmon: /usr/sap/PP9/DVEBMGS01/exe/dpmon=>sapparam: SAPSYSTEMNAME neither in Profile nor in Commandline
Oct 6 16:16:54 root@htlxici sapinstance.sh[29446]: (crit_test_app): Trying to connect via RFC to host ciPP9 instance DVEBMGS01 ...
Oct 6 16:16:54 root@htlxici sapinstance.sh[29446]: (find_sap_binary): found location: "/usr/sap/PP9/DVEBMGS01/exe/startrfc" owner: "pp9adm"
Oct 6 16:16:54 root@htlxici sapinstance.sh[29446]: (watchdog): Watchdog initiated (PIDs: 2412 for 2410 - Timeout: 100 secs)
Oct 6 16:16:55 root@htlxici sapinstance.sh[29446]: (watchdog): wait for PID 2410 returns 1
Oct 6 16:16:55 root@htlxici sapinstance.sh[29446]: (crit_test_app): No connection to instance DVEBMGS01
Oct 6 16:16:55 root@htlxici sapinstance.sh[29446]: (crit_test_app): Delaying 20 secs to allow instance DVEBMGS01 startup/recover
Oct 6 16:17:15 root@htlxici sapinstance.sh[29446]: (is_ip_local): ciPP9 is local
Oct 6 16:17:15 root@htlxici sapinstance.sh[29446]: (crit_test_app): Trying to connect local dispatcher of instance DVEBMGS01 ...
Oct 6 16:17:15 root@htlxici sapinstance.sh[29446]: (find_sap_binary): found location: "/usr/sap/PP9/DVEBMGS01/exe/dpmon" owner: "pp9adm"
Oct 6 16:17:16 root@htlxici sapinstance.sh[29446]: (crit_test_app): dpmon: /usr/sap/PP9/DVEBMGS01/exe/dpmon=>sapparam: SAPSYSTEMNAME neither in Profile nor in Commandline
Oct 6 16:17:16 root@htlxici sapinstance.sh[29446]: (crit_test_app): Trying to connect via RFC to host ciPP9 instance DVEBMGS01 ...
Oct 6 16:17:16 root@htlxici sapinstance.sh[29446]: (find_sap_binary): found location: "/usr/sap/PP9/DVEBMGS01/exe/startrfc" owner: "pp9adm"
Oct 6 16:17:16 root@htlxici sapinstance.sh[29446]: (watchdog): Watchdog initiated (PIDs: 2878 for 2875 - Timeout: 100 secs)
Oct 6 16:17:17 root@htlxici sapinstance.sh[29446]: (watchdog): wait for PID 2875 returns 1
Oct 6 16:17:17 root@htlxici sapinstance.sh[29446]: (crit_test_app): No connection to instance DVEBMGS01
Oct 6 16:17:17 root@htlxici sapinstance.sh[29446]: (crit_test_app): Instance DVEBMGS01 not responding
Oct 6 16:17:17 root@htlxici sapinstance.sh[29446]: (start_d): ERROR: Instance DVEBMGS01 - fatal startup problem detected
Oct 6 16:17:17 root@htlxici master_control_script.sh[28963]: ##### Failed to start package ciPP9, rollback steps #####
Oct 6 16:17:18 root@htlxici sapinstance.sh[3089]: Entering SGeSAP sapinstance.sh 'stop' runtime steps ...
Oct 6 16:17:18 root@htlxici sapinstance.sh[3089]: SGeSAP - B.05.00.00 - Last modified 02/11/08
Oct 6 16:17:18 root@htlxici sapinstance.sh[3089]: Found: /etc/cmcluster/scripts/sgesap/sap_functions.sh
Oct 6 16:17:18 root@htlxici sapinstance.sh[3089]: Found: /etc/cmcluster/scripts/sgesap/customer_functions.sh
Oct 6 16:17:18 root@htlxici sapinstance.sh[3089]: Not found: /etc/cmcluster/scripts/ext/ciPP9_customer_functions.sh
Oct 6 16:17:18 root@htlxici sapinstance.sh[3089]: (check_versions): Version check passed
Oct 6 16:17:18 root@htlxici sapinstance.sh[3089]: (check_versions): Log Level is 4
Oct 6 16:17:18 root@htlxici sapinstance.sh[3089]: (set_environment DVEBMGS01): Instance administrator : 'pp9adm'
Oct 6 16:17:18 root@htlxici sapinstance.sh[3089]: (set_environment DVEBMGS01): Instance home directory : '/home/pp9adm'
Oct 6 16:17:18 root@htlxici sapinstance.sh[3089]: (set_environment DVEBMGS01): Startprofile            : '/usr/sap/PP9/SYS/profile/PP9_DVEBMGS01_ciPP9'
Oct 6 16:17:18 root@htlxici sapinstance.sh[3089]: (set_environment DVEBMGS01): Instance profile        : '/usr/sap/PP9/SYS/profile/PP9_DVEBMGS01_ciPP9'
Oct 6 16:17:18 root@htlxici sapinstance.sh[3089]: (set_environment DVEBMGS01): Instance work directory : '/usr/sap/PP9/DVEBMGS01/work'
Oct 6 16:17:18 root@htlxici sapinstance.sh[3089]: (find_sap_binary): found location: "/usr/sap/PP9/DVEBMGS01/exe/sappfpar" owner: "pp9adm"
Oct 6 16:17:18 root@htlxici sapinstance.sh[3089]: (init_params_sap_inst): Trying to determine instance type of DVEBMGS01...
Oct 6 16:17:18 root@htlxici sapinstance.sh[3089]: (init_params_sap_inst): Package will handle Application Server Instance DVEBMGS01
Oct 6 16:17:18 root@htlxici sapinstance.sh[3089]: (check_access): Testing directory /sapmnt/PP9/global...
Oct 6 16:17:18 root@htlxici sapinstance.sh[3089]: (watchdog): Watchdog initiated (PIDs: 3216 for 3215 - Timeout: 100 secs)
Oct 6 16:17:18 root@htlxici sapinstance.sh[3089]: (watchdog): wait for PID 3215 returns 0
Oct 6 16:17:18 root@htlxici sapinstance.sh[3089]: (check_access): /sapmnt/PP9/global accessible
Oct 6 16:17:19 root@htlxici sapinstance.sh[3089]: (check_access): Testing directory /usr/sap/PP9...
Oct 6 16:17:19 root@htlxici sapinstance.sh[3089]: (watchdog): Watchdog initiated (PIDs: 3244 for 3243 - Timeout: 100 secs)
Oct 6 16:17:19 root@htlxici sapinstance.sh[3089]: (watchdog): wait for PID 3243 returns 0
Oct 6 16:17:19 root@htlxici sapinstance.sh[3089]: (check_access): /usr/sap/PP9 accessible
Oct 6 16:17:19 root@htlxici sapinstance.sh[3089]: (init_params_sap_inst): System is not using Instance Agents
Oct 6 16:17:19 root@htlxici sapinstance.sh[3089]: (stop_d): Initiate stopping of dialog instance DVEBMGS01 on ciPP9
Oct 6 16:17:19 root@htlxici sapinstance.sh[3089]: (is_ip_local): ciPP9 is local
Oct 6 16:17:19 root@htlxici sapinstance.sh[3089]: (stop_app ciPP9 01 pp9adm): Attempting local stop of instance...
Oct 6 16:17:19 root@htlxici sapinstance.sh[3089]: (stop_d): Waiting for parallel shutdown sequence to finish
Oct 6 16:17:19 root@htlxici sapinstance.sh[3089]: (find_sap_binary): found location: "/usr/sap/PP9/DVEBMGS01/exe/sapcontrol" owner: "pp9adm"
Oct 6 16:17:19 root@htlxici sapinstance.sh[3089]: (stop_app ciPP9 01 pp9adm): Running /usr/sap/PP9/DVEBMGS01/exe/sapcontrol -nr 01 -function StopWait 100 1
Oct 6 16:17:19 root@htlxici sapinstance.sh[3089]: (watchdog): Watchdog initiated (PIDs: 3325 for 3322 - Timeout: 100 secs)
Oct 6 16:17:19 root@htlxici sapinstance.sh[3089]: (wait_pidlist): Forked the wait_pidlist background shell. PID: 3319
Oct 6 16:17:19 root@htlxici sapinstance.sh[3089]: (wait_pidlist): PIDLIST: 3271 -1
Oct 6 16:17:19 root@htlxici sapinstance.sh[3089]: (wait_pidlist): PIDlist watchdog initiated (PIDlist: 3271)
Oct 6 16:17:20 root@htlxici sapinstance.sh[3089]: (watchdog): wait for PID 3322 returns 0
Oct 6 16:17:20 root@htlxici sapinstance.sh[3089]: (find_sap_binary): found location: "/usr/sap/PP9/DVEBMGS01/exe/cleanipc" owner: "pp9adm"
Oct 6 16:17:22 root@htlxici sapinstance.sh[3089]: (clean_ipc): Searching shmem of DVEBMGS01 on htlxici using normal cleanup policy
Oct 6 16:17:23 root@htlxici: (clean_ipc): P: OsKey:    10110 0x0000277e Shared Memory Key: 10 removed
Oct 6 16:17:23 root@htlxici sapinstance.sh[3089]: (wait_pidlist): Killed the wait_pidlist background shell. PID: 3319
Oct 6 16:17:23 root@htlxici sapinstance.sh[3089]: (stop_d): Parallel dialog instance shutdown finished
Oct 6 16:17:23 root@htlxici sapinstance.sh[3089]: (find_sap_binary): found location: "/usr/sap/PP9/DVEBMGS01/exe/sapcontrol" owner: "pp9adm"
Oct 6 16:17:25 root@htlxici sapinstance.sh[3089]: (is_ip_local): ciPP9 is local
Oct 6 16:17:25 root@htlxici sapinstance.sh[3089]: (crit_test_app): Trying to connect local dispatcher of instance DVEBMGS01 ...
Oct 6 16:17:25 root@htlxici sapinstance.sh[3089]: (find_sap_binary): found location: "/usr/sap/PP9/DVEBMGS01/exe/dpmon" owner: "pp9adm"
Oct 6 16:17:26 root@htlxici sapinstance.sh[3089]: (crit_test_app): dpmon: /usr/sap/PP9/DVEBMGS01/exe/dpmon=>sapparam: SAPSYSTEMNAME neither in Profile nor in Commandline
Oct 6 16:17:26 root@htlxici sapinstance.sh[3089]: (crit_test_app): Trying to connect via RFC to host ciPP9 instance DVEBMGS01 ...
Oct 6 16:17:26 root@htlxici sapinstance.sh[3089]: (find_sap_binary): found location: "/usr/sap/PP9/DVEBMGS01/exe/startrfc" owner: "pp9adm"
Oct 6 16:17:26 root@htlxici sapinstance.sh[3089]: (watchdog): Watchdog initiated (PIDs: 4369 for 4368 - Timeout: 100 secs)
Oct 6 16:17:27 root@htlxici sapinstance.sh[3089]: (watchdog): wait for PID 4368 returns 1
Oct 6 16:17:27 root@htlxici sapinstance.sh[3089]: (crit_test_app): No connection to instance DVEBMGS01
Oct 6 16:17:27 root@htlxici sapinstance.sh[3089]: (crit_test_app): Instance DVEBMGS01 not responding
Oct 6 16:17:27 root@htlxici sapinstance.sh[3089]: Leaving SGeSAP sapinstance.sh 'stop' runtime steps ...
Oct 6 16:17:27 root@htlxici package_ip.sh[4578]: Removing 172.31.112.131
Oct 6 16:17:27 root@htlxici package_ip.sh[4578]: Remove IP address 172.31.112.131 from subnet 172.31.112.0
Oct 6 16:17:27 root@htlxici filesystem.sh[4610]: Number of components: 5 6
Oct 6 16:17:27 root@htlxici filesystem.sh[4610]: sorted components in array: 5 6
Oct 6 16:17:27 root@htlxici filesystem.sh[4610]: sorted indexes: 0 1
Oct 6 16:17:27 root@htlxici filesystem.sh[4610]: processing 1 /usr/sap/PP9/DVEBMGS01 1
Oct 6 16:17:27 root@htlxici filesystem.sh[4610]: processing 0 /usr/sap/PP9 1
Oct 6 16:17:27 root@htlxici filesystem.sh[4610]: Mount order: 1 2
Oct 6 16:17:27 root@htlxici filesystem.sh[4610]: max mnt order: 2
Oct 6 16:17:28 root@htlxici filesystem.sh[4610]: Unmounting filesystem on /dev/vx/dsk/pp9cidg/DVEBMGS61
Oct 6 16:17:29 root@htlxici filesystem.sh[4610]: Unmounting filesystem on /dev/vx/dsk/pp9cidg/sap_PP9
Oct 6 16:17:29 root@htlxici volume_group.sh[4678]: Deporting disk group pp9cidg
Oct 6 16:17:30 root@htlxici master_control_script.sh[28963]: ###### Failed to start package for ciPP9 ######

Sql Server Agent not starting automatically in failover in a clustered environment.

Hi,
We are running Sql Server 2008 R2 as a 2 node cluster in Windows 2008 R2
server. In the Sql Server Configuration manager we find that service of
the Sql Server(database engine) as got a start mode as manual being
an instance in the 2 node cluster. When the node in which the service is
running fails the the Sql Server service gets started in the other node. However
we find that the Sql Server Agent service(whose start mode is also in manual)
does not get started automatically in the other node along with the Sql Server
service.Why does the cluster service do not start Sql Server agent service as well.
Should we make the Sql Server agent service start mode to be automatic
instead of being manual as it is now? Thanking you in advance
Binny Mathew

Folks - the startup type of all clustered services should be set to manual - when you virtualize SQL Services, they are put in manual startup mode and this should not be changed. It is the cluster manager which starts the SQL and SQLAgent when a
failover happens (SQL does not start SQLAgent). If your SQLAgent doesn't start after a cluster failover, check the SQLAgent logs to see what the root cause of the problem is and rectify it. You should not change the startup type to "Automatic" -
leave it as manual
Satish Kartan www.sqlfood.com
I suspect that your clustered SQLAgent resource is currently NOT dependent on SQL resource. If not, make SQLAgent dependent on SQL resource, which will coerce SQLAgent to wait for the SQL resource to come online before it brings itselft (SQLAgent) resource
online, when a failover happens.
Satish Kartan www.sqlfood.com

SAP not starting after crash: Terminateing With error code 12

Hi,
After system crash SAP is not starting normally. When running startsap under SIDadm puts out: /usr/sap/TST/SYS/exe/run/startdb: Terminateing With error code 12
startdb.log shows that:
/oracle/TST/102_64/bin/sqlplus: error while loading shared libraries: libsqlplus.so: cannot open shares object file: No such file or directory
I have checked - file and directory are present.
However - when manually starting DB under oraSID and then logging in as SIDadm and starting SAP - everything starts normally.
(Allthough SID is has been changed before - system also worked normally after SID change) I have checked userrights and groups , also profile - everything seems to be normal. Any ideas?
Edited by: Kristjan T on Mar 16, 2011 1:16 PM

Hi,
1.what UNIX Flavor are we talking about -> SuSe
2.What SAP Kernel Release is in place (may be 6.40 non EX2 ?) -> 6.40
3.What release is the DB suposed to have? -> 10.2.0.2.0 - 64bit Prod
4.I see, you are calling an sqlplus from a 10.2 ORACLE_HOME.
Is that the correct HOME the DB is running with ? -> Yes
5.Can you start the DB with
brconnect -c -u / -f dbstart -> NO
Error is:
:devadm 51> brconnect -c -u / -f dbstart
BR0801I BRCONNECT 7.00 (40)
oracleDEV: error while loading shared libraries: libskgxp10.so: cannot open shared object file: No such file or directory
BR0278E Command output of '/oracle/DEV/102_64/bin/sqlplus /nolog':
/oracle/DEV/102_64/bin/sqlplus: error while loading shared libraries: libsqlplus.so: cannot open shared object file: No such file or directory
BR0280I BRCONNECT time stamp: 2011-05-05 15.01.17
BR0279E Return code from '/oracle/DEV/102_64/bin/sqlplus /nolog': 127
BR0302E SQLPLUS call for database instance DEV failed
BR0303E Determination of Oracle version failed
BR0280I BRCONNECT time stamp: 2011-05-05 15.01.17
BR0804I BRCONNECT terminated with errors
(Different machine but same situation)
6.As already requested, what is the output of:
6.1.ldd sqlplus
:devadm 55> ldd sqlplus
ldd: ./sqlplus: No such file or directory
in addition:
6.2. env | grep -i ora
devadm 56> env | grep -i ora
PATH=/oracle/DEV/102_64/bin:/opt/IBMJava2-amd64-142/bin:.:/home/devadm:/usr/sap/DEV/SYS/exe/run:/usr/local/bin:/bin:/usr/bin:/usr/X11R6/bin:/home/devadm/bin:/usr/games:/opt/gnome/bin:/opt/kde3/bin:/usr/bin/X11:/usr/lib/mit/bin:/usr/lib/mit/sbin
LD_LIBRARY_PATH=/usr/sap/DEV/SYS/exe/run:/oracle/client/10x_64/instantclient
dbms_type=ORA
dbs_ora_tnsname=DEV
dbs_ora_schema=SAPSR3
ORACLE_SID=DEV
ORACLE_BASE=/oracle
TNS_ADMIN=/usr/sap/DEV/SYS/profile/oracle
ORACLE_HOME=/oracle/DEV/102_64
SAPDATA_HOME=/oracle/DEV
6.3 env | grep -i nls
:devadm 57> env | grep -i nls
XNLSPATH=/usr/X11R6/lib/X11/nls
NLS_LANG=AMERICAN_AMERICA.UTF8
6.4 env | grep -i lib
devadm 58> env | grep -i lib
PATH=/oracle/DEV/102_64/bin:/opt/IBMJava2-amd64-142/bin:.:/home/devadm:/usr/sap/DEV/SYS/exe/run:/usr/local/bin:/bin:/usr/bin:/usr/X11R6/bin:/home/devadm/bin:/usr/games:/opt/gnome/bin:/opt/kde3/bin:/usr/bin/X11:/usr/lib/mit/bin:/usr/lib/mit/sbin
XKEYSYMDB=/usr/X11R6/lib/X11/XKeysymDB
XNLSPATH=/usr/X11R6/lib/X11/nls
PKG_CONFIG_PATH=/usr/local/lib/pkgconfig:/usr/local/share/pkgconfig:/usr/lib64/pkgconfig:/usr/share/pkgconfig:/opt/kde3/lib64/pkgconfig:/opt/gnome/lib64/pkgconfig:/opt/gnome/lib64/pkgconfig:/opt/gnome/share/pkgconfig
GTK_PATH=/usr/local/lib/gtk-2.0:/opt/gnome/lib/gtk-2.0:/usr/lib/gtk-2.0
GTK_PATH64=/usr/local/lib64/gtk-2.0:/opt/gnome/lib64/gtk-2.0:/usr/lib64/gtk-2.0
DIR_LIBRARY=/usr/sap/DEV/SYS/exe/run
LD_LIBRARY_PATH=/usr/sap/DEV/SYS/exe/run:/oracle/client/10x_64/instantclient
Any ideas???
Br,
Kristjan T.

Alternate Payee Number not capture during Manual payment posting (FBZ2)

Dear Friend,
Appreciate if anyone can help me with below issue.
Scenario:
- Vendor master already been updated with the alternative payee number.
- I have create a vendor invoice with payee data in the field BSEG-EMPFB.
Problem:
When I perform FBZ2 - post outgoing payment and select the invoice created, the payee field was not updated automatically neither based from the original invoice nor vendor master. Furthermore, the field was greyed out during payment posting.
Pls help how can I cantured the payee number based from the original invoice during post outgoing payment.
Thx.

Hi Kiran,
Here is my answer to your Q.
1. Have you given alternate payee in vendor master
- YES, at the genral data->payment transaction and also at alternative payee in doc. I already insert the payee number.
2. While doing FBZ2 in account give the alternate payee and when you go inside it tells no open items found
-NOT exactly, coz i dont use the alternate payee number for choosing open item. I use the same vendor code as per invoice.
3. Click other items and click process open items there you will find the open invoice of the the vendors.
-NOT applicable as i already select the vendor based from the invoice to be made.
When I choose open item during FBZ2, entered the main vendor code as per invoice to be made. In the invoice, the alternate payee number is there already. Just during FBZ2 the field is greayed out, hence the payee number from invoice wav not adopted when manual payment was done.
I notice if i use the FBZ2, the payee field is not open for entry.
Pls help.
Thanks.

Dispatcher does not start during Refresh

Hi all,
We are currently carrying out System Refresh from our Production to Quality system using Oracle backup and recovery method.
We are currently able to restore & recover the Production backup on Quality System. We have tried to restart the database & application to continue with Post-refresh activities. However, we are unable to start the SAP application ( Note: Both SAP application & database resides on different host. Also, we have other SAP applications running on the same server).
Following are the details:
SAP ECC 6.0 (RMCA)
SunOS sun4u sparc SUNW
Oracle 10.2.0.4.
When checked , dev_disp shows the below logs :
EsStdUnamFileMapInit: Info: mmap() failed. errno = 11(Resource temporarily unavailable)
EsStdInit: unable to allocate 4 MB
EsStdInit: try to allocate 0 MB
ERROR => EsStdInit: unable to allocate 20576 MB
Error 11 while initializing OS dependent part.
ERROR => DpEmInit: EmInit (1)
ERROR => DpMemInit: DpEmInit (-1)
DP_FATAL_ERROR => DpSapEnvInit: DpMemInit
DISPATCHER EMERGENCY SHUTDOWN ***
increase tracelevel of WPs
NiWait: sleep (10000ms) ...
NiISelect: timeout 10000ms
NiISelect: maximum fd=1
NiISelect: read-mask is NULL
NiISelect: write-mask is NULL
Fri Dec 16 14:59:01 2011
NiISelect: TIMEOUT occured (10000ms)
Also, the startup logs shows as below:
Starting Programs
SAP-R/3-Startup Program Rel 700 V1.8 (2003/04/24)
Starting at 2011/12/16 14:57:46
Startup Profile: "/usr/sap/QUL/SYS/profile/START_DVEBMGS03"
Setup Environment Variables
(735) SETENV LD_LIBRARY_PATH=/usr/sap/QUL/DVEBMGS03/exe:/usr/sap/QUL/DVEBMGS03/exe:/usr/sap/QUL/SYS/exe/run:/oracle/client/10x_64/instantclient
(735) SETENV SHLIB_PATH=/usr/sap/QUL/DVEBMGS03/exe:
(735) SETENV LIBPATH=/usr/sap/QUL/DVEBMGS03/exe:
Update local Kernel Files
(737) Local: /usr/sap/QUL/SYS/exe/run/sapcpe name=QUL
(735) system(/usr/sap/QUL/SYS/exe/run/sapcpe name=QUL) returns 1
(735) Return-Code 1 in Local-Kernel-Update. See sapcpe.log.
Execute Pre-Startup Commands
(743) Local: /usr/sap/QUL/SYS/exe/run/sapcpe pf=/sapmnt/QUL/profile/QUL_DVEBMGS03
(735) system(/usr/sap/QUL/SYS/exe/run/sapcpe pf=/sapmnt/QUL/profile/QUL_DVEBMGS03) returns 1
(749) Local: /usr/sap/QUL/DVEBMGS03/exe/sapmscsa pf=/sapmnt/QUL/profile/QUL_DVEBMGS03_ -n
/usr/sap/QUL/DVEBMGS03/exe/sapmscsa: make new mode. SCSA currently non existent.
sapcscsa: SCSA defined. sapscsaId == 500318684 == 1e00089c
sapcscsa: SCSA attached at address ffffffff7e000000
sapcscsa: SCSA initialized.
rslgwr1(21): Searching for overlap point in pre-existing SysLog file...
/usr/sap/QUL/DVEBMGS03/exe/sapmscsa: finished.
(751) Local: rm -f ms.sapQUL_DVEBMGS03
(753) Local: ln -s -f /usr/sap/QUL/DVEBMGS03/exe/msg_server ms.sapQUL_DVEBMGS03
(755) Local: rm -f dw.sapQUL_DVEBMGS03
(757) Local: ln -s -f /usr/sap/QUL/DVEBMGS03/exe/disp+work dw.sapQUL_DVEBMGS03
(759) Local: rm -f co.sapQUL_DVEBMGS03
(761) Local: ln -s -f /usr/sap/QUL/DVEBMGS03/exe/rslgcoll co.sapQUL_DVEBMGS03
(763) Local: rm -f se.sapQUL_DVEBMGS03
(765) Local: ln -s -f /usr/sap/QUL/DVEBMGS03/exe/rslgsend se.sapQUL_DVEBMGS03
(767) Local: rm -f ig.sapQUL_DVEBMGS03
(769) Local: ln -s -f /usr/sap/QUL/DVEBMGS03/exe/igswd_mt ig.sapQUL_DVEBMGS03
Starting Programs
16.12.2011 14:57:47
ShmDetach
OK
(794) Starting: local ms.sapQUL_DVEBMGS03 pf=/sapmnt/QUL/profile/QUL_DVEBMGS03_
(795) Starting: local dw.sapQUL_DVEBMGS03 pf=/sapmnt/QUL/profile/QUL_DVEBMGS03_
(796) Starting: local co.sapQUL_DVEBMGS03 pf=/sapmnt/QUL/profile/QUL_DVEBMGS03_ -F
(798) Starting: local se.sapQUL_DVEBMGS03 pf=/sapmnt/QUL/profile/QUL_DVEBMGS03_ -F
(799) Starting: local ig.sapQUL_DVEBMGS03 -mode=profile pf=/sapmnt/QUL/profile/QUL_DVEBMGS03_
(735) Waiting for Child Processes to terminate.
(735) **** 2011/12/16 14:59:07 Child 795 terminated with Status 0 . ****
(795) **** 2011/12/16 14:59:07 No RestartProgram command for program 1 ****
:QULadm 38%
Can you please help us on how to resolve this error as soon as possible?
Your help in this regard will be highly appreciated.
With regards,
Raj
Edited by: Arul Sekar on Dec 19, 2011 6:25 AM

Hi all,
Thanks for your reply!!
I have the below output for memlimits -l
Maximum heap size per process........: 9628 MB
Maximum mapped file size (mmap)......: 7420 MB
    this value is probably limited by swap space
Maximum protectable size (mprotect)..: 7420 MB
    em/initial_size_MB > 7420 MB will not work
Maximum address space per process....: 15768 MB
Total available swap space...........: 10572 MB
    main memory size x 3 recommended , minimum 1 GB
Based on the input, we have tried changing the Extended memory settings for the server ( em/initial_size_MB = 7000 , ztta/roll_extension = 2147483648) This time the SAP application started, but did not last for long. The Dispatcher died soon with the below error:
Mon Dec 19 12:11:17 2011
ERROR => DpWpCreate: fork (12: Not enough space)
***LOG Q0I=> DpWpCreate, fork ( fork 12)
ERROR => DpWpDynCreate: DpWpCreate
ERROR => DpProcCreate: DpWpDynCreate
DP_FATAL_ERROR => DpSapEnvInit: DpProcCreate
DISPATCHER EMERGENCY SHUTDOWN ***
increase trace level of WPs
kill(22278,0) successful -> process alive
killing W0-22278 (SIGUSR2)
Kindly let us know how can this be resolved?
with regards,
Raja

Configurations tools ( netca,dbca ,assistants) not started during install

Friends,
I am trying to install Oracle 9iR2 on redhat advanced server.
We copied the files into a staging area.During
install it asked for Oracle.swd.jre file which i checked
not there.
But i ignored the error message and finished the
install.Installation went through successfully but the
configurations tools netca,dbca and agent assistants have
not started. Apache server has started sucessfully.
I have done installs earlier on Redhat 8 but i never
had problems like this.I checked the staging area and i could able to see a directory like oracle.swd.jre in
Disk1/stage/Components/oracle.swd.jre but not the file.
I will be glad if anyone can tell me the work around
for this.
Regards.

Friends,
I am trying to install Oracle 9iR2 on redhat advanced server.
We copied the files into a staging area.During
install it asked for Oracle.swd.jre file which i checked
not there.
But i ignored the error message and finished the
install.Installation went through successfully but the
configurations tools netca,dbca and agent assistants have
not started. Apache server has started sucessfully.
I have done installs earlier on Redhat 8 but i never
had problems like this.I checked the staging area and i could able to see a directory like oracle.swd.jre in
Disk1/stage/Components/oracle.swd.jre but not the file.
I will be glad if anyone can tell me the work around
for this.
Regards.

CSSD does not start during root.sh execution

hi,
I am using oracle10gR2 on solaris 9 sparc.
when i start root.sh script it stops at following point.
Running Oracle10 root.sh script...
The following environment variables are set as:
ORACLE_OWNER= oracle
ORACLE_HOME= /u01/app/oracle/product/10.2.0/Db_1
Enter the full pathname of the local bin directory: [usr/local/bin]:
Copying dbhome to /usr/local/bin ...
Copying oraenv to /usr/local/bin ...
Copying coraenv to /usr/local/bin ...
Creating /etc/oratab file...
Adding entry to /etc/oratab file...
Entries will be added to the /etc/oratab file as needed by
Database Configuration Assistant when a database is created
Finished running generic part of root.sh script.
Now product-specific root actions will be performed.
but i think this is not the complete run by root.sh script because complete execution of this script perform following tasks also.
/var/opt/oracle does not exist. Creating it now.
/etc/oracle does not exist. Creating it now.
Successfully accumulated necessary OCR keys.
Creating OCR keys for user 'root', privgrp 'root'..
Operation successful.
Oracle Cluster Registry for cluster has been initialized
Adding to inittab
Checking the status of Oracle init process...
Expecting the CRS daemons to be up within 600 seconds.
CSS is active on these nodes.
mars
CSS is active on all nodes.
Oracle CSS service is installed and running under init(1M)
I have tried to use the localconfig reset command but still it is giving same error.
I have searched through this forum but still no solution.
I have tried metalink note 314173.1 also but error is still there.
Any solution for this????

CSSD does not start (Cluster Manager)
CSSD does not start (Cluster Manager)

SAP-NOTES (ERROR DURING APPLIYING NOTES "ELEMENT TAX1 OVERLAPPING")

HI,
I HAVE PROBLEM WITH STANDARD TRANSACTION SAPJ1IH .....(T-CODE- J1IH )
I APPLIED SAP-NOTES FOR THIS WHERE I HAVE APPLIED NEW FIELDS IN TABLE CONTROL ON SCREEN, IT IS DONE WITHOUT ERROR. BUT WHEN APPLYING NOTES BY THE BASIS PERSON THERE AN ERROR MESSAGE FOR SCREEN-2020 THAT "ELEMENTS TAX1 IS OVERLAPPING ".
BASICALLY TAX1 IS THE NAME OF LABEL IN TABLE CONTROL WHICH I HAVE APPLIED AS PER CORRECTION CODE OF SAP-NOTES.
DISCUSS WITH SAP....
THEY MAIL THAT WE HAVE TO REMOVE ANY EXISTING SCREEN ELEMENTS AS THE SYSTEM DOES NOT FOUND SPACE AUTOMATICALLY.............. BUT I HAVE TO JUST ADD THE FIELD.
I HAVE NO IDEA ABOUT IT. SUGGEST ME SOME.
Edited by: RAHUL SINGH on Mar 25, 2009 9:16 AM
Edited by: RAHUL SINGH on Mar 25, 2009 9:18 AM

noT
           JuST
WitH
                                                            thE
                 KeyBOArd
                          bUt
                                                                                a
                                                    Lot
      oF                                                           OthER
                              ISsuES
                                                                                tOO.
DONt
                                          yOU
THiNk?
pk
PS: Sorry for the Code Tags
Edited by: kishan P on Mar 25, 2009 2:35 PM

Shadow Instance Not starting during upgrade Pre-processing

Hi All,
I am upgrading CRM Dev system from 6.0 to 7.02. I am getting an error during the start of shadow system in pre-processing phase in MAIN_SHDPREPUT/START_SHDI_PREPUT! Please help ASAP.
Last error code set: Shadow instance couldn't be started, check 'STARTSSC.LOG' and 'DEVTRACE.LOG': Process F:\SUM\SUM\abap\exe/sapcontrol.exe exited with 2, see 'F:\SUM\SUM\abap\log\SAPup.ECO' for details.
STARTSSC:
1 ETQ399 SYSTEM HEALTH MANAGER: check for instance processlist.
1 ETQ399 SAPCONTROL MANAGER: getProcessList with host: SAPCRMDEV and instance: 04
3 ETQ120 20150113094015: PID 4656 execute 'F:\SUM\SUM\abap\exe\sapcontrol.exe -format script -prot PIPE -host SAPCRMDEV -nr 04 -function GetProcessList', output written to 'F:\SUM\SUM\abap\log\SAPup.ECO'.
3 ETQ123 20150113094015: PID 4656 exited with status 4 (time 0.000 real)
1 ETQ399 SAPCONTROL MANAGER: get parameter value
3 ETQ120 20150113094015: PID 6968 execute 'F:\SUM\SUM\abap\exe\sapcontrol.exe -prot PIPE -host SAPCRMDEV -nr 04 -function ParameterValue SAPSYSTEMNAME', output written to 'F:\SUM\SUM\abap\log\SAPup.ECO'.
3 ETQ123 20150113094015: PID 6968 exited with status 0 (time 0.000 real)
1 ETQ399 SYSTEM HEALTH MANAGER: running postCheck for instance 04 on host SAPCRMDEV
4 ETQ399 Set RFC variables for shadow connect:
4 ETQ399 System-nr = '04', GwService = 'sapgw04' Client = '000'
1 ETQ359 RFC Login to: System="CRD", AsHost="SAPCRMDEV" Nr="04", GwHost="SAPCRMDEV", GwService="sapgw04"
2EETQ231 RFC Login failed
2 ETQ399 SYSTEM HEALTH MANAGER: Checking instance number 4 for used ports on host 'SAPCRMDEV'.
3 ETQ399 SYSTEM HEALTH MANAGER: Port 3204 appears to be unused.
3 ETQ399 SYSTEM HEALTH MANAGER: Port 3304 appears to be unused.
3 ETQ399 SYSTEM HEALTH MANAGER: Port 3604 appears to be unused.
3 ETQ399 SYSTEM HEALTH MANAGER: Port 3904 appears to be unused.
3 ETQ399 SYSTEM HEALTH MANAGER: Port 8104 appears to be unused.
3 ETQ399 SYSTEM HEALTH MANAGER: Port 30401 appears to be unused.
3 ETQ399 SYSTEM HEALTH MANAGER: Port 50419 appears to be unused.
1 ETQ399 SAPCONTROL MANAGER: restartService with kernelstate: 0
3 ETQ120 20150113094040: PID 8848 execute 'F:\SUM\SUM\abap\exe\sapcontrol.exe -prot PIPE -host SAPCRMDEV -nr 04 -function RestartService', output written to 'F:\SUM\SUM\abap\log\SAPup.ECO'.
3 ETQ123 20150113094040: PID 8848 exited with status 0 (time 0.000 real)
1 ETQ399 SYSTEM MANAGER: SAPControl tries to control all instances.
1 ETQ399 SYSTEM MANAGER: Calling getInstances.
1 ETQ399 SYSTEM MANAGER: found instance for action START : Instance Number: 04
1 ETQ399 SYSTEM MANAGER: ControlInstance with SAPCONTOL action START for instance 04.
1 ETQ399 SYSTEM HEALTH MANAGER: running preCheck for instance 04 on host SAPCRMDEV.
2 ETQ399 SYSTEM HEALTH MANAGER: Checking instance number 4 for used ports on host 'SAPCRMDEV'.
3 ETQ399 SYSTEM HEALTH MANAGER: Port 3204 appears to be unused.
3 ETQ399 SYSTEM HEALTH MANAGER: Port 3304 appears to be unused.
3 ETQ399 SYSTEM HEALTH MANAGER: Port 3604 appears to be unused.
3 ETQ399 SYSTEM HEALTH MANAGER: Port 3904 appears to be unused.
3 ETQ399 SYSTEM HEALTH MANAGER: Port 8104 appears to be unused.
3 ETQ399 SYSTEM HEALTH MANAGER: Port 30401 appears to be unused.
3 ETQ399 SYSTEM HEALTH MANAGER: Port 50419 appears to be unused.
1 ETQ399 SYSTEM HEALTH MANAGER: call test rfc.
4 ETQ399 Set RFC variables for shadow connect:
4 ETQ399 System-nr = '04', GwService = 'sapgw04' Client = '000'
1 ETQ359 RFC Login to: System="CRD", AsHost="SAPCRMDEV" Nr="04", GwHost="SAPCRMDEV", GwService="sapgw04"
2EETQ231 RFC Login failed
1 ETQ399 SYSTEM HEALTH MANAGER: check for instance processlist.
1 ETQ399 SAPCONTROL MANAGER: getProcessList with host: SAPCRMDEV and instance: 04
3 ETQ120 20150113094113: PID 8484 execute 'F:\SUM\SUM\abap\exe\sapcontrol.exe -format script -prot PIPE -host SAPCRMDEV -nr 04 -function GetProcessList', output written to 'F:\SUM\SUM\abap\log\SAPup.ECO'.
3 ETQ123 20150113094113: PID 8484 exited with status 4 (time 0.000 real)
1 ETQ399 SYSTEM HEALTH MANAGER: System is down, go on with start action
1 ETQ399 SAPCONTROL MANAGER: startWait with host: SAPCRMDEV and instance: 04
3 ETQ120 20150113094113: PID 7860 execute 'F:\SUM\SUM\abap\exe\sapcontrol.exe -prot PIPE -host SAPCRMDEV -nr 04 -function StartWait 300 10', output written to 'F:\SUM\SUM\abap\log\SAPup.ECO'.
3 ETQ123 20150113094153: PID 7860 exited with status 2 (time 0.000 real)
1 ETQ399 SYSTEM MANAGER: SAPControl action START failed for instance 04 ('SAPCONTROL MANAGER: call (sapcontrol.exe) failed with return code '-1'
1 ETQ399 SYSTEM MANAGER: CheckSystemStatus.
1 ETQ399 SAPCONTROL MANAGER: getProcessList with host: SAPCRMDEV and instance: 04
3 ETQ120 20150113094153: PID 8728 execute 'F:\SUM\SUM\abap\exe\sapcontrol.exe -format script -prot PIPE -host SAPCRMDEV -nr 04 -function GetProcessList', output written to 'F:\SUM\SUM\abap\log\SAPup.ECO'.
3 ETQ123 20150113094153: PID 8728 exited with status 0 (time 0.000 real)
1EETQ399 SYSTEM MANAGER: START of mandatory instance 04 on server SAPCRMDEV has failed
2EETQ399 Starting shadow instance failed
1EETQ399 Last error code set is: Shadow instance couldn't be started, check 'STARTSSC.LOG' and 'DEVTRACE.LOG': Process F:\SUM\SUM\abap\exe/sapcontrol.exe exited with 2, see 'F:\SUM\SUM\abap\log\SAPup.ECO' for details
1EETQ204 Upgrade phase "START_SHDI_PREPUT" aborted with severe errors ("20150113094153")
DEVTRACE:
trc file: "dev_disp", trc level: 1, release: "721"
sysno      04
sid        CRD
systemid   562 (PC with Windows NT)
relno      7210
patchlevel 0
patchno    400
intno      20020600
make       multithreaded, Unicode, 64 bit, optimized
profile    F:\SUM\SUM\abap\system\CRD\SYS\profile\CRD_DVEBMGS04_SAPCRMDEV
pid        8608
kernel runs with dp version 139000(ext=121000) (@(#) DPLIB-INT-VERSION-139000-UC)
length of sys_adm_ext is 592 bytes
*** SWITCH TRC-HIDE on ***
***LOG Q00=> DpSapEnvInit, DPStart (04 8608) [dpxxdisp.c   1323]
shared lib "dw_xml.dll" version 400 successfully loaded
shared lib "dw_xtc.dll" version 400 successfully loaded
shared lib "dw_stl.dll" version 400 successfully loaded
shared lib "dw_gui.dll" version 400 successfully loaded
shared lib "dw_mdm.dll" version 400 successfully loaded
shared lib "dw_rndrt.dll" version 400 successfully loaded
shared lib "dw_abp.dll" version 400 successfully loaded
shared lib "dw_sym.dll" version 400 successfully loaded
shared lib "dw_aci.dll" version 400 successfully loaded
rdisp/softcancel_sequence : -> 0,5,-1
use internal message server connection to port 3904
rdisp/dynamic_wp_check : 0
rdisp/calculateLoadAverage : 1
Tue Jan 13 08:53:56 2015
*** WARNING => DpNetCheck: NiAddrToHost(1.0.0.0) took 4 seconds
***LOG GZZ=> 1 possible network problems detected - check tracefile and adjust the DNS settings [dpxxtool2.c 6525]
MtxInit: 30000 0 0
DpSysAdmExtInit: ABAP is active
DpSysAdmExtInit: VMC (JAVA VM in WP) is not active
display_tcp_ip: 0
Set Check Logoff Flags to 0x0
DpIPCInit2: write dp-profile-values into sys_adm_ext
DpIPCInit2: start server >SAPCRMDEV_CRD_04                        <
DpShMCreate: sizeof(wp_adm) 42864 (2256)
DpShMCreate: sizeof(tm_adm) 5517056 (27448)
DpShMCreate: sizeof(wp_ca_adm) 64000 (64)
DpShMCreate: sizeof(appc_ca_adm) 64000 (64)
DpCommTableSize: max/headSize/ftSize/tableSize=500/16/1392064/1392080
DpShMCreate: sizeof(comm_adm) 1392080 (2768)
DpSlockTableSize: max/headSize/ftSize/fiSize/tableSize=0/0/0/0/0
DpShMCreate: sizeof(slock_adm) 0 (296)
DpFileTableSize: max/headSize/ftSize/tableSize=0/0/0/0
DpShMCreate: sizeof(file_adm) 0 (80)
DpShMCreate: sizeof(vmc_adm) 0 (2160)
DpShMCreate: sizeof(wall_adm) (41664/42896/64/192)
DpShMCreate: sizeof(gw_adm) 48
DpShMCreate: sizeof(j2ee_adm) 3952
DpShMCreate: SHM_DP_ADM_KEY (addr: 00000000073B0050, size: 7182832)
DpShMCreate: allocated sys_adm at 00000000073B0060
DpShMCreate: allocated wp_adm_list at 00000000073B30B0
DpShMCreate: allocated wp_adm at 00000000073B32A0
DpShMCreate: allocated tm_adm_list at 00000000073BDA20
DpShMCreate: allocated tm_adm at 00000000073BDA70
DpShMCreate: allocated wp_ca_adm at 0000000007900980
DpShMCreate: allocated appc_ca_adm at 0000000007910390
DpShMCreate: allocated comm_adm at 000000000791FDA0
DpShMCreate: system runs without slock table
DpShMCreate: system runs without file table
DpShMCreate: allocated vmc_adm_list at 0000000007A73B80
DpShMCreate: system runs without vmc_adm
DpShMCreate: allocated gw_adm at 0000000007A73C30
DpShMCreate: allocated j2ee_adm at 0000000007A73C70
DpShMCreate: allocated ca_info at 0000000007A74BF0
DpShMCreate: allocated wall_adm at 0000000007A74C80
DpCommAttachTable: attached comm table (header=000000000791FDA0/ft=000000000791FDB0)
DpSysAdmIntInit: initialize sys_adm
rdisp/test_roll : roll strategy is DP_NORMAL_ROLL
dia token check not active (8 token)
MBUF state OFF
DpCommInitTable: init table for 500 entries
DpRqQInit: keep protect_queue / slots_per_queue 0 / 2001 in sys_adm
rdisp/queue_size_check_value : -> on,50,30,40,500,50,500,80
EmInit: MmSetImplementation( 2 ).
MM global diagnostic options set: 0
<ES> client 0 initializing ....
<ES> EsILock: use Mutex for locking
<ES> InitFreeList
<ES> block size is 4096 kByte.
<ES> Info: em/initial_size_MB( 8191MB) not multiple of em/blocksize_KB( 4096KB)
<ES> Info: em/initial_size_MB rounded up to 8192MB
Using implementation view
<EsNT> Using memory model view.
<EsNT> Memory Reset disabled as NT default
*** ERROR => <EsNT> CreateFileMapping name=Global\ES_SEG_04_003 ,size=2044 MB, error=1455 [esnti.c      1278]
* Memory diagnostic                                 *
Systeminformation
Processor-Typ             : Processor-Count           : 4
Operating System          : NT 6.1, Build 7601
Service Pack              : Service Pack 1
NT Pagefile Informations
Config. minimum size      :     0 K
Config. maximum size      :     0 K
Avail. maximum size      :     0 K
| Num|Pagefile                      | Min.Size| Max.Size| Avail.Max| Curr.Size|
|----|------------------------------|----------|----------|----------|----------|
NT Task Manager Informations
Total Handles             :    42631
Total Threads             :     1579
Total Processes           :      124
Commit Charge Total       : 38104688 K
Commit Charge Limit       : 39413172 K
Commit Charge Peak        : 38104688 K
Phys.Memory Total         : 16776696 K
Phys.Memory Available     : 4975120 K
File Cache                :   260104 K
Kernel Memory Total       :   370268 K
Kernel Memory Paged       :   284740 K
Kernel Memory Nonpaged    :    85528 K
Memory usage of current process
Total virt.address space : 0000008589934464 K
Avail.virt.address space : 0000008588857984 K
Private Pages             :        0 K
Total heap size           :    14399 K
Virtual memory regions    :       42 K
Uncommitted heap memory   :     5660 K
Allocated heap memory     :     7949 K
Moveable heap memory      :        0 K
DDE shared heap memory    :     4372 K
Memory usage of all processes
| PID|Image               |Instance   | Work.Set|   WS Peak|Priv.Pages|   PP Peak|Pg Fault|
|----|--------------------|-----------|----------|----------|----------|----------|--------|
|5088|conhost.exe         |           |    1228 K|    3148 K|    1204 K|    7952 K|       0|
|6672|conhost.exe         |           |    1228 K|    3156 K|    1204 K|   35924 K|       0|
|6416|conhost.exe         |           |    1228 K|    3144 K|    1204 K|   35924 K|       0|
|5148|taskhost.exe        |           |    6320 K|   10896 K|    7908 K|    8600 K|     235|
|2576|rdpclip.exe         |           |    6224 K|    8708 K|    2968 K|    3008 K|       3|
|5664|Dwm.exe             |           |    3564 K|    5576 K|    1884 K|    2064 K|       8|
|7232|Explorer.EXE        |           |   28532 K|   45316 K|   30488 K|   32508 K|      26|
|5860|vmtoolsd.exe        |           |    6004 K|   12512 K|    6204 K|    6296 K|      13|
|3824|MagicDisc.exe       |           |    3208 K|    6812 K|    3000 K|    3176 K|       1|
|5600|mmc.exe             |           |    9244 K|   28268 K|   21772 K|   21892 K|      14|
|7952|msg_server.EXE      |[MS] CRD_00|   27324 K|   32816 K|   34368 K|   34636 K|       8|
|8020|conhost.exe         |           |    1244 K|    3152 K|    1216 K|    1332 K|       0|
|5756|disp+work.EXE       |[DP] CRD_00|   25144 K| 126440 K| 107700 K| 109536 K|      32|
|3588|igswd.EXE           |[**] CRD_00|    3740 K|    7808 K|    5252 K|    6364 K|       2|
|5844|conhost.exe         |           |    1300 K|    3340 K|    1224 K|    1340 K|       1|
|6536|conhost.exe         |           |    1244 K|    3172 K|    1216 K|    1332 K|       0|
|7272|igsmux.exe          |           |   30968 K|   30968 K|   37552 K|   37552 K|       9|
|7636|igspw.exe           |           |   30356 K|   38880 K|   39248 K|   39404 K|      37|
|1316|igspw.exe           |           |   30408 K|   38924 K|   39428 K|   39584 K|      37|
| 732|gwrd.EXE            |[GW] CRD_00|   11736 K|   20188 K|   15120 K|   15420 K|       7|
|3908|icman.EXE           |[**] CRD_00| 109388 K| 118116 K| 116920 K| 117744 K|      29|
|7264|disp+work.EXE       |[WP] CRD_00| 139528 K| 444572 K| 133204 K| 242864 K|    2417|
|7620|disp+work.EXE       |[WP] CRD_00|   34728 K| 506312 K| 121364 K| 368924 K|    1174|
|3620|disp+work.EXE       |[WP] CRD_00| 141068 K| 309044 K| 129432 K| 243256 K|    2035|
|7140|disp+work.EXE       |[WP] CRD_00| 148012 K| 289512 K| 125064 K| 257388 K|    2123|
|7296|disp+work.EXE       |[WP] CRD_00|   29664 K|   77940 K| 117004 K| 117272 K|      19|
|5884|disp+work.EXE       |[WP] CRD_00| 149536 K| 592744 K| 127968 K| 309976 K|   11517|
|5236|disp+work.EXE       |[WP] CRD_00| 148264 K| 259552 K| 133824 K| 155352 K|    3329|
|7864|disp+work.EXE       |[WP] CRD_00| 130780 K| 307832 K| 135488 K| 294336 K|    2179|
|7980|disp+work.EXE       |[WP] CRD_00|   32088 K| 239100 K| 118672 K| 118940 K|      65|
|3996|disp+work.EXE       |[WP] CRD_00|   28664 K|   57556 K| 116188 K| 116344 K|      14|
|6140|disp+work.EXE       |[WP] CRD_00|   31348 K| 105800 K| 118016 K| 118172 K|      26|
|7968|disp+work.EXE       |[WP] CRD_00|   27988 K|   54684 K| 115096 K| 115240 K|      13|
|7584|disp+work.EXE       |[WP] CRD_00|   35656 K| 150072 K| 123180 K| 132752 K|      71|
|7856|disp+work.EXE       |[WP] CRD_00|   75496 K| 397344 K| 128608 K| 257352 K|     352|
|6992|disp+work.EXE       |[WP] CRD_00|   34324 K|   97024 K| 121640 K| 121904 K|      31|
|8032|disp+work.EXE       |[WP] CRD_00|   31456 K|   85396 K| 119484 K| 119632 K|      24|
|6196|disp+work.EXE       |[WP] CRD_00|   35688 K| 213644 K| 123180 K| 123632 K|      80|
| 628|disp+work.EXE       |[WP] CRD_00|   30756 K|   73208 K| 118884 K| 119040 K|      20|
|3684|disp+work.EXE       |[WP] CRD_00|   41876 K|   69024 K| 117412 K| 117688 K|     166|
|5456|disp+work.EXE       |[WP] CRD_00|   28516 K|   55980 K| 116140 K| 116296 K|      13|
|5580|jcontrol.EXE        |[**] CDJ_02|    4960 K|   18960 K|   11776 K|   16620 K|       7|
|3608|igswd.EXE           |[**] CDJ_02|    2948 K|    7460 K|    4120 K|    5680 K|       2|
|7480|conhost.exe         |           |    1236 K|    3168 K|    1212 K|    1332 K|       0|
|4768|conhost.exe         |           |    1248 K|    3168 K|    1216 K|    1332 K|       0|
|5760|igsmux.exe          |           |   21512 K|   21512 K|   27372 K|   27372 K|       6|
|6996|igspw.exe           |           |   30516 K|   39044 K|   39524 K|   39716 K|      37|
|3508|igspw.exe           |           |   30244 K|   38752 K|   38560 K|   38712 K|      37|
|3368|msg_server.EXE      |[MS] CDJ_03|    9588 K|   15004 K|   15408 K|   15560 K|       3|
|7260|enserver.EXE        |[**] CDJ_03|   17396 K|   25324 K|   62652 K|   62800 K|       6|
|2376|conhost.exe         |           |    1240 K|    3144 K|    1212 K|    1332 K|       0|
|6884|conhost.exe         |           |    1244 K|    3148 K|    1216 K|    1332 K|       0|
|4264|cmd.exe             |           |    1132 K|    3176 K|    2372 K|    3468 K|       0|
|5196|conhost.exe         |           |    1472 K|    3840 K|    1332 K|    1452 K|       1|
|5800|jlaunch.exe         |           | 157752 K| 236956 K| 411928 K| 423684 K|      96|
|3636|jlaunch.exe         |           | 892232 K| 909720 K| 2438664 K| 2459780 K|     428|
|5216|jlaunch.exe         |           | 161616 K| 175812 K| 209044 K| 211344 K|      64|
|5928|cmd.exe             |           |    1176 K|    3156 K|    2408 K|    3504 K|       0|
|7672|conhost.exe         |           |    1448 K|    3600 K|    1312 K|    1428 K|       1|
|2732|java.exe            |           | 300320 K| 328740 K| 405232 K| 422776 K|     161|
|5192|iexplore.exe        |           |   16248 K|   31204 K|   11508 K|   12872 K|      11|
|6364|IEXPLORE.EXE        |           |   16700 K|   35472 K|   15356 K|   19092 K|      11|
| 256|javaw.exe           |           | 130904 K| 187428 K| 293136 K| 355476 K|     288|
|2812|SAPup.exe           |           | 151960 K| 372148 K| 150948 K| 367436 K|     848|
|6876|conhost.exe         |           |    1112 K|    3032 K|    1176 K|    3180 K|       0|
|2276|saposcol.exe        |           |   18312 K|   22844 K|   20364 K| 1390432 K|      71|
|6908|sapstartsrv.exe     |           |   84424 K|   84424 K| 109840 K| 169528 K|      52|
|9108|sapcontrol.exe      |           |   12176 K|   12176 K|    9588 K|    9588 K|       3|
|3504|conhost.exe         |           |    3072 K|    3072 K|    1196 K|   34964 K|       0|
|5628|msg_server.EXE      |[MS] CRD_04|   14264 K|   14264 K|   15384 K|   15388 K|       3|
|5572|conhost.exe         |           |    3108 K|    3108 K|    1212 K|    1212 K|       0|
|8888|enserver.EXE        |[**] CRD_04|   41128 K|   41128 K|   17576 K|   17580 K|      10|
|8412|conhost.exe         |           |    3104 K|    3104 K|    1216 K|    1216 K|       0|
|8608|disp+work.EXE       |           |   49264 K|   49264 K|   80656 K|   85836 K|      20|
|9088|conhost.exe         |           |    3116 K|    3116 K|    1212 K|    1212 K|       0|
|----|--------------------|-----------|----------|----------|----------|----------|--------|
|    |Sum                 |           | 3883240 K|**********| 7343856 K|**********|********|
Tue Jan 13 08:53:57 2015
*** Error 11 while initializing OS dependent part.
*** ERROR => DpEmInit: EmInit (1) [dpxxdisp.c   10995]
*** ERROR => DpMemInit: DpEmInit (-1) [dpxxdisp.c   10909]
*** DP_FATAL_ERROR => DpSapEnvInit: DpMemInit
*** DISPATCHER EMERGENCY SHUTDOWN ***
increase tracelevel of WPs
NiWait: sleep (10000ms) ...
NiISelect: timeout 10000ms
NiISelect: maximum fd=1
NiISelect: read-mask is NULL
NiISelect: write-mask is NULL
Tue Jan 13 08:54:07 2015
NiISelect: TIMEOUT occured (10000ms)
dump system status
Workprocess Table (long)   Tue Jan 13 13:54:07 2015
========================
No Type Pid    Status Cause Start Rstr Err Sem Time Program          Cl User         Action                    Table
Dispatcher Queue Statistics   Tue Jan 13 13:54:07 2015
===========================
+------+--------+--------+--------+------------+------------+
| Typ |    now |   high |    max | writes     | reads     |
+------+--------+--------+--------+------------+------------+
| NOWP |      0 |      0 |   2000 |          0 |          0 |
+------+--------+--------+--------+------------+------------+
| DIA |      0 |      0 |   2000 |          0 |          0 |
+------+--------+--------+--------+------------+------------+
| UPD |      0 |      0 |   2000 |          0 |          0 |
+------+--------+--------+--------+------------+------------+
| ENQ |      0 |      0 |   2000 |          0 |          0 |
+------+--------+--------+--------+------------+------------+
| BTC |      0 |      0 |   2000 |          0 |          0 |
+------+--------+--------+--------+------------+------------+
| SPO |      0 |      0 |   2000 |          0 |          0 |
+------+--------+--------+--------+------------+------------+
| UP2 |      0 |      0 |   2000 |          0 |          0 |
+------+--------+--------+--------+------------+------------+
max_rq_id 0
wake_evt_udp_now 0
wake events       total     0, udp     0 ( 0%), shm     0 ( 0%)
since last update total     0, udp     0 ( 0%), shm     0 ( 0%)
Dump of tm_adm structure:   Tue Jan 13 13:54:07 2015
=========================
Term    uid man user    term   lastop mod wp ta   a/i (modes)
Workprocess Comm. Area Blocks   Tue Jan 13 13:54:07 2015
=============================
Slots: 1000, Used: 0, Max: 0
+------+--------------+----------+-------------+
|   id | owner        |   pid    | eyecatcher |
+------+--------------+----------+-------------+
NiWait: sleep (5000ms) ...
NiISelect: timeout 5000ms
NiISelect: maximum fd=1
NiISelect: read-mask is NULL
NiISelect: write-mask is NULL
Tue Jan 13 08:54:12 2015
NiISelect: TIMEOUT occured (5000ms)
DpHalt: shutdown server >SAPCRMDEV_CRD_04                        < (normal)
DpJ2eeDisableRestart
DpHalt: switch off Shared memory profiling
ShmProtect( 57, 3 )
ShmProtect(SHM_PROFILE, SHM_PROT_RW
ShmProtect( 57, 1 )
ShmProtect(SHM_PROFILE, SHM_PROT_RD
DpWakeUpWps: wake up all wp's
DpHalt: stop work processes
DpHalt: terminate gui connections
DpHalt: wait for end of work processes
DpHalt: not attached to the message server
DpHalt: cleanup EM
EsCleanup( )
EsCleanup ....
EmCleanup() -> 0
Es2Cleanup: Cleanup ES2
***LOG Q05=> DpHalt, DPStop ( 8608) [dpxxdisp.c   11819]
DpHalt: Good Bye .....
trc file: "dev_ms", trc level: 1, release: "721"
[Thr 8464] Tue Jan 13 08:53:49 2015
[Thr 8464] ms/http_max_clients = 500 -> 500
[Thr 8464] MsSSetTrcLog: trc logging active, max size = 52428800 bytes
systemid   562 (PC with Windows NT)
relno      7210
patchlevel 0
patchno    327
intno      20020600
make       multithreaded, Unicode, 64 bit, optimized
pid        5628
[Thr 8464] ***LOG Q01=> MsSInit, MSStart (Msg Server 1 5628) [msxxserv.c   2305]
[Thr 8464] MsInitAclInfo: acl file F:\SUM\SUM\abap\system\CRD\SYS\global\ms_acl_info.DAT not found, unrestricted access
[Thr 8464] MsGetOwnIpAddr: my host addresses are :
[Thr 8464]   1 : [192.168.200.142] SAPCRMDEV.CRESTRON.CRESTRON.com (HOSTNAME)
[Thr 8464]   2 : [127.0.0.1] SAPCRMDEV.CRESTRON.CRESTRON.com (LOCALHOST)
[Thr 8464] MsHttpInit: full qualified hostname = SAPCRMDEV.CRESTRON.CRESTRON.com
[Thr 8464] HTTP logging is switch off
[Thr 8464] MsHttpOwnDomain: own domain[1] = CRESTRON.CRESTRON.com
[Thr 8464] *** I listen to port 3604 (3604) ***
[Thr 8464] *** I listen to internal port 3904 (3904) ***
[Thr 8464] CUSTOMER KEY: >G0021204657<
[Thr 8464] build version=721.2014.07.17
Thanks,
Kavitha Rajan.

Hi Kavitha,
Hope you are doing good.
Looks like a memory issue:
EsNT> Memory Reset disabled as NT default
*** ERROR => <EsNT> CreateFileMapping name=Global\ES_SEG_04_003 ,size=2044 MB, error=1455 [esnti.c      1278]
Tue Jan 13 08:53:57 2015
*** Error 11 while initializing OS dependent part.
*** ERROR => DpEmInit: EmInit (1) [dpxxdisp.c   10995]
*** ERROR => DpMemInit: DpEmInit (-1) [dpxxdisp.c   10909]
*** DP_FATAL_ERROR => DpSapEnvInit: DpMemInit
First restart Windows and then try to start the SAP system from the MMC.If that doesn't help then increase the pagefile size and restart the Windows.
Kind Regards,
Hemanth
SAP AGS

Sap not starting during manual failover testing

Similar Messages

Maybe you are looking for