Extra tablespaces

hi
when we create databse using DBA and we add support of intermedia or OLAP then extra
tablespaces are created and then scripts are run to create schems in these tablespaces for
support of OLAP etc. i have a question that if we dont add OLAP support at database creation
and after that we manually add tablespace to create schema for OLAP (or some other facility
like intermedia) then should we use the same tablespace name oracle uses while creatin these
tablespaces at database creation using DBCA...mean that we cant have a tablespace for OLAP
different then a default specified by oracle....because the question in my mind is that when
a spesific user is created for OLAP using SCRIPT provided by oracle it also creates a user
and it must grant quota on that tablespace we created for OLAP....so if we don create
tablespace with the same name (the name DBCA uses to create)...oracle will retuyrn an error
when we will run script to add OLAP support as when it wil create a user for OLAP and grant
him quota then tablespace name will be different
geting my point??
Regards

It would seem to be more robust to stick with the TS names that Oracle suggests (albeit they do so in a round-about way)

Similar Messages

EXP/IMP..of table having LOB column to export and import using expdp/impdp

we have one table in that having colum LOB now this table LOB size is approx 550GB.
as per our knowldge LOB space can not be resused.so we have alrady rasied SR on that
we are come to clusion that we need to take backup of this table then truncate this table and then start import
we need help on bekow ponts.
1)we are taking backup with expdp using parellal parameter=4 this backup will complete sussessfully? any other parameter need to keep in expdp while takig backup.
2)once truncate done,does import will complete successfully..?
any SGA PGA or undo tablespace size or undo retention we need to increase.. to completer susecfully import? because its production Critical database?
current SGA 2GB
PGA 398MB
undo retention 1800
undo tbs 6GB
please any one give suggestion to perform activity without error...also suggest parameter need to keep during expdp/impdp
thanks an advance.

Hi,
From my experience be prepared for a long outage to do this - expdp is pretty quick at getting lobs out but very slow at getting them back in again - a lot of the speed optimizations that may datapump so excellent for normal objects are not available for lobs. You really need to test this somewhere first - can you not expdp from live and load into some test area - you don't need the whole database just the table/lob in question. You don;t want to find out after you truncate the table that its going to take 3 days to import back in....
You might want to consider DBMS_REDEFINITION instead?
Here you precreate a temporary table (with same definitiion as the existing one), load the data into it from the existing table and then do a dictionary switch to swap them over - giving you minimal downtime. I think this should work fine with LOBS at 10g but you should do some research and see if it works fine. You'll need a lot of extra tablespace (temporarily) for this approach though.
Regards,
Harry

Create an Object in Logical standby database in Oracle 10G

Hi,
I have logical standby database in oracle 10g R2 for reporting purpose.Now i want to create procedure in logical standby which is use to create new temp table in logical standby and contained data generated from select operation on existing table.
Can i create a new user in logical standby database,add new tablespace in logical standby which can insert,update and delete data in standby database base table?
kindly provide me the steps to implement all this.What will be effect if i set guard_Status in v$database is NONE in logical standby?
Thanks,
Shital Patel

Hi Shital,
Guard_status protects the data from being changed.
ALL- By default it is not possible for a non-privileged user to modify data on a data guard SQL apply database. This is because the database guard is automatically set to ALL.
With this level of security, only SYS user can modify the data.
STANDBY- When you set this level of security, users are able to modify data that is not maintained by the Logical apply engine.
NONE permits any users to access the standby database as long as they have correct privileges. This is the normal security for all data in the database.
You can change the guard status value from ALL to NONE in order to allow non-privileged users to modify data and Yes you can create user and extra tablespace in logical standby database..this is what the one of advantage of using Logical standby database.
SQL> ALTER DATABASE GUARD NONE;
Thanks

Add new datafile to logical standby database but not in primary

Hi,
Is it ok to add a new datafile to the SYSAUX tablespace on the logical standby database but not on primary? We are running out of disk space on the partition where SYSAUX01.dbf resides so we want to add a new SYSAUX02.dbf in another partition which has space. but this will only be on the logical standby not on primary, there is still lots of space in primary. standby_file_management is MANUAL and this is LOGICAL STANDBY not PHYSICAL.
Is this possible or where there be any issues?
Thanks.

Logical Standby can differ from Primary, it can have extra tablespaces, datafiles, tables, indexes, users ...
HTH
Enrique

Oracle 10g Logical Standby

The question is on Oracle 10g Logical Standby Data Guard. Below is the short description of what we wanted to do.
We currently run our Remedy application on Oracle10g. We wanted to setup Data Guard (logical standby) so we can perform our application upgrade on the logical standby. While we upgrade our application, our customers perform the dml on the primary instance.
During the upgrade, we will change the ddl on our application in the logical standby instance. After the application upgrade, we do a role switch between the two instances (primary became a new logical standby and logical standby became new primary). Now, we wanted the data or the dml that our customers perform on the old primary replicate over to the new primary.
It is possible for the logical standby to perform the ddl at the same time user perform the ddl and dml on the primary instance?
After role switch between the two instances, is the data changed on the primary replicate over to the new primary?
Thank you for your helps.
Loc Nguyen
[email protected]

Hi Shital,
Guard_status protects the data from being changed.
ALL- By default it is not possible for a non-privileged user to modify data on a data guard SQL apply database. This is because the database guard is automatically set to ALL.
With this level of security, only SYS user can modify the data.
STANDBY- When you set this level of security, users are able to modify data that is not maintained by the Logical apply engine.
NONE permits any users to access the standby database as long as they have correct privileges. This is the normal security for all data in the database.
You can change the guard status value from ALL to NONE in order to allow non-privileged users to modify data and Yes you can create user and extra tablespace in logical standby database..this is what the one of advantage of using Logical standby database.
SQL> ALTER DATABASE GUARD NONE;
Thanks

Upgradation of 3.1 i to 4.6c and 4.7

Can any body please send the relevant information on Upgradation of 3.1 i to 4.6c and 4.7. And please tell what are all thing we can do in this process and what sort of obstacles we may face in this process

Hi,
I am sorry. I am sending you a long file since your question was very general.
Guidelines / Checklist for Upgrade
Before Upgrade
1.     Have the following information readily available to estimate and assess the effort and timelines :
a.     Hardware Upgrade plans (if any)
b.     No of Application servers
c.     Add-ons Installed and their respective version
d.     No of custom developed objects like reports, Module Pools, BDC etc
e.     % of changes to Standard SAP repository Objects
f.     PC configuration for end users
2.     Complete hardware should be available before upgrade as planned.
3.     Ensure hardware compatibility with target SAP R/3 Release in terms of performance & database storage capacity. A minimum storage of around 50-75 GB will be required for dump of Upgrade CDs (includes extra Tablespace)
4.     Ensure that database / OS Upgrade hardware patches are readily available, if the same has to be updated.
5.     Ensure O/s level compatibility for 64 bit for Non windows based O/s. For example UNIX etc.
6.     Final System landscape should be finalized before the start of the Upgrade. A minimum of three servers are required for any upgrade, one server will the current production server, One server for test upgrade and one server to restore the old production server backup just before go-live.
7.     The test upgrade server should have the configuration equivalent to current production server, to get a proper estimate of times lines and Critical downtime
8.     Ensure that all SAP software CDs are available and check for their usability
9.     Have all the support packages readily available and apply highest level of support packs available in each of the respective area to minimize the problems after the upgrade.
10.     Ensure that all SAP perquisites have been taken care before the trigger of upgrade.
11.     Make sure that all SAP notes, which details and describes the activities required to be carried out in order to avoid data loss and solution to known problems are available in the repository and all the activities have been carried out as per those notes. For example to avoid loss of customizing of movement types refer to note no : ???
12.     If any add on like CIN, Cable Solution has been installed, please make sure that you search SAP notes for conversion / migration guides. These migration guides are very useful to determine the customizing changes to be made and also for converting old data to new tables and fields
13.     Analyze the SAP customizing, for any specific customizing / application , which generally is not part of a standard Normal R/3 customizing / application (for example Variant Configuration). Collect all notes related to such customizing if any before upgrade activities to avoid any surprises. The same is true where the skill set of the consultant is not up to standards required in a particular area.
14.     A list of ABAP programs developed should be made available before the upgrade. The list should also classify the programs in terms of their criticality. A core team member should be assigned to each critical program for testing and sign off
15.     OSS connectivity is a must. It is preferred to have OSS connectivity thru SAP Front end using OSS1 transaction instead of internet based OSS connectivity
16.      The latest SAP GUI version required to run the upgraded SAP version should be installed on the Users PC before the start of upgrade process.
17.     If possible, find out the Holiday schedule for the time frame of the upgrade project. This is required to find dates for PRD Go live so as to ensure that SAP shutdown is planned during holidays, therefore minimizing the impact of such shutdown.
18.     If a Go-live date is set prior to the upgrade then work back words to decide about the availability of test server, involvement of functional Team, user training etc.
Upgrade Test server
1.     Use SAP upgrade tools like ASU. Refer to note no: 623723.   This will provide readily available solutions for known problems.
2.     Latest offline O/S level backup should be restored to the Test upgrade Server prior to Upgrade
3.     If possible SAP support packs should be applied as part of Upgrade process.
4.     Process should be put in place to record and monitor the changes made to ABAP and customizing and transported to production during upgrade of Test server.
5.     Make sure that for Change requests related to upgrade is captured under a Project. This is required specifically for ABAP request. This also helps to avoid the confusion related to dependencies at the time of release and import into PRD system.
6.     All the issues faced during upgrade should be properly documented. A proper issue log should be maintained describing the problems and the resolution. This will serve has a reference for problems faced after go-live.
7.     All the test scenarios / test results should be documented along with the hardcopies of Layout and critical documents. This will serve as a base for user sign off.
8.     For problems faced while testing, search for SAP Notes for the resolution of the same. As it has been observed that for 90% of the problems there is a Note available in the SAP Repository
9.     Please use following methodology to find relevant SAP notes
a.     If an error message is displayed the put the Message <Message Class> <Message ID> in the search field and sort the messages by date to get the latest notes.
b.     If a note reference is given in the source code where error has occurred check for related notes and latest version of the note
c.     Enter the Program name or Transaction code related to the error to get all the notes related to it.
d.     In case ABAP Dump enter the actual error like SQL_DUPREC_INSERT_ARRAY and program name
e.     Sometimes titles of the SAP note are misleading, so please make sure that you check all the notes.
f.     Most of the Notes released prior the release date of last applied patch may be not be relevant, but sometime there are notes available which are release independent.
10.     Plan for the user trainings should be finalized as soon as first level testing is over. The training should cover New GUI features and Delta training for transactions and new transactions if any.
11.     If possible follow Train the Trainer approach to speed up the training. This also ensures that responsibility of training lies with the client and not with us
12.     A feedback form must be filled by the users / Core team members for the training conducted.
13.     Cutover plan for Pre-Go live and after go-live should be prepared for smooth go live and a proper recording of the backlog.
14.     Finalize the Go-live dates with the help of the TOP MANAGEMENT once 90% of the testing is completed. Make sure that TOP MANAGEMENT is involved in issuing notifications to the users with regards to Non-availability of the SAP and activities required to be carried out before and after such period.
PRD Upgrade
1.     Take an offline backup on the cutoff date. Make sure that backup copy is a working one. To ensure this restore the backup once. This will serve as fallback in case of upgrade failure. This will increase the minimum shutdown time by approximate 8-9 Hours.
2.     A user with only display rights should be available during shutdown for OLD PRD system. This provides data traceability to the users.
3.     Import the Transport requests, once the Post processing activities are over
4.     Schedule SGEN for database Generation after the import of Transport requests. Make sure that enough archiving and Table space is available for ICNV and SGEN.
5.     Run conversion programs if any required.
6.     Release the system to functional consultant for Pre-Go Live test. Make sure that no one saves any transactions in PRD server
7.     Once Functional test is over by functional team, release the system to those users only whose work has been affected during the shutdown.
8.     For errors reported in PRD system, simulate the scenario first in Test upgrade server. If the same scenario can be simulated in Test server then find out a solution for the same. Otherwise check for missing customizing and master data errors.
9.     Once backlog of shutdown period is completed, release the system to other users.
Regards
Karthik

File mismatch

I had a linux 10g with 10g xe installed.
I stopped db, removed all db files and xe stuff, and installed 11g xe.
Then I created 2 extra tablespaces and imp(orted) a datafile with 10.2.0.3.0 oracle user's tables (from node 1 of a clustered enterprise edition database).
Here is what I get, very strange:
select ts.name, da.name, da.bytes, ta.status
from dba_tablespaces ta, v$tablespace ts,
v$datafile da
where da.ts#=ts.ts#
and ts.name=ta.TABLESPACE_NAME;
NAME
NAME
BYTES STATUS
SYSTEM
/u01/app/oracle/oradata/XE/system.dbf
377487360 ONLINE
SYSAUX
/u01/app/oracle/oradata/XE/undotbs1.dbf
555745280 ONLINE
UNDOTBS1
*/u01/app/oracle/oradata/XE/sysaux.dbf
5620367360 ONLINE*
USERS
/u01/app/oracle/oradata/XE/users.dbf
5242880 ONLINE
UNDOTBS2
/u01/app/oracle/oradata/XE/XE/datafile/o1_mf_undotbs2_6zyjnnxw_.dbf
104857600 ONLINE
INDX
/u01/app/oracle/oradata/XE/XE/datafile/o1_mf_indx_70oxvj27_.dbf
1048576000 ONLINE
T_JOBINS
/u01/app/oracle/oradata/XE/XE/datafile/o1_mf_t_jobins_6zyjqlbw_.dbf
10485760 ONLINE
USR
/u01/app/oracle/oradata/XE/XE/datafile/o1_mf_usr_6zykwso9_.dbf
104857600 ONLINE
ABIEC
/u01/app/oracle/oradata/XE/XE/datafile/o1_mf_abiec_70oxw6rw_.dbf
2097152000 ONLINE
9 rows selected.
SQL>
Problem 1:
undotbs1 is undo tablespace of 10.2.0.3.0 db.
Sysaux tablespace now works with undotbs1.dbf datafile, and undotbs1 undo tablespace now uses sysaux.dbf.
why why why? (This would have been difficult to do this using sql :) ).
Problem 2: sysaux.dbf datafile size grew to 5 Gb, I will have to look how to shrink it.

Tablespace-datafile names mix up reported earlier in {thread:id=2207251}.

Moving partitions

Hi guys.
Based on a new request, i need to create a script to backup and delete old data from our huge and many tables, which are growing a lot every day.
Backups to tapes will be done by db admins, so my sript should just move old partitions. I was thinking about to create extra tablespace where i will be moving those old partitions and data from this tablespace will be put on tapes and deleted later on. All tables are partitioned by time.
Could you please advise me how should i do so ? What is the best way to move huge partitions to diff. tablespace. Script will be run one per day
Thanks a lot

dusoo wrote:
No reply, so i guess there is no better way in ora10 for moving partitions between two partitioned tables ?
I still need to move it from source part. table to a non-part. table, and from there to the final part. tableYou need to understand that this two-way operation is not expensive if you simply want to bring a partition from one partitioned table to another one which is having the same partition boundary definitions. You're simply performing two exchange partition operations (partition<->unpartitioned, unpartitioned<->partitioned) which optimally can be pure data dictionary updates (there are exceptions to this rule if you e.g. have enabled unique constraints then the validation can not be skipped (WITHOUT VALIDATION clause)) and don't involve any actual data movement.
The expensive part in your particular case is the actual data movement to a different tablespace. The question is do you need to move the segments to a separate tablespace? Probably yes if you want to use a backup method based on binary copies of datafiles and tablespaces like RMAN. A logical export of the tables e.g. using datapump could be restricted to tables and/or partitions so you wouldn't need to perform an actual data movement.
Regards,
Randolf
Oracle related stuff blog:
http://oracle-randolf.blogspot.com/
SQLTools++ for Oracle (Open source Oracle GUI for Windows):
http://www.sqltools-plusplus.org:7676/
http://sourceforge.net/projects/sqlt-pp/

DB2 UDB - Oracle 10g Size Difference

Hi -
We are looking to migrate a production database from DB2 UDB to Oracle 10g. Can anyone provide any insight as to what kind of size changes we can expect?
Thanks!

I don't know even the a b c of DB2 but still I can say that it must be saving some sort of metadata as oracle. In oracle 10g the extra tablespaces which you must have to create are SYSTEM and SYSAUX which actually store the metadata and AWR information. How big your current database is on DB2, check it with and without metadata.
Daljit Singh

Generating traffic report of a tablespace or schema

Hello together,
at an Oracle 11gR2 (11.2.0.3.0) Enterprise Edition (fully licensed) with RHEL 6 as OS I'm trying to generate a statistic, that shows me a weekly or monthly report over the traffic on a tablespace or a schema.
Until now, I've worked with the HIST_VIEW dba_hist_tbspc_space_usage (I mean there is also one nearly called so for schema), but that view show me only the grow of a tablespace in a timeline of 1 week. But that would not be the hole traffic. Because SELECT statements will nothing do on the grow of the tablespace but it generates traffic.
In that case it wouldn't be so important, if it is more tablespace or schema sided because at this database each tablespace has it's own schema and timeline would be nice if it is weekly or monthly.
Does somebody of you know a way to generate such a report? I know I could do with some tcp_dump, but i would also see if there is also any Oracle database way.
Thanks and regards,
David

Thanks for your answer Justin!
That is what i meant with fully licensed. Performance and tuning pack is on board.
Directly, I can try the view tomorrow, I'm not at work right now.
But it sounded not like that what I'm searching for. Normally traffic should be something in MB or GB I think.
Better would be to describe, for whgat I need that: my company want's to "outsource" our dedicated server to an IAAS provider. To calculate the cost they need informatioin about:
The complete size of DB
Size of each schema / tablespace
And the traffic, because traffic generate extra cost
Traffic in this case doesn't mean only the shrink and grow of a schema or a tablespace (insert, update, delete) it also means the read out of data in the database by select or merge or something like that.
So the shrink and grow I'm able to calculate them by dba_hist_tbspc_space_usage by getting the size of a tablespace each hour and make an addition of the changes of the size. But here I can't see the traffic that is generating by everything else? And you mean, that can I do with DBA_HIST_SEG_STAT?
Regards,
David

Script for adding datafile to tablespace

Hi
Does anyone have a template alter tablespace add datafile script handy?
Basically, we need to, in the event of a tablespace alert, do two things:
query that tablespace to see how much space is remaining.
ascertain the size of the datafiles added to that tablespace already (to clarify what size we should make the additional datafile)
finally, the command itself for adding the extra datafile.
Thanks.
10.0.2.0

SELECT Total.tablespace_name "TSPACE_NAME",
round(nvl(TOTAL_SPACE,0),2) Tot_space,
round(nvl(USED_Space,0),2) Used_space,
round(nvl(TOTAL_SPACE - USED_Space,0),2) Free_space,
round(nvl(round(nvl((TOTAL_SPACE - USED_Space)*100,0),2)/(Total_space),0),2) "USED%"
FROM
(select tablespace_name, sum(bytes/1024/1024) TOTAL_SPACE
from sys.dba_data_files
group by tablespace_name
) Total,
(select tablespace_name, sum(bytes/1024/1024) USED_Space
from sys.dba_segments
group by tablespace_name
) USED
WHERE Total.Tablespace_name(+) = USED.tablespace_name and
round(nvl(round(nvl((TOTAL_SPACE - USED_Space)*100,0),2)/(Total_space),0),2)< 20;
the above query will display tablespaces which are having freespace below 20%
select file_name,autoextensible,sum(bytes)/1024/1024,sum(maxbytes)/1024/1024
from dba_data_files
where tablespace_name='TBS_NAME'
group by file_name,autoextensible;
the above query will give details of datafiles like autoextensible or not etc.
SELECT SUBSTR (df.NAME, 1, 40) file_name,dfs.tablespace_name, df.bytes / 1024 / 1024 allocated_mb,
((df.bytes / 1024 / 1024) - NVL (SUM (dfs.bytes) / 1024 / 1024, 0))
used_mb,
NVL (SUM (dfs.bytes) / 1024 / 1024, 0) free_space_mb
FROM v$datafile df, dba_free_space dfs
WHERE df.file# = dfs.file_id(+)
GROUP BY dfs.file_id, df.NAME, df.file#, df.bytes,dfs.tablespace_name
ORDER BY file_name;
the above query will show how much freespace is left in each datafile.

Shrinking a Locally Managed Temporary Tablespace

So, even thoguh the documentation is pretty clear about how to use this feature, I cannot get it to do what I expect it to do for me.
And that would be shrinking the tempfile ;)
Now lets face it, I have a large tempfile and want to resize it without restarting the database:
C:\Users\Administrator>sqlplus / as sysdba
SQL*Plus: Release 11.2.0.2.0 Production on Di Nov 20 05:49:59 2012
Copyright (c) 1982, 2010, Oracle. All rights reserved.
Connected to:
Oracle Database 11g Release 11.2.0.2.0 - 64bit Production
SQL> select file_name
, ceil(bytes / 1024 / 1024) "size MB"
from dba_temp_files
FILE_NAME size MB
R:\MXVC01\TEMP01.DBF 31,231
SQL> select su.username
, ses.sid
, ses.serial#
, su.tablespace
, ceil((su.blocks * dt.block_size) / 1048576) MB
from v$sort_usage su
, dba_tablespaces dt
, v$session ses
where su.tablespace = dt.tablespace_name
and su.session_addr = ses.saddr
USERNAME SID SERIAL# TABLESPACE MB
VPXADMIN 15 15 TEMP 14
VPXADMIN 17 5 TEMP 1,203
VPXADMIN 17 5 TEMP 1
VPXADMIN 18 3 TEMP 7
VPXADMIN 19 3 TEMP 1
VPXADMIN 144 3 TEMP 1
VUMADMIN 156 2597 TEMP 1
7 rows selected.
Or this one:
SQL> select tablespace_size/1024/1024 "tablespace_size mb"
, allocated_space/1024/1024 "allocated_space mb"
, free_space/1024/1024 "free_space mb"
from dba_temp_free_space
tablespace_size mb allocated_space mb free_space mb
31230,9922 1228,99219 30002
Documetation from here: http://docs.oracle.com/cd/E11882_01/server.112/e25494/tspaces007.htm#ADMIN12353
+"Shrinking a Locally Managed Temporary Tablespace+
+Large sort operations performed by the database may result in a temporary tablespace growing and occupying a considerable amount of disk space. After the sort operation completes, the extra space is not released; it is just marked as free and available for reuse. Therefore, a single large sort operation might result in a large amount of allocated temporary space that remains unused after the sort operation is complete. For this reason, the database enables you to shrink locally managed temporary tablespaces and release unused space.+
+You use the SHRINK SPACE clause of the ALTER TABLESPACE statement to shrink a temporary tablespace, or the SHRINK TEMPFILE clause of the ALTER TABLESPACE statement to shrink a specific tempfile of a temporary tablespace. Shrinking frees as much space as possible while maintaining the other attributes of the tablespace or tempfile. The optional KEEP clause defines a minimum size for the tablespace or tempfile.+
+Shrinking is an online operation, which means that user sessions can continue to allocate sort extents if needed, and already-running queries are not affected.+
+The following example shrinks the locally managed temporary tablespace lmtmp1 to a size of 20M.+
+ALTER TABLESPACE lmtemp1 SHRINK SPACE KEEP 20M;+
+The following example shrinks the tempfile lmtemp02.dbf of the locally managed temporary tablespace lmtmp2. Because the KEEP clause is omitted, the database attempts to shrink the tempfile to the minimum possible size.+
+ALTER TABLESPACE lmtemp2 SHRINK TEMPFILE '/u02/oracle/data/lmtemp02.dbf';"+
OK, lets do it:
SQL> alter tablespace temp shrink tempfile 'R:\MXVC01\TEMP01.DBF';
alter tablespace temp shrink tempfile 'R:\MXVC01\TEMP01.DBF'
ERROR at line 1:
ORA-03214: File Size specified is smaller than minimum required
It seems there is a bug? Should I report it, or is it the expected behaviour?
Now lets try this one:
SQL> alter tablespace temp shrink tempfile 'R:\MXVC01\TEMP01.DBF' keep 2048M;
Tablespace altered.
SQL> select file_name
, ceil(bytes / 1024 / 1024) "size MB"
from dba_temp_files
FILE_NAME size MB
R:\MXVC01\TEMP01.DBF 31,231
So .... this lasts about *10 minutes*, and nothing changes?
It seems there is a bug? Should I report it, or is it the expected behaviour?
Could someone enlighten me, what this SHRINK is actually doing?
Is it worth to report this as bug, if not a software bug it is at least a documentation bug because it doesn't mention under which conditions it is working?
P.S.: OMG the posting looks terrible, who's the one to blame for this forum software where it is not possible to use fixed size fonts, or format paragraphs as code, or what about the fact that the forum software is using default SQLPlus output as META for some graphical lines?
Isn't this the forum for Oracle Database users?
Edited by: Gerrit Haase on 20.11.2012 13:44

So, you are kidding with me? No? Who are you?
How can I block users here? Is there a moderator present at this forum?
Maybe you read my initial post again?
I didn't look at the wrong place.
I reported you for general abuse.
SQL> define
DEFINE _DATE           = "20.11.12" (CHAR)
DEFINE CONNECTIDENTIFIER = "MXVC01" (CHAR)
DEFINE _USER           = "SYS" (CHAR)
DEFINE _PRIVILEGE      = "AS SYSDBA" (CHAR)
DEFINE SQLPLUSRELEASE = "1102000200" (CHAR)
DEFINE _EDITOR         = "Notepad" (CHAR)
DEFINE OVERSION = "Oracle Database 11g Release 11.2.0.2.0 - 64bit Production" (CHAR)
DEFINE ORELEASE = "1102000200" (CHAR)
SQL> SELECT * FROM dba_temp_free_space;
TABLESPACE_NAME TABLESPACE_SIZE ALLOCATED_SPACE FREE_SPACE
TEMP 3,2748E+10 1306517504 3,1443E+10
SQL> select TABLESPACE_SIZE/power(2,20), ALLOCATED_SPACE/power(2,20), FREE_SPACE/power(2,20) from dba_temp_free_space ;
TABLESPACE_SIZE/POWER(2,20) ALLOCATED_SPACE/POWER(2,20) FREE_SPACE/POWER(2,20)
31230,9922 1245,99219 29986
SQL> ALTER TABLESPACE temp SHRINK SPACE;
Tablespace altered.
SQL> select TABLESPACE_SIZE/power(2,20), ALLOCATED_SPACE/power(2,20), FREE_SPACE/power(2,20) from dba_temp_free_space ;
TABLESPACE_SIZE/POWER(2,20) ALLOCATED_SPACE/POWER(2,20) FREE_SPACE/POWER(2,20)
31230,9922 1244,99219 *29986*
R:\mxvc01>dir temp
Volume in drive R is Disk_R
Volume Serial Number is 248B-61D4
Directory of R:\mxvc01
20.11.2012 08:09 32.748.077.056 TEMP01.DBF
1 File(s) 32.748.077.056 bytes
0 Dir(s) 8.259.297.280 bytes free
SQL> alter tablespace temp shrink tempfile 'R:\mxvc01\TEMP01.DBF';
alter tablespace temp shrink tempfile 'R:\mxvc01\TEMP01.DBF'
ERROR at line 1:
ORA-03214: File Size specified is smaller than minimum required
*It clearly says that there is 29986 MB Space FREE and the above shrink space changes nothing and so does shrink tempfile:*
SQL> alter tablespace temp shrink tempfile 'R:\mxvc01\TEMP01.DBF';
alter tablespace temp shrink tempfile 'R:\mxvc01\TEMP01.DBF'
ERROR at line 1:
ORA-03214: File Size specified is smaller than minimum required
SQL> alter tablespace temp shrink tempfile 'R:\mxvc01\TEMP01.DBF' KEEP 20M;
Tablespace altered.
R:\mxvc01>dir temp
Volume in drive R is Disk_R
Volume Serial Number is 248B-61D4
Directory of R:\mxvc01
20.11.2012 08:24 32.748.077.056 TEMP01.DBF
1 File(s) 32.748.077.056 bytes
0 Dir(s) 8.259.280.896 bytes free
*... nothing changes, the tempfile isn't smaller now ...*

9i - How to save everything in one tablespace and put back in later?

I'm trying to do a very simple refresh of a 9i database. Basically shutting it down and copying all the dbfs and redo files, then creating new controlfiles. However, the database that is the source does not have one dbf (and tablespace) that the target does. I plan on dropping the one extra dbf, and refreshing the target tb, then adding in the dbf and all it's objects.
I have already done this partly but have had problems. I'm not getting all the objects that are supposed to be there. I had to recreate the user that owns all the tables in the extra dbf tablespace. Plus, how do I make sure all the permissions are reset on these objects?
I am using TOAD, so I had tried the export feature and did get most of the info. I know how to create the dbf and recreate the user. Help?

Not a good way to do refresh in this way.
Use exp/imp to refresh or maintain exact same structure between database(s). You can then use rman's duplicate method for this purpose.

Backing up database with read-only tablespaces

I am trying to develop a script that will dynamically build RMAN scripts for backing up
a database with read-only tablespaces. The application running on this database creates
new tablespaces in read-write mode on weekly basis, populates them, and then puts them in read-only mode. So I need to backup all read-write tablespaces plus take backup of all read-only tablespaces once. The problem is that the application also includes a process that puts a tablespace back into read-write mode, updates it, and puts it back into read-write mode. So I need to be able to access "a history" of the tablespace - when was it put into read-only mode - to compare it with a history of backups. While history of backups is available in RMAN views, I couldn't find any way to extract tablspaces
history.
There should be RMAN command to the effect
"backup all read-write tablespaces and read-only tablespaces if they have not been backed up at least once since becoming read-only".
Regards,
Sev
null

just rsync the files to a compressed Zpool. do this using shadow migration, and you only loose access to the data for a few seconds.
1) make new dataset with compression
2) enable shadow migration between the new and old
3) change the database to use the new location
4) watch as data is automatically copied and compressed :-)
the the down side, you need extra space to pull the off.

TABLESPACE cleanup not happening after table data delete

Hi all
I have a partitioned table with 4 partitions all residing in a single tablespace. I populated the table with sample data and then deleted all with a simple delete statement followed by a commit. But the tablespace is still showing data from the 4 partitions under the bytes column in query below:
select segment_name, partition_name, tablespace_name, bytes
from dba_segments
where tablespace_name='tb_name'
Am I missing something here? Do I need to run some other command after delete and commit to fully flush out the data?
FYI, my system specs are:
Windows 2008 Server Standard (32-bit)
ORACLE 11.1.0.7.0

HI,
LMT is Locally Managed Tablespace.
+Moreover, when you say the blocks will not be available immediately when do you reckon they will be available? How do I go about automating this to free up space as soon as data is deleted?+
You cannot automate this job, this is already automated by Oracle.
+FYI, both pct_free and pct_used come up as empty values for my table.+
reason for a NULL-value for PCT_USED is that the tablespace where the table resides uses automatic segments space management (ASSM). With ASSM there is no need for PCT_USED only for PCT_FREE. Oracle manages blocks automatically.
You dont worry about releasing the space, Oracle will take care of it automatically.
Go through the below link
[http://download.oracle.com/docs/cd/B19306_01/server.102/b14231/tspaces.htm#ADMIN10065]
[http://download.oracle.com/docs/cd/B19306_01/server.102/b14231/schema.htm#sthref2100]
[http://www.dba-oracle.com/art_builder_assm.htm]
This is an extract form Oracle docs
Understanding Reclaimable Unused Space
Over time, updates and deletes on objects within a tablespace can create pockets of empty space that individually are not large enough to be reused for new data. This type of empty space is referred to as fragmented free space.
Objects with fragmented free space can result in much wasted space, and can impact database performance. The preferred way to defragment and reclaim this space is to perform an online segment shrink. This process consolidates fragmented free space below the high water mark and compacts the segment. After compaction, the high water mark is moved, resulting in new free space above the high water mark. That space above the high water mark is then deallocated. The segment remains available for queries and DML during most of the operation, and no extra disk space need be allocated.
You use the Segment Advisor to identify segments that would benefit from online segment shrink. Only segments in locally managed tablespaces with automatic segment space management (ASSM) are eligible. Other restrictions on segment type exist. For more information, see "Shrinking Database Segments Online".
If a table with reclaimable space is not eligible for online segment shrink, or if you want to make changes to logical or physical attributes of the table while reclaiming space, you can use online table redefinition as an alternative to segment shrink. Online redefinition is also referred to as reorganization. Unlike online segment shrink, it requires extra disk space to be allocated. See "Redefining Tables Online" for more information.Regards,
Vijayaraghavan K

Extra tablespaces

Similar Messages

Maybe you are looking for