Home » RDBMS Server » Server Administration » ora-01033 when connecting to db
ora-01033 when connecting to db [message #55833] Wed, 19 February 2003 03:24 Go to next message
jürgen müller
Messages: 1
Registered: February 2003
Junior Member
Hi all,

I've the following problem:

I've setup my database on a notebook which is connected to our network. The database works fine. When I boot my notebook without connecten to the network and I try to log in to the same db, I get ORA-01033. Connected to the network again, the log in and the db works fine...

When I create a db with my notbook not connected to the network, then this db works fine.

Any ideas?

System: Win 2000
DB: Oracle 8.1.7.0.0

ALERT.LOG:

Dump file E:Oracleadminphx2bdumpphx2ALRT.LOG
Wed Feb 19 11:05:55 2003
ORACLE V8.1.7.0.0 - Production vsnsta=0
vsnsql=e vsnxtr=3
Windows 2000 Version 5.0 , CPU type 586
Starting up ORACLE RDBMS Version: 8.1.7.0.0.
System parameters with non-default values:
processes = 150
shared_pool_size = 39961804
large_pool_size = 614400
java_pool_size = 20971520
control_files = E:Oracleoradataphx2control01.ctl, E:Oracleoradataphx2control02.ctl, E:Oracleoradataphx2control03.ctl
db_block_buffers = 14634
db_block_size = 8192
compatible = 8.1.0
log_archive_start = FALSE
log_buffer = 32768
log_checkpoint_interval = 10000
log_checkpoint_timeout = 1800
db_files = 1024
db_file_multiblock_read_count= 8
max_enabled_roles = 50
remote_login_passwordfile= EXCLUSIVE
db_domain = jumul1
global_names = TRUE
distributed_transactions = 500
instance_name = phx2
service_names = phx2.jumul1
mts_dispatchers = (PROTOCOL=TCP)(PRE=oracle.aurora.server.SGiopServer)
open_links = 4
sort_area_size = 65536
sort_area_retained_size = 65536
db_name = phx2
open_cursors = 300
os_authent_prefix =
job_queue_processes = 4
job_queue_interval = 10
parallel_max_servers = 5
background_dump_dest = E:Oracleadminphx2bdump
user_dump_dest = E:Oracleadminphx2udump
max_dump_file_size = 10240
oracle_trace_collection_name=
PMON started with pid=2
DBW0 started with pid=3
LGWR started with pid=4
CKPT started with pid=5
SMON started with pid=6
RECO started with pid=7
SNP0 started with pid=8
SNP1 started with pid=9
SNP2 started with pid=10
SNP3 started with pid=11
Wed Feb 19 11:05:58 2003
starting up 1 shared server(s) ...
starting up 1 dispatcher(s) for network address '(ADDRESS=(PARTIAL=YES)(PROTOCOL=TCP))'...
Wed Feb 19 11:05:59 2003
alter database mount exclusive
Wed Feb 19 11:06:06 2003
Successful mount of redo thread 1, with mount id 518217758.
Wed Feb 19 11:06:06 2003
Database mounted in Exclusive Mode.
Completed: alter database mount exclusive
Wed Feb 19 11:06:06 2003
alter database open
Beginning crash recovery of 1 threads
Wed Feb 19 11:06:09 2003
Thread recovery: start rolling forward thread 1
Recovery of Online Redo Log: Thread 1 Group 1 Seq 241 Reading mem 0
Mem# 0 errs 0: E:ORACLEORADATAPHX2REDO03.LOG
Wed Feb 19 11:06:09 2003
Thread recovery: finish rolling forward thread 1
Thread recovery: 6 data blocks read, 6 data blocks written, 175 redo blocks read
Crash recovery completed successfully
Wed Feb 19 11:06:11 2003
Thread 1 advanced to log sequence 242
Thread 1 opened at log sequence 242
Current log# 2 seq# 242 mem# 0: E:ORACLEORADATAPHX2REDO02.LOG
Successful open of redo thread 1.
Wed Feb 19 11:06:11 2003
SMON: enabling cache recovery
SMON: disabling cache recovery
Wed Feb 19 11:06:14 2003
ORA-1599 signalled during: alter database open...
Re: ora-01033 when connecting to db [message #55835 is a reply to message #55833] Wed, 19 February 2003 05:51 Go to previous message
Mahesh Rajendran
Messages: 10707
Registered: March 2002
Location: oracleDocoVille
Senior Member
Account Moderator
ORA-1599 deals with rollback segs.
its wierd...that it is appearing here...
try replacing IP or hostName with LOCALHOST in all sqlnet.ora, tnsnames.ora , listener.ora etc...
Previous Topic: LGWR: terminating instance due to error 227
Next Topic: How to know the oracle database size
Goto Forum:
  


Current Time: Fri Sep 20 05:29:30 CDT 2024