Home » Infrastructure » Windows » Error ORA-12505 tns listener does not currently know of sid given in connect descriptor (Oracle 10, Windows Server 2003)
|
|
Re: Error ORA-12505 tns listener does not currently know of sid given in connect descriptor [message #648331 is a reply to message #648330] |
Sun, 21 February 2016 08:10   |
 |
JeremyS
Messages: 10 Registered: February 2016 Location: FRANCE
|
Junior Member |
|
|
lsnrctl status :
LSNRCTL for 32-bit Windows: Version 10.1.0.2.0 - Production on 21-FEB-2016 15:07
:47
Copyright (c) 1991, 2004, Oracle. All rights reserved.
Connecting to (DESCRIPTION=(ADDRESS=(PROTOCOL=TCP)(HOST=192.168.10.5)(PORT=1521)
))
STATUS of the LISTENER
------------------------
Alias LISTENER
Version TNSLSNR for 32-bit Windows: Version 10.1.0.2.0 - Produ
ction
Start Date 20-FEB-2016 14:14:52
Uptime 1 days 0 hr. 52 min. 55 sec
Trace Level off
Security ON: Local OS Authentication
SNMP OFF
Listener Parameter File D:\oracle\HomeVega10G\network\admin\listener.ora
Listener Log File D:\oracle\HomeVega10G\network\log\listener.log
Listening Endpoints Summary...
(DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=192.168.10.5)(PORT=1521)))
Services Summary...
Service "VEGA" has 2 instance(s).
Instance "VEGA", status UNKNOWN, has 1 handler(s) for this service...
Instance "vega", status READY, has 1 handler(s) for this service...
The command completed successfully
lsnrctl service :
LSNRCTL for 32-bit Windows: Version 10.1.0.2.0 - Production on 21-FEB-2016 15:09
:18
Copyright (c) 1991, 2004, Oracle. All rights reserved.
Connecting to (DESCRIPTION=(ADDRESS=(PROTOCOL=TCP)(HOST=192.168.10.5)(PORT=1521)
))
Services Summary...
Service "VEGA" has 2 instance(s).
Instance "VEGA", status UNKNOWN, has 1 handler(s) for this service...
Handler(s):
"DEDICATED" established:0 refused:0
LOCAL SERVER
Instance "vega", status READY, has 1 handler(s) for this service...
Handler(s):
"DEDICATED" established:0 refused:0 state:ready
LOCAL SERVER
The command completed successfully
|
|
|
|
|
|
Re: Error ORA-12505 tns listener does not currently know of sid given in connect descriptor [message #648335 is a reply to message #648334] |
Sun, 21 February 2016 08:50   |
 |
JeremyS
Messages: 10 Registered: February 2016 Location: FRANCE
|
Junior Member |
|
|
I find 2 alert_gima.log files :
One in d:\oracle\admin\gima\bdump :
Thu Feb 18 12:00:39 2016
Private_strands 7 at log switch
Thread 1 advanced to log sequence 12650
Current log# 2 seq# 12650 mem# 0: D:\ORACLE\ORADATA\GIMA\REDO02.LOG
Thu Feb 18 17:34:09 2016
Starting background process EMN0
EMN0 started with pid=17, OS id=1212
Thu Feb 18 17:34:09 2016
Shutting down instance: further logons disabled
Thu Feb 18 17:34:09 2016
Stopping background process QMNC
Thu Feb 18 17:34:09 2016
Stopping background process CJQ0
Thu Feb 18 17:34:11 2016
Stopping background process MMNL
Thu Feb 18 17:34:12 2016
Stopping background process MMON
Thu Feb 18 17:34:13 2016
Shutting down instance (immediate)
License high water mark = 6
Thu Feb 18 17:34:13 2016
Stopping Job queue slave processes
Thu Feb 18 17:34:13 2016
Job queue slave processes stopped
All dispatchers and shared servers shutdown
Starting up ORACLE RDBMS Version: 10.1.0.2.0.
System parameters with non-default values:
processes = 150
shared_pool_size = 83886080
large_pool_size = 8388608
java_pool_size = 50331648
control_files = D:\ORACLE\ORADATA\GIMA\CONTROL01.CTL, D:\ORACLE\ORADATA\GIMA\CONTROL02.CTL, D:\ORACLE\ORADATA\GIMA\CONTROL03.CTL
db_block_size = 8192
db_cache_size = 25165824
compatible = 10.1.0.2.0
db_file_multiblock_read_count= 16
undo_management = AUTO
undo_tablespace = UNDOTBS1
remote_login_passwordfile= EXCLUSIVE
db_domain =
dispatchers = (PROTOCOL=TCP) (SERVICE=GIMAXDB)
job_queue_processes = 10
background_dump_dest = D:\ORACLE\ADMIN\GIMA\BDUMP
user_dump_dest = D:\ORACLE\ADMIN\GIMA\UDUMP
core_dump_dest = D:\ORACLE\ADMIN\GIMA\CDUMP
sort_area_size = 65536
db_name = GIMA
open_cursors = 300
pga_aggregate_target = 25165824
PMON started with pid=2, OS id=4776
MMAN started with pid=3, OS id=4384
DBW0 started with pid=4, OS id=4768
LGWR started with pid=5, OS id=4920
CKPT started with pid=6, OS id=2128
SMON started with pid=7, OS id=5332
RECO started with pid=8, OS id=4828
CJQ0 started with pid=9, OS id=4860
Fri Feb 19 08:22:10 2016
starting up 1 dispatcher(s) for network address '(ADDRESS=(PARTIAL=YES)(PROTOCOL=TCP))'...
starting up 1 shared server(s) ...
Oracle Data Guard is not available in this edition of Oracle.
Fri Feb 19 08:22:11 2016
ALTER DATABASE MOUNT
Fri Feb 19 08:22:11 2016
Controlfile identified with block size 16384
Fri Feb 19 08:22:15 2016
Setting recovery target incarnation to 1
Fri Feb 19 08:22:16 2016
Successful mount of redo thread 1, with mount id 1265443187
Fri Feb 19 08:22:16 2016
Database mounted in Exclusive Mode.
Completed: ALTER DATABASE MOUNT
Fri Feb 19 08:22:17 2016
ALTER DATABASE OPEN
Fri Feb 19 08:22:17 2016
Beginning crash recovery of 1 threads
Fri Feb 19 08:22:17 2016
Started first pass scan
Fri Feb 19 08:22:17 2016
Completed first pass scan
0 redo blocks read, 0 data blocks need recovery
Fri Feb 19 08:22:17 2016
Started redo application at
Thread 1: logseq 12650, block 16889, scn 0.70772822
Recovery of Online Redo Log: Thread 1 Group 2 Seq 12650 Reading mem 0
Mem# 0 errs 0: D:\ORACLE\ORADATA\GIMA\REDO02.LOG
Fri Feb 19 08:22:17 2016
Completed redo application
Fri Feb 19 08:22:17 2016
Completed crash recovery at
Thread 1: logseq 12650, block 16889, scn 0.70792823
0 data blocks read, 0 data blocks written, 0 redo blocks read
Fri Feb 19 08:22:18 2016
Thread 1 advanced to log sequence 12651
Maximum redo generation record size = 120832 bytes
Maximum redo generation change vector size = 116476 bytes
Private_strands 7 at log switch
Thread 1 opened at log sequence 12651
Current log# 3 seq# 12651 mem# 0: D:\ORACLE\ORADATA\GIMA\REDO03.LOG
Successful open of redo thread 1
Fri Feb 19 08:22:18 2016
SMON: enabling cache recovery
Fri Feb 19 08:22:19 2016
Successfully onlined Undo Tablespace 1.
Fri Feb 19 08:22:19 2016
SMON: enabling tx recovery
Fri Feb 19 08:22:19 2016
Database Characterset is WE8MSWIN1252
Fri Feb 19 08:22:19 2016
Published database character set on system events channel
Fri Feb 19 08:22:19 2016
All processes have switched to database character set
Fri Feb 19 08:22:20 2016
Starting background process QMNC
QMNC started with pid=13, OS id=5296
Fri Feb 19 08:22:20 2016
replication_dependency_tracking turned off (no async multimaster replication found)
Fri Feb 19 08:22:21 2016
Starting background process MMON
MMON started with pid=14, OS id=1916
Fri Feb 19 08:22:21 2016
Starting background process MMNL
MMNL started with pid=15, OS id=5728
Fri Feb 19 08:22:22 2016
Completed: ALTER DATABASE OPEN
Fri Feb 19 08:22:47 2016
Running without dynamic strand for Non-Enterprise Edition
Fri Feb 19 08:22:47 2016
Starting ORACLE instance (normal)
Fri Feb 19 08:29:28 2016
Running without dynamic strand for Non-Enterprise Edition
Fri Feb 19 08:29:28 2016
Starting ORACLE instance (normal)
Fri Feb 19 08:33:10 2016
Running without dynamic strand for Non-Enterprise Edition
Fri Feb 19 08:33:10 2016
Starting ORACLE instance (normal)
Running without dynamic strand for Non-Enterprise Edition
Fri Feb 19 08:37:32 2016
Starting ORACLE instance (normal)
Fri Feb 19 08:52:39 2016
Private_strands 7 at log switch
Thread 1 advanced to log sequence 12652
Current log# 1 seq# 12652 mem# 0: D:\ORACLE\ORADATA\GIMA\REDO01.LOG
Fri Feb 19 09:34:41 2016
Starting background process EMN0
EMN0 started with pid=17, OS id=5640
Fri Feb 19 09:34:41 2016
Shutting down instance: further logons disabled
Fri Feb 19 09:34:41 2016
Stopping background process QMNC
Fri Feb 19 09:34:41 2016
Stopping background process CJQ0
Fri Feb 19 09:34:43 2016
Stopping background process MMNL
Fri Feb 19 09:34:44 2016
Stopping background process MMON
Fri Feb 19 09:34:45 2016
Shutting down instance (immediate)
License high water mark = 2
Fri Feb 19 09:34:45 2016
Stopping Job queue slave processes
Fri Feb 19 09:34:45 2016
Job queue slave processes stopped
All dispatchers and shared servers shutdown
Fri Feb 19 09:34:49 2016
alter database close normal
Fri Feb 19 09:34:49 2016
SMON: disabling tx recovery
SMON: disabling cache recovery
Fri Feb 19 09:34:49 2016
Shutting down archive processes
Archiving is disabled
Archive process shutdown avoided: 0 active
Thread 1 closed at log sequence 12652
Successful close of redo thread 1
Fri Feb 19 09:34:50 2016
Completed: alter database close normal
Fri Feb 19 09:34:50 2016
alter database dismount
Completed: alter database dismount
ARCH: Archival disabled due to shutdown: 1089
Shutting down archive processes
Archiving is disabled
Archive process shutdown avoided: 0 active
ARCH: Archival disabled due to shutdown: 1089
Shutting down archive processes
Archiving is disabled
Archive process shutdown avoided: 0 active
Another in d:\oracle\homevega10g\rdbms\trace :
Fri Feb 19 08:22:09 2016
ORACLE V10.1.0.2.0 - Production vsnsta=0
vsnsql=13 vsnxtr=3
Windows NT Version V5.2 Service Pack 2
CPU : 2 - type 586, 2 Physical Cores
Process Affinity: 0x00000000
Memory (A/P) : PH:3238M/4095M, PG:5159M/5977M, VA:1958M/2047M
Fri Feb 19 08:22:09 2016
Running without dynamic strand for Non-Enterprise Edition
Fri Feb 19 08:22:09 2016
Starting ORACLE instance (normal)
Fri Feb 19 08:22:09 2016
Running with 1 strand for Non-Enterprise Edition
LICENSE_MAX_SESSION = 0
LICENSE_SESSIONS_WARNING = 0
Picked latch-free SCN scheme 2
KCCDEBUG_LEVEL = 0
Using LOG_ARCHIVE_DEST_1 parameter default value as D:\oracle\HomeVega10G\RDBMS
Autotune of undo retention is turned on.
Running with 1 strand for Non-Enterprise Edition
Dynamic strands is set to FALSE
Running with 1 shared and 18 private strand(s). Zero-copy redo is FALSE
IMODE=BR
ILAT =18
LICENSE_MAX_USERS = 0
SYS auditing is disabled
I don't know if GIMA database is up and online now. How can i check this ?
|
|
|
|
|
|
|
|
|
|
|
|
Re: Error ORA-12505 tns listener does not currently know of sid given in connect descriptor [message #648345 is a reply to message #648344] |
Sun, 21 February 2016 10:53   |
 |
JeremyS
Messages: 10 Registered: February 2016 Location: FRANCE
|
Junior Member |
|
|
Michel Cadot wrote on Sun, 21 February 2016 17:33
JeremyS wrote on Sun, 21 February 2016 16:29The server is already in ORA_DBA group (active directory local domain security group).
What does this mean?
I meant the account you are connected with on the Windows database server must be in the local Windows group ORA_DBA.
I have a group named ORA_DBA in Active Directory. In this group, i have the domain administrator user and the Oracle server object.
I also tried to create a local group with the name ORA_DBA on the Oracle Server. In this group, i put the domain administrator account, the local administrator account, the local system account. But the sqlplus as sysdba connexion still failed.
Michel Cadot wrote on Sun, 21 February 2016 17:33
In addition, the %ORACLE_HOME%\network\admin\sqlnet.ora file must contain the line:
SQLNET.AUTHENTICATION_SERVICES = (NTS)
I don't find any sqlnet.ora files in d:\oracle\homevega10g\network\admin folder.

[mod-edit: imaged inserted into message body by bb]
[Updated on: Sun, 21 February 2016 12:52] by Moderator Report message to a moderator
|
|
|
|
|
|
Re: Error ORA-12505 tns listener does not currently know of sid given in connect descriptor [message #648349 is a reply to message #648335] |
Sun, 21 February 2016 11:11  |
 |
EdStevens
Messages: 1376 Registered: September 2013
|
Senior Member |
|
|
JeremyS wrote on Sun, 21 February 2016 08:50I find 2 alert_gima.log files :
One in d:\oracle\admin\gima\bdump :
Several things very strange about this, starting with the fact that you seem to have two alert logs for the same database, in different directories, and overlapping times. And within the first, we see further strangeness:
Thu Feb 18 12:00:39 2016
Shutting down instance: further logons disabled
Thu Feb 18 17:34:09 2016
Stopping background process QMNC
Thu Feb 18 17:34:09 2016
Stopping background process CJQ0
Thu Feb 18 17:34:11 2016
Stopping background process MMNL
Thu Feb 18 17:34:12 2016
Stopping background process MMON
Thu Feb 18 17:34:13 2016
Shutting down instance (immediate)
Looks like a shutdown was issued on Feb 18 at 12:00:39. The line just before would have shown if it were 'norma', 'immediate' or 'abort'. In any event, we don't see any actual shutdown progress messages until 17:34, and those get interrupted with another 'shutdown immediate'
License high water mark = 6
Thu Feb 18 17:34:13 2016
Stopping Job queue slave processes
Thu Feb 18 17:34:13 2016
Job queue slave processes stopped
All dispatchers and shared servers shutdown
And we see no progress on that shutdown. Then we see a startup at Fri Feb 19 08:22:10:
Starting up ORACLE RDBMS Version: 10.1.0.2.0.
System parameters with non-default values:
processes = 150
shared_pool_size = 83886080
large_pool_size = 8388608
java_pool_size = 50331648
control_files = D:\ORACLE\ORADATA\GIMA\CONTROL01.CTL, D:\ORACLE\ORADATA\GIMA\CONTROL02.CTL, D:\ORACLE\ORADATA\GIMA\CONTROL03.CTL
db_block_size = 8192
db_cache_size = 25165824
compatible = 10.1.0.2.0
db_file_multiblock_read_count= 16
undo_management = AUTO
undo_tablespace = UNDOTBS1
remote_login_passwordfile= EXCLUSIVE
db_domain =
dispatchers = (PROTOCOL=TCP) (SERVICE=GIMAXDB)
job_queue_processes = 10
background_dump_dest = D:\ORACLE\ADMIN\GIMA\BDUMP
user_dump_dest = D:\ORACLE\ADMIN\GIMA\UDUMP
core_dump_dest = D:\ORACLE\ADMIN\GIMA\CDUMP
sort_area_size = 65536
db_name = GIMA
open_cursors = 300
pga_aggregate_target = 25165824
PMON started with pid=2, OS id=4776
MMAN started with pid=3, OS id=4384
DBW0 started with pid=4, OS id=4768
LGWR started with pid=5, OS id=4920
CKPT started with pid=6, OS id=2128
SMON started with pid=7, OS id=5332
RECO started with pid=8, OS id=4828
CJQ0 started with pid=9, OS id=4860
Fri Feb 19 08:22:10 2016
starting up 1 dispatcher(s) for network address '(ADDRESS=(PARTIAL=YES)(PROTOCOL=TCP))'...
starting up 1 shared server(s) ...
Oracle Data Guard is not available in this edition of Oracle.
Fri Feb 19 08:22:11 2016
ALTER DATABASE MOUNT
Fri Feb 19 08:22:11 2016
Controlfile identified with block size 16384
Fri Feb 19 08:22:15 2016
Setting recovery target incarnation to 1
Fri Feb 19 08:22:16 2016
Successful mount of redo thread 1, with mount id 1265443187
Fri Feb 19 08:22:16 2016
Database mounted in Exclusive Mode.
Completed: ALTER DATABASE MOUNT
Fri Feb 19 08:22:17 2016
ALTER DATABASE OPEN
And as part of the startup, a crash recovery, indicating the previous shutdown did not complete cleanly:
Fri Feb 19 08:22:17 2016
Beginning crash recovery of 1 threads
Fri Feb 19 08:22:17 2016
<snip crash recovery activity>
Completed crash recovery at
Thread 1: logseq 12650, block 16889, scn 0.70792823
0 data blocks read, 0 data blocks written, 0 redo blocks read
Fri Feb 19 08:22:18 2016
Thread 1 advanced to log sequence 12651
And eventually a successful OPEN:
Maximum redo generation record size = 120832 bytes
Maximum redo generation change vector size = 116476 bytes
Private_strands 7 at log switch
Thread 1 opened at log sequence 12651
Current log# 3 seq# 12651 mem# 0: D:\ORACLE\ORADATA\GIMA\REDO03.LOG
Successful open of redo thread 1
Fri Feb 19 08:22:18 2016
SMON: enabling cache recovery
Fri Feb 19 08:22:19 2016
Successfully onlined Undo Tablespace 1.
Fri Feb 19 08:22:19 2016
SMON: enabling tx recovery
Fri Feb 19 08:22:19 2016
Database Characterset is WE8MSWIN1252
Fri Feb 19 08:22:19 2016
Published database character set on system events channel
Fri Feb 19 08:22:19 2016
All processes have switched to database character set
Fri Feb 19 08:22:20 2016
Starting background process QMNC
QMNC started with pid=13, OS id=5296
Fri Feb 19 08:22:20 2016
replication_dependency_tracking turned off (no async multimaster replication found)
Fri Feb 19 08:22:21 2016
Starting background process MMON
MMON started with pid=14, OS id=1916
Fri Feb 19 08:22:21 2016
Starting background process MMNL
MMNL started with pid=15, OS id=5728
Fri Feb 19 08:22:22 2016
Completed: ALTER DATABASE OPEN
Fri Feb 19 08:22:47 2016
Then, beginning just a few minutes later, a series of startups issued in quick succession:
Running without dynamic strand for Non-Enterprise Edition
Fri Feb 19 08:22:47 2016
Starting ORACLE instance (normal)
Fri Feb 19 08:29:28 2016
Running without dynamic strand for Non-Enterprise Edition
Fri Feb 19 08:29:28 2016
Starting ORACLE instance (normal)
Fri Feb 19 08:33:10 2016
Running without dynamic strand for Non-Enterprise Edition
Fri Feb 19 08:33:10 2016
Starting ORACLE instance (normal)
Running without dynamic strand for Non-Enterprise Edition
Fri Feb 19 08:37:32 2016
Starting ORACLE instance (normal)
Then a 15 minute lag before the next message, with none of the normal startup messages:
Fri Feb 19 08:52:39 2016
Private_strands 7 at log switch
Thread 1 advanced to log sequence 12652
Current log# 1 seq# 12652 mem# 0: D:\ORACLE\ORADATA\GIMA\REDO01.LOG
Fri Feb 19 09:34:41 2016
Starting background process EMN0
EMN0 started with pid=17, OS id=5640
then another shutdown:
Fri Feb 19 09:34:41 2016
Shutting down instance: further logons disabled
Fri Feb 19 09:34:41 2016
Stopping background process QMNC
Fri Feb 19 09:34:41 2016
Stopping background process CJQ0
Fri Feb 19 09:34:43 2016
Stopping background process MMNL
Fri Feb 19 09:34:44 2016
Stopping background process MMON
Fri Feb 19 09:34:45 2016
Shutting down instance (immediate)
License high water mark = 2
Fri Feb 19 09:34:45 2016
Stopping Job queue slave processes
Fri Feb 19 09:34:45 2016
Job queue slave processes stopped
All dispatchers and shared servers shutdown
Fri Feb 19 09:34:49 2016
alter database close normal
Fri Feb 19 09:34:49 2016
SMON: disabling tx recovery
SMON: disabling cache recovery
Fri Feb 19 09:34:49 2016
Shutting down archive processes
Archiving is disabled
Archive process shutdown avoided: 0 active
Thread 1 closed at log sequence 12652
Successful close of redo thread 1
Fri Feb 19 09:34:50 2016
Completed: alter database close normal
Fri Feb 19 09:34:50 2016
alter database dismount
Completed: alter database dismount
ARCH: Archival disabled due to shutdown: 1089
Shutting down archive processes
Archiving is disabled
Archive process shutdown avoided: 0 active
ARCH: Archival disabled due to shutdown: 1089
Shutting down archive processes
Archiving is disabled
Archive process shutdown avoided: 0 active
Quote:
Another in d:\oracle\homevega10g\rdbms\trace :
What was the actual name of this file? And exactly what directory is it in? It should be 'd:\oracle\homevega10g\rdbms\%ORACLE_SID%\%ORACLE_SID%\trace\alert%ORACLE_SID%.log'. There is nothing in the content you present that identifies what database it is from, and without the full path/file name of the alert, we can't trust it.
Fri Feb 19 08:22:09 2016
ORACLE V10.1.0.2.0 - Production vsnsta=0
vsnsql=13 vsnxtr=3
Windows NT Version V5.2 Service Pack 2
CPU : 2 - type 586, 2 Physical Cores
Process Affinity: 0x00000000
Memory (A/P) : PH:3238M/4095M, PG:5159M/5977M, VA:1958M/2047M
Fri Feb 19 08:22:09 2016
Running without dynamic strand for Non-Enterprise Edition
Fri Feb 19 08:22:09 2016
Starting ORACLE instance (normal)
Fri Feb 19 08:22:09 2016
Running with 1 strand for Non-Enterprise Edition
LICENSE_MAX_SESSION = 0
LICENSE_SESSIONS_WARNING = 0
Picked latch-free SCN scheme 2
KCCDEBUG_LEVEL = 0
Using LOG_ARCHIVE_DEST_1 parameter default value as D:\oracle\HomeVega10G\RDBMS
Autotune of undo retention is turned on.
Running with 1 strand for Non-Enterprise Edition
Dynamic strands is set to FALSE
Running with 1 shared and 18 private strand(s). Zero-copy redo is FALSE
IMODE=BR
ILAT =18
LICENSE_MAX_USERS = 0
SYS auditing is disabled
Quote:I don't know if GIMA database is up and online now. How can i check this ?
[Updated on: Sun, 21 February 2016 13:40] Report message to a moderator
|
|
|
Goto Forum:
Current Time: Thu Mar 06 05:47:00 CST 2025
|