SORT ARE SIZE

SORT operations are performed in temporary segments, then why SORT_AREA_SIZE is required?
regards
wire

i've checked log files, they do not contain information in this concern, i think i've made a mess by asking lot of questions. i just want to know what exactly redo log files contain, do they contain all sql statements? and how can i view redo log files contents?
regards
wire

Similar Messages

OEM 10g - reorganize tablespace error on invalid sort area size

Hi all,
When I try to reorganize a tablespace with OEM 10g, I get an error in the 3rd step (options) saying :
Invalid value for sort area size. The minimum value is 96 KB. My SGA management is set to AUTO.
Why this error on sort size area ?
Thanks for your help.

Found a workaround. ( Not a real answer to the "why" )
My settings were : pga_aggregate_target : 400 MB
work_area_policy : AUTO
Following the documentation the sort_area_size should then default to 20% of SGA ( which is 1200MB ), and should thus be 240 MB, largely sufficient I would think ...
I now changed the work_area_policy to MANUAL, and the sort_area_size to 100MB, and then it works fine.
If anyone would have an explanation for this, it is still most welcome !
Linde

Pga and sort area size both are set in parameter file

Hello,
Both the pga and sort area size are set in the parameter file. Is this an issue? Are there conflicts? Can both be set and only pga will take effect? Db is 10.1.0.5.

hi,
might also be worth looking at metalink note Note:223730.1
rgds
Alan

Sort Area Size in Automatic memory management

Hello All
I am aware that the AREASIZE is ignored of the PGA_AGGREGATE_TARGET is set.
So how is it possible that if we incrase the SORT_AREA_SIZE, the performance improves?
does this necessarily mean that the PGA_AGGREGATE_TARGET was not set to a proper value that it instead used the SORT_AREA_SIZE instead?
thanks

Hi,
If you have set workarea_size_policy=auto then under the automatic PGA memory management mode, sizing of work
areas for all sessions becomes automatic and the AREASIZE parameters are
ignored by all sessions running in that mode.
In auto mode if you change any AREASIZE parameters will be ignored.
If you want to manually handle ARASIZE then turnoff the Automatic pga memory by setting workarea_size_policy=MANUAL and then your changes to parameter will take effect but it's advisable to set pga to automatic.
To check whether your pga is set proper or not check v$pga_target_advice view
SELECT round(PGA_TARGET_FOR_ESTIMATE/1024/1024) target_mb,
ESTD_PGA_CACHE_HIT_PERCENTAGE cache_hit_perc,
ESTD_OVERALLOC_COUNT
FROM V$PGA_TARGET_ADVICE;
This will give you how your pga is set.
chirag

Sorting by size in lightroom

From Lightroom's first beta version I have been disappointed that there is no way to sort in the library module by image file size. Sorting by size is so common in computer programs. The mac operating system windows have had this option as far back as I can remember. I really miss it in organizing my files in Lightroom. I am presently using Lightroom 2.1.
Please add this to the next update.
Thanks.
Jim Klebau

I strongly support Simon Tindemans request
Simon Tindemans, "Allow import of and basic operations on non-image files (AVI, etc)" #15, 29 Jan 2009 11:41 pm (and I am sure from the others too, expressed or just wished for) that unsupported files should appear in the Grid mode with some kind of generic icon, and clicking on it would trigger the editing in the appropriate program (Photoshop, Illustrator, etc.) or allow copying them to some other location. Among 200,000-plus photos, still waiting in my server to be imported into LR and join those 100,000 already there - the legacy of my 7 years of the digital photography, there are the thousands of CMYK and PSD files, and digging them out by reading the printed list and then typing one by one the file names into the search field of browser's find feature, instead of just selecting the whole lot in the Grid module and opening them in the Photoshop with one click is, well, a stone-age method?
I also strongly support the James Klebau's request for file size sorting (and I add filtering too). Just as Mikael Albrecht, who explains the reasons for this to Wolf Eilers, the latter somehow not recognizing the need for this feature, and many others, I too have imported the thousands of jpg and tiff photos from the pre-LR and pre-RAW shooting era, all of them in the various sizes, from 600x400 pixels to 20x16" exhibition photos, besides the several hundreds of web albums' thumbnails which have crept in by mistake. To find them among the100,000-plus photos in the catalog is darn hard - I believe everyone will agree on this. Every other program, browser or DMA, has it and I was really surprised and disappointed when I realized that LR lacks this so common feature.
Finally I would like to see very much the additional Find and Replace option in the batch file (re)naming Editor. I have my own file naming system which besides the 4-digit file number suffix (usually the original one, sometimes created by sequence) incorporates also the 5-char theme and year prefix code, the location, and the 3-char code of the image type/purpose of the edited image (Exhibition, B&W, press, web...)
I often need to rename the batch of the photos, sometimes because I've goofed and exported the whole series of the photos, forgetting to change the previous file naming settings, but more often as at some latter time and for the various reasons I need to change the part of the file name - some code or the location - in the series of the photos.
When renaming the single file it would be also very helpful if the input field with the original file name would appear in the pop-up window besides the previous renaming setting, so one could simply (re)type in the needed change. In the Filename Template Editor, the only option where the file renaming can be carried out, the original name doesn't appear and the whole file name must be typed in - very cumbersome, time consuming, and error-prone. Perhaps this single file renaming option could appear in the context pop-up menu by right clicking on the image in question, upon which the input window would appear with the original file name already in the input window. Without doubt this would greatly expedite the single file renaming.
Misko

Data retrieval buffers - buffer size and sort buffer size

Any difference to tune BSO and ASO on data retrieval buffers?
From Oracle documentation, the buffer size setting is per database per Essbase user i.e. more physical memory will be used if there are lots of concurrent data access from users.
However even for 100 concurrent users, default buffer size of 10KB (BSO) or 20KB (ASO) seems very small compare to other cache setting (total buffer cache is 100*20 = 2MB). Should we increase the value to 1000KB to improve the data retrieval performance by users? The improvement impact is the same for online application e.g. Hyperion Planning and reporting application e.g. Financial Reporting?
Assume 3 Essbase plan types with 100 concurrent access:
PLAN1 - 1000KB * 100 = 100MB 1000KB * 100 = 100MB (total sort buffer size)
PLAN2 - 1000KB * 100 = 100MB 1000KB * 100 = 100MB (total sort buffer size)
PLAN3 - 1000KB * 100 = 100MB 1000KB * 100 = 100MB (total sort buffer size)
Total physical memory required is 600MB.
Thanks in advance!

256 samples Buffer size will always give you a noticable amount of latency. If you use Software Monitoring you should try setting your Buffer to 64 samples. With the recording delay slider in the preferences->Audio you can compensate for the latency (of course not in realtime) so that the Audio will be placed exactly there, where it should hae been recorded at. In your case set it to a -value. A loopback test (check the link below) will clarify the exact amount of Latency occuring on your system.
http://discussions.apple.com/thread.jspa?threadID=1883662&tstart=0

Sort Index Size failed in file

Hi Experts,
Do you have any idea why we get this error in MDS log file? I am sure you must have come across it, what could be a fix for it?
We have observed Log info "Sort Index Size failed in file" logged into MDS Log file while doing following:
It happens during following processes:
a)_Master Slave Sync between Master and Slave Repo->> MDSAdminServer@GetAndApplyMasterChangeRep_
2010-08-05T12:00:01.012 14 23 Condition: pos < sortIndexSize failed in file /export/home/builder/mdm.build/7.1.03.xx/Cpp/MDM/Servers/MDS /DataMgmt/Update.cpp , line 1097
MDSAdminServer@GetAndApplyMasterChangeRep Dbg.cpp 65
Admin SRM_MDM_CATALOG_CHILDPROD3-DB- HA:1527/PMDORCL_21_20_4_3
b)_Remove Records from Data Manager->> CatMgr@RemoveRecords336_
2010-07-30T21:00:02.378 42 23 Condition: pos < sortIndexSize failed in file /export/home/builder/mdm.build/7.1.03.xx/Cpp/MDM/Servers/MDS/DataMgmt/Update.cpp , line 1097
MDSAdminServer@GetAndApplyMasterChangeRep Dbg.cpp 65
Admin SRM_MDM_CATALOG_CHILDPROD3-DB- HA:1527/PMDORCL_21_20_4_3
c)_Update Records from Data Manager->> CatMgr@ModifyRecords326_
2010-08-04T22:24:11.602 43 23 Condition: pos < sortIndexSize failed in file /export/home/builder/mdm.build/7.1.03.xx/Cpp/MDM/Servers/MDS/DataMgmt/Update.cpp , line 1097 CatMgr@RemoveRecords336 Dbg.cpp 65 49 harrik3 SRM_MDM_CATALOG <PROD3-DB-HA:1527/PMD[Oracle]>
As the Log Info name indicates "Sort Index Size failed in file", we are wondering is there anything to do with the -Size of Index File. Is there any parameter in DB side or in MDS which controls logging file size. May be that file size is not allowing Index sorting to be written into that file and file gets overflown due to less file size and MDS Logs this "Log Info". And since Indexing is not completed and not written into Index file, eventually the search made thru Advance Search gets weird and start throwing null pinter exception in browser because Index is not present for some searches.
This error seems like some unhandled exception code in program- Update.cpp at line 1097.
I would appreciate if you can throw some light on this and how to avoid this?
Regards
Pravin

Hi Jignesh and Ravi,
There is no Repo schema change and we made sure that we create new slave after any Repo schema change. I dont think there is an issue with master-slave, but issue probably lies some where else.
In fact my original question is scrambled. Let me mention it again clearly. Its not alone master-slave sync we get this log info-" Sort Index Size failed in file". Actually we get it during following 3 operations:
a) On Master Slave Sync between Master and Slave Repo->> MDSAdminServer@GetAndApplyMasterChangeRep
b) OnRemove Records from Data Manager in master->> CatMgr@RemoveRecords336
c) On Updating Records in Data Manager->> CatMgr@ModifyRecords326
Is there anything to do with the -Size of Index File. Is there any parameter in DB side or in MDS which controls logging file size. This error seems like some unhandled exception code in program- Update.cpp at line 1097.
_Pravin

Folder mis sorted by size

I have a folder on my desktop.. I copied many items from my applications folder there (only the things I have downloaded) I am burning the extra apps to CD, ones I don't use.
Moved apps to folder
duplicated folder
Put duplicate back into apps folder
Made archives of each item
Sorted by size
--- Things are not properly sorted??
top few things in order 388kb, 120kb, 16.2mb, 4kb, 96kb, 12kb
The folder is sorted by size with the triangle next to "Size" pointing downward.
What's up?

Hi Ronald,
Welcome to Apple Discussions
Try verifying and repairing permissions (Knowledge Base Document #106712 on Troubleshooting permissions issues in Mac OS X). Have you restarted your computer?
Jon
Mac Mini 1.42Ghz, iPod (All), Airport (Graphite & Express), G4 1.33Ghz iBook, G4 iMac 1Ghz, G3 500Mhz, iBook iMac 233Mhz, eMate, Power Mac 5400 LC, PowerBook 540c, Macintosh 128K, Apple //e, Apple //, and some more... Mac OS X (10.4.5) Moto Razr, iLife '06, SmartDisk 160Gb, Apple BT Mouse, Sight..

Why is the Log Area size much smaller than the log volume

I have been following up on an Early Watch report that has been generated for our production SCM 5.0 system running liveCache 7.6.02 Build 14. The alert says "The LOG volumes size in your system is too small. Recommendation: Configure LOG Volumes to at least 2 GB". There are two interesting things about this.
1) I have spent the last couple of days reading all the OSS Notes, and MaxDB documentation I could find, and this does not seem to be documented as a recommendation anywhere. Does this seem like a realistic recommendation without taking into account the level of change actifity?
2) There is a single log volume allocated with size 2,097,160 KB. In production LC10 and DBMGUI report this to be correct size under volume details, but only list the total log area size as 1,706,328 (81% of the volume size). We have a non-production environment with exactly the same size log volume, but it reports that the log area size is 2,032,008 KB (97% of the volume). What leads to these different amounts of wasted space, and is there any way of getting the database to start using it?
Thanks,
Mark

Hi Natalia,
I did read 869267, several times. It does not answer my questions which is why I posted here.
DBMGUI version = 7.6.00.25
DBMCLI commands for PL1 (Production)
> xinstinfo PL1
IndepData           : /sapdb/data
IndepPrograms       : /sapdb/programs
InstallationPath    : /sapdb/PL1/db
Kernelversion       : KERNEL    7.6.02   BUILD 014-123-152-175
Rundirectory        : /sapdb/data/wrk/PL1
> dbmcli -d PL1 -u control,control
dbmcli on PL1>db_state
OK
State
ONLINE
dbmcli on PL1>info log
OK
END
Name                            | Value
Log Mirrored                    = NO
Log Writing                     = ON
Log Automatic Overwrite         = OFF
Max. Size (KB)                  = 1706328
Backup Segment Size (KB)        = 699048
Used Size (KB)                  = 104640
Used Size (%)                   = 6
Not Saved (KB)                  = 104640
Not Saved (%)                   = 6
Log Since Last Data Backup (KB) = 0
Savepoints                      = 5210
Checkpoints                     = 0
Physical Reads                  = 2469115
Physical Writes                 = 15655616
Queue Size (KB)                 = 48000
Queue Overflows                 = 646
Group Commits                   = 98205
Waits for Logwriter             = 10957511
Max. Waits                      = 10
Average Waits                   = 0
OMS Log Used Pages              = 0
OMS Min. Free Pages             = 0
dbmcli on PL1>param_getvolsall
OK
LOG_MIRRORED                     NO
MAXLOGVOLUMES                    2
MAXDATAVOLUMES                   14
LOG_VOLUME_NAME_001              262145     F /sapdb/PL1/saplog/DISKL001
DATA_VOLUME_NAME_0001            524289     F /sapdb/PL1/sapdata/DISKD0001
DATA_VOLUME_NAME_0002            524289     F /sapdb/PL1/sapdata/DISKD0002
DATA_VOLUME_NAME_0003            524289     F /sapdb/PL1/sapdata/DISKD0003
DATA_VOLUME_NAME_0004            524289     F /sapdb/PL1/sapdata/DISKD0004
DATA_VOLUME_NAME_0005            524289     F /sapdb/PL1/sapdata/DISKD0005
DATA_VOLUME_NAME_0006            524289     F /sapdb/PL1/sapdata/DISKD0006
DATA_VOLUME_NAME_0007            524289     F /sapdb/PL1/sapdata/DISKD0007
DATA_VOLUME_NAME_0008            524289     F /sapdb/PL1/sapdata/DISKD0008
DATA_VOLUME_NAME_0009            1048577    F /sapdb/PL1/sapdata/DISKD0009
DATA_VOLUME_NAME_0010            1048577    F /sapdb/PL1/sapdata/DISKD0010
DATA_VOLUME_NAME_0011            1048577    F /sapdb/PL1/sapdata/DISKD0011
DATA_VOLUME_NAME_0012            1048577    F /sapdb/PL1/sapdata/DISKD0012
dbmcli on PL1>param_directget MAXCPU
OK
MAXCPU 12
dbmcli on PL1>param_directget MAX_LOG_QUEUE_COUNT
OK
MAX_LOG_QUEUE_COUNT     0
dbmcli on PL1>param_directget LOG_IO_QUEUE
OK
LOG_IO_QUEUE    6000
> xinstinfo SL1
IndepData           : /sapdb/data
IndepPrograms       : /sapdb/programs
InstallationPath    : /sapdb/SL1/db
Kernelversion       : KERNEL    7.6.02   BUILD 014-123-152-175
Rundirectory        : /sapdb/data/wrk/SL1
dbmcli on SL1>db_state
OK
State
ONLINE
dbmcli on SL1>info log
OK
END
Name                            | Value
Log Mirrored                    = NO
Log Writing                     = ON
Log Automatic Overwrite         = OFF
Max. Size (KB)                  = 2032008
Backup Segment Size (KB)        = 699048
Used Size (KB)                  = 3824
Used Size (%)                   = 0
Not Saved (KB)                  = 3824
Not Saved (%)                   = 0
Log Since Last Data Backup (KB) = 0
Savepoints                      = 1256
Checkpoints                     = 0
Physical Reads                  = 2178269
Physical Writes                 = 4969914
Queue Size (KB)                 = 16000
Queue Overflows                 = 21201
Group Commits                   = 643
Waits for Logwriter             = 751336
Max. Waits                      = 4
Average Waits                   = 0
OMS Log Used Pages              = 0
OMS Min. Free Pages             = 0
dbmcli on SL1>param_getvolsall
OK
LOG_MIRRORED                     NO
MAXLOGVOLUMES                    2
MAXDATAVOLUMES                   10
LOG_VOLUME_NAME_001              262145     F /sapdb/SL1/saplog/DISKL001
DATA_VOLUME_NAME_0001            262145     F /sapdb/SL1/sapdata1/DISKD0001
DATA_VOLUME_NAME_0002            262145     F /sapdb/SL1/sapdata2/DISKD0002
DATA_VOLUME_NAME_0003            1048577    F /sapdb/SL1/sapdata3/DISKD0003
DATA_VOLUME_NAME_0004            1048577    F /sapdb/SL1/sapdata4/DISKD0004
DATA_VOLUME_NAME_0005            783501     F /sapdb/SL1/sapdata1/DISKD0005
DATA_VOLUME_NAME_0006            783501     F /sapdb/SL1/sapdata2/DISKD0006
dbmcli on SL1>param_directget MAXCPU
OK
MAXCPU 4
dbmcli on SL1>param_directget MAX_LOG_QUEUE_COUNT
OK
MAX_LOG_QUEUE_COUNT     0
dbmcli on SL1>param_directget LOG_IO_QUEUE
OK
LOG_IO_QUEUE    2000
Thanks for the explaination of the reserved space for the Log Queue pages. This does explain why there is the difference between the two. I think we probably have our log segment size too large. As you can see we do get occasional log queue overflows. Do you suggest we increase the size of our log IO queue higher, and allocate more log volume space to compensate?
select * from SYSINFO.LOGSTATISTICS (on PL1)
1706328;334176;19;334176;19;1879;20305192;64109066;7806480;182151514;12;48000
DBMGUI Log Area Usage
Total Size: 2048.01 MB
Free Log Area: 1330.38 MB
Used Log Area: 335.96 MB
Unsaved Log Area: 335.96
Log since Last Data Backup: 0.00 MB
Thanks,
Mark

IPhoto library too big -- how do I sort video, size to remove/archive?

Okay folks. So my iphoto library has gotten so big, I can't even install updates on my MacBook. Normally with any files on my computer, I can sort by size...see who's hogging up space and what I don't need. Not only can I not sort by size, I really have no way of managing these files in finder.
Advice?
Saw previous posts about "no sort by size". Someone even said "iPhoto is a photo manager, not a file manager" -- cute, but at some point the space runs out.

I really have no way of managing these files in finder.
It is strongly recommended that you do not use the finder to delete, move or otherwise modify any files within the iPhoto library - doing so risks corrupting your library and losing data
If you want to delete anything in the iPhoto library you must us the iPhoto program to do it
To identify your movies you can make a smart album for all items with the keyword = movie - selecting one and looking in the information window at the lower left hand corner will show you its size
LN

Excecution plan Area + Sort area

Dear Friends,
Some selects of our application is relatively slow in some location (When database is slow) . But same selects shown good performance in most of the time. Database is always not slow in peak hours. I feel there would be insufficient space in Execution plan area or Sort area.
Can you give me how i change these settings in my database. and where these execution plan and sort area located.
regards
upul Indika.

Collect trace information for the application sessions (or instance). Use Statspack or AWR to collect workload snapshots. Then analyse the results to see where the bottlenecks is.

How to find JPanel viewable or drawing area size

hi,
I have a two small question. First one is, I have a JPanel what I need is to find the viewable area size or the drawing size of the Panel. I don't want to get the size of the Title bar. All I need is how to find the actual drawing area not including the title bar. I know how to get the total size of the JPanel, I just needs to know how to get the drawing area size where you put your components. e.g. if the size of my Panel is (300,300) then it also includes the title bar and the border too. But I need to find or get only the area size where we actually put our components.
Another question is how can I get the size of my Title bar means the width and height.
I'll really appreciate for any help
Thanks

Er... what's wrong with panel.getSize()?

How to increare roll area size programmatically? Is there any code?

Hello everyone:
          I am running a program that goes to dump with an error "roll area size too small" in ECC6.0. The same program works fine in 4.6C. We worked with BASIS to set roll area related paramteres, logged OSS notes and set parameters as SAP suggested but nothing worked! Is there any function module or any code that I could use to free the roll area size in the program? Rewards assured.
Thanks.
Mithun

Thanks everyone for the feedback. I did work with SAP and had BASIS set the parameters as per the suggestions by SAP and after going back and forth they said it might be a program issue. This is the Z program and this is the code where it goes to DUMP with the error "Roll area too small".
================================================
CALL FUNCTION 'GET_PRINT_PARAMETERS'
      EXPORTING
        authority              = space
        immediately            = space
        new_list_id            = c_x
        no_dialog              = c_x
       user                   = sy-uname
      IMPORTING
        out_parameters         = params
      EXCEPTIONS
        archive_info_not_found = 1
        invalid_print_params   = 2
        invalid_archive_params = 3
        OTHERS                 = 4.
    IF sy-subrc NE 0.
      CLEAR : params.
    ENDIF.
The printer destination has to be set up
    params-pdest = v_dest.
    params-prtxt = v_spool_text.
    params-paart = c_paart.
    params-prtxt = v_spool_text.
    params-primm = 'X'.
    params-prrel = space.
    NEW-PAGE PRINT ON PARAMETERS params NO DIALOG.
    NEW-PAGE PRINT OFF.
===========================================
I used FREE statements in the program to free internal tables and if I remove the code above the program runs successfully! This works fine in 4.6C! All the paramters like roll area and stuff is more in ECC6.0 compared to 4.6C but the program still abends!! Please let me know if there is any resolution!!
*I am rewarding all the answers*
Thanks.
Mithun

IPad photos sort by size, largest disk size to smallest?

iPad photos sort by size, largest disk size to smallest?

PS. I searched for exact phrase "sort iPad photos by size" on Google and I am aghast that there were ZERO RESULTS.
https://www.google.com/search?site=webhp&ei=yEsuU9nNGYzkoASmmILoBQ&q=%22sort+iPa d+photos+by+size%22&oq=%22sort+iPad+photos+by+size%22&gs_l=mobile-gws-serp.3..0i 22i30.19488.31073.0.31755.19.19.0.0.0.2.350.3389.0j15j3j1.19.0....0...1c.1.37.mo bile-gws-serp..2.17.2771.LsiZBTPRvQk

What is the "sorting" area in the Get Info menu?

I would like to know what the sorting area does but I also have a specific question.
I bought the singles for an album, but now that the album came out, the singles and the rest of the album are grouped seperately. When I try to play songs of just that album on iTunes or on my iPhone, the singles are excluded. Can I use the "Sort album" field in the Get Info menu for the singles to group them with the album? Will I lose the album artwork of the singlesitunes?

Thanks for the reply.
Strangely enough I didn't find any information on it in the help system, in the knowlegebase, or any of my Tiger books. Seems this was overlooked in just about everything.

SORT ARE SIZE

Similar Messages

Maybe you are looking for