You maybe jumping the gun here. You say the system boots normally but you didn’t specify if the database was up and running. Or the listener for the database. First ensure you can connect to the listener by performing a tnsping “SID” from an oracle client with the correct tnsnames.ora setup. If that works then the listener is listening. If you can tnsping the SID then next try and connect to the database with a valid username and password. If you can connect then the database is more than likely fine as well. This leaves connectivity between the app and the db and I can’t comment on that.

like the other guys said check your alert.log file
any errors towards the end of that file?

the instance is not opening the database, you’ll need to connect with svrmgr user:internal your database probaly needs recovery

you might need to recover some datafile or the database

I hope you’re running in archivelog mode

Hello all,

thanks for your replies!
It’s unfortunately true, that the last backup is very old.

I checked my Alert.log:

*********************************************************
Starting ORACLE instance (normal)
LICENSE_MAX_SESSION = 0
LICENSE_SESSIONS_WARNING = 0
LICENSE_MAX_USERS = 0
Starting up ORACLE RDBMS Version: 7.3.2.3.0.
System parameters with non-default values:
processes = 50
shared_pool_size = 6000000
control_files = /home/opt/adaaaa/oracle/standard/cntrl1advantdb.ctl, /home/opt/adaaaa/oracle/standard/cntrl2adaaaadb.ctl
log_buffer = 163840
log_checkpoint_interval = 10000
db_files = 1021
rollback_segments = rs_1, rs_2, rs_3, rs_4, rs_5, rs_6, rs_7, rs_8, rs_9, rs_10, rs_11, rs_12
sequence_cache_hash_buckets= 10
remote_login_passwordfile= NONE
global_names = TRUE
mts_service = adaaaadb
mts_servers = 0
mts_max_servers = 0
mts_max_dispatchers = 0
audit_trail = NONE
sort_area_retained_size = 65536
sort_direct_writes = AUTO
db_name = adaaaadb
open_cursors = 150
background_dump_dest = /var/opt/adaaaa/log/oracle
user_dump_dest = /tmp
DBWR started
LGWR started
PMON started
RECO started
Wed Nov 30 15:30:31 2005
alter database mount exclusive
Wed Nov 30 15:30:31 2005
Successful mount of redo thread 1.
Wed Nov 30 15:30:31 2005
Completed: alter database mount exclusive
Wed Nov 30 15:30:31 2005
alter database open
Beginning crash recovery of 1 threads
Wed Nov 30 15:31:10 2005
Errors in file /tmp/ora_1269.trc:
ORA-00333: redo log read error block 3003 count 64
ORA-00312: online log 1 thread 1: ‘/home/opt/adaaaa/oracle/standard/log1adaaaadb.dbf’
ORA-07372: sfrfb: read error, unable to read requested block from database file.
HP-UX Error: 5: I/O error
Additional information: 3003
ORA-333 signalled during: alter database open…
**********************************************************

Usually I connect to the Database from my application. How can I connect to the database from a terminal window?
Greetings
Pine

Hi
you have a corrupted logfile!

first you should take a backup NOW!!
before you attempt anything

2nd Do you know if your logs were multiplexed?
if yes you can copy the other log in the group over the one that can’t be read and try to reopen the database

>Usually I connect to the Database from my application. >How can I connect to the database from a terminal window?

connect to Unix with the oracle owner
then I think you should run “svrmgr” or svrmgr23 something like that (check in $ORACLE_HOME/bin), man this database is old last time I used a 7.3.2 was over 6 years ago

once you got that running: connect /
or if this doesn’t work: connect internal default password was oracle

your database should be in a mounted state so you should be able to see your logfile with
select * from v$logfile;

like I said above if your logfiles are multiplexed you’re saved! Copy the good one over the corrupted one,
then : Alter database open;
Then close the database and another backup!

if not then it might be complicated but not undoable to reopen your database but you’ll lose some data that was in the logfile