How to increase the time at the end of what aaa requeries the authentication of a client web

Hi All,
I configure ASA aaa to authentificate our internal web client to access to internet. It's check the username/password of client in our Active Directory.
When the client initiate the first connexion, the ASA request the login connexion and when it's correct, it authorise the access. But after 10 min for exemple, it's request again the login, and so one and so one. Approximativelly, after each ten minute, it requeste an username/password.
I want to know how can i increase the time between two authentifcation. Or increase the time of 10 min.
Thanks.

The authentication timeout is configurable via the "timeout uauth" command, and you can set either absolute or inactivity timeout.
Here is the command for your reference:
http://www.cisco.com/en/US/docs/security/asa/asa84/command/reference/t.html#wp1569874

Similar Messages

I am using my first apple product, mac book pro. somehow i FIGURED OUT HOW TO INCREASE THE FONT FOR SEARCHES AND WEB PAGES, BUT THE FONT IS TOO BIG AND FOR THE LIFE OF ME I CAN NOT FIND WHERE TO GET THE SCREEN BACK TO NORMAL, HELP ANYONE?

I am new to Apple, somehow I figured out how to make font of Web pages bigger, but it is too big and I can't use sites properly. for the life of me I can not how to get my font size reduced. Help anyone? thank you, sbb

Probably command-minus will do the trick.

How to increase the waiting time for response in Adapter Engine not in IE

Hi Experts,
It is a SOAP to Proxy Synchronous interface. SOAP system is sending the request to PI, PI sending the same request to ECC system, After execution of some logic response back to PI in 7 minutes. In ABAP Stack(sxmb_moni) processing the response message also successfully with success flag after completion of these 7 minutes. But exactly 5 minutes later getting the error at Java Stack RWB- in communication channel monitoring i.e
com.sap.engine.interfaces.messaging.api.exception.MessagingException: com.sap.engine.interfaces.messaging.api.exception.MessageExpiredException: Message bd2bf8d0-b2c2-11e0-c383-001cc4fb5cb7(OUTBOUND) expired. We have set the "runtime-HTTP_TIMEOUT" parameter as 3600. thats why in Integration engine it is processing successfully.
kindly suggest me how to increase the waiting time for response in Adapter Engine. Exactly after 5 mins getting the above error in rwb, but in Integration Engine getting successful flag after 7 mins until then it is waiting for response with status flag Log version.
Thanks & Regards,
Srihari.

Hi,
Please see
How To... Investigate Timeouts In Synchronous XI/PI Scenarios
It will answer all your queries
http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/c059d583-a551-2c10-e095-eb5d95e03747?QuickLink=index&overridelayout=true

How to increase the time for detect a device down on Prime 2.0

Hi,
I would like to know how to increase the time for detect when a device has lost connection, currently I monitor several stand alone Access Points that are paleced on differents locations connected to prime through 256 Mbps Links, so when the location has very high bandwith utilization, an e-mail notification about the unreachable Access Point is sent, but if we check te reachability, the Access Point is reachable, and we don´t want to receive to many of this notificatios,
thanks for your help

Go to the Console, Select the server --> configuration --> tuning tab,
Stuck Thread Max Time and Stuck Thread Timer Interval (give your required time)
This will definitely increase the Stuck Thread time interval.
or
by using work manager also you can define Stuck Thread Max Time interval by editing deployment descriptor file
<work-manager>
<name>wm_name</name>
<max-stuck-thread-time>30</max-stuck-thread-time>
<stuck-thread-count>5</stuck-thread-count>
</work-manager>

How to increase the length of internal table dynamically

How to increase the length of internal table dynamically depending on the number of fields fetched into the internal table ?
The requirement code :
types: begin of t_data,
         form          like zscr_data_hdr-form,
         werks         like zscr_data_hdr-werks,
         matnr         like zscr_data_hdr-matnr,
         verid         like zscr_data_hdr-verid,
         lot           like zscr_data_hdr-lot,
         lot_qty       like zscr_data_hdr-lot_qty,
         udate         like zscr_data_hdr-udate,
         utime         like zscr_data_hdr-utime,
         zuser         like zscr_data_hdr-zuser,
         processed     like zscr_data_hdr-processed,
         defect        like zscr_defect_data-defect,
         vornr         like zscr_route_data-vornr,
         fld1          like zscr_defect_data-defect_val,
         fld2          like zscr_defect_data-defect_val,
         fld3          like zscr_defect_data-defect_val,
         fld4          like zscr_defect_data-defect_val,
         fld5          like zscr_defect_data-defect_val,
         fld6          like zscr_defect_data-defect_val,
         fld7          like zscr_defect_data-defect_val,
         fld8          like zscr_defect_data-defect_val,
         fld9          like zscr_defect_data-defect_val,
         fld10         like zscr_defect_data-defect_val,
         fld11         like zscr_defect_data-defect_val,
         fld12         like zscr_defect_data-defect_val,
         fld13         like zscr_defect_data-defect_val,
         fld14         like zscr_defect_data-defect_val,
         fld15         like zscr_defect_data-defect_val,
         fld16         like zscr_defect_data-defect_val,
         fld17         like zscr_defect_data-defect_val,
         fld18         like zscr_defect_data-defect_val,
         fld19         like zscr_defect_data-defect_val,
         fld20         like zscr_defect_data-defect_val,
         fld21         like zscr_defect_data-defect_val,
         fld22         like zscr_defect_data-defect_val,
         fld23         like zscr_defect_data-defect_val,
         fld24         like zscr_defect_data-defect_val,
         fld25         like zscr_defect_data-defect_val,
         fld26         like zscr_defect_data-defect_val,
         fld27         like zscr_defect_data-defect_val,
         fld28         like zscr_defect_data-defect_val,
         fld29         like zscr_defect_data-defect_val,
         fld30         like zscr_defect_data-defect_val,
         fld31         like zscr_defect_data-defect_val,
         fld32         like zscr_defect_data-defect_val,
         fld33         like zscr_defect_data-defect_val,
         fld34         like zscr_defect_data-defect_val,
         fld35         like zscr_defect_data-defect_val,
         fld36         like zscr_defect_data-defect_val,
         fld37         like zscr_defect_data-defect_val,
         fld38         like zscr_defect_data-defect_val,
         fld39         like zscr_defect_data-defect_val,
         fld40         like zscr_defect_data-defect_val,
         fld41         like zscr_defect_data-defect_val,
         fld42         like zscr_defect_data-defect_val,
         fld43         like zscr_defect_data-defect_val,
         fld44         like zscr_defect_data-defect_val,
         fld45         like zscr_defect_data-defect_val,
         fld46         like zscr_defect_data-defect_val,
         fld47         like zscr_defect_data-defect_val,
         fld48         like zscr_defect_data-defect_val,
         fld49         like zscr_defect_data-defect_val,
         fld50         like zscr_defect_data-defect_val,
         fld51         like zscr_defect_data-defect_val,
         fld52         like zscr_defect_data-defect_val,
         fld53         like zscr_defect_data-defect_val,
         fld54         like zscr_defect_data-defect_val,
         fld55         like zscr_defect_data-defect_val,
         fld56         like zscr_defect_data-defect_val,
         fld57         like zscr_defect_data-defect_val,
         fld58         like zscr_defect_data-defect_val,
         fld59         like zscr_defect_data-defect_val,
         fld60         like zscr_defect_data-defect_val,
         fld61         like zscr_defect_data-defect_val,
         fld62         like zscr_defect_data-defect_val,
         fld63         like zscr_defect_data-defect_val,
         fld64         like zscr_defect_data-defect_val,
         fld65         like zscr_defect_data-defect_val,
         fld66         like zscr_defect_data-defect_val,
         fld67         like zscr_defect_data-defect_val,
         fld68         like zscr_defect_data-defect_val,
         fld69         like zscr_defect_data-defect_val,
         fld70         like zscr_defect_data-defect_val,
         fld71         like zscr_defect_data-defect_val,
         fld72         like zscr_defect_data-defect_val,
         fld73         like zscr_defect_data-defect_val,
         fld74         like zscr_defect_data-defect_val,
         fld75         like zscr_defect_data-defect_val,
         fld76         like zscr_defect_data-defect_val,
         fld77         like zscr_defect_data-defect_val,
         fld78         like zscr_defect_data-defect_val,
         fld79         like zscr_defect_data-defect_val,
         fld80         like zscr_defect_data-defect_val,
         fld81         like zscr_defect_data-defect_val,
         fld82         like zscr_defect_data-defect_val,
         fld83         like zscr_defect_data-defect_val,
         fld84         like zscr_defect_data-defect_val,
         fld85         like zscr_defect_data-defect_val,
         fld86         like zscr_defect_data-defect_val,
         fld87         like zscr_defect_data-defect_val,
         fld88         like zscr_defect_data-defect_val,
         fld89         like zscr_defect_data-defect_val,
         fld90         like zscr_defect_data-defect_val,
         fld91         like zscr_defect_data-defect_val,
         fld92         like zscr_defect_data-defect_val,
         fld93         like zscr_defect_data-defect_val,
         fld94         like zscr_defect_data-defect_val,
         fld95         like zscr_defect_data-defect_val,
         fld96         like zscr_defect_data-defect_val,
         fld97         like zscr_defect_data-defect_val,
         fld98         like zscr_defect_data-defect_val,
         fld99         like zscr_defect_data-defect_val,
         fld100         like zscr_defect_data-defect_val,
         fld101         like zscr_defect_data-defect_val,
         fld102         like zscr_defect_data-defect_val,
         fld103         like zscr_defect_data-defect_val,
         fld104         like zscr_defect_data-defect_val,
         fld105         like zscr_defect_data-defect_val,
         fld106         like zscr_defect_data-defect_val,
         fld107         like zscr_defect_data-defect_val,
         fld108         like zscr_defect_data-defect_val,
         fld109         like zscr_defect_data-defect_val,
         fld110         like zscr_defect_data-defect_val,
         fld111         like zscr_defect_data-defect_val,
         fld112         like zscr_defect_data-defect_val,
         fld113         like zscr_defect_data-defect_val,
         fld114         like zscr_defect_data-defect_val,
         fld115         like zscr_defect_data-defect_val,
         fld116         like zscr_defect_data-defect_val,
         fld117         like zscr_defect_data-defect_val,
         fld118         like zscr_defect_data-defect_val,
         fld119         like zscr_defect_data-defect_val,
         fld120         like zscr_defect_data-defect_val,
         fld121         like zscr_defect_data-defect_val,
         fld122         like zscr_defect_data-defect_val,
         fld123         like zscr_defect_data-defect_val,
         fld124         like zscr_defect_data-defect_val,
         fld125         like zscr_defect_data-defect_val,
         fld126         like zscr_defect_data-defect_val,
         fld127         like zscr_defect_data-defect_val,
         fld128         like zscr_defect_data-defect_val,
         fld129         like zscr_defect_data-defect_val,
         fld130         like zscr_defect_data-defect_val,
         fld131         like zscr_defect_data-defect_val,
         fld132         like zscr_defect_data-defect_val,
         fld133         like zscr_defect_data-defect_val,
         fld134         like zscr_defect_data-defect_val,
         fld135         like zscr_defect_data-defect_val,
         dayst         like zscr_data_hdr-dayst,
       end of t_data.
In this fld1 to fld135 are defined in internal table.
But if the number of fields are more than 135 then the program is going to short dump.
Some times fld1 to fid170 or more fields will be there in my internal table.
Please suggest me how to make my requirement dynamic and display this data fetched into this internal table onto a .XLS file in the presentation server ?

Hi
You can try to use the type string:
form like zscr_data_hdr-form,
werks like zscr_data_hdr-werks,
matnr like zscr_data_hdr-matnr,
verid like zscr_data_hdr-verid,
lot like zscr_data_hdr-lot,
lot_qty like zscr_data_hdr-lot_qty,
udate like zscr_data_hdr-udate,
utime like zscr_data_hdr-utime,
zuser like zscr_data_hdr-zuser,
processed like zscr_data_hdr-processed,
defect like zscr_defect_data-defect,
vornr like zscr_route_data-vornr,
fieldxx type string,
dayst like zscr_data_hdr-dayst,
end of t_data.
So you can save you informations of every fld<n> concatenating their values into fieldxx.
Max

How to increase the database size

Hi All ,
Our Client is going to increase their customers from 3.5 million to 5 millions
(12 millions in future ) and there is no increase in the existing licenses..
At present we have very less space in Data base server. We are Going Live at the End of the Month.
How to increase the database size to meet the Client requirements.
we have to increase the No of Processerors etc...
Below are the details of Servers:
System Model: IBM,7040-681
Machine Serial Number: 830D5BF
Processor Type: PowerPC_POWER4
Number Of Processors: 2
Processor Clock Speed: 1904 MHz
CPU Type: 64-bit
Kernel Type: 64-bit
LPAR Info: 4 bgl-svr-biap
Memory Size: 4096 MB
Good Memory Size: 4096 MB
Note : Server is IBM P690.
1) System Lansdcape --> Two System Landsacpe ( Dev to Prod )
2) BW Version --> 3.5
3) SAP Basis --- > 6.4
4) No of Application servers currently having --> Only One Server
Can any body suggest me how to solve this.....
Thanks in Advance..
Kasi Chukka

Hi Kasi,
Your question is not very clear, from the looks of it, the load on your client's system will be doubling soon.
You need to look at the system stats on how the system is handling the current load, use transactions ST06, ST04 and ST02 to check if the DB hit ratios are as expected, the cpu idle time, the busy periods. Identify if there is large amounts of paging on the server(candidate for increase in real memory).
On AIX level, you will need to look at CPU / Memory usage.
On SAP Application server, you need to look at SAP Buffers.
On Oracle end, look at SGA stats, if it need to increase, the data growth that is current and estimated growth (DB02).
You will not get an exact answer to it, you will need to analyze the existing load and then estimate (guess). The hardware upgrade will also depend on what the client is willing to spend, its always a good practise to add 20% to what you have estimated as these figures are never accurate.
All the best.
Cheers,
Nisch

How to increase the number of rows to be displayed in BEx Web Analyzer

hi,
I am viewing reports using BEx Web analyzer option. It is displaying only 24 rows of data at a time. How to increase the number of rows? do i need to any kind of settings?
pls reply.

Hi,
I think the standard template in 2004s is named 0ANALYSIS_PATTERN. You can find it in Web Application Designer, open, and search for the technical name. If you want to change the number of rows or columns, you can find this setting near the bottom of the XHTML view of the template:
<bi:BLOCK_COLUMNS_SIZE value="4" />
<bi:BLOCK_ROWS_SIZE value="17" />
Then just save, and ignore the error messages.
Message was edited by:
vind Reinsberg

How to increase the battery life of your N series ...

What I am about to post here is valid for any 3G phone or device regardless of model but it is particularly focused towards the N series devices and their power hogging features.
Your battery life is dependant on many many things. How often you take calls on the device, the condition of your battery, the features you use on the device and so on and on. Therefore it is impossible to say that by following the information in this post you will get x amount of days battery life, but it will get you more time out of the battery than you otherwise would have got.
So with that out the way, if your looking to increase your battery life then follow these tips and your battery should start looking a lot healthier.
First of all lets start with THE big one. The one that is going to save you the most juice. Switching 3G off.
Yep, you heard me right. Just by switching the 3G capability of your phone off you will add hours and hours to your battery life. How is this so? Allow me to explain...
Due to the rather poor delivery of 3G in the UK by the network operators, it is rare for any 3G phone to maintain a constant 3G signal. Instead you will find that the phone constantly flips between 3G and GSM mode (Keep an eye on your signal one day). Even those of you on Vodafone who probably have the best 3G network coverage will find this is the case.
Unfortunately, this constant flipping between the two modes sucks power from the battery like a vampire as it alters its reception state for the different modes and the constant flipping is..well...causing it do this constantly! It can sometimes even make your phone unavailable for calls for very brief periods as it trips from GSM to 3G and vice versa.
If you need to use 3G for video calls or whatever then I'm afraid your just going to have to live with this but if you don't (And lets face it few of us do) then you can switch 3G off and increase your battery life considerably.
To do this, go into the "Settings" application (Found in the menu somewhere, by default Nokia normally stick it in "Tools"), and then to the "Phone" tab. In there you will see an option that says "Network mode" and you have a choice of "GSM" or "Dual Mode" (I.e. UMTS and GSM). Set it to GSM and your phone will restart. Once it restarts it will be working in GSM with GPRS speeds only but really for most purposes this is fine.
You have now just extended your battery capability considerably. You can further extend it by going to the "Connection" tab, going into "Packet data" and changing it to "When needed" so it is not constantly checking for a data connection.
The second big change you can make is to turn your phones wifi scanning capability off. The last time I looked not all Nokia's phones that have wifi capability can have their wifi cards switched off entirely but if you can, turn it off except for when you need to use it. Wifi is a power hog.
The next big change you can make is to lower the screen brightness settings on your phone. The less bright your screen is the less power is being used to light it up. Nokia by default leave the screen brightness at something like 50%. Lowering this a bit more will conserve more juice. Before you do this though please consider the fact that lowering the brightness setting will have a big impact on your ability to see the screen clearly in sunny conditions although you will be fine in the dark as you can't lower the brightness that far.
To lower the brightness, go to the settings tool in your phone and into the display option (Hidden in a subcategory called "Personalisation" on the N95). It won't hurt to set the power saving time out to 1 minute and the backlight time out to 10 seconds while your here (Although these are the Nokia default so they should already be set to this).
Finally in regards to the screen, although they may look pretty, animated screensavers use more battery power than the standard blank screen with time and date so avoid them if you can.
It also helps to keep Bluetooth switched off until you need it although the power savings are minimal in comparison to the other changes but every little milliamp counts!
Using the above methods I generally get about 3 to 4 days with about 3 hours talktime on my N95 without using Bluetooth, GPS or anything like that (I might be able to get more but so far I have not paid attention to the battery state before I put it on charge). If I am on a long train journey I can get about 4 hours worth of full screen video and about 2 hours talktime over the period of about 24 hours before it needs a recharge. As I said at the start of the post your mileage will vary greatly depending on how you use your device.
Hope this helps.
Useful links: Phone firmware update | Nokia support site

02-May-200701:14 PM
bixby wrote:
no keffa it is a cop out from nokia
its not unfai as its a premium device with a premium price
the n95 battery is atrocious
dont change the post content as the title is 'How to increase the battery life of your N series device'
your talking about nokia phones specifically
the networks are not to blame
they do not make the handsets : Nokia do !!!!!!!!!!
I'm going to choose my words carefully here...
I would never deny the battery on the N95 is not really up to the job of powering the N95 with its power hungry features. To put the same battery into a phone that has WiFi, GPS and a large 320x240 screen, the same one that goes into the E65 which has comparatively nothing compared to it is a bit pants.
However at no point was I criticising them for the band hopping problem. I labelled the post as how to increase the battery life of your N series device because this is a board for the N series devices. It was a simple choice of wording and not intended to be cutting in any way and I did make a remark that the details would be true of any 3G device at the top of the post.
What I was trying to point out in my second post is that the constant band hopping the phone is being forced to do that is draining its battery so much more quicker than it would if it had a constant signal of one kind or another isn't quite Nokia's fault.
They build it to conform to a laid out specification for 3G. However if the network operators cannot be bothered to roll out their 3G infrastructure adequately enough that the phone can find and remain locked onto a 3G signal that is usable then what are Nokia to do other than offer you the capability to turn 3G off until you need it (Although note to Nokia: That **bleep** reboot the phone does when you do this is entirely unneeded and you know it).
Blaming Nokia for this would be like blaming the manufacturer of your radio for failing to pick up radio because the radio station does not have any transmitters within range of your radio's receiver.
Finally...this band hopping is exhibited by all 3G phones built by Samsung, Nokia, Sony Ericsson, etc, from their most budget 3G model to their priciest piece and is the reason that all phones with 3G capabilities have batteries that do not last for any respectable length of time because these phones are also having to band hop between 3G and GSM.
Finally the proof is in the pudding. Turn 3G off for a few days. See your battery improve. Then (Although admittedly this will be harder to do...mcuh harder) find an area where you get a fairly decent 3G signal constantly. Again, see your battery improve. Try it with a different 3G phone...different manufacturer even. The same will be true.
So I stand by my comment, the network operators and their woeful 3G rollout are the villains costing you a fair chunk of your battery and Nokia cannot be expected to mitigate this....but a better battery would be nice all the same...
Useful links: Phone firmware update | Nokia support site

How to increase the speed of video (avi file) using labview

How to increase the speed of video (.avi file) using labview? I have tried this by skiping alternate frames. also I have used minimum time delay.Is there any other option for which i can go?
please suggest me...........

Are you using NI Vision IMAQ AVI Read Frame or anther method to read the AVI file?
Matthew Fitzsimons
Certified LabVIEW Architect
LabVIEW 6.1 ... 2013, LVOOP, GOOP, TestStand, DAQ, and Vison

How to increase the performance in server 2008 R2 for RDP users

Hi,
My application take to much time to load. If anyone double click on mail client the exe file will appear in task manager but it will open after 5 mins. how to increase the performance.
My sever configuration is as below,
SC2600 Intel motherboard with total 24 core processors and 32 GB RAM and 8 TB Hard Disk. RAID 5 is configured which has two lungs one is 167 GB for C drive and other is 4.5 TB for D drive.
There are 28 Thin-clients connected to server through L300 N computing Thin-clients.
Thin-clients connect to V-space server installed in server for RDP users to get connected.
we have installed around 20 applications including printer and scanner driver. And apps are has below,
Firefox browser, windows mail, Adobe acrobat XI, canon printer and scanner drivers, Epson printer and scanner driver, E scan anti-virus, office 2007, v space, power ISO, win-rar,Tally and e token drivers and some backup software's.
Below are the services and features enabled,
AD, File services, RDP, web server, Hyper-v, .net frame work.
Is there a way to increase the performance .
Very slow performance.

Hi,
what would you suggest on hardware configuration must be for above mentioned applications and services with those many users.
how many cores and ram size is required.

How to Increase the Length of Condition table in OV20

While creating a condition table in T.code OV20 if fields length is more that 50 bytes table is not getting generated.it gives error as Too Many Fields Selected(More than 50 Bytes).
Actually i need to create a tabel with Basic Material(WRKST) which has length of 48 bytes.
Is there a solution on how to increase the length so that error is avoided.
There is no such error occuring while crating condition table in V/03

Hi,
You can try to use the type string:
form like zscr_data_hdr-form,
werks like zscr_data_hdr-werks,
matnr like zscr_data_hdr-matnr,
verid like zscr_data_hdr-verid,
lot like zscr_data_hdr-lot,
lot_qty like zscr_data_hdr-lot_qty,
udate like zscr_data_hdr-udate,
utime like zscr_data_hdr-utime,
zuser like zscr_data_hdr-zuser,
processed like zscr_data_hdr-processed,
defect like zscr_defect_data-defect,
vornr like zscr_route_data-vornr,
fieldxx type string,
dayst like zscr_data_hdr-dayst,
end of t_data.
So you can save you informations of every fld<n> concatenating their values into fieldxx.
Regards

How to increase the limit of maximim connections that the iMS will accept

how to increase the limit of maximim smtp connections that the iMS will accept & route the mails for specific domain on different mta like iMS will accpet mails on 192.168.1.5|25 & route all @mydomain.com's mails towards 192.168.1.55|25. although I am able to route the mails but to know how to increase the limit of maximum connection & maximum chiild processes per connection.
Thanks

Best thing for you to do is read the tuning guide, found here:
http://ims.balius.com/downloads.php#tuning_guide
Please note, this site does not work with IE. It's not a Sun site, but has the best tuning guide available.
You may end up increasing maxjobs for your channels, increasing the POOL that the jobs are pulled from, etc. It's all well covered in the guide, as are some OS related tuning tips.
Strongly recommended.

How to increase the size of sort_area_size

How to increase the size of sort_area_size and what size should be according to the PROD database
Thanks

user10869960 wrote:
Hi,
Many Thanks Charles
Oracle does not recommend using the SORT_AREA_SIZE parameter unless the instance is configured with the shared server option. Oracle recommends that you enable automatic sizing of SQL working areas by setting PGA_AGGREGATE_TARGET instead. SORT_AREA_SIZE is retained for backward compatibility."
--How can i know the instance is configured with the shared server option or not?This might be a tough question to answer. A shared server configuration may be enabled, but the clients may still connect using dedicated sessions, in which case PGA_AGGREGATE_TARGET would still apply.
From
http://download.oracle.com/docs/cd/B19306_01/server.102/b14237/dynviews_2088.htm
V$SESSION includes a column named SERVER which will contain one of the following for each of the sessions: DEDICATED, SHARED, PSEUDO, or NONE. As a quick check, you could query V$SESSION to see if any sessions are connected using a shared server connection.
From:
http://download.oracle.com/docs/cd/B19306_01/server.102/b14231/manproc.htm
There are several parameters which are used to configure shared server support, as well as several views to monitor shared server.
As Robert mentioned, when the WORKAREA_SIZE_POLICY is set to AUTO, the SORT_AREA_SIZE setting is not used, unless a shared server configuration is in use.
--What default value is WORKAREA_SIZE_POLICY and SORT_AREA_SIZE ?From:
http://download.oracle.com/docs/cd/B19306_01/server.102/b14237/initparams157.htm
"Setting PGA_AGGREGATE_TARGET to a nonzero value has the effect of automatically setting the WORKAREA_SIZE_POLICY parameter to AUTO. This means that SQL working areas used by memory-intensive SQL operators (such as sort, group-by, hash-join, bitmap merge, and bitmap create) will be automatically sized. A nonzero value for this parameter is the default since, unless you specify otherwise, Oracle sets it to 20% of the SGA or 10 MB, whichever is greater."
Actually I am facing performence issue since long time till now i did not get the solution even i have raised SRs but i could not.When the issue occur system seems hang.what i monitored whenever hdisk0 and hdisk1 use 100% the issue occur.
Regards,
SajidWhen you say that you have had a performance issue for a long time, is it a performance problem faced by a single SQL statement, a single user, a single application, or everything on the server? If you are able to identify a single user, or SQL statement that is experiencing poor performance, I suggest starting with a 10046 trace at level 8 (wait events) or level 12 (wait events and bind variables) to determine why the execution appears to be slow. If you have not yet determined a specific user or SQL statement that is experiencing performance problems, you might start with either a Statspack Report or an AWR Report (AWR requires a separate license).
If you believe that temp tablespace usage may be a contributing factor to the performance problem, you may want to periodically run this query, which will indicate currently in use temp tablespace usage:
{code}
SELECT /*+ ORDERED */
TU.USERNAME,
S.SID,
S.SERIAL#,
S.SQL_ID,
S.SQL_ADDRESS,
TU.SEGTYPE,
TU.EXTENTS,
TU.BLOCKS,
SQL.SQL_TEXT
FROM
V$TEMPSEG_USAGE TU,
V$SESSION S,
V$SQL SQL
WHERE
TU.SESSION_ADDR=S.SADDR
AND TU.SESSION_NUM=S.SERIAL#
AND S.SQL_ID=SQL.SQL_ID
AND S.SQL_ADDRESS=SQL.ADDRESS;
{code}
The SID and SERIAL# returned by the above could then be used to enable a 10046 trace for a session. The SQL_ID (and CHILD_NUMBER from V$SESSION in recent releases) could be used with DBMS_XPLAN.DISPLAY_CURSOR to return the execution plan for the SQL statement.
You could also take a look in V$SQL_WORKAREA_ACTIVE to determine which, if any, SQL statement are resulting in single-pass, or multi-pass executions, which both access the temp tablespace.
Charles Hooper
IT Manager/Oracle DBA
K&M Machine-Fabricating, Inc.

How to increase the buffer size ?

Our BI system displays the following message when I execute a query on the web : buffer too small
How to increase the buffer size ?
Thanks in advance

Indeed, we are using Bex Web 7.0
The query uses a big structure and when I execute it on the web, it takes a long time (> 5 min) and I receive folowing message on top of the result page : " could not buffer query structures. Buffer too small "
When I execute the query in Bex analyzer, it takes a long time too but we dont get the message
I have checked the cache size:
- Local cache : 100 MB
- Global cache : 200 MB
Please let me know any solution as there is no BASIS TEAM. The guy who installed the soft was a consultant and is no more reachable.
Thanks in adavnce

How to increase the font size of print ouput in SAP 4.7

Hi,
How to increase the font size of the ouput of Write statement on PRINT ? in 4.7
THANKS IN ADVANCE
MOOSA

You can do that using the PRINT-CONTROL Statement.This will only work when you send the list to the printer.Sample code is as below :
REPORT zfont NO STANDARD PAGE HEADING LINE-SIZE 80 LINE-COUNT 65.
Start of print-control
NEW-PAGE PRINT ON.
PRINT-CONTROL FUNCTION 'SF000'.
WRITE: / 'This is CPI 20'.
SKIP.
PRINT-CONTROL FUNCTION 'SF020'.
WRITE: / 'This is CPI 6'.
SKIP.
PRINT-CONTROL FUNCTION 'SF008'.
WRITE: / 'This is CPI 12'.
Depending on your SAP printer device, this may also work
PRINT-CONTROL FONT 1 LPI 6.
you can try to change font and LPI numbers
WRITE: / 'font 1 lpi 6'.
PRINT-CONTROL FONT 2 LPI 6.
WRITE: / 'font 2 lpi 6'.
PRINT-CONTROL FONT 3 LPI 6.
WRITE: / 'font 3 lpi 6'.
End of print-control
NEW-PAGE PRINT OFF.
*--- End of Program

How to increase the time at the end of what aaa requeries the authentication of a client web

Similar Messages

Maybe you are looking for