dbTalk Databases Forums  

ora-01034 and ora-27101 after reboot

comp.databases.oracle.server comp.databases.oracle.server


Discuss ora-01034 and ora-27101 after reboot in the comp.databases.oracle.server forum.



Reply
 
Thread Tools Display Modes
  #1  
Old   
sien
 
Posts: n/a

Default ora-01034 and ora-27101 after reboot - 06-24-2003 , 02:49 AM






Hello!

I have looked for the solution for this problem in this newsgroup and
tried every possibility but it doesn't work yet.
I install oracle enterprise edition 8.17 on windows 2000 server. The
machine is pentium 4, 2GHz, 512 MB ram.
I just have one database running on this server. Everytime I reboot
the server and I try to connect to the database I get this error:
ORA-01034: ORACLE not available
ORA-27101: shared memory realm does not exist
If I look at control panel/services, the database oracle service and
the listener service are started.
What I can do to be able to connect to the database is to start
Database configuration assistant, select 'Change database
configuration' option and click on next, next, finish.

This is the init.ora

db_name = sfma
db_block_size = 4096
db_files = 10
control_files = (D:\oracle\ora81\database\ctl1sfma.ora,
D:\oracle\ora81\database\ctl2sfma.ora)
rollback_segments = (rb0, rb1, rb2, rb3)

remote_login_passwordfile = shared
global_names = TRUE

text_enable = FALSE
mts_max_servers = 30

optimizer_mode = RULE


# options for advanced replication

parallel_max_servers = 5 # number of processors of server times 5

job_queue_processes = 2
job_queue_interval = 10

# Distributed_Transactions = 5

# settings for memory management

shared_pool_size = 100M

pre_page_sga = TRUE
java_pool_size = 1M
# large_pool_size = 15000K

sort_area_size = 4000000
sort_area_retained_size = 0

processes = 200

dml_locks = 750

db_file_multiblock_read_count = 16

db_block_buffers = 20000

cursor_space_for_time = TRUE

# settings for log file and for creating dumps

log_checkpoint_interval = 10000
log_buffer = 131072

max_dump_file_size = 10240
background_dump_dest=D:\oracle\ora81\otrace\public
user_dump_dest=D:\oracle\ora81\otrace\public

# settings for tkprof/performance tests (temporary only, please!):

timed_statistics = FALSE # for tkprof
# db_block_lru_statistics = TRUE
# db_block_lru_extended_statistics = 4000 # test for db_block_buffers

# automatic archiving

# log_archive_start = TRUE


Thanks a lot in advance.

Reply With Quote
  #2  
Old   
Anthony Hogan
 
Posts: n/a

Default Re: ora-01034 and ora-27101 after reboot - 06-24-2003 , 07:02 AM






I have the same problem on some of my W2K servers: The instance does not
open automatically on reboot. You can connect sys as sysdba and manually
startup the instance after reboot or create a script which opens the
instance. This script can then be associated with a scheduled task which
runs at system startup.
Beware of the script option if you have multiple instances on the server
as it may not always open all the instances.

HTH
Anthony Hogan

Reply With Quote
  #3  
Old   
Paul Drake
 
Posts: n/a

Default Re: ora-01034 and ora-27101 after reboot - 06-24-2003 , 07:52 AM



linda_68 (AT) hotmail (DOT) com (sien) wrote in message news:<31d3e92a.0306232349.59647171 (AT) posting (DOT) google.com>...
Quote:
Hello!

I have looked for the solution for this problem in this newsgroup and
tried every possibility but it doesn't work yet.
I install oracle enterprise edition 8.17 on windows 2000 server. The
machine is pentium 4, 2GHz, 512 MB ram.
I just have one database running on this server. Everytime I reboot
the server and I try to connect to the database I get this error:
ORA-01034: ORACLE not available
ORA-27101: shared memory realm does not exist
If I look at control panel/services, the database oracle service and
the listener service are started.
What I can do to be able to connect to the database is to start
Database configuration assistant, select 'Change database
configuration' option and click on next, next, finish.

This is the init.ora

--- snip ---

Thanks a lot in advance.
I'd guess that you have not installed the 8i Admin Assistant for
NT/W2K.
If you have, use it to "start the instance when the service is
started".
If you have not, edit the registry key:

HKLM\SOFTWARE\ORACLE\HOME0\ORA_%ORACLE_SID%_AUTOST ART = TRUE.

Also - might you be running the base release 8.1.7.0.0?
There is a known issue in that release that was fixed in 8.1.7.0.2.
If you have a metalink account, you can download the patchset.
I'd recommend using at least the 8.1.7.4.1 patchset, and apply the
8.1.7.4.10 patchset if you can afford time for testing on another
server. Multiple security fixes are included in that patchset, but if
you use cursor_sharing = FORCE, do not apply 8.1.7.4.10.

Btw - you're running in archivelog mode but do not have archiving set
to autostart?

Pd


Reply With Quote
  #4  
Old   
Sybrand Bakker
 
Posts: n/a

Default Re: ora-01034 and ora-27101 after reboot - 06-24-2003 , 12:02 PM



On Tue, 24 Jun 2003 13:02:48 +0100, Anthony Hogan
<ahogan-nospam- (AT) iespana (DOT) es> wrote:

Quote:
I have the same problem on some of my W2K servers: The instance does not
open automatically on reboot. You can connect sys as sysdba and manually
startup the instance after reboot or create a script which opens the
instance. This script can then be associated with a scheduled task which
runs at system startup.
Beware of the script option if you have multiple instances on the server
as it may not always open all the instances.

HTH
Anthony Hogan
Is this a solution or just a workaround?
You need to identify *why* your database doesn't start by verifying
oradim.log and the alert log, instead of implementing and -even worse-
recommending this crap workaround, which doesn't *solve* anything!


Sybrand Bakker, Senior Oracle DBA

To reply remove -verwijderdit from my e-mail address


Reply With Quote
  #5  
Old   
Anthony Hogan
 
Posts: n/a

Default Re: ora-01034 and ora-27101 after reboot - 06-25-2003 , 03:07 AM



Sybrand Bakker wrote:
Quote:
On Tue, 24 Jun 2003 13:02:48 +0100, Anthony Hogan
ahogan-nospam- (AT) iespana (DOT) es> wrote:

I have the same problem on some of my W2K servers: The instance does not
open automatically on reboot. You can connect sys as sysdba and manually
startup the instance after reboot or create a script which opens the
instance. This script can then be associated with a scheduled task which
runs at system startup.
Beware of the script option if you have multiple instances on the server
as it may not always open all the instances.

HTH
Anthony Hogan

Is this a solution or just a workaround?
You need to identify *why* your database doesn't start by verifying
oradim.log and the alert log, instead of implementing and -even worse-
recommending this crap workaround, which doesn't *solve* anything!

Sybrand Bakker, Senior Oracle DBA

Sybrand,
Point taken. I know why the database doesn't start: it's a bug in
8.1.7.0.0 which (sometimes) manifests itself on W2K servers. The
permanent solution is to apply the patches.
Failing this, the workaround does solve the problem of unscheduled
server reboots not bringing up the instance.

Anthony Hogan


Reply With Quote
  #6  
Old   
Paul Drake
 
Posts: n/a

Default Re: ora-01034 and ora-27101 after reboot - 06-25-2003 , 12:01 PM



timbedford (AT) hotmail (DOT) com (Tim Bedford) wrote in message news:<a411bafb.0306250615.2362f17b (AT) posting (DOT) google.com>...
Quote:
drak0nian (AT) yahoo (DOT) com (Paul Drake) wrote in message news:<1ac7c7b3.0306240452.55ba8d6e (AT) posting (DOT) google.com>...
linda_68 (AT) hotmail (DOT) com (sien) wrote in message news:<31d3e92a.0306232349.59647171 (AT) posting (DOT) google.com>...
Hello!

I have looked for the solution for this problem in this newsgroup and
tried every possibility but it doesn't work yet.
I install oracle enterprise edition 8.17 on windows 2000 server. The
machine is pentium 4, 2GHz, 512 MB ram.
I just have one database running on this server. Everytime I reboot
the server and I try to connect to the database I get this error:
ORA-01034: ORACLE not available
ORA-27101: shared memory realm does not exist
If I look at control panel/services, the database oracle service and
the listener service are started.
What I can do to be able to connect to the database is to start
Database configuration assistant, select 'Change database
configuration' option and click on next, next, finish.

This is the init.ora

--- snip ---

Thanks a lot in advance.

I'd guess that you have not installed the 8i Admin Assistant for
NT/W2K.
If you have, use it to "start the instance when the service is
started".
If you have not, edit the registry key:

HKLM\SOFTWARE\ORACLE\HOME0\ORA_%ORACLE_SID%_AUTOST ART = TRUE.

Also - might you be running the base release 8.1.7.0.0?
There is a known issue in that release that was fixed in 8.1.7.0.2.
If you have a metalink account, you can download the patchset.
I'd recommend using at least the 8.1.7.4.1 patchset, and apply the
8.1.7.4.10 patchset if you can afford time for testing on another
server. Multiple security fixes are included in that patchset, but if
you use cursor_sharing = FORCE, do not apply 8.1.7.4.10.

Btw - you're running in archivelog mode but do not have archiving set
to autostart?

Pd


I've had the same problem and its been doing my head in. What's the
actual patch number that fixes this? Is seeing ORA-27101 related to
Windows not giving an Oracle service enough time to shut down? I've
been trying all kinds of automated shutdown setups and I always still
get "crash recovery" in the alert log.

Tim
Tim,

The patchset 8.1.7.0.2 included a fix for this.
As far as your unclean shutdowns, did you reset the following:

HKLM\SOFTWARE\ORACLE\HOMEn\ORA_%ORACLE_SID%_SHUTDO WN_TIMEOUT = 300
HKLM\SYSTEM\CurrentControlSet\Control\WaitToKillSe rviceTimeout = 300000

Also, just to double-check, make sure that the following entry is set:

HKLM\SOFTWARE\ORACLE\HOMEn\ORA_%ORACLE_SID%_AUTOST ART = TRUE

I have not had a problem with this since 8.1.7.0.2.

hth,

Paul


Reply With Quote
  #7  
Old   
sien
 
Posts: n/a

Default Re: ora-01034 and ora-27101 after reboot - 06-26-2003 , 01:51 AM



Thanks for all the answers. I will then upgrade to 8.1.7.4

Have a nice day!!



Sybrand Bakker <gooiditweg (AT) sybrandb (DOT) demon.nl> wrote

Quote:
On 25 Jun 2003 07:15:36 -0700, timbedford (AT) hotmail (DOT) com (Tim Bedford)
wrote:

I've had the same problem and its been doing my head in. What's the
actual patch number that fixes this? Is seeing ORA-27101 related to
Windows not giving an Oracle service enough time to shut down? I've
been trying all kinds of automated shutdown setups and I always still
get "crash recovery" in the alert log.

Tim

Just upgrade to 8.1.7.4.

Can be found easily from the patch screen in Metalink, provided you
are capable of selecting 8.1.7 from a combo box.


Sybrand Bakker, Senior Oracle DBA

To reply remove -verwijderdit from my e-mail address

Reply With Quote
Reply




Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

vB code is On
Smilies are On
[IMG] code is On
HTML code is Off



Powered by vBulletin Version 3.5.3
Copyright ©2000 - 2012, Jelsoft Enterprises Ltd.