ORA-01111: for undo tablespace
Hi,
We have large archive gap in standby.
When we try to apply archive log manually using recover standby database, it throws the below error
SQL> recover standby database;
ORA-00283: recovery session canceled due to errors
ORA-01111: name for data file 35 is unknown - rename to correct file
ORA-01110: data file 35: '/data/db/tech_st/11.1.0/dbs/UNNAMED00035'
ORA-01157: cannot identify/lock data file 35 - see DBWR trace file
ORA-01111: name for data file 35 is unknown - rename to correct file
ORA-01110: data file 35: '/data/db/tech_st/11.1.0/dbs/UNNAMED00035'
We have added File 35 in Primary in undo tablespace , hence it's throwing error.
Please advice.
Thanks
Hi,
If you have the same filesystem on both primary and standby database, then why dont you try backing up single file and restoring to standby database.
Connect to your primary database:
rman target /
run
allocate channels...;
backup datafile 35;
Copy the backup piece to standby database. On standby database:
rman target /
catalog start with 'backup location';
restore datafile 35;
then on your sqlplus:
recover standby database;
Hope this will resolve your problem.
Similar Messages
-
Error Oracle Mobile ORA-30023 Duplicate undo tablespace specification
Hi,
I have the following mobile application (Oracle Mobile 10g R3):
- Win32 (Forms 6i) App.
- snapshots (12 updateable, 36 read-only)
I have a successfully compilation of my form connected to the mobile database. However when I put a value over a textitem, my WHEN-VALIDATE-ITEM trigger send me an error:
ORA-30023 Duplicate undo tablespace specification
How can I solve this???, It seems like there is a parameter that I have to change.
The WHEN-VALIDATE-ITEM trigger only has a basic select over a "readonly" table.
Please help.
Regards,
SantiagoI think the problem is the following,
I need to convert a date to julian format, example:
to_char(sysdate,'j')
The problem is that it seems like Oracle Mobile connot support this kind format convertion.
So, How can I get the number of days between 01-jan-4712 BC and other date????
I found this function TO_DATE('-4712-01-01', 'SYYYY-MM-DD'), but it doesn´t works on Oracle Mobile.
If someone have any idea about how can I get the number of days between 01-jan-4712 BC and other day without using the format 'SYYYY'......please help -
FLASHBACK OFF FOR UNDO TABLESPACE????
Hi all
As my Undo tablespace growing evryday 2 GB & NOW it reached 19,
Database size is 6GB only
using Oracle 10g Release 2 without patch Set (release 1002000100) on Hp-Unix OS
Can i use the Undo tablespace with FLASHBACK OFF option?
what are the Consequences for Turning off the FLASHBACK,
Can we use this type of Undo tablespace with Flashback OFF???
CREATE UNDO TABLESPACE UNDOTBS03 DATAFILE
'/app/oracle/product/oradata/prod/undotbs03.dbf' SIZE 1000M AUTOEXTEND OFF
ONLINE
RETENTION NOGUARANTEE
BLOCKSIZE 8K
FLASHBACK OFF;
THANKS ALOTOracle Flashback Database: feature is similar to conventional point-in-time recovery in its results, allowing you to return a database to its state at a time in the recent past. It is, however, much faster than point-in-time recovery, because it does not require restoration of datafiles from a backup and it requires application of fewer changes from the archived redo logs.
UNDO Tablespace: Oracle db save the old value when a process change data in undo tablespace.
I think that you can change de default UNDO tablespace as NO AUTOEXTEND, and
Configure
SET UNDO_MANAGEMENT=AUTO
SET UNDO_RETENTION= ( second need for logger transaction )
UNDO_RETENTION specifies (in seconds) the low threshold value of undo retention. For AUTOEXTEND undo tablespaces, the system retains undo for at least the time specified in this parameter, and automatically tunes the undo retention period to satisfy the undo requirements of the queries.
For fixed- size undo tablespaces, the system automatically tunes for the maximum possible undo retention period, based on undo tablespace size and usage history, and ignores UNDO_RETENTION unless retention guarantee is enabled. -
High Water Mark for Undo tablespace..!!
Hello Everybody,
I was searching since long to get how much maximum the undo tablespace might have reached.
Can somebody please help me with the query to find out what is the maximum that undo tablespace has been reached.
Any help will be greatly appreciated.
Thanks -
Harsh.Hi,
Undo tablespace are different from the normal tablespace. They consist of undo segments which can have undo blocks in three status
1)ACTIVE
This means that undo extent is Active and being currently used by a transaction
2)UNEXPIRED
This represents the extents which are required to satisfy the time specified by Undo_retention Initialisation parameter.
3)EXPIRED
These are extents which are not being used by transaction and have crossed the time specified by Undo_retention .
(http://askoracledba.blogspot.com/2008/04/undo-tablespace-sizing.html)
Now there might be case that the blocks for committed transactions which has passed undo_retention are in middle of datafile.
In case you want HWM information so as to reduce the datafilesize, then I would recommend you to create a new undo tablespace and switch to it. After that you can drop the old undo tablespace.
-Amit
http://askoracledba.blogspot.com -
Snapshot too old in a very big undo tablespace
Hi,
I can see the snapshot too old error message in my alert log file.
ORA-01555 caused by SQL statement below (Query Duration=5 sec, SCN: 0x000d.a1e610e5):
It shows that query failed just after its start within 5 seconds. I really dont understand this in the presence of following facts
Current size of my undo tablespace is around 15G and undo retention is 180 minutes and for my environment, oracle recommends to use around 8 G size for undo tablespace if i want to use undo retention to be set for 180 minutes.
I am using oracle 9.2.0.6 and automatic undo management.
Thanks
SalmanCould it be that the ora-1555 is thrown by the statement in the alert log, but is really caused by another statement that has been sitting around since yesterday? Oracle may be trying to make read-consistent some data that the other statement used to have in undo.
I see this all the time if I don't kill off leftover sessions in the middle of the night. Darn users.
Search asktom.oracle.com for the error, many good explanations there and in his books. There are some application coding conditions that can cause this, too.
Also, try doing a full scan of the table - select some arbitrary column without a where statement. This may correct a "delayed block cleanout" condition. Google that for more info if you don't know about it. -
Total space occupied by UNDO tablespace is : 3G and used space for UNDO tablespace is only 512M , so approx 2.5G space is free. But when i tried to resize the undo tablespace to 1G then its showing the below error :
ORA-03297: file contains used data beyond requested RESIZE value
but the used data size is 512M only.
Kindly help me to resize the undo tablespace to 1G.
Database : Oracle Database 10g Enterprise Edition Release 10.2.0.2.0 - 64bi
Kindly suggest.
Advance thanks !!you can't resize undo tablespace. If you are trying to reduce the size.
then add a unod tablespace may like undotbs2 then set undotbs2 as default to your database. then drop the prvious undo tablespace
Anil Malkai -
Undo tablespace full even with no active transaction and undo_retention 10s
The 9.2.0.4 instance is AUM (auto undo management). The undo table space is 50G and is almost full.
I have set the undo_retention to 10, previously it was 10800 (3hours). I restart the database. Wait quite long time.
And search on the dba_undo_extents.
select sum(bytes/(1024*1024*1024)),status from dba_undo_extents d where d.tablespace_name='UNDOTBS2' group by status;
SUM(BYTES/(1024*1024*1024)) STATUS
.574447632 EXPIRED
45.5358887 UNEXPIRED
It is hard to explain. 10 seconds already passed, at least all the extents should be expired.
Why so many 45G is still unexpried.
Is there a bug for undo tablespace? how to fix it.
It is a rac instance, I am trouble shooting the undo tablespace issues.
The UNDOTBS2 is for node2 to use.If you start the database in exclusive (one instance) mode then the database instance can have only one undo tablespace so I would not expect Oracle to do anything with the undo tablespace for the non-running instance.
Run you database as normal and generate undo. See if the status changes. If if does that would imply that Oracle does not expire undo unless the undo segments (rbs segments) are accessed. Please post back with results of what you see.
Between having batch production running on all my databases that use undo tablespaces and the fact we use uniform extent undo tabllespaces I am not in a position to try to duplicate what you are seeing.
HTH -- Mark D Powell -- -
ORA-30012: undo tablespace 'UNDOTBS' does not exist or of wrong type
OS Version : AIX 6.1
DB Version : 11.2.0.1
I am duplicating database and got below error:
contents of Memory Script:
Alter clone database open resetlogs;
executing Memory Script
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-00601: fatal error in recovery manager
RMAN-03004: fatal error during execution of command
RMAN-10041: Could not re-create polling channel context following failure.
RMAN-10024: error setting up for rpc polling
RMAN-10005: error opening cursor
RMAN-10002: ORACLE error: ORA-03114: not connected to ORACLE
RMAN-03002: failure of Duplicate Db command at 02/16/2013 17:20:02
RMAN-03015: error occurred in stored script Memory Script
RMAN-06136: ORACLE error from auxiliary database: ORA-01092: ORACLE instance terminated. Disconnection forced
ORA-30012: undo tablespace 'UNDOTBS' does not exist or of wrong type
Process ID: 44040326
Session ID: 65 Serial number: 3
Error is because in target database undo tablespace is UNDOTBS_NEW and in auxiliary database undo tablespace name in init file is UNDOTBS. I followed the meatlink doc 433992.1 which suggest following steps to recover from above error:
1) edit the parameter UNDO_MANAGEMENT to "MANUAL"
2) start database again
3) drop the UNDO tablespace
4) recreate UNDO tablespace which matches to name in init file.
5) shutdown & start DB again.
Now, i edited init file and tried to start DB and got following error:
oracore@cph-core-db01-s $ sqlplus /nolog
SQL*Plus: Release 11.2.0.1.0 Production on Sat Feb 16 17:22:11 2013
Copyright (c) 1982, 2009, Oracle. All rights reserved.
SQL> conn sys as sysdba
Enter password:
Connected to an idle instance.
SQL> startup
ORACLE instance started.
Total System Global Area 4275781632 bytes
Fixed Size 2213632 bytes
Variable Size 822085888 bytes
Database Buffers 3439329280 bytes
Redo Buffers 12152832 bytes
Database mounted.
ORA-01113: file 1 needs media recovery
ORA-01110: data file 1: '/u04/oradata/CORE/CORE_DUP/system01.dbf'I don't want to run duplicate command with correct UNDO tablespace name. Any other work around for this ?STARTUP MOUNT
RECOVER DATABASE USING BACKUP CONTROLFILE UNTIL CANCEL
CANCEL
ALTER DATABASE OPEN RESETLOGS
Above option is not working for CORE_DUP, i am getting very strange error, while trying to recover i am getting very strange error as below:
oracore@cph-core-db01-s $ export ORACLE_SID=CORE_DUP
SQL*Plus: Release 11.2.0.1.0 Production on Mon Feb 18 11:17:25 2013
Copyright (c) 1982, 2009, Oracle. All rights reserved.
SQL> conn sys as sysdba
Enter password:
Connected to an idle instance.
SQL> startup mount
ORACLE instance started.
Total System Global Area 4275781632 bytes
Fixed Size 2213632 bytes
Variable Size 822085888 bytes
Database Buffers 3439329280 bytes
Redo Buffers 12152832 bytes
Database mounted.
SQL> alter database open resetlogs;
alter database open resetlogs
ERROR at line 1:
ORA-01139: RESETLOGS option only valid after an incomplete database recovery
SQL> recover database using backup controlfile until cancel;
ORA-00283: recovery session canceled due to errors
ORA-16433: The database must be opened in read/write mode.Primary database initfile:
event="10298 trace name context forever, level 32"
db_block_size=8192
db_file_multiblock_read_count=16
open_cursors=300
db_name=CORE
cursor_sharing='SIMILAR'
global_names=FALSE
diagnostic_dest=/u01/app/oracore/diag/CORE
#background_dump_dest=/u01/app/oracore/diag/rdbms/bdump
#core_dump_dest=/u01/app/oracore/diag/rdbms/cdump
#user_dump_dest=/u01/app/oracore/diag/rdbms/udump
control_files=("/u01/oradata/CORE/control01.ctl", "/u02/oradata/CORE/control02.ctl", "/u03/oradata/CORE/control03.ctl")
log_archive_dest_1='LOCATION=/u05/oradata/CORE/'
log_archive_format='CORE_%s%t%r.ARC'
job_queue_processes=10
compatible=11.2.0.1
processes=150
fast_start_mttr_target=300
filesystemio_options='SETALL'
pga_aggregate_target=500M
recyclebin='OFF'
remote_login_passwordfile='EXCLUSIVE'
session_cached_cursors=100
sga_target=4G
undo_management='AUTO'
undo_tablespace='UNDOTBS_NEW'
nls_date_format='DD-MON-RRRR'
nls_length_semantics='CHAR'initfile for CORE_DUP
event="10298 trace name context forever, level 32"
db_block_size=8192
db_file_multiblock_read_count=16
open_cursors=300
db_name=CORE_DUP
cursor_sharing='SIMILAR'
global_names=FALSE
diagnostic_dest=/u01/app/oracore/diag/CORE/CORE_DUP
control_files=("/u01/oradata/CORE/CORE_DUP/control01.ctl", "/u02/oradata/CORE/CORE_DUP/control02.ctl", "/u03/oradata/CORE/CORE_DUP/control03.ctl")
log_archive_dest_1='LOCATION=/u05/oradata/CORE/CORE_DUP/'
log_archive_format='CORE_DUP%s%t%r.ARC'
job_queue_processes=10
compatible=11.2.0.1
_compression_compatibility="11.2.0"
processes=150
fast_start_mttr_target=300
filesystemio_options='SETALL'
pga_aggregate_target=500M
recyclebin='OFF'
remote_login_passwordfile='EXCLUSIVE'
session_cached_cursors=100
sga_target=4G
undo_management='AUTO'
undo_tablespace='UNDOTBS'
nls_date_format='DD-MON-RRRR'
nls_length_semantics='CHAR'
log_file_name_convert='/CORE','/CORE/CORE_DUP'
db_file_name_convert='/CORE','/CORE/CORE_DUP'Duplicate steps are as:
oracore@cph-core-db01-s $ rman target sys/zzzz@core catalog rmantst10/zzzzz@catdb auxiliary /
Recovery Manager: Release 11.2.0.1.0 - Production on Mon Feb 18 15:50:00 2013
Copyright (c) 1982, 2009, Oracle and/or its affiliates. All rights reserved.
connected to target database: CORE (DBID=913972022)
connected to recovery catalog database
connected to auxiliary database: CORE_DUP (not mounted)
RMAN> duplicate target database to CORE_DUP;
Starting Duplicate Db at 18-FEB-13
allocated channel: ORA_AUX_DISK_1
channel ORA_AUX_DISK_1: SID=96 device type=DISK
allocated channel: ORA_AUX_DISK_2
channel ORA_AUX_DISK_2: SID=127 device type=DISK
contents of Memory Script:
sql clone "create spfile from memory";
executing Memory Script
sql statement: create spfile from memory
contents of Memory Script:
shutdown clone immediate;
startup clone nomount;
executing Memory Script
Oracle instance shut down
connected to auxiliary database (not started)
Oracle instance started
Total System Global Area 4275781632 bytes
Fixed Size 2213632 bytes
Variable Size 838863104 bytes
Database Buffers 3422552064 bytes
Redo Buffers 12152832 bytes
contents of Memory Script:
sql clone "alter system set db_name =
''CORE'' comment=
''Modified by RMAN duplicate'' scope=spfile";
sql clone "alter system set db_unique_name =
''CORE_DUP'' comment=
''Modified by RMAN duplicate'' scope=spfile";
shutdown clone immediate;
startup clone force nomount
restore clone primary controlfile;
alter clone database mount;
executing Memory Script
sql statement: alter system set db_name = ''CORE'' comment= ''Modified by RMAN duplicate'' scope=spfile
sql statement: alter system set db_unique_name = ''CORE_DUP'' comment= ''Modified by RMAN duplicate'' scope=spfile
Oracle instance shut down
Oracle instance started
Total System Global Area 4275781632 bytes
Fixed Size 2213632 bytes
Variable Size 838863104 bytes
Database Buffers 3422552064 bytes
Redo Buffers 12152832 bytes
Starting restore at 18-FEB-13
allocated channel: ORA_AUX_DISK_1
channel ORA_AUX_DISK_1: SID=96 device type=DISK
allocated channel: ORA_AUX_DISK_2
channel ORA_AUX_DISK_2: SID=127 device type=DISK
channel ORA_AUX_DISK_1: starting datafile backup set restore
channel ORA_AUX_DISK_1: restoring control file
channel ORA_AUX_DISK_1: reading from backup piece /oraclebackup/CORE/DF_L1_CORE_16022013_5fo246k3_175_1
channel ORA_AUX_DISK_1: piece handle=/oraclebackup/CORE/DF_L1_CORE_16022013_5fo246k3_175_1 tag=LEVEL1
channel ORA_AUX_DISK_1: restored backup piece 1
channel ORA_AUX_DISK_1: restore complete, elapsed time: 00:00:03
output file name=/u01/oradata/CORE/CORE_DUP/control01.ctl
output file name=/u02/oradata/CORE/CORE_DUP/control02.ctl
output file name=/u03/oradata/CORE/CORE_DUP/control03.ctl
Finished restore at 18-FEB-13
database mounted
contents of Memory Script:
set until scn 1217601;
set newname for datafile 1 to
"/u04/oradata/CORE/CORE_DUP/system01.dbf";
set newname for datafile 2 to
"/u04/oradata/CORE/CORE_DUP/sysaux01.dbf";
set newname for datafile 4 to
"/u04/oradata/CORE/CORE_DUP/users01.dbf";
set newname for datafile 5 to
"/u04/oradata/CORE/CORE_DUP/users02.dbf";
set newname for datafile 6 to
"/u04/oradata/CORE/CORE_DUP/users03.dbf";
set newname for datafile 9 to
"/u04/oradata/CORE/CORE_DUP/undotbs_new01.dbf";
restore
clone database
executing Memory Script
executing command: SET until clause
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
Starting restore at 18-FEB-13
using channel ORA_AUX_DISK_1
using channel ORA_AUX_DISK_2
channel ORA_AUX_DISK_1: starting datafile backup set restore
channel ORA_AUX_DISK_1: specifying datafile(s) to restore from backup set
channel ORA_AUX_DISK_1: restoring datafile 00004 to /u04/oradata/CORE/CORE_DUP/users01.dbf
channel ORA_AUX_DISK_1: restoring datafile 00005 to /u04/oradata/CORE/CORE_DUP/users02.dbf
channel ORA_AUX_DISK_1: restoring datafile 00006 to /u04/oradata/CORE/CORE_DUP/users03.dbf
channel ORA_AUX_DISK_1: reading from backup piece /oraclebackup/CORE/DF_L0_CORE_16022013_55o246fe_165_1
channel ORA_AUX_DISK_2: starting datafile backup set restore
channel ORA_AUX_DISK_2: specifying datafile(s) to restore from backup set
channel ORA_AUX_DISK_2: restoring datafile 00001 to /u04/oradata/CORE/CORE_DUP/system01.dbf
channel ORA_AUX_DISK_2: restoring datafile 00002 to /u04/oradata/CORE/CORE_DUP/sysaux01.dbf
channel ORA_AUX_DISK_2: restoring datafile 00009 to /u04/oradata/CORE/CORE_DUP/undotbs_new01.dbf
channel ORA_AUX_DISK_2: reading from backup piece /oraclebackup/CORE/DF_L0_CORE_16022013_56o246fe_166_1
channel ORA_AUX_DISK_2: piece handle=/oraclebackup/CORE/DF_L0_CORE_16022013_56o246fe_166_1 tag=LEVEL0
channel ORA_AUX_DISK_2: restored backup piece 1
channel ORA_AUX_DISK_2: restore complete, elapsed time: 00:01:15
channel ORA_AUX_DISK_1: piece handle=/oraclebackup/CORE/DF_L0_CORE_16022013_55o246fe_165_1 tag=LEVEL0
channel ORA_AUX_DISK_1: restored backup piece 1
channel ORA_AUX_DISK_1: restore complete, elapsed time: 00:01:35
Finished restore at 18-FEB-13
contents of Memory Script:
switch clone datafile all;
executing Memory Script
datafile 1 switched to datafile copy
input datafile copy RECID=24 STAMP=807724355 file name=/u04/oradata/CORE/CORE_DUP/system01.dbf
datafile 2 switched to datafile copy
input datafile copy RECID=25 STAMP=807724355 file name=/u04/oradata/CORE/CORE_DUP/sysaux01.dbf
datafile 4 switched to datafile copy
input datafile copy RECID=26 STAMP=807724356 file name=/u04/oradata/CORE/CORE_DUP/users01.dbf
datafile 5 switched to datafile copy
input datafile copy RECID=27 STAMP=807724356 file name=/u04/oradata/CORE/CORE_DUP/users02.dbf
datafile 6 switched to datafile copy
input datafile copy RECID=28 STAMP=807724356 file name=/u04/oradata/CORE/CORE_DUP/users03.dbf
datafile 9 switched to datafile copy
input datafile copy RECID=29 STAMP=807724356 file name=/u04/oradata/CORE/CORE_DUP/undotbs_new01.dbf
contents of Memory Script:
set until scn 1217601;
recover
clone database
delete archivelog
executing Memory Script
executing command: SET until clause
Starting recover at 18-FEB-13
using channel ORA_AUX_DISK_1
using channel ORA_AUX_DISK_2
channel ORA_AUX_DISK_1: starting incremental datafile backup set restore
channel ORA_AUX_DISK_1: specifying datafile(s) to restore from backup set
destination for restore of datafile 00001: /u04/oradata/CORE/CORE_DUP/system01.dbf
destination for restore of datafile 00002: /u04/oradata/CORE/CORE_DUP/sysaux01.dbf
destination for restore of datafile 00009: /u04/oradata/CORE/CORE_DUP/undotbs_new01.dbf
channel ORA_AUX_DISK_1: reading from backup piece /oraclebackup/CORE/DF_L1_CORE_16022013_5eo246k2_174_1
channel ORA_AUX_DISK_2: starting incremental datafile backup set restore
channel ORA_AUX_DISK_2: specifying datafile(s) to restore from backup set
destination for restore of datafile 00004: /u04/oradata/CORE/CORE_DUP/users01.dbf
destination for restore of datafile 00005: /u04/oradata/CORE/CORE_DUP/users02.dbf
destination for restore of datafile 00006: /u04/oradata/CORE/CORE_DUP/users03.dbf
channel ORA_AUX_DISK_2: reading from backup piece /oraclebackup/CORE/DF_L1_CORE_16022013_5do246k2_173_1
channel ORA_AUX_DISK_1: piece handle=/oraclebackup/CORE/DF_L1_CORE_16022013_5eo246k2_174_1 tag=LEVEL1
channel ORA_AUX_DISK_1: restored backup piece 1
channel ORA_AUX_DISK_1: restore complete, elapsed time: 00:00:01
channel ORA_AUX_DISK_2: piece handle=/oraclebackup/CORE/DF_L1_CORE_16022013_5do246k2_173_1 tag=LEVEL1
channel ORA_AUX_DISK_2: restored backup piece 1
channel ORA_AUX_DISK_2: restore complete, elapsed time: 00:00:01
starting media recovery
archived log for thread 1 with sequence 1718 is already on disk as file /u05/oradata/CORE/CORE_17181807276264.ARC
archived log for thread 1 with sequence 1719 is already on disk as file /u05/oradata/CORE/CORE_17191807276264.ARC
archived log for thread 1 with sequence 1720 is already on disk as file /u05/oradata/CORE/CORE_17201807276264.ARC
archived log for thread 1 with sequence 1721 is already on disk as file /u05/oradata/CORE/CORE_17211807276264.ARC
archived log for thread 1 with sequence 1722 is already on disk as file /u05/oradata/CORE/CORE_17221807276264.ARC
archived log for thread 1 with sequence 1723 is already on disk as file /u05/oradata/CORE/CORE_17231807276264.ARC
archived log for thread 1 with sequence 1724 is already on disk as file /u05/oradata/CORE/CORE_17241807276264.ARC
archived log for thread 1 with sequence 1725 is already on disk as file /u05/oradata/CORE/CORE_17251807276264.ARC
archived log for thread 1 with sequence 1726 is already on disk as file /u05/oradata/CORE/CORE_17261807276264.ARC
archived log for thread 1 with sequence 1727 is already on disk as file /u05/oradata/CORE/CORE_17271807276264.ARC
archived log for thread 1 with sequence 1728 is already on disk as file /u05/oradata/CORE/CORE_17281807276264.ARC
archived log for thread 1 with sequence 1729 is already on disk as file /u05/oradata/CORE/CORE_17291807276264.ARC
archived log for thread 1 with sequence 1730 is already on disk as file /u05/oradata/CORE/CORE_17301807276264.ARC
archived log for thread 1 with sequence 1731 is already on disk as file /u05/oradata/CORE/CORE_17311807276264.ARC
archived log for thread 1 with sequence 1732 is already on disk as file /u05/oradata/CORE/CORE_17321807276264.ARC
archived log for thread 1 with sequence 1733 is already on disk as file /u05/oradata/CORE/CORE_17331807276264.ARC
archived log for thread 1 with sequence 1734 is already on disk as file /u05/oradata/CORE/CORE_17341807276264.ARC
archived log for thread 1 with sequence 1735 is already on disk as file /u05/oradata/CORE/CORE_17351807276264.ARC
archived log for thread 1 with sequence 1736 is already on disk as file /u05/oradata/CORE/CORE_17361807276264.ARC
archived log for thread 1 with sequence 1737 is already on disk as file /u05/oradata/CORE/CORE_17371807276264.ARC
archived log for thread 1 with sequence 1738 is already on disk as file /u05/oradata/CORE/CORE_17381807276264.ARC
archived log for thread 1 with sequence 1739 is already on disk as file /u05/oradata/CORE/CORE_17391807276264.ARC
archived log for thread 1 with sequence 1740 is already on disk as file /u05/oradata/CORE/CORE_17401807276264.ARC
archived log for thread 1 with sequence 1741 is already on disk as file /u05/oradata/CORE/CORE_17411807276264.ARC
archived log for thread 1 with sequence 1742 is already on disk as file /u05/oradata/CORE/CORE_17421807276264.ARC
archived log for thread 1 with sequence 1743 is already on disk as file /u05/oradata/CORE/CORE_17431807276264.ARC
archived log for thread 1 with sequence 1744 is already on disk as file /u05/oradata/CORE/CORE_17441807276264.ARC
channel ORA_AUX_DISK_1: starting archived log restore to default destination
channel ORA_AUX_DISK_1: restoring archived log
archived log thread=1 sequence=1710
channel ORA_AUX_DISK_1: reading from backup piece /oraclebackup/CORE/ARC_1HR_CORE_16022013_5jo24jp8_179_1
channel ORA_AUX_DISK_2: starting archived log restore to default destination
channel ORA_AUX_DISK_2: restoring archived log
archived log thread=1 sequence=1711
channel ORA_AUX_DISK_2: restoring archived log
archived log thread=1 sequence=1712
channel ORA_AUX_DISK_2: restoring archived log
archived log thread=1 sequence=1713
channel ORA_AUX_DISK_2: restoring archived log
archived log thread=1 sequence=1714
channel ORA_AUX_DISK_2: restoring archived log
archived log thread=1 sequence=1715
channel ORA_AUX_DISK_2: restoring archived log
archived log thread=1 sequence=1716
channel ORA_AUX_DISK_2: restoring archived log
archived log thread=1 sequence=1717
channel ORA_AUX_DISK_2: reading from backup piece /oraclebackup/CORE/ARC_1HR_CORE_18022013_5ko296uf_180_1
channel ORA_AUX_DISK_1: piece handle=/oraclebackup/CORE/ARC_1HR_CORE_16022013_5jo24jp8_179_1 tag=ARC_1HR
channel ORA_AUX_DISK_1: restored backup piece 1
channel ORA_AUX_DISK_1: restore complete, elapsed time: 00:00:01
archived log file name=/u05/oradata/CORE/CORE_DUP/CORE_DUP17101807276264.ARC thread=1 sequence=1710
channel clone_default: deleting archived log(s)
archived log file name=/u05/oradata/CORE/CORE_DUP/CORE_DUP17101807276264.ARC RECID=3041 STAMP=807724360
channel ORA_AUX_DISK_2: piece handle=/oraclebackup/CORE/ARC_1HR_CORE_18022013_5ko296uf_180_1 tag=ARC_1HR
channel ORA_AUX_DISK_2: restored backup piece 1
channel ORA_AUX_DISK_2: restore complete, elapsed time: 00:00:08
archived log file name=/u05/oradata/CORE/CORE_DUP/CORE_DUP17111807276264.ARC thread=1 sequence=1711
channel clone_default: deleting archived log(s)
archived log file name=/u05/oradata/CORE/CORE_DUP/CORE_DUP17111807276264.ARC RECID=3042 STAMP=807724362
archived log file name=/u05/oradata/CORE/CORE_DUP/CORE_DUP17121807276264.ARC thread=1 sequence=1712
channel clone_default: deleting archived log(s)
archived log file name=/u05/oradata/CORE/CORE_DUP/CORE_DUP17121807276264.ARC RECID=3043 STAMP=807724363
archived log file name=/u05/oradata/CORE/CORE_DUP/CORE_DUP17131807276264.ARC thread=1 sequence=1713
channel clone_default: deleting archived log(s)
archived log file name=/u05/oradata/CORE/CORE_DUP/CORE_DUP17131807276264.ARC RECID=3044 STAMP=807724367
archived log file name=/u05/oradata/CORE/CORE_DUP/CORE_DUP17141807276264.ARC thread=1 sequence=1714
channel clone_default: deleting archived log(s)
archived log file name=/u05/oradata/CORE/CORE_DUP/CORE_DUP17141807276264.ARC RECID=3048 STAMP=807724367
archived log file name=/u05/oradata/CORE/CORE_DUP/CORE_DUP17151807276264.ARC thread=1 sequence=1715
channel clone_default: deleting archived log(s)
archived log file name=/u05/oradata/CORE/CORE_DUP/CORE_DUP17151807276264.ARC RECID=3046 STAMP=807724367
archived log file name=/u05/oradata/CORE/CORE_DUP/CORE_DUP17161807276264.ARC thread=1 sequence=1716
channel clone_default: deleting archived log(s)
archived log file name=/u05/oradata/CORE/CORE_DUP/CORE_DUP17161807276264.ARC RECID=3045 STAMP=807724367
archived log file name=/u05/oradata/CORE/CORE_DUP/CORE_DUP17171807276264.ARC thread=1 sequence=1717
channel clone_default: deleting archived log(s)
archived log file name=/u05/oradata/CORE/CORE_DUP/CORE_DUP17171807276264.ARC RECID=3047 STAMP=807724367
archived log file name=/u05/oradata/CORE/CORE_17181807276264.ARC thread=1 sequence=1718
archived log file name=/u05/oradata/CORE/CORE_17191807276264.ARC thread=1 sequence=1719
archived log file name=/u05/oradata/CORE/CORE_17201807276264.ARC thread=1 sequence=1720
archived log file name=/u05/oradata/CORE/CORE_17211807276264.ARC thread=1 sequence=1721
archived log file name=/u05/oradata/CORE/CORE_17221807276264.ARC thread=1 sequence=1722
archived log file name=/u05/oradata/CORE/CORE_17231807276264.ARC thread=1 sequence=1723
archived log file name=/u05/oradata/CORE/CORE_17241807276264.ARC thread=1 sequence=1724
archived log file name=/u05/oradata/CORE/CORE_17251807276264.ARC thread=1 sequence=1725
archived log file name=/u05/oradata/CORE/CORE_17261807276264.ARC thread=1 sequence=1726
archived log file name=/u05/oradata/CORE/CORE_17271807276264.ARC thread=1 sequence=1727
archived log file name=/u05/oradata/CORE/CORE_17281807276264.ARC thread=1 sequence=1728
archived log file name=/u05/oradata/CORE/CORE_17291807276264.ARC thread=1 sequence=1729
archived log file name=/u05/oradata/CORE/CORE_17301807276264.ARC thread=1 sequence=1730
archived log file name=/u05/oradata/CORE/CORE_17311807276264.ARC thread=1 sequence=1731
archived log file name=/u05/oradata/CORE/CORE_17321807276264.ARC thread=1 sequence=1732
archived log file name=/u05/oradata/CORE/CORE_17331807276264.ARC thread=1 sequence=1733
archived log file name=/u05/oradata/CORE/CORE_17341807276264.ARC thread=1 sequence=1734
archived log file name=/u05/oradata/CORE/CORE_17351807276264.ARC thread=1 sequence=1735
archived log file name=/u05/oradata/CORE/CORE_17361807276264.ARC thread=1 sequence=1736
archived log file name=/u05/oradata/CORE/CORE_17371807276264.ARC thread=1 sequence=1737
archived log file name=/u05/oradata/CORE/CORE_17381807276264.ARC thread=1 sequence=1738
archived log file name=/u05/oradata/CORE/CORE_17391807276264.ARC thread=1 sequence=1739
archived log file name=/u05/oradata/CORE/CORE_17401807276264.ARC thread=1 sequence=1740
archived log file name=/u05/oradata/CORE/CORE_17411807276264.ARC thread=1 sequence=1741
archived log file name=/u05/oradata/CORE/CORE_17421807276264.ARC thread=1 sequence=1742
archived log file name=/u05/oradata/CORE/CORE_17431807276264.ARC thread=1 sequence=1743
archived log file name=/u05/oradata/CORE/CORE_17441807276264.ARC thread=1 sequence=1744
media recovery complete, elapsed time: 00:00:33
Finished recover at 18-FEB-13
contents of Memory Script:
shutdown clone immediate;
startup clone nomount;
sql clone "alter system set db_name =
''CORE_DUP'' comment=
''Reset to original value by RMAN'' scope=spfile";
sql clone "alter system reset db_unique_name scope=spfile";
shutdown clone immediate;
startup clone nomount;
executing Memory Script
database dismounted
Oracle instance shut down
connected to auxiliary database (not started)
Oracle instance started
Total System Global Area 4275781632 bytes
Fixed Size 2213632 bytes
Variable Size 838863104 bytes
Database Buffers 3422552064 bytes
Redo Buffers 12152832 bytes
sql statement: alter system set db_name = ''CORE_DUP'' comment= ''Reset to original value by RMAN'' scope=spfile
sql statement: alter system reset db_unique_name scope=spfile
Oracle instance shut down
connected to auxiliary database (not started)
Oracle instance started
Total System Global Area 4275781632 bytes
Fixed Size 2213632 bytes
Variable Size 838863104 bytes
Database Buffers 3422552064 bytes
Redo Buffers 12152832 bytes
sql statement: CREATE CONTROLFILE REUSE SET DATABASE "CORE_DUP" RESETLOGS ARCHIVELOG
MAXLOGFILES 32
MAXLOGMEMBERS 4
MAXDATAFILES 500
MAXINSTANCES 1
MAXLOGHISTORY 2298
LOGFILE
GROUP 1 ( '/u02/oradata/CORE/CORE_DUP/redo01a.log', '/u03/oradata/CORE/CORE_DUP/redo01b.log' ) SIZE 10 M REUSE,
GROUP 2 ( '/u02/oradata/CORE/CORE_DUP/redo02a.log', '/u03/oradata/CORE/CORE_DUP/redo02b.log' ) SIZE 10 M REUSE,
GROUP 3 ( '/u02/oradata/CORE/CORE_DUP/redo03a.log', '/u03/oradata/CORE/CORE_DUP/redo03b.log' ) SIZE 10 M REUSE
DATAFILE
'/u04/oradata/CORE/CORE_DUP/system01.dbf'
CHARACTER SET AL32UTF8
contents of Memory Script:
set newname for tempfile 1 to
"/u04/oradata/CORE/CORE_DUP/temp01.dbf";
switch clone tempfile all;
catalog clone datafilecopy "/u04/oradata/CORE/CORE_DUP/sysaux01.dbf",
"/u04/oradata/CORE/CORE_DUP/users01.dbf",
"/u04/oradata/CORE/CORE_DUP/users02.dbf",
"/u04/oradata/CORE/CORE_DUP/users03.dbf",
"/u04/oradata/CORE/CORE_DUP/undotbs_new01.dbf";
switch clone datafile all;
executing Memory Script
executing command: SET NEWNAME
renamed tempfile 1 to /u04/oradata/CORE/CORE_DUP/temp01.dbf in control file
cataloged datafile copy
datafile copy file name=/u04/oradata/CORE/CORE_DUP/sysaux01.dbf RECID=1 STAMP=807724423
cataloged datafile copy
datafile copy file name=/u04/oradata/CORE/CORE_DUP/users01.dbf RECID=2 STAMP=807724423
cataloged datafile copy
datafile copy file name=/u04/oradata/CORE/CORE_DUP/users02.dbf RECID=3 STAMP=807724423
cataloged datafile copy
datafile copy file name=/u04/oradata/CORE/CORE_DUP/users03.dbf RECID=4 STAMP=807724423
cataloged datafile copy
datafile copy file name=/u04/oradata/CORE/CORE_DUP/undotbs_new01.dbf RECID=5 STAMP=807724423
datafile 2 switched to datafile copy
input datafile copy RECID=1 STAMP=807724423 file name=/u04/oradata/CORE/CORE_DUP/sysaux01.dbf
datafile 4 switched to datafile copy
input datafile copy RECID=2 STAMP=807724423 file name=/u04/oradata/CORE/CORE_DUP/users01.dbf
datafile 5 switched to datafile copy
input datafile copy RECID=3 STAMP=807724423 file name=/u04/oradata/CORE/CORE_DUP/users02.dbf
datafile 6 switched to datafile copy
input datafile copy RECID=4 STAMP=807724423 file name=/u04/oradata/CORE/CORE_DUP/users03.dbf
datafile 9 switched to datafile copy
input datafile copy RECID=5 STAMP=807724423 file name=/u04/oradata/CORE/CORE_DUP/undotbs_new01.dbf
contents of Memory Script:
Alter clone database open resetlogs;
executing Memory Script
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-00601: fatal error in recovery manager
RMAN-03004: fatal error during execution of command
RMAN-10041: Could not re-create polling channel context following failure.
RMAN-10024: error setting up for rpc polling
RMAN-10005: error opening cursor
RMAN-10002: ORACLE error: ORA-03114: not connected to ORACLE
RMAN-03002: failure of Duplicate Db command at 02/18/2013 15:53:50
RMAN-03015: error occurred in stored script Memory Script
RMAN-06136: ORACLE error from auxiliary database: ORA-01092: ORACLE instance terminated. Disconnection forced
ORA-30012: undo tablespace 'UNDOTBS' does not exist or of wrong type
Process ID: 3670170
Session ID: 33 Serial number: 7
oracore@cph-core-db01-s $ -
Doubt regarding ORA-30036: unable to extend segment by 8 in undo tablespace
I am using 11g Release 1 Database .
I have to analyze the performance of two tables of different designs which serve the same purpose and come up with the design which is efficient .
SQL> desc staging_dict
Name Null? Type
SNO NUMBER
CODE_FRAGMENTS CLOB
CODE_FRAGMENTS_U CLOB
CODE_FRAGMENTS_D CLOB
CODE_FRAGMENTS_DO CLOB
SQL> desc staging_dict1
Name Null? Type
SNO NUMBER
CODE_FRAGMENTS CLOB
CODE_FRAGMENTS_UD CLOB
CODE_TYPE VARCHAR2(5 CHAR)Initially I tried inserting a few thousand records into both the tables . Then I did some conversion on one column and I populate the result on other column of the same table . So I update the table in bulk mode and I commit for every thousand records .
I have a undo tablespace of 2G with undo_retention=900 , retention guratantee is not set for the undo tablespace .
When I tried the conversion and update on the first table (STAGING_DICT) it took more time for around 2500 records compared to other table and when I increased the number of records to 10000 it threw an error
ORA-30036: unable to extend segment by 8 in undo tablespace 'UNDOTBS'
But I didn't come across this error when I tried the conversion and update on the table for the same 2500 records (STAGING_DICT1) and it was also 10 times faster .
My doubt is does the error ORA-30036 occur because it is saving the undo image of all the four clob columns though I am doing conversion on one column and updating the other column (using only two columns in the update and only one column is affected by update command) ?
Also how is that having less CLOB rows prove more effective by adding one more VARCHAR column which differentiates the code_frament type in the STAGING_DICT1 table than having it as more CLOB columns as in STAGING_DICT table ?Don't you think the error OP reported is kind of weird?
Because as you said, Oracle stores "undo" of lob in user tablespace not undo tablespace if the lob is stored out-of-line.
1. If the size of lob was small, small size of undo would be stored into undo tablespace,
and OP would'nt have undo tablespace shortage problem.
(How does small lob flood undo tablespace?)
2. If the size of lob was big, OP would have 01555 error on user tablespace not undo tablespace shortage error.
So, i think there are 2 theories that can explain this abnormality.
1. OP hit the bug of massive undo generation.
2. OP is using securefile which is 11g new feature.
Oracle documents says that undo for securefile lob is stored in "undo" tablespace, not user tablespace.
But unfortunately, i'm not sture about this coz i didn't try it myself -
ORA-30036: unable to extend segment by string in undo tablespace "string"
Hi hussein/helios,
EBS 11i
RHEL 4.6
Our users in Inventory - Order Management Module , tried to enter and save transactions, but they encounter this ORA-30036 error:
Unable to extend segment by 8 in undo tablespace 'APPS_UNDOTS1'
in Package OE_ORDER_WF_UTIL Procedure Start_FlowIn your experience how do you tune this package for an appropriate UNDO? What is the appropriate size for my UNDO? Do I allow it to
to autoextend? or just allocate enough space.
Thanks a lot,
Ms Kuser_unlimited wrote:
Hi new2,
I don't get it clearly :( . I guess oracle already tuned these apps tablespaces extents. I just want to know if its >ok to increase it.Not all tablespace i found is tuned.
Do you have a productions EBS 11i? EBS R12 RUP 6 DB 10.2.0.0
what is the size of your UNDO?4GB
>
>
ThanksUNDO Tablespaces should contain between 1024 and 4096 extents
To check for UNDO and TEMP tablespaces that do not obey the extent size rules you can run the following query:
select tablespace_name, initial_extent, next_extent, pct_increase, min_extlen
from dba_tablespaces t,
(select tablespace_name tbspc,
sum(bytes) tbspc_sz,
count(*) num_files,
sum(bytes)/sum(blocks) blk_sz
from dba_data_files
group by tablespace_name) f
where
( initial_extent < (tbspc_sz - blk_sz * num_files) / 4096
or initial_extent > (tbspc_sz - blk_sz * num_files) / 1024
or next_extent != initial_extent
or pct_increase != 0
or min_extlen != initial_extent)
and tablespace_name = tbspc
and tablespace_name != 'SYSTEM'
and ( contents = 'TEMPORARY'
or tablespace_name in (select tablespace_name from dba_rollback_segs));My cases i found iitial extent 65536 and min_exlen 65536
check with this query then decide what will u do...
HTH -
ORA-30036: unable to extend segment by 8 in undo tablespace 'UNDOTBS1'
Hi experts,
I'm getting this error
"ORA-30036: unable to extend segment by 8 in undo tablespace 'UNDOTBS1'"
will you please tell me the reason and suggest me, what to do.
OS - SunOS 5.10
oracle - 10.2.0.3.0Hallo.
I have this problem 30036 after this request (ver. 10.2):
DELETE FROM AUDITDBA.SEOSDATA where COMPUTERNAME ='xxxxx' AND TIMSTAMP >= '18-03-2011' (! number of rows is less as 2 000 000)
I tried do this:
ALTER SYSTEM SET UNDO_RETENTION = 5;
But after next action "DELETE" again problem 30036..
Here is a "space status" from the system:
TABLESPACE_NAME VOLNE_MIESTO
CA_AUDIT 3714,1875 MB
SYSAUX 42,1875 MB
SYSTEM 5,25 MB
UNDO_TEMP 7998,0625 MB
USERS 999,125 MB
It's clear for me that datafile UNDOTBS is small but I have same questions:
1. What You recommend - use autoextend on for the UNDOTBS datafile or extend it manualy?
2. What size You recommend for the UNDOTBS when I have DB size cca 350 GB, into DB incomming cca 50 events (rows) per second and I need remove from this DB aproximetly 1/2 numbers of rows (old data)
3. Recommend me best way how I can remove old data from DB without problems as "30036"...
Thank You in advance
Peter -
Error During Installation: ORA-02180: invalid option for CREATE TABLESPACE
Hi all,
This is our enviroment,
Windows 2000 Service Pack 4
We are installing SAP R/3 Enterprise 4.7 Ext. 200 SR1
First we installed:
Oracle: 9.2
Patch: 9.2.0.7
SAP Central Instance
Now we are installing the DB Instance, but it gives this error:
INFO 2007-11-22 16:58:20
Working directory changed to C:\Program Files\sapinst_instdir\R3E47X2\SYSTEM\ABAP\ORA\NUC\DB.
ERROR 2007-11-22 16:58:21
CJS-00084 SQL statement or script failed.DIAGNOSIS: Error message: ORA-02180: invalid option for CREATE TABLESPACE
We are in the step 19 of 34
Create Tablespaces
Please some tips.
Regards,
ErickHi! Thanks a lot for the reply.
This is our <b>ora_sql_results.log</b>
================================================================================
2007-11-23, 07:31:09 SAPINST ORACLE start logging for
connect / as sysdba ;
set newpage 0
set space 0
set pagesize 0
set linesize 32767
set markup HTML off
set heading off
set verify off
set feedback off
set trimspool on
set sqlprompt SQL>
set termout on
set verify off
set echo off
spool ora_query3_tmp0_1.res
SELECT STATUS FROM V$INSTANCE;
spool off
exit;
Output of SQL executing program:
SQL*Plus: Release 9.2.0.7.0 - Production on Fri Nov 23 07:31:09 2007
Copyright (c) 1982, 2002, Oracle Corporation. All rights reserved.
Connected.
OPEN
Disconnected from Oracle9i Enterprise Edition Release 9.2.0.7.0 - Production
With the Partitioning, OLAP and Oracle Data Mining options
JServer Release 9.2.0.7.0 - Production
SAPINST: End of output of SQL executing program D:\oracle\TVD\920/bin/sqlplus.
2007-11-23, 07:31:10 SAPINST ORACLE stop logging
================================================================================
2007-11-23, 07:31:10 SAPINST ORACLE start logging for
connect / as sysdba ;
CREATE TABLESPACE PSAP@SCHEMAID@ DATAFILE 'E:\oracle\TVD\sapdata4\psap@schemaid@_1\psap@[email protected]' SIZE 2000M REUSE AUTOEXTEND ON NEXT 20M MAXSIZE 10000M LOGGING ONLINE PERMANENT EXTENT MANAGEMENT LOCAL AUTOALLOCATE SEGMENT SPACE MANAGEMENT AUTO ;
exit;
Output of SQL executing program:
SQL*Plus: Release 9.2.0.7.0 - Production on Fri Nov 23 07:31:10 2007
Copyright (c) 1982, 2002, Oracle Corporation. All rights reserved.
Connected.
CREATE TABLESPACE PSAP@SCHEMAID@ DATAFILE 'E:\oracle\TVD\sapdata4\psap@schemaid@_1\psap@[email protected]' SIZE 2000M REUSE AUTOEXTEND ON NEXT 20M MAXSIZE 10000M LOGGING ONLINE PERMANENT EXTENT MANAGEMENT LOCAL AUTOALLOCATE SEGMENT SPACE MANAGEMENT AUTO
ERROR at line 1:
ORA-02180: invalid option for CREATE TABLESPACE
Disconnected from Oracle9i Enterprise Edition Release 9.2.0.7.0 - Production
With the Partitioning, OLAP and Oracle Data Mining options
JServer Release 9.2.0.7.0 - Production
SAPINST: End of output of SQL executing program D:\oracle\TVD\920/bin/sqlplus.
SAPINST found errors.
SAPINST The current process environment may be found in sapinst_ora_environment.log.
2007-11-23, 07:31:10 SAPINST ORACLE stop logging
And this is <b>our alert_SID.log</b>
Dump file d:\oracle\tvd\saptrace\background\alert_tvd.log
Thu Nov 22 16:27:45 2007
ORACLE V9.2.0.7.0 - Production vsnsta=0
vsnsql=12 vsnxtr=3
Windows 2000 Version 5.0 Service Pack 4, CPU type 586
Thu Nov 22 16:27:45 2007
Starting ORACLE instance (normal)
LICENSE_MAX_SESSION = 0
LICENSE_SESSIONS_WARNING = 0
SCN scheme 2
LICENSE_MAX_USERS = 0
SYS auditing is disabled
Starting up ORACLE RDBMS Version: 9.2.0.7.0.
System parameters with non-default values:
processes = 80
sessions = 96
shared_pool_size = 251658240
sga_max_size = 546906620
shared_pool_reserved_size= 24363663
enqueue_resources = 8000
control_files = E:\oracle\TVD\origlogA\cntrl\cntrlTVD.dbf, E:\oracle\TVD\sapdata1\system_1\cntrl\cntrlTVD.dbf, D:\oracle\TVD\saparch\cntrl\cntrlTVD.dbf
db_block_size = 8192
db_cache_size = 251658240
compatible = 9.2.0
log_archive_start = TRUE
log_archive_dest = D:\oracle\TVD\oraarch\TVDarch
log_buffer = 1048576
log_checkpoint_interval = 0
db_files = 254
fast_start_mttr_target = 900
log_checkpoints_to_alert = TRUE
control_file_record_keep_time= 30
dml_locks = 4000
transaction_auditing = FALSE
undo_management = AUTO
undo_tablespace = PSAPUNDO
undo_retention = 43200
remote_os_authent = TRUE
hash_join_enabled = FALSE
background_dump_dest = D:\oracle\TVD\saptrace\background
user_dump_dest = D:\oracle\TVD\saptrace\usertrace
core_dump_dest = D:\oracle\TVD\saptrace\background
optimizer_features_enable= 9.2.0
sort_area_size = 2097152
sort_area_retained_size = 0
db_name = TVD
open_cursors = 800
pga_aggregate_target = 324848844
workarea_size_policy = AUTO
statistics_level = typical
PMON started with pid=2
DBW0 started with pid=3
LGWR started with pid=4
CKPT started with pid=5
SMON started with pid=6
RECO started with pid=7
Thu Nov 22 16:27:48 2007
ARCH: STARTING ARCH PROCESSES
ARC0 started with pid=8
ARC1 started with pid=9
Thu Nov 22 16:27:48 2007
ARC0: Archival started
Thu Nov 22 16:27:48 2007
ARCH: STARTING ARCH PROCESSES COMPLETE
Thu Nov 22 16:27:48 2007
ARC1: Archival started
Thu Nov 22 16:27:48 2007
ARC0: Becoming the 'no FAL' ARCH
Thu Nov 22 16:27:48 2007
ARC1: Becoming the heartbeat ARCH
Thu Nov 22 16:27:48 2007
ARC0: Becoming the 'no FAL' ARCHARC0: Thread not mounted
Thu Nov 22 16:27:48 2007
ARC1: Becoming the heartbeat ARCHARC1: Thread not mounted
Thu Nov 22 16:27:49 2007
alter database mount exclusive
Thu Nov 22 16:27:49 2007
ORA-00202: controlfile: 'E:\oracle\TVD\origlogA\cntrl\cntrlTVD.dbf'
ORA-27041: unable to open file
OSD-04002: unable to open file
O/S-Error: (OS 2) The system cannot find the file specified.
Thu Nov 22 16:27:50 2007
ORA-205 signalled during: alter database mount exclusive...
Shutting down instance (abort)
License high water mark = 1
Instance terminated by USER, pid = 1768
Thu Nov 22 16:28:05 2007
Starting ORACLE instance (normal)
LICENSE_MAX_SESSION = 0
LICENSE_SESSIONS_WARNING = 0
SCN scheme 2
LICENSE_MAX_USERS = 0
SYS auditing is disabled
Starting up ORACLE RDBMS Version: 9.2.0.7.0.
System parameters with non-default values:
processes = 80
sessions = 96
shared_pool_size = 251658240
sga_max_size = 546906620
shared_pool_reserved_size= 24363663
enqueue_resources = 8000
control_files = E:\oracle\TVD\origlogA\cntrl\cntrlTVD.dbf, E:\oracle\TVD\sapdata1\system_1\cntrl\cntrlTVD.dbf, D:\oracle\TVD\saparch\cntrl\cntrlTVD.dbf
db_block_size = 8192
db_cache_size = 251658240
compatible = 9.2.0
log_archive_start = TRUE
log_archive_dest = D:\oracle\TVD\oraarch\TVDarch
log_buffer = 1048576
log_checkpoint_interval = 0
db_files = 254
fast_start_mttr_target = 900
log_checkpoints_to_alert = TRUE
control_file_record_keep_time= 30
dml_locks = 4000
transaction_auditing = FALSE
undo_management = AUTO
undo_tablespace = PSAPUNDO
undo_retention = 43200
remote_os_authent = TRUE
hash_join_enabled = FALSE
background_dump_dest = D:\oracle\TVD\saptrace\background
user_dump_dest = D:\oracle\TVD\saptrace\usertrace
core_dump_dest = D:\oracle\TVD\saptrace\background
optimizer_features_enable= 9.2.0
sort_area_size = 2097152
sort_area_retained_size = 0
db_name = TVD
open_cursors = 800
pga_aggregate_target = 324848844
workarea_size_policy = AUTO
statistics_level = typical
PMON started with pid=2
DBW0 started with pid=3
LGWR started with pid=4
CKPT started with pid=5
SMON started with pid=6
RECO started with pid=7
Thu Nov 22 16:28:08 2007
ARCH: STARTING ARCH PROCESSES
ARC0 started with pid=8
ARC0: Archival started
ARC1 started with pid=9
Thu Nov 22 16:28:08 2007
ARCH: STARTING ARCH PROCESSES COMPLETE
Thu Nov 22 16:28:08 2007
ARC0: Becoming the 'no FAL' ARCH
ARC0: Becoming the 'no FAL' ARCHARC0: Thread not mounted
Thu Nov 22 16:28:09 2007
ARC1: Archival started
Thu Nov 22 16:28:09 2007
ARC1: Becoming the heartbeat ARCH
ARC1: Becoming the heartbeat ARCHARC1: Thread not mounted
Thu Nov 22 16:28:11 2007
CREATE DATABASE TVD CONTROLFILE REUSE MAXLOGFILES 255 MAXLOGMEMBERS 3 MAXLOGHISTORY 1000 MAXDATAFILES 254 MAXINSTANCES 50 NOARCHIVELOG CHARACTER SET WE8DEC NATIONAL CHARACTER SET UTF8 DATAFILE 'E:\oracle\TVD\sapdata1\system_1\system.data1' SIZE 550M REUSE AUTOEXTEND ON NEXT 20M MAXSIZE 10000M EXTENT MANAGEMENT LOCAL DEFAULT TEMPORARY TABLESPACE PSAPTEMP TEMPFILE 'E:\oracle\TVD\sapdata3\temp_1\temp.data1' SIZE 540M REUSE AUTOEXTEND ON NEXT 20M MAXSIZE 10000M UNDO TABLESPACE PSAPUNDO DATAFILE 'E:\oracle\TVD\sapdata2\undo_1\undo.data1' SIZE 700M REUSE AUTOEXTEND ON NEXT 20M MAXSIZE 10000M
LOGFILE GROUP 1 ('E:
oracle/TVD/origlogA/log_g11m1.dbf',
'D:
oracle/TVD/mirrlogA/log_g11m2.dbf') SIZE 50M REUSE ,
GROUP 2 ('E:
oracle/TVD/origlogB/log_g12m1.dbf',
'D:
oracle/TVD/mirrlogB/log_g12m2.dbf') SIZE 50M REUSE ,
GROUP 3 ('E:
oracle/TVD/origlogA/log_g13m1.dbf',
'D:
oracle/TVD/mirrlogA/log_g13m2.dbf') SIZE 50M REUSE ,
GROUP 4 ('E:
oracle/TVD/origlogB/log_g14m1.dbf',
'D:
oracle/TVD/mirrlogB/log_g14m2.dbf') SIZE 50M REUSE
Thu Nov 22 16:28:12 2007
Database mounted in Exclusive Mode.
Thu Nov 22 16:28:29 2007
Successful mount of redo thread 1, with mount id 1434613531
Assigning activation ID 1434613531 (0x5582771b)
Thread 1 opened at log sequence 1
Thu Nov 22 16:28:30 2007
ARC1: Media recovery disabled
Thu Nov 22 16:28:31 2007
Current log# 1 seq# 1 mem# 0: E:\ORACLE\TVD\ORIGLOGA\LOG_G11M1.DBF
Current log# 1 seq# 1 mem# 1: D:\ORACLE\TVD\MIRRLOGA\LOG_G11M2.DBF
Successful open of redo thread 1
Thu Nov 22 16:28:31 2007
ARC0: Media recovery disabled
Thu Nov 22 16:28:31 2007
SMON: enabling cache recovery
Thu Nov 22 16:28:32 2007
WARNING: Default passwords for SYS and SYSTEM will be used.
Please change the passwords.
Thu Nov 22 16:28:32 2007
create tablespace SYSTEM datafile 'E:\oracle\TVD\sapdata1\system_1\system.data1' SIZE 550M REUSE AUTOEXTEND ON NEXT 20M MAXSIZE 10000M
EXTENT MANAGEMENT LOCAL online
Thu Nov 22 16:28:51 2007
Completed: create tablespace SYSTEM datafile 'E:\oracle\TVD\
Thu Nov 22 16:28:51 2007
create rollback segment SYSTEM tablespace SYSTEM
storage (initial 50K next 50K)
Completed: create rollback segment SYSTEM tablespace SYSTEM
Thu Nov 22 16:29:08 2007
ARC1: Media recovery disabled
Thu Nov 22 16:29:10 2007
CREATE UNDO TABLESPACE PSAPUNDO DATAFILE 'E:\oracle\TVD\sapdata2\undo_1\undo.data1' SIZE 700M REUSE AUTOEXTEND ON NEXT 20M MAXSIZE 10000M
Thu Nov 22 16:29:35 2007
Successfully onlined Undo Tablespace 1.
Completed: CREATE UNDO TABLESPACE PSAPUNDO DATAFILE 'E:\orac
Thu Nov 22 16:29:36 2007
CREATE TEMPORARY TABLESPACE PSAPTEMP TEMPFILE 'E:\oracle\TVD\sapdata3\temp_1\temp.data1' SIZE 540M REUSE AUTOEXTEND ON NEXT 20M MAXSIZE 10000M
Completed: CREATE TEMPORARY TABLESPACE PSAPTEMP TEMPFILE 'E:
Thu Nov 22 16:29:36 2007
ALTER DATABASE DEFAULT TEMPORARY TABLESPACE PSAPTEMP
Completed: ALTER DATABASE DEFAULT TEMPORARY TABLESPACE PSAPTE
Thu Nov 22 16:29:39 2007
SMON: enabling tx recovery
Thu Nov 22 16:29:39 2007
Beginning local checkpoint up to RBA [0x1.538b.10], SCN: 0x0000.000019d9
Completed checkpoint up to RBA [0x1.538b.10], SCN: 0x0000.000019d9
kwqplbsc: open notifier exception err 604
replication_dependency_tracking turned off (no async multimaster replication found)
Completed: CREATE DATABASE TVD CONTROLFILE REUSE MAXLOGFILES
Thu Nov 22 16:30:08 2007
ARC1: Media recovery disabled
Thu Nov 22 16:31:08 2007
ARC1: Media recovery disabled
Thu Nov 22 16:31:28 2007
Beginning log switch checkpoint up to RBA [0x2.2.10], SCN: 0x0000.00006489
Thread 1 advanced to log sequence 2
Thu Nov 22 16:31:28 2007
ARC1: Media recovery disabled
Thu Nov 22 16:31:29 2007
Current log# 2 seq# 2 mem# 0: E:\ORACLE\TVD\ORIGLOGB\LOG_G12M1.DBF
Current log# 2 seq# 2 mem# 1: D:\ORACLE\TVD\MIRRLOGB\LOG_G12M2.DBF
Thu Nov 22 16:32:08 2007
ARC1: Media recovery disabled
Thu Nov 22 16:33:08 2007
ARC0: Media recovery disabled
Thu Nov 22 16:33:08 2007
ARC1: Media recovery disabled
Thu Nov 22 16:33:16 2007
Completed checkpoint up to RBA [0x2.2.10], SCN: 0x0000.00006489
Thu Nov 22 16:33:26 2007
Beginning log switch checkpoint up to RBA [0x3.2.10], SCN: 0x0000.00009227
Thread 1 advanced to log sequence 3
Thu Nov 22 16:33:26 2007
ARC0: Media recovery disabled
Thu Nov 22 16:33:26 2007
Current log# 3 seq# 3 mem# 0: E:\ORACLE\TVD\ORIGLOGA\LOG_G13M1.DBF
Current log# 3 seq# 3 mem# 1: D:\ORACLE\TVD\MIRRLOGA\LOG_G13M2.DBF
Thu Nov 22 16:34:08 2007
ARC1: Media recovery disabled
Thu Nov 22 16:35:08 2007
ARC1: Media recovery disabled
Thu Nov 22 16:35:19 2007
Completed checkpoint up to RBA [0x3.2.10], SCN: 0x0000.00009227
Thu Nov 22 16:35:28 2007
Beginning log switch checkpoint up to RBA [0x4.2.10], SCN: 0x0000.0000b0ac
Thread 1 advanced to log sequence 4
Current log# 4 seq# 4 mem# 0: E:\ORACLE\TVD\ORIGLOGB\LOG_G14M1.DBF
Thu Nov 22 16:35:28 2007
ARC1: Media recovery disabled
Thu Nov 22 16:35:28 2007
Current log# 4 seq# 4 mem# 1: D:\ORACLE\TVD\MIRRLOGB\LOG_G14M2.DBF
Thu Nov 22 16:36:08 2007
ARC1: Media recovery disabled
Thu Nov 22 16:37:08 2007
ARC1: Media recovery disabled
Thu Nov 22 16:38:08 2007
ARC0: Media recovery disabled
Thu Nov 22 16:38:08 2007
ARC1: Media recovery disabled
Thu Nov 22 16:38:51 2007
Completed checkpoint up to RBA [0x4.2.10], SCN: 0x0000.0000b0ac
Thu Nov 22 16:38:59 2007
Beginning log switch checkpoint up to RBA [0x5.2.10], SCN: 0x0000.0000e12b
Thread 1 advanced to log sequence 5
Thu Nov 22 16:38:59 2007
Current log# 1 seq# 5 mem# 0: E:\ORACLE\TVD\ORIGLOGA\LOG_G11M1.DBF
Current log# 1 seq# 5 mem# 1: D:\ORACLE\TVD\MIRRLOGA\LOG_G11M2.DBF
Thu Nov 22 16:39:00 2007
ARC0: Media recovery disabled
Thu Nov 22 16:39:08 2007
ARC1: Media recovery disabled
Thu Nov 22 16:40:08 2007
ARC1: Media recovery disabled
Thu Nov 22 16:41:08 2007
ARC1: Media recovery disabled
Thu Nov 22 16:41:09 2007
Completed checkpoint up to RBA [0x5.2.10], SCN: 0x0000.0000e12b
Thu Nov 22 16:41:18 2007
Beginning log switch checkpoint up to RBA [0x6.2.10], SCN: 0x0000.0000ee94
Thread 1 advanced to log sequence 6
Current log# 2 seq# 6 mem# 0: E:\ORACLE\TVD\ORIGLOGB\LOG_G12M1.DBF
Current log# 2 seq# 6 mem# 1: D:\ORACLE\TVD\MIRRLOGB\LOG_G12M2.DBF
Thu Nov 22 16:41:18 2007
ARC1: Media recovery disabled
Thu Nov 22 16:42:08 2007
Fri Nov 23 07:38:10 2007
ARC1: Media recovery disabled
Regards,
Erick -
ORA-30036: unable to extend segment by 8 in undo tablespace 'APPS_UNDOTS1'
Hi,
A user who is trying to run a report on an EBS system, gets the following error from the application end:
java.sql.SQLException: ORA-30036: unable to extend segment by 8 in undo tablespace 'APPS_UNDOTS1'
I would have expected to see this ORA error in the Oracle database alert log as well, however this is not the case.
I increased the size of the APPS_UNDOTS1 tablespace from 1700mb with autoextend to max 3000mb, however it seems that the tablespace is not extending beyond it's original size of 1700mb. In TOAD, I see that the tablespace has not grown even after the user ran the report again. Any idea why? Is there perhaps something that needs to be adjusted on the application side as well?
Thanks.Hi,
The tablespace is not extending and this error is not written to the alert log, but I found a trace file with the following information....
ORA-30036 happens when trying to extend undo segment SYSSMU91258636580$ (usn=9) by 8 blocks
Reason: Fail to Steal
Current undo tablespace APPS_UNDOTS1 (tsn=1)
undo tablespace current size 218240 blks, maxsize 218240 blks, fixed sized
Undo Retention (reactive): 936, Parameter Undo Retention: 900, Tuned Undo Retention: 936, High threshold Undo Retention: -2
Retention Guarantee FALSE
Does anyone know how to solve this "Fail to Steal" problem?
Btw, the query SELECT DISTINCT STATUS, SUM(BYTES), COUNT(*) FROM DBA_UNDO_EXTENTS GROUP BY STATUS; returns about 55 expired extents, therefore there are still available extents to "steal" from. So why does this fail? -
ORA-30036: unable to extend segment, our UNDO TABLESPACE grow to 500 GB
Our client report that when they run their batch job the error "ORA-30036: unable to extend segment..." came into their log file.
I have checked with alert log but nothing there. We use Oracle 11g on Solaris 10 SPARC.
Any suggestion ?
Thanks & RegardsRefer to
Troubleshooting ORA-30036 - Unable To Extend Undo Tablespace [ID 460481.1]
ORA-30036: unable to extend segment by <N> in undo tablespace '<tname>' [ID 271664.1] -
OEM Upgrade - ORA-30036: unable to extend segment by 8 in undo tablespace
Oem upgrade Installer failed on repository in upgrading to grid Control 10.2.0.5
757921: ORA-30036: unable to extend segment by 8 in undo tablespace 'UNDOTBS'
757922: ORA-06512: at line 117
I added two datafiles to fix this error so I thought I had enough space now - installer failed when upgrading the repository with ORA-30036 unable to extend segment by 8 in undo tablespace 'UNDOTBS', When I hit retry it keeps failing on the same error. The upgrade is in STATUS -3. Could I run this as sysman and then go back to the installer screen and retry again.
execute emd_maintenance.set_comp_status('_
UPGRADE_', EMD_MAINTENANCE.G_STATUS_
CONFIGURED_READY);
If you have any tips going forward pleases let me know.,
JosephHas anyone encountered this error: doing re-installation on OEM upgrade. I can seem to find anything on metallink. There is no error code
txnRemoveConfirmation .
Joseph
Maybe you are looking for
-
Can't change email address in 4.0 Contact book
I need to change my email address in the Sharing palette of the Contact book (as accessed from the Photo Browser). When I highlight my address in the recipient list and then go to Edit, I get a message saying "This contact is used by a print recipie
-
Correcting useful life of an asset in previous year
Hi, We have implemented SAP last year in April at one of our sites. At the time of initial upload of assets, we made a mistake and some of the assets were uploaded with incorrect useful life. Till date every month we were running depreciation based o
-
Boolean values are not displaying correct
hi .. i have created a application which has one report .. in report field there's boolean field (true or false) when i run my application it will show the correct results... but when host the application in IIS7 then the result will not show correct
-
WRT54GL connects via cable, but not wireless
I've got a WRT54GL that I connected via the ethernet cable, but when I try to connect wirelessly it can't. I've tried EasyLink Connect and EasyLink Advisor to try and fix the connection and "unwire" it, but neither were any help. I can setup my other
-
Quick problem... I have a curve 8320. Just got a new laptop, and i lost the software disk for the desktop manager, so i just went online and downloaded it from blackberrys site. So, when i plug the phone in the computer, its saying the computer is re