Migration LONG to LOB in manual space management tablespaces

Hi everyone,
We have Netweaver 7.0 and Oracle 11g and we are considering to migrate our manual tablespaces to ASSM. The first problem we've found is we can't do that online due to the LONG data type. So we decided to migrate LONG to LOB first. Note 835552 says that for Oracle version 11g the conversion is from LONG to SECUREFILE. But we follow seeking notes and in 1426979 (Oracle 11g: SecureFiles - The new way to store LOB data) one of the prerequisites for the conversion is to use ASSM tablespaces.
At this point, we can't migrate (online) to ASSM due to LONG data and neither can migrate to SECUREFILE due to the ASSM.
My question is: is it possible to make the migration from LONG to SECUREFILE specifying in the brspace a new tablespace with ASSM?
Thanks in advanced.

Hello
It is in fact possible to reorganize segment to a specific target tablespace using brspace option -n|-newts
brspace -u / -f tbreorg -a long2lob -o sapsr3 -s <source_tablesapce> -t allsel -n <target_tablespace_in_ASSM>
It is odd that in 11g you are not in ASSM, so you upgrade to that version and never performed tablespace reorg ?
620803 - Oracle 9i: Automatic Segment Space Management
The new ASSM function is available as of Oracle Release 9i. As of Oracle 10g, ASSM is already contained in the standard system, and new tablespaces are by default created as ASSM tablespaces.
Regards

Similar Messages

Manual segment space managed tablespaces , How tune?

I use Manual segment space managed tablespaces.
How I can tuning for high performance?
What's advantage and disavantage of Manual segment space managed tablespaces and Auto segment space managed tablespaces?
if I used more data.
I'll use Auto or manual?
Please introduce me.

ASSM deal with freelist, freelist group(RAC) storage parameters. If you use ASSM you dont need to worry about adjusting freelist and group, oracle will automatically deal with it. If you are using manual storage segment management there would no problem unless you you see heavy buffer busy waits on your tables. You may also play with freelist value for tables which have concurrent inserts and access to avoid buffer busy waits.
From oracle 9i Rel 2 onwards, you have segment level statistics to find out which segments causing more buffer busy waits and tune them accordingly. There are other meaning for buffer busy waits, check v$event_name for buffe busy waits and find out the reason code for the cause of buffer busy waits event.
Jaffar

WSB manual space management

According to the
Backup Version and Space Management in Windows Server Backup article:
"If the backup storage location is full, Windows Server Backup automatically deletes the oldest backup version to make space for the current backup."
Is it possible to change WSB behavior to prevent a deletion of the old backups?
I want to manage the disk space in my own powershell script.

Hi,
If there is enough space for keeping backup, oldest backups will not be deleted.
Generally we prefer deleting oldest backups instead of failed to create new backup due to lack of free disk space.
To set a larger shadow storage space you could run "vssadmin resize shadowstorage".
If you have any feedback on our support, please send to [email protected]

Manual segment space management and LMT

hi,
I am reading a book that says:
Using manual space management requires the DBA or the creator of the segment to specify values for the PCTFREE, PCTUSED, FREELISTS, and FREELIST GROUPS parameters when creating the object and maintaining them as the volume of segment data increases.
EXAM TIP PCTFREE, PCTUSED, FREELISTS, and FREELIST GROUPS can be set only for dictionary-managed tablespaces.
This confuses me. Surely a LMT can have objects that have MSM and not ASSM, if so, why can those not objects have PCTFREE, PCTUSED, FREELISTS, and FREELIST GROUPS set?
thanks

sybrand_b wrote:
Confusion can best be resolved by referring to the official documentation (as opposed to cluttering up this forum full of doc questions with further doc questions).
Is there any particular reason (your boss beats you up when he sees you reading documentation) why you can't be bothered to visit http://tahiti.oracle.com, or do you -mistakingly- think this is an online chatroom, instead of an offline forum?
Sybrand Bakker
Senior Oracle DBAwhat kind of an answer is that? I mean, what is the points of books if docs were everything one ever needed? I have read something in a book that confuses me, and I disagree with, but maybe my understanding is wrong, so that is why I am come here to ask others for their opinion. What is wrong with that?

How to change segment space management (to manual)

How do I change the segment space management for a tablespace, from auto to manual
I can find documentation, to create tablespaces, and set them to auto, but nothing yet to change them from auto to manual.

I just found out, that I am confusing 2 subjects here: segment space management, and auto extensibility. My apologies ....... still new with Oracle :-o
Ok, to change autoextend to manual, do I do this on data_file level ? Do I only need to change this on the last datafile of a tablespace ?

Manual segment space management / want to shrink through segment advisor

I am trying to free space from table space , but i can't check the manual segment space manageme tablespaces, only auto segment space management allow me to do so. How i can do that?
any suggestions.

sybrand_b wrote:
Confusion can best be resolved by referring to the official documentation (as opposed to cluttering up this forum full of doc questions with further doc questions).
Is there any particular reason (your boss beats you up when he sees you reading documentation) why you can't be bothered to visit http://tahiti.oracle.com, or do you -mistakingly- think this is an online chatroom, instead of an offline forum?
Sybrand Bakker
Senior Oracle DBAwhat kind of an answer is that? I mean, what is the points of books if docs were everything one ever needed? I have read something in a book that confuses me, and I disagree with, but maybe my understanding is wrong, so that is why I am come here to ask others for their opinion. What is wrong with that?

Change SEGMENT SPACE MANAGEMENT from manual toAUTO

Hi, how can i to alter tablespace to SEGMENT SPACE MANAGEMENT AUTO ?
only with re-create the tablespace ?
regards
MDF

Hi,
Oracle says :
Your specification at tablespace creation time of your method for managing available space in segments, applies to all segments subsequently created in the tablespace. Also, your choice of method cannot be subsequently altered. Only permanent, locally managed tablespaces can specify automatic segment-space management.
Paolo

Problem about space management of archived log files

Dear friends,
I have a problem about space management of archived log files.
my database is Oracle 10g release 1 running in archivelog mode. I use OEM(web based) to config all the backup and recovery settings.
I config "Flash Recovery Area" to do backup and recovery automatically. my daily backup schedule is every night at 2:00am. and my backup setting is "disk settings"--"compressed backup set". the following is the RMAN script:
Daily Script:
run {
allocate channel oem_disk_backup device type disk;
recover copy of database with tag 'ORA$OEM_LEVEL_0';
backup incremental level 1 cumulative copies=1 for recover of copy with tag 'ORA$OEM_LEVEL_0' database;
the retention policy is the second choice, that is "Retain backups that are necessary for a recovery to any time within the specified number of days (point-in-time recovery)". the recovery window is 1 day.
I assign enough space for flash recovery area. my database size is about 2G. I assign 20G as flash recovery area.
now here is the problem, through oracle online manual, it said oracle can manage the flash recovery area automatically, that is, when the space is full, it can delete the obsolete archived log files. but in fact, it never works! whenever the space is full, the database will hang up! besides, the status of archived log files is very strange, for example, it can change "obsolete" stauts from "yes" to "no", and then from "no" to "yes". I really have no idea about this! even though I know oracle usually keep archived files for some longer days than retention policy, but I really don't know why the obsolete status can change automatically. although I can write a schedule job to delete obsolete archived files every day, but I just want to know the reason. my goal is to backup all the files on disk and let oracle automatically manage them.
also, there is another problem about archive mode. I have two oracle 10g databases(release one), the size of db1 is more than 20G, the size of db2 is about 2G. both of them have the same backup and recovery policy, except I assign more flash recovery area for db1. both of them are on archive mode. both of nearly nobody access except for the schedule backup job and sometime I will admin through oem. the strange thing is that the number of archived log files of smaller database, db2, are much bigger than ones of bigger database. also the same situation for the size of the flashback logs for point-in-time recovery. (I enable flashback logging for fast database point-in-time recovery, the flashback retention time is 24 hours.) I found the memory utility of smaller database is higher than bigger database. nearly all the time the smaller database's memory utility keeps more than 99%. while the bigger one's memory utility keeps about 97%. (I enable "Automatic Shared Memory Management" on both databases.) but both database's cup and queue are very low. I'm nearly sure no one hack the databases. so I really have no idea why the same backup and recovery policy will result so different result, especially the smaller one produces more redo logs than bigger one. does there anyone happen to know the reason or how should I do to check the reason?
by the way, I found web based OEM can't reflect the correct database status when the database shutdown abnormally. for example, if the database hang up because of out of flash recovery area, after I assign more flash recovery area space and then restart the database, the OEM usually can't reflect the correct database status. I must restart OEM manually to correctly reflect the current database status. does there anyone know in what situation I should restart OEM to reflect the correct database status?
sorry for the long message, I just want to describe in details to easy diagnosis.
any hint will be greatly appreciated!
Sammy

thank you very much, in fact, my site's oracle never works about managing archive files automatically although I have tried all my best. at last, I made a job running daily to check the archive files and delete them.
thanks again.

Roblem about space management of archived log files

Dear friends,
I have a problem about space management of archived log files.
my database is Oracle 10g release 1 running in archivelog mode. I use OEM(web based) to config all the backup and recovery settings.
I config "Flash Recovery Area" to do backup and recovery automatically. my daily backup schedule is every night at 2:00am. and my backup setting is "disk settings"--"compressed backup set". the following is the RMAN script:
Daily Script:
run {
allocate channel oem_disk_backup device type disk;
recover copy of database with tag 'ORA$OEM_LEVEL_0';
backup incremental level 1 cumulative copies=1 for recover of copy with tag 'ORA$OEM_LEVEL_0' database;
the retention policy is the second choice, that is "Retain backups that are necessary for a recovery to any time within the specified number of days (point-in-time recovery)". the recovery window is 1 day.
I assign enough space for flash recovery area. my database size is about 2G. I assign 20G as flash recovery area.
now here is the problem, through oracle online manual, it said oracle can manage the flash recovery area automatically, that is, when the space is full, it can delete the obsolete archived log files. but in fact, it never works! whenever the space is full, the database will hang up! besides, the status of archived log files is very strange, for example, it can change "obsolete" stauts from "yes" to "no", and then from "no" to "yes". I really have no idea about this! even though I know oracle usually keep archived files for some longer days than retention policy, but I really don't know why the obsolete status can change automatically. although I can write a schedule job to delete obsolete archived files every day, but I just want to know the reason. my goal is to backup all the files on disk and let oracle automatically manage them.
also, there is another problem about archive mode. I have two oracle 10g databases(release one), the size of db1 is more than 20G, the size of db2 is about 2G. both of them have the same backup and recovery policy, except I assign more flash recovery area for db1. both of them are on archive mode. both of nearly nobody access except for the schedule backup job and sometime I will admin through oem. the strange thing is that the number of archived log files of smaller database, db2, are much bigger than ones of bigger database. also the same situation for the size of the flashback logs for point-in-time recovery. (I enable flashback logging for fast database point-in-time recovery, the flashback retention time is 24 hours.) I found the memory utility of smaller database is higher than bigger database. nearly all the time the smaller database's memory utility keeps more than 99%. while the bigger one's memory utility keeps about 97%. (I enable "Automatic Shared Memory Management" on both databases.) but both database's cup and queue are very low. I'm nearly sure no one hack the databases. so I really have no idea why the same backup and recovery policy will result so different result, especially the smaller one produces more redo logs than bigger one. does there anyone happen to know the reason or how should I do to check the reason?
by the way, I found web based OEM can't reflect the correct database status when the database shutdown abnormally. for example, if the database hang up because of out of flash recovery area, after I assign more flash recovery area space and then restart the database, the OEM usually can't reflect the correct database status. I must restart OEM manually to correctly reflect the current database status. does there anyone know in what situation I should restart OEM to reflect the correct database status?
sorry for the long message, I just want to describe in details to easy diagnosis.
any hint will be greatly appreciated!
Sammy

thank you very much, in fact, my site's oracle never works about managing archive files automatically although I have tried all my best. at last, I made a job running daily to check the archive files and delete them.
thanks again.

White Space Management

Digging through the web trying to solve some white space
issues, i stumbled upon the CF Administrator setting in CFMX7
called White Space Management (under Server Settings). Enabling
this reduces the size of pages that are parsed (obviously), but are
there any consequences of enabling it? If there are not any
consequences, then why is it not enabled by default in CFAdmin?

i'm not sure the CF comment solution will work as
intended...from what i've read, the manual way to do it is to
either use the <cfsilent> tag (which suppresses all output to
the buffer) or use <cfsetting enablecfoutputonly="true"> to
only output to the buffer between cfoutput tags.
I'm thinking that the whtie space management option is a
solution to having to use these tags.
My question really is, is there a performance hit for using
it? how much? and does using it effect anything? (i've heard other
comments on how it sometimes interferes with using the cfmail
tag...which i'm not too worried about since we changed our mailer
to use something other than cfmail)

Datafile - space management

Hi,
Which is teh best practice in creating a tablespace? We have our production db on solaris. We are in teh process of migrating teh db into a linux box.
Our tablespaces comprises of one datafile each, and these datafiles are of size mostly over 3-4 gb
Is it advisable to create tablespace with multiple datafiles( eg three datafiles of one 1gb each) so that this I/O overhead is distributed equally among teh files.
Suppose tehre are more than one datafile for a tablespace..
How does data get stored in these files? I mean does these files get filled concurrently or does the second datafile start filling up only after the first datafile runs out of space?
Pls advise..
I want to know whether i have to split the large datafiles i have for my tablespaces when i create these tablespaces in teh linux box.
Pls advise

Hi,
>>I want to know how datafiles are wriitten..like if teh 2'nd datafile starts filling only if teh 1'st datifile is filled up
No. There is no order or rule for DBWn background process to writes on data files when a tablespace there are many data files, and 2'nd datafile can be used even if 1'st is not complete filled.
Look at the example below:
SYSTEM@teste> create tablespace test
2      datafile
3      '/u01/oradata/BDRPS/test01.dbf' size 5M,
4      '/u01/oradata/BDRPS/test02.dbf' size 5M,
5      '/u01/oradata/BDRPS/test03.dbf' size 5M,
6      '/u01/oradata/BDRPS/test04.dbf' size 5M,
7      '/u01/oradata/BDRPS/test05.dbf' size 5M,
8      '/u01/oradata/BDRPS/test06.dbf' size 5M
9      extent management local segment space management auto;
Tablespace created.
SYSTEM@teste> select   FILE_NAME AS DATAFILE,
2           d.TABLESPACE_NAME AS TABLESPACE,
3           d.BYTES/1048576 as SIZE_MB,
4           ROUND(sum(nvl(e.BYTES,0))/1048576) as USED_MB,
5           (round(sum(nvl(e.BYTES,0)) / (d.BYTES), 4) * 100) AS PERC_USED,
6           ROUND((d.BYTES - nvl(sum(e.BYTES),0))/1048576) AS FREE_SPACE_MB
7 from     DBA_EXTENTS e,    DBA_DATA_FILES d
8 where    d.FILE_ID = e.FILE_ID (+) AND d.tablespace_name = 'TEST'
9 group    by FILE_NAME, d.TABLESPACE_NAME, d.FILE_ID, d.BYTES, STATUS
10 order    by d.TABLESPACE_NAME, d.FILE_ID;
DATAFILE                                 TABLESPACE                        SIZE_MB    USED_MB PERC_USED FREE_SPACE_MB
/u01/oradata/BDRPS/test01.dbf            TEST                                    5          0          0             5
/u01/oradata/BDRPS/test02.dbf            TEST                                    5          0          0             5
/u01/oradata/BDRPS/test03.dbf            TEST                                    5          0          0             5
/u01/oradata/BDRPS/test04.dbf            TEST                                    5          0          0             5
/u01/oradata/BDRPS/test05.dbf            TEST                                    5          0          0             5
/u01/oradata/BDRPS/test06.dbf            TEST                                    5          0          0             5
6 rows selected.
SYSTEM@teste> create user scott identified by tiger default tablespace test quota unlimited on test;
User created.
SYSTEM@teste> grant connect to scott;
Grant succeeded.
SYSTEM@teste> connect scott/tiger@teste;
Conectado.
SCOTT@teste> create table emp (cod number);
Table created.
SCOTT@teste> begin
2    for i in 1..100000
3    loop
4     insert into emp values (i);
5    end loop;
6 end;
7 /
PL/SQL procedure successfully completed.
SCOTT@teste> commit;
Commit complete.
SCOTT@teste> connect system/manager@teste
SYSTEM@teste> select   FILE_NAME AS DATAFILE,
2           d.TABLESPACE_NAME AS TABLESPACE,
3           d.BYTES/1048576 as SIZE_MB,
4           ROUND(sum(nvl(e.BYTES,0))/1048576) as USED_MB,
5           (round(sum(nvl(e.BYTES,0)) / (d.BYTES), 4) * 100) AS PERC_USED,
6           ROUND((d.BYTES - nvl(sum(e.BYTES),0))/1048576) AS FREE_SPACE_MB
7 from     DBA_EXTENTS e,    DBA_DATA_FILES d
8 where    d.FILE_ID = e.FILE_ID (+) AND d.tablespace_name = 'TEST'
9 group    by FILE_NAME, d.TABLESPACE_NAME, d.FILE_ID, d.BYTES, STATUS
10 order    by d.TABLESPACE_NAME, d.FILE_ID;
DATAFILE                                 TABLESPACE                        SIZE_MB    USED_MB PERC_USED FREE_SPACE_MB
/u01/oradata/BDRPS/test01.dbf            TEST                                    5          0          0             5
/u01/oradata/BDRPS/test02.dbf            TEST                                    5          0          0             5
/u01/oradata/BDRPS/test03.dbf            TEST                                    5          0          0             5
/u01/oradata/BDRPS/test04.dbf            TEST                                    5          0          0             5
/u01/oradata/BDRPS/test05.dbf TEST 5 1 20 4
/u01/oradata/BDRPS/test06.dbf TEST 5 1 20 4
6 rows selected.
SYSTEM@teste> connect scott/tiger@teste;
Connected.
SCOTT@teste> insert into emp select * from emp;
100000 rows created.
SCOTT@teste> /
200000 rows created.
SCOTT@teste> commit;
Commit complete.
SCOTT@teste> insert into emp select * from emp;
400000 rows created.
SCOTT@teste> rollback;
Rollback complete.
SCOTT@teste> connect system/manager@teste
Connected.
SYSTEM@teste> select   FILE_NAME AS DATAFILE,
2           d.TABLESPACE_NAME AS TABLESPACE,
3           d.BYTES/1048576 as SIZE_MB,
4           ROUND(sum(nvl(e.BYTES,0))/1048576) as USED_MB,
5           (round(sum(nvl(e.BYTES,0)) / (d.BYTES), 4) * 100) AS PERC_USED,
6           ROUND((d.BYTES - nvl(sum(e.BYTES),0))/1048576) AS FREE_SPACE_MB
7 from     DBA_EXTENTS e,    DBA_DATA_FILES d
8 where    d.FILE_ID = e.FILE_ID (+) AND d.tablespace_name = 'TEST'
9 group    by FILE_NAME, d.TABLESPACE_NAME, d.FILE_ID, d.BYTES, STATUS
10 order    by d.TABLESPACE_NAME, d.FILE_ID;
DATAFILE                                 TABLESPACE                        SIZE_MB    USED_MB PERC_USED FREE_SPACE_MB
/u01/oradata/BDRPS/test01.dbf TEST 5 2 40 3
/u01/oradata/BDRPS/test02.dbf TEST 5 2 40 3
/u01/oradata/BDRPS/test03.dbf TEST 5 1 20 4
/u01/oradata/BDRPS/test04.dbf TEST 5 1 20 4
/u01/oradata/BDRPS/test05.dbf TEST 5 2 40 3
/u01/oradata/BDRPS/test06.dbf TEST 5 2 40 3
6 rows selected.You can see that the data files are been writing without a specific order.
Cheers

Segment space management

hai experts
can anyone tell me the reason why system tablespace's segment space management is manual. any link for the description

thanks Jonathan Ferreira
want to know why manual management is made as
default for system tablespace
hen auto space management will reduce the burden of a
DBA and make space management easyIf I had to make a guess, I would suggest that since the system tablespace contains rollback (undo) segments, ASSM cannot be used. With ASSM, the extent size starts small (64KB) and grows to 1MB, 8MB, etc. as additional extents are added to segments.
Since regular users should not be using the SYSTEM tablespace for inserts/updates/undo, there should be minimal burden for the DBA in managing that tablespace.
Charles Hooper
IT Manager/Oracle DBA
K&M Machine-Fabricating, Inc.

Space Management auto in Existing tablespace

Hi,
I already have several tablespaces for which I want to use/transfer to automatic space management, is it possible if yes, then How, Thanks in advance.
khawar.

If syed khawar ekram really is asking about ASM, automatic storage management, available with 10g then I think the answer is the same: Create a new tablespace using ASM files and migrate the objects.
I find conversion of dictionary managed tablespaces to locally managed using dbms_space_admin to not be worth the effort since your only option is the auto-allocate storage method and the procedure does not rebuild the objects leaving the tablespace a hodgepod of whatever happens to be there. It is generally worth the efford to build a new tablespace and migrate the objects.
IMHO -- Mark D Powell --

Oracle Free Space Management

Is Free Space Management a Initialization Parameters,
if so which one,
Where is Free Space Management keepth ?
Eric

Eric, Free space management is not a database parameter. You should read the Concepts manual. It explains Tablespace management and object management basics. Or you can see the chapters devoted to Tablespace and Object management in the DBA Administration Guide for a more detailed analysis.
To find free space in the database see the dictionary view: dba_free_space.
To how space management is handled for a tablespace see the dictionary view: dba_tablespaces.
HTH -- Mark D Powell --

ORACLE8I - LONG TYPE을 LOB TYPE으로 CONVERSION하는 방법(TO_LOB)

제품 : ORACLE SERVER
작성날짜 : 2002-04-12
ORACLE8I - LONG TYPE을 LOB TYPE으로 CONVERSION하는 방법(TO_LOB)
===============================================================
Purpose
Long type의 data를 lob type으로 conversion하는 to_lob function에 대해
알아보자.
Explanation
Oracle8 부터 long 이나 long raw type과는 별도로 lob type이 추가되었다.
long 이나 long raw type을 clob 또는 blob type으로 변경하기 위해서는
Oracle8 에서는 데이타를 다시 입력해야 했지만, Oracle8i 에서는 추가된
TO_LOB function을 이용하여 간단히 data migration을 할 수 있다.
TO_LOB function은 보통 create table .. as select .. 문장이나
insert into .. select .. 문장에서 쉽게 사용할 수 있다.
Example
[예제1] long type의 데이타를 clob type으로 옮기는 방법
아래의 예제에서 type만 long raw와 blob 로 바꾸어도 가능하다.
SQL> create table long_data (c1 number, c2 long);
Table created.
SQL> desc long_data
Name Null? Type
C1 NUMBER
C2 LONG
SQL> insert into long_data values
2 (1, 'This is some long data to be migrated to a CLOB');
1 row created.
SQL> create table test_lobs
2 (c1 number, c2 clob);
Table created.
SQL> desc test_lobs
Name Null? Type
C1 NUMBER
C2 CLOB
SQL> insert into test_lobs
2 select c1, to_lob(c2) from long_data;
1 row created.
SQL> select c2 from test_lobs;
C2
This is some long data to be migrated to a CLOB
[예제2] long type을 clob type으로 바꾸어 table 생성하는 방법
SQL> create table clob_data
2 as select c1, to_lob(c2) c2 from long_data;
Table created.
SQL> desc clob_data
Name Null? Type
C1 NUMBER
C2 CLOB
[예제3] long raw type을 blob type으로 바꾸어 table 생성하는 방법
SQL> desc image_data
Name Null? Type
C1 NUMBER
C2 LONG RAW
SQL> create table blob_data
2 as select c1, to_lob(c2) c2 from image_data;
Table created.
SQL> desc blob_data
Name Null? Type
C1 NUMBER
C2 BLOB

You may not insert LONGs into a table that are selected from a remote database. You can simply SELECT LONGs across a DB link, but you just can't INSERT... SELECT them.
Greg Pike
http://www.singlequery.com

Migration LONG to LOB in manual space management tablespaces

Similar Messages

Maybe you are looking for