No privileges on system tablespace?

I am a new dba & have succesfully created tables and added constraints.
Today I tried to add a constraint to an existing table, and received the message
ORA-01950: no privileges on tablespace 'SYSTEM'
I tried to add the constraint as the owner of the table, as a user with granted privs on the table, and finally as SYS, and get the same error.
The system tablespace is only about 60% full, and I have not changed any user privs since I last sucessfully added constraints.
If someone would give me a clue as to what's going on, I would really appreciate it.
Thanks, Helen

I granted unlimited tablespace to the user that owns the table, and the constraint was added successfully.
I don't know if a user should have unlimited tablespace on SYSTEM...any advice on what a good limit would be? My system tablespace is 325 M and about 60% full. Would it make sense to grant sys unlimited tablespace on SYSTEM?
Thanks very much for your help. You gave me the incentive to keep trying things until something worked.

Similar Messages

Error no privilege on system tablespace

Hi all,
I am trying to do follwing but getting an error
SQL> connect system/manager@kiran
Connected.
SQL> create user my_user
2 identified by my_user;
User created.
SQL> grant create session,create table
2 to my_user;
Grant succeeded.
SQL> connect my_user/my_user@kiran
Connected.
SQL> create table my_tab(a number);
create table my_tab(a number)
ERROR at line 1:
ORA-01950: no privileges on tablespace 'SYSTEM'
Can anybody tell me why I am getting this error ???

SQL> create user test identified by test;
User created.
SQL> grant create session,create table to test;
Grant succeeded.
SQL> conn test/test
Connected.
SQL> create table test_tab(a number);
create table test_tab(a number)
ERROR at line 1:
ORA-01950: no privileges on tablespace 'SYSTEM'
SQL> conn / as sysdba
Connected.
SQL> alter user test quota 10M on system;
User altered.
SQL> conn test/test
Connected.
SQL> create table test_tab(a number);
Table created.
SQL>As I said before, this is not the best way, you should define a default tablespace when you create users, e.g.
SQL> create user test identified by test
2 default tablespace t_data
3 temporary tablespace temp;Message was edited by:
Paul M.
Message was edited by:
Paul M.

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

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

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"?

Adding datafile to ASM file system tablespace

Hi
Can some one plz help in writing a script to add a datafile to the system tablespace on ASM filesystems.
below is the result of the query ..
select file_name, bytes, autoextensible, maxbytes from dba_data_files where tablespace_name='SYSTEM';
FILE_NAME BYTES AUT MAXBYTES
+DATA1/cir_p/datafile/system.260.6037360 5892997120 NO 0
Thanks

790072 wrote:
Hi
Can some one plz help in writing a script to add a datafile to the system tablespace on ASM filesystems.
below is the result of the query ..
select file_name, bytes, autoextensible, maxbytes from dba_data_files where tablespace_name='SYSTEM';
FILE_NAME BYTES AUT MAXBYTES
+DATA1/cir_p/datafile/system.260.6037360 5892997120 NO 0
Thanks
You can use
ALTER TABLESPACE "SYSTEM" ADD DATAFILE '+DATA1' SIZE 1024M
Cheers

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 is growing fast in 10g

Hi,
Using 10.2.0.1.0 on Linux
My SYSTEM tablespace is growing much faster on 10g than it was on 9i, in 2 month it went from 350mb to 500mb, I don't to add more disk, incase there are issues with my database, I want to know why it is growing.
I have read docs on why SYSAUX grows on 10g but not SYSTEM.
SYSTEM size - 500 mb
Schema/size on System are:
SYS______455.8125 mb
SYSTEM______15.25 mb
OUTLN______0.5 mb
In this database I only have 1 very large schema that is 200 GB
Any ideas, reasons, shall I increase it 700mb?
In 9i my SYSTEM tablespace was very static.
Thanks for any help.

Are you using Oracle's audit feature, either standard or FGA? If you were using standard auditing before moving to 10g check that the purge task is still running successfully.
Verify that no users have their temp tablespace set to system. If is still possible for this to happen on 10g.
HTH -- Mark D Powell --

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

System tablespace file suffered media failure

Hi All,
Our DB is shutdown due to this error:
===
ORA-01243: system tablespace file suffered media failure
ORA-01122: database file 1 failed verification check
ORA-01110: data file 1: '/dumps/rmodevdb/db/apps_st/data/system01.dbf'
ORA-01206: file is not part of this database - wrong database id
CKPT: terminating instance due to error 1243
Instance terminated by CKPT, pid = 8203
====
Please let me know how to resolve this.
Thanks,
Kishore

Yes Aman.. This happened after cloning in apps.
However, issue got resolved.
Data files were zipped using tar- cvzf ...
I could successfully complete the cloning when backup is taken with "tar cvf" (with out including z)
So, learnt that datafiles should not be zipped when tar.
But datafiles can be zipped using gzip after " tar cvf " is completed.
Am i right ?

Why the system tablespace increase a lot?

I have noticed that the system tablespace of my prod Oracle 10g R2 on AIX 5.3L reaches over the 85% warning level now, and the size has increased from ~68% to 88% of 1.6G total assigned capacity during the last 7 months. How do i find out what reason causes the increase? can I remove some "fat" out of them? or just keep increasing the size? My fresh backup AIX 5.3L system with the same 10g R2 only takes 38% of 1.6 G.

SEGMENT_NAME SEGMENT_TYPE MBYTES
SYS_LOB0000125172C00039$$ LOBSEGMENT 152
C_OBJ#_INTCOL# CLUSTER 136
I_CON1 INDEX 104
C_OBJ# CLUSTER 96
C_COBJ# CLUSTER 88
HIST_HEAD$ TABLE 57
CON$ TABLE 41
I_COL1 INDEX 41
C_FILE#_BLOCK# CLUSTER 38
I_HH_OBJ#_COL# INDEX 34
I_HH_OBJ#_INTCOL# INDEX 34
SOURCE$ TABLE 32
I_CON2 INDEX 27
IDL_UB1$ TABLE 26
I_CDEF4 INDEX 26
I_H_OBJ#_COL# INDEX 25
I_COL2 INDEX 20
OBJ$ TABLE 19
I_COL3 INDEX 19
I_CCOL1 INDEX 19
I saw some LOB segments in SYS; however my fresh new 10g R2 (v SE) on other AIX machine does not list those. Where are they from?
I checked the user_lobs, Here are the tables which has LOB seg stored the system tablespace
AW_OBJ$
VIEWCON$
SNAP$
SNAP$
TABPART$
INDPART$
TABSUBPART$
INDSUBPART$
TABCOMPART$
INDCOMPART$
DEFSUBPART$
KOTTD$
KOTTB$
KOTAD$
KOTMD$
KOTTBX$
KOTADX$
SUM$
SUM$
SQL$TEXT
METASTYLESHEET
EXTERNAL_TAB$
EXTERNAL_TAB$
JIREFRESHSQL$
AUD$
AUD$
FGA_LOG$
FGA_LOG$
PS$
STREAMS$_DEF_PROC
STREAMS$_DEF_PROC
STREAMS$_DEF_PROC
REDEF_DEP_ERROR$
NCOMP_DLL$
EXPIMP_TTS_CT$
ATTRIBUTE_TRANSFORMATIONS$
RULE$
RULE$
REG$
AQ_EVENT_TABLE
AQ_SRVNTFN_TABLE
AQ_SRVNTFN_TABLE
SCHEDULER$_JOBQTAB
SCHEDULER$_JOBQTAB
SCHEDULER$_JOB_ARGUMENT
SCHEDULER$_PROGRAM_ARGUMENT
SCHEDULER$_EVENT_QTAB
KUPC$DATAPUMP_QUETAB
KUPC$DATAPUMP_QUETAB
KUPC$DATAPUMP_QUETAB
KUPC$DATAPUMP_QUETAB
KUPC$DATAPUMP_QUETAB
KUPC$DATAPUMP_QUETAB
KUPC$DATAPUMP_QUETAB
STREAMS$_INTERNAL_TRANSFORM
AQ$_MEM_MC
AQ$_MEM_MC
AQ$_KUPC$DATAPUMP_QUETAB_P
AQ$_KUPC$DATAPUMP_QUETAB_P
AQ$_KUPC$DATAPUMP_QUETAB_P
AQ$_KUPC$DATAPUMP_QUETAB_P
AQ$_KUPC$DATAPUMP_QUETAB_P
AQ$_KUPC$DATAPUMP_QUETAB_P
AQ$_KUPC$DATAPUMP_QUETAB_P
AQ$_KUPC$DATAPUMP_QUETAB_D
SYS_EXPORT_FULL_01
SYS_EXPORT_FULL_02
Does not look like any non-system user here?
Message was edited by:
user508054

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                  :
-----------------

How to remove data file from System tablespace

Hi All,
I have wrongly added data file in SYSTEM tablespace, now I want remove it. I have tried to set datafile offline but it is giving me the error system tableapce can not set offline. so please help me. I am working Oracle 10g .
thanks in advance
sv

In 10gR2, you can drop a datafile from tablespace, as long it's empty (and of course not the last one):
ALTER TABLESPACE tbs_03 DROP DATAFILE 'tbs_f04.dbf';
Otherwise, there's no direct way to get rid of the file. You can just shrink it and move (i.e. "rename") it another location. For a non-system tablespace, move of all segments to another tablespace (and later renaming it) would be an option, but this of course won't work with system tablespace.

Block Corruption in SYSTEM Tablespace

Hi,
well it´s just a test database without a backup, but i would like to repair it anyway :-)
Here are the facts:
Errors in file c:\oracle\admin\o10g\bdump\o10g_smon_1404.trc:
ORA-01578: ORACLE data block corrupted (file # 1, block # 50187)
ORA-01110: data file 1: 'C:\ORACLE\ORADATA\O10G\SYSTEM01.DBF'
1. I found the object: It´s a Cluster named SYS.C_TOID_VERSION#
containing a lot of table stuff (type$,parameter$, ...)
i tried to repair it with dbms_repair:
BEGIN SYS.DBMS_REPAIR.SKIP_CORRUPT_BLOCKS (
SCHEMA_NAME => 'SYS',
OBJECT_NAME => 'C_TOID_VERSION#',
OBJECT_TYPE => dbms_repair.cluster_object,
FLAGS => dbms_repair.skip_flag);
END;
No error, but the same block corruption message in the alert.log 1 minute later.
i can select the tables in the cluster.
Has anyboby another trick to repair a cluster?
Thanks
Marco

Hi,
if you have rman backup then this problem become resolved by only one command.
BLOCKRECOVER DATAFILE 1 BLOCK 3 DATAFILE 50187;
otherwise restore system tablespace from backup and recover it.
and one more thing
**Don't fix the block in system tablespace it may create problem if that block contain some useful information of oracle(internal information).
Thanks
Kuljeet Pal Singh

InterMedia leaves garbage in the system tablespace

During the creation of a context(interMedia) index, I shutdown
the Oracle server with abort. I started the server up and
proceeded to delete the bad index. When I tried to create a new
index with the same name an error occured. I looked in some
tables in the system tablespace under the ctxsys user, and found
references to my corrupted index. Is there a way to clear out
this bad data w/o having to re-install Oracle?

You don't say what the error is so I can't be sure, but I
suspect that deleting the entry in dr$index (owned by ctxsys)
for your 'bad' index will allow you to recreate it.

No privileges on system tablespace?

Similar Messages

Maybe you are looking for