System tablespace management in oracle 9i

Hi,
I would like to know whether system tablespace in oracle 9i by default is locally managed or dictionary managed

Hi,
I would like to know whether system tablespace in oracle 9i by default is locally managed or dictionary managed SYSTEM tablespace in 9i rdbms can ONLY be dictionary managed.

Similar Messages

Migrating SYSTEM tablespace from DMTS to LMTS in Oracle 9.2.0.7

Migrating SYSTEM tablespace from DMTS to LMTS in Oracle 9.2.0.7 using
brspace -f dbcreate
SAP version: 4.6C
Oracle: 9.2.0.7
OS: AIX 5.3
BRTools: 6.40(42)    /** 6.40(10) or (12) will be sufficient according to SAP ***/
IMPORTANT ***************************************
MUST DO:
1. Create a Full Backup of your system
2. Test your Restore and recovery of your backup.
3. Have a copy of all your tablespaces names on hand
4. Know your SYS and SYSTEM passwords
5. Run CheckDB in DB13 to ensure it is completed successfully with no warnings. This reduce the chance of hitting errors in the process
6. Ensure your UNDO tablespace is big enough
7. OSS 400241 Problems with ops$ or sapr3 connect to Oracle
NOTE: OSS 706625(Read this note)
The migration from a dictionary-managed SYSTEM tablespace to a locally-managed tablespace using the PL/SQL procedure DBMS_SPACE_ADMIN.TABLESPACE_MIGRATE_TO_LOCAL is not supported in the SAP environment.
In UNIX, logon as ora<sid>
run command: brspace -f dbcreate
This command will triggers a Menu. The are seven(7) steps to complete the whole process. Do them in sequence, from step 1 to step 7 faithfully. In Step 1, ensure that your settings of PSAPTEMP, PSAPUNDO etc details such as filenames are correct. The rest I leave it as default and they are fine. Do not change redo log group from 8 to 4 even if you only have 4 redo groups. If not, you might need to restore the system! If the seven steps are complete without errors(warnings is acceptable), congrats. Perform a backup again.
Problems I encountered that caused me to restore system:
1./ Problem: I changed the redo group from 8 to 4 and in the later stage after the tablespaces and files are dropped, the system prompted me that 4 is not acceptable! I can't go back then so a restore is performed.
Solution: Leave the default value 8 as it is
2./ I was using wireless network and the network breaks thus process breaks.
Solution: This process in user-interactive and requires you to input confirmation along the way so do it using LAN.
3./ In the process of dropping tablespace PSAP<SID>, I encountered:
BR0301E SQL error -604 at location BrTspDrop-2
ORA-00601: error occurred at recursive SQL level 1
ORA-01555: snapshot too old: rollback segment number 22 with name '_SYSSMU22$" too small
Solution: I have not fixed this yet but I think it is because my PSAPUNDO is too small(800M) so I will increase it to a bigger value e.g. 5GB
4. Problem: Unable to start sap after successfully migrated. OPS$user problem
Solution: logon as <sid>adm, run R3trans -x in a directory that <sid>adm has read/write permission. R3trans -x will creates a file call trans.log. Read the details and refer to OSS 400241
Result: I have successfully performed this on one(1) system and doing this on the another one currently but encounter Problem 3. Will update this further if there are more findings.
REFERENCE:
OSS 748434 New BRSPACE function "dbcreate" - recreate database
OSS 646681 Reorganizing tables with BRSPACE
OSS 541538 FAX: Reorganizations
Message was edited by:
        Annie Chan
Message was edited by:
        Annie Chan
Message was edited by:
        Annie Chan

The current one I am implementing is a development system. The database is less than 100GB. 800MB of PSAPUNDO is sufficient for our development usage.
Follow up on Problem 3:
I created another undo tablespace PSAPUNDO2(undodata.dbf) with size of 5GB. I switched undo tablespace to PSAPUNDO2 and placed PSAPUNDO(undo.data1) offline. With PSAPUNDO2 online and PSAPUNDO offline, I started brspace -f dbcreate and encountered the error below at Step 2 Export User tablespace:
BR0301E SQL error -376 at location BrStattabCreate-3
ORA-00376: file 17 cannot be read at this time
ORA-01110: data file 17: '/oracle/DVT/sapdata1/undo_1/undo.data1'
ORA-06512: at 'SYS.DBMS_STATS", line 5317
ORA-06512: at line 1
I aborted the process and verified that SAP is able to run with this settings. I started CheckDB in DB13 and it shows me these messages:
BR0301W SQL error -376 at location brc_dblog_open-5
ORA-00376: file 17 cannot be read at this time
ORA-01110: data file 17: '/oracle/DEV/sapdata1/undo_1/undo.data1'
BR0324W Insertion of database log header failed
I don't understand then. I have already switched the undo tablespace from PSAPUNDO to PSAPUNDO2. Why the message above still appears? Once I put PSAPUNDO online, CheckDB completes successfully without warning.
I did show parameter undo_tablespace and the result is PSAPUNDO2(5GB).
So exactly, what's going on? Can anyone advise?
===============================================
I have managed to clear the message in DB13 after dropping PSAPUNDO tablespace including contents and datafiles. This is mentioned is OSS note 600141 pg 8 as below:
Note: You cannot just set the old rollback-tablespace PSAPROLL to offline instead of deleting it properly. This results in ORA-00376 in connection with ORA-01110 error messages. PSAPROLL must remain ONLINE until it is deleted. (Oracle bug 3635653)
Message was edited by:
        Annie Chan

SYSTEM Tablespace Segment Management

When creating a new database (11.1.0.7) on AIX 5.3, what are the benefits of creating a SYSTEM tablespace with MANUAL segment management? This question may not be limited to 11g databases, but I was curious if the SYSTEM tablespace could be set to AUTO segement management and what drawbacks I might see in doing so?
Most of the databases I help manage have been established years ago and most, if not all, are set to MANUAL.
Thanks

This is the default. I do not think you or I know better than the Oracle designers ho to best setup the SYSTEM tablespace. You are best to leave it alone.
SQL> exec print_table('select * from dba_tablespaces where tablespace_name = ''SYSTEM''');
TABLESPACE_NAME               : SYSTEM
BLOCK_SIZE                    : 8192
INITIAL_EXTENT                : 65536
NEXT_EXTENT                   :
MIN_EXTENTS                   : 1
MAX_EXTENTS                   : 2147483645
MAX_SIZE                      : 2147483645
PCT_INCREASE                  :
MIN_EXTLEN                    : 65536
STATUS                        : ONLINE
CONTENTS                      : PERMANENT
LOGGING                       : LOGGING
FORCE_LOGGING                 : NO
EXTENT_MANAGEMENT             : LOCAL
ALLOCATION_TYPE               : SYSTEM
PLUGGED_IN                    : NO
SEGMENT_SPACE_MANAGEMENT      : MANUAL
DEF_TAB_COMPRESSION           : DISABLED
RETENTION                     : NOT APPLY
BIGFILE                       : NO
PREDICATE_EVALUATION          : HOST
ENCRYPTED                     : NO
COMPRESS_FOR                  :
-----------------As you can see, SYSAUX is set up a bit different. System being special, you are best to leave it alone.
SQL> exec print_table('select * from dba_tablespaces where tablespace_name = ''SYSAUX''');
TABLESPACE_NAME               : SYSAUX
BLOCK_SIZE                    : 8192
INITIAL_EXTENT                : 65536
NEXT_EXTENT                   :
MIN_EXTENTS                   : 1
MAX_EXTENTS                   : 2147483645
MAX_SIZE                      : 2147483645
PCT_INCREASE                  :
MIN_EXTLEN                    : 65536
STATUS                        : ONLINE
CONTENTS                      : PERMANENT
LOGGING                       : LOGGING
FORCE_LOGGING                 : NO
EXTENT_MANAGEMENT             : LOCAL
ALLOCATION_TYPE               : SYSTEM
PLUGGED_IN                    : NO
SEGMENT_SPACE_MANAGEMENT      : AUTO
DEF_TAB_COMPRESSION           : DISABLED
RETENTION                     : NOT APPLY
BIGFILE                       : NO
PREDICATE_EVALUATION          : HOST
ENCRYPTED                     : NO
COMPRESS_FOR                  :
-----------------

Tablespace management system and sysaux size.. a concern..

Hi mates,
I have the report of my tablespace as thus:
FILE_NAME TABLESPACE_NAME STA Total MB % Free Aext
/usr/lib/oracle/xe/oradata/XE/MD MDATE AVA 196.608 13.57 YES
ATE.dbf
/usr/lib/oracle/xe/oradata/XE/SL SLIPSTREAM AVA 327.680 17.54 YES
IPSTREAM.dbf
/usr/lib/oracle/xe/oradata/XE/sy SYSAUX AVA 542.720 1.77 YES
saux.dbf
/usr/lib/oracle/xe/oradata/XE/sy SYSTEM AVA 378.880 1.69 YES
stem.dbf
/usr/lib/oracle/xe/oradata/XE/TX TXCD AVA 131.072 99.46 YES
CD.dbf
/usr/lib/oracle/xe/oradata/XE/un UNDO AVA 1,048.576 90.92 NO
do
/usr/lib/oracle/xe/oradata/XE/us USERS AVA 102.400 98.38 YES
ers.dbf
Can you pls tell me if the size of the sysaux and system tablespace should be a concern as I have freespace of 1.69 and 1.77%.
Thanxxxx.
Kenny

A datafile may not be able to resize (file system full). And resizing it may cause file fragmentation of that file (on that file system).
I prefer to add a new file, e.g.
ALTER TABLESPACE <tablespace> ADD DATAFILE [<filename>] SIZE <size>
When using ASM, the filename is determined (per OFA standards) by ASM itself. No need for the DBA to concern him/herself with directory structures and filenames.
By the way, the topic of this forum is SQL and PL/SQL - not database administration. I suggest that in future you post questions like this to the Database forum instead.

System tablespace space not regained when objects are dropped

Mine is a Oracle 10g 10.2 on windows.
I am importing a export file into a user ,It takes some amount of space in SYSTEM and another tablespace .When I drop the user space in system tablespace is not coming back. ANY IDEA WHY
BEFORE IMPORT
SQL> select sum(bytes)/1024/1024 from dba_segments where owner='SYSTEM';
SUM(BYTES)/1024/1024
22.1875
SQL> select sum(bytes)/1024/1024 from dba_segments where owner='SYS';
SUM(BYTES)/1024/1024
544.1875
SQL> select sum(bytes)/1024/1024 from dba_segments where segment_name='SOURCE$';
SUM(BYTES)/1024/1024
41
I use the following commands to import
SQL>create user <username> identified by <password> default tablespace <tsname> quota unlimited on <tsname>;
SQL>grant create session,imp_full_database to <username>;
imp system file=filename.dmp log=logname.log fromuser=<username> touser=<username> statistics=none
AFTER IMPORT
SQL> select sum(bytes)/1024/1024 from dba_segments where segment_name='SOURCE$';
SUM(BYTES)/1024/1024
53
SQL> select sum(bytes)/1024/1024 from dba_segments where owner='SYSTEM';
SUM(BYTES)/1024/1024
22.1875
SQL> select sum(bytes)/1024/1024 from dba_segments where owner='SYS';
SUM(BYTES)/1024/1024
728.375
AFTER DROPPING THE USER/SCHEMA
SQL> select sum(bytes)/1024/1024 from dba_segments where owner='SYS';
SUM(BYTES)/1024/1024
728.375
SQL> select sum(bytes)/1024/1024 from dba_segments where owner='SYSTEM';
SUM(BYTES)/1024/1024
22.1875
SQL> select sum(bytes)/1024/1024 from dba_segments where segment_name='SOURCE$';
SUM(BYTES)/1024/1024
53
I even tried deleting the objects first and then dropping the user
SQL> delete from source$ where obj# in(select object_id from dba_objects where owner='USERNAME');
211252 rows deleted.
SQL> commit;
Commit complete.
SQL> drop user USERNAME cascade;
User dropped.
The space used by the schema on system tablespace is not coming back.

Hi user509593!
Adding objects to a tablespace requires space in that tablespace. This space is managed in segments and extents. If an extent is fully used (that means 100 % usage) a new extent will be added to a segment. Oracle uses a mechanism called "High Water Mark" to mark the last used extent.
Your problem is that oracle don't set this High Water Mark back if you are dropping objects from a tablespace. Once an extent is marked as it it retains marked as used.
Before Adding Objects:
u = used Extent
x = free Extent
| = High Water Mark
uuuuuuxxxxx
...........|
After Adding Objects:
uuuuuuuxxxx
............|
After dropping objects:
uuuuuuuxxxx
............|
The only chance to get your "unused" space back is to reorganized your tablespace. But before you reorganize something please read the documentation to know all about the costs and traps that comes with reorganization.
Hope this help!
null

How to create a system tablespace as locally manged in 8.1.7

After a good time looking for it I still haven't found an example of how to create a database with the system tablespace as locally managed in release 8.1.7
I'm trying this, that isn't OK at all:
create database CSR
character set "WE8ISO8859P15"
datafile '/home/oracle/create/CSR/system/sysCSR.dbf' size 75M
extent management local
DEFAULT TEMPORARY TABLESPACE tsp_temp
DATAFILE '/home/oracle/create/CSR/temp/tempCSR.dbf'
SIZE 80M REUSE
logfile '/home/oracle/create/CSR/redo/redo1CSR.log' SIZE 500k,
'/home/oracle/create/CSR/redo/redo2CSR.log' SIZE 500k,
'/home/oracle/create/CSR/redo/redo3CSR.log' SIZE 500k;
Can someone tell me what is wrong, please?

I'm trying this, that isn't OK at allAre there any errors? can you explain what is not "OK"?

SYSTEM Tablespace issue (10.2.0.1 database)

Hi ,
Oracle database 10.2.0.1 (upgraded from 8.1.7.0 via 8.1.7.4)...successfully upgraded
Now when we open dbcontrol, we are getting alerts regarding the Tablespace.
It shows two critical alert messages as below :-
1) Tablesapace SYSTEM (dictionary managed) is 95.16 % full
2) 1 segment in SYSTEM tablespace is unable to extend.
Now how to deal with this type of issues ?
Can we extend the size of datafile of SYSTEM Tablespace which is dictionary managed ? or can we add another new datafile to system tablespace ? what is appropriate solution ?SYSTEM Tablespace
How to solve the point no. (2) as the TS is dictionary managed ?
With Regards

hi ,
Plz add the datafile to the system tablespace tp increase its size , and the conver the system tablespace from dictionary managed to local.
To Change SYSTEM tablespaces to locally managed follow the below procedures:
Before the SYSTEM tablespace can be migrated to locally managed format, you should ensure the following:
The database has a default temporary tablespace which is not SYSTEM
There are not any rollback segments in dictionary managed tablespaces
There is at least one online rollback segment in a locally managed tablespace, or an undo tablespace (if using automatic undo management mode) should be online.
All tablespaces other than the tablespace containing the undo space (undo tablespace or the tablespace containing the rollback segment) and the default temporary tablespace are in read-only mode.
There is a complete backup of the system.
The system is in restricted mode.
Notr, that we already have an UNDO Tablespace. The following query determines whether the SYSTEM tablespace is locally managed:
SQL> SELECT ts# FROM ts$ WHERE ts# = 0 AND bitmapped <> 0;
If 0 rows are returned, then the SYSTEM tablespace is dictionary managed. Otherwise, the SYSTEM tablespace is locally managed.
Steps to change SYSTEM tablespaces to locally managed
SQL> shutdown immediate
SQL> startup restrict
SQL> execute DBMS_SPACE_ADMIN.TABLESPACE_MIGRATE_TO_LOCAL ('SYSTEM');
ERROR at line 1:
ORA-10644: SYSTEM tablespace cannot be default temporary tablespace
ORA-06512: at "SYS.DBMS_SPACE_ADMIN", line 227
ORA-06512: at line 1
SQL> ALTER DATABASE DEFAULT TEMPORARY TABLESPACE temp;
SQL> execute DBMS_SPACE_ADMIN.TABLESPACE_MIGRATE_TO_LOCAL ('SYSTEM');
ERROR at line 1:
ORA-10647: Tablespace other than SYSTEM, UNDO, TEMP not
found in read only mode
ORA-06512: at "SYS.DBMS_SPACE_ADMIN", line 227
ORA-06512: at line 1
SQL> select tablespace_name from dba_tablespaces;
TABLESPACE_NAME
SYSTEM
TEMP
USERS
TAB
IDX
SYSAUX
UNDO
SQL> alter tablespace USERS read only;
SQL> alter tablespace TAB read only;
SQL> alter tablespace IDX read only;
SQL> execute DBMS_SPACE_ADMIN.TABLESPACE_MIGRATE_TO_LOCAL ('SYSTEM');
ERROR at line 1:
ORA-10648: Tablespace SYSAUX is not offline
ORA-06512: at "SYS.DBMS_SPACE_ADMIN", line 227
ORA-06512: at line 1
SQL> alter tablespace SYSAUX offline;
SQL> execute DBMS_SPACE_ADMIN.TABLESPACE_MIGRATE_TO_LOCAL ('SYSTEM');
PL/SQL procedure successfully completed.
Regards,
Mohd Mehraj Hussain
http://mehrajdba.wordpress.com

Error:cannot use system rollback segment for non-system tablespace

Hi,
I have created a oracle database 10.2.0 on fedora 9 system. I have created a user and assigned the default tablespace SATYA and given the permissions. But when I create a table in the user I am getting the following error.
Can anyone help me in rectifying this error.
ORA-01552: cannot use system rollback segment for non-system tablespace 'SATYA'
thankyou
satya

Undo management is either AUTO or Manual, no local
http://download.oracle.com/docs/cd/B19306_01/server.102/b14231/undo.htm#sthref1469
Since you are using 10g, you are recommended to use Auto undo management
If you still plan to use manual undo management, make sure you have other non-system rollback segment in place.

System tablespace is 99% full

hello all,
I created a new Oracle 11gR2 11.2.0.3.
i am checking the Oracle Enterprise manager, i saw the my system tablespace size is 700 M and it is 99% full.
Do i have to re size system tablespace datafile?
does that affect my database, do i have to restart it ?
99% full of system table space will affect my database performance?
How can I specify the best size of my system tablespace?
Regards,

That does seem to be the size system tablespace you get with a new db. After a couple of years, mine is still that size, though it appears something has come and gone, but I don't really care.
Recent versions separate out various things into the sysaux tablespace. You do have to watch out that it doesn't start growing. dbconsole has an interesting tablespace map (and there are command lines ways also) to see what segments are in tablespaces. Don't worry too much about any apparent "fragmentation" (and I use that word loosely, and probably shouldn't) you see in the mapping of segments, but it is useful to be aware [url http://docs.oracle.com/cd/B28359_01/server.111/b28310/create004.htm#i1011308]what is in sysaux and why it might start growing. Autoextend is perfectly fine for these tablespaces.
Edit: Auditing is special, and may cause the system tablespace to grow under certain circumstances.
Edited by: jgarry on Apr 11, 2012 3:27 PM

Temp usage in system tablespace

Hi
I have oracle 9i with dictionary managed tablespaces.
I have put a trigger to capture sql statement which cause temp errors.
Recently, I have found out that the below sql cause:
ORA-1652: unable to extend temp segment by 5394 in tablespace SYSTEM
select distinct i.*
from PREM i, Summ p
WHERE i.Contract_Branch_Id = p.Pol_Branch_Id
AND i.Product_Code = p.Product_Code
AND i.Contract_Pol_No = p.Pol_No
AND p.Transaction_Type = 'V23'
AND p.Accounting_Prd IN
(TO_NUMBER(TO_CHAR(ADD_MONTHS(SYSDATE, -1),'YYYYMM')), TO_NUMBER(TO_CHAR(SYSDATE, 'YYYYMM')))My question is, how come such a sql uses temp segments in System tablespace rather than normal temp tablespace ?

in sqlplus do the following
SET AUTOTRACE TRACEONLY EXPLAIN STATISTICS
select distinct i.*
from PREM i, Summ p
WHERE i.Contract_Branch_Id = p.Pol_Branch_Id
AND i.Product_Code = p.Product_Code
AND i.Contract_Pol_No = p.Pol_No
AND p.Transaction_Type = 'V23'
AND p.Accounting_Prd IN
(TO_NUMBER(TO_CHAR(ADD_MONTHS(SYSDATE, -1),'YYYYMM')), TO_NUMBER(TO_CHAR(SYSDATE, 'YYYYMM')))
post FORMATTED results back here

ORA-01251 on system tablespace

hi folks,
(of course we didn't have any backup)
when we try to open our DB we get:
SVRMGR> alter database open;
alter database open
ORA-01122: database file 19 failed verification check
ORA-01110: data file 19: '/tecdata/oradata/INVSID/system08.dbf'
ORA-01251: Unknown File Header Version read for file number 19
SVRMGR>
We find some recovery solution but not in case of system tablespace datafile
we cannot drop the datafile 'couse we are not able to open the database.
there is any solution?
thanks everyone!

Hello,
in dba_temp_files, it shows MAXBYTES as 34359721984, so UNLIMITED apparently does mean 32GB??As Sybrand posted, it depends on your Block Size.
If you use Smallfile Tablespace (the default) then, each of its Datafile is limited to *4 MBlock* (so 4x1024x1024 blocks). So, for a Block Size of 8 Ko it gives (8x1024)x(4x1024x1024) Bytes = *32 GB*. But, you may have up to *1022* Datafiles for your Tablespace.
So, if you want your Tablespace to extend more than 32 GB you may add other datafiles, up to *1022*. So in fact the maximum size for your Tablespace can reach almost *32 TB* (for a block size of 8 Ko). Of course, in this case, you'll have so many datafiles that it won't be easy to manage them.
This is the reason why, starting with Oracle 10.1 you may create Bigfile Tablespace. They have just one datafile but, it can reach *4 GBlock*, so 32 TB for a Block Size of 8 Ko.
Before using Bigfile Tablespace, you should ensure that your OS can support such large file else, the capacity of the Tablespace could be really limited.
Hope this help.
Best regards,
Jean-Valentin

How to reduce the size of SYSTEM tablespace?

* Solaris
* Oracle 9.2.0.4.0
* Locally managed database (since SYSTEM is locally managed TS)
I have a Oracle 9i database with is around 7 months old. Over the 7 months it had around 400 schemas at most and SYSTEM tablespace was increased to 850MB. Now it only has around 120 schemas and size of the SYSTEM tablespace still 850MB and its 99% used.
How can I get more free space on system tablespace?
* I have made sure that non-sys(tem) user dont have objects on SYSTEM tablespace.
* I understand that dropping schema does not give you all the space back, since objects are store as row in System tables etc.
Increasing disk is not an option for me. Any tips to free space on system welcome.
Thanks,
Nazrul Islam

Thanks Joel Pérez for trying to help.
SQL> select segment_name, owner from
dba_segments
where owner not in
('SYS','SYSTEM','OUTLN','MDSYS','ORDSYS','WMSYS')
and
TABLESPACE_NAME='SYSTEM';
SEGMENT_NAME                   OWNER
TOAD_PLAN_SQL                  TOAD
TOAD_PLAN_TABLE                TOAD
PLSQL_PROFILER_RUNS            TOAD
PLSQL_PROFILER_UNITS           TOAD
PLSQL_PROFILER_DATA            TOAD
TPSQL_IDX                      TOAD
TPTBL_IDX                      TOAD
SYS_C006895561                 TOAD
SYS_C006895563                 TOAD
SYS_C006895566                 TOAD
10 rows selected.
SQL> select owner from dba_segments where
tablespace_name='SYSTEM'
group by owner;
OWNER
OUTLN
SYS
SYSTEM
TOAD
WMSYSHere is my query (to show TOAD is taking very little
space):r.- That is true, the space used by TOAD is little
>
SQL> select owner, SUM(bytes)/1048576 AS "TOTAL
(MB)"
from dba_segments
where tablespace_name = 'SYSTEM'
group by owner order by "TOTAL (MB)" desc;
OWNER                 TOTAL (MB)
SYS                     820.4375
SYSTEM                      20.5
WMSYS                     3.6875
TOAD                       .6875
OUTLN                       .375Looks like, I have to grow system. Or since I have a
fixed number of schema now, I think I will have to
recreate a DB to reduce SYSTEM size.
Joel one other info that might explain why
this happening. Part of our build process is to drop
4 schemas and roles and recreate them.
e.g.
drop user nislam cascade;
create user nislam ....And we do many builds a day. Maybe Oracle uses more
space in doing that since new userid, better might be
drop objects from the schema. WHAT do you
say?
r.- In theorical lines. Both must give the same results but... I would recommend you to carry out some intensive test about it in a test enviroment testing both methods to monitor the behavior of the growth of the tablespace system. As you said, perhaps dropping the user objects will get better results.
>
Regards,
Nazrul IslamJoel Pérez
http://otn.oracle.com/experts

System Tablespace LMT

Has anyone tried creating a Locally Managed System tablespace for Oracle 9.2.0.4? If so, has it been a good move maintenance-wise and performance-wise?

I would think that the autoallocate space management feature would be ideal for system since it is a tablespace where very small and potentially relatively large objects would both exist.
I am pretty sure this is the default for 10g tablespace build from scratch.
We have used it on a non-system tablespace used to support a vendor product where large and small objects exist together and it works fine.
HTH -- Mark D Powell --

RMAN duplicate target database for standby from active fails to create newname for system tablespace/datafile

When executing 'duplicate target database for standby from active' the system tablespace/datafile (datafile 1) is not cloned. All other datafiles clone successfully. The RMAN process aborts with the following errors while attempting to clone the system tablespace/datafile.
ORA-19558: error de-allocating device
ORA-19557: device error, device type: DISK, device name:
ORA-17627: ORA-01041: internal error. hostdef extension doesn't exist
ORA-17627: ORA-01041: internal error. hostdef extension doesn't exist
ORA-03135: connection lost contact
Here are the details:
Primary is 11.2.0.2 RAC database on an Exadata platform
Standby is 11.2.0.2 Single Instance database (same patch level as primary) on a Red Hat Linux box
This is an ASM to ASM duplication.
This is not unique to this database. We tried another database and go the same behavior - all datafiles clone successfully with the exception of the system tablespace/datafile.
We have traced the RMAN execution and it seems to fail when it is trying to assign a NEWNAME to the system tablespace/datafile.
We even issued an explicit SET NEWNAME command but RMAN ignored it.
We also shutdown the primary and started is up in mount mode thinking that something had ahold of the System Tablespace/datafile.
We also opened up the network firewall to allow permit any,any traffic.
We increased the max_server_processes
and added TCP.NODELAY=yes to the sqlnet.ora file.
There seems to be some artifact present in our Primary System tablespace/data file that is preventing it form being cloned.
checked all alert files grid, asm, and dbhome - no abnormal messages.
We are in the process of restoring the database from a backup but we would prefer to get this working using the 'Active Database' methodology

I successfully created the standby database using RMAN backup and recovery.
I started the managed recovery. Archive logs are being sent from the primary to the standby ( I can see them in ASM), but the standby is not applying them.
I get the following messages in the standby alert log...
Fetching gap sequence in thread 2, gap sequence 154158-154257
Tue Nov 26 16:19:58 2013
Using STANDBY_ARCHIVE_DEST parameter default value as USE_DB_RECOVERY_FILE_DEST
Using STANDBY_ARCHIVE_DEST parameter default value as USE_DB_RECOVERY_FILE_DEST
Tue Nov 26 16:20:01 2013
Fetching gap sequence in thread 2, gap sequence 154158-154257
Tue Nov 26 16:20:11 2013
Fetching gap sequence in thread 2, gap sequence 154158-154257
Tue Nov 26 16:20:22 2013
Fetching gap sequence in thread 2, gap sequence 154158-154257
Tue Nov 26 16:20:32 2013
Fetching gap sequence in thread 2, gap sequence 154158-154257
I don't see any MRP processes:
select process,
status,
    thread#,
    sequence#,
   block#,
blocks
7     from v$managed_standby;
PROCESS   STATUS          THREAD# SEQUENCE#     BLOCK#     BLOCKS
ARCH      CLOSING               2     154363          1        132
ARCH      CONNECTED             0          0          0          0
ARCH      CONNECTED             0          0          0          0
ARCH      CONNECTED             0          0          0          0
ARCH      CONNECTED             0          0          0          0
ARCH      CONNECTED             0          0          0          0
ARCH      CONNECTED             0          0          0          0
ARCH      CONNECTED             0          0          0          0
RFS       IDLE                  0          0          0          0
RFS       IDLE                  1     145418        121          1
RFS       IDLE                  0          0          0          0
PROCESS   STATUS          THREAD# SEQUENCE#     BLOCK#     BLOCKS
RFS       IDLE                  0          0          0          0
12 rows selected.
SQL> SELECT THREAD#, SEQUENCE#, APPLIED FROM V$ARCHIVED_LOG;
   THREAD# SEQUENCE# APPLIED
         2     154356 NO
         2     154357 NO
         1     145411 NO
         2     154358 NO
         2     154360 NO
         2     154361 NO
         1     145414 NO
         1     145415 NO
         2     154362 NO
         2     154363 NO
         1     145416 NO
11 rows selected.
I do have the archive logs that cover sequences 154158-154257
Crosschecked 38 objects
Crosschecked 62 objects
Finished implicit crosscheck backup at 26-NOV-13
Starting implicit crosscheck copy at 26-NOV-13
using channel ORA_DISK_1
using channel ORA_DISK_2
Crosschecked 2 objects
archived log file name=+RECO_XORA/nmuasb00/archivelog/2013_11_26/thread_2_seq_154377.344.832521989 RECID=29 STAMP=832521990
validation succeeded for archived log
archived log file name=+RECO_XORA/nmuasb00/archivelog/2013_11_26/thread_2_seq_154378.346.832521991 RECID=31 STAMP=832521993
Crosschecked 31 objects

R/3 System Copy PRD -- QA Oracle 9

Hi all,
We need to perform a system copy of Production back to QA (4.7/6.40 kernel). My previous experience with a system copy was on a 4.6C system with Oracle 8 using R3COPY. I have just downloaded the latest system copy guide 'Homogeneous and Heterogeneous System Copy for SAP® Systems Based on SAP Web Application Server 6.20' and for Oracle it says that backup/restore method is not recommended or support and to use R3LOAD. We are not keen to use this method as it requires a longer Production downtime for us (more than twice what would be required for offline backup), also we would need the space available on the disk.
Has anyone still used the backup/restore method as described in the 4.6C system copy guide with Oracle 9? I don't see why this method is not supported since for us it would be much easier.
Thanks
- Natalie

Hello,
Perhaps this notes can be of help:
<a href="http://service.sap.com/sap/support/notes/427836">427836</a> OneDb system: Homogeneous system copy with DBR3CP.R3S ( bit old, perhaps not good for your system )
<a href="http://service.sap.com/sap/support/notes/713685">713685</a> Hom./Het.System Copy SAP Web AS 6.40
<a href="http://service.sap.com/sap/support/notes/857734">857734</a> System Copy of SAP Systems based on 6.20 and 6.40 / Oracle
On this notes you can find other interesting refering the same issue
Not much into system copies with the new tools, but I think it is possible to use backup/restore.
The only thing is that you will have a little "mess" -> the tablespace name will have the old "SID", same happens with the schema. Unless you have installed the system with this issue in mind and used a "neutral" schema, the note is ( I think )[url=http://service.sap.com/sap/support/notes/617444]617444[/url]

System tablespace management in oracle 9i

Similar Messages

Maybe you are looking for