THE ORACLEORADB10G_HOME1TNSLISTENER SERVICE ON LOCAL COMPUTER STARTED AND THEN STOPPED

Database in windows throws an error when starting up the listener service:


“THE ORACLEORADB10G_HOME1TNSLISTENER SERVICE ON LOCAL COMPUTER STARTED AND THEN  STOPPED. SOME SERVICES STOP AUTOMATICALLY IF THEY HAVE NO WORK TO DO, FOR EXAMPLE, THE PERFORMANCE LOGS AND ALERTS SERVICE.”

-          Verify how many listener you have in the server

-          Ensure the listener you are working with, the environment as set properly such as “ORACLE_HOME”, “PATH”

-          When shutting and starting the service, verify your required listener service is starting ( when starting it will be mentioned in the command prompt)

-          Verify all the entries are correct in the listener file manually.

-          If nothing works out, recreate the listener using Network Configuration Assistant.

-          Stop and verify (or add) all the service that the respective listener should listen to.

Fatal NI connect error 12170 from your alert.log

Fatal NI connect error 12170. VERSION INFORMATION: TNS for Linux: Version 11.1.0.7.0 - Production Oracle Bequeath NT Protocol Adapter for Linux: Version 11.1.0.7.0 - Production TCP/IP NT Protocol Adapter for Linux: Version 11.1.0.7.0 - Production Time: 12-MAR-2013 10:39:03 Tracing not turned on. Tns error struct: ns main err code: 12535 TNS-12535: TNS:operation timed out ns secondary err code: 12606 nt main err code: 0 nt secondary err code: 0 nt OS err code: 0 Client address: (ADDRESS=(PROTOCOL=tcp)(HOST=TESTSVR)(PORT=43155)) WARNING: inbound connection timed out (ORA-3136)

 

Cause:

 The client failed to establish a connection and complete authentication in the time specified by the SQLNET.INBOUND_CONNECT_TIMEOUT parameter in the sqlnet.ora file. This error may be a result of network or system delays

Action:

You can set a higher value for INBOUND_CONNECT_TIMEOUT in sqlnet and listener.ora file or simple provide a value 0 to avoid these messages. This is just a warning saying that users were trying to connect and ultimately failed in connecting.

Oracle 11g new Features , IPS ( Incident Packaging Service)

To make oracle support better, oracle 11g introduce new feature / Service known IPS (Incident Packaging Service ) . Basically it is a part/extension of Oracle 11g new feature ADR ( Automatic Diagnostic repository). ADR is new concept in oracle 11g and it is just a file based repository of diagnostic data. ADR gives lot flexibility to maintain / handle diagnostic data.

When critical errors(i.e Problem) are detected, they automatically create an “incident” ( one occurrence of problem is Incident i.e relation between problem and incident is one to many).
Information(trace ,dump ) related to the incident is automatically captured in file based repository known as ADR ( Automatic Diagnostic repository), all the incident related files are tagged with Incident Number and certain health checks are run automatically. This information can be packaged to be sent to Oracle support

Incident Packaging Service (IPS) wraps up all information about an incident and allows you to send the whole package to Oracle Support.

Here is a step to collect and send data to support using IPS

$ adrci adrci> help ips adrci> show incident ( For example above command show incident No 9817 for ORA-600 [XYZ] ) adrci> ips create package incident 9817 <= ( it will give package No.) adrci> ips create package incident 9817 Created package 4 based on incident id 9817, correlation level typical adrci> ips add incident 9817 package 4 Added incident 9817 to package 4 adrci> adrci>>ips add file /u01/app/oracle/diag/rdbms/orcl2/orcl2/trace/alert_orcl2.log package 4 Added file /u01/app/oracle/diag/rdbms/orcl2/orcl2/trace/alert_orcl2.log to package 4 adrci>>ips generate package 4 in /tmp Generated package 4 in file /tmp/ORA600kci_20070514184516_COM_1.zip, mode complete adrci>>

Send above created file to Support

ORA-24324: service handle not initialized when shutting down database.

When we try to SHUTDOWN NORMAL/IMMEDIATE, it fails with the below errors.

ORA-24324: service handle not initialized
ORA-24323: value not allowed
ORA-01090: shutdown in progress - connection is not permitted 

Cause: for this is that the Background processes are hanging/not stared correctly during the previous startup of this database. Hence the smeaphores and shared memory segements are not getting detached properly now during shutdown.

Solution

1. Verify that there are no background processes owned by "oracle" , if there are kill them
$ ps -ef | grep ora_ | grep $ORACLE_SID

2. remove shared memory and semaphores:
A) checking for shared memory and semaphores
$ ipcs -mt (if there is anything owned by oracle remove it)
$ ipcrm -m [ID] (to remove it)

B) checking and removing semaphores
$ ipcs -sbt (if there is anything owned by oracle remove it)
$ ipcrm -s [ID] (to remove it)

C) remove sga and lk file
$ cd $ORACLE_HOME/dbs
$ rm sgadef<SID>.dbf (removing sga file)
$ORACLE_HOME/dbs/lk<sid> (removing lk... flies)

D) try to bring up oracle one step at a time:
$ sqlplus /nolog
> startup nomount pfile = ...[path]
> alter database mount;
> alter database open;

ORA-03113: end-of-file on communication channel

All connections between a client software and an Oracle Server are created and managed by Oracle Networking or Net8. This is a two way connection between a Net8 Server (Listener) and a Net8 client. After a connection is established between the two, this error may occur when the net8 server is no longer available, or can not respond to Net8 client requests due to problems with the Oracle Server.It can also be due to a network failure. If it occurs at startup a configuration or installation problem is a likely cause. If it occurs after a shutdown some defunct processes may be running.

Follow is a sampling of the issue, and how it could be fix.

[oracle@our12test 11.1.0]$ sqlplus "/as sysdba"
SQL*Plus: Release 11.1.0.7.0 - Production on Wed Dec 8 08:58:06 2010
Copyright (c) 1982, 2008, Oracle.  All rights reserved.
Connected to an idle instance.
 

SQL> startup
ORACLE instance started.
Total System Global Area 1068937216 bytes
Fixed Size                  2166536 bytes
Variable Size             427819256 bytes
Database Buffers          624951296 bytes
Redo Buffers               14000128 bytes
Database mounted.
ORA-03113: end-of-file on communication channel
Process ID: 16033
Session ID: 3000 Serial number: 5

SQL> shut abort
ORA-24324: service handle not initialized
ORA-01041: internal error. hostdef extension doesn't exist
SQL> exit
Disconnected from Oracle Database 11g Enterprise Edition Release 11.1.0.7.0 64 bit Production
With the Partitioning, OLAP, Data Mining and Real Application Testing options
 

[oracle@our12test 11.1.0]$ sqlplus "/as sysdba"
SQL*Plus: Release 11.1.0.7.0 - Production on Wed Dec 8 09:00:20 2010
Copyright (c) 1982, 2008, Oracle.  All rights reserved.
Connected.
SQL> shut abort
ORACLE instance shut down.
SQL> exit
Disconnected
[oracle@our12test 11.1.0]$ sqlplus "/as sysdba"
SQL*Plus: Release 11.1.0.7.0 - Production on Wed Dec 8 09:00:20 2010
Copyright (c) 1982, 2008, Oracle.  All rights reserved.
Connected.
SQL> shut abort
ORACLE instance shut down.
SQL> exit
Disconnected
 

[oracle@our12test 11.1.0]$ sqlplus "/as sysdba"
SQL*Plus: Release 11.1.0.7.0 - Production on Wed Dec 8 09:00:35 2010
Copyright (c) 1982, 2008, Oracle.  All rights reserved.
Connected to an idle instance.
SQL> startup mount
ORACLE instance started.
Total System Global Area 1068937216 bytes
Fixed Size                  2166536 bytes
Variable Size             427819256 bytes
Database Buffers          624951296 bytes
Redo Buffers               14000128 bytes
Database mounted.
SQL> recover database;
Media recovery complete.
SQL> alter database open;
Database altered.
SQL> exit
Disconnected from Oracle Database 11g Enterprise Edition Release 11.1.0.7.0-64 bit Production
With the Partitioning, OLAP, Data Mining and Real Application Testing options

[oracle@our12test 11.1.0]$ sqlplus "/as sysdba"
SQL*Plus: Release 11.1.0.7.0 - Production on Wed Dec 8 09:04:55 2010
Copyright (c) 1982, 2008, Oracle.  All rights reserved.
Connected to:
Oracle Database 11g Enterprise Edition Release 11.1.0.7.0 - 64bit Production
With the Partitioning, OLAP, Data Mining and Real Application Testing options
SQL> shut immediate
Database closed.
Database dismounted.
ORACLE instance shut down.
SQL> exit
 

Then start normaly ...

ORA-27123: unable to attach to shared memory segment

ORA-27123: unable to attach to shared memory segment 
SVR4 Error: 13: Permission denied

Cause

This error encounters  probably in a Linux O/S due to permission problem.

 Solution

-         In order to resolve the respective is issue, you can do the following:  

      

        1.) Check the file permission of a file name "oracle" in the Oracle home bin directory.

             ls -l $ORACLE_HOME/bin/oracle

  

2     2.) The respective file will have the permission (of either 755 or 777 ) according to the way you have set it. Ensure the respective file name "oracle" is owned by oracle and not other user.

   

3      3.) And execute the following command:

             chmod 6751 $ORACLE_HOME/bin/oracle