Skip to Main Content

Oracle Database Express Edition (XE)

Announcement

For appeals, questions and feedback about Oracle Forums, please email oracle-forums-moderators_us@oracle.com. Technical questions should be asked in the appropriate category. Thank you!

ORA-27101: shared memory realm does not exist

543310Nov 2 2006 — edited Nov 2 2006
Hi,

I installed OracleExpress on a windows 2003 server. Right after the
installation, I was able to create and use a database. Then, after the
first reboot, the database didn't start automatically, but after
SQL> connect /
SQL> startup
things worked fine again. Now, after a third reboot, this trick doesn't
work anymore:
SQL> connect /
ERROR:
ORA-01034: ORACLE not available
ORA-27101: shared memory realm does not exist

Q: How can I fix this? (there is already data in my database that I
really would like to use) And that Oracle behaves differently after the
second and the third reboot?

Thanks in advance for your help. Below is the result of a few obvious
things that I checked before posting this message.

I've checked the ORACLE_SID in the environment and it is set to XE.
>set
...
ORACLE_SID=XE
...

The listener is running:
>lsnrctl status XE
STATUS of the LISTENER
------------------------
Alias LISTENER
Version TNSLSNR for 32-bit W..: Ver.. 10.2.0.1.0 - Production
Start Date 01-NOV-2006 10:29:36
Uptime 0 days 0 hr. 1 min. 22 sec
Trace Level off
Security ON: Local OS Authentication
SNMP OFF
Default Service XE

and tnsping works:
>tnsping xe
...
OK (30 msec)

The init.ora only contains valid paths (the installation was done 'out of
the box', and I tried to stick to the defaults... I did not edit the
config files manually). The alert_xe.log file contains no data after the
third reboot (1 nov). I don't know what the look for in the alert_xe.log.
I've copied the content below, starting from thursday 26th of october.

[alert_xe.log]
Thu Oct 26 11:20:04 2006
db_recovery_file_dest_size of 10240 MB is 0.98% used. This is a
user-specified limit on the amount of space that will be used by this
database for recovery-related files, and does not reflect the amount of
space available in the underlying filesystem or ASM diskgroup.
Dump file f:\oraclexe\app\oracle\admin\xe\bdump\alert_xe.log
Mon Oct 30 11:35:02 2006
ORACLE V10.2.0.1.0 - Production vsnsta=0
vsnsql=14 vsnxtr=3
Windows Server 2003 Version V5.2 Service Pack 1
CPU : 1 - type 586, 1 Physical Cores
Process Affinity : 0x00000000
Memory (Avail/Total): Ph:957M/1271M, Ph+PgF:1514M/1697M, VA:1933M/2047M
Mon Oct 30 11:35:02 2006
Starting ORACLE instance (normal)
LICENSE_MAX_SESSION = 0
LICENSE_SESSIONS_WARNING = 0
Picked latch-free SCN scheme 2
Using LOG_ARCHIVE_DEST_10 parameter default value as
USE_DB_RECOVERY_FILE_DEST
Autotune of undo retention is turned on.
IMODE=BR
ILAT =10
LICENSE_MAX_USERS = 0
SYS auditing is disabled
ksdpec: called for event 13740 prior to event group initialization
Starting up ORACLE RDBMS Version: 10.2.0.1.0.
System parameters with non-default values:
sessions = 49
__shared_pool_size = 100663296
__large_pool_size = 12582912
__java_pool_size = 4194304
__streams_pool_size = 0
spfile = F:\ORACLEXE\APP\ORACLE\PRODUCT\10.2.0\SERVER
\DBS\SPFILEXE.ORA
sga_target = 348127232
control_files = F:\ORACLEXE\ORADATA\XE\CONTROL.DBF
__db_cache_size = 226492416
compatible = 10.2.0.1.0
db_recovery_file_dest = F:\oraclexe\app\oracle\flash_recovery_area
db_recovery_file_dest_size= 10737418240
undo_management = AUTO
undo_tablespace = UNDO
remote_login_passwordfile= EXCLUSIVE
dispatchers = (PROTOCOL=TCP) (SERVICE=XEXDB)
shared_servers = 4
job_queue_processes = 4
audit_file_dest = F:\ORACLEXE\APP\ORACLE\ADMIN\XE\ADUMP
background_dump_dest = F:\ORACLEXE\APP\ORACLE\ADMIN\XE\BDUMP
user_dump_dest = F:\ORACLEXE\APP\ORACLE\ADMIN\XE\UDUMP
core_dump_dest = F:\ORACLEXE\APP\ORACLE\ADMIN\XE\CDUMP
db_name = XE
open_cursors = 300
os_authent_prefix =
pga_aggregate_target = 115343360
PSP0 started with pid=3, OS id=3044
MMAN started with pid=4, OS id=2540
PMON started with pid=2, OS id=3400
DBW0 started with pid=5, OS id=2140
LGWR started with pid=6, OS id=3816
CKPT started with pid=7, OS id=972
SMON started with pid=8, OS id=2532
RECO started with pid=9, OS id=1904
CJQ0 started with pid=10, OS id=2668
MMON started with pid=11, OS id=3640
MMNL started with pid=12, OS id=1948
Mon Oct 30 11:35:07 2006
starting up 1 dispatcher(s) for network address '(ADDRESS=(PARTIAL=YES)
(PROTOCOL=TCP))'...
starting up 4 shared server(s) ...
Oracle Data Guard is not available in this edition of Oracle.
Mon Oct 30 11:35:13 2006
ALTER DATABASE MOUNT
Mon Oct 30 11:35:17 2006
Setting recovery target incarnation to 2
Mon Oct 30 11:35:17 2006
Successful mount of redo thread 1, with mount id 2486284977
Mon Oct 30 11:35:17 2006
Database mounted in Exclusive Mode
Completed: ALTER DATABASE MOUNT
Mon Oct 30 11:35:18 2006
ALTER DATABASE OPEN
Mon Oct 30 11:35:19 2006
Beginning crash recovery of 1 threads
Mon Oct 30 11:35:19 2006
Started redo scan
Mon Oct 30 11:35:19 2006
Completed redo scan
1132 redo blocks read, 278 data blocks need recovery
Mon Oct 30 11:35:19 2006
Started redo application at
Thread 1: logseq 9, block 73566
Mon Oct 30 11:35:20 2006
Recovery of Online Redo Log: Thread 1 Group 2 Seq 9 Reading mem 0
Mem# 0 errs 0: F:\ORACLEXE\APP\ORACLE\FLASH_RECOVERY_AREA\XE\ONLINELOG
\O1_MF_2_2LSS2S5V_.LOG
Mon Oct 30 11:35:22 2006
Completed redo application
Mon Oct 30 11:35:22 2006
Completed crash recovery at
Thread 1: logseq 9, block 74698, scn 555729
278 data blocks read, 278 data blocks written, 1132 redo blocks read
Mon Oct 30 11:35:23 2006
Thread 1 advanced to log sequence 10
Thread 1 opened at log sequence 10
Current log# 1 seq# 10 mem# 0: F:\ORACLEXE\APP\ORACLE
\FLASH_RECOVERY_AREA\XE\ONLINELOG\O1_MF_1_2LSS2QJ3_.LOG
Successful open of redo thread 1
Mon Oct 30 11:35:23 2006
SMON: enabling cache recovery
Mon Oct 30 11:35:28 2006
Successfully onlined Undo Tablespace 1.
Mon Oct 30 11:35:28 2006
SMON: enabling tx recovery
Mon Oct 30 11:35:28 2006
Database Characterset is WE8MSWIN1252
replication_dependency_tracking turned off (no async multimaster
replication found)
Starting background process QMNC
QMNC started with pid=19, OS id=3652
Mon Oct 30 11:35:43 2006
Completed: ALTER DATABASE OPEN
Mon Oct 30 11:35:49 2006
db_recovery_file_dest_size of 10240 MB is 0.98% used. This is a
user-specified limit on the amount of space that will be used by this
database for recovery-related files, and does not reflect the amount of
space available in the underlying filesystem or ASM diskgroup.
Mon Oct 30 11:35:58 2006
Memory Notification: Library Cache Object loaded into SGA
Heap size 2208K exceeds notification threshold (2048K)
KGL object name :XDB.XDbD/PLZ01TcHgNAgAIIegtw==
Comments
Locked Post
New comments cannot be posted to this locked post.
Post Details
Locked on Nov 30 2006
Added on Nov 2 2006
5 comments
504 views