"Connected to an Idle Instance" Message when Connecting Bequeath to a Running Instance
Last updated on OCTOBER 10, 2017
Applies to:
Oracle Database - Enterprise Edition - Version 8.0.6.0 to 11.2.0.1.0 [Release 8.0.6 to 11.2]Information in this document applies to any platform.
***Checked for relevance on 26-Oct-2016***
Symptoms
While connecting bequeath to a running instance the following message appears :
$ export ORACLE_SID=test
$ sqlplus "/ as sysdba"
SQL*Plus: Release 10.2.0.1.0 - Production on Wed Jun 6 12:17:14 2007
Copyright (c) 1982, 2005, Oracle. All rights reserved.
Connected to an idle instance.
SQL>
$ sqlplus "/ as sysdba"
SQL*Plus: Release 10.2.0.1.0 - Production on Wed Jun 6 12:17:14 2007
Copyright (c) 1982, 2005, Oracle. All rights reserved.
Connected to an idle instance.
SQL>
The "test" instance was running and this was verified with the ps command:
$ ps -ef | grep pmon
oracle 9714 1 0 May28 ? 00:00:07 ora_pmon_test
oracle 32635 1 0 May30 ? 00:00:01 ora_pmon_orcl115b
oracle 9714 1 0 May28 ? 00:00:07 ora_pmon_test
oracle 32635 1 0 May30 ? 00:00:01 ora_pmon_orcl115b
Furthermore the test instance can be started up:
$ export ORACLE_SID=test
$ sqlplus "/ as sysdba"
SQL*Plus: Release 10.2.0.1.0 - Production on Wed Jun 6 12:17:14 2007
Copyright (c) 1982, 2005, Oracle. All rights reserved.
Connected to an idle instance.
SQL> startup nomount
ORACLE instance started.
Total System Global Area 866291712 bytes
Fixed Size 1302036 bytes
Variable Size 239075820 bytes
Database Buffers 620756992 bytes
Redo Buffers 5156864 bytes
SQL>
$ sqlplus "/ as sysdba"
SQL*Plus: Release 10.2.0.1.0 - Production on Wed Jun 6 12:17:14 2007
Copyright (c) 1982, 2005, Oracle. All rights reserved.
Connected to an idle instance.
SQL> startup nomount
ORACLE instance started.
Total System Global Area 866291712 bytes
Fixed Size 1302036 bytes
Variable Size 239075820 bytes
Database Buffers 620756992 bytes
Redo Buffers 5156864 bytes
SQL>
The alert.log was immediately written to with the informations pertaining to the startup of the operation. When a log switch was performed in the "real" test instance (within a SQL*NET connection) then the alert.log was appended with the corresponding information. So at that point on the system there were two instances "test" running from the same Oracle Home
$ ps -ef | grep pmon
oracle 9714 1 0 May28 ? 00:00:07 ora_pmon_test
oracle 32635 1 0 May30 ? 00:00:01 ora_pmon_orcl115b
oracle 10382 1 0 12:27 ? 00:00:00 ora_pmon_test
oracle 9714 1 0 May28 ? 00:00:07 ora_pmon_test
oracle 32635 1 0 May30 ? 00:00:01 ora_pmon_orcl115b
oracle 10382 1 0 12:27 ? 00:00:00 ora_pmon_test
Cause
Sign In with your My Oracle Support account |
|
Don't have a My Oracle Support account? Click to get started |
My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms