Database shutdown history

Hi
Is there any table or view for database shutdown history or availibility?

user13344656 wrote:
i want to save startup&shutdown history .That's not a business requirement, that's "I want".
But i dont know what message is true ...only 'ALTER DATABASE OPEN' OR 'COMPLETE:ALTER DATABASE OPEN'Every message written to the alert log is true. You can see what gets written to the log. Only you can decide which message is relevant to your want.
and when the server getting down abnormally (oute electricity) what is written on alert.log.Without electricity, nothing gets written . . .

Similar Messages

Urgent help needed; Database shutdown issues.

Urgent help needed; Database shutdown issues.
Hi all,
I am trying to shutdown my SAP database and am facing the issues below, can someone please suggest how I can go about resolving this issue and restart the database?
SQL> shutdown immediate
ORA-24324: service handle not initialized
ORA-24323: value not allowed
ORA-01089: immediate shutdown in progress - no operations are permitted
SQL> shutdown abort
ORA-01031: insufficient privileges
Thanks and regards,
Iqbal

Hi,
check SAP Note 700548 - FAQ: Oracle authorizations
also check Note 834917 - Oracle Database 10g: New database role SAPCONN
regards,
kaushal

8.1.5.-automate database shutdown:hepl needed

I have tried to setup the automate database shutdown by following Oracle Manual. When rebooting the Unix system(sun solaris 2.6), nothing could be recorded in the alert logfile. After manually starting up the database, alert logfile indicated always a crash recovery during the process.
Any suggestion will be appreciated on above problem!
Felix

Hi,
Below is the information from orclALRT.log:
There's a write/open error. At July 21, 21:00PM our backup is start to run.
Is it because the backup software locked some oracle's files ?
But after the error, the next morning July 22 the ORACLE instance is started with no error, even though user can't connect to the database.
TIA
Andi
Thread 1 advanced to log sequence 46212
Current log# 4 seq# 46212 mem# 0: E:\ORANT\ORADATA\ORACLE\REDO01.LOG
Sun Jul 21 21:38:26 2002
KCF: write/open error block=0x11072 online=1
file=1 E:\ORANT\ORADATA\ORACLE\SYSTEM01.DBF
error=27072 txt: 'OSD-04008: WriteFile() failure, unable to write to file
O/S-Error: (OS 33) The process cannot access the file because
another process has locked a portion of the file.'
DBW0: terminating instance due to error 1242
Instance terminated by DBW0, pid = 248
Mon Jul 22 03:00:04 2002
Starting ORACLE instance (normal)
Dump file E:\orant\admin\oracle\bdump\orclALRT.LOG
---------

Database shutdown problem

Hi,
My database takes quite a lot of time in shutting down, when I do normal shutdown.
Pls help
vip

Hi Aman,
F. Munoz Alvarez wrote:
This is because Oracle terminates all sessions and does a rollback on all.Francisco,
What does it mean by rollback here? So if I would kick in really big transaction and Oracle is shutting down, it will be rolling back my transcton? I don't think so. > My transaction info would be cleared immediately. Is there any way that I can see this happening ?
Aman....Take a look in the Oracle Docs:
- http://download.oracle.com/docs/cd/B19306_01/server.102/b14231/start.htm#sthref589
Immediate database shutdown proceeds with the following conditions:
- No new connections are allowed, nor are new transactions allowed to be started, after the statement is issued.
- Any uncommitted transactions are rolled back. (If long uncommitted transactions exist, this method of shutdown might not complete quickly, despite its name.)
- Oracle Database does not wait for users currently connected to the database to disconnect. The database implicitly rolls back active transactions and disconnects all connected users.
The next startup of the database will not require any instance recovery procedures.
Transactional database shutdown proceeds with the following conditions:
- No new connections are allowed, nor are new transactions allowed to be started, after the statement is issued.
- After all transactions have completed, any client still connected to the instance is disconnected.
- At this point, the instance shuts down just as it would when a SHUTDOWN IMMEDIATE statement is submitted.
The next startup of the database will not require any instance recovery procedures.
A transactional shutdown prevents clients from losing work, and at the same time, does not require all users to log off.
Cheers,
Francisco Munoz Alvarez
http://www.oraclenz.com
Sorry by the delay to answer, I'm having some issues with my internet connection :(

Database shutdown/startup

Dear all,
10.2.0.3 on Solaris 10.
When shutting down the database, shutdown hangs after database mounted as you can see below
SQL> startup
ORACLE instance started.
Total System Global Area 1073741824 bytes
Fixed Size                  2133800 bytes
Variable Size             435843288 bytes
Database Buffers          624951296 bytes
Redo Buffers               10813440 bytes
Database mounted.In one more session, I checked the alert log
Fri Jan 7 10:13:16 2011
Incremental checkpoint up to RBA [0x417a.3.0], current log tail at RBA [0x417a.87.0]
Fri Jan 7 10:13:16 2011
replication_dependency_tracking turned off (no async multimaster replication found)
Starting background process QMNC
QMNC started with pid=36, OS id=15146
Fri Jan 7 10:13:19 2011
Completed: ALTER DATABASE OPEN
^C
bash-3.00$
bash-3.00$
bash-3.00$
bash-3.00$
bash-3.00$ sqlplus "/ as sysdba"
SQL*Plus: Release 10.2.0.3.0 - Production on Fri Jan 7 10:16:28 2011
Copyright (c) 1982, 2006, Oracle. All Rights Reserved.
Connected to:
Oracle Database 10g Enterprise Edition Release 10.2.0.3.0 - 64bit Production
With the Partitioning, OLAP and Data Mining options
SQL>
SQL> select open_mode from v$database;
OPEN_MODE
READ WRITEAny idea ?.
Kai

There is no error message . Anyway alert log
Fri Jan 7 10:13:08 2011
Starting ORACLE instance (normal)
LICENSE_MAX_SESSION = 0
LICENSE_SESSIONS_WARNING = 0
Picked latch-free SCN scheme 3
Autotune of undo retention is turned on.
IMODE=BR
ILAT =88
LICENSE_MAX_USERS = 0
SYS auditing is disabled
ksdpec: called for event 13740 prior to event group initialization
Starting up ORACLE RDBMS Version: 10.2.0.3.0.
System parameters with non-default values:
_trace_files_public      = TRUE
processes                = 400
sessions                 = 800
timed_statistics         = TRUE
shared_pool_size         = 419430400
shared_pool_reserved_size= 41943040
sga_target               = 1073741824
control_files            = /erp/u01/medh/db/apps_st/data/cntrl01.dbf, /erp/u01/medh/db/apps_st/data/cntrl02.dbf, /erp/u01/medh/db/apps_st/data/cnt
rl03.dbf
db_block_checksum        = TRUE
log_archive_dest         = /oracle/arch/medh_ARCH
log_archive_format       = medh%t_%s_%r.arc
log_buffer               = 10485760
log_checkpoint_interval = 100000
log_checkpoint_timeout   = 1200
db_files                 = 512
db_file_multiblock_read_count= 8
log_checkpoints_to_alert = TRUE
dml_locks                = 10000
undo_management          = AUTO
undo_tablespace          = APPS_UNDOTS1
db_block_checking        = FALSE
session_cached_cursors   = 500
utl_file_dir             = /usr/tmp, /usr/tmp, /erp/u01/medh/db/tech_st/10.2.0/appsutil/outbound/medh_sed04, /usr/tmp
plsql_native_library_dir = /erp/u01/medh/db/tech_st/10.2.0/plsql/nativelib
plsql_native_library_subdir_count= 149
plsql_code_type          = INTERPRETED
plsql_optimize_level     = 2
job_queue_processes      = 2
cursor_sharing           = EXACT
parallel_min_servers     = 0
parallel_max_servers     = 8
background_dump_dest     = /erp/u01/medh/db/tech_st/10.2.0/admin/medh_sed04/bdump
user_dump_dest           = /erp/u01/medh/db/tech_st/10.2.0/admin/medh_sed04/udump
max_dump_file_size       = 20480
core_dump_dest           = /erp/u01/medh/db/tech_st/10.2.0/admin/medh_sed04/cdump
db_name                  = medh
open_cursors             = 600
ifile                    = /erp/u01/medh/db/tech_st/10.2.0/dbs/medh_sed04_ifile.ora
_sort_elimination_cost_ratio= 5
_b_tree_bitmap_plans     = FALSE
_fast_full_scan_enabled = FALSE
_sqlexec_progression_cost= 2147483647
_like_with_bind_as_equality= TRUE
pga_aggregate_target     = 1073741824
workarea_size_policy     = AUTO
optimizer_secure_view_merging= FALSE
aq_tm_processes          = 1
olap_page_pool_size      = 4194304
PMON started with pid=2, OS id=12494
PSP0 started with pid=4, OS id=12496
MMAN started with pid=6, OS id=12499
DBW0 started with pid=8, OS id=12511
DBW1 started with pid=3, OS id=12544
DBW2 started with pid=10, OS id=12574
LGWR started with pid=5, OS id=12604
CKPT started with pid=12, OS id=12628
SMON started with pid=14, OS id=12653
RECO started with pid=16, OS id=12680
CJQ0 started with pid=18, OS id=12712
MMON started with pid=20, OS id=12738
MMNL started with pid=22, OS id=12761
Fri Jan 7 10:13:10 2011
ALTER DATABASE   MOUNT
Fri Jan 7 10:13:14 2011
Setting recovery target incarnation to 2
Fri Jan 7 10:13:14 2011
Successful mount of redo thread 1, with mount id 3947812854
Fri Jan 7 10:13:14 2011
Database mounted in Exclusive Mode
Completed: ALTER DATABASE   MOUNT
Fri Jan 7 10:13:15 2011
ALTER DATABASE OPEN
Fri Jan 7 10:13:15 2011
Beginning crash recovery of 1 threads
parallel recovery started with 8 processes
Fri Jan 7 10:13:15 2011
Started redo scan
Fri Jan 7 10:13:15 2011
Completed redo scan
0 redo blocks read, 0 data blocks need recovery
Fri Jan 7 10:13:15 2011
Started redo application at
Thread 1: logseq 16761, block 30591, scn 30945234899
Fri Jan 7 10:13:15 2011
Recovery of Online Redo Log: Thread 1 Group 2 Seq 16761 Reading mem 0
Mem# 0: /erp/u01/medh/db/apps_st/data/log02b.rdo
Mem# 1: /erp/u01/medh/db/apps_st/data/log02a.rdo
Fri Jan 7 10:13:15 2011
Completed redo application
Fri Jan 7 10:13:15 2011
Completed crash recovery at
Thread 1: logseq 16761, block 30591, scn 30945254900
0 data blocks read, 0 data blocks written, 0 redo blocks read
Fri Jan 7 10:13:15 2011
LGWR: STARTING ARCH PROCESSES
ARC0 started with pid=34, OS id=14889
Fri Jan 7 10:13:15 2011
ARC0: Archival started
ARC1: Archival started
LGWR: STARTING ARCH PROCESSES COMPLETE
ARC1 started with pid=15, OS id=14921
Fri Jan 7 10:13:15 2011
Thread 1 advanced to log sequence 16762
Thread 1 opened at log sequence 16762
Current log# 3 seq# 16762 mem# 0: /erp/u01/medh/db/apps_st/data/log03b.rdo
Current log# 3 seq# 16762 mem# 1: /erp/u01/medh/db/apps_st/data/log03a.rdo
Successful open of redo thread 1
Fri Jan 7 10:13:15 2011
MTTR advisory is disabled because FAST_START_MTTR_TARGET is not set
Fri Jan 7 10:13:15 2011
ARC0: Becoming the 'no FAL' ARCH
ARC0: Becoming the 'no SRL' ARCH
Fri Jan 7 10:13:15 2011
ARC1: Becoming the heartbeat ARCH
Fri Jan 7 10:13:15 2011
SMON: enabling cache recovery
Fri Jan 7 10:13:16 2011
Successfully onlined Undo Tablespace 1.
Fri Jan 7 10:13:16 2011
SMON: enabling tx recovery
Fri Jan 7 10:13:16 2011
Database Characterset is AR8MSWIN1256
Fri Jan 7 10:13:16 2011
Incremental checkpoint up to RBA [0x417a.3.0], current log tail at RBA [0x417a.87.0]
Fri Jan 7 10:13:16 2011
replication_dependency_tracking turned off (no async multimaster replication found)
Starting background process QMNC
QMNC started with pid=36, OS id=15146
Fri Jan 7 10:13:19 2011
Completed: ALTER DATABASE OPEN

Database size history on Java instance

Hello,
Does anybody know how to get the database size history (db02) on a Java only instance.
The system is portal 7 running on SQL 2005 and windows 2003.
Thanks

Kruger,
Your best bet to get this type of information is going to be through the SQL Server Enterprise Manager. J2EE Engines typically do not grow as they rarely hold information but are pass-through systems. For this reason, there is little detail in the Portal for this specific type of information.
If you setup the Solution Manager as a CEN Monitor for the Java Instance you can provide some thresholds for the MTE's on Db but again, won't hold informaiton on size history.
Hope that helps - if this answers your question, please set this thread to answered.

Oracle database shutdown unexpectedly

Hi,
My oracle database shutdown unexpectedly several times this week and the alert log shows the below errors
database shutdown unexpectedly with the folloing messge in alert
Fatal NI connect error 12560, connecting to:
(LOCAL=NO)
VERSION INFORMATION:
TNS for 64-bit Windows: Version 11.1.0.6.0 - Production
Oracle Bequeath NT Protocol Adapter for 64-bit Windows: Version 11.1.0.6.0 - Production
Windows NT TCP/IP NT Protocol Adapter for 64-bit Windows: Version 11.1.0.6.0 - Production
Time: 29-JUL-2012 06:24:48
Tracing not turned on.
Tns error struct:
ns main err code: 12560
TNS-12560: TNS:protocol adapter error
ns secondary err code: 0
nt main err code: 0
nt secondary err code: 0
nt OS err code: 0
ORA-609 : opiodr aborting process unknown ospid (3948_1704)
Sun Jul 29 06:26:54 2012
Please any help ???
Thanks

943086 wrote:
Thanks
both links descriping the same oracle metalink docs, witch its not applicable
thanksyou are not help us to help you , both metalink that i have been posted talking about windows environment , OTN thread talking about windows environment and seems to me in all links that i have been posted its same alertlog error .

DB02 - Database size history report

Hi,
On our ECC 6.0 PRD system, we need to extend the time span of the history report. Currently the report goes back to 1/31/08. We need to extend that date to at least a year.
To navigate to the DB size history report, use:
Tx DB02 -> Space ->History ->Database size history report
Regards,
Sai R.

The statistics are shown from where the collector was started.
If you cant see statistics before 1-31-08 I think there is no way to solve the problem because there is no data before ( RSCOLL00 program ).
But someone else can help you better or give you the solution.
Antonio Voce.
Edited by: Antonio Voce on Jun 9, 2008 4:45 PM

Database shutdown tooks 20 minutes

Hi
We have Oracle EBS R12.0.6 running on single node configuration. I have a strange situation with database shutdown normal. When i had shutdown database normal last 2 weeks for level 0 backup, shutdown took 5 minutes. Yesterday, again for database level 0 backup, shutdown took 20 minutes. I checked alert log, there were no active calls to kill but it took 20 minutes,why? How can i make the database shutdown faster with normal option?
Help me please, thanks.
Ariz

Arizuddin wrote:
Hi
We have Oracle EBS R12.0.6 running on single node configuration. I have a strange situation with database shutdown normal. When i had shutdown database normal last 2 weeks for level 0 backup, shutdown took 5 minutes. Yesterday, again for database level 0 backup, shutdown took 20 minutes. I checked alert log, there were no active calls to kill but it took 20 minutes,why? How can i make the database shutdown faster with normal option?
Help me please, thanks.
ArizYou can make shutdown faster with the normal option pretty much only by ensuring that all client sessions -- including background jobs, concurrent managers, workflow etc are shutdown and logged off
You could however also do one of the following (in my order of preference):
1) don't shutdown the database for backup and use hot backup. For an OLTP db whose data you care about this should be the option of choice IMO.
2) use shutdown immediate; - this is normally faster and is guaranteed to complete after an hour - shutdown normal isn't guaranteed to shutdown ( if an active session is left open but uncommitted).
3) use shutdown abort; This is very fast! It's no good for a cold backup though as the datafiles will be inconsistent.

Database Shutdown Some Times

Dear All
I have Installed Oracle Database 10G on Windows Server 2003
But When I need Connect To The database I Discover it shutdown then I will Startup Again to Connect.
Please I need help To see What Happen To Oracle Because its Online Database
There is files In Oracle That I can Trace The Error or Any Thing To Help.
Thanks In Advance.

user8942603 wrote:
Dear All
I have Installed Oracle Database 10G on Windows Server 2003
But When I need Connect To The database I Discover it shutdown then I will Startup Again to Connect.
Please I need help To see What Happen To Oracle Because its Online Database
There is files In Oracle That I can Trace The Error or Any Thing To Help.
Thanks In Advance.Duplicate post. Please do not cross post
Database Shutdown In Some Times

DATABASE SHUTDOWN 후 STARTUP시 ORA-7445가 발생하면서 OS PROMPT로 빠짐

제품 : ORACLE SERVER
작성날짜 : 2002-04-10
DATABASE SHUTDOWN 후 STARTUP시 ORA-7445가 발생하면서 OS PROMPT로 빠짐
=====================================================================
Server Platform : Sparc Sunw Ultra Enterprise 10000
(CPU 44개, Main Memory 9 Megabytes)
ORACLE RDBMS 7.3.3.4
ORACLE PARALLEL SERVER 환경
Sun Cluster Volume Manager 2.0
DB size : 약 1.2 Terabytes (=1200 Gigabytes)
관련 TAR : 9168089.7
조치 내역 :
1. init.ora에 다음의 event와 hidden parameter를 설정
1) event="10210 trace name context forever, level 10"
(Data Block Integrity를 check, Refer to Note 21184.1)
2) event="10211 trace name context forever, level 10"
(Data Block Integrity를 check, Refer to Note 21185.1
3) dbblock_cache_protect = true (Refer to note18144.1)
corrupt된 block이 memory에 load되는 것을 방지
2. Startup mount 후 recover database를 실행
ORA-600[6593] [26]발생 - Detection of block corruption
3. alter database open 실행
ORA-1578 file#88 block #172628 발생 하였으나
ORA-7445 없이 open됨
(문제가 되는 특정 테이블과 데이타 블럭 발견)
4. 위의 file block에 data를 확인하기 위하여 block dump를 함
"Alter session set events 'immediate trace name
blockdump level xxxxx"
( xxxxx는 Data Block Address 값의 decimal 값)
- Block dump에 있는 hexa값을 ascii로 변환
5. corrupt된 block을 제외한 data를 recover하기 위하여 새로운
tablespace를 생성 후 다음 실행.
"Insert into (TABLEA) select * from (TABLEB)
where index_column > ' '
and rowid not like 'corrupt된 row의 rowid들';"
(TABLEA는 corrupt되지 않은 row들을 제외한 나머지 row들을
포함할 새로운 테이블이고, TABLEB는 corrupt된 row들을 갖고
있었던 기존의 테이블)
6. 새로 생성한 테이블의 데이타 확인한 후 기존의 corrupt된
테이블 drop시킴
7. 새 테이블을 rename하여 기존의 테이블 이름과 같게 함.

How to monitor the success of database shutdown command

Sometimes , the "shutdown immediate" command can fail on one of our databases. We want to monitor the success of the shutdown command. If it fails, then we will issue a "shutdown abort" command. My question is: how can I monitor the success of database shutdown command?
sqlplus / as sysdba <<EOF
shutdown immediate
EOF
if failed ???? ;then
sqlplus / as sysdba <<EOF
shutdown abort
EOF
Thanks in advance for your help!

No version, no platform. How do you expect help?
And what does 'fail' mean?
A few remarks:
You can have sqlplus error out to the O/S by using whenever sqlerror exit failure
Shutdown immediate usually doesn't fail but just doesn't complete.
One would usually monitor the alert log as to check what is going on, and issue the shutdown abort in a different session.
Sybrand Bakker
Senior Oracle DBA

TNS Listener -ORA-12514 error following database shutdown - Oracle 11g

Hi
I have hit a problem with my oracle development database.
When in sqlplus I executed the shutdown command, but nothing happened for several minutes and it was just hanging. No messages were displayed to the screen. The only thing was to close the command window. When I open sqlplus again and enter in the user name password as sysdba I am getting ORA 12514 TNS Listener could not resolve service in descriptor. This is odd as I could log on before and use the database. So I thought that the services were still shutting down I waited, and using the Windows snap on tool for Oracle 11g, I restarted the services on the database, but this has had no effect.
Even using EM made no difference because I couldn't log on to perform a startup or recovery.
So, please does anyone know how I can fix this?
Thanks

user633278 wrote:
Hi
I have hit a problem with my oracle development database.
When in sqlplus I executed the shutdown command, but nothing happened for several minutes and it was just hanging. No messages were displayed to the screen. The only thing was to close the command window. When I open sqlplus again and enter in the user name password as sysdba I am getting ORA 12514 TNS Listener could not resolve service in descriptor. This is odd as I could log on before and use the database. So I thought that the services were still shutting down I waited, and using the Windows snap on tool for Oracle 11g, I restarted the services on the database, but this has had no effect.
Even using EM made no difference because I couldn't log on to perform a startup or recovery.
So, please does anyone know how I can fix this?
open Command Window & do EXACTLY as below; line for line
sqlplus
/ as sysdba
shutdown abort
startup
exit
COPY command & results from above then PASTE all back here

Database shutdown taking more time, is listener process a problem??

Dear all,
though its a general process to stop the listener before shutting down the database for cold backup. but is it so that if you don't stop the listener before giving shutdown immediate command, the shutdown process takes long time than normal expected time?
because as per my understanding, the listener process is used just for the connection and when we give shutdown command the database automatically rejects any new connections. your valuable comments are required.

No version, as usual, and the answer is version specific.
Why is it so difficult to include those 4 digits?
Dear all,
though its a general process to stop the listener
before shutting down the database for cold backup.
but is it so that if you don't stop the listener
before giving shutdown immediate command, the
shutdown process takes long time than normal expected
time? No. Must be a fairy tale without proof.
You might need set job_queue_processes to 0 and aq_tm_processes to 0, but that has nothing to do with the listener.
>
because as per my understanding, the listener process
is used just for the connection and when we give
shutdown command the database automatically rejects
any new connections. your valuable comments are
required.--
Sybrand Bakker
Senior Oracle DBA

Oracle 10.2..0.3.0 - Database shutdown during connection

Hi,
I have oracle 10.2.0.3.0 with developer 6i as front-end. I can successfully connect to the database from forms6i during the development and runtime but failing to connect to oracle when trying through oracle query builder. It also shutdown the database.
The same problem I am getting when I try to connect through OLEDB or ODBC.
Please let me know what is the problem. Is there something wrong with this version.
Thanks
Nasir

There is only one database available and I can connect via SQLPLUS.
I also tried to seach any reason in trace files but only get following line. I dont know if it is related to this issue.
Dump file c:\oracle\product\10.2.0\admin\orcllife\udump\orcllife_ora_1420.trc
Thu Mar 06 14:46:44 2008
ORACLE V10.2.0.3.0 - 64bit Production vsnsta=0
vsnsql=14 vsnxtr=3
Oracle Database 10g Release 10.2.0.3.0 - 64bit Production
Windows NT Version V5.2 Service Pack 2
CPU : 4 - type 8664, 1 Physical Cores
Process Affinity : 0x0000000000000000
Memory (Avail/Total): Ph:1265M/4089M, Ph+PgF:3874M/6788M
Instance name: orcllife
Redo thread mounted by this instance: 1
Oracle process number: 23
Windows thread id: 1420, image: ORACLE.EXE (SHAD)
*** 2008-03-06 14:46:45.056
opiino: Attach failed! error=-1 ifvp=0000000000000000
Thanks

Database shutdown history

Similar Messages

Maybe you are looking for