Database instance is down after machine reboots

Hi,
I have oracle 10gR2 on my machine.
It is a windows XP machine.
After every time the machine is restarted the database service and listener are down.
They need to be started manually each time.
How to avoid this ?
Thanks.

After every time the machine is restarted the database service and listener are down.Go to running services Run-->services.msc-----in services make the two services to start automatically by right clicking the services of database and listener--click on properties and then set automatic. That is all for listener but for database you will have to edit the SID by ORADIM utility to start it autmatically. Type
C:/>ORADIM help=y --You will get to option to edit the sid and start it automatically.
Regards.

Similar Messages

10G agent and Database Instance is down

Im install oracle 10G on oracle enterprice linux 4. machine is P4 512 MB ram 3.GZ desktop one. oracle is working fine. but little slow. it is ok.
But few minuts after opening the database, enterprice manager cosole display that agent and Database Instance is down.
Display the following message
""Details The instance has been terminated by a database process because of a fatal internal condition, or a critical background process was killed by the user.""
But oracle is working. select and other this working fine.
Please help me to overcome the problem.
Regrds
upul Indika

Define a fixed IP address for your server. If problem persists then you can use emca-Enterprise Manager Configuration assistance to delete and reconfigure the console.
emca -deconfig dbcontrol db
emca -config dbcontrol db

Database Instance is down?

Hello,
This is my Database Instance:
Status: Down
Host: localhost
Port: 1523
SID: ORCL
Oracle Home: C:\app\L31004\product\11.2.0\dbhome_3
Details: There has been a user-initiatied shutdown.
What does it mean?

Refer this thread
Re: ORA-01031: insufficient privileges
ORA-01031 insuffiecient privilidges

Database Down after Server Reboot

Hello
I am getting a weird problem after I reboot my server (windows 2003) where by my database (10.2) does not automatically start. To get it to start I have to go into administrative tools >> services and then manually restart the OracleASMService+ASM (it says it is already running).
Thanks in advance for any Idea's/suggestions

Right;
After rebooting the server and lauching the OEM Database Control it tells me the following:
- Database Instance = Down
- Listener = Up
- Agent Connection to Instance = Failed ORA-12505: TNS:Listener does not currently know of SID given in connect descriptor(DBD ERROR: OCIServerAttach)
In response to your troubleshooting suggestions;
1. alert.log has no new errors logged in the past week
2. As far as I can tell, yes. It says the service (and other associated oracle services) are running
3. No I can not connect to the database with sql*plus (before I restart the OracleASMService+ASM). SQL*Plus errors:
ORA-01034: ORACLE not available
ORA-27101: shared memory realm does not exist
After I restart the service I can connect without any problems.
4. N/A
I appreciate any help you can offer on this matter.
Regards
Toby

10g database fails to start after 3rd reboot

Hi,
I've reloaded my test server several times and loaded 10g with the default "orcl" database. Works just fine, reboot a couple times and it still works. Around the 3rd reboot the database instance fails to start. I even have to reload the OS to clear this problem. Just uninstalling Oracle and reinstalling will not clear this problem I have to reload the OS. Is there some sort of limit on the software we download from the OTN download area?
Thanks.

I found in another post that suggested I needed to update my listener.ora file. I did that and the error went to telling me that oracle was unavailable. Then I found a post that suggested this:
Set oracle_sid=orcl
SQLPLUS /NOLOG
CONN SYS/????@orcl AS SYSDBA
STARTUP
EXIT
Ran this and sure enough, the database was ok but sitting idle. It went through some initialization steps and mounted so I can now launch the manager tool and have access to my database.
So, ok, this is running on VMware and that "might" be causing the problems but this is very strange since it survived three reboots then out of the blue this issue comes up. I can live with running a batch file everytime I reboot in my little test environment so I'm ok :]
Thanks for your time.

Suddenly Weblogic instance shut down after issuing HANGUP

Suddenly Weblogic instance shut down and when I check the logs, there is no exception or error.
There is only one word "HANGUP" which is new and after that there is no logs

This looks like a crash, check if there is any file generated with extension .pid?
If yes, please paste the contents here.

EM Event: Warning: Database Instance - Agent Down

Hello,
while upgrading plugins for the OMS 12 Bundle Patch and applying the BP on the agents, I get a lot of mails with the above subject - namely, one mail by every database instance and every listener running on the host.
Content of the mail is as follows:
Host=<hostname>
Target type=Database Instance
Target name=<database name>
Categories=Availability
Message=Agent Down
Severity=Warning
Availability status=Agent Down
Rule Name=Database Availability and Critical States,Target Availability Event Rule
Rule Owner=SYSMAN
Blackout on the host leads to the OMS not being able to do the upgrades - obviously a blacked-out agent is not able to do that. What puzzles me that in the Rule mentioned in the mail, incidents should only be created for the target type being down (i.e. for database instance when database is down, and so on) as one would expect.
I would rather not blackout all targets on a host EXCEPT the agent as this gets old with our number of hosts and dbs, does anyone know which rule is responsible for the mails and how they could be suppressed temporarily in an efficient way?

I think Jay was referring to selecting availability events by severity. So in the rule create/edit "Select Events" step you can do the following:
1. select (event) Type= Target Availability
2. Leave the radio button in the sub-section at "All events of type Target Availability"
3. select the check box next to "Severity" right below the Type field
4. When a subsequent drop down shows up for severity - select "Fatal"
5. Optionally, check the box next to "Target type" and choose "Database Instance" if your target set includes other targets - this step should not be needed.
6. Everything else should remain the same.
Essentially, the "target down" events come with "Fatal" severity and these "agent down" events come with a "Critical" severity. So this is a way to avoid getting the agent down notifications on databases (or any other targets) while getting the genuine target down notifications. Hope this helps.

Database Instance down Agent Connection to Instance down

Hi
I have installed Oracle 10g on Windows XP SP2 and i m new to Oracle 10g.
In Oracle Enterprise manager I have
1. database instance Down
2. Listener is UP
3. Agent Connection to Instance is Down and giving an error
ORA-12505: TNS:listener does not currently know of SID given in connect scriptor (DBD ERROR: OCIServerAttach)
I m unable to connect through sql*plus command window it gives protocol adapter error
But I am able to connect through windows command prompt
but each time when i connect through it i have to set sid by command
set ORACLE_SID=orcl10g
I m also not able to use isqlplus
what should i do
pleease help me

I tried ur suggestion and the command i typed are here
C:\Documents and Settings\tony>sqlplus /nolog
SQL*Plus: Release 10.2.0.1.0 - Production on Wed Apr 2 15:05:01 2008
Copyright (c) 1982, 2005, Oracle. All rights reserved.
SQL> conn / as sysdba
Connected.
SQL>
but problem is same database instance is down Agent Connection to Instance is down and listener is up.

Database automatically goes down

Hi all,
Our SAP version is 4.7E and OS is HP-UX and database oracle 9.2.0.7.
the problem is suddenly the database and the central instance is goes down.
when I check at os level the central and Database instance goes down.
how can I find where the problem is located?is it belongs to database or OS?
Regards,
Nani Prakash.

Hi Nani
Check the Oracle alert logs and trace files from SAP side
Thanks
Prince Jose

Hand Held application not recognising a database instance when running in cradled mode through Windows Mobile Device Centre.

How do I get a Hand Held application to recognise a database instance when running cradled through Mobile Device Centre?
I have a database instance on a networked machine as NZTESTSERVER2\NZ2008.
If I run the Hand Held application in WI-Fi connected mode it resolved this database connection name without any problems.
This database connection name also works from a Desktop application running on the PC that I have cradled the Hand Held to.
But the instance isn’t being resolved when I run the Hand Held application in cradled mode, without a Wi-Fi connection. In this case it still recognises the server address part ‘NZTESTSERVER2’ but it doesn’t recognise this with the database instance included
(\NZ2008).
I even tried using it with the servers IP and the instance (192.168.0.14\NZ2008), but again it recognises the server IP address (192.168.0.14), but not with the instance (\NZ2008).
So why does the app run in WI-Fi but not cradled mode?

It would better to understand your problem if you can share some code here,

How send mail when oracle instance went down

Hi All,
Please help me to configure email set in oracle standard edition so that it sends email whenever database /instance went down.
Thanks in advance
sankar

user12994238 wrote:
Many Thanks,
Need a small clarification in the normal scenario it works, if shutdown the server without shutdown the database we not receiving the alert.
is there any way i can configure alert mail for the instance shutdown (database is up and oracle instance is down) due to some unexpected reason.
Thanks
sankar"database is up and oracle instance is down"
A very interesting concept. Given that a database is just the collection of files that are kept transactionally consistent, and the instance is the memory and processes that manage those files, could you explain what is meant by "database is up and oracle instance is down". If the instance is up it may (or may not, depending on its state) have the database (files) open. If the instance is not up, then the database is ???

Restoring a RMAN backup to a new database instance

Hi Mates,
I have an issue with restoring a RMAN backup that i have with me to a new database instance. What i have with me are:
1. Backup of SPFile. (O1_MF_NCNNF_CTLFILE_BU_92DVGYO2_.BKP)
2. Backup of Control file (O1_MF_NNSNF_SPFILE_BU_92DVGW9H_.BKP)
3. Full database backup (O1_MF_NNSNF_FULLPROD_BU_92DVGW9H_.BKP)
I have received these files from a customer environment and I need to restore these to a new database instance in a local machine. I have given a attempt as follows (in Oracle 10g):
1, Created a new database instance (Test75) using Oracle Database Configuration Assistant
2. SET ORACLE_SID = Test75
3. Connected to this instance using RMAN
4. Tried to restore the SPFILE from the received BKP file.
I am getting errors and cannot proceed. I am not sure whether I am executing the correct steps. Please help me out by telling me how should I achieve this.
Thank you.

1. Backup of SPFile. (O1_MF_NCNNF_CTLFILE_BU_92DVGYO2_.BKP)
2. Backup of Control file (O1_MF_NNSNF_SPFILE_BU_92DVGW9H_.BKP)
The first backuppiece looks like a ControlFile and the second one looks like an SPFILE'
>I am getting errors and cannot proceed
What is the error ? (I assume that you tried to restore the SPFILE from O1_MF_NNSNF_SPFILE_BU_92DVGW9H_.BKP
Note that you also have to SET DBID before you restore the controlfile
Hemant K Chitale

Oracle 10G Db Starts-up After Server Reboot, BUT Goes DOWN After Some Time

Hi All,
I am really puzzled over this one. I have couple of servers running DB on them and I have used scripts to auto-enable them when server(s) reboot.
But there is one server where I see this funny behavior.
The DB comes-up after server reboot.
I can verify that in the startup logs and some more logs that I created.
I can see that LISTENER is able to communicate also.
But after a while, the DB shuts-down....!!
I have checked all the places I could. I have also tried to see the difference between this server and others (I did not install this one), but can not see any difference.
Is there anyway to find out (log) what is shutting down the DB??
Any help will be much appreciated as I am at my wits end.
Following is snap-shot from my logs:
Fri Mar 16 20:42:29 EDT 2007
Running dbstart.
Done with starting all, let's check status...
Fri Mar 16 20:42:42 EDT 2007
LSNRCTL for Solaris: Version 10.2.0.1.0 - Production on 16-MAR-2007 20:42:42
Copyright (c) 1991, 2005, Oracle. All rights reserved.
Connecting to (DESCRIPTION=(ADDRESS=(PROTOCOL=IPC)(KEY=EXTPROC1)))
STATUS of the LISTENER
Alias LISTENER
Version TNSLSNR for Solaris: Version 10.2.0.1.0 - Production
Start Date 16-MAR-2007 00:46:56
Uptime 0 days 19 hr. 55 min. 46 sec
Trace Level off
Security ON: Local OS Authentication
SNMP OFF
Listener Parameter File /oracle/product/10.2.0/Db_1/network/admin/listener.ora
Listener Log File /oracle/product/10.2.0/Db_1/network/log/listener.log
Listening Endpoints Summary...
(DESCRIPTION=(ADDRESS=(PROTOCOL=ipc)(KEY=EXTPROC1)))
(DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=10.103.253.50)(PORT=1521)))
Services Summary...
Service "orcl" has 2 instance(s).
Instance "orcl", status UNKNOWN, has 1 handler(s) for this service...
Instance "orcl", status READY, has 1 handler(s) for this service...
Service "orclXDB" has 1 instance(s).
Instance "orcl", status READY, has 1 handler(s) for this service...
Service "orcl_XPT" has 1 instance(s).
Instance "orcl", status READY, has 1 handler(s) for this service...
The command completed successfully
Current Status:
# date
Fri Mar 16 21:30:40 EDT 2007
# su - oracle -c "lsnrctl status"
Sun Microsystems Inc. SunOS 5.10 Generic January 2005
LSNRCTL for Solaris: Version 10.2.0.1.0 - Production on 16-MAR-2007 21:30:53
Copyright (c) 1991, 2005, Oracle. All rights reserved.
Connecting to (DESCRIPTION=(ADDRESS=(PROTOCOL=IPC)(KEY=EXTPROC1)))
TNS-12541: TNS:no listener
TNS-12560: TNS:protocol adapter error
TNS-00511: No listener
Solaris Error: 146: Connection refused
Connecting to (DESCRIPTION=(ADDRESS=(PROTOCOL=TCP)(HOST=10.103.253.50)(PORT=1521)))
TNS-12541: TNS:no listener
TNS-12560: TNS:protocol adapter error
TNS-00511: No listener
Solaris Error: 146: Connection refused

I was just looking at that.. Thanks for the tip.
Following is what I see. But not sure what does it tell me?? Please help......
From alert_orcl.log:
<snip>
db_recovery_file_dest_size of 2048 MB is 0.00% 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.
Fri Mar 16 20:42:41 2007
Errors in file /oracle/product/10.2.0/Db_1/admin/orcl/udump/orcl_ora_7700.trc:
ORA-00604: error occurred at recursive SQL level 1
ORA-12663: Services required by client not available on the server
ORA-36961: Oracle OLAP is not available.
ORA-06512: at "SYS.OLAPIHISTORYRETENTION", line 1
ORA-06512: at line 15
Fri Mar 16 20:42:42 2007
Completed: ALTER DATABASE OPEN
From /oracle/product/10.2.0/Db_1/admin/orcl/udump/orcl_ora_7700.trc
# cat /oracle/product/10.2.0/Db_1/admin/orcl/udump/orcl_ora_7700.trc
/oracle/product/10.2.0/Db_1/admin/orcl/udump/orcl_ora_7700.trc
Oracle Database 10g Release 10.2.0.1.0 - 64bit Production
ORACLE_HOME = /oracle/product/10.2.0/Db_1
System name: SunOS
Node name: gcars0j6
Release: 5.10
Version: Generic_118833-24
Machine: sun4u
Instance name: orcl
Redo thread mounted by this instance: 1
Oracle process number: 15
Unix process pid: 7700, image: oracle@gcars0j6 (TNS V1-V3)
*** SERVICE NAME:() 2007-03-16 20:42:37.548
*** SESSION ID:(159.3) 2007-03-16 20:42:37.548
Thread 1 checkpoint: logseq 255, block 2, scn 8602014
cache-low rba: logseq 255, block 3
on-disk rba: logseq 255, block 767, scn 8602399
start recovery at logseq 255, block 3, scn 0
----- Redo read statistics for thread 1 -----
Read rate (ASYNC): 382Kb in 0.16s => 2.33 Mb/sec
Total physical reads: 4096Kb
Longest record: 3Kb, moves: 0/1066 (0%)
Change moves: 1/8 (12%), moved: 0Mb
Longest LWN: 308Kb, moves: 0/29 (0%), moved: 0Mb
Last redo scn: 0x0000.0083431e (8602398)
----- Recovery Hash Table Statistics ---------
Hash table buckets = 32768
Longest hash chain = 1
Average hash chain = 149/149 = 1.0
Max compares per lookup = 1
Avg compares per lookup = 1925/2083 = 0.9
*** 2007-03-16 20:42:37.702
KCRA: start recovery claims for 149 data blocks
*** 2007-03-16 20:42:37.705
KCRA: blocks processed = 149/149, claimed = 149, eliminated = 0
*** 2007-03-16 20:42:37.706
Recovery of Online Redo Log: Thread 1 Group 2 Seq 255 Reading mem 0
----- Recovery Hash Table Statistics ---------
Hash table buckets = 32768
Longest hash chain = 1
Average hash chain = 149/149 = 1.0
Max compares per lookup = 1
Avg compares per lookup = 2054/2074 = 1.0
Error in executing triggers on database startup
*** 2007-03-16 20:42:41.963
ksedmp: internal or fatal error
ORA-00604: error occurred at recursive SQL level 1
ORA-12663: Services required by client not available on the server
ORA-36961: Oracle OLAP is not available.
ORA-06512: at "SYS.OLAPIHISTORYRETENTION", line 1
ORA-06512: at line 15

Database not automatically starting after reboot of RedHat ES4 Linux

Hi,
I have Oracle database enterprise edition 9.2.0.4 running on RedHat Linux ES release 4. Although the installation went fine and after the installation I was able to see the common processes like ora_pmon started in system, but when I reboot system the database does not comeup.
I am using dbstart command via a /etc/init.d/oracle file. This is linked to /etc/rc5.d and /etc/rc3.d as well in the Linux server.
The amazing thing is that tnslistener is started automatically after system reboot but not database. That is, when I check the status of that via the command "lsnrctl status" it shows me the one database instance that I am hoping to see correctly. But no ora_pmon etc processes are there.
Even interesting thing is that when I manually run the command "/etc/init.d/oracle start" by hand, it does start the database perfectly fine. This is the same command that I am running via the startup scripts in /etc/rc5.d and othe runlevels.
Please help me finding out why is the database not starting up automatically? I have checked the /u02/app/oracle/product/9.2.0/startup.log which just says reports that Listener has started but after that it does not show anything about database starting up.
Below I am pasting the chunk of /etc/init.d/oracle script that is supposed to start the listener and database. Please have a look at it and tell me what can I be doing wrong in this case?
ORACLE=oracle1
export ORACLE_HOME PATH
LOG=$ORACLE_HOME/startup.log
touch $LOG
chmod a+r $LOG
case $1 in
'start')
echo "$0: starting up" >> $LOG
date >> $LOG
# Start Oracle Net
if [ -f $ORACLE_HOME/bin/tnslsnr ] ; then
echo "starting Oracle Net listener"
su - oracle1 -c "$ORACLE_HOME/bin/lsnrctl start" >> $LOG 2>&1 &
fi
echo "starting Oracle databases"
su - oracle1 -c "$ORACLE_HOME/bin/dbstart" >> $LOG 2>&1
Thanks in advance for your urgent help.
--Smb

Thanks for your reply, actually I have already set the value of $ORACLE_HOME to the correct value as per my installation, sorry that line was cut when I last time pasted the chunk of my /etc/init.d/oracle file because I only wanted to paste the relevant portion of that file.
But here is the complete /etc/init.d/oracle file that I have below, please suggest what might be wrong?
thanks.
#!/bin/sh
# chkconfig: 235 99 01
# description: controls Oracle database startup and shutdown
ORACLE_HOME=/u02/app/oracle/product/9.2.0
PATH=${PATH}:$ORACLE_HOME/bin
HOST=`hostname`
ORACLE=oracle1
export ORACLE_HOME PATH
LOG=$ORACLE_HOME/startup.log
touch $LOG
chmod a+r $LOG
case $1 in
'start')
echo "$0: starting up" >> $LOG
date >> $LOG
# Start Oracle Net
if [ -f $ORACLE_HOME/bin/tnslsnr ] ; then
echo "Shahid starting Oracle Net listener"
su - oracle1 -c "$ORACLE_HOME/bin/lsnrctl start" >> $LOG 2>&1 &
fi
echo "Shahid starting Oracle databases"
su - oracle1 -c "$ORACLE_HOME/bin/dbstart" >> $LOG 2>&1
'stop')
echo "$0: shutting down" >> $LOG
date >> $LOG
# Stop Oracle Net
if [ -f $ORACLE_HOME/bin/tnslsnr ] ; then
echo "stopping Oracle Net listener"
su - oracle1 -c "$ORACLE_HOME/bin/lsnrctl stop" >> $LOG 2>&1
fi
echo "stopping Oracle databases"
su - oracle1 -c "$ORACLE_HOME/bin/dbshut" >> $LOG 2>&1
echo "usage: $0 {start|stop}"
exit
esac
exit
########################################################

Oracle Database unavailable after machine restart

I have a dedicated machine where I have installed Oracle Database 11.2.0.1.0 under Oracle Linux 6. It worked fine until today, when I had to shutdown the machine for physical relocation. Much to my surprise, when I have restarted the machine, EM wasn't available. Then I realized I could no longer remotely connect to the Database. Then I found out that the listener was down. Then I tried starting the listener, it said that no clients are supported. Then I tried to manually start the DB from sqlplus, I could not even log in to it. Then I ran dbca, which cried about EM not being secure. Then I found out that the emkey.ora was missing (and as a newbie, I hadn't made a backup).
I spent 3 hours trying to figure out how to bring the DB online; I'm afraid I ran out of solutions. Right now I am rebuilding the whole EM Repository using dbca and hope for the best.
Update: dbca finished with no errors. I can now connect with sqlplus and see that all data is there. However, EM still doesn't properly connect. I am getting "Enterprise Manager is not able to connect to the database instance". However, state of components lists:
- Database Instance: Open
- Listener status: UP
- Agent connection to Instance: Succeeded
I can't figure out why EM won't connect. I have this feeling it's a listener misconfiguration, however netca is very limited, just a next-next-next thing.
My listener.ora is below:
SID_LIST_LISTENER =
(SID_LIST =
(SID_DESC =
(GLOBAL_DBNAME = eburlacu)
(ORACLE_HOME = /oracledb/product/11.2.0/dbhome_1)
(SID_NAME = eburlacu)
LISTENER =
(DESCRIPTION_LIST =
(DESCRIPTION =
(ADDRESS = (PROTOCOL = TCP)(HOST = eburlacu-server.ro.oracle.com)(PORT = 1521))
ADR_BASE_LISTENER = /oracledb
SUBSCRIBE_FOR_NODE_DOWN_EVENT_LISTENER = OFF
...And why is EM using port 5500?
LE: I can now remotely connect to the Database from a different machine, using Oracle SQL Developer, so the listener seems to be working well, after all. I'm confused now...
Edited by: EduardB on Sep 28, 2012 3:24 PM

Thank you for the response. It makes some sense, however I wouldn't have expected the Oracle DB to be so se sensitive to a simple machine move.
The network configuration hasn't changed a bit. I am in the same network, I have the same IP (it's a static IP and a static DNS hostname which was granted to this machine specifically). I just changed floors.
I never touched the EM environment. All I did was:
1. Installed Oracle Database.
2. Added a schema (basically created a new user).
3. Allowed SQL Developer through the firewall.
4. Remotely connected with SQL Developer and created tables and functions, all basic SQL work, nothing fancy.
The restarts were simply for testing purposes (does it still start as expected? Are there warnings, error messages?). Two restarts were performed to re-arange some wiring, again nothing fancy.
I am just a newbie doing some learning and gaining some hands-on experience (after taking Linux and SQL classes). The Oracle Database 11g Administration Workshops are scheduled for 2013 but in the meanwhile I am trying to understand why could my installation mess up so badly with no outside interaction.
What would your advice be in this situation? Reinstall everything under OEL5 + 11.2.0.1.0? Reinstall OEL6 with clean 11.2.0.3.0 installation?
Note: my first priority at this moment is hands-on experience with SQL. Since both sql*plus and Oracle SQL Developer can connect and work fine, should I simply stop bothering with EM for the moment and let it limp until I attend the Administration Workshops? I have almost half a million records in the DB but my SQL statements (saved on a different machine) can re-generate all the data in about 1h or so, so it's not a big deal if I wipe everything.

Database instance is down after machine reboots

Similar Messages

Maybe you are looking for