cancel
Showing results for 
Search instead for 
Did you mean: 

Cannot start SAP after Linux upgrade

Former Member
0 Kudos

We have an ECC application server running on an OEL5.

Recently this OEL5 has been upgraded to OEL6.

We also upgraded the kernel to patch level 526 per PAM.

Now startsap throws out an error:

bloosom:devadm 22> more stderr0

(10819) New Child Process created.

(10819) Starting local Command:

Command:  dw.sapDEV_D16

           pf=/sapmnt/DEV/profile/DEV_D16_bloosom

Thu Sep 24 11:04:27 2015

DpShmPrfCreate : created shared memory at 7fdafb06c000, 1807 entries (1673256 bytes)

Thu Sep 24 11:04:28 2015

ES/TABLE = UNIX_STD

***

*** DISPATCHER EMERGENCY SHUTDOWN => DpSapEnvInit: DpIPCInit2

Many people fixed above error by rebooting server. But it does not work for me.

Thanks if can help.

Accepted Solutions (1)

Accepted Solutions (1)

IanSegobio
Advisor
Advisor
0 Kudos

Hello Qiyong,

After restarting sapstartsrv process in order for it to get the new environment, you should be able to start the instance normaly using the sapcontrol web method:

sapcontrol -nr <instance number> -function Start

Cheers,
Ian Segobio.

Former Member
0 Kudos

Friends:

Thanks for your input.

Now I can start the DI with following change:

In script startsap , after the line sapstartsrv I added following lines:

sleep 25

cd /usr/sap/DEV/D16/work

dw.sapDEV_D16 pf=/sapmnt/DEV/profile/DEV_D16_bloosom

above sleep 25 is to wait for the link /usr/sap/DEV/D16/work/dw.sapDEV_D16->disp+work to be created.

I am not happy about above method. Please advise.

Regards to all.

Former Member
0 Kudos

Dear Friends:

This has been fixed.

The cause is that /etc/csh.login was corrupted. I copied it from other AS and now it's working.

Thanks!!

Answers (3)

Answers (3)

Sriram2009
Active Contributor
0 Kudos

Hi Zeng

Just do the full restart and then check the SAP application sever, Check this SCN thread with same issue.

BR

SS

Former Member
0 Kudos

Thanks to all for help.

This problem is still unsolved.

I notice that in dev_w## log following error:

C  Client NLS setting (OCINlsGetInfo): connection handle 0, 'AMERICAN_AMERICA.UTF16'

C  Logon as OPS$-user to get SAPR3's password

C  Connecting as /@DEV on connection 0 (nls_hdl 0) ... (dbsl 720 140910)

C  Nls CharacterSet                 NationalCharSet              Env        Err        ErrBt   

C    0 UTF8                                                      90b7410 90bef10 90d1698

C  Attaching to database server DEV (con=0, svchp=90d15c8, srvhp=90d3d68)

C     OCIServerAttach(OCI_DEFAULT) failed with SQL error 12154:

C     ORA-12154: TNS:could not resolve the connect identifier specified                                                       

C  *** ERROR => CONNECT failed with sql error '12154'

That "Connecting as /@DEV"  should be "Connecting as /@DEV_SAP"

The reasons are:

1) R3trans -x RC=0000, trans.log shows:

   Connecting as /@DEV_SAP

2) on other application servers for the SAME ECC system, the dev_w## shows:

   "Connecting as /@DEV_SAP"

   and free of ORA-12154 error

3) in tnsnames.ora, both DEV and DEV_SAP are defined as independent entries,

   but only DEV_SAP is pointing to the correct DB host.

What is very strange is that we have env variable DB_SID=DEV_SAP for devadm,

when running startsap we see the output:

...

checking DEV_SAP database

...

database is running

...

But in all dev_w## we still see "Connecting as /@DEV" , NOT "Connecting as /@DEV_SAP".

So it fails.

How to make sure disp+work picks up DEV_SAP?

Thanks for help.

PS. dboraslib.so used by R3trans and startsap has the same size and time stamp (721

patch level 216)

Sriram2009
Active Contributor
0 Kudos

Hi Zeng

Could you refer the SAP KBA's for error message "ERROR CONNECT failed with sql error 12154

1860519 - SAP fails to connect to the database

  2153975 - Database connectivity fails with ORA-12154


BR

SS

Former Member
0 Kudos

Hi Zeng,

Also do verify your schema password and try to avoid special character "@" in password which causes issues.

Do let us know the current status.

Regards,

Ram

Former Member
0 Kudos

Thanks to all.

I have found out this discrepancy:

bloosom:devadm 63> !50

sapcontrol -nr 16 -function GetEnvironment | grep PATH

PATH=/usr/local/bin:/bin:/usr/bin

LD_LIBRARY_PATH=/usr/sap/DEV/SYS/exe/run

bloosom:devadm 64> env|grep PATH

PATH=/usr/local/bin:/bin:/usr/bin:/usr/X11R6/bin:/opt/IBMJava2-amd64-142/bin:/oracle/GRID/112_64/bin:/oracle/sapctl/bin:/usr/sap/DEV/SYS/exe/uc/linuxx86_64:/usr/sap/DEV/SYS/exe/run:/home/devadm:.

LD_LIBRARY_PATH=/opt/CA/SharedComponents/lib:/usr/sap/DEV/SYS/exe/uc/linuxx86_64:/usr/sap/DEV/SYS/exe/run:/oracle/client/10x_64/instantclient:/usr/sap/DEV/hdbclient

We see that run-time env is wrong. I have edited profile (note 1825259)  and have edited .*csh files in devadm home directory, but cannot fix above difference.

Thanks! Any idea?

BTW, on its sister application servers, both commands give consistent results:

PATH=/usr/local/bin:/bin:/usr/bin:/usr/X11R6/bin:/opt/IBMJava2-amd64-142/bin:/oracle/GRID/112_64/bin:/oracle/sapctl/bin:/usr/sap/DEV/SYS/exe/uc/linuxx86_64:/usr/sap/DEV/SYS/exe/run:/home/devadm:.

LD_LIBRARY_PATH=/opt/CA/SharedComponents/lib:/usr/sap/DEV/SYS/exe/uc/linuxx86_64:/usr/sap/DEV/SYS/exe/run:/oracle/client/10x_64/instantclient:/usr/sap/DEV/hdbclient

Former Member
0 Kudos

Hi Zeng,

Do check the devadm .profile in the home directory if it is correctly modified and with right permission.

Also verify the user default shell is /usr/bin/csh in /etc/passwd.

Do let us know if this help.

Regards,

Ram

isaias_freitas
Advisor
Advisor
0 Kudos

Have you restarted the sapstartsrv process?

It will take the new environment only after being restarted.

You can stop it with

sapcontrol -nr 16 -function StopService

After no SAP process is running, you can try starting SAP as usual.

Former Member
0 Kudos

-rw-r-----   1 devadm sapsys  1624 Sep 25 12:11 .profile

above permission is the same for all sister application servers.

devadm:x:4700:400:devadm functional ID:/home/devadm:/bin/csh

above default is the same for all sister application servers.



Our problem is that sapstartsrv does not have the right env, e.g. TNS_ADMIN defined:

Upgraded system:

bloosom:devadm 14> sapcontrol -nr 16 -function GetEnvironment | grep TNS

nothing returned

bloosom:ndevadm 15> env|grep TNS

TNS_ADMIN=/sapmnt/DEV/profile/oracle



non-upgraded sister application server:

cherrywood:devadm 60> sapcontrol -nr 15 -function GetEnvironment | grep TNS

TNS_ADMIN=/sapmnt/DEV/profile/oracle

cherrywood:devadm 61> env|grep TNS

TNS_ADMIN=/sapmnt/DEV/profile/oracle





Per 1860519

Check SAP Note 1825259 and make sure the sapstartsrv environment contains at least the following variables properly set:

  • TNS_ADMIN (pointing to valid tnsnames.ora, usually under /usr/sap/<SID>/SYS/profile/oracle)
  • LD_LIBRARY_PATH or LIBPATH (containing DIR_LIBRARY and the path to the Oracle Instant client)

I did accordingly but still same error.

Former Member
0 Kudos

I did

sapcontrol -nr 16 -function StopService


then:


sapcontrol -nr 16 -function StartService DEV


still the same error. 


Thanks!

Former Member
0 Kudos

Friends,

Now I bring SAP up using this way:

disp+work pf=instance profile.

But this is not the right way, please advise how to improve? i.e. how to use startsap

to start it?

Thanks.

IanSegobio
Advisor
Advisor
0 Kudos

Hello there,

Please check the section "IX. MULTICAST ERROR:" from the SAP wiki for startup issues:

SAP Startup Troubleshooting Guide for Netweaver Application Server - Application Server Infrastructu...

Cheers,
Ian Segóbio.

manumohandas82
Active Contributor
0 Kudos

Hi  ,

Please supply the following logs from your  work directory  (/usr/sap/<SID>/DV<>/work )

dev_disp

dev_w0

Thanks ,

Manu