Problème dans Oracle 10G
Solved
bilanabl
Posted messages
63
Status
Member
-
HostOfSeraphim Posted messages 7340 Status Contributor -
HostOfSeraphim Posted messages 7340 Status Contributor -
Hello,
I am trying to connect to my database but I keep getting this error
ERROR: ORA-01033: ORACLE initialization or shutdown in progress
I can't solve the problem
I am trying to connect to my database but I keep getting this error
ERROR: ORA-01033: ORACLE initialization or shutdown in progress
I can't solve the problem
Configuration: Windows XP Internet Explorer 6.0
15 answers
I can connect with sys
I executed shutdown immediate and startup open
C:\>set ORACLE_SID=teste
C:\>sqlplus /nolog
SQL*Plus: Release 10.1.0.4.2 - Production on Fri Aug 21 22:33:17 2009
Copyright (c) 1982, 2005, Oracle. All rights reserved.
SQL> connect SYS/soprep AS SYSDBA
Connected.
SQL> shutdown immediate
ORA-01109: database not open
Database dismounted.
ORACLE instance stopped.
SQL> startup open
ORACLE instance started.
Total System Global Area 566231040 bytes
Fixed Size 789876 bytes
Variable Size 166720140 bytes
Database Buffers 398458880 bytes
Redo Buffers 262144 bytes
Database mounted.
ORA-16038: log 2 sequence# 249 cannot be archived
ORA-19809: limit exceeded for recovery files
ORA-00312: online log 2 thread 1:
'C:\ORACLE\PRODUCT\10.1.0\ORADATA\TESTE\REDO02.LOG'
SQL>
But when I connect to sqlplus, it always shows me the same error
ERROR: ORA-01033: ORACLE initialization or shutdown in progress
I executed shutdown immediate and startup open
C:\>set ORACLE_SID=teste
C:\>sqlplus /nolog
SQL*Plus: Release 10.1.0.4.2 - Production on Fri Aug 21 22:33:17 2009
Copyright (c) 1982, 2005, Oracle. All rights reserved.
SQL> connect SYS/soprep AS SYSDBA
Connected.
SQL> shutdown immediate
ORA-01109: database not open
Database dismounted.
ORACLE instance stopped.
SQL> startup open
ORACLE instance started.
Total System Global Area 566231040 bytes
Fixed Size 789876 bytes
Variable Size 166720140 bytes
Database Buffers 398458880 bytes
Redo Buffers 262144 bytes
Database mounted.
ORA-16038: log 2 sequence# 249 cannot be archived
ORA-19809: limit exceeded for recovery files
ORA-00312: online log 2 thread 1:
'C:\ORACLE\PRODUCT\10.1.0\ORADATA\TESTE\REDO02.LOG'
SQL>
But when I connect to sqlplus, it always shows me the same error
ERROR: ORA-01033: ORACLE initialization or shutdown in progress
SQL> SELECT * FROM v$recovery_file_dest;
NAME
--------------------------------------------------------------------------------
SPACE_LIMIT SPACE_USED SPACE_RECLAIMABLE NUMBER_OF_FILES
----------- ---------- ----------------- ---------------
C:\oracle\product\10.1.0\flash_recovery_area
2147483648 2141157888 0 244
NAME
--------------------------------------------------------------------------------
SPACE_LIMIT SPACE_USED SPACE_RECLAIMABLE NUMBER_OF_FILES
----------- ---------- ----------------- ---------------
C:\oracle\product\10.1.0\flash_recovery_area
2147483648 2141157888 0 244
Ok, my comic book is working very well thanks to you. I thank you for helping me and I'm sorry because I took a bit of your time.
Please, can you explain to me what the problem was?
Because I didn't quite understand these commands that you gave me.
Please, can you explain to me what the problem was?
Because I didn't quite understand these commands that you gave me.
Glad to have been able to help you.
The recovery files are histories of the modifications made to the database. Oracle relies on the parameter DB_RECOVERY_FILE_DEST_SIZE to limit the maximum size of these files: in your case, the write action exceeded the maximum file size and could not be completed, which caused the crash. The corrective query simply raised the max value to 3 GB instead of 2 GB, which resolved the issue.
The query "SELECT * FROM v$recovery_file_dest;" allows you to check the current limit and current usage. In the last line, the first value corresponds to the limit, and the second to the current usage (values expressed in bytes).
--
Configuration: Linux Debian Lenny / Kernel 2.6.26 / Gnome / Iceweasel 3
Internet Connection: ADSL Orange 8M (Livebox)
The recovery files are histories of the modifications made to the database. Oracle relies on the parameter DB_RECOVERY_FILE_DEST_SIZE to limit the maximum size of these files: in your case, the write action exceeded the maximum file size and could not be completed, which caused the crash. The corrective query simply raised the max value to 3 GB instead of 2 GB, which resolved the issue.
The query "SELECT * FROM v$recovery_file_dest;" allows you to check the current limit and current usage. In the last line, the first value corresponds to the limit, and the second to the current usage (values expressed in bytes).
--
Configuration: Linux Debian Lenny / Kernel 2.6.26 / Gnome / Iceweasel 3
Internet Connection: ADSL Orange 8M (Livebox)
Connect as SYSDBA and perform an immediate shutdown, or an abort shutdown if necessary.
--
Configuration: Linux Debian Lenny / Kernel 2.6.26 / Gnome / Iceweasel 3
Internet Connection: ADSL Orange 8M (Livebox)
--
Configuration: Linux Debian Lenny / Kernel 2.6.26 / Gnome / Iceweasel 3
Internet Connection: ADSL Orange 8M (Livebox)
OK.
So in your Windows console:
set ORACLE_SID=XXXX
sqlplus /nolog
connect / as SYSDBA
(XXXX being the instance you want to connect to)
Then, if you want to connect to another instance:
set ORACLE_SID=YYYY
sqlplus /nolog
connect ...
--
Configuration: Linux Debian Lenny / Kernel 2.6.26 / Gnome / Iceweasel 3
Internet connection: ADSL Orange 8M (Livebox)
So in your Windows console:
set ORACLE_SID=XXXX
sqlplus /nolog
connect / as SYSDBA
(XXXX being the instance you want to connect to)
Then, if you want to connect to another instance:
set ORACLE_SID=YYYY
sqlplus /nolog
connect ...
--
Configuration: Linux Debian Lenny / Kernel 2.6.26 / Gnome / Iceweasel 3
Internet connection: ADSL Orange 8M (Livebox)
Once connected, copy and paste the result of this command here:
SELECT * FROM v$recovery_file_dest;
--
Configuration: Linux Debian Lenny / Kernel 2.6.26 / Gnome / Iceweasel 3
Internet connection: ADSL Orange 8M (Livebox)