![]() | |
![]() |
| | Thread Tools | Display Modes |
#1
| |||
| |||
|
#2
| |||
| |||
|
#3
| |||
| |||
|
|
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. |
#4
| |||
| |||
|
|
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 |
#5
| |||
| |||
|
|
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, |
#6
| |||
| |||
|
|
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 |
#7
| |||
| |||
|
|
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 |
![]() |
| Thread Tools | |
| Display Modes | |
| |