sapstart fails after installation of CPU-Patch Apr...

Hi Experts,

after installing the CPU-Patch April2009 for Oracle 10.2.0.4, startsap fails with error code 12.

Starting everything manually works (lsnrctl start, sqlplus and do startup, after that startsap works).

When the listener and the database are running, things like R3trans -x also work without errors.

I found a SAP-Note 97953 but I don't know if this is the solution. Some of the oracle-executables in the bin-directory have been modified. So there is a "oracle" and a "oracle0" . The timestamp indicates to me that these files were modified while implementing the CPU-Patch.

I also checked SAP-Note 583861but with no success.

regards

Dirk

SAP Managed Tags:
Oracle Database

You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.

Comment

Accepted Solutions (0)

Answers (2)

I solved my problem.

The CPU-Patch built a new init<SID>.ora and a spfile<SID>.ora. I copied the old ones back and startsap works again.

The Parameter LOCAL_LISTENER is in the old init<SID>.ora.

Thanks for your help.

regards

Dirk

You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.

Comment

Execute

R3trans -d

and check the output of trans.log

Markus

You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.

Comment

Hi Markus,

if the database ist down and I execute "R3trans -d" I'll get the following error.

R3trans -d

This is R3trans version 6.18 (release 710 - 08.10.07 - 13:37:00).

unicode enabled version

2EETW169 no connect possible: "DBMS = ORACLE --- dbs_ora_tnsname = 'QXI'"

R3trans finished (0012).

and trans.log looks like:

more trans.log

4 ETW000 R3trans version 6.18 (release 710 - 08.10.07 - 13:37:00).

4 ETW000 unicode enabled version

4 ETW000 ===============================================

4 ETW000

4 ETW000 date&time : 19.06.2009 - 09:36:55

4 ETW000 control file:

4 ETW000 R3trans was called as follows: R3trans -d

4 ETW000 trace at level 2 opened for a given file pointer

4 ETW000 Fri Jun 19 09:36:55 2009 123 0.000123

4 ETW000 db_con_init called 17 0.000140

4 ETW000 determine_block_commit: no con_hdl found as blocked for con_name = R/3

4 ETW000 66 0.000206

4 ETW000 create_con (con_name=R/3) 21 0.000227

4 ETW000 Loading DB library '/usr/sap/QXI/SYS/exe/uc/sunx86_64/dboraslib.so' ...

4 ETW000 65 0.000292

4 ETW000 load shared library (/usr/sap/QXI/SYS/exe/uc/sunx86_64/dboraslib.so), hdl 0

4 ETW000 10039 0.010331

4 ETW000 Library '/usr/sap/QXI/SYS/exe/uc/sunx86_64/dboraslib.so' loaded

4 ETW000 26 0.010357

4 ETW000 function DbSlExpFuns loaded from library /usr/sap/QXI/SYS/exe/uc/sunx86_64/dboraslib.so

4 ETW000 35 0.010392

4 ETW000 Version of '/usr/sap/QXI/SYS/exe/uc/sunx86_64/dboraslib.so' is "710.16", patchlevel (0.6

4 ETW000 75 0.010467

4 ETW000 function dsql_db_init loaded from library /usr/sap/QXI/SYS/exe/uc/sunx86_64/dboraslib.so

4 ETW000 26 0.010493

4 ETW000 function dbdd_exp_funs loaded from library /usr/sap/QXI/SYS/exe/uc/sunx86_64/dboraslib.s

4 ETW000 66 0.010559

4 ETW000 New connection 0 created 31 0.010590

4 ETW000 0: name = R/3, con_id = -000000001 state = DISCONNECTED, tx = NO , bc = NO , hc = NO , p

erm = YES, reco = NO , timeout = 000, con_max = 255, con_opt = 255, occ = NO

4 ETW000 39 0.010629

4 ETW000 db_con_connect (con_name=R/3) 30 0.010659

4 ETW000 determine_block_commit: no con_hdl found as blocked for con_name = R/3

4 ETW000 24 0.010683

4 ETW000 find_con_by_name found the following connection:

4 ETW000 25 0.010708

4 ETW000 0: name = R/3, con_id = 000000000 state = DISCONNECTED, tx = NO , bc = NO , hc = NO , pe

rm = YES, reco = NO , timeout = 000, con_max = 255, con_opt = 255, occ = NO

4 ETW000 32 0.010740

4 ETW000 Oracle Client Version: '10.2.0.2.0' 503 0.011243

4 ETW000 -->oci_initialize (con_hdl=0) 30 0.011273

4 ETW000 Environment NLS_LANG='AMERICAN_AMERICA.UTF8' 21 0.011294

4 ETW000 application info callback registered 16 0.011310

4 ETW000 Client NLS settings: 'AMERICAN_AMERICA.UTF8' 3166 0.014476

4 ETW000 Logon as OPS$-user to get SAPSR3's password 36 0.014512

4 ETW000 Connecting as /@QXI on connection 0 (nls_hdl 0) ... (dbsl BIN 220507)

4 ETW000 50 0.014562

4 ETW000 Nls CharacterSet NationalCharSet C EnvHp ErrHp Er

rHpBatch

4 ETW000 35 0.014597

4 ETW000 0 UTF8 1 2bcdc70 2bd56c0

2be5df8

4 ETW000 28 0.014625

4 ETW000 Allocating server context handle 35 0.014660

4 ETW000 Attaching to DB Server QXI (con_hdl=0,svchp=2be5d28,srvhp=2be8018)

4 ETW000 77 0.014737

4 ETW000 Assigning server context 2be8018 to service context 2be5d28

4 ETW000 25597 0.040334

4 ETW000 Starting user session (con_hdl=0,svchp=2be5d28,srvhp=2be8018,usrhp=2bd5ed8)

4 ETW000 71 0.040405

4 ETW000 OCI-call failed with -1=OCI_ERROR 3460 0.043865

4 ETW000 SQL error 1034: 'ORA-01034: ORACLE not available

4 ETW000 ORA-27101: shared memory realm does not exist 103 0.043968

4 ETW000 Solaris-AMD64 Error: 2: No such file or directory'

4 ETW000 *** ERROR => OCI-call 'OCISessionBegin' failed: rc = 1034

4 ETW000 51 0.044019

4 ETW000 server_detach(con_hdl=0,stale=1,srvhp=2be8018) 18 0.044037

4 ETW000 Detaching from DB Server (con_hdl=0,svchp=2be5d28,srvhp=2be8018)

4 ETW000 30 0.044067

4 ETW000 Deallocating server context handle 2be8018 from con_hdl=0

4 ETW000 233 0.044300

4 ETW000 *** ERROR => CONNECT failed with sql error '1034'

4 ETW000 52 0.044352

4 ETW000 set_ocica() -> OCI or SQL return code 1034 26 0.044378

4 ETW000 OCIErrorGet -> SQL error code: 0 54 0.044432

4 ETW000 error text: 'ORA-01034: ORACLE not available 18 0.044450

4 ETW000 ORA-27101: shared memory realm does not exist

4 ETW000 Solaris-AMD64 Error: 2: No such file or directory'

4 ETW000 Try to connect with default password 30 0.044480

4 ETW000 Connecting as SAPSR3/@QXI on connection 0 (nls_hdl 0) ... (dbsl BIN 220507)

4 ETW000 32 0.044512

4 ETW000 Nls CharacterSet NationalCharSet C EnvHp ErrHp Er

rHpBatch

4 ETW000 30 0.044542

4 ETW000 0 UTF8 1 2bcdc70 2bd56c0

2be5df8

4 ETW000 29 0.044571

4 ETW000 Allocating server context handle 17 0.044588

4 ETW000 Attaching to DB Server QXI (con_hdl=0,svchp=2be5d28,srvhp=2be8018)

4 ETW000 41 0.044629

4 ETW000 Assigning server context 2be8018 to service context 2be5d28

4 ETW000 23436 0.068065

4 ETW000 Assigning username to user session 2bd5ed8 23 0.068088

4 ETW000 Assigning password to user session 2bd5ed8 41 0.068129

4 ETW000 Starting user session (con_hdl=0,svchp=2be5d28,srvhp=2be8018,usrhp=2bd5ed8)

4 ETW000 33 0.068162

4 ETW000 OCI-call failed with -1=OCI_ERROR 2900 0.071062

4 ETW000 SQL error 1034: 'ORA-01034: ORACLE not available

4 ETW000 ORA-27101: shared memory realm does not exist 73 0.071135

4 ETW000 Solaris-AMD64 Error: 2: No such file or directory'

4 ETW000 *** ERROR => OCI-call 'OCISessionBegin' failed: rc = 1034

4 ETW000 55 0.071190

4 ETW000 server_detach(con_hdl=0,stale=1,srvhp=2be8018) 20 0.071210

4 ETW000 Detaching from DB Server (con_hdl=0,svchp=2be5d28,srvhp=2be8018)

4 ETW000 25 0.071235

4 ETW000 Deallocating server context handle 2be8018 from con_hdl=0

4 ETW000 144 0.071379

4 ETW000 *** ERROR => CONNECT failed with sql error '1034'

4 ETW000 32 0.071411

4 ETW000 set_ocica() -> OCI or SQL return code 1034 16 0.071427

4 ETW000 OCIErrorGet -> SQL error code: 0 51 0.071478

4 ETW000 error text: 'ORA-01034: ORACLE not available 19 0.071497

4 ETW000 ORA-27101: shared memory realm does not exist

4 ETW000 Solaris-AMD64 Error: 2: No such file or directory'

4 ETW000 ***LOG BY2=>sql error 1034 performing CON 131 0.071628

4 ETW000 ***LOG BY0=>ORA-01034: ORACLE not available 21 0.071649

4 ETW000 ORA-27101: shared memory realm does not exist

4 ETW000 Solaris-AMD64 Error: 2: No such file or directory

2EETW169 no connect possible: "DBMS = ORACLE --- dbs_ora_tnsname = 'QXI'"

If the database is up everything works. Here is the output of "R3trans -d"

R3trans -d

This is R3trans version 6.18 (release 710 - 08.10.07 - 13:37:00).

unicode enabled version

R3trans finished (0000).

For me this all looks o.k. when the database is down R3trans won't be able to reach it and if the database is up it works. But why I can't then just execute "sapstart" ?

Edited by: Dirk Rödl on Jun 19, 2009 9:46 AM

Edited by: Dirk Rödl on Jun 19, 2009 9:48 AM

Edited by: Dirk Rödl on Jun 19, 2009 9:49 AM

startsap will not work if Oracle listener isn't running. So let me ask: Are you sure Oracle listener was started automatically before upgrade?

And what is your operating system by the way?

Hello Joe,

SAP and Oracle are running on "Solaris 10 5/08 X86".

I made the upgrade just like the readme said. I had to stop and start the listener several time during the upgrade.

Ok, I don't work with Solaris, but with other flavours of Unix.

We always have to start Oracle listener once when the system boots. From then on, we always use startsap and stopsap. Oracle listener will keep on running till the next shutdown.

The only other reason for stopping Oracle listener is patching. Afterwards we have to start listener again.

So my question was: What is different in your case? Sorry, I read your postings a few times, but still not sure if I understood.

Wondering whether there is a real problem, or just some kind of misunderstanding?

regards

Yes I always have to be sure that the listener is running. And after that "normally" I can work with startsap and stopsap.

But my problem is that "startsap" ist NOT working. It only works if I manually start the listener AND the database.

I know if everything is o.k. you just start the listener and than do a "startsap" thats it.

regards

Dirk

Thanks for clarifying; it wasn't clear to me that startsap wouldn't start the db even if listener was running.

In this case compare permissions of binaries oracle and oracle0.

I guess s-bit is missing?

-rwsr-s--x 1 oraqxi dba 141861976 Jun 18 11:58 oracle

-rwsr-s--x 1 oraqxi dba 141867848 Jun 18 10:05 oracleO

Looks good.

Could you please provide the output of 'startsap db' when Oracle is down, but listener is running?

startsap db -

Checking QXI Database

Database is not available via R3trans---

Running /usr/sap/QXI/SYS/exe/run/startdb---

Trying to start QXI database ...

Log file: /export/home/qxiadm/startdb.log---

/usr/sap/QXI/SYS/exe/run/startdb: Terminating with error code 12---

DB startup failed---

qxiadm@ecsnms012 # more /export/home/qxiadm/startdb.log---

Freitag, 19. Juni 2009 11:18 Uhr CEST

LOGFILE FOR STARTING ORACLE

---

Trying to start QXI database ...

Freitag, 19. Juni 2009 11:18 Uhr CEST

checking required environment variables

---

ORACLE_HOME is >/oracle/QXI/102_64<

ORACLE_SID is >QXI<

Freitag, 19. Juni 2009 11:18 Uhr CEST

check initora

Freitag, 19. Juni 2009 11:18 Uhr CEST

check initora

Freitag, 19. Juni 2009 11:18 Uhr CEST

checking V2 connect

---

TNS Ping Utility for Solaris: Version 10.2.0.4.0 - Production on 19-JUN-2009 11:18:23

---

Used parameter files:

/usr/sap/QXI/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 = ecsnms0

12) (PORT = 1527))) (CONNECT_DATA = (SID = QXI) (GLOBAL_NAME = QXI.WORLD)))

OK (10 msec)

tnsping: V2 connect to QXI

Freitag, 19. Juni 2009 11:18 Uhr CEST

Connect to the database to check the database state:

R3trans: connect check finished with return code: 12

Database not available

Freitag, 19. Juni 2009 11:18 Uhr CEST

Shutdown database

First trying to shutdown the database - May be,

the database is in the nomount or mount state

Freitag, 19. Juni 2009 11:18 Uhr CEST

starting database

SQL*Plus: Release 10.2.0.4.0 - Production on Fri Jun 19 11:18:24 2009

Connected to an idle instance.

ORA-00119: invalid specification for system parameter LOCAL_LISTENER

ORA-00132: syntax error or unresolved network name 'LISTENER_QXI'

Disconnected

Freitag, 19. Juni 2009 11:18 Uhr CEST

Connect to the database to verify, that the database is now open

R3trans check finished with return code: 12

ERROR: Startup of database failed

Notify Database Administrator.

/usr/sap/QXI/SYS/exe/run/startdb: Terminating with error code 12

here is my listener.ora:

more /oracle/QXI/102_64/network/admin/listener.ora

################

Filename......: listener.ora
Created.......: created by SAP AG, R/3 Rel. >= 6.10
Name..........:
Date..........:
@(#) $Id: //bc/710-1_REL/src/ins/SAPINST/impl/tpls/ora/ind/LISTENER.ORA#2 $

################

ADMIN_RESTRICTIONS_LISTENER = on

LISTENER =

(ADDRESS_LIST =

(ADDRESS =

(PROTOCOL = IPC)

(KEY = QXI.WORLD)

)

(ADDRESS=

(PROTOCOL = IPC)

(KEY = QXI)

)

(ADDRESS =

(COMMUNITY = SAP.WORLD)

(PROTOCOL = TCP)

(HOST = ecsnms012)

(PORT = 1527)

)

STARTUP_WAIT_TIME_LISTENER = 0

CONNECT_TIMEOUT_LISTENER = 10

TRACE_LEVEL_LISTENER = OFF

SID_LIST_LISTENER =

(SID_LIST =

(SID_DESC =

(SID_NAME = QXI)

(ORACLE_HOME = /oracle/QXI/102_64)

)

> 4 ETW000 [dev trc ,00000] SQL error 1034: 'ORA-01034: ORACLE not available

> 4 ETW000 ORA-27101: shared memory realm does not exist 103 0.043968

> 4 ETW000 Solaris-AMD64 Error: 2: No such file or directory'

As you can see here, your database is not completely started.

What's the output of

sqlplus / as sysdba
shutdown immediate
startup

Markus

oraqxi@ecsnms012 # sqlplus /nolog

SQL*Plus: Release 10.2.0.4.0 - Production on Fri Jun 19 11:45:33 2009

SQL> connect / as sysdba

Connected to an idle instance.

SQL> shutdown immediate

ORA-01034: ORACLE not available

ORA-27101: shared memory realm does not exist

Solaris-AMD64 Error: 2: No such file or directory

SQL> startup

ORACLE instance started.

Total System Global Area 4747952128 bytes

Fixed Size 2090304 bytes

Variable Size 2399144640 bytes

Database Buffers 2332033024 bytes

Redo Buffers 14684160 bytes

Database mounted.

Database opened.

regards

Dirk

Well,

it is quite difficult to read that "copypaste" thing.

So my first advice for you is to learn to paste things and use the markup on the left.

Second, in your server probably you can see it better and probably you can see that the first error happens when startsap tried to start the db:


Freitag, 19. Juni 2009 11:18 Uhr CEST starting database 
----------------- 
SQL*Plus: Release 10.2.0.4.0 - 
Production on Fri Jun 19 11:18:24 2009 
Copyright (c) 1982, 2007, Oracle. All Rights Reserved. 
Connected to an idle instance. 
ORA-00119: invalid specification for system parameter LOCAL_LISTENER 
ORA-00132: syntax error or unresolved network name 'LISTENER_QXI' Disconnected 
------------------------------

So, take a look at your parameters, it looks like the LOCAL_LISTENER is not OK

Ask a Question

Top Q&A Solution Author

User

Count