Monday, 1 March 2021

 SQL profiles:


A SQL profile contains supplementary or additional statistics specific to a SQL query. SQL profile information is stored in the data dictionary. The optimizer uses this information during optimization to determine the most optimal plan.

Below steps will help to implement SQL profile for a query in different scenarios:

1. SQL Tuning Advisor task created for a slow performing query and the task includes a recommendation to create SQL profile.

2. Restore old execution plan for a query.

3. Copy execution plan for a query from one database to another database.


Prerequisite Steps

• Identify the SQL_ID and plan hash value for the slow performing query.

• Run below queries to find if there is change in plan or if a better performing plan was used.


set pages 200 linesize 200

select distinct *from (select sql_id, plan_hash_value, trunc(begin_interval_time) as begin_date

from dba_hist_snapshot natural join dba_hist_sqlstat

where begin_interval_time between

to_date('01-JAN-2021 1228','dd-mon-yyyy hh24mi')

and to_date('30-JAN-2021 1248','dd-mon-yyyy hh24mi')

and sql_id in ( ' <SQL_ID>' ) ) order by 3 desc;


Average Elapsed Time in sec for each plan: 

WITH p AS (

SELECT plan_hash_value FROM gv$sql_plan

WHERE sql_id = TRIM(‘<YOUR_SQL_ID>')

AND other_xml IS NOT NULL

UNION

SELECT plan_hash_value FROM dba_hist_sql_plan

WHERE sql_id = TRIM('&&sql_id.')

AND other_xml IS NOT NULL ),

m AS (SELECT plan_hash_value,

SUM(elapsed_time)/SUM(executions) avg_et_secs

FROM gv$sql

WHERE sql_id = TRIM('&&sql_id.')

AND executions > 0

GROUP BY

plan_hash_value ),

a AS (

SELECT plan_hash_value,

SUM(elapsed_time_total)/SUM(executions_total) avg_et_secs

FROM dba_hist_sqlstat

WHERE sql_id = TRIM('<YOUR_SQL_ID>')

AND executions_total > 0

GROUP BY

plan_hash_value )

SELECT p.plan_hash_value,

ROUND(NVL(m.avg_et_secs, a.avg_et_secs)/1e6, 3) avg_et_secs

FROM p, m, a

WHERE p.plan_hash_value = m.plan_hash_value(+)

AND p.plan_hash_value = a.plan_hash_value(+)

ORDER BY

avg_et_secs NULLS LAST;

PLAN_HASH_VALUE AVG_ET_SECS

--------------- -----------

12233642251     .006

3453222222       .036

1234543016      .922


From above two queries it is evident that the old plan hash value (1234543016 ) performed better.

  • Execution Steps

This section describe the process to create SQL profile for different scenarios discussed above.

• SQL Tuning Advisor:

o After identifying the candidate query’s SQL_ID and Plan Hash Value, login to the database using Enterprise Manager Cloud Control.

o Navigate to the query by searching the SQL_ID and execute the SQL Tuning Advisor for the query.

o If a SQL profile is recommended, accept the profile and test the query performance, with and without profile. 

• Restore old execution plan/Copy SQL profile to another database:

o Run the coe_xfr_sql_profile.sql in SQLT's utl subdirectory, by inputing the SQL_ID and Plan Hash Value (good) as parameters


download sqlt and unzip the file to your custom location

cd SQLT_LOCATION/sqlt/utl

login to oracle database server:

setup database env

sqlplus "/ as sysdba"

SQL> @coe_xfr_sql_profile.sql <your sql_id>  <plan_hash_value>


example:

SQL> @coe_xfr_sql_profile.sql 2fxxxxxxxxu 3731234451

Parameter 1:

SQL_ID (required)

PLAN_HASH_VALUE AVG_ET_SECS

--------------- -----------

3731234451 .006

3432922222 .036

2253653324 .916

17434378898

Parameter 2:

PLAN_HASH_VALUE (required)

Values passed:

~~~~~~~~~~~~~

SQL_ID : "2fxxxxxxxxu"

PLAN_HASH_VALUE: "3731234451"

Execute coe_xfr_sql_profile_2fxxxxxxxxu_3731234451.sql

on TARGET system in order to create a custom SQL Profile

with plan 3733642251 linked to adjusted sql_text.

COE_XFR_SQL_PROFILE completed.

Edit the above profile creation script and in the end change the FORCE_MATCH from FALSE to TRUE.


Create the SQL PROFILE.

SQL> @coe_xfr_sql_profile_2fxxxxxxxxu_3731234451.sql

....................

... manual custom SQL Profile has been created

COE_XFR_SQL_PROFILE_coe_2fxxxxxxxxu_3731234451 completed

SQL> 6. Post Execution Steps

• Verify the SQL profile

SQL> select name, trunc(created) ,status , FORCE_MATCHING from dba_sql_profiles where name like '%22fxxxxxxxxu%' order by created desc;

NAME TRUNC(CRE STATUS FOR

------------------------------ --------- -------- ---

coe_2fxxxxxxxxu_3731234451 25-JAN-21 ENABLED YES

• Verify the Plan Hash Value using the query from prerequisites steps


 Backout Plan

• Drop the SQL profile

As sysdba

BEGIN

DBMS_SQLTUNE.DROP_SQL_PROFILE(name => '&name_of_sql_profile');

END;

/

Posted by at No comments:

Thursday, 14 March 2013

About oracle database “startup & Shutdown"

About the “startup”
From front-end:
 
[oracle@geetdb ~]$ sqlplus "/as sysdba"
SQL*Plus: Release 11.2.0.3.0 Production on Sat Mar 1 10:03:56 2013
 
Copyright (c) 1982, 2011, Oracle.  All rights reserved.
 
Connected to an idle instance.
 
SQL> startup
ORACLE instance started.
 
Total System Global Area  368263168 bytes
Fixed Size                 1345016 bytes
Variable Size            276826632 bytes
Database Buffers          83886080 bytes
Redo Buffers               6205440 bytes
Database mounted.
Database opened.
 
From back-end:
 
[oracle@geetdb trace]$ tail -f  alert_GEETDB11G.log
Time drift detected. Please check VKTM trace file for more details.
Tue Feb 26 19:34:14 2013
Closing scheduler window
Closing Resource Manager plan via scheduler window
Clearing Resource Manager plan via parameter
Tue Feb 26 20:29:31 2013
Thread 1 advanced to log sequence 5 (LGWR switch)
  Current log# 2 seq# 5 mem# 0: /u01/app/oracle/oradata/GEETDB11G/redo02.log
Tue Feb 26 20:29:34 2013
Archived Log entry 20 added for thread 1 sequence 4 ID 0x5f72a5bb dest 1:
Sat Mar  01 10:04:07 2013
Starting ORACLE instance (normal)
LICENSE_MAX_SESSION = 0
LICENSE_SESSIONS_WARNING = 0
Picked latch-free SCN scheme 2
Using LOG_ARCHIVE_DEST_1 parameter default value as USE_DB_RECOVERY_FILE_DEST
Autotune of undo retention is turned on.
IMODE=BR
ILAT =27
LICENSE_MAX_USERS = 0
SYS auditing is disabled
Starting up:
Oracle Database 11g Enterprise Edition Release 11.2.0.3.0 - Production
With the Partitioning, OLAP, Data Mining and Real Application Testing options.
ORACLE_HOME = /u01/app/oracle/database/11.2.0
System name:   Linux
Node name:     geetdb.dbinterest.local
Release:       2.6.18-164.el5xen
Version:       #1 SMP Thu Sep 3 02:41:56 EDT 2009
Machine:       i686
VM name:       Xen Version: 3.1 (PVM)
Using parameter settings in server-side spfile /u01/app/oracle/database/11.2.0/dbs/spfileGEETDB11G.ora
System parameters with non-default values:
  processes                = 150
  memory_target            = 352M
  control_files            = "/u01/app/oracle/oradata/GEETDB11G/control01.ctl"
  control_files            = "/u01/app/oracle/fast_recovery_area/GEETDB11G/control02.ctl"
  db_block_size            = 8192
  compatible               = "11.2.0.0.0"
  log_archive_format       = "%t_%s_%r.dbf"
  db_recovery_file_dest    = "/u01/app/oracle/fast_rec"
  db_recovery_file_dest_size= 4977M
  undo_tablespace          = "UNDOTBS1"
  remote_login_passwordfile= "EXCLUSIVE"
  db_domain                = ""
  dispatchers              = "(PROTOCOL=TCP) (SERVICE=GEETDB11GXDB)"
  audit_file_dest          = "/u01/app/oracle/admin/GEETDB11G/adump"
  audit_trail              = "DB"
  db_name                  = "GEETDB11G"
  open_cursors             = 300
  diagnostic_dest          = "/u01/app/oracle"
Sat Mar  01 10:04:13 2013
PMON started with pid=2, OS id=4788
Sat Mar  01 10:04:13 2013
PSP0 started with pid=3, OS id=4790
Sat Mar  01 10:04:14 2013
VKTM started with pid=4, OS id=4792 at elevated priority
VKTM running at (4)millisec precision with DBRM quantum (100)ms
Sat Mar  01 10:04:14 2013
GEN0 started with pid=5, OS id=4796
Sat Mar  01 10:04:14 2013
DIAG started with pid=6, OS id=4798
Sat Mar  01 10:04:14 2013
DBRM started with pid=7, OS id=4800
Sat Mar  01 10:04:14 2013
DIA0 started with pid=8, OS id=4802
Sat Mar  01 10:04:14 2013
MMAN started with pid=9, OS id=4804
Sat Mar  01 10:04:14 2013
DBW0 started with pid=10, OS id=4806
Sat Mar  01 10:04:14 2013
LGWR started with pid=11, OS id=4808
Sat Mar  01 10:04:14 2013
CKPT started with pid=12, OS id=4810
Sat Mar  01 10:04:14 2013
SMON started with pid=13, OS id=4812
Sat Mar  01 10:04:14 2013
RECO started with pid=14, OS id=4814
Sat Mar  01 10:04:14 2013
MMON started with pid=15, OS id=4816
starting up 1 dispatcher(s) for network address '(ADDRESS=(PARTIAL=YES)(PROTOCOL=TCP))'...
Sat Mar  01 10:04:14 2013
MMNL started with pid=16, OS id=4818
starting up 1 shared server(s) ...
ORACLE_BASE from environment = /u01/app/oracle
Sat Mar  01 10:04:16 2013
ALTER DATABASE   MOUNT
Successful mount of redo thread 1, with mount id 1602180576
Allocated 3981204 bytes in shared pool for flashback generation buffer
Starting background process RVWR
Sat Mar  01 10:04:20 2013
RVWR started with pid=20, OS id=4847
Database mounted in Exclusive Mode
Lost write protection disabled
Completed: ALTER DATABASE   MOUNT
Sat Mar  01 10:04:21 2013
ALTER DATABASE OPEN
Beginning crash recovery of 1 threads
Started redo scan
Completed redo scan
 read 158 KB redo, 38 data blocks need recovery
Started redo application at
 Thread 1: logseq 4, block 78144
Recovery of Online Redo Log: Thread 1 Group 1 Seq 4 Reading mem 0
  Mem# 0: /u01/app/oracle/oradata/GEETDB11G/redo01.log
Recovery of Online Redo Log: Thread 1 Group 2 Seq 5 Reading mem 0
  Mem# 0: /u01/app/oracle/oradata/GEETDB11G/redo02.log
Completed redo application of 0.03MB
Completed crash recovery at
 Thread 1: logseq 5, block 18, scn 852252
 38 data blocks read, 38 data blocks written, 158 redo k-bytes read
LGWR: STARTING ARCH PROCESSES
Sat Mar  01 10:04:23 2013
ARC0 started with pid=21, OS id=4850
Sat Mar  01 10:04:24 2013
ARC0: Archival started
LGWR: STARTING ARCH PROCESSES COMPLETE
ARC0: STARTING ARCH PROCESSES
Sat Mar  01 10:04:24 2013
ARC1 started with pid=22, OS id=4852
Thread 1 advanced to log sequence 6 (thread open)
Thread 1 opened at log sequence 6
  Current log# 3 seq# 6 mem# 0: /u01/app/oracle/oradata/GEETDB11G/redo03.log
Successful open of redo thread 1
MTTR advisory is disabled because FAST_START_MTTR_TARGET is not set
Sat Mar 02 10:04:25 2013
SMON: enabling cache recovery
Sat Mar 02 10:04:25 2013
ARC2 started with pid=23, OS id=4854
ARC1: Archival started
ARC2: Archival started
Sat Mar 02 10:04:25 2013
ARC3 started with pid=24, OS id=4856
ARC1: Becoming the 'no FAL' ARCH
ARC1: Becoming the 'no SRL' ARCH
ARC2: Becoming the heartbeat ARCH
Archived Log entry 21 added for thread 1 sequence 5 ID 0x5f72a5bb dest 1:
ARC3: Archival started
ARC0: STARTING ARCH PROCESSES COMPLETE
[4848] Successfully onlined Undo Tablespace 2.
Undo initialization finished serial:0 start:1153636 end:1155226 diff:1590 (15 seconds)
Verifying file header compatibility for 11g tablespace encryption..
Verifying 11g file header compatibility for tablespace encryption completed
SMON: enabling tx recovery
Database Characterset is AL32UTF8
No Resource Manager plan active
replication_dependency_tracking turned off (no async multimaster replication found)
Sat Mar 02 10:04:33 2013
Starting background process QMNC
Sat Mar 02 10:04:33 2013
QMNC started with pid=25, OS id=4858
Completed: ALTER DATABASE OPEN
Sat Mar 02 10:04:43 2013
db_recovery_file_dest_size of 4977 MB is 41.60% 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.
Sat Mar 02 10:04:43 2013
Starting background process CJQ0
Sat Mar 02 10:04:44 2013
CJQ0 started with pid=32, OS id=4881
Setting Resource Manager plan SCHEDULER[0x318E]:DEFAULT_MAINTENANCE_PLAN via scheduler window
Setting Resource Manager plan DEFAULT_MAINTENANCE_PLAN via parameter
Sat Mar 02 10:04:50 2013
Starting background process VKRM
Sat Mar 02 10:04:50 2013
VKRM started with pid=28, OS id=4913
Sat Mar 02 10:05:07 2013
Begin automatic SQL Tuning Advisor run for special tuning task  "SYS_AUTO_SQL_TUNING_TASK"
Sat Mar 02 10:05:26 2013
End automatic SQL Tuning Advisor run for special tuning task  "SYS_AUTO_SQL_TUNING_TASK"
Sat Mar 02 10:09:35 2013
Starting background process SMCO
Sat Mar 02 10:09:35 2013
SMCO started with pid=29, OS id=4965
 
About the Oracle “shutdown immediate”
 
From front-end:
SQL> shutdown immediate
Database closed.
Database dismounted.
ORACLE instance shut down.
 
From back-end:
Sat Mar 02 11:19:30 2013
Shutting down instance (immediate)
Stopping background process SMCO
Shutting down instance: further logons disabled
Sat Mar 02 11:19:31 2013
Stopping background process CJQ0
Stopping background process QMNC
Stopping background process MMNL
Stopping background process MMON
License high water mark = 14
All dispatchers and shared servers shutdown
ALTER DATABASE CLOSE NORMAL
Sat Mar 02 11:19:33 2013
SMON: disabling tx recovery
SMON: disabling cache recovery
Sat Mar 02 11:19:33 2013
Shutting down archive processes
Archiving is disabled
Sat Mar 02 11:19:33 2013
ARCH shutting down
ARC3: Archival stopped
Sat Mar 02 11:19:33 2013
ARCH shutting down
ARC2: Archival stopped
Sat Mar 02 11:19:33 2013
ARCH shutting down
ARC1: Archival stopped
Sat Mar 02 11:19:33 2013
ARCH shutting down
ARC0: Archival stopped
Thread 1 closed at log sequence 6
Successful close of redo thread 1
Completed: ALTER DATABASE CLOSE NORMAL
ALTER DATABASE DISMOUNT
Shutting down archive processes
Archiving is disabled
Completed: ALTER DATABASE DISMOUNT
ARCH: Archival disabled due to shutdown: 1089
Shutting down archive processes
Archiving is disabled
Sat Mar 02 11:19:35 2013
Stopping background process VKTM
ARCH: Archival disabled due to shutdown: 1089
Shutting down archive processes
Archiving is disabled
Sat Mar 02 11:19:38 2013
Instance shutdown complete
 
The complete step by step startup “nomount -> mount -> open”
 
From front-end:
SQL>
SQL> startup nomount;
ORACLE instance started.
 
Total System Global Area  368263168 bytes
Fixed Size                 1345016 bytes
Variable Size            276826632 bytes
Database Buffers          83886080 bytes
Redo Buffers               6205440 bytes
SQL>
SQL>
SQL>
SQL> alter database mount;
 
Database altered.
 
SQL>
SQL>
SQL>
SQL> alter database open;
 
Database altered.
 
SQL>
 
From back-end:
Sat Mar 02 11:22:53 2013
Starting ORACLE instance (normal)
LICENSE_MAX_SESSION = 0
LICENSE_SESSIONS_WARNING = 0
Picked latch-free SCN scheme 2
Using LOG_ARCHIVE_DEST_1 parameter default value as USE_DB_RECOVERY_FILE_DEST
Autotune of undo retention is turned on.
IMODE=BR
ILAT =27
LICENSE_MAX_USERS = 0
SYS auditing is disabled
Starting up:
Oracle Database 11g Enterprise Edition Release 11.2.0.3.0 - Production
With the Partitioning, OLAP, Data Mining and Real Application Testing options.
ORACLE_HOME = /u01/app/oracle/database/11.2.0
System name:   Linux
Node name:     geetdb.dbinterest.local
Release:       2.6.18-164.el5xen
Version:       #1 SMP Thu Sep 3 02:41:56 EDT 2009
Machine:       i686
VM name:       Xen Version: 3.1 (PVM)
Using parameter settings in server-side spfile /u01/app/oracle/database/11.2.0/dbs/spfileGEETDB11G.ora
System parameters with non-default values:
  processes                = 150
  memory_target            = 352M
  control_files            = "/u01/app/oracle/oradata/GEETDB11G/control01.ctl"
  control_files            = "/u01/app/oracle/fast_recovery_area/GEETDB11G/control02.ctl"
  db_block_size            = 8192
  compatible               = "11.2.0.0.0"
  log_archive_format       = "%t_%s_%r.dbf"
  db_recovery_file_dest    = "/u01/app/oracle/fast_rec"
  db_recovery_file_dest_size= 4977M
  undo_tablespace          = "UNDOTBS1"
  remote_login_passwordfile= "EXCLUSIVE"
  db_domain                = ""
  dispatchers              = "(PROTOCOL=TCP) (SERVICE=GEETDB11GXDB)"
  audit_file_dest          = "/u01/app/oracle/admin/GEETDB11G/adump"
  audit_trail              = "DB"
  db_name                  = "GEETDB11G"
  open_cursors             = 300
  diagnostic_dest          = "/u01/app/oracle"
Sat Mar 02 11:22:56 2013
PMON started with pid=2, OS id=3130
Sat Mar 02 11:22:56 2013
PSP0 started with pid=3, OS id=3132
Sat Mar 02 11:22:57 2013
VKTM started with pid=4, OS id=3134 at elevated priority
VKTM running at (4)millisec precision with DBRM quantum (100)ms
Sat Mar 02 11:22:57 2013
GEN0 started with pid=5, OS id=3138
Sat Mar 02 11:22:57 2013
DIAG started with pid=6, OS id=3140
Sat Mar 02 11:22:57 2013
DBRM started with pid=7, OS id=3142
Sat Mar 02 11:22:57 2013
DIA0 started with pid=8, OS id=3144
Sat Mar 02 11:22:57 2013
MMAN started with pid=9, OS id=3146
Sat Mar 02 11:22:57 2013
DBW0 started with pid=10, OS id=3148
Sat Mar 02 11:22:57 2013
LGWR started with pid=11, OS id=3150
Sat Mar 02 11:22:57 2013
CKPT started with pid=12, OS id=3152
Sat Mar 02 11:22:57 2013
SMON started with pid=13, OS id=3154
Sat Mar 02 11:22:57 2013
RECO started with pid=14, OS id=3156
Sat Mar 02 11:22:57 2013
MMON started with pid=15, OS id=3158
starting up 1 dispatcher(s) for network address '(ADDRESS=(PARTIAL=YES)(PROTOCOL=TCP))'...
Sat Mar 02 11:22:57 2013
MMNL started with pid=16, OS id=3160
starting up 1 shared server(s) ...
ORACLE_BASE from environment = /u01/app/oracle
 
Sat Mar 02 11:24:08 2013
alter database mount
Sat Mar 02 11:24:12 2013
Successful mount of redo thread 1, with mount id 1602168472
Allocated 3981204 bytes in shared pool for flashback generation buffer
Starting background process RVWR
Sat Mar 02 11:24:13 2013
RVWR started with pid=20, OS id=3192
Database mounted in Exclusive Mode
Lost write protection disabled
Completed: alter database mount
 
Sat Mar 02 11:24:42 2013
alter database open
Sat Mar 02 11:24:42 2013
LGWR: STARTING ARCH PROCESSES
Sat Mar 02 11:24:42 2013
ARC0 started with pid=21, OS id=3194
ARC0: Archival started
LGWR: STARTING ARCH PROCESSES COMPLETE
ARC0: STARTING ARCH PROCESSES
Sat Mar 02 11:24:43 2013
ARC1 started with pid=22, OS id=3196
Thread 1 opened at log sequence 6
  Current log# 3 seq# 6 mem# 0: /u01/app/oracle/oradata/GEETDB11G/redo03.log
Successful open of redo thread 1
MTTR advisory is disabled because FAST_START_MTTR_TARGET is not set
Sat Mar 02 11:24:43 2013
SMON: enabling cache recovery
Sat Mar 02 11:24:43 2013
ARC2 started with pid=23, OS id=3198
ARC1: Archival started
ARC2: Archival started
ARC1: Becoming the 'no FAL' ARCH
ARC1: Becoming the 'no SRL' ARCH
Sat Mar 02 11:24:43 2013
ARC3 started with pid=24, OS id=3200
ARC2: Becoming the heartbeat ARCH
[3165] Successfully onlined Undo Tablespace 2.
Undo initialization finished serial:0 start:5971056 end:5971566 diff:510 (5 seconds)
Verifying file header compatibility for 11g tablespace encryption..
Verifying 11g file header compatibility for tablespace encryption completed
SMON: enabling tx recovery
Database Characterset is AL32UTF8
No Resource Manager plan active
ARC3: Archival started
ARC0: STARTING ARCH PROCESSES COMPLETE
replication_dependency_tracking turned off (no async multimaster replication found)
Starting background process QMNC
Sat Mar 02 11:24:47 2013
QMNC started with pid=25, OS id=3202
Completed: alter database open
Sat Mar 02 11:24:52 2013
db_recovery_file_dest_size of 4977 MB is 43.61% 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.
Sat Mar 02 11:24:52 2013
Starting background process CJQ0
Sat Mar 02 11:24:53 2013
CJQ0 started with pid=26, OS id=3216
Setting Resource Manager plan SCHEDULER[0x318E]:DEFAULT_MAINTENANCE_PLAN via scheduler window
Setting Resource Manager plan DEFAULT_MAINTENANCE_PLAN via parameter
Sat Mar 02 11:24:56 2013
Starting background process VKRM
Sat Mar 02 11:24:56 2013
VKRM started with pid=27, OS id=3219
 
Step by step shutdown “close -> dismount -> shutdown”
 
From front-end:
SQL>
SQL> alter database close;
 
Database altered.
 
SQL>
SQL>
SQL>
SQL> alter database dismount;
 
Database altered.
 
SQL>
SQL>
SQL>
SQL> shutdown immediate;
ORA-01507: database not mounted
 
ORACLE instance shut down.
SQL>
 
From back-end:
Sat Mar 02 11:29:32 2013
alter database close
Warning: ALTER DATABASE CLOSE is not a publicly supported command.
Sat Mar 02 11:29:32 2013
SMON: disabling tx recovery
Sat Mar 02 11:29:32 2013
Stopping background process CJQ0
Stopping background process QMNC
All dispatchers and shared servers shutdown
CLOSE: killing server sessions.
CLOSE: all sessions shutdown successfully.
SMON: disabling cache recovery
Sat Mar 02 11:29:34 2013
Shutting down archive processes
Archiving is disabled
Sat Mar 02 11:29:34 2013
ARCH shutting down
ARC3: Archival stopped
Sat Mar 02 11:29:34 2013
ARCH shutting down
ARC2: Archival stopped
Sat Mar 02 11:29:34 2013
ARCH shutting down
ARC1: Archival stopped
Sat Mar 02 11:29:34 2013
ARCH shutting down
ARC0: Archival stopped
Thread 1 closed at log sequence 6
Successful close of redo thread 1
Completed: alter database close
 
Sat Mar 02 11:30:15 2013
alter database dismount
Shutting down archive processes
Archiving is disabled
Sat Mar 02 11:30:15 2013
idle dispatcher 'D000' terminated, pid = (17, 1)
Completed: alter database dismount
 
Sat Mar 02 11:31:02 2013
Shutting down instance (immediate)
Shutting down instance: further logons disabled
Stopping background process MMNL
Stopping background process MMON
License high water mark = 3
All dispatchers and shared servers shutdown
ALTER DATABASE CLOSE NORMAL
ORA-1507 signalled during: ALTER DATABASE CLOSE NORMAL...
ARCH: Archival disabled due to shutdown: 1089
Shutting down archive processes
Archiving is disabled
Sat Mar 02 11:31:05 2013
Stopping background process VKTM
ARCH: Archival disabled due to shutdown: 1089
Shutting down archive processes
Archiving is disabled
Sat Mar 02 11:31:07 2013
Instance shutdown complete
 
Posted by at No comments:
Location: Asia
Subscribe to: Comments (Atom)