cancel
Showing results for 
Search instead for 
Did you mean: 

Issue after Oracle database patch upgrade 10.2.0.4

former_member231914
Participant
0 Kudos

Hello,

After database patch application 10.2.0.4, we are getting error in starting database from 'startsap' script from sidadm user. We are getting this error in all the systems.

FYI...Once Oracle start explicitly, then there is no problem for starting SAP.

Please find the error below & let us know the path forward.

********************************************************************************************

DQESAP05:dpiadm 24> more /home/dpiadm/startdb.log

50y0C

-


Wed Mar 4 12:19:41 IST 2009

LOGFILE FOR STARTING ORACLE

Trying to start DPI database ...

-


Wed Mar 4 12:19:41 IST 2009

checking required environment variables

ORACLE_HOME is >/oracle/DPI/102_64<

ORACLE_SID is >DPI<

-


Wed Mar 4 12:19:41 IST 2009

check initora

-


Wed Mar 4 12:19:41 IST 2009

check initora

-


Wed Mar 4 12:19:41 IST 2009

checking V2 connect

TNS Ping Utility for HPUX: Version 10.2.0.4.0 - Production on 04-MAR-2009 12:19:41

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

Used parameter files:

/usr/sap/DPI/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 = DQESAP05) (PORT = 1527))) (CONNECT_DATA = (SID = DPI) (GLOBAL_NAME = DPI.WORLD)))

OK (10 msec)

tnsping: V2 connect to DPI

-


Wed Mar 4 12:19:41 IST 2009

Connect to the database to check the database state:

R3trans: connect check finished with return code: 12

Database not available

-


Wed Mar 4 12:19:42 IST 2009

Shutdown database

First trying to shutdown the database - May be,

the database is in the nomount or mount state

50y0CBstartdb.log (66%)@50y0C50y0C----


Wed Mar 4 12:19:50 IST 2009

starting database

SQL*Plus: Release 10.2.0.4.0 - Production on Wed Mar 4 12:19:50 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_DPI'

Disconnected

-


Wed Mar 4 12:19:51 IST 2009

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/DPI/SYS/exe/run/startdb: Terminating with error code 12

***************************************************************************************

It is not able to get below information

"ORA-00119: invalid specification for system parameter LOCAL_LISTENER

ORA-00132: syntax error or unresolved network name 'LISTENER_DPI'"

Accepted Solutions (0)

Answers (2)

Answers (2)

Former Member
0 Kudos

Hi,

This is due to a error in tnsnames.ora.

Try this : Login with sysdba and perform the below steps:

conn / as sysdba;

alter system set LOCAL_LISTENER="(address=(protocol=tcp)(host=yourhostname)(port=yourportname))" scope=both sid='instancename';

Where the value for "instancename" is your actual INSTANCE_NAME.

And try starting using the script.

Thanks Nirmal

former_member231914
Participant
0 Kudos

Hi All,

Problem is solved. After oracle upgrade to 10.2.0.4, parameter Local_Listener was added which was giving problem. So with help of BRTools, you need to reset this parameter value to blank.

Once this is done, restart Oracle and check whether this parameter is still showing any value, now it should not.

Then shutdown oracle and then start it with startsap command from sidadm.

Thanks for all the suggestions.

Former Member
0 Kudos

Basis Team,

Great finding. I had the same problem today and i did as explained through BRTOOLS and it is working fine. But this issue is happening only on a portal system which is of 7.0 version since there is no dbaoraslib.o file in executable directory, but with other systems with same syntax of local_listener it is working fine since there is dbaoraslib.o

Thanks,

Murali.

Former Member
0 Kudos

Hi,

Looks like your listner is not running. Please check the status with lsnrctl status. And start with lsnrctl start if it is down.

Hope this helps.

Manoj

former_member231914
Participant
0 Kudos

Listener is already started and it's running fine.

Former Member
0 Kudos

Hi,

Please find few links below:

[]

[https://websmp130.sap-ag.de/sap(bD1lbiZjPTAwMQ==)/bc/bsp/spn/sapnotes/index2.htm?numm=403004]

[https://websmp130.sap-ag.de/sap(bD1lbiZjPTAwMQ==)/bc/bsp/spn/sapnotes/index2.htm?numm=819829]

Hope this helps.

Manoj