on 01-29-2009 6:29 PM
Hi,
I have installed Solution Manager 7.0 in Suse Linux 10, with oracle 10.2.0.4.
I am trying to start after a normal shutdown but now i have this error message:
startdb.log
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/SMG/SYS/exe/run/startdb: Terminating with error code 12
And in the listener.log
29-JAN-2009 16:52:53 * (CONNECT_DATA=(SID=SMG)(GLOBAL_NAME=SMG.WORLD)(CID=(PROGRAM=R3trans)(HOST=sm-0)(USER=smgadm))) * (ADDRESS=(PROTOCOL=tcp)(HOST=10.48.48.50)(PORT=48026)) * establish * SMG * 12518
TNS-12518: TNS:listener could not hand off client connection
TNS-12547: TNS:lost contact
TNS-12560: TNS:protocol adapter error
TNS-00517: Lost contact
Linux Error: 32: Broken pipe
I didn´t do any change to this system...
Can you help me solve the problem?
Kind regards,
Nuno Silva
Hai,
Please check the following.
I guess reason for this when attempting to start the listener the log file for the listener $ORACLE_HOME/network/log/listener.log has reached its 2GB file size limit on Linux. To solve the problem move the contents or copy (backup) the file and restart the listener.
Hope this helps.
Regards,
Yoganand.V
Edited by: Yoganand Vedagiri on Jan 29, 2009 9:09 PM
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi,
You can see if i run this:
sm-0:smgadm 47> sqlplus /"as sysdba"
SQL*Plus: Release 10.2.0.4.0 - Production on Fri Jan 30 13:23:47 2009
Copyright (c) 1982, 2007, Oracle. All Rights Reserved.
Connected to an idle instance.
SQL> startup
ORACLE instance started.
Total System Global Area 1224736768 bytes
Fixed Size 2083560 bytes
Variable Size 620758296 bytes
Database Buffers 587202560 bytes
Redo Buffers 14692352 bytes
Database mounted.
Database opened.
sm-0:orasmg 52> lsnrctl status
LSNRCTL for Linux: Version 10.2.0.4.0 - Production on 30-JAN-2009 13:28:49
Copyright (c) 1991, 2007, Oracle. All rights reserved.
Connecting to (ADDRESS=(PROTOCOL=IPC)(KEY=SMG.WORLD))
STATUS of the LISTENER
-
Alias LISTENER
Version TNSLSNR for Linux: Version 10.2.0.4.0 - Production
Start Date 29-JAN-2009 18:18:06
Uptime 0 days 19 hr. 10 min. 43 sec
Trace Level off
Security ON: Local OS Authentication
SNMP OFF
Listener Parameter File /oracle/SMG/102_64/network/admin/listener.ora
Listener Log File /oracle/SMG/102_64/network/log/listener.log
Listening Endpoints Summary...
(DESCRIPTION=(ADDRESS=(PROTOCOL=ipc)(KEY=SMG.WORLD)))
(DESCRIPTION=(ADDRESS=(PROTOCOL=ipc)(KEY=SMG)))
(DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=sm-0.wayfield.lan)(PORT=1527)))
Services Summary...
Service "SMG" has 1 instance(s).
Instance "SMG", status UNKNOWN, has 1 handler(s) for this service...
The command completed successfully
What should i see in alertSMG.log?
kind regards,
Nuno
What you showed looks good so far.
I was asking about error messages in alert<SID>.log; usually they begin with ORA-
Look at the times when you started Oracle and when you tried to start SAP.
And are you sure you didn't change anything in Oracle configuration?
Changes in init<SID>.ora or spfile<SID>.ora will come into effect not immediately, but only at the next start of Oracle. Could that have been the case here?
Hi,
On the log that you ask me i don´t have any error.
But in sqlnet.log
***********************************************************************
Fatal NI connect error 12537, connecting to:
(DESCRIPTION=(ADDRESS=(COMMUNITY=SAP.WORLD)(PROTOCOL=TCP)(HOST=sm-0)(PORT=1527))(CONNECT_DATA=(SID=SMG)(GLOBAL_NAME=SMG.WORLD)(CID=(PROGRAM=R3trans)(HOST=sm-0)(USER=smgadm))))
VERSION INFORMATION:
TNS for Linux: Version 10.2.0.2.0 - Production
TCP/IP NT Protocol Adapter for Linux: Version 10.2.0.2.0 - Production
Time: 30-JAN-2009 12:47:04
Tracing not turned on.
Tns error struct:
ns main err code: 12537
TNS-12537: TNS:connection closed
ns secondary err code: 12560
nt main err code: 507
TNS-00507: Connection closed
nt secondary err code: 0
nt OS err code: 0
Hai,
Cause:
The error 32 indicates the communication has been broken while the listener is trying to hand off the client connection to the server process or dispatcher process.
Action:
1. One of reason would be processes parameter being low, and can be verified by the v$resource_limit view.
2. In Shared Server mode, check the 'lsnrctl services' output and see if the dispatcher has refused any connections, if so, then consider increasing the number of dispatchers.
3. Check the alert log for any possible errors.
4. Memory resource is also another cause for this issue. Check the swap, memory usage of the OS.
Regards,
Yoganand.V
User | Count |
---|---|
83 | |
10 | |
10 | |
9 | |
7 | |
6 | |
5 | |
5 | |
4 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.