PGA Limits for 11.1.0.7 on AIX 6.1
With an 11gR1 Database running under AIX I have the Impression, that requests for pga memory get an ORA-04030 too early. In the following statements there is a skript, that consumes more an more pga memory. It always stops when ~ 113MB of pga are consumed, but there should be posssible much more in my opinion. I shut down other database instances on the same server, I increased ulimit for rss and stack but the result is always the same. After the skript the 'session pga memory max' for my SID is 113MB.
Why is more pga cosumption not possible?
select name, to_number(value)/1024 KB
from v$parameter
where name like 'pga%'
or name like 'memory%'
or name like 'sga%';
NAME KB
sga_max_size 3,670,016
sga_target 3,670,016
memory_target 4,620,288
memory_max_target 6,291,456
pga_aggregate_target 950,272
create table temp_pga as
select * from v$pgastat;
select n.name, sum(t.value)/1024 KB
from v$sesstat t,
v$statname n
where n.statistic# = t.statistic#
and n.name in ('session pga memory', 'session pga memory max', 'session uga memory', 'session uga memory max')
group by n.name
order by 1;
NAME KB
session pga memory 65,484
session pga memory max 160,590
session uga memory 25,379
session uga memory max 68,069
select
s.sid,
n.name,
sum(t.value/1024) KB
from
v$statname n,
v$session s,
v$sesstat t
where
s.sid=t.sid
and n.statistic# = t.statistic#
and s.audsid = SYS_CONTEXT('userenv','sessionid')
and n.name in ('session pga memory', 'session pga memory max', 'session uga memory', 'session uga memory max')
group by
s.sid, n.name
order by 2;
SID NAME KB
94 session pga memory 1,832
94 session pga memory max 2,536
94 session uga memory 616
94 session uga memory max 1,240
declare
type array is table of long index by binary_integer;
l_data array;
begin
loop
l_data(l_data.count+1) := rpad('*',32000,'*');
end loop;
end;
FEHLER in Zeile 1:
ORA-04030: Zu wenig Prozessspeicher für Versuch 32712 Bytes zuzuweisen (koh-kghu call ,pl/sql vc2)
select n.name, sum(t.value)/1024 KB
from v$sesstat t,
v$statname n
where n.statistic# = t.statistic#
and n.name in ('session pga memory', 'session pga memory max', 'session uga memory', 'session uga memory max')
group by n.name
order by 1;
NAME KB
session pga memory 77,988
session pga memory max 291,431
session uga memory 32,088
session uga memory max 77,023
select
s.sid,
n.name,
sum(t.value/1024) KB
from
v$statname n,
v$session s,
v$sesstat t
where
s.sid=t.sid
and n.statistic# = t.statistic#
and s.audsid = SYS_CONTEXT('userenv','sessionid')
and n.name in ('session pga memory', 'session pga memory max', 'session uga memory', 'session uga memory max')
group by
s.sid, n.name
order by 2;
SID NAME KB
94 session pga memory 1,384
94 session pga memory max 113,832
94 session uga memory 616
94 session uga memory max 1,240
select n.name, v.value before, n.value after, n.unit
from
v$pgastat n,
temp_pga v
where n.name = v.name
order by n.unit, n.name;
NAME BEFORE AFTER UNIT
aggregate PGA auto target 819,505,152 715,511,808 bytes
aggregate PGA target parameter 973,078,528 973,078,528 bytes
bytes processed 21,978,394,624 22,010,895,360 bytes
extra bytes read/written 1,066,005,504 1,066,005,504 bytes
global memory bound 104,857,600 104,857,600 bytes
maximum PGA allocated 454,460,416 454,460,416 bytes
maximum PGA used for auto workareas 106,148,864 106,148,864 bytes
maximum PGA used for manual workareas 0 0 bytes
PGA memory freed back to OS 9,104,392,192 9,222,684,672 bytes
total freeable PGA memory 48,103,424 52,101,120 bytes
total PGA allocated 143,251,456 164,831,232 bytes
total PGA inuse 64,303,104 77,556,736 bytes
total PGA used for auto workareas 1,277,952 1,529,856 bytes
total PGA used for manual workareas 0 0 bytes
cache hit percentage 95 95 percent
max processes count 82 82
over allocation count 0 0
process count 49 63
recompute count (total) 5,239 5,240
I found my problem. After changing the ulimit parameters for the oracle user I didn't restart the listener, only the database.
As new client connections inherit their limits from the listener process the old values were still valid.
Similar Messages
-
Memory limitation for session object!
what is the memory limitation for using session objects?
venuas already mentioned there is no actual memory limitation within the specification, it only depends on the jvm's settings
how different app-server handle memory management of session objects is another part of the puzzle, but in general you should not have problems in writting any object to the session.
we had the requirement once to keep big objects in session, we decided to do a ResourceFactory that returns us the objects, and only store unique-Ids into the session.
We could lateron build on this and perform special serialization tasks of big objects in the distributed environment.
Dietmar -
Limitation for CLOB columns? - ORA-01704: string literal too long
Hello!
I'm trying to update a CLOB column with more than 35000 characteres, but I get "ORA-01704: string literal too long".
The code:
declare
l_clob clob;
begin
update test set test = empty_clob()
WHERE ID = 1
returning test into l_clob;
dbms_lob.write( l_clob, length('A...here 35000xA...A'), 1,'A...here 35000xA...A');
end;
Is there any limitation for CLOB columns?
Thanks for help.
Danieluser605489 wrote:
32768 characteres :)Actually it's 1 character less than 32K...
*32767*
SQL> declare
2 v_vc varchar2(32768);
3 begin
4 null;
5 end;
6 /
v_vc varchar2(32768);
ERROR at line 2:
ORA-06550: line 2, column 17:
PLS-00215: String length constraints must be in range (1 .. 32767)
SQL>I guess it comes from a legacy thing where signed words (2 bytes) are/were used to represent a value. As the most significant bit of the word is used to represent the sign of the number the range goes from -32768 to 32767. -
Hi all,
Is there any possibility to maintain tolerance limits for Quantity in Quantity Contract (doc type MK),,,
ex: Quantity Contract (MK) -- target quantity = 100
it should allow me to create release orders (Purchase orders) for 105 quantity(tolerance of +5%)
regards
urendraHi,
By using Purchasing Value Key in Material Master you can control over and under deliveries.But its applicable to that material.
If Purchasing Info Record exists for that material then tolerance limit which is given in inforecord takes priority.
Regards,
Ramesh
Message was edited by:
Ramesh -
Tolerance limits for Price Variation
Dear All,
I have set the Following in Customizing.
In the following node : IMG-------> Materials Management ----------> Purchasing -----------> Purchase Order ---------> Set tolerance limits for price Variance.
In this, For Company code & Tolerance Key "PE" combination, it has been set " Check Limit 20%" in the Percentage field ( Upper limit ).
Now, I have a material having a Moving Average price of 100 INR in the material master Accounting view. When I create a PO for 130 INR, there is no warning/error message that is popping up? Isn't the system supposed to throw a message here, since 130 inr exceeds 120 INR, or am I missing something out here ?
Note : 120 INR = 100 + (20%)(100) = 120 INR.
Regards
SathyaHi Sathyanarayana Rao V N
You can benefit from M8 messages for incoming invoices with tolerances to solve your problem. You have to configure your system messages with error.
Regards.
M.Ozgur Unal -
Tolerance limits for PO,MIGO..etc..?
Dear all
Can anybody explain me about the tolerance limits in SAP-MM,
1.what is tolerance limits..?
2.Why tolerance limits need in SAP-MM..?
3.How to configure in SPRO
Which are all the area has to maintain Tolerance limits according to MM point of view
Advance thanks
goods answers will be highly rewardable.
Thanks
sap-mmHi
tolerance limits for price variancesin Purchase order
When processing a purchase order, the system checks whether the effective price of a PO item shows variances compared with the valuation price stored in the material master record. In addition, it checks whether the specified cash discount value is admissible.
Variances are allowed within the framework of tolerance limits. If a variance exceeds a tolerance limit, the system issues a warning or error message.
In the SAP System, the types of variance are represented by the tolerance keys. For each tolerance key, you can define percentage and value-dependent upper and lower limits per company code.
Standard settings
The standard SAP System supplied contains the following tolerance keys:
PE Price variance, Purchasing
Tolerance limit for system message no. 207. This message appears if the specified effective price exceeds the predefined tolerances when compared with the material price.
SE Maximum cash discount deduction, Purchasing
Tolerance limit for system message no. 231. This is a warning message, which appears when the specified cash discount percentage exceeds the predefined tolerances.
Note
You can specify whether the system message appears as a warning or error message using the menu options Environment -> Define Attributes of System Messages.
For Invoices specify the tolerance limits for each tolerance key for each company code.
When processing an invoice, the R/3 System checks each item for variances between the invoice and the purchase order or goods receipt. The different types of variances are defined in tolerance keys.
The system uses the following tolerance keys to check for variances:
AN: Amount for item without order reference
If you activate the item amount check, the system checks every line item in an invoice with no order reference against the absolute upper limit defined.
AP: Amount for item with order reference
If you activate the item amount check, the system checks specific line items in an invoice with order reference against the absolute upper limit defined. Which invoice items are checked depends on how you configure the item amount check.
BD: Form small differences automatically
The system checks the balance of the invoice against the absolute upper limit defined. If the upper limit is not exceeded, the system automatically creates a posting line called Expense/Income from Small Differences, making the balance zero and allowing the system to post the document.
BR: Percentage OPUn variance (IR before GR)
The system calculates the percentage variance between the following ratios: quantity invoiced in order price quantity units : quantity invoiced in order units and quantity ordered in order price quantity units : quantity ordered in order units. The system compares the variance with the upper and lower percentage tolerance limits.
BW: Percentage OPUn variance (GR before IR)
The system calculates the percentage variance between the following ratios: quantity invoiced in order price quantity units: quantity invoiced in order units and goods receipt quantity in order price quantity units : goods receipt quantity in order units. The system compares the variance with the upper and lower percentage limits defined.
DQ: Exceed amount: quantity variance
If a goods receipt has been defined for an order item and a goods receipt has already been posted, the system multiplies the net order price by (quantity invoiced - (total quantity delivered - total quantity invoiced)).
If no goods receipt has been defined, the system multiplies the net order price by (quantity invoiced - (quantity ordered - total quantity invoiced)).
The system compares the outcome with the absolute upper and lower limits defined.
This allows relatively high quantity variances for invoice items for small amounts, but only small quantity variances for invoice items for larger amounts.
You can also configure percentage limits for the quantity variance check. In this case, the system calculates the percentage variance from the expected quantity, irrespective of the order price, and compares the outcome with the percentage limits configured.
The system also carries out a quantity variance check for planned delivery costs.
DW: Quantity variance when GR quantity = zero
If a goods receipt is defined for an order item but none has as yet been posted, the system multiplies the net order price by (quantity invoiced + total quantity invoiced so far).
The system then compares the outcome with the absolute upper tolerance limit defined.
If you have not maintained tolerance key DW for your company code, the system blocks an invoice for which no goods receipt has been posted yet. If you want to prevent this block, then set the tolerance limits for your company code for tolerance key DW to Do not check.
KW: Variance from condition value
The system calculates the amount by which each delivery costs item varies from the product of quantity invoiced * planned delivery costs/ planned quantity. It compares the variance with the upper and lower limits defined (absolute limits and percentage limits).
LA: Amount of blanket purchase order
The system calculates the sum of the value invoiced so far for the order item and the value of the current invoice and compares it with the value limit of the purchase order. It then compares the difference with the upper percentage and absolute tolerances defined.
LD: Blanket purchase order time limit exceeded
The system determines the number of days by which the invoice is outside the planned time interval. If the posting date of the invoice is before the validity period, the system calculates the number of days between the posting date and the start of the validity period. If the posting date of the invoice is after the validity period, the system calculates the number of days between the posting date and the end of the validity period. The system compares the number of days with the with the absolute upper limit defined.
PP: Price variance
The system determines by how much each invoice item varies from the product of quantity invoiced * order price. It then compares the variance with the upper and lower limits defined (absolute limits and percentage limits).
When posting a subsequent debit/credit, the system first checks if a price check has been defined for subsequent debits/credits. If so, the system calculates the difference between (value of subsequent debit/credit + value invoiced so far) / quantity invoiced so far * quantity to be debited/credited and the product of the quantity to be debited/credited * order price and compares this with the upper and lower tolerance limits (absolute limits and percentage limits).
PS: Price variance: estimated price
If the price in an order item is marked as an estimated price, for this item, the system calculates the difference between the invoice value and the product of quantity invoiced * order price and compares the variance with the upper and lower tolerance limits defined (absolute limits and percentage limits).
When posting a subsequent debit/credit, the system first checks whether a price check has been defined for subsequent debits/credits, If so, the system calculates the difference between (value of subsequent debit/credit + value invoiced so far) / quantity invoiced so far * quantity to be debited/credited and the product quantity to be debited/credited * order price. It then compares the variance with the upper and lower tolerance limits defined (absolute limits and percentage limits).
ST: Date variance (value x days)
The system calculates for each item the product of amount * (scheduled delivery date - date invoice entered) and compares this product with the absolute upper limit defined. This allows relatively high schedule variances for invoice items for small amounts, but only small schedule variances for invoice items for large amounts.
VP: Moving average price variance
When a stock posting line is created as a result of an invoice item, the system calculates the new moving average price that results from the posting. It compares the percentage variance of the new moving average price to the old price using the percentage tolerance limits defined.
Variances are allowed within predefined tolerance limits. If a variance exceeds a tolerance limit, however, the system issues a message informing the user. If an upper limit (except with BD and VP) is exceeded, the invoice is blocked for payment when you post it. You must then release the invoice in a separate step. If the tolerance limit for BD is breached, the system cannot post the invoice.
Note that if you set all limits for a tolerance key to Do not check, the system does not check that tolerance limit. Therefore any variance would be accepted. This does not make sense particularly in the case of the tolerance key Form small differences automatically.
Thanks & Regards
Kishore -
Tolerance Limits for Date and quantity..??
Hi Experts,
We would like to set the GR Tolerance Limits in the Configuration level.
how to set the Tolerance Limits for Date and quantity..??
if we created PO 100qty and date 01-05-009.
if we receive the goods on 20-04-2009 and 50qty...
For GR .. Migo should be give error message..
where can i set this Tolerance Limit Configuration.... can u please explin me..
Thanks in Advance,
Anthyodaya.Hai
for quantity tolerence limit u can do it while creating P O in item details-->delivery tab.
for date go to SPRO-->mm>purchasing->material master> define purchase value key>in that st.del.time var here it wil compare the dates and shows how much deviation is occuring for GR date
configure messages in SPRO-->mm>environment data--> define attributes of system messages
hope it may help u
regards
chandrasekhar -
Maintain Tolerance limits for tolerance key B1
Hi,
When We tried to reverse a 'reversal' document using MBST but the system does not let me a throws up the following message no. M8125...
"maintaintolerance limits for tolerance key B1 (CoCode 5000)".
I checked configuration in OMc0, we have lower limit 10 % anf Higher limit 10% and BOTH 'check limit'.
Still I donot where is the problem?
Can somebody throw smoe light on this issue? Please....Any Help?
-
Maintain tolerance limits for tolerance key PE (CoCode S001)
Dear all
im getting error when i creating PO
Maintain tolerance limits for tolerance key PE (CoCode S001)
Please help me
Regards
venu gopalHi
You need to maintain the Tolerance key
PE Price variance, Purchasing
Tolerance limit for system message no. 207. This message appears if the specified effective price exceeds the predefined tolerances when compared with the material price.
Maintain the tolearnce key in
SPRO-> IMG-> Materials Management-> Purchasing-> Purchase Order-> Set Tolerance Limits for Price Variance
If you want the sytem to propmt for a warning or Error message you can configure the same in
SPRO-> IMG-> Materials Management-> Purchasing-> Environment Data-> Define Attributes of System Messages -
Maintain tolerance limits for tolerance key PE
Hi,
How can I correct the error below?
"Maintain tolerance limits for tolerance key PE"
ThanksREFER BELOW SDN POST
Re: TOLERANCE KEY ERROR DURING MIGO
MAINTAIN TOLERANCE LIMITS FOR TOLERANCE KEY PE ACCOUNT ASSIGNMENT -
> Please follow this link --> SPRO -> MM-> Purchasing --> Purchase Order --> Set Tolerance limits for price variance --> Here you have to set for Tolerance keys PE and SE. Just copy them from std co. code.
Message was edited by:
SHESAGIRI.G -
As of yesterday, calendar subscribers are no longer getting event alerts. We are not exceeding the limits for number of calendars, and have not installed new hardware or software. What else could be causing this, and how do I fix it? This is critical!
The warranty entitles you to complimentary phone support for the first 90 days of ownership.
-
What are Azure limitations for Websockets in Cloud Services (web and worker role)?
A WebSocket Server should be built on Azure platform with OnPrem connections and have questions regarding limitations for Websockets in Azure Cloud Services - web and worker roles.
Websockets can be configured for Web Sites and limitations are understood, but Azure Websites is not an option.
Nevertheless it is planned to run a web service (without UI - no web site) as a Cloud service which has secure websocket (WSS) connections to OnPrem machines. Websocket protocol is enabled for IIS8 on Cloud services web and worker roles. Azure Service Bus Relay
is not an option.
Questions:
1) Are Websockets supported for Azure Cloud services web and worker roles? we assume yes
2) What are potential limitations from Azure side to support concurrent Websocket connections? We are aware that CPU, memory etc are limitations, but are there additional limitations from MS Azure side?
Hi,
As I know, azure cloud service web and worker role support Websockets, users can connect to the role via the special endpoint, if we use Azure cloud service, I think we can monitor the metrics such as CPU, memory, etc... and scale our cloud service via these
metrics to keep the websockets working, refer to
http://azure.microsoft.com/en-us/documentation/articles/cloud-services-how-to-scale/ for more information about how to scale a cloud service.
Regards -
Increasing Email Size Limits for some users
Hi All,
For some users (management) i needed to arrange that they are able to send bigger files then the default 10MB limit to each other.
I used this procedure to do so,
https://www.simple-talk.com/sysadmin/exchange/increasing-email-size-limits-for-your-high-profile-users-in-exchange-2010/
In a nutshell:
Set Global Transport Org. Config to 200MB
Set Transport Send and Receive connector to 200MB
Created a Distribution group adding the MT members and me (for testing)
Created a transport Rule for the 10MB limit for all users and exception for the distribution group
(Believe me, i am not happy with the 200MB size limit)
All seems to work but i have one issue that i cannot tackel or maybe it is by design.
-Managemant can also send big files to all
users who do not have this privelige, this is not someting i want, sending 100MB+ attachments to over 150 users.
Is this by design or do i mis something?
Thanks,
RonHi RonGielgens,
Attachment size in exchange has to be set on
Global settings
Connectors (send and receive connectors)
Mailbox
The global settings will affect all the others. of course connectors will affect specific servers and mailbox one user. You have to set the global to the absolute max size you want to allow in your organization.
after you do this you will need either to set the 10MB on each mailbox
Get-Mailbox | Set-Mailbox -MaxSendSize 10MB -MaxReceiveSize 10MB
Then change the limit on specific mailbox
or another way is to create a transport rule that will reject the email if the attachment size it > 10MB unless the sender/recipient is the required user or group.
so basically create 2 transport rules
1. reject messages sent to anyone with attachment > 10mb unless the recipient is userX
2. reject messages sent from anyone with attachment > 10mb unless the sender is userX
Normal case it should not allow.
Thanks, MAS
Please mark as helpful if you find my comment helpful or as an answer if it does answer your question. That will encourage me - and others - to take time out to help you. -
Export Limits for Multiple Sequences in the Same Sequence File for TS3.0
Hi,
I am using TestStand 3.0 to a test application. Because we want to have our limits in a csv-file I have tried to use the Import/Export tools in TS. But this application only supports to export limits for the selected sequence (e.g. main, or subseq1) at a time. This makes it a pretty hard job to export limits from 30 test sequences. What I need is a possibility to export my limits from �all sequences� in my seq-file.
I have found an article on NI Dev. Zone about �Export Limits for Multiple Sequences in the Same Sequence File (TestStand 1.0.x)�.
http://sine.ni.com/apps/we/niepd_web_display.DISPLAY_EPD4?p_guid=B45EACE3D9CB56A4E034080020E74861&p_node=DZ52236&p_submitted=N&p_rank=&p_answer=&p_sourc
e=External
I have tried to use this code but because it�s for TS 1.0.2 the limits from my multi num test step and my custom steptypes isn�t exported. So that doesn�t fulfill my needs.
Is there an updated version with �all sequences� added to TS 3.0? Is there other good solutions to my problem out there?
Best Regards,
Morten Pedersen
CIM Industrial Systems A/S
DenmarkHi David Mc,
Thanks for your reply. I have already considered this solution because the source code is added in the folder described in your reply. But that is not a good solution. It will cost me a lot of time to establish the toolchain, reverse engineer the source code, make the implementations and build a new dll (most off these is already knowledge by NI). And when NI make future releases of TestStand I have some merge work to do every time NI have made some changes in the files I have changed.
But as I write above: I have hoped that NI already has/or could made a solution like the one to 1.0.2 (see link in root) to me. And then they could include it in the next version.
I don't think I am the only one in the TestStand world that ne
ed this feature.
Best regards,
Morten Pedersen
CIM Industrial Systems A/S
Denmark -
Time limits for time capsule access
I want to set time limits for individual devices on my Time Capsule network. How do I set this up??
You will need a hardware address for each wireless device that you want to be able to control. If you do not have the device listed, it will have "default" access to the wireless network, which means that it will have unlimited access at all times.
If you are having difficulty finding a hardware address for a given device, turn off all the wireless devices that will connect to the network except your Mac. You know the hardware address of your Mac already, correct?
Turn on one other wireless device and look for the info about that device. Then turn on the next device to get info about that device. You may not see a device name and instead see something like 10.0.1.x for the device name. Click on the 10.0.1.x display to reveal more information about the device, including the hardware address.
You can set up rules for each device on either the Time Capsule or the AirPort Extreme and the settings will automatically be transferred to the "other" device, so you only have to enter the rules on one device.
Open Airport Utility again and click on the Time Capsule if that is your "main" base station or router. Otherwise click on the AirPort Extreme if that is the main base station.
Click Edit
Click the Network tab at the top of the window
Look toward the bottom of the next window and make sure that there is a check mark next to Enable Access Control. Later, you will need to make sure that the other router you have is also enabled.
Click on Timed Access Control
Here you will see the "default' rule for the network of Unlimited Access. This means that any device that has not been assigned a specific rule will be able to connect to the network at any time. Leave this rule alone.
Click on the + (plus) button at the bottom of the Wireless Clients box
Type in a device name next to Description.....example.....iPad
Type in the hardware address of the device next to MAC Address
You probably want to have the rule in effect Everyday, so leave that box the same. If you click on the box, you will see that you are able to have the rule in effect with a number of other options.
Click on the All Day box and change that to Between
Double click on each time display to edit the start time and end time for the device each day. For example, the device might be able to connect Everyday, Between 9 AM and 10 PM. It is possible to have multiple rules for the same device by clicking the + button in this area to add another time slot.
Click Save
Click Timed Access Control again and repeat the process for the next device, etc until entries for all wireless devices that you want to control are complete
Click Update to save all of the settings and the Time Capsule will restart in 30 seconds.
Be sure to enter a check mark on the other router that you have to Enable Timed Access and Update to save the setting. This will transfer the stored settings from the Time Capsule to the AirPort Extreme or vice versa.
Good luck.
Maybe you are looking for
-
how do i use my 3TB airport time capsule as both time machine and hard drive? currently on Yosemite 10.10.1.....Many Thanks.
-
This makes emails I forward or print very difficult to read without time being wasdted deleting unwanted info every email.
-
Aperture has come back to the Media Browser in Pages and Keynote
Lokk for the iWork Software update. Keynote 6.2, Pages 5.2
-
Cannot vertify my account through email as no link to click on. Help!
Cannot vertify my account through email as no link to click on. Help! I have emaild iTunes support but have not come back to me yet (over 24hrs)
-
The correct SAPCAR.EXE Version (Win Server 2003 & MSQL DB)
Hi there, I am getting a stuped error (cant open file. not a win32 file...etc). I want to install supportpackages and of cours first the SAPAM ( SAPKD64038 SPAM/SAINT Update - Version 640/0038). 1) My problem when use: SAPCAR -xvf <file name> it