Installation Problem for ERP 6.0 SR3

[Former Member]

Hello Experts,

I am installing SAP ERP 6.0 SR3 on Windows Server 2003 64 bit for MAXDB 7.7 Version.

Steps: I have followed below steps for both machine.

1. Define Swap space = RAM * 3

2. Installed win Server SP2

3. Installed j2sdk1.4.2_18 and Set Env variables of java

4. Run SAP.EXE and set path of exports,kernel,RDBMS 7.7.

First I have installaled DEMO machine and machine configuration is

6 GB RAM

Intel Dual Core Processor (Desktop Board )

250 GB harddisk

After installation it is working file.

I have run R3Trans . it is working fine. I have checked sap remote connection also.

After succefully installation on demo machine.

I have been installed on Live server. Please see below server Details. Installation was done succesfully.

manufactured : DELL Inc.

System Type : PowerEdge T410

Raid 5 Configuration

8 GB Ram

Intel Xeon CPU

2.4 GHz

But SAP Application could not connect with database. I used " R3Trans -d " command. It is not showing anything.

disp+work.exe is not working and all work processes are in run mode.

Question:

Is it any hardware issue or sap application issue or Database issue ? I am not geeting proper answer still

Please suggest me from above details and let me know it is very valuable for me.

Answer will be appriciated.

Thanks,

Rahul S.

[former_member709110]

Assuming that there was no error reported during the installation ... and now the system is not coming up properly

1. Check if the message service is running or not

2. Check if other process are running or not

3. Final check the message , dispatcher and work process logs under the work directory

I am sure you will find error message in the logs

Regards,

Neel

[Former Member]

Hello,

As per your suggestion,

msg_server.exe is running properly.

igswd.exe is running properly.

but disp+work.exe is not connected. it is stand still.

and login with <SID>adm users.

Thanks,

[Former Member]

did you restart OS? i don't think this is good idea but try to do that. and also paste the dev_w0 log.

[Former Member]

Yes I have restarted OS and login with <SID>ADM user.

-

---

trc file: "dev_w0", trc level: 1, release: "700"

-

---

*

• ACTIVE TRACE LEVEL 1

• ACTIVE TRACE COMPONENTS all, MJ

*

B

B Thu Feb 03 11:22:46 2011

B create_con (con_name=R/3)

B Loading DB library 'F:\usr\sap\LS1\DVEBMGS00\exe\dbsdbslib.dll' ...

B Library 'F:\usr\sap\LS1\DVEBMGS00\exe\dbsdbslib.dll' loaded

B Version of 'F:\usr\sap\LS1\DVEBMGS00\exe\dbsdbslib.dll' is "700.08", patchlevel (0.144)

B New connection 0 created

M sysno 00

M sid LS1

M systemid 562 (PC with Windows NT)

M relno 7000

M patchlevel 0

M patchno 144

M intno 20050900

M make: multithreaded, Unicode, 64 bit, optimized

M pid 2824

M

M kernel runs with dp version 232000(ext=109000) (@(#) DPLIB-INT-VERSION-232000-UC)

M length of sys_adm_ext is 576 bytes

M ***LOG Q0Q=> tskh_init, WPStart (Workproc 0 2824) [dpxxdisp.c 1305]

I MtxInit: 30000 0 0

M DpSysAdmExtCreate: ABAP is active

M DpSysAdmExtCreate: VMC (JAVA VM in WP) is not active

M DpShMCreate: sizeof(wp_adm) 25168 (1480)

M DpShMCreate: sizeof(tm_adm) 5652128 (28120)

M DpShMCreate: sizeof(wp_ca_adm) 24000 (80)

M DpShMCreate: sizeof(appc_ca_adm) 8000 (80)

M DpCommTableSize: max/headSize/ftSize/tableSize=500/16/552064/552080

M DpShMCreate: sizeof(comm_adm) 552080 (1088)

M DpSlockTableSize: max/headSize/ftSize/fiSize/tableSize=0/0/0/0/0

M DpShMCreate: sizeof(slock_adm) 0 (104)

M DpFileTableSize: max/headSize/ftSize/tableSize=0/0/0/0

M DpShMCreate: sizeof(file_adm) 0 (72)

M DpShMCreate: sizeof(vmc_adm) 0 (1864)

M DpShMCreate: sizeof(wall_adm) (41664/36752/64/192)

M DpShMCreate: sizeof(gw_adm) 48

M DpShMCreate: SHM_DP_ADM_KEY (addr: 000000000EE70050, size: 6348592)

M DpShMCreate: allocated sys_adm at 000000000EE70050

M DpShMCreate: allocated wp_adm at 000000000EE72150

M DpShMCreate: allocated tm_adm_list at 000000000EE783A0

M DpShMCreate: allocated tm_adm at 000000000EE78400

M DpShMCreate: allocated wp_ca_adm at 000000000F3DC2A0

M DpShMCreate: allocated appc_ca_adm at 000000000F3E2060

M DpShMCreate: allocated comm_adm at 000000000F3E3FA0

M DpShMCreate: system runs without slock table

M DpShMCreate: system runs without file table

M DpShMCreate: allocated vmc_adm_list at 000000000F46AC30

M DpShMCreate: allocated gw_adm at 000000000F46ACB0

M DpShMCreate: system runs without vmc_adm

M DpShMCreate: allocated ca_info at 000000000F46ACE0

M DpShMCreate: allocated wall_adm at 000000000F46ACF0

M ThTaskStatus: rdisp/reset_online_during_debug 0

X EmInit: MmSetImplementation( 2 ).

X MM global diagnostic options set: 0

X <ES> client 0 initializing ....

X Using implementation view

X <EsNT> Using memory model view.

M <EsNT> Memory Reset disabled as NT default

X ES initialized.

M

M Thu Feb 03 11:22:47 2011

M ThInit: running on host LOELS1CI

M

M Thu Feb 03 11:22:48 2011

M calling db_connect ...

C

C DBSDBSLIB : version 700.08, patch 0.144 (Make PL 0.144)

C MAXDB shared library (dbsdbslib) patchlevels (last 10)

C (0.144) MSSQL: ODBC fastload on separate connection (note 1131805)

C (0.144) I5/OS ldappasswd support for 5250 terminal. (note 1129573)

C (0.139) Return DS_SQLERR instead of DS_CONNECTERR (note 1121076)

C (0.131) Do not trace password of SQLOPT into dev trace (note 1097930)

C (0.130) Performance optimization for UPDSTAT PREPARE (note 1096387)

C (0.125) Update statistic prepare on row level (note 1086430)

C (0.104) Update statistic with empty schemas (note 1041547)

C (0.095) MaxDB DBSL patch collection 1 2007 (note 1014270)

C (0.082) MaxDB DBSL patch collection 3 2006 (note 991258)

C (0.079) MaxDB DBSL patch collection 2 2006 (note 984406)

C

C

C Loading SQLDBC client runtime ...

C SQLDBC SDK Version : SQLDBC.H 7.6.0 BUILD 007-123-091-175

C SQLDBC Library Version : libSQLDBC 7.6.5 BUILD 015-123-202-938

C SQLDBC client runtime is MaxDB 7.6.5.015 CL 202938

C SQLDBC supports new DECIMAL interface : 0

C SQLDBC supports VARIABLE INPUT data : 1

C SQLDBC supports keepAlive indicator : 0

C INFO : SQLOPT= -I 0 -t 0 -S SAPR3

C Try to connect (DEFAULT) on connection 0 ...

C Attach to SAP DB : Kernel 7.7.06 Build 010-123-204-327

C Database release is SAP DB 7.7.06.010

C INFO : Database 'LS1' instance is running on 'LOELS1CI'

C INFO : SAP DB Packet_Size = 131072

C INFO : SAP DB Min_Reply_Size = 4096

C INFO : SAP DB Comm_Size = 126976

C INFO : DBSL buffer size = 126976

C INFO : SAP DB MaxLocks = 300000

C INFO : Connect to DB as 'SAPLS1'

C Command info enabled

C Now I'm connected to SAP DB

C 00: LOELS1CI-LS1, since=20110203112248, ABAP= <unknown> (0)

B Connection 0 opened (DBSL handle 0)

B Wp Hdl ConName ConId ConState TX PRM RCT TIM MAX OPT Date Time DBHost

B 000 000 R/3 000000000 ACTIVE NO YES NO 000 255 255 20110203 112248 LOELS1CI

C INFO : SAP RELEASE (DB) = 700

M db_connect o.k.

M ICT: exclude compression: .zip,.cs,.rar,.arj,.z,.gz,.tar,.lzh,.cab,.hqx,.ace,.jar,.ear,.war,.css,.pdf,.js,.gzip,.uue,.bz2,.iso,.sda,.sar,.gif

[Former Member]

Problem is solved.

When I checked database datafile and log files, Log file is full / 100%.

I added one more logfile and then sap worked fine.

Thanks your supportive answers.

Rahul S.

[nirmal_konchada]

Hi,

Seems to be a problem wqith the environment for SIDadm and oraSID users.

Please check.

Regards,

Nirmal.K