• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 818
  • Last Modified:

Oracle Database Instance Crashed, Restarted but still without connection using SQLPLUS

Hi,

I was running a script as per instructions, and it stoped the database.

I then logged into Solaris/Unix and ran the command ./dbstart and it stated that my instance went to "instance name" warm started.

Now when I try to login using Sqlplus name/pwd@instanc name, I recieve ORA-01034: Oracle Not Available.


Do I need to run something else to get the database back to normal?

Thanks!
0
byd2k
Asked:
byd2k
  • 8
  • 3
  • 2
  • +1
3 Solutions
 
actonwangCommented:
>>my instance went to "instance name" warm started
    was it stuck there?
   
    look at cdump and bdump to see if you find any error message in log files.
0
 
actonwangCommented:
there is alert log inside bdump directory and you should be able to find some information there.
0
 
ivanovnCommented:
Check this link and see if the suggested solution works.
http://lists.suse.com/archive/suse-oracle/2001-May/0215.html
0
Get your Conversational Ransomware Defense e‑book

This e-book gives you an insight into the ransomware threat and reviews the fundamentals of top-notch ransomware preparedness and recovery. To help you protect yourself and your organization. The initial infection may be inevitable, so the best protection is to be fully prepared.

 
byd2kAuthor Commented:
Hi Actionwang,

Thanks for the fast response.  For alert_"oracle_instance".log file:


Errors in file /dsk0/oracle/app/oracle/product/9.2.0/../../admin/dbase/bdump/dbase_dbw0_25342.trc:
ORA-00600: internal error code, arguments: [kslawe:!pwq], [0x381CE8708], [], [], [], [], [], []
Thread 1 advanced to log sequence 27171
  Current log# 3 seq# 27171 mem# 0: /dsk1/oradata2/dbase/redodbase03.log
Thread 1 cannot allocate new log, sequence 27172
Checkpoint not complete
  Current log# 3 seq# 27171 mem# 0: /dsk1/oradata2/dbase/redodbase03.log
Fri Apr 28 09:02:58 2006
Errors in file /dsk0/oracle/app/oracle/product/9.2.0/../../admin/dbase/bdump/dbase_dbw0_25342.trc:
ORA-00600: internal error code, arguments: [kslawe:!pwq], [0x381CE8708], [], [], [], [], [], []
Fri Apr 28 09:02:58 2006
DBW0: terminating instance due to error 600
Instance terminated by DBW0, pid = 25342


I'll go ahead and find the other log files, and post them in just a minute.
0
 
byd2kAuthor Commented:
There is nothing in the cdump folder.  We have had this problem before, however I am unable to get ahold of the techs for a few more hours.  They seem to do a few things behind the scenes and have this problem resolved in a very short period of time.  

Any ideas on re-starting this dbase back to normal?

Thanks!
0
 
actonwangCommented:
seems like a bug in 9.0.5 and fixed at 9.0.6
0
 
actonwangCommented:
0
 
actonwangCommented:
>>Thread 1 cannot allocate new log
 
     this is a known message. Look at this:

http://asktom.oracle.com/pls/ask/f?p=4950:8:::::F4950_P8_DISPLAYID:69012348056
0
 
actonwangCommented:
you'd add more log files or shorten your checkpoint time.
0
 
actonwangCommented:
>>They seem to do a few things behind the scenes and have this problem resolved in a very short period of time.  
     ask them what they do. Maybe they just add some log files ...
0
 
johnsoneSenior Oracle DBACommented:
Was the server restarted?  If so, my guess would be the listener is down.

Assuming a standard configuration...

"lsnrctl status"  would show you if the listener is up and the databases it is listening for.

If it is down, "lsnrctl start" will bring it back up.
0
 
johnsoneSenior Oracle DBACommented:
If moving to 9.2.0.6 is not an option...

If you have MetaLink access, look at note 271084.1.  There is a patch available for 9.2.0.5 that should fix the problem.
0
 
actonwangCommented:
as I said, you need to ask your DBAs, it is obviously in their responsibilites to fix this error for you because it seems that they know what goes wrong with it.
0
 
byd2kAuthor Commented:
Thank you all for your assistance.  The techs restrated the database after it crasehed and all is well.  It was due to a trigger either prior to or after running a scripts.

-Byd2k
0

Featured Post

What does it mean to be "Always On"?

Is your cloud always on? With an Always On cloud you won't have to worry about downtime for maintenance or software application code updates, ensuring that your bottom line isn't affected.

  • 8
  • 3
  • 2
  • +1
Tackle projects and never again get stuck behind a technical roadblock.
Join Now