Impact of switching UNDO?
Hi All,
I want to drop a datafile from UNDO. I've read that I need to create a new UNDO then switch the old to the new UNDO. What is the impact to the current transactions if I switch the UNDO?
Are there any ways other than this to drop a datafile from UNDO?
Make sure that the status of the undo segments in the old undo tablespace are offline. The segments in the new tablespace may also show offline.
SQL>select owner, segment_name, tablespace_name, status from dba_rollback_segs;
Once all the segments in the old undo tablespace are offline, you can now drop the old undo tablespace:
SQL>drop tablespace UNDOTBS_OLD including contents and datafiles;
Tablespace dropped.
Edit the init parameter.
Thanks,
Similar Messages
-
Is it OK to Switching Undo Tablespaces without DB stop ?
We use Oracle11g R2.
I read Oracle Doc and It looks OK.
But, how could I make sure UNDO tablespace mode(ONLINE,PENDING OFFLINE) ?
Switching Undo Tablespaces
You can switch from using one undo tablespace to another. Because the UNDO_TABLESPACE initialization parameter is a dynamic parameter, the ALTER SYSTEM SET statement can be used to assign a new undo tablespace.
The following statement switches to a new undo tablespace:
ALTER SYSTEM SET UNDO_TABLESPACE = undotbs_02;
Assuming undotbs_01 is the current undo tablespace, after this command successfully executes, the instance uses undotbs_02 in place of undotbs_01 as its undo tablespace.
If any of the following conditions exist for the tablespace being switched to, an error is reported and no switching occurs:
The tablespace does not exist
The tablespace is not an undo tablespace
The tablespace is already being used by another instance (in an Oracle RAC environment only)
The database is online while the switch operation is performed, and user transactions can be executed while this command is being executed. When the switch operation completes successfully, all transactions started after the switch operation began are assigned to transaction tables in the new undo tablespace.
The switch operation does not wait for transactions in the old undo tablespace to commit. If there are any pending transactions in the old undo tablespace, the old undo tablespace enters into a PENDING OFFLINE mode (status). In this mode, existing transactions can continue to execute, but undo records for new user transactions cannot be stored in this undo tablespace.
An undo tablespace can exist in this PENDING OFFLINE mode, even after the switch operation completes successfully. A PENDING OFFLINE undo tablespace cannot be used by another instance, nor can it be dropped. Eventually, after all active transactions have committed, the undo tablespace automatically goes from the PENDING OFFLINE mode to the OFFLINE mode. From then on, the undo tablespace is available for other instances (in an Oracle Real Application Cluster environment).After you switch the UNDO_TABLESPACE parameter to the new tablespace, at the minimum, you have to wait for active transactions to complete (commit/rollback) before you can take the old Undo Tablespace offline. Note that if you take the old Undo Tablespace offline too quickly, you may prevent long running queries from reading from the old Undo Tablespace and may cause them to error with ORA-01555. So you need to wait a reasonable time (e.g look at MAXQUERYLEN in V$UNDOSTAT) before you take the old Undo Tablespace offline.
Hemant K Chitale -
Dear all,
I have created a new undo tablespace named undotbs2, How can i switch all the session use the undotbs2?
Many sessions are running and using the old undo tablespace named undotbs1.user7244870 wrote:
CKPT wrote:
Sb has already mentioned links how to manage undo..
For more reference check this below links.
http://oracleflash.com/32/Change-or-switch-undo-tablespace-in-Oracle-database.html
http://download.oracle.com/docs/cd/B19306_01/server.102/b14231/undo.htm#BABGJBJH
I can't open the link.
http://oracleflash.com/32/Change-or-switch-undo-tablespace-in-Oracle-database.html
Is there a specific reason that you are not willing to read the official doc link?
http://download.oracle.com/docs/cd/E11882_01/server.112/e16508/logical.htm#CNCPT1079
Aman.... -
I want to swithch current undo tablespace to another current undo tablespace,how can i check whether all the sessions have finished and commited in current table space?
I don't think you really need to check because Oracle will handle the switch from old to new undo tablespace the following way:
>
The switch operation does not wait for transactions in the old undo tablespace to commit. If there are any pending transactions in the old undo tablespace, the old undo tablespace enters into a PENDING OFFLINE mode (status). In this mode, existing transactions can continue to execute, but undo records for new user transactions cannot be stored in this undo tablespace.
An undo tablespace can exist in this PENDING OFFLINE mode, even after the switch operation completes successfully. A PENDING OFFLINE undo tablespace cannot be used by another instance, nor can it be dropped. Eventually, after all active transactions have committed, the undo tablespace automatically goes from the PENDING OFFLINE mode to the OFFLINE mode. From then on, the undo tablespace is available for other instances (in an Oracle Real Application Cluster environment). -
Hello,
I created a new undo tablespace and have successfully switched the database to use the new undo tablespace. Now I want to drop the old undo tablespace.
What is the process for me to drop the old undo tablespace?
Is it drop tablespace undotabsOLD; ? What are the 'gotachas' I should be aware before drop a tablespace that was unsed as an undo tablespace? Thank you in advance.undo_retention is not a 'gotcha' in this case,
according the Oracle document I posted earlier,
the undo tablespace is ready to be dropped when all active transactions gone. It will not wait for undo_retention
see following examples,
--Make a bigger retention just in case
SQL> show parameter undo
NAME TYPE VALUE
undo_management string AUTO
undo_retention integer 3600
undo_tablespace string UNDOTBS_01
-- Now create a new undo
SQL> CREATE UNDO TABLESPACE undotbs_02
2 DATAFILE '/u02/oradata/undo/undo2.dbf' SIZE 100M REUSE AUTOEXTEND ON
3 /
Tablespace created.
-- Before we switch make an uncommited transaction on other session
-- Then
SQL> ALTER SYSTEM SET UNDO_TABLESPACE = undotbs_02;
System altered.
SQL> show parameter undo
NAME TYPE VALUE
undo_management string AUTO
undo_retention integer 3600
undo_tablespace string UNDOTBS_02
-- Try to drop UNDOTBS_01
SQL> drop tablespace UNDOTBS_01 including contents and datafiles
2 /
drop tablespace UNDOTBS_01 including contents and datafiles
ERROR at line 1:
ORA-30013: undo tablespace 'UNDOTBS_01' is currently in use
-- Run a query to list PENDING OFFLINE rollback segments
SQL> SELECT NAME, XACTS "ACTIVE TRANSACTIONS"
2 FROM V$ROLLNAME, V$ROLLSTAT
3 WHERE STATUS = 'PENDING OFFLINE'
4 AND V$ROLLNAME.USN = V$ROLLSTAT.USN;
NAME ACTIVE TRANSACTIONS
_SYSSMU10$ 1
-- Now commit on other session
SQL> select sysdate from dual
2 /
SYSDATE
2007-06-21 03:49:49
SQL> SELECT NAME, XACTS "ACTIVE TRANSACTIONS"
2 FROM V$ROLLNAME, V$ROLLSTAT
3 WHERE STATUS = 'PENDING OFFLINE'
4 AND V$ROLLNAME.USN = V$ROLLSTAT.USN;
NAME ACTIVE TRANSACTIONS
_SYSSMU10$ 0
-- Wait a few seconds
SQL> select sysdate from dual;
SYSDATE
2007-06-21 03:50:00
SQL> SELECT NAME, XACTS "ACTIVE TRANSACTIONS"
2 FROM V$ROLLNAME, V$ROLLSTAT
3 WHERE STATUS = 'PENDING OFFLINE'
4 AND V$ROLLNAME.USN = V$ROLLSTAT.USN;
no rows selected
-- NOW, drop the tablespace
SQL> drop tablespace UNDOTBS_01 including contents and datafiles;
Tablespace dropped.
Done -
Impacts for switching from Extended Classic to Classic in production
Hi,
Has anyone involved project that customer has switched from Extended Classic to Classic in production system?
SRM 4.0 is live in Extended Classic now.
Customer is going to upgrade and switch their production system to SRM 7.0 Classic.
Main process is
PS -> MM PR -> SRM Sourcing -> SRM PO (Extended) -> SUS PO -> SUS PO Response
GR, Service Entry and Invoice are handled in ERP
I see an issue if we switch SRM-SUS to MM-SUS, SUS PO is created before switch and PO Response is created after switch.
Do you have any lessens and learned topics for switching Extended Classic to Classic? Which documents have to be take care?
Regards,
MasaI'm also interested in the same question. We plan on going from 5 Extended Classic to 7.1 Classic.
-
We are noticing some of these snapshot too old errors 01555 errors and we are not making use of any of the flashback functionality so I believe we are only interested in the undo table keeping the undo data while the transaction itself is active to ensure read consistency.
Previously we had undo_retention set to 10800 (3 hours) and I am thinking I should shrink this so that we only keep data as long as the transaction is active. If I set the undo retention length to a value like 300 (5 minutes) and a transaction takes 20 minutes am I going to get snapshot too old errors?
I am hoping the behavior is to keep the transaction data in the undo segment as long as the transaction is active for a minimum of undo_retention time and it would keep making use of space until it runs out of space that is not being used by some other transaction and not being held because of the 5 minutes retention. Is this how it will behave or after the 5 minutes will other transactions be able to overwrite this undo data causing an error even if there is other free space?
Some of the documentation seemed to say the undo_retention is a minimum recommendation to oracle. So if I don't care about flashback at all would a setting like 1 be reasonable assuming it would keep stuff as long as the transaction lasts +1 second(suggesting 1 since 0 means use the default of 900 aka 15 minutes)? I saw some other documentation suggesting setting it to the value of your longest transaction but I surely don't want to keep data from shorter transactions as long as my longest transaction as that would require a much larger undo tablespace so I am trying to figure out the most efficient setting to ensure consistency while being as space efficient as possible.
Thanks,
JaredThank you for all the replys on this thread those plus some stuff I have read in metalink have been very helpful. Have some follow up related questions.
From what I have read when a block is modified it goes into the undo in one of the segments and has an associated SCN number for each change.
1. If one DB connection does a series of updates to a given block and then disconnects (assume each update autocommits) and then the process is restarted and does more updates to the same block would it re-use the existing undo segment? (assuming that no select statements reference this block and cause it to be flushed) Does a new transaction on a given block imply a segment switch is a new select intersecting with a datablock the only thing that would cause it to change segments?
2. In the same scenario as above with a select happening between the two passes I am assuming that the select would cause it to flush the block (update the actual data) and that the second pass of updates on the same block would do the updates in a different undo segment? Does having a higher retention setting make it more likely to keep rotating segments as opposed to overwriting a previous one? In other words if I have my retention set to some very high amount of time like 10 days would it rotate all of the segments for that block before overwriting the first change?
My application currently has one process that does large queries that could last 5 hours or so at worst(all read only). And another process that does only new inserts.
Trying to figure out the exact behavior of how the undo retention manages switching undo segments to determine what is causing our problems. I have noticed on 10g2 that the number of undo segments is 10 and on 9.2.0.5 it was more like 108 or so and it seems like 10 is more likely to get 1555 errors and I am wondering if this is because it is more likely to cycle all segments and start overwriting blocks that are needed for a long running queries consistency.
Thanks,
Jared -
Hi there,
I have a Datawarehouse DB , with two UNDO tablespaces,Last friday we switched UNDO_TABLESPACE to UNDO01 and UNDO02 is not active.While querying DBA_UNDO_EXTENTS , status of all extents in UNDO02 is marked as EXPIRED but there is no free space left in UNDO02 tablespace.
Now the qustion is
1. why Oracle is not releasing EXPIRED extents from the NON-ACTIVE Undo tablespace?
2. AS per Oracle Documentation "Switching Undo Tablespaces" - "The switch operation does not wait for transactions in the old undo tablespace to commit. If there are any pending transactions in the old undo tablespace, the old undo tablespace enters into a PENDING OFFLINE mode (status). In this mode, existing transactions can continue to execute, but undo records for new user transactions cannot be stored in this undo tablespace" ---- But STATUS column in DBA_TABLESPACES in my DB showing both Tablespaces are "ONLINE",
Any thoughts????
Thanks in advanceSQL> select segment_name, owner, tablespace_name,status from dba_rollback_segs;
SEGMENT_NAME OWNER TABLESPACE_NAME STATUS
SYSTEM SYS SYSTEM ONLINE
SYSROL SYS SYSTEM OFFLINE
_SYSSMU2$ PUBLIC UNDO1 ONLINE
_SYSSMU3$ PUBLIC UNDO1 ONLINE
_SYSSMU4$ PUBLIC UNDO1 ONLINE
_SYSSMU5$ PUBLIC UNDO1 ONLINE
_SYSSMU6$ PUBLIC UNDO1 ONLINE
_SYSSMU7$ PUBLIC UNDO1 ONLINE
_SYSSMU8$ PUBLIC UNDO1 ONLINE
_SYSSMU9$ PUBLIC UNDO1 ONLINE
_SYSSMU10$ PUBLIC UNDO1 ONLINE
_SYSSMU11$ PUBLIC UNDO1 ONLINE
_SYSSMU12$ PUBLIC UNDO1 ONLINE
_SYSSMU13$ PUBLIC UNDO1 ONLINE
_SYSSMU14$ PUBLIC UNDO1 ONLINE
_SYSSMU15$ PUBLIC UNDO1 ONLINE
_SYSSMU16$ PUBLIC UNDO1 ONLINE
_SYSSMU17$ PUBLIC UNDO1 ONLINE
_SYSSMU18$ PUBLIC UNDO2 OFFLINE
_SYSSMU19$ PUBLIC UNDO2 OFFLINE
_SYSSMU20$ PUBLIC UNDO2 OFFLINE
_SYSSMU21$ PUBLIC UNDO2 OFFLINE
_SYSSMU22$ PUBLIC UNDO1 ONLINE
_SYSSMU23$ PUBLIC UNDO1 OFFLINE
_SYSSMU24$ PUBLIC UNDO1 OFFLINE
_SYSSMU25$ PUBLIC UNDO1 OFFLINE
_SYSSMU26$ PUBLIC UNDO1 OFFLINE
_SYSSMU27$ PUBLIC UNDO1 OFFLINE
_SYSSMU28$ PUBLIC UNDO2 OFFLINE
_SYSSMU29$ PUBLIC UNDO2 OFFLINE
_SYSSMU30$ PUBLIC UNDO2 OFFLINE
_SYSSMU31$ PUBLIC UNDO2 OFFLINE
_SYSSMU32$ PUBLIC UNDO2 OFFLINE
_SYSSMU33$ PUBLIC UNDO2 OFFLINE
34 rows selected.
SQL> show parameter UNDO
NAME TYPE VALUE
undo_management string AUTO
undo_retention integer 40000
undo_suppress_errors boolean FALSE
undo_tablespace string UNDO1
SQL>
Thanks -
Active Table Logging T000 performance impact
Hi fellow SAP experts,
I need some advice on system performance impact when switching on Table Logging for T000 - configuration in production please?
We have decided to turn on Table Logging for auditing purposes, only allowing developer config in production following a volume of evidence being supplied.
I need to know how much this activation is going to impact the performance of the companies production environments, how much storage, memory, performance, etc. this function is going to consume and how much of the above consumables I need to cater for now and in the future?
We have a Dual Track environment, BAU want to switch on Table Logging for fix on fail, I want to swich it on for Project deliveries.
Please advise, with referencing if possible?
Thank you kindly
PaulHi Paul,
There has been a constant debate whether table logging affects the System performance, especially in Produciton environment. Please see my comments below :
1) To turn on logging for table T000, you will have to activate the parameter rec/client, with values for one client or all the clients in the System depending on your requirement.
2) This parameter setting will not only log changes to T000, but also for over 28000 tables.
3) But these are customizing tables which usually contain a relatively small amount of data which is changed occasionally.
4) After activating, if you suddenly find performance issues, you can check which tables are causing issues via transaction SCU3.
5) You can go to transaction SE13 and deactivate logging for a table, if you find too many entries for any particular table in SCU3.
So, logging tables doesn't necessarily impact performance. Hope this helps. Please refer to SAP Note-608835 related to this.
Best Regards,
Savitha -
Which one should I drop - undo or rollback?
I have both undo tablespace and rollback tablespace. Is it possible I can drop any one of them?
Below is the free space in each. By looking at these figures, the undotbs1 tablespace can be dropped. Howver I neeed to know if there is any risk in dropping it ...and how to take precaution sagaint any risks?
tablespacename || free space
RBS || 40.91%
UNDOTBS1 || 99.87%
ThanksHi,
Parameters as you requested.
NUM NAME TYPE VALUE ISDEFAULT ISSES_MODIFIABLE ISSYS_MODIFIABLE ISMODIFIED ISADJUSTED DESCRIPTION UPDATE_COMMENT
2 tracefile_identifier 2 TRUE TRUE FALSE FALSE FALSE trace file custom identifier
18 processes 3 150 FALSE FALSE FALSE FALSE FALSE user processes
20 sessions 3 170 TRUE FALSE FALSE FALSE FALSE user and system sessions
21 timed_statistics 1 TRUE FALSE TRUE IMMEDIATE FALSE FALSE maintain internal timing statistics
22 timed_os_statistics 3 0 TRUE TRUE IMMEDIATE FALSE FALSE internal os statistic gathering interval in seconds
23 resource_limit 1 FALSE TRUE FALSE IMMEDIATE FALSE FALSE master switch for resource limit
24 license_max_sessions 3 0 TRUE FALSE IMMEDIATE FALSE FALSE maximum number of non-system user sessions allowed
25 license_sessions_warning 3 0 TRUE FALSE IMMEDIATE FALSE FALSE warning level for number of non-system user sessions
33 cpu_count 3 2 TRUE FALSE FALSE FALSE FALSE initial number of cpu's for this instance
36 instance_groups 2 TRUE FALSE FALSE FALSE FALSE list of instance group names
37 event 2 TRUE FALSE FALSE FALSE FALSE debug event control - default null string
44 shared_pool_size 6 50331648 FALSE FALSE IMMEDIATE FALSE FALSE size in bytes of shared pool
45 sga_max_size 6 537993848 FALSE FALSE FALSE FALSE FALSE max total SGA size internally adjusted
49 shared_pool_reserved_size 6 2516582 TRUE FALSE FALSE FALSE FALSE size in bytes of reserved area of shared pool
52 large_pool_size 6 8388608 FALSE FALSE IMMEDIATE FALSE FALSE size in bytes of the large allocation pool
54 java_pool_size 6 41943040 FALSE FALSE FALSE FALSE FALSE size in bytes of the Java pool
55 java_soft_sessionspace_limit 3 0 TRUE FALSE FALSE FALSE FALSE warning limit on size in bytes of a Java sessionspace
56 java_max_sessionspace_size 3 0 TRUE FALSE FALSE FALSE FALSE max allowed size in bytes of a Java sessionspace
57 pre_page_sga 1 FALSE TRUE FALSE FALSE FALSE FALSE pre-page sga for process
58 shared_memory_address 3 0 TRUE FALSE FALSE FALSE FALSE SGA starting address (low order 32-bits on 64-bit platforms)
59 hi_shared_memory_address 3 0 TRUE FALSE FALSE FALSE FALSE SGA starting address (high order 32-bits on 64-bit platforms)
60 use_indirect_data_buffers 1 FALSE TRUE FALSE FALSE FALSE FALSE Enable indirect data buffers (very large SGA on 32-bit platforms
62 lock_sga 1 FALSE TRUE FALSE FALSE FALSE FALSE Lock entire SGA in physical memory
77 spfile 2 %ORACLE_HOME%\DATABASE\SPFILE%ORACLE_SID%.ORA TRUE FALSE FALSE FALSE FALSE server parameter file
81 lock_name_space 2 TRUE FALSE FALSE FALSE FALSE lock name space used for generating lock names for standby/clone
83 enqueue_resources 3 968 TRUE FALSE FALSE FALSE FALSE resources for enqueues
88 trace_enabled 1 TRUE TRUE FALSE IMMEDIATE FALSE FALSE enable KST tracing
96 nls_language 2 AMERICAN TRUE TRUE FALSE FALSE FALSE NLS language name
97 nls_territory 2 AMERICA TRUE TRUE FALSE FALSE FALSE NLS territory name
98 nls_sort 2 TRUE TRUE FALSE FALSE FALSE NLS linguistic definition name
99 nls_date_language 2 TRUE TRUE FALSE FALSE FALSE NLS date language name
100 nls_date_format 2 TRUE TRUE FALSE FALSE FALSE NLS Oracle date format
101 nls_currency 2 TRUE TRUE FALSE FALSE FALSE NLS local currency symbol
102 nls_numeric_characters 2 TRUE TRUE FALSE FALSE FALSE NLS numeric characters
103 nls_iso_currency 2 TRUE TRUE FALSE FALSE FALSE NLS ISO currency territory name
104 nls_calendar 2 TRUE TRUE FALSE FALSE FALSE NLS calendar system name
105 nls_time_format 2 TRUE TRUE FALSE FALSE FALSE time format
106 nls_timestamp_format 2 TRUE TRUE FALSE FALSE FALSE time stamp format
107 nls_time_tz_format 2 TRUE TRUE FALSE FALSE FALSE time with timezone format
108 nls_timestamp_tz_format 2 TRUE TRUE FALSE FALSE FALSE timestampe with timezone format
109 nls_dual_currency 2 TRUE TRUE FALSE FALSE FALSE Dual currency symbol
110 nls_comp 2 TRUE TRUE FALSE FALSE FALSE NLS comparison
111 nls_length_semantics 2 BYTE TRUE TRUE IMMEDIATE FALSE FALSE create columns using byte or char semantics by default
112 nls_nchar_conv_excp 2 FALSE TRUE TRUE IMMEDIATE FALSE FALSE NLS raise an exception instead of allowing implicit conversion
120 filesystemio_options 2 TRUE TRUE IMMEDIATE FALSE FALSE IO operations on filesystem files
124 disk_asynch_io 1 TRUE TRUE FALSE FALSE FALSE FALSE Use asynch I/O for random access devices
125 tape_asynch_io 1 TRUE TRUE FALSE FALSE FALSE FALSE Use asynch I/O requests for tape devices
127 dbwr_io_slaves 3 0 TRUE FALSE FALSE FALSE FALSE DBWR I/O slaves
131 backup_tape_io_slaves 1 FALSE TRUE FALSE DEFERRED FALSE FALSE BACKUP Tape I/O slaves
135 resource_manager_plan 2 TRUE FALSE IMMEDIATE FALSE FALSE resource mgr top plan
144 cluster_interconnects 2 TRUE FALSE FALSE FALSE FALSE interconnects for RAC use
147 file_mapping 1 FALSE TRUE FALSE IMMEDIATE FALSE FALSE enable file mapping
165 active_instance_count 3 TRUE FALSE FALSE FALSE FALSE number of active instances in the cluster database
228 control_files 2 E:\ORACLE\ORADATA\ora92dbd\CONTROL01.CTL, E:\ORACLE\ORADATA\ora92dbd\CONTROL02.CTL, E:\ORACLE\ORADATA\ora92dbd\CONTROL03.CTL FALSE FALSE FALSE FALSE FALSE control file names list
230 db_file_name_convert 2 TRUE FALSE FALSE FALSE FALSE datafile name convert patterns and strings for standby/clone db
231 log_file_name_convert 2 TRUE FALSE FALSE FALSE FALSE logfile name convert patterns and strings for standby/clone db
232 db_block_buffers 3 0 TRUE FALSE FALSE FALSE FALSE Number of database blocks cached in memory
236 db_block_checksum 1 TRUE TRUE FALSE IMMEDIATE FALSE FALSE store checksum in db blocks and check during reads
237 db_block_size 3 8192 FALSE FALSE FALSE FALSE FALSE Size of database block in bytes
244 db_writer_processes 3 1 TRUE FALSE FALSE FALSE FALSE number of background database writer processes to start
258 db_keep_cache_size 6 0 TRUE FALSE IMMEDIATE FALSE FALSE Size of KEEP buffer pool for standard block size buffers
259 db_recycle_cache_size 6 0 TRUE FALSE IMMEDIATE FALSE FALSE Size of RECYCLE buffer pool for standard block size buffers
260 db_2k_cache_size 6 0 TRUE FALSE IMMEDIATE FALSE FALSE Size of cache for 2K buffers
261 db_4k_cache_size 6 0 TRUE FALSE IMMEDIATE FALSE FALSE Size of cache for 4K buffers
262 db_8k_cache_size 6 0 TRUE FALSE IMMEDIATE FALSE FALSE Size of cache for 8K buffers
263 db_16k_cache_size 6 0 TRUE FALSE IMMEDIATE FALSE FALSE Size of cache for 16K buffers
264 db_32k_cache_size 6 0 TRUE FALSE IMMEDIATE FALSE FALSE Size of cache for 32K buffers
265 db_cache_size 6 109051904 FALSE FALSE IMMEDIATE FALSE FALSE Size of DEFAULT buffer pool for standard block size buffers
267 buffer_pool_keep 2 TRUE FALSE FALSE FALSE FALSE Number of database blocks/latches in keep buffer pool
268 buffer_pool_recycle 2 TRUE FALSE FALSE FALSE FALSE Number of database blocks/latches in recycle buffer pool
295 db_cache_advice 2 ON TRUE FALSE IMMEDIATE FALSE FALSE Buffer cache sizing advisory
304 max_commit_propagation_delay 3 700 TRUE FALSE FALSE FALSE FALSE Max age of new snapshot in .01 seconds
306 compatible 2 9.2.0.0.0 FALSE FALSE FALSE FALSE FALSE Database will be completely compatible with this software versio
312 remote_archive_enable 2 true TRUE FALSE FALSE FALSE FALSE remote archival enable setting
313 log_archive_start 1 TRUE FALSE FALSE FALSE FALSE FALSE start archival process on SGA initialization
317 log_archive_dest 2 TRUE FALSE IMMEDIATE FALSE FALSE archival destination text string
318 log_archive_duplex_dest 2 TRUE FALSE IMMEDIATE FALSE FALSE duplex archival destination text string
319 log_archive_dest_1 2 location=F:\ORACLE\ARCHIVE FALSE TRUE IMMEDIATE FALSE FALSE archival destination #1 text string
320 log_archive_dest_2 2 TRUE TRUE IMMEDIATE FALSE FALSE archival destination #2 text string
321 log_archive_dest_3 2 TRUE TRUE IMMEDIATE FALSE FALSE archival destination #3 text string
322 log_archive_dest_4 2 TRUE TRUE IMMEDIATE FALSE FALSE archival destination #4 text string
323 log_archive_dest_5 2 TRUE TRUE IMMEDIATE FALSE FALSE archival destination #5 text string
324 log_archive_dest_6 2 TRUE TRUE IMMEDIATE FALSE FALSE archival destination #6 text string
325 log_archive_dest_7 2 TRUE TRUE IMMEDIATE FALSE FALSE archival destination #7 text string
326 log_archive_dest_8 2 TRUE TRUE IMMEDIATE FALSE FALSE archival destination #8 text string
327 log_archive_dest_9 2 TRUE TRUE IMMEDIATE FALSE FALSE archival destination #9 text string
328 log_archive_dest_10 2 TRUE TRUE IMMEDIATE FALSE FALSE archival destination #10 text string
329 log_archive_dest_state_1 2 enable TRUE TRUE IMMEDIATE FALSE FALSE archival destination #1 state text string
330 log_archive_dest_state_2 2 enable TRUE TRUE IMMEDIATE FALSE FALSE archival destination #2 state text string
331 log_archive_dest_state_3 2 enable TRUE TRUE IMMEDIATE FALSE FALSE archival destination #3 state text string
332 log_archive_dest_state_4 2 enable TRUE TRUE IMMEDIATE FALSE FALSE archival destination #4 state text string
333 log_archive_dest_state_5 2 enable TRUE TRUE IMMEDIATE FALSE FALSE archival destination #5 state text string
334 log_archive_dest_state_6 2 enable TRUE TRUE IMMEDIATE FALSE FALSE archival destination #6 state text string
335 log_archive_dest_state_7 2 enable TRUE TRUE IMMEDIATE FALSE FALSE archival destination #7 state text string
336 log_archive_dest_state_8 2 enable TRUE TRUE IMMEDIATE FALSE FALSE archival destination #8 state text string
337 log_archive_dest_state_9 2 enable TRUE TRUE IMMEDIATE FALSE FALSE archival destination #9 state text string
338 log_archive_dest_state_10 2 enable TRUE TRUE IMMEDIATE FALSE FALSE archival destination #10 state text string
339 log_archive_max_processes 3 2 TRUE FALSE IMMEDIATE FALSE FALSE maximum number of active ARCH processes
342 log_archive_min_succeed_dest 3 1 TRUE TRUE IMMEDIATE FALSE FALSE minimum number of archive destinations that must succeed
343 standby_archive_dest 2 %ORACLE_HOME%\RDBMS TRUE FALSE IMMEDIATE FALSE FALSE standby database archivelog destination text string
344 log_archive_trace 3 0 TRUE FALSE IMMEDIATE FALSE FALSE Establish archivelog operation tracing level
345 fal_server 2 TRUE FALSE IMMEDIATE FALSE FALSE FAL server list
346 fal_client 2 TRUE FALSE IMMEDIATE FALSE FALSE FAL client
347 log_archive_format 2 ARC%S.%T TRUE FALSE FALSE FALSE FALSE archival destination format
355 log_buffer 3 524288 TRUE FALSE FALSE FALSE FALSE redo circular buffer size
357 log_checkpoint_interval 3 0 TRUE FALSE IMMEDIATE FALSE FALSE # redo blocks checkpoint threshold
358 log_checkpoint_timeout 3 1800 TRUE FALSE IMMEDIATE FALSE FALSE Maximum time interval between checkpoints in seconds
360 archive_lag_target 3 0 TRUE FALSE IMMEDIATE FALSE FALSE Maximum number of seconds of redos the standby could lose
365 log_parallelism 3 1 TRUE FALSE FALSE FALSE FALSE Number of log buffer strands
367 db_files 3 200 TRUE FALSE FALSE FALSE FALSE max allowable # db files
368 db_file_multiblock_read_count 3 16 FALSE TRUE IMMEDIATE FALSE FALSE db block to be read each IO
370 read_only_open_delayed 1 FALSE TRUE FALSE FALSE FALSE FALSE if TRUE delay opening of read only files until first access
371 cluster_database 1 FALSE FALSE FALSE FALSE FALSE FALSE if TRUE startup in cluster database mode
372 parallel_server 1 FALSE TRUE FALSE FALSE FALSE FALSE if TRUE startup in parallel server mode
373 parallel_server_instances 3 1 TRUE FALSE FALSE FALSE FALSE number of instances to use for sizing OPS SGA structures
374 cluster_database_instances 3 1 TRUE FALSE FALSE FALSE FALSE number of instances to use for sizing cluster db SGA structures
376 db_create_file_dest 2 TRUE TRUE IMMEDIATE FALSE FALSE default database location
377 db_create_online_log_dest_1 2 TRUE TRUE IMMEDIATE FALSE FALSE online log/controlfile destination #1
378 db_create_online_log_dest_2 2 TRUE TRUE IMMEDIATE FALSE FALSE online log/controlfile destination #2
379 db_create_online_log_dest_3 2 TRUE TRUE IMMEDIATE FALSE FALSE online log/controlfile destination #3
380 db_create_online_log_dest_4 2 TRUE TRUE IMMEDIATE FALSE FALSE online log/controlfile destination #4
381 db_create_online_log_dest_5 2 TRUE TRUE IMMEDIATE FALSE FALSE online log/controlfile destination #5
382 standby_file_management 2 MANUAL TRUE FALSE IMMEDIATE FALSE FALSE if auto then files are created/dropped automatically on standby
391 gc_files_to_locks 2 TRUE FALSE FALSE FALSE FALSE mapping between file numbers and global cache locks (DFS)
414 thread 3 0 TRUE FALSE FALSE FALSE FALSE Redo thread to mount
417 fast_start_io_target 3 0 TRUE FALSE IMMEDIATE FALSE FALSE Upper bound on recovery reads
418 fast_start_mttr_target 3 300 FALSE FALSE IMMEDIATE FALSE FALSE MTTR target of forward crash recovery in seconds
423 log_checkpoints_to_alert 1 FALSE TRUE FALSE IMMEDIATE FALSE FALSE log checkpoint begin/end to alert file
424 recovery_parallelism 3 0 TRUE FALSE FALSE FALSE FALSE number of server processes to use for parallel recovery
425 control_file_record_keep_time 3 7 TRUE FALSE IMMEDIATE FALSE FALSE control file record keep time in days
426 logmnr_max_persistent_sessions 3 1 TRUE FALSE FALSE FALSE FALSE maximum number of threads to mine
430 dml_locks 3 748 TRUE FALSE FALSE FALSE FALSE dml locks - one for each table modified in a transaction
431 row_locking 2 always TRUE FALSE FALSE FALSE FALSE row-locking
432 serializable 1 FALSE TRUE FALSE FALSE FALSE FALSE serializable
433 replication_dependency_tracking 1 TRUE TRUE FALSE FALSE FALSE FALSE tracking dependency for Replication parallel propagation
436 instance_number 3 0 TRUE FALSE FALSE FALSE FALSE instance number
443 transactions 3 187 TRUE FALSE FALSE FALSE FALSE max. number of concurrent active transactions
444 transactions_per_rollback_segment 3 5 TRUE FALSE FALSE FALSE FALSE number of active transactions per rollback segment
445 max_rollback_segments 3 37 TRUE FALSE FALSE FALSE FALSE max. number of rollback segments in SGA cache
447 rollback_segments 2 TRUE FALSE FALSE FALSE FALSE undo segment list
452 transaction_auditing 1 TRUE TRUE FALSE DEFERRED FALSE FALSE transaction auditing records generated in the redo log
455 undo_management 2 AUTO FALSE FALSE FALSE FALSE FALSE instance runs in SMU mode if TRUE, else in RBU mode
456 undo_tablespace 2 UNDOTBS1 FALSE FALSE IMMEDIATE FALSE FALSE use/switch undo tablespace
460 undo_suppress_errors 1 FALSE TRUE TRUE IMMEDIATE FALSE FALSE Suppress RBU errors in SMU mode
465 undo_retention 3 10800 FALSE FALSE IMMEDIATE FALSE FALSE undo retention in seconds
469 fast_start_parallel_rollback 2 LOW TRUE FALSE IMMEDIATE FALSE FALSE max number of parallel recovery slaves that may be used
471 db_block_checking 1 FALSE TRUE TRUE IMMEDIATE FALSE FALSE data and index block checking
487 os_roles 1 FALSE TRUE FALSE FALSE FALSE FALSE retrieve roles from the operating system
488 rdbms_server_dn 2 TRUE FALSE FALSE FALSE FALSE RDBMS's Distinguished Name
489 max_enabled_roles 3 100 FALSE FALSE FALSE FALSE FALSE max number of roles a user can have enabled
490 remote_os_authent 1 FALSE TRUE FALSE FALSE FALSE FALSE allow non-secure remote clients to use auto-logon accounts
491 remote_os_roles 1 FALSE TRUE FALSE FALSE FALSE FALSE allow non-secure remote clients to use os roles
492 O7_DICTIONARY_ACCESSIBILITY 1 FALSE TRUE FALSE FALSE FALSE FALSE Version 7 Dictionary Accessibility Support
494 remote_login_passwordfile 2 EXCLUSIVE FALSE FALSE FALSE FALSE FALSE password file usage parameter
495 dblink_encrypt_login 1 FALSE TRUE FALSE FALSE FALSE FALSE enforce password for distributed login always be encrypted
496 license_max_users 3 0 TRUE FALSE IMMEDIATE FALSE FALSE maximum number of named users that can be created in the databas
498 global_context_pool_size 2 TRUE FALSE FALSE FALSE FALSE Global Application Context Pool Size in Bytes
500 audit_sys_operations 1 FALSE TRUE FALSE FALSE FALSE FALSE enable sys auditing
501 db_domain 2 govnet.local FALSE FALSE FALSE FALSE FALSE directory part of global database name stored with CREATE DATABA
502 global_names 1 TRUE FALSE TRUE IMMEDIATE FALSE FALSE enforce that database links have same name as remote database
503 distributed_lock_timeout 3 60 TRUE FALSE FALSE FALSE FALSE number of seconds a distributed transaction waits for a lock
505 commit_point_strength 3 1 TRUE FALSE FALSE FALSE FALSE Bias this node has toward not preparing in a two-phase commit
506 instance_name 2 ora92dbd FALSE FALSE FALSE FALSE FALSE instance name supported by the instance
507 service_names 2 ora92dbd.govnet.local TRUE FALSE IMMEDIATE FALSE FALSE service names supported by the instance
508 dispatchers 2 (PROTOCOL=TCP) (SERVICE=ora92dbdXDB) FALSE FALSE IMMEDIATE FALSE FALSE specifications of dispatchers
509 mts_dispatchers 2 (PROTOCOL=TCP) (SERVICE=ora92dbdXDB) TRUE FALSE IMMEDIATE FALSE FALSE specifications of dispatchers
510 shared_servers 3 1 TRUE FALSE IMMEDIATE FALSE FALSE number of shared servers to start up
511 mts_servers 3 1 TRUE FALSE IMMEDIATE FALSE FALSE number of shared servers to start up
512 max_shared_servers 3 20 TRUE FALSE FALSE FALSE FALSE max number of shared servers
513 mts_max_servers 3 20 TRUE FALSE FALSE FALSE FALSE max number of shared servers
514 max_dispatchers 3 5 TRUE FALSE FALSE FALSE FALSE max number of dispatchers
515 mts_max_dispatchers 3 5 TRUE FALSE FALSE FALSE FALSE max number of dispatchers
516 circuits 3 170 TRUE FALSE FALSE FALSE FALSE max number of circuits
517 mts_circuits 3 170 TRUE FALSE FALSE FALSE FALSE max number of circuits
518 shared_server_sessions 3 165 TRUE FALSE FALSE FALSE FALSE max number of shared server sessions
519 mts_sessions 3 165 TRUE FALSE FALSE FALSE FALSE max number of shared server sessions
520 local_listener 2 TRUE FALSE IMMEDIATE FALSE FALSE local listener
521 remote_listener 2 TRUE FALSE IMMEDIATE FALSE FALSE remote listener
525 mts_service 2 ora92dbd TRUE FALSE FALSE FALSE FALSE service supported by dispatchers
526 mts_listener_address 2 TRUE FALSE FALSE FALSE FALSE address(es) of network listener
527 mts_multiple_listeners 1 FALSE TRUE FALSE FALSE FALSE FALSE Are multiple listeners enabled?
528 serial_reuse 2 DISABLE TRUE FALSE FALSE FALSE FALSE reuse the frame segments
529 cursor_space_for_time 1 FALSE TRUE FALSE FALSE FALSE FALSE use more memory in order to get faster execution
530 session_cached_cursors 3 0 TRUE TRUE FALSE FALSE FALSE number of cursors to save in the session cursor cache
531 remote_dependencies_mode 2 TIMESTAMP TRUE TRUE IMMEDIATE FALSE FALSE remote-procedure-call dependencies mode parameter
532 utl_file_dir 2 F:\UTIL_FILE_DIR\ FALSE FALSE FALSE FALSE FALSE utl_file accessible directories list
534 plsql_v2_compatibility 1 FALSE TRUE TRUE IMMEDIATE FALSE FALSE PL/SQL version 2.x compatibility flag
535 plsql_compiler_flags 2 INTERPRETED TRUE TRUE IMMEDIATE FALSE FALSE PL/SQL compiler flags
536 plsql_native_c_compiler 2 TRUE FALSE IMMEDIATE FALSE FALSE plsql native C compiler
537 plsql_native_linker 2 TRUE FALSE IMMEDIATE FALSE FALSE plsql native linker
538 plsql_native_library_dir 2 TRUE FALSE IMMEDIATE FALSE FALSE plsql native library dir
539 plsql_native_make_utility 2 TRUE FALSE IMMEDIATE FALSE FALSE plsql native compilation make utility
540 plsql_native_make_file_name 2 TRUE FALSE IMMEDIATE FALSE FALSE plsql native compilation make file
541 plsql_native_library_subdir_count 3 0 TRUE FALSE IMMEDIATE FALSE FALSE plsql native library number of subdirectories
543 job_queue_processes 3 10 FALSE FALSE IMMEDIATE FALSE FALSE number of job queue slave processes
547 parallel_min_percent 3 0 TRUE TRUE FALSE FALSE FALSE minimum percent of threads required for parallel query
550 create_bitmap_area_size 3 8388608 TRUE FALSE FALSE FALSE FALSE size of create bitmap buffer for bitmap index
551 bitmap_merge_area_size 3 1048576 TRUE FALSE FALSE FALSE FALSE maximum memory allow for BITMAP MERGE
553 cursor_sharing 2 EXACT TRUE TRUE IMMEDIATE FALSE FALSE cursor sharing mode
557 parallel_min_servers 3 0 TRUE FALSE FALSE FALSE FALSE minimum parallel query servers per instance
558 parallel_max_servers 3 5 TRUE FALSE FALSE FALSE FALSE maximum parallel query servers per instance
562 parallel_instance_group 2 TRUE TRUE IMMEDIATE FALSE FALSE instance group to use for all parallel operations
565 parallel_execution_message_size 3 2148 TRUE FALSE FALSE FALSE FALSE message buffer size for parallel execution
573 hash_join_enabled 1 TRUE FALSE TRUE FALSE FALSE FALSE enable/disable hash join
574 hash_area_size 3 1048576 TRUE TRUE FALSE FALSE FALSE size of in-memory hash work area
582 shadow_core_dump 2 partial TRUE FALSE FALSE FALSE FALSE Core Size for Shadow Processes
583 background_core_dump 2 partial TRUE FALSE FALSE FALSE FALSE Core Size for Background Processes
584 background_dump_dest 2 c:\oracle\admin\ora92dbd\bdump FALSE FALSE IMMEDIATE FALSE FALSE Detached process dump directory
585 user_dump_dest 2 c:\oracle\admin\ora92dbd\udump FALSE FALSE IMMEDIATE FALSE FALSE User process dump directory
586 max_dump_file_size 2 UNLIMITED TRUE TRUE IMMEDIATE FALSE FALSE Maximum size (blocks) of dump file
587 core_dump_dest 2 c:\oracle\admin\ora92dbd\cdump FALSE FALSE IMMEDIATE FALSE FALSE Core dump directory
589 oracle_trace_enable 1 FALSE TRUE TRUE IMMEDIATE FALSE FALSE Oracle Trace enabled/disabled
590 oracle_trace_facility_path 2 %ORACLE_HOME%\OTRACE\ADMIN\FDF\ TRUE FALSE FALSE FALSE FALSE Oracle TRACE facility path
591 oracle_trace_collection_path 2 %ORACLE_HOME%\OTRACE\ADMIN\CDF\ TRUE FALSE FALSE FALSE FALSE Oracle TRACE collection path
592 oracle_trace_facility_name 2 oracled TRUE FALSE FALSE FALSE FALSE Oracle TRACE default facility name
593 oracle_trace_collection_name 2 TRUE FALSE FALSE FALSE FALSE Oracle TRACE default collection name
594 oracle_trace_collection_size 3 5242880 TRUE FALSE FALSE FALSE FALSE Oracle TRACE collection file max. size
597 object_cache_optimal_size 3 102400 TRUE TRUE DEFERRED FALSE FALSE optimal size of the user session's object cache in bytes
598 object_cache_max_size_percent 3 10 TRUE TRUE DEFERRED FALSE FALSE percentage of maximum size over optimal of the user session's ob
600 session_max_open_files 3 10 TRUE FALSE FALSE FALSE FALSE maximum number of open files allowed per session
604 open_links 3 4 TRUE FALSE FALSE FALSE FALSE max # open links per session
605 open_links_per_instance 3 4 TRUE FALSE FALSE FALSE FALSE max # open links per instance
610 optimizer_features_enable 2 9.2.0 TRUE FALSE FALSE FALSE FALSE optimizer plan compatibility parameter
611 fixed_date 2 TRUE FALSE IMMEDIATE FALSE FALSE fixed SYSDATE value
612 audit_trail 2 NONE TRUE FALSE FALSE FALSE FALSE enable system auditing
613 sort_area_size 3 524288 FALSE TRUE DEFERRED FALSE FALSE size of in-memory sort work area
614 sort_area_retained_size 3 0 TRUE TRUE DEFERRED FALSE FALSE size of in-memory sort work area retained between fetch calls
620 db_name 2 ora92dbd FALSE FALSE FALSE FALSE FALSE database name specified in CREATE DATABASE
621 open_cursors 3 300 FALSE FALSE IMMEDIATE FALSE FALSE max # cursors per session
622 ifile 4 TRUE FALSE FALSE FALSE FALSE include file in init.ora
623 sql_trace 1 FALSE TRUE FALSE FALSE FALSE FALSE enable SQL trace
625 os_authent_prefix 2 OPS$ TRUE FALSE FALSE FALSE FALSE prefix for auto-logon accounts
627 optimizer_mode 2 FIRST_ROWS FALSE TRUE FALSE FALSE FALSE optimizer mode
632 sql92_security 1 FALSE TRUE FALSE FALSE FALSE FALSE require select privilege for searched update/delete
634 blank_trimming 1 FALSE TRUE FALSE FALSE FALSE FALSE blank trimming semantics parameter
636 partition_view_enabled 1 FALSE TRUE TRUE FALSE FALSE FALSE enable/disable partitioned views
639 star_transformation_enabled 2 FALSE FALSE TRUE FALSE FALSE FALSE enable the use of star transformation
667 parallel_adaptive_multi_user 1 FALSE TRUE FALSE IMMEDIATE FALSE FALSE enable adaptive setting of degree for multiple user streams
668 parallel_threads_per_cpu 3 2 TRUE FALSE IMMEDIATE FALSE FALSE number of parallel execution threads per CPU
669 parallel_automatic_tuning 1 FALSE TRUE FALSE FALSE FALSE FALSE enable intelligent defaults for parallel execution parameters
689 optimizer_max_permutations 3 2000 TRUE TRUE FALSE FALSE FALSE optimizer maximum join permutations per query block
690 optimizer_index_cost_adj 3 100 TRUE TRUE FALSE FALSE FALSE optimizer index cost adjustment
691 optimizer_index_caching 3 0 TRUE TRUE FALSE FALSE FALSE optimizer percent index caching
698 query_rewrite_enabled 2 FALSE FALSE TRUE IMMEDIATE FALSE FALSE allow rewrite of queries using materialized views if enabled
699 query_rewrite_integrity 2 enforced TRUE TRUE IMMEDIATE FALSE FALSE perform rewrite using materialized views with desired integrity
727 sql_version 2 NATIVE TRUE TRUE FALSE FALSE FALSE sql language version parameter for compatibility issues
754 pga_aggregate_target 6 52428800 FALSE FALSE IMMEDIATE FALSE FALSE Target size for the aggregate PGA memory consumed by the instanc
756 workarea_size_policy 2 AUTO TRUE TRUE IMMEDIATE FALSE FALSE policy used to size SQL working areas (MANUAL/AUTO)
775 optimizer_dynamic_sampling 3 1 TRUE TRUE IMMEDIATE FALSE FALSE optimizer dynamic sampling
792 statistics_level 2 TYPICAL TRUE TRUE IMMEDIATE FALSE FALSE statistics level
795 aq_tm_processes 3 1 FALSE FALSE IMMEDIATE FALSE FALSE number of AQ Time Managers to start
797 hs_autoregister 1 TRUE TRUE FALSE IMMEDIATE FALSE FALSE enable automatic server DD updates in HS agent self-registration
798 dg_broker_start 1 FALSE TRUE FALSE IMMEDIATE FALSE FALSE start Data Guard broker framework (DMON process)
799 drs_start 1 FALSE TRUE FALSE IMMEDIATE FALSE FALSE start DG Broker monitor (DMON process)
800 dg_broker_config_file1 2 %ORACLE_HOME%\DATABASE\DR1%ORACLE_SID%.DAT TRUE FALSE IMMEDIATE FALSE FALSE data guard broker configuration file #1
801 dg_broker_config_file2 2 %ORACLE_HOME%\DATABASE\DR2%ORACLE_SID%.DAT TRUE FALSE IMMEDIATE FALSE FALSE data guard broker configuration file #2
802 olap_page_pool_size 3 33554432 TRUE TRUE DEFERRED FALSE FALSE size of the olap page pool in bytes
SQL> show parameter undo;
NAME TYPE VALUE
undo_management string AUTO
undo_retention integer 10800
undo_suppress_errors boolean FALSE
undo_tablespace string UNDOTBS1
SQL> -
2 Undo Tablespace both ONLINE, How to drop previous undo tbs
Hello Team,
Undo management=auto
After Cloning :-
To reclaim space i created another undo tablespace, but now both are online, but as per oracle as soon as you switch undo tablespace, previous undo TBS gets in Pending offline mode,offline mode, (So that transaction get finished)
But in my case Both UNDO Tablespaces are online
Previous Undo TBS1:- 600 GB
New UNDo Tb2s:- 100GB
Please suggest how to drop this online undo TBS1
TABLESPACE_NAME ONLINE_
APPS_UNDOTS1 ONLINE
APPS_UNDOTS1 ONLINE
APPS_UNDOTS1 ONLINE
APPS_UNDOTS1 ONLINE
APPS_UNDOTS1 ONLINE
APPS_UNDOTS1 ONLINE
APPS_UNDOTS1 ONLINE
APPS_UNDOTS1 ONLINE
APPS_UNDOTS1 ONLINE
APPS_UNDOTS2 ONLINE
APPS_UNDOTS2 ONLINE
TABLESPACE_NAME ONLINE_
APPS_UNDOTS2 ONLINEHi As per
select segment_name,owner,tablespace_name,status from dba_rollback_segs where tablespace_name like 'UNDOTBS1';
All Are offline for UNDOTBS1(Previous)
SEGMENT_NAME OWNER TABLESPACE_NAME STATUS
SYSSMU49861044602693$ PUBLIC APPS_UNDOTS1 OFFLINE
SYSSMU4893847838046$ PUBLIC APPS_UNDOTS1 OFFLINE
SYSSMU48682660477388$ PUBLIC APPS_UNDOTS1 OFFLINE
SYSSMU47753309457002$ PUBLIC APPS_UNDOTS1 OFFLINE
SYSSMU47131240212364$ PUBLIC APPS_UNDOTS1 OFFLINE
434 rows selected. -
No icmp reply from my catalyst 2950 switch
My switches is still operating but when i ping the switch, there isn't any reply. Expert please advice.
David
There are several things that might produce the symptoms that you describe. Without some more details it is difficult to know which one it might be. Some of the possibilities include:
- the switches may not have an IP address assigned. The switch will still do an excellent job of forwarding frames at layer 2, but without an IP address it can not respond to ping.
- the switch may have an IP address but there is some error in configuration of the address (perhaps a misconfigured mask, or a keying error in the address). This would not impact the switch ability to function at layer 2 but would not allow it to respond to ping etc.
- the switch may not be configured with a default gateway (or configured with an error about the default gateway). This would allow the switch to respond at layer 3 within its own subnet but not able to respond to anything outside its subnet.
- the switch may have its IP address assigned for management purposes, but the address may be associated with a VLAN which has no active ports and therefore is inactive and can not respond.
- there might be an access list assigned somewhere that is not permitting the ping.
There could be some other things. If you can provide some more details, like what kind of switches are we talking about, and some details of how the switches are configured we may be able to find better answers.
HTH
Rick -
RAC 10g - Undo full istance off
Hi,
I have Oracle Rac 10g environment with 2 istances in Solaris 10 SPARC.
For testing high availability, I have shutdown one istance and I have executed the performance test.
The undo datafile of instance off was filled, while the instance was running the other half, why?
Best Regards
Francesco MaisanoHi Francesco,
Each instance in the RAC system can only use one undo tablespace at a time. In other words, instances cannot share undo tablespaces. Each instance in the cluster, being an independent transaction-processing environment, maintains its own UNDO area for undo management.
The undo tablespace cannot be shared among the instances at the same time. Only once an undo tablespace is released by an instance, it can be assigned to another instance. However, all instances can read blocks from any or all undo tablespaces for the purpose of constructing read-consistency images.
Switching Undo Tablespaces
You can switch from using one undo tablespace to another. Because the UNDO_TABLESPACE initialization parameter is a dynamic parameter, the ALTER SYSTEM SET statement can be used to assign a new undo tablespace.
If the parameter value for UNDO TABLESPACE is set to '' (two single quotes), then the current undo tablespace is switched out and the next available undo tablespace is switched in.
The database is online while the switch operation is performed, and user transactions can be executed while this command is being executed. When the switch operation completes successfully, all transactions started after the switch operation began are assigned to transaction tables in the new undo tablespace.
The switch operation does not wait for transactions in the old undo tablespace to commit. If there are any pending transactions in the old undo tablespace, the old undo tablespace enters into a PENDING OFFLINE mode (status). In this mode, existing transactions can continue to execute, but undo records for new user transactions cannot be stored in this undo tablespace.
An undo tablespace can exist in this PENDING OFFLINE mode, even after the switch operation completes successfully. A PENDING OFFLINE undo tablespace cannot be used by another instance, nor can it be dropped. Eventually, after all active transactions have committed, the undo tablespace automatically goes from the PENDING OFFLINE mode to the OFFLINE mode. From then on, the undo tablespace is available for other instances.
In another post I put the GV$ .. to you identify the cause of UNDO is full. (e.g Which transactions are on TBS UNDO full)
How undo Space Allocation Works
http://arjudba.blogspot.com/2008/04/how-undo-space-allocation-works.html
Regards,
Levi Pereira -
Move an undo tablespace datafile while online
Having a spirited debate at work today. Is it possible, or has anyone successfully moved an undo tablespace datafile while keeping the database online? (Hypothetically someone created it in the wrong directory)
My logic:
Create a new undo tablespace B
Switch undo tablespace from A to B
Take tablespace A offline
Once A goes from 'PENDING OFFLINE' to 'OFFLINE' copy the file to new location
Alter database rename file location
Switch undo tablespace from B to A
Drop tablespace B
Any comments?Yes I do understood that, but you don't have to "move" the datafile.
The procedure I proposed is just to create a new undo tablespace, drop the former and forget about it.
You can't "move" the file stricto sensu while the database is online, but nothing prevents you from switching from one tablespace to another. Once it's done, everything's fine. And if you're on 10G (r2?) you might even rename tablespace "B" to tablespace "A"!
Yoann. -
Mid month Acquisition/ Divesture
We have Company A and B. A own 80% in Company B till March 15th. Following are the questions in the context..
Q1> If divesture of the Consolidation unit is occurring in the mid month(March 15th) , when the divesture will be accounted in consolidation? On March 15th 70% is divested and consolidation method changes from Purchasing to Equity method.
Q2>Where do we capture the exact date of divesture for BCS records.
Q3>Is it possible to account for Purchase method and equity method for one month. I.e. Up to March 15th entries need to reflected with Purchase method and March 15th to 31st need to accounted using Equity method. Is it possible to have 2 method in consolidation period.Since you'll switch to Equity method, then, yes, for Equity Adjustments.
Flags:
DABP - Switching immediately at the beginning period. RE for this period is not taken into account.
DAEP - RE is apportioned according to Purchase method. Then goes switch to Equity.
For the half month with Purhase method the Parent company earned its share of RE of divested company. So, IMHO, if you set DABP then calculate and add some more equity adjustment, IF DAEP - deduct some.
Of course, you should estimate the impact of switching methods on increase or decrease in your parent company net profit.
Maybe you are looking for
-
Cisco ISE and WLC Timeout Best Practices
I am fairly new to ISE. Our Cisco WLC is using 802.1x and ISE is configured for PEAP with all inner methods enabled. I am looking for some guidance around where I should be configuring timeouts. There is a PEAP Session timeout in ISE, a session timeo
-
Dynamic Calc Issue - CalcLockBlock or Data Cache Setting
We recently started seeing an issue with a Dynamic scenario member in our UAT and DEV environments. When we tried to reference the scenario member in Financial Reports, we get the following error: Error executing query: The data form grid is invalid.
-
I need help with the Quote applet.
Hey all, I need help with the Quote applet. I downloaded it and encoded it in the following html code: <html> <head> <title>Part 2</title> </head> <body> <applet codebase="/demo/quote/classes" code="/demo/quote/JavaQuote.class" width="300" heigh
-
LIBGW_CAT:1000: ERROR: Message dropped by gw_msg_recv(). Error = 402003
All , Could you please help me in getting the details about this error message ? LIBGW_CAT:1000: ERROR: Message dropped by gw_msg_recv(). Error = 402003. GWIDOMAIN.20404.1438440448.0: LIBGW_CAT:1000: ERROR: Message dropped by gw_msg_recv(). Error = 4
-
Is there a way to change the order of the items in the HUB menu? Ie. the order is typically (I think) HUB NOTIFICATIONS BBM TEXT EMAIL ADDRESS CALLs could you change it to have HUB NOTIFICATIONS CALLS EMAIL TEXT BBM