Hello. I'm not very knowledgeable when it comes to DBA work, but I've hit a snag and would appreciate a little advice. I have an Oracle XE install on my home computer for keeping track of business receipts and such. Recently I couldn't connect to APEX and started looking into it. When I tried to connect with SQL+, I would get the message:
ERROR
OR-01033: Oracle initialization or shutdown in progress
So I stopped and started the DB, checked to see the listener service was going, and still have the issue. I checked my alert_xe.log file, and it's... huge. Attached at the bottom, I included a fragment of my log file that consists of the last recent timestamp.
I do have a script that runs on my computer that does an EXP every night on my schema, but if I try an IMP, I get the same message (which makes sense since my DB apparently isn't running).
What would be your suggestions? I wanted some advice before I uninstalled and re-installed then imported my dmp backups.
Thanks to any necromancers who can help me bring this back from the dead!
Dump file e:\oraclexe\app\Oracle\admin\xe\bdump\alert_xe.log
Thu Oct 29 20:40:40 2009
Oracle V10.2.0.1.0 - Production vsnsta=0
vsnsql=14 vsnxtr=3Windows XP Version V5.1 Service Pack 2
CPU: 1 - type 586
Process Affinity: 0x00000000
Memory (Avail/Total): Ph:211M/511M, Ph+PgF:1012M/1247M, VA:1945M/2047M
Thu Oct 29 20:40:40 2009
Starting Oracle instance (normal)
LICENSE_MAX_SESSION = 0
LICENSE_SESSIONS_WARNING = 0
Picked latch-free SCN scheme 2
Using LOG_ARCHIVE_DEST_10 parameter default value as USE_DB_RECOVERY_FILE_DEST
Autotune of undo retention is turned on.
IMODE=BRILAT =10
LICENSE_MAX_USERS = 0
SYS auditing is disabled
Thu Oct 29 20:40:52 2009
Ksdpec: called for event 13740 prior to event group initialization
Starting up Oracle RDBMS Version: 10.2.0.1.0.
System parameters with non-default values
Sessions = 49
__shared_pool_size = 104857600
__large_pool_size = 8388608
__java_pool_size = 4194304
__streams_pool_size = 0
Spfile = E:\ORACLEXE\APP\Oracle\PRODUCT\10.2.0\SERVER\DBS\SPFILEXE.ORA
Sga_target = 146800640
Control_files = E:\ORACLEXE\ORADATA\XE\CONTROL.DBF
__db_cache_size = 25165824
Compatible = 10.2.0.1.0
Db_recovery_file_dest = E:\oraclexe\app\Oracle\flash_recovery_area
db_recovery_file_dest_size= 10737418240Undo_management = AUTO
Undo_tablespace = UNDO
remote_login_passwordfile= EXCLUSIVEDispatchers = (PROTOCOL=TCP) (SERVICE=XEXDB)
Shared_servers = 4
Job_queue_processes = 4
Audit_file_dest = E:\ORACLEXE\APP\Oracle\ADMIN\XE\ADUMP
Background_dump_dest = E:\ORACLEXE\APP\Oracle\ADMIN\XE\BDUMP
User_dump_dest = E:\ORACLEXE\APP\Oracle\ADMIN\XE\UDUMP
Core_dump_dest = E:\ORACLEXE\APP\Oracle\ADMIN\XE\CDUMP
Db_name = XE
Open_cursors = 300
Os_authent_prefix =
Pga_aggregate_target = 41943040
PSP0 started with pid=3, OS id=2988
MMAN started with pid=4, OS id=2992
PMON started with pid=2, OS id=2984
DBW0 started with pid=5, OS id=3004
LGWR started with pid=6, OS id=3008
CKPT started with pid=7, OS id=3012
SMON started with pid=8, OS id=3016
RECO started with pid=9, OS id=3020
CJQ0 started with pid=10, OS id=3024
MMON started with pid=11, OS id=3028
MMNL started with pid=12, OS id=3032
Thu Oct 29 20:40:55 2009
Starting up 1 dispatcher(s) for network address '(ADDRESS=(PARTIAL=YES)(PROTOCOL=TCP))'...
Starting up 4 shared server(s) ...
Oracle Data Guard is not available in this edition of Oracle.
Thu Oct 29 20:41:00 2009
Alter database mount exclusive
Thu Oct 29 20:41:05 2009
Setting recovery target incarnation to 2
Thu Oct 29 20:41:05 2009
Successful mount of redo thread 1, with mount id 2582644764
Thu Oct 29 20:41:05 2009
Database mounted in Exclusive Mode
Completed: alter database mount exclusive
Thu Oct 29 20:41:05 2009
ALTER DATABASE OPEN
Thu Oct 29 20:41:06 2009
Beginning crash recovery of 1 threads
Thu Oct 29 20:41:06 2009
Started redo scan
Thu Oct 29 20:41:07 2009
Completed redo scan
9180 redo blocks read, 514 data blocks need recovery
Thu Oct 29 20:41:07 2009
Started redo application at
Thread 1: logseq 797, block 5520
Thu Oct 29 20:41:09 2009
Recovery of Online Redo Log: Thread 1 Group 2 Seq 797 Reading mem 0
Mem# 0 errs 0: E:\ORACLEXE\APP\Oracle\FLASH_RECOVERY_AREA\XE\ONLINELOG\O1_MF_2_2MXYQN2G_.LOG
RECOVERY OF THREAD 1 STUCK AT BLOCK 28 OF FILE 2
Thu Oct 29 20:41:11 2009
Aborting crash recovery due to error 1172
Thu Oct 29 20:41:11 2009
Errors in file e:\oraclexe\app\Oracle\admin\xe\udump\xe_ora_3080.trc
ORA-01172: recovery of thread 1 stuck at block 28 of file 2
ORA-01151: use media recovery to recover block, restore backup if needed
ORA-1172 signalled during: alter database open...Thu Oct 29 20:55:05 2009
Db_recovery_file_dest_size of 10240 MB is 0.98% 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.
Thu Oct 29 22:50:17 2009
WARNING: inbound connection timed out (ORA-3136)
While I would generally wholeheartedly concur with that, I believe that XE only allows you to install one instance per server. I haven't tried to see whether that is a licensing restriction or a technical restriction that is checked by the installer, but I'm not sure that you can get a second XE database running on the server.
And while there are tools that can recover data from old datafiles, given that the free version of Oracle is being used, those tools probably aren't an option-- I don't think Oracle's DUL is available unless you have a support contract which isn't available on XE and the competitors are pretty darned pricey. If the data isn't important enough to need a commercial version of the database with support, patches, etc., it's probably not important enough to license one of these tools.
You can also try PRM-DUL:DBRECOVER for Oracle
DBRECOVER Recovery Options
For Oracle incidents, start with the DBRECOVER for Oracle trial to verify table visibility, row previews, and export readiness on copied datafiles. For MySQL and InnoDB incidents, DBRECOVER for MySQL is free software and can inspect.ibd files, ibdata1, and database directories locally.
When the case is urgent, preserve the original files first, work from copies, and contact paid emergency support with the database version, platform, error messages, file list, and recovery objective.