ORA-12514

[oracle@oradb ~]$ tnsping dbtest

TNS Ping Utility for Linux: Version 11.2.0.1.0 - Production on 20-JUN-2013 08:43:11

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

Used parameter files:
/db/oracle/product/11.2.0/db_1/network/admin/sqlnet.ora


Used TNSNAMES adapter to resolve the alias
Attempting to contact (DESCRIPTION = (ADDRESS = (PROTOCOL = TCP)(HOST = oradb.egolife.com)(PORT = 1521)) (CONNECT_DATA = (SERVER = DEDICATED) (SERVICE_NAME = DBTEST.oradb.egolife.com)))
OK (0 msec)

[oracle@oradb ~]$ sqlplus  /nolog

SQL*Plus: Release 11.2.0.1.0 Production on Thu Jun 20 08:43:17 2013

Copyright (c) 1982, 2009, Oracle.  All rights reserved.

SQL> conn barcode@dbtest
Enter password: 
ERROR:
ORA-12514: TNS:listener does not currently know of service requested in connect
descriptor

SQL> show parameter name

NAME				     TYPE			 VALUE
------------------------ --------------- --------
db_file_name_convert	 string
db_name					 string			 DBTEST
db_unique_name			 string			 DBTEST
global_names			 boolean		 TRUE
instance_name			 string			 DBTEST
lock_name_space 		 string
log_file_name_convert	 string
service_names			 string			 DBTEST

SQL> alter system set service_names = 'DBTEST.oradb.egolife.com' scope=both;

System altered.

[oracle@oradb ~]$ sqlplus  /nolog

SQL*Plus: Release 11.2.0.1.0 Production on Thu Jun 20 08:57:55 2013

Copyright (c) 1982, 2009, Oracle.  All rights reserved.

SQL> conn barcode@dbtest
Enter password: 
Connected.

SQL> alter session set NLS_DATE_FORMAT = 'mm-dd-yyyy hh24:mi:ss';

Session altered.

SQL> select instance_name,startup_time,status from v$instance;

INSTANCE_NAME	     STARTUP_TIME		 STATUS
-------------------- ------------------- ------------------------------------
DBTEST		         06-19-2013 14:22:48 OPEN

[oracle@oradb trace]$ grep ORA- alert_DBTEST.log.2013-06-19  | sort | uniq
opiodr aborting process unknown ospid (21424) as a result of ORA-1092
opiodr aborting process unknown ospid (21484) as a result of ORA-1092
opiodr aborting process unknown ospid (21818) as a result of ORA-1092
opiodr aborting process unknown ospid (21872) as a result of ORA-1092
opiodr aborting process unknown ospid (21931) as a result of ORA-1092
opiodr aborting process unknown ospid (21987) as a result of ORA-1092
opiodr aborting process unknown ospid (22051) as a result of ORA-1092
ORA-00020: maximum number of processes 50 exceeded
ORA-00020: No more process state objects available
ORA-00202: control file: '/db/oracle/oradata/DBTEST/ctl01DBTEST.ora'
ORA-00202: control file: '/db/oracle/oradata/DBTEST/ctl02DBTEST.ora'
ORA-00202: control file: '/db/oracle/oradata/DBTEST/ctl03DBTEST.ora'
ORA-00210: cannot open the specified control file
ORA-01565: error in identifying file '/db/oracle/product/11.2.0/db_1/dbs/spfileDBTEST.ora'
ORA-01565: Unable to open Spfile /db/oracle/product/11.2.0/db_1/dbs/spfileDBTEST.ora.
ORA-1031 signalled during: create undo tablespace undotbs datafile '/db/oracle/oradata/DBTEST/undotbs02.dbf' size 300M...
ORA-1092 : opitsk aborting process
ORA-1092 signalled during: ALTER DATABASE OPEN...
ORA-1507 signalled during: ALTER DATABASE CLOSE NORMAL...
ORA-1543 signalled during: CREATE TABLESPACE USERS LOGGING DATAFILE
ORA-201 signalled during: ALTER DATABASE   MOUNT...
ORA-205 signalled during: ALTER DATABASE   MOUNT...
ORA-20 errors will not be written to the alert log for
ORA-27037: unable to obtain file status
ORA-27300: OS system dependent operation:open failed with status: 2
ORA-27301: OS failure message: No such file or directory
ORA-27302: failure occurred at: sskgmsmr_7
ORA-30012: undo tablespace 'AUTO' does not exist or of wrong type
ORA-30012: undo tablespace '/db/oracle/oradata/DBTEST/undo' does not exist or of wrong type
ORA-30012: undo tablespace 'UNDO' does not exist or of wrong type
ORA-30012: undo tablespace 'undotbs01.dbf' does not exist or of wrong type
 the ORA-20 errors.
WARNING: inbound connection timed out (ORA-3136)

ORA-12514: TNS:listener does not currently know of service requested in connect descriptor
Cause: The listener received a request to establish a connection to a database or other service. The connect descriptor received by the listener specified a service name for a service (usually a database service) that either has not yet dynamically registered with the listener or has not been statically configured for the listener. This may be a temporary condition such as after the listener has started, but before the database instance has registered with the listener.
Action:
- Wait a moment and try to connect a second time.

- Check which services are currently known by the listener by executing: lsnrctl services [listener name]

- Check that the SERVICE_NAME parameter in the connect descriptor of the net service name used specifies a service known by the listener.

- If an easy connect naming connect identifier was used, check that the service name specified is a service known by the listener.

- Check for an event in the listener.log file.