Home » RDBMS Server » Networking and Gateways » Lsnrctl stop -> database crashes (Oracle Database 12c Standard Edition Release 12.2.0.1.0 - 64bit, Oracle Linux Server release 7.3)
Lsnrctl stop -> database crashes [message #664627] Tue, 25 July 2017 06:41 Go to next message
DjZg
Messages: 6
Registered: July 2017
Junior Member
Hello,

I had some strange problem with lsnrctl stop command. When I executed lsnrctl stop command, my database shut down.
Here is listener.log:

2017-07-25T10:26:13.168130+02:00
WARNING: Subscription for node down event still pending
25-JUL-2017 10:26:13 * (CONNECT_DATA=(CID=(PROGRAM=)(HOST=db.lokalna)(USER=oracle))(COMMAND=status)(ARGUMENTS=64)(SERVICE=LISTENER)(VERSION=203424000)) * status * 0
2017-07-25T10:26:33.811032+02:00
No longer listening on: (DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=db.lokalna)(PORT=1521)))
No longer listening on: (DESCRIPTION=(ADDRESS=(PROTOCOL=ipc)(KEY=EXTPROC1521)))
Listener completed notification to CRS on stop
25-JUL-2017 10:26:33 * (CONNECT_DATA=(CID=(PROGRAM=)(HOST=db.lokalna)(USER=oracle))(COMMAND=stop)(ARGUMENTS=64)(SERVICE=LISTENER)(VERSION=203424000)(CRS=ON)) * stop * 0
2017-07-25T10:26:58.459708+02:00
System parameter file is /u01/app/oracle/product/12.2.0.1/db_1/network/admin/listener.ora
Log messages written to /u01/app/oracle/diag/tnslsnr/db/listener/alert/log.xml
Trace information written to /u01/app/oracle/diag/tnslsnr/db/listener/trace/ora_5207_140649488617856.trc
Trace level is currently 0

Started with pid=5207
Listening on: (DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=db.lokalna)(PORT=1521)))
Listening on: (DESCRIPTION=(ADDRESS=(PROTOCOL=ipc)(KEY=EXTPROC1521)))
Listener completed notification to CRS on start

And alert.log:

25.07.2017 10:26:33	Shutdown instance (immediate)	Shutting down instance (immediate) (OS id: 5134)
25.07.2017 10:26:35	Shutdown background process	Stopping background process SMCO
25.07.2017 10:26:36	Shutdown instance	Shutting down instance: further logons disabled
25.07.2017 10:26:36	Shutdown background process	Stopping background process CJQ0
Stopping background process MMNL
25.07.2017 10:26:37	Shutdown background process	Stopping background process MMON
25.07.2017 10:26:38		alter pluggable database all close immediate
25.07.2017 10:26:38	Alter database	BAZAHOSS(3):JIT: pid 5134 requesting stop
Pluggable database BAZAHOSS closed
Completed: alter pluggable database all close immediate
PDB$SEED(2):JIT: pid 5134 requesting stop
License high water mark = 9
Dispatchers and shared servers shutdown
ALTER DATABASE CLOSE NORMAL
Stopping Emon pool
alter pluggable database all close immediate
Completed: alter pluggable database all close immediate
Stopping Emon pool
25.07.2017 10:26:39		Shutting down archive processes
25.07.2017 10:26:39		TT00: Gap Manager exiting (PID:3228)
25.07.2017 10:26:40		Archiving is disabled
25.07.2017 10:26:40		Thread 1 closed at log sequence 62
Successful close of redo thread 1
25.07.2017 10:26:40	Alter database	Completed: ALTER DATABASE CLOSE NORMAL
ALTER DATABASE DISMOUNT
Shutting down archive processes
Archiving is disabled
Completed: ALTER DATABASE DISMOUNT
25.07.2017 10:26:41		ARCH: Archival disabled due to shutdown: 1089
Shutting down archive processes
Archiving is disabled
25.07.2017 10:26:42		JIT: pid 5134 requesting stop
25.07.2017 10:26:43		ARCH: Archival disabled due to shutdown: 1089
25.07.2017 10:26:43	Shutdown background process	Stopping background process VKTM
Shutting down archive processes
Archiving is disabled
25.07.2017 10:26:43		JIT: pid 5134 requesting stop
25.07.2017 10:26:52		Instance shutdown complete (OS id: 5134)
25.07.2017 10:35:25	Startup instance	Adjusting the requested value of parameter parallel_max_servers
from 0 to 1 due to running in CDB mode
Starting ORACLE instance (normal) (OS id: 5507)
25.07.2017 10:35:25		CLI notifier numLatches:7 maxDescs:849
25.07.2017 10:35:25		**********************************************************************
25.07.2017 10:35:25		Dump of system resources acquired for SHARED GLOBAL AREA (SGA)
25.07.2017 10:35:25		Per process system memlock (soft) limit = 64K
25.07.2017 10:35:25		Expected per process system memlock (soft) limit to lock
 SHARED GLOBAL AREA (SGA) into memory: 2402M
25.07.2017 10:35:25		Available system pagesizes:
  4K, 2048K
25.07.2017 10:35:25		Supported system pagesize(s):
25.07.2017 10:35:25		PAGESIZE  AVAILABLE_PAGES  EXPECTED_PAGES  ALLOCATED_PAGES  ERROR(s)
25.07.2017 10:35:25		4K       Configured               4          614404        NONE
25.07.2017 10:35:25		2048K                0            1201               0        NONE
25.07.2017 10:35:25		RECOMMENDATION:
25.07.2017 10:35:25		1. For optimal performance, configure system with expected number 
 of pages for every supported system pagesize prior to the next 
 instance restart operation.
25.07.2017 10:35:25		2. Increase per process memlock (soft) limit to at least 2402MB
 to lock 100% of SHARED GLOBAL AREA (SGA) pages into physical memory
25.07.2017 10:35:25		**********************************************************************
LICENSE_MAX_SESSION = 0
LICENSE_SESSIONS_WARNING = 0
Initial number of CPU is 4
Number of processor cores in the system is 4
Number of processor sockets in the system is 2
Using LOG_ARCHIVE_DEST_1 parameter default value as USE_DB_RECOVERY_FILE_DEST
Autotune of undo retention is turned on. 
IMODE=BR
ILAT =84
LICENSE_MAX_USERS = 0
SYS auditing is enabled
NOTE: remote asm mode is local (mode 0x1; from cluster type)
NOTE: Using default ASM root directory ASM
NOTE: Cluster configuration type = NONE [2]
Oracle Database 12c Standard Edition Release 12.2.0.1.0 - 64bit Production.
ORACLE_HOME:    /u01/app/oracle/product/12.2.0.1/db_1
System name:	Linux
Node name:	hossdb.lokalna
Release:	3.10.0-514.26.2.el7.x86_64
Version:	#1 SMP Tue Jul 4 07:15:04 PDT 2017
Machine:	x86_64
Using parameter settings in server-side spfile /u01/app/oracle/product/12.2.0.1/db_1/dbs/spfilehossroot.ora
System parameters with non-default values:
  processes                = 500
  nls_language             = "CROATIAN"
  nls_territory            = "CROATIA"
  sga_target               = 2400M
  control_files            = "/u02/oradata/hossroot/control01.ctl"
  control_files            = "/u02/fast_recovery_area/hossroot/control02.ctl"
  db_block_size            = 8192
  compatible               = "12.2.0"
  db_recovery_file_dest    = "/u02/fast_recovery_area/hossroot"
  db_recovery_file_dest_size= 17271M
  undo_tablespace          = "UNDOTBS1"
  remote_login_passwordfile= "EXCLUSIVE"
  dispatchers              = "(PROTOCOL=TCP) (SERVICE=hossrootXDB)"
  local_listener           = "LISTENER_HOSSROOT"
  audit_file_dest          = "/u01/app/oracle/admin/hossroot/adump"
  audit_trail              = "DB"
  db_name                  = "hossroot"
  open_cursors             = 300
  pga_aggregate_target     = 799M
  diagnostic_dest          = "/u01/app/oracle"
  enable_pluggable_database= TRUE
NOTE:
25.07.2017 10:35:25	Startup background process	============================================================
NOTE: PatchLevel of this instance 0
============================================================
Starting background process PMON
25.07.2017 10:35:25	Startup background process	PMON started with pid=2, OS id=5519 
Starting background process CLMN
25.07.2017 10:35:25	Startup background process	CLMN started with pid=3, OS id=5521 
Starting background process PSP0
Starting background process VKTM
25.07.2017 10:35:25	Startup background process	PSP0 started with pid=4, OS id=5523
25.07.2017 10:35:26	Startup background process	VKTM started with pid=5, OS id=5525 at elevated (RT) priority
25.07.2017 10:35:26	Startup background process	Starting background process GEN0
25.07.2017 10:35:26	Startup background process	VKTM running at (1)millisec precision with DBRM quantum (100)ms
Starting background process MMAN
25.07.2017 10:35:26	Startup background process	GEN0 started with pid=6, OS id=5529
25.07.2017 10:35:26	Startup background process	MMAN started with pid=7, OS id=5531 
Starting background process GEN1
Starting background process DIAG
25.07.2017 10:35:26	Startup background process	GEN1 started with pid=9, OS id=5535_5537 
Starting background process OFSD
25.07.2017 10:35:26	Startup background process	DIAG started with pid=11, OS id=5539 
Starting background process DBRM
25.07.2017 10:35:26	Startup background process	OFSD started with pid=12, OS id=5541_5543
25.07.2017 10:35:26	Startup background process	Oracle running with ofslib:'Oracle File Server Library' version=2
Starting background process VKRM
25.07.2017 10:35:26	Startup background process	DBRM started with pid=14, OS id=5545 
Starting background process SVCB
25.07.2017 10:35:26	Startup background process	VKRM started with pid=15, OS id=5547
25.07.2017 10:35:26	Startup background process	SVCB started with pid=16, OS id=5549 
Starting background process PMAN
Starting background process DIA0
25.07.2017 10:35:26	Startup background process	PMAN started with pid=17, OS id=5551
25.07.2017 10:35:26	Startup background process	DIA0 started with pid=18, OS id=5553 
Starting background process DBW0
25.07.2017 10:35:26	Startup background process	DBW0 started with pid=19, OS id=5555 
Starting background process LGWR
Starting background process CKPT
25.07.2017 10:35:26	Startup background process	LGWR started with pid=20, OS id=5557
25.07.2017 10:35:26	Startup background process	CKPT started with pid=21, OS id=5559
25.07.2017 10:35:26	Startup background process	LGWR slave LG00 created with pid=22, OS pid=5561
Starting background process SMON
25.07.2017 10:35:26	Startup background process	SMON started with pid=23, OS id=5563 
LGWR slave LG01 created with pid=24, OS pid=5565
Starting background process SMCO
25.07.2017 10:35:26	Startup background process	SMCO started with pid=25, OS id=5567 
Starting background process RECO
25.07.2017 10:35:26	Startup background process	RECO started with pid=26, OS id=5569 
Starting background process LREG
25.07.2017 10:35:26	Startup background process	LREG started with pid=28, OS id=5573 
Starting background process PXMN
25.07.2017 10:35:26	Startup background process	PXMN started with pid=30, OS id=5577 
Starting background process FENC
Starting background process MMON
25.07.2017 10:35:26	Startup background process	FENC started with pid=31, OS id=5579 
Starting background process MMNL
25.07.2017 10:35:26	Startup background process	MMON started with pid=32, OS id=5581
25.07.2017 10:35:26	Startup background process	MMNL started with pid=31, OS id=5583
25.07.2017 10:35:26	Startup background process	starting up 1 dispatcher(s) for network address '(ADDRESS=(PARTIAL=YES)(PROTOCOL=TCP))'...
starting up 1 shared server(s) ...
Starting background process TMON
25.07.2017 10:35:26	Startup background process	TMON started with pid=35, OS id=5589 
ORACLE_BASE from environment = /u01/app/oracle
25.07.2017 10:35:26	Alter database	ALTER DATABASE   MOUNT
25.07.2017 10:35:29		Using default pga_aggregate_limit of 2048 MB
25.07.2017 10:35:31		Network throttle feature is disabled as mount time
25.07.2017 10:35:31		Successful mount of redo thread 1, with mount id 1567345518
25.07.2017 10:35:31	Alter database	Database mounted in Exclusive Mode
Lost write protection disabled
Using STANDBY_ARCHIVE_DEST parameter default value as USE_DB_RECOVERY_FILE_DEST
Completed: ALTER DATABASE   MOUNT
25.07.2017 10:35:31	Alter database open	ALTER DATABASE OPEN
25.07.2017 10:35:31		Ping without log force is disabled:
  instance mounted in exclusive mode.
Endian type of dictionary set to little
25.07.2017 10:35:31		TT00: Gap Manager starting (PID:5599)
25.07.2017 10:35:31		Thread 1 opened at log sequence 62
  Current log# 2 seq# 62 mem# 0: /u02/oradata/hossroot/redo02.log
Successful open of redo thread 1
25.07.2017 10:35:31	Startup background process	[5597] Successfully onlined Undo Tablespace 2.
Undo initialization finished serial:0 start:952348052 end:952348093 diff:41 ms (0.0 seconds)
Verifying minimum file header compatibility for tablespace encryption for pdb 1..
Verifying file header compatibility for tablespace encryption completed for pdb 1
Database Characterset is AL32UTF8
Opening with Resource Manager plan: DEFAULT_CDB_PLAN 
replication_dependency_tracking turned off (no async multimaster replication found)
Starting background process AQPC
25.07.2017 10:35:31	Startup background process	AQPC started with pid=39, OS id=5605 
PDB$SEED(2):Autotune of undo retention is turned on. 
PDB$SEED(2):Endian type of dictionary set to little
PDB$SEED(2):Undo initialization finished serial:0 start:952348804 end:952348804 diff:0 ms (0.0 seconds)
PDB$SEED(2):Database Characterset for PDB$SEED is AL32UTF8
25.07.2017 10:35:32		PDB$SEED(2):Opatch validation is skipped for PDB PDB$SEED (con_id=0)
25.07.2017 10:35:32		PDB$SEED(2):Opening pdb with Resource Manager plan: DEFAULT_PLAN
BAZAHOSS(3):Autotune of undo retention is turned on. 
BAZAHOSS(3):Endian type of dictionary set to little
BAZAHOSS(3):[5597] Successfully onlined Undo Tablespace 2.
BAZAHOSS(3):Undo initialization finished serial:0 start:952349403 end:952349493 diff:90 ms (0.1 seconds)
BAZAHOSS(3):Database Characterset for BAZAHOSS is AL32UTF8
BAZAHOSS(3):Opatch validation is skipped for PDB BAZAHOSS (con_id=0)
25.07.2017 10:35:33	Startup background process	BAZAHOSS(3):Opening pdb with Resource Manager plan: DEFAULT_PLAN
Pluggable database BAZAHOSS opened read write
Starting background process CJQ0
25.07.2017 10:35:33	Alter database open	CJQ0 started with pid=40, OS id=5755 
Completed: ALTER DATABASE OPEN
25.07.2017 10:35:33		Shared IO Pool defaulting to 112MB. Trying to get it from Buffer Cache for process 5581.
===========================================================
Dumping current patch information
===========================================================
No patches have been applied
===========================================================

After I try to stop listener again, everything was fine.
Does anyone have idea what could be the problem or what to check?
Thank you
Re: Lsnrctl stop -> database crashes [message #664628 is a reply to message #664627] Tue, 25 July 2017 06:59 Go to previous messageGo to next message
Roachcoach
Messages: 1501
Registered: May 2010
Location: UK
Senior Member
What exactly did you run and what is the HA setup, if any?
Re: Lsnrctl stop -> database crashes [message #664629 is a reply to message #664628] Tue, 25 July 2017 07:13 Go to previous messageGo to next message
DjZg
Messages: 6
Registered: July 2017
Junior Member
I only run command:
[oracle@db ~]$ lsnrctl stop
Nothing special.
There's no any HA, its simple, non-RAC,no ASM, no Clusterware..
Re: Lsnrctl stop -> database crashes [message #664630 is a reply to message #664629] Tue, 25 July 2017 07:38 Go to previous messageGo to next message
BlackSwan
Messages: 25751
Registered: January 2009
Location: SoCal
Senior Member
I am hard pressed to believe that lsnrctl stop directly resulted in the database going down.

Content of alert_SID.log file indicates that "SHUTDOWN IMMEDIATE" was issued & 9 minute later instance was (re)started

>25.07.2017 10:26:52 Instance shutdown complete (OS id: 5134)
>25.07.2017 10:35:25 Startup instance Adjusting the requested value of parameter parallel_max_servers
Re: Lsnrctl stop -> database crashes [message #664631 is a reply to message #664630] Tue, 25 July 2017 08:00 Go to previous messageGo to next message
DjZg
Messages: 6
Registered: July 2017
Junior Member
Quote:
I am hard pressed to believe that lsnrctl stop directly resulted in the database going down.
I know its strange so i wanna know what happened.

I didnt issue "SHUTDOWN IMMEDIATE"
As you can see at the same time (10:26:33) was:
5-JUL-2017 10:26:33 * (CONNECT_DATA=(CID=(PROGRAM=)(HOST=db.lokalna)(USER=oracle))(COMMAND=stop)(ARGUMENTS=64)(SERVICE=LISTENER)(VERSION=203424000)(CRS=ON)) * stop * 0
2017-07-25T10:26:58.459708+02:00

and
25.07.2017 10:26:33	Shutdown instance (immediate)	Shutting down instance (immediate) (OS id: 5134)

Its hard to execute lsnrctl stop and shutdown immediate in the same second Smile
Here is also audit trace file (from adump):

Tue Jul 25 10:26:33 2017 +02:00
LENGTH : '260'
ACTION :[7] 'CONNECT'
DATABASE USER:[1] '/'
PRIVILEGE :[6] 'SYSDBA'
CLIENT USER:[6] 'oracle'
CLIENT TERMINAL:[0] ''
STATUS:[1] '0'
DBID:[10] '1566401467'
SESSIONID:[10] '4294967295'
USERHOST:[14] 'db.lokalna'
CLIENT ADDRESS:[0] ''
ACTION NUMBER:[3] '100'

Tue Jul 25 10:26:33 2017 +02:00
LENGTH : '258'
ACTION :[6] 'COMMIT'
DATABASE USER:[1] '/'
PRIVILEGE :[6] 'SYSDBA'
CLIENT USER:[6] 'oracle'
CLIENT TERMINAL:[0] ''
STATUS:[1] '0'
DBID:[10] '1566401467'
SESSIONID:[10] '4294967295'
USERHOST:[14] 'db.lokalna'
CLIENT ADDRESS:[0] ''
ACTION NUMBER:[2] '44'

Tue Jul 25 10:26:33 2017 +02:00
LENGTH : '258'
ACTION :[6] 'COMMIT'
DATABASE USER:[1] '/'
PRIVILEGE :[6] 'SYSDBA'
CLIENT USER:[6] 'oracle'
CLIENT TERMINAL:[0] ''
STATUS:[1] '0'
DBID:[10] '1566401467'
SESSIONID:[10] '4294967295'
USERHOST:[14] 'db.lokalna'
CLIENT ADDRESS:[0] ''
ACTION NUMBER:[2] '44'

Tue Jul 25 10:26:33 2017 +02:00
LENGTH : '398'
ACTION :[145] 'SELECT SYS_CONTEXT('USERENV','CDB_NAME'),    SYS_CONTEXT('USERENV','CON_NAME'),    SYS_CONTEXT('USERENV','IS_APPLICATION_ROOT')    FROM SYS.DUAL^@'
DATABASE USER:[1] '/'
PRIVILEGE :[6] 'SYSDBA'
CLIENT USER:[6] 'oracle'
CLIENT TERMINAL:[0] ''
STATUS:[1] '0'
DBID:[10] '1566401467'
SESSIONID:[10] '4294967295'
USERHOST:[14] 'db.lokalna'
CLIENT ADDRESS:[0] ''
ACTION NUMBER:[1] '3'

Tue Jul 25 10:26:40 2017 +02:00
LENGTH : '280'
ACTION :[27] 'ALTER DATABASE CLOSE NORMAL'
DATABASE USER:[1] '/'
PRIVILEGE :[6] 'SYSDBA'
CLIENT USER:[6] 'oracle'
CLIENT TERMINAL:[0] ''
STATUS:[1] '0'
DBID:[10] '1566401467'
SESSIONID:[10] '4294967295'
USERHOST:[14] 'db.lokalna'
CLIENT ADDRESS:[0] ''
ACTION NUMBER:[2] '35'

Tue Jul 25 10:26:40 2017 +02:00
LENGTH : '265'
ACTION :[23] 'ALTER DATABASE DISMOUNT'
DATABASE USER:[1] '/'
PRIVILEGE :[6] 'SYSDBA'
CLIENT USER:[6] 'oracle'
CLIENT TERMINAL:[0] ''
STATUS:[1] '0'
DBID:[0] ''
SESSIONID:[10] '4294967295'
USERHOST:[14] 'db.lokalna'
CLIENT ADDRESS:[0] ''
ACTION NUMBER:[2] '35'

Tue Jul 25 10:26:40 2017 +02:00
LENGTH : '261'
ACTION :[18] 'SHUTDOWN IMMEDIATE'
DATABASE USER:[1] '/'
PRIVILEGE :[6] 'SYSDBA'
CLIENT USER:[6] 'oracle'
CLIENT TERMINAL:[0] ''
STATUS:[1] '0'
DBID:[0] ''
SESSIONID:[10] '4294967295'
USERHOST:[14] 'db.lokalna'
CLIENT ADDRESS:[0] ''
ACTION NUMBER:[3] '139'

[Updated on: Tue, 25 July 2017 08:02]

Report message to a moderator

Re: Lsnrctl stop -> database crashes [message #664634 is a reply to message #664631] Tue, 25 July 2017 08:43 Go to previous messageGo to next message
DjZg
Messages: 6
Registered: July 2017
Junior Member
I found one more thing in linux log file:

Jul 25 10:26:33 db dbshut: Processing Database instance "dbroot": log file /u01/app/oracle/product/12.2.0.1/db_1/shutdown.log

So i believe script /u01/app/oracle/product/12.2.0.1/db_1/bin/dbshut was triggered after lsnrctl stop. But why?

[Updated on: Tue, 25 July 2017 08:43]

Report message to a moderator

Re: Lsnrctl stop -> database crashes [message #664635 is a reply to message #664634] Tue, 25 July 2017 08:44 Go to previous messageGo to next message
BlackSwan
Messages: 25751
Registered: January 2009
Location: SoCal
Senior Member
DjZg wrote on Tue, 25 July 2017 06:43
I found one more thing in linux log file:

Jul 25 10:26:33 db dbshut: Processing Database instance "dbroot": log file /u01/app/oracle/product/12.2.0.1/db_1/shutdown.log

So i believe script /u01/app/oracle/product/12.2.0.1/db_1/bin/dbshut was triggered after lsnrctl stop. But why?
IMO, not possible
Re: Lsnrctl stop -> database crashes [message #664641 is a reply to message #664635] Tue, 25 July 2017 13:24 Go to previous messageGo to next message
DjZg
Messages: 6
Registered: July 2017
Junior Member
You have all logs which tells when is lsnrctl stopped, instance shutdown by dbshut. Everything at the same time.
So whats your theory?
Re: Lsnrctl stop -> database crashes [message #664652 is a reply to message #664641] Wed, 26 July 2017 06:47 Go to previous messageGo to next message
EdStevens
Messages: 863
Registered: September 2013
Senior Member
I find this message in your listener.log to be very interesting:

"Listener completed notification to CRS on stop"

This reference to CRS suggests that you are using Grid Infrastructure. I find this message in the listener log of my servers running GI to support a stand-alone ASM instance. I never find it in the logs on my non-GI servers. Matching the timestamp of that message in my listener log with the alert log of a database on that server, I see the database was shut down at the same time. And matching that time against my putty logs, I see that I was running an upgrade of my GI from 11.2.0.4 to 12.1.0.2 at the time.

So, if as you say there is no RAC, no ASM, no GI installation, why is the listener reporting a notification to CRS?

Re: Lsnrctl stop -> database crashes [message #664654 is a reply to message #664627] Wed, 26 July 2017 06:58 Go to previous messageGo to next message
EdStevens
Messages: 863
Registered: September 2013
Senior Member
Also posted in MOS Communities at https://community.oracle.com/thread/4066775 (for those that have access).
Re: Lsnrctl stop -> database crashes [message #664658 is a reply to message #664652] Wed, 26 July 2017 07:20 Go to previous message
DjZg
Messages: 6
Registered: July 2017
Junior Member
Yes, i saw that, but Im not using Clusterware:

[root@db ~]# find / -name crsctl -ls
[root@db ~]#
Previous Topic: LISTENER BLOCKED the instance during nomount state
Next Topic: Oracle: ORA-12504: TNS:listener was not given the SERVICE_NAME in CONNECT_DATA"
Goto Forum:
  


Current Time: Sat Dec 16 22:33:02 CST 2017

Total time taken to generate the page: 0.63866 seconds