After Kernel upgrade to 720, Oracle database doesn't start with startsap.

[Former Member]

Hello,

after kernel upgrade to 720, I can't start sap.

Oracle database doesn't start with startsap.

I must start the database first seperatly and after that I can start sap with startsap.

Can anybody advise me how i solve this problem.

regards,

[Former Member · Accepted solution]

Hi all,

I have solved the problem. After I restart the listener , I could restart sap with startsap properly.

Thanks for your support

[kundangandhi]

Hi,

Have to changed kernel to All required location?

Else do it manucally and start it

Sometime sapscp will not work to copy kernel @ required location

1. <drive>\usr\sap\<SID>\SYS

2. <Drive>\usr\sap\<SID>\DVEBMGS<no>

3. <Drive>\usr\sap\<SID>\ASCS<no>

Thanks,

Kundan Gandhi

[Former Member]

Hi Shatti,

Please share the kernel version and patch level from which u upgraded

[Former Member]

Hi,

Try to start first the listener and then sapstart.

Regards.

[divyanshu_srivastava3]

That is expected, atleast.

[divyanshu_srivastava3]

Share the log files.. also from which version of kernel have you updated to 720.

Check for database profile parameters and environment variables, if kernel has right DBSL.

That's all is needed to resolve this.

[divyanshu_srivastava3]

Run runtrans -d from sidadm, share trans.log if return code is not 0000

Share /home/sidadm/startdb.log

[divyanshu_srivastava3]

Typo - run R3trans -d

[Former Member]

lmtaix006:plhadm 48> R3trans -d

This is R3trans version 6.24 (release 720 - 04.02.14 - 20:14:02 ).

unicode enabled version

R3trans finished (0000).

[divyanshu_srivastava3]

Check ora_home for sidadm and run root.sh.

[divyanshu_srivastava3]

Have a look at this

http://service.sap.com/sap/support/notes/583861

1837499 - startsap/stopsap script not able to start or stop DB

1859915 - startsap 7.20/7.20 EXT: Database is not started

809477 - startsap/stopsap for SAP WebAs 640, 700, 701, 710, 711, 720

[divyanshu_srivastava3]

Did you follow the above KBAs for resolution.

I think they can help you, please have a look at them.

[Former Member]

can you help me here? I do not know what I have to do.

regards,

[divyanshu_srivastava3]

Hi Shatti,

I asked you share startdb .logs.

Are these logs generated ?

Divyanshu

[Former Member]

Hi Divyanshu,

here the startdb.log:

lmtaix006:plhadm 3> more startdb.log

------------------------------ Fri Aug 8 16:03:02 CEST 2014

LOGFILE FOR STARTING ORACLE

Trying to start PLH database ...

------------------------------ Fri Aug 8 16:03:02 CEST 2014

checking required environment variables

ORACLE_HOME  is >/oracle/PLH/11202<

ORACLE_SID   is >PLH<

------------------------------ Fri Aug 8 16:03:02 CEST 2014

check spfile or initora

------------------------------ Fri Aug 8 16:03:02 CEST 2014

check initora

------------------------------ Fri Aug 8 16:03:02 CEST 2014

checking V2 connect

TNS Ping Utility for IBM/AIX RISC System/6000: Version 11.2.0.2.0 - Production on 08-AUG-2014 16:03:02

Copyright (c) 1997, 2010, Oracle.  All rights reserved.

Used parameter files:

/usr/sap/PLH/SYS/profile/oracle/sqlnet.ora

Used TNSNAMES adapter to resolve the alias

Attempting to contact (DESCRIPTION = (ADDRESS_LIST = (ADDRESS = (COMMUNITY = SAP.WORLD) (PROTOCOL = TCP) (HOST

= lmtaix006) (PORT = 1562))) (CONNECT_DATA = (SID = PLH) (GLOBAL_NAME = PLH.WORLD)))

OK (0 msec)

tnsping: V2 connect to PLH

------------------------------ Fri Aug 8 16:03:02 CEST 2014

Connect to the database to check the database state:

  -------------------------------------------------------------

Fri Aug 8 16:03:02 CEST 2014

check if Oracle processes are running

Database already running

check_db_running: check finished with return code: 0

Database already running

regards,

[divyanshu_srivastava3]

Hi,

Are these the latest logs ? If no, then share the latest log file.

If yes, then share latest startsap.log.

Also, when you give command startsap - what error do you see on screen.

Can you see startdb in kernel directory ?

Check default profile for parameter SAPDBHOST and if not set then set it. Before making changes take a backup of default profile.

Divyanshu

[Former Member]

Hi,

yes this are the latest log.

I can't restart the sap now, only on weekend!

Yes i see the startdb in the Kernel directory

-rwxr-xr-x

1 plhadm   sapsys

15648 Jul 18 15:46 startdb

The parameter SAPDBHOST is set!

[divyanshu_srivastava3]

Hi,

Did you downloaded database dependent kernel part i.e. SAPEXEDB ?

Anyway, share the last startsap.log also because that should have also noted the failure.

Regards,

Divyanshu

Divyanshu

[Former Member]

Did you downloaded database dependent kernel part i.e. SAPEXEDB ?

--> Yes

that's all I have.

I'm going on Friday the whole kernel upload one more time,

only then can I let you get all the logs!

regards,

[Former Member]

Hi Shatti,

Please Post the log file in the work directory "sapstartsrv" log

Regards,

Karthikeyan palani

[Former Member]

Hello Karthikeyan,

here the sapstartsrv.log:

lmtaix006:plhadm 37> more sapstartsrv.log

---------------------------------------------------

trc file: "sapstartsrv.log", trc level: 0, release: "720"

---------------------------------------------------

pid        8388744

[Thr 01] Fri Aug  8 16:03:07 2014

No halib defined => HA support disabled

CCMS agent initialization for instance type ABAP: return code 0.

CCMS agent start: return code 0.

Initializing SAPControl Webservice

Starting AutoRestart thread

[Thr 515] Fri Aug  8 16:03:13 2014

AutoRestart thread started

Starting WebService SSL thread

Webservice SSL thread started, listening on port 56214

Starting WebService thread

Webservice thread started, listening on port 56213

Trusted https connect via Unix domain socket '/tmp/.sapstream56214' enabled.

Trusted http connect via Unix domain socket '/tmp/.sapstream56213' enabled.

trusted unix domain socket user is starting SAP System at 2014/08/08 16:03:17

trusted unix domain socket user is stopping SAP System at 2014/08/08 16:04:36

trusted unix domain socket user is starting SAP System at 2014/08/08 16:05:39

startsap.log:

lmtaix006:plhadm 38> more sapstart.log

SAP-R/3-Startup Program Rel 720 V2.0 (2008/11/15)

-------------------------------------------------

Starting at 2014/08/08 16:05:39

Startup Profile: "/usr/sap/PLH/SYS/profile/START_DVEBMGS62_lmtaix006"

Setup Environment Variables

---------------------------

(43843830) SETENV LD_LIBRARY_PATH=/usr/sap/PLH/DVEBMGS62/exe:

(43843830) SETENV SHLIB_PATH=/usr/sap/PLH/DVEBMGS62/exe:

(43843830) SETENV LIBPATH=/usr/sap/PLH/DVEBMGS62/exe:/usr/sap/PLH/DVEBMGS62/exe:/usr/lib:/lib:/usr/s

ap/PLH/SYS/exe/run:/oracle/client/11x_64/instantclient

Execute Pre-Startup Commands

----------------------------

(32506010) Local: /usr/sap/PLH/SYS/exe/run/sapcpe pf=/usr/sap/PLH/SYS/profile/PLH_DVEBMGS62_lmtplh

(43843830) system(/usr/sap/PLH/SYS/exe/run/sapcpe pf=/usr/sap/PLH/SYS/profile/PLH_DVEBMGS62_lmtplh)

returns 4

(32506012) Local: /usr/sap/PLH/DVEBMGS62/exe/sapmscsa pf=/usr/sap/PLH/SYS/profile/PLH_DVEBMGS62_lmtp

lh -n

(32506014) Local: rm -f ms.sapPLH_DVEBMGS62

(32506016) Local: ln -s -f /usr/sap/PLH/DVEBMGS62/exe/msg_server ms.sapPLH_DVEBMGS62

(32506018) Local: rm -f dw.sapPLH_DVEBMGS62

(32506020) Local: ln -s -f /usr/sap/PLH/DVEBMGS62/exe/disp+work dw.sapPLH_DVEBMGS62

(32506022) Local: rm -f co.sapPLH_DVEBMGS62

(32506024) Local: ln -s -f /usr/sap/PLH/DVEBMGS62/exe/rslgcoll co.sapPLH_DVEBMGS62

(32506026) Local: rm -f se.sapPLH_DVEBMGS62

(32506028) Local: ln -s -f /usr/sap/PLH/DVEBMGS62/exe/rslgsend se.sapPLH_DVEBMGS62

(32506030) Local: rm -f ig.sapPLH_DVEBMGS62

(32506032) Local: ln -s -f /usr/sap/PLH/DVEBMGS62/exe/igswd_mt ig.sapPLH_DVEBMGS62

Starting Programs

-----------------

(32506036) Starting: local ms.sapPLH_DVEBMGS62 pf=/usr/sap/PLH/SYS/profile/PLH_DVEBMGS62_lmtplh

(41156614) Starting: local dw.sapPLH_DVEBMGS62 pf=/usr/sap/PLH/SYS/profile/PLH_DVEBMGS62_lmtplh

(32506036) New Child Process created.

(32506036) Starting local Command:

Command:  ms.sapPLH_DVEBMGS62

           pf=/usr/sap/PLH/SYS/profile/PLH_DVEBMGS62_lmtplh

(29819028) Starting: local co.sapPLH_DVEBMGS62 pf=/usr/sap/PLH/SYS/profile/PLH_DVEBMGS62_lmtplh -F

(41156614) New Child Process created.

(41156614) Starting local Command:

Command:  dw.sapPLH_DVEBMGS62

           pf=/usr/sap/PLH/SYS/profile/PLH_DVEBMGS62_lmtplh

(29819028) New Child Process created.

(29819028) Starting local Command:

Command:  co.sapPLH_DVEBMGS62

           pf=/usr/sap/PLH/SYS/profile/PLH_DVEBMGS62_lmtplh

           -F

(25559098) Starting: local se.sapPLH_DVEBMGS62 pf=/usr/sap/PLH/SYS/profile/PLH_DVEBMGS62_lmtplh -F

(25559098) New Child Process created.

(25559098) Starting local Command:

Command:  se.sapPLH_DVEBMGS62

           pf=/usr/sap/PLH/SYS/profile/PLH_DVEBMGS62_lmtplh

           -F

(42598466) Starting: local ig.sapPLH_DVEBMGS62 -mode=profile pf=/usr/sap/PLH/SYS/profile/PLH_DVEBMGS

62_lmtplh

(43843830) Waiting for Child Processes to terminate.

(42598466) New Child Process created.

(42598466) Starting local Command:

Command:  ig.sapPLH_DVEBMGS62

           -mode=profile

           pf=/usr/sap/PLH/SYS/profile/PLH_DVEBMGS62_lmtplh

I updated the kernel from 700 to 720

[Sriram2009]

Hi

If possible do the full system restart, after that start first Oracle DB & then SAP

BR

SS

[Former Member]

I updated the kernel from 640 to 720 and not from 700

[Reagan]

If the BASIS is release is not 700 and above then you cannot use SAP kernel 720.

You should instead use kernel 640 EXT release.

[Former Member]

I use SAP Kernel 720_REL and the basis release is 700

[Reagan]

Provide me the output of this command.

su - plhadm

sapcontrol -nr 62 -function GetVersionInfo

Regards

RB

[Former Member]

Hi Reagan,

here the output:

lmtaix006:plhadm 1> sapcontrol -nr 62 -function GetVersionInfo

12.08.2014 08:35:56

GetVersionInfo

OK

Filename, VersionInfo, Time

/usr/sap/PLH/DVEBMGS62/exe/sapstartsrv, 720, patch 600, changelist 1480835, optu (Mar  8 2014, 07:23:29), rs6000_64, 2014 07 18 15:46:14

/usr/sap/PLH/DVEBMGS62/exe/disp+work, 720, patch 600, changelist 1480835, optu (Mar  8 2014, 00:38:38), rs6000_64, 2014 07 18 15:45:55

/usr/sap/PLH/DVEBMGS62/exe/gwrd, 720, patch 600, changelist 1480835, optu (Mar  8 2014, 00:38:38), rs6000_64, 2014 07 18 15:46:02

/usr/sap/PLH/DVEBMGS62/exe/msg_server, 720, patch 600, changelist 1480835, optu (Mar  8 2014, 07:23:29), rs6000_64, 2014 07 18 15:46:10

/usr/sap/PLH/DVEBMGS62/exe/dboraslib.o, 720, patch 600, changelist 1480835, optu (Mar  8 2014, 00:38:38), rs6000_64, 2014 07 18 15:45:52

/usr/sap/PLH/DVEBMGS62/exe/dbdb2slib.o, 720, patch 600, changelist 1480835, optu (Mar  8 2014, 00:38:38), rs6000_64, 2014 07 18 15:45:50

/usr/sap/PLH/DVEBMGS62/exe/dbdb4slib.o, 720, patch 600, changelist 1480835, optu (Mar  8 2014, 00:38:38), rs6000_64, 2014 07 18 15:45:50

/usr/sap/PLH/DVEBMGS62/exe/dbdb6slib.o, 720, patch 600, changelist 1480835, optu (Mar  8 2014, 00:38:38), rs6000_64, 2014 07 18 15:45:52

/usr/sap/PLH/DVEBMGS62/exe/dbsybslib.o, 720, patch 600, changelist 1480835, optu (Mar  8 2014, 00:38:38), rs6000_64, 2014 07 18 15:45:52

/usr/sap/PLH/DVEBMGS62/exe/enserver, 720, patch 600, changelist 1480835, optu (Mar  8 2014, 07:23:29), rs6000_64, 2014 07 18 15:46:02

/usr/sap/PLH/DVEBMGS62/exe/icman, 720, patch 600, changelist 1480835, optu (Mar  8 2014, 07:23:29), rs6000_64, 2014 07 18 15:46:02

/usr/sap/PLH/DVEBMGS62/exe/sapwebdisp, 720, patch 600, changelist 1480835, optu (Mar  8 2014, 07:23:29), rs6000_64, 2014 07 18 15:46:15

/usr/sap/PLH/DVEBMGS62/exe/jcontrol, 720, patch 600, changelist 1480835, optu (Mar  8 2014, 07:23:29), rs6000_64, 2014 07 18 15:46:03

/usr/sap/PLH/DVEBMGS62/exe/jlaunch, 720, patch 600, changelist 1480835, optu (Mar  8 2014, 07:23:29), rs6000_64, 2014 07 18 15:46:05

/usr/sap/PLH/DVEBMGS62/exe/jstart, 720, patch 600, changelist 1480835, optu (Mar  8 2014, 07:23:29), rs6000_64, 2014 07 18 15:46:05

regards,

[Reagan]

Your problem is when you stop the SAP system and the DB fails to stop. This happens after the kernel update. You need to reproduce the issue to identify where the problem is. There is no point in supplying the logs which are of no use. Also providing the right information is very important. I am still wondering how you were able to update the kernel from 640 release to 720 release.

Reproduce the issue and come back with the logs.