LiveCache sizing

Hi All
We had few performance issues in production box and after checks found that data area usage in LC was very high at 90% ,during peak load.
So we have added 4gb ( two new data files of MAXDB ), now the system performance looks better and data area utilization of max db is about 72%.
Currently we have 30GB RAM ( memory ) in LC and 52 GB data files of MaxDB .Out of 52 GB , we have 14GB as free space.
Is there any simple ratio or thumb rule for MAXDB disc space to physical Memory
Do we have to increase the physical memory (RAM) in LLC
Radhakrishnan

Hello Radhakrishnan,
1.
During the high loading in parallel the luck of CPU, memory and locking issues could occur, which leaded to the long running liveCache transactions, many history pages created.
After the transactions finished or canceled, the consistent views in liveCache were released/flaged for deletion & deleted by Garbage collectors, which run regularly.
Use the DB analyzer to find the bottleneck in liveCache.
Create the SAP message to SV-BO-SCM component to check & help you with performance tunning of the load to liveCache scenario.
2.
Please review the SAP note:
1247666 FAQ: SAP MaxDB/liveCache history pages
Regards, Natalia Khlopina

Similar Messages

Report for LiveCache size

Hi everybody,
is there a report that provides me with the LiveCache size?
Thank you in advance for your help.
Kind regards
Mitch

Hello Mitch
May be this thread will give some insight on Livecache Sizing and maintenance.
Reduce Livecache Database size
Also based on my old notes, following are key considerations while calculating Livecache Size. This has to be for every planning area which exist in your APO system
Number of Characteristic Combinations
Number of Keyfigures in Planning horizon
Number of Periods in planning horizon
Number of Keyfigures in Historical horizon
Number of Periods in Historical horizon
Total Number of Keyfigures in the entire horizon
Total Number of periods in the entire horizon
Number of planning versions in Infocube
Number of planning versions in livecache
Hope this will help.
Thank you
Satish Waghmare

Restriction of Overlapping of the periods in Planning Book

Hi Experts
Currently we are using monthly planning for future horizon of 12 months,We want to replace monthly level planning to the weekly level.
I am worried about the time buckets in the planning book, we cannot determine the exact forecast quantity of the particular month when week is shared between the two months since overlapping of the time period happens.
When i use Weekly Time buckets:
Planning book appears like: wk1.2011-wk2.2011-wk3.2011-wk4.2011-wk5.2011-wk6.2011-wk7.2011-wk8.2011-w9.2011-wk10.2011
T
In the above time buckets represents the following from date to to date:
wk1.2011 = 03.01.2011-09.01.2011
wk2.2011 = 10.01.2011-16.01.2011
wk3.2011 = 17.01.2011-23.01.2011
wk4.2011 = 24.01.2011-30.01.2011
wk5.2011 = 31.01.2011-06.02.2011
wk6.2011 = 07.02.2011-13.02.2011
wk7.2011 = 14.02.2011-20.02.2011
wk8.2011 = 21.02.2011-27.02.2011
wk9.2011 = 28.02.2011-06.03.2011
wk10.2011 = 07.03.2011-13.03.2011
WK5.2011 is sharing between the Jan 2011 and Feb 2011
WK9.2011 is sharing between the Feb 2011 and Mar 2011
But my customer requirment is as follows:
03.01.2011-09.01.2011/10.01.2011-16.01.2011/17.01.2011-23.01.2011/24.01.2011-30.01.2011/31.01.2011-31.01.2011/01.02.2011-06.02.2011/07.02.2011-13.02.2011/14.02.2011-20.02.2011/21.02.2011-27.02.2011/28.02.2011-28.02.2011/01.03.2011-06.03.2011/07.03.2011-13.03.2011
If the week is sharing between the two months, there should be two columns to separate the week by month days.
How to achieve this ?
Thanks
Kanth

Thomas
Respectfully disagree that Days is necessarily required in the storage bucket profile. Even without Days, as long as both Week and Month are selected, the system will automatically split quantities into technical periods and allow planning books to display data by week or month (But not day).
From SAP Help :
You select the periodicities month and week in the storage buckets profile.Data for the months of June and July 2001 is stored in the following buckets, also known as technical periods.
June 1-3               3 days
June 4-10             7 days
June 11-17           7 days
June 18-24           7 days
June 25-30           6 days
July 1                   1 day
July 2-8                7 days
July 9-15             7 days
July 16-22            7 days
July 23-29            7 days
July 30-31            2 days
Of course, it would work if days is included as well, but it would unneccarily increase Livecache Sizing requirements. Again from SAP Help:
Include in the storage buckets profile only the periodicities you need because the technical periods take up storage space. On the other hand, you must include all the periodicities in which you intend to plan.
Rishi Menon

Reason to size liveCache filesystems 2x RAM?

Hi,
I am sizing liveCache database for future rollouts of existing system. (liveCache 7.7.04, SCM 5.1, Unix platform)
In the liveCache installation guide, the recommendation is to size the unix sapdata filesystems to be 2x the size of RAM.
SAP SCM 5.1 Standalone Engine SAP liveCache Technology 7.7: UNIX Document version: 1.0 ‒ 08/31/2007
Page 11, section 3.3
File System Name Description Recommendation
/sapdb/<LC_NAME>/sapdata[1-n] Data Volumes 2 x RAM, minimum 3 GB
/sapdb/<LC_NAME>/saplog Log Volume 2 GB
What is reason for this recommendation? I assume it has something to do with the history data in datacache during system shutdown and not also the 1x RAM for KernelDumpFileName path, and > 1x RAM for backup directory because only the liveCache database, not the KernelDumpFileName or backup directories are in the sapdata* filesystems.
In these frugal economic times, we are requested to justify hardware expenditures. 2x RAM seems excessive for sapdata filesystems when the RAM is 200-350GB in addition to the 1x RAM KernelDumpFileName and >1x RAM backup space needed.
Also, I assume it means the total space of all sapdata filesystems is requested to be 2x RAM, and not each individual filesystem.
Is there more explanation, clarification or justification on the disk sizing for liveCache?
Thanks in advance,
Margaret

Hello Margaret
> What is reason for this recommendation?
Plain and simple: it's necessary to have that amount of space to put data to.
>I assume it has something to do with the history data in datacache during system shutdown
?? Not totally sure what you mean by that.
However, liveCache implements what is calles a "consistent view" to it's objects.
This means that it needs to keep several versions of the same object in the data area at the same time.
Let's assume that your planning scenarios really use up the whole RAM for the liveCache, this alone does not allow to keep multiple versions.
Thus there need to be more space available in the data area.
Doubling the size of the RAM for the Data area (not for each single filesystem) has proven to be a good starting estimation.
> and not also the 1x RAM for KernelDumpFileName path, and > 1x RAM for backup directory because only the liveCache database, not the KernelDumpFileName or backup directories are in the sapdata* filesystems.
?? did not get that...
> In these frugal economic times, we are requested to justify hardware expenditures. 2x RAM seems excessive for sapdata filesystems when the RAM is 200-350GB in addition to the 1x RAM KernelDumpFileName and >1x RAM backup space needed.
No it isn't.
And, really, what does a TB harddisk space cost these days?
> Also, I assume it means the total space of all sapdata filesystems is requested to be 2x RAM, and not each individual filesystem.
You assume correclty.
> Is there more explanation, clarification or justification on the disk sizing for liveCache?
That's pretty much it.
You may of course start with less then recommended diskspace, but you might run into problems later on with it.
regards,
Lars

Quick sizing for Demand Planning system

Hi All
Our team is required to do quick sizing for a SCM 5.0 Demand Planning system with Livecache. The DEV and QAS is already available but not being used at all but now we need the quick sizing for the production box. I have never done any quick sizing, detailed help is appreciated. I have gone through the service.sap.com/quicksizing for demand planning it shows 3 input tables only for Throughput sizing - Time Series, DP Run, DP Users. The APO functional guys entered some numbers but not sure what to do next as the Calculate Result shows information Iam not able to understand.
What I need from sizing is CPU processor, disk size, memory size, etc in clear detail. Please suggest, Thanks in advance.
Regards
Ali

Hello Ali,
First of all I am not a BASIS consultant and hence it would not be prudent for me to comment on hardware configuration reuqired in your case.
Secondly I do not understand what you mean by Quicksizer has been shut down. It is available online at <a href="http://service.sap.com/quicksizer">Quicksizer Tool</a> in Service Marketplace.
There is good amount of documentation available in the website giving details on the basis of computation of different parameters. Again SCM Hardware Configuration is not just dependent on the number of users but the functional requirements as well.
Thirdly - I cannot explain how SAPS concept is related to SCM Quicksizing. Per my understanding the SAPS concept is an hardware-independent benchmark of throughput which is an indicator of the processing capabilities required at peak loads. SAPS will determines the number and processor speed on your Application Server depending on the processor capabilities. Most hardware vendors provide datasheets with SAPS capabilities.
Suggest you go through the document "Background: Sizing mySAP Business Suite" under Sizing Guidelines >> General Sizing Procedures.
Thanks,
somnath

MaxDB/Livecache running on VSphere

Does anyone have productive instances of MaxDB/Livecache running in a virtual mode using Vsphere 4.x? We have a Livecache system that was originally sized for slightly over 128GB of memory but now have a memory requirement that is < 64GB. We are trying to determine if running on VSphere is an alternative to eliminate the need for dedicated physical servers.
Joe

We run a few smaller SAP production systems on MaxDB on vSpher 4.1. Two bigger test and QA systems (1 TB + 2,9 TB) are also running under vSphere. The production however runs on bare metal because our tests showed that I/O is slower.
Since a liveCache doesn't do "traditional database I/O" I'd say that the performance would be equal than non-virtualized.
Markus

Livecache 7.5 installation

Hi All
We are planning to install a new Livecache 7.5 on AIX 5.1 server but we already have another SAPDB version 7.3.0 installed on same machine (It servs an XI installation). Our doubt is :
1. During the installation fase (for Livecache), our indep programs will be upgraded or do we need to do it before?
2. Is there any problem installing and working with this two softwares on same host?
Many Thanks
Daniela Godoi

Hello Daniela,
you should be able to run both on the same machine. Please make sure both instances are correctly configured and sized, so that you don't run into resource problems.
To answer your questions:
1. You have to do it before. In case you try to install a new liveCache/MaxDB 7.5 instance on a machine which already has a liveCache/SAP DB instance <= 7.4, then you need to upgrade the Client Installation first.
In other words: install the 7.5 client on your machine first (you can use sdbinst using the new 7.5 liveCache software to do that, as described in OSS note 649814).
!!! IMPORTANT:
Please be aware that with liveCache 7.5 there's a new Unix security concept. During the above client installation, you will be asked for a user & group, to whom the database will belong. The defaults are 'sdb' (user) and 'sdba' (group). If you have no objection against these, I suggest you take the defaults.
-> The user of the other instances (7.3) will then be placed in the 'sdba' group.
After installing the new 7.5 client software, you should be able to follow your 7.5 liveCache installation guide to install the complete liveCache 7.5 software.
2. As said in the beginning, there should be no problems, <i>if</i> everything is handled correctly.
Should you experience any problems at all, I'll probably ask you to open a OSS/CSS message on queue BC-DB-LVC.
Kind regards,
Roland

NetWeaver 2004s (BI-IP) liveCache Infrastructure Requirements

Team SAP,
One of my customers is interested in utilizing the liveCache option to manage their lock table for Integrated Planning (BI-IP).
Do we have any documentation and guidance we can provide on requirements and configuration scenarios. Some of the questions being asked include:
1) Can the liveCache be installed on the same box where BI-IP will be running (i.e. NetWeaver 2004s production box)
2) Is there a need to purchase new hardware, and what are the guidelines for sizing and configuration?
Thank you in advance for any help you may be able to provide.
-M

Hi Michael,
This functionality should documented. E.g. When you call transaction RSPLAN, there is a button "Manage Lock Server", on the first tab ("Lock Table"), there are "i"-buttons for a short introduction. For configuration information on live cache, please look at note 816730.
This technology is new with NW2004s, and we at SAP development are very much interested in your feedback. (customer scenario, numbers of concurring users, comparison to shared object based technology, etc.)
So, for best project support please involve your SAP ramp up coach in order to get into contact with the ramp up back office. This will garantuee you best support.
Regards,
Tobias Hagen

Error in Starting liveCache

Hello there,
    When starting our liveCache in LC10, I encountered an error message stating that "ERROR DBMCLI COMMANDEXECUTE_ERROR when starting liveCache LC1 on server". But nevertheless, the liveCache status turned green. I read the logs in Messages --> Logs --> History and found the following messages: (i replaced the actual password with <b><password of SAPLC1>)</b>
START *****************************
liveCache LC1 (restart)
Thu 09/13/2007
01:23 PM
installation path = c:\sapdb\lc1\db
OK
OK
DBMServer 7.6.00   Build 029-123-130-265
starting LC1 into ONLINE
OK
Creating liveCache application procedures
ERR
-24964,ERR_EXECUTE: error in program execution
3,""c:\sapdb\lc1\db\bin\x_python" "c:\sapdb\lc1\db\env\lapps.py" -R "c:\sapdb\lc1\db" -d LC1 -u SUPERDBA,*"
Installing APPS
Traceback----
File "c:\sapdb\lc1\db\env\installib.py", line 410, in connectAndInstall
    installRoutine (session, options)
File "c:\sapdb\lc1\db\env\lapps.py", line 43, in install
    "APPS"
File "c:\sapdb\lc1\db\env\installib.py", line 172, in include
    install (session, options)
File "c:\sapdb\lc1\db\env\APPS.py", line 75, in install
    loaderCmd (session, 'USE USER %s %s' % (sapuser[0], sapuser[1]))
Command----
USE USER saplc1 <password of SAPLC1>
Error----
loader.LoaderError: [-25008] Logon failure; previous user's (SUPERDBA) connection was restored.
ERROR : liveCache LC1 not started
Thu 09/13/2007
01:24 PM
END ******************************
START *****************************
liveCache LC1 (shutdown)
Thu 09/13/2007
01:31 PM
installation path = c:\sapdb\lc1\db
OK
DBMServer 7.6.00   Build 029-123-130-265
stopping LC1
OK
liveCache LC1 successfully stopped.
Thu 09/13/2007
01:31 PM
END ******************************
START *****************************
liveCache LC1 (restart)
Thu 09/13/2007
01:31 PM
installation path = c:\sapdb\lc1\db
OK
OK
DBMServer 7.6.00   Build 029-123-130-265
starting LC1 into ONLINE
OK
Creating liveCache application procedures
ERR
-24964,ERR_EXECUTE: error in program execution
3,""c:\sapdb\lc1\db\bin\x_python" "c:\sapdb\lc1\db\env\lapps.py" -R "c:\sapdb\lc1\db" -d LC1 -u SUPERDBA,*"
Installing APPS
Traceback----
File "c:\sapdb\lc1\db\env\installib.py", line 410, in connectAndInstall
    installRoutine (session, options)
File "c:\sapdb\lc1\db\env\lapps.py", line 43, in install
    "APPS"
File "c:\sapdb\lc1\db\env\installib.py", line 172, in include
    install (session, options)
File "c:\sapdb\lc1\db\env\APPS.py", line 75, in install
    loaderCmd (session, 'USE USER %s %s' % (sapuser[0], sapuser[1]))
Command----
USE USER saplc1 <password of SAPLC1>
Error----
loader.LoaderError: [-25008] Logon failure; previous user's (SUPERDBA) connection was restored.
ERROR : liveCache LC1 not started
Thu 09/13/2007
01:31 PM
END ******************************
Another thing is, the actual password is not the same password I changed in DBMGUI and in Integration. Can you please help me with this error and -24964,ERR_EXECUTE: error in program execution keeps appearing in the logs.
Thank you.

Hello Deanna Mariel Marasigan,
-> please check which user you set for LCA connection in LC10 -> Integration.
    You wrote, that it's SAPLC1. Correct?
-> run the SQL statement as superdba user & check if this user is listed:
select * from domain.users
-> To make sure that the lcinit script works with the correct Standard liveCache
user then you should run the commands to check the
liveCache user in the upc container:
In a dbmcli session (e.g. in LC10 -> liveCache:Monitoring -> Tools)
sql_execute user-type=SAP select user from dual
Should return this user - SAPLC1
When an error returns ( unknown user/password ), then no user is set or wrong password.
To set the new password for Standard user in the upc container run:
dbmcli -d LC1 -n <LC-server> -u control,<control> user_sap SAPLC1,<pwd-new>
( please see the SAP note 616555 for more details ).
This sets the new user/pwd in the upc container.
After that the above command should return the user.
Restart the liveCache in the LC10 transaction.
Thank you and best regards, Natalia Khlopina

Data Federator Sizing & Usage

Hi,
I am looking for a Data Federator wiki & sizing guide..
we have in the process of installing Data Federator 3.0 on a windows platform.
I am not familiar with this component. Please throw some light on how is it exactly used..
What does the Data Federator do ? why is it implmented...Please help me..

Hi
I would recommend to take a look at the user guide:
http://help.sap.com/businessobject/product_guides/boexi3SP2/en/xi3_sp2_df_userguide_en.pdf
Regards,
Stratos

While running the livecache server test a native sql error occures

We are using scm4.1 livecache 7.5.0 And every time we are running the livecache test program he is dumping
whith the following dump
patch level scm & scm_basis is 8
Runtime Errors         DBIF_DSQL2_SQL_ERROR
Except.                CX_SY_NATIVE_SQL_ERROR
Date and Time          31.10.2005 16:50:55
ShrtText
An SQL error occurred when executing Native SQL.
What happened?
Error 600 occurred in the current database connection "LCA".
What can you do?
Print out the error message (using the "Print" function)
and make a note of the actions and input that caused the
error.
To resolve the problem, contact your SAP system administrator.
You can use transaction ST22 (ABAP Dump Analysis) to view and administer
termination messages, especially those beyond their normal deletion
date.
is especially useful if you want to keep a particular message.
How to correct the error
Database error text........: "Work rolled back: DbpError -28814 in
APS_ORDER_CH"
Database error code .......: 600
Triggering SQL statement...: " ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ?
? ? ? ? ? ? ? or'"
Internal call code.........: "[DBDS/NEW DSQL]"
Please check the entries in the system log (Transaction SM21).
You may able to find an interim solution to the problem
in the SAP note system. If you have access to the note system yourself,
use the following search criteria:
"DBIF_DSQL2_SQL_ERROR" CX_SY_NATIVE_SQL_ERRORC
"/SAPAPO/SAPLOM_PLANNING" or "/SAPAPO/LOM_PLANNINGU08"
"/SAPAPO/OM_ORDER_CHANGE"
If you cannot solve the problem yourself and you wish to send
an error message to SAP, include the following documents:
1. A printout of the problem description (short dump)
To obtain this, select in the current display "System->List->
Save->Local File (unconverted)".
2. A suitable printout of the system log
To obtain this, call the system log through transaction SM21.
Limit the time interval to 10 minutes before and 5 minutes
after the short dump. In the display, then select the function
"System->List->Save->Local File (unconverted)".
3. If the programs are your own programs or modified SAP programs,
supply the source code.
To do this, select the Editor function "Further Utilities->
Upload/Download->Download".
4. Details regarding the conditions under which the error occurred
or which actions and input led to the error.
The exception must either be prevented, caught within the procedure
"/SAPAPO/OM_ORDER_CHANGE"
"(FUNCTION)", or declared in the procedure's RAISING clause.
To prevent the exception, note the following:
System environment
SAP Release.............. "640"
Application server....... "bebruap2"
Network address.......... "195.213.49.227"
Operating system......... "Windows NT"
Release.................. "5.2"
Hardware type............ "4x Intel 801586"
Character length......... 16 Bits
Pointer length........... 32 Bits
Work process number...... 1
Short dump setting....... "full"
Database server.......... "BEBRUAP2"
Database type............ "MSSQL"
Database name............ "APD"
Database owner........... "apd"
Character set............ "C"
SAP kernel............... "640"
Created on............... "Aug 23 2005 00:00:49"
Created in............... "NT 5.0 2195 Service Pack 4 x86 MS VC++ 13.10"
Database version......... "SQL_Server_8.00 "
Patch level.............. "87"
Patch text............... " "
Supported environment....
Database................. "MSSQL 7.00.699 or higher, MSSQL 8.00.194"
SAP database version..... "640"
Operating system......... "Windows NT 5.0, Windows NT 5.1, Windows NT 5.2"
Memory usage.............
Roll..................... 8176
EM....................... 24040336
Heap..................... 0
Page..................... 1687552
MM Used.................. 1516920
MM Free.................. 572032
SAP Release.............. "640"
User and Transaction
Client.............. 000
User................ "CGRAULS"
Language key........ "E"
Transaction......... "/SAPAPO/OM03 "
Program............. "/SAPAPO/SAPLOM_PLANNING"
Screen.............. "SAPMSSY0 1000"
Screen line......... 6
Information on where terminated
The termination occurred in the ABAP program "/SAPAPO/SAPLOM_PLANNING" in
"/SAPAPO/OM_ORDER_CHANGE".
The main program was "/SAPAPO/OM_TB_FLOW_QUANTITY ".
The termination occurred in line 91 of the source code of the (Include)
program "/SAPAPO/LOM_PLANNINGU08"
of the source code of program "/SAPAPO/LOM_PLANNINGU08" (when calling the
editor 910).
Processing was terminated because the exception "CX_SY_NATIVE_SQL_ERROR"
occurred in the
procedure "/SAPAPO/OM_ORDER_CHANGE" "(FUNCTION)" but was not handled locally,
not declared in the
RAISING clause of the procedure.
The procedure is in the program "/SAPAPO/SAPLOM_PLANNING ". Its source code
starts in line 5
of the (Include) program "/SAPAPO/LOM_PLANNING$08 ".
Source Code Extract
Line
SourceCde
61
is_gen_params-simversion
62
is_gen_params-dont_set_netchg_flag
63
space.
64
65
Kontrollstruktur IS_GET_CHANGED_OPTIONS anpassen.
66
IF NOT et_changed_orders IS REQUESTED.
67
is_get_changed_options-send_chg_top_order = gc_false.
68
ENDIF.
69
IF NOT et_changed_cap_reqs IS REQUESTED.
70
is_get_changed_options-send_chg_cap_req = gc_false.
71
ENDIF.
72
IF NOT et_changed_io_nodes IS REQUESTED.
73
is_get_changed_options-send_chg_ionode = gc_false.
74
ENDIF.
75
IF NOT et_changed_io_pp_nodes IS REQUESTED.
76
is_get_changed_options-send_chg_io_pp = gc_false.
77
ENDIF.
78
IF NOT et_changed_pegids IS REQUESTED.
79
is_get_changed_options-send_chg_pegid = gc_false.
80
ENDIF.
81
IF NOT et_deleted_fix_pegging IS REQUESTED.
82
is_get_changed_options-send_del_fix_peg = gc_false.
83
ENDIF.
84
start_function 'OM_ORDER_CHANGE'.                         "#EC *
85
Verbindung zum liveCache aufbauen
86
check_server.
87
connect_to_livecache.
88
COM-Routine zum Anlegen bzw. Überschreiben eines Zeitstrahls
89
90
EXEC sql.
>>>>>
execute procedure                  "APS_ORDER_CHANGE" (
92
in :ls_gen_com_params,
93
out :lv_rc,
94
in :et_rc,
95
in :it_order_method,
96
in :it_ordkeys,
97
in :it_ordmaps,
98
in :it_orders,
99
in :it_activities,
100
in :it_mode,
101
in :it_cap_reqs,
102
in :it_positions,
103
in :it_inputs,
104
in :it_outputs,
105
in :it_prodflow,
106
in :it_intern_constraints,
107
in :it_extern_constraints,
108
in :it_charact_val_acts,
109
in :it_charact_req_inpnode,
110
in :it_charact_val_outnode,
Contents of system fields
Name
Val.
SY-SUBRC
0
SY-INDEX
0
SY-TABIX
1
SY-DBCNT
1
SY-FDPOS
0
SY-LSIND
0
SY-PAGNO
0
SY-LINNO
1
SY-COLNO
1
SY-PFKEY
SY-UCOMM
SY-TITLE
Flow Quantity Test
SY-MSGTY
S
SY-MSGID
/SAPAPO/OM_TEST
SY-MSGNO
001
SY-MSGV1
Create transSim
SY-MSGV2
SY-MSGV3
SY-MSGV4
Active Calls/Events
No.   Ty.          Program                             Include                             Line
Name
3 FUNCTION     /SAPAPO/SAPLOM_PLANNING             /SAPAPO/LOM_PLANNINGU08                91
/SAPAPO/OM_ORDER_CHANGE
2 FORM         /SAPAPO/OM_TB_FLOW_QUANTITY         /SAPAPO/OM_TB_FLOW_QUANTITY           802
CHANGE_DATA
1 EVENT        /SAPAPO/OM_TB_FLOW_QUANTITY         /SAPAPO/OM_TB_FLOW_QUANTITY            11
START-OF-SELECTION
Chosen variables
Name
Val.
No.       3 Ty.          FUNCTION
Name /SAPAPO/OM_ORDER_CHANGE
IS_ATP_INFO
01ATP0000001~CGRAULSXX##
334553333333744545455500
011400000001E37215C38800
000000000000000000000000
000000000000000000000000
IS_CONTROLPARAMETERS
霁က#ం̂⍱㔒鲔#####
2222222222222222222222001007190000022
0000000000000000000000100221240000100
0000000000000000000000910002390000000
0000000000000000000000700C335C000C000
IS_GEN_PARAMS
01PLV0000001~CGRAULS
3354533333337445454522222
010C60000001E37215C300000
0000000000000000000000000
0000000000000000000000000
IS_GET_CHANGED_OPTIONS
2222222
0000000
0000000
0000000
IT_ACTIVITIES
Table IT_274[1x256]
PROGRAM=/SAPAPO/OM_TB_FLOW_QUANTITYFORM=CHANGE_DATADATA=LT_ACTIVITIES
Table reference: 41
TABH+ 0(20) = 5087FFDF00000000000000002900000012010000
TABH+ 20(20) = 0100000000010000FFFFFFFF0487000000290000
TABH+ 40( 8) = 10000000C1308000
store        = 0x5087FFDF
ext1         = 0x00000000
shmId        = 0     (0x00000000)
id           = 41    (0x29000000)
label        = 274   (0x12010000)
fill         = 1     (0x01000000)
leng         = 256   (0x00010000)
loop         = -1    (0xFFFFFFFF)
xtyp         = TYPE#000205
occu         = 16    (0x10000000)
access       = 1     (ItAccessStandard)
idxKind      = 0     (ItIndexNone)
uniKind      = 2     (ItUniqueNon)
keyKind      = 1     (default)
cmpMode      = 8     (cmpManyEq)
occu0        = 1
collHash     = 0
groupCntl    = 0
rfc          = 0
unShareable = 0
mightBeShared = 0
sharedWithShmTab = 0
isShmLockId = 0
gcKind       = 0
isUsed       = 1
>>>>> Shareable Table Header Data <<<<<
tabi         = 0x180112E0
pghook       = 0x00000000
idxPtr       = 0x00000000
refCount     = 0     (0x00000000)
tstRefCount = 0     (0x00000000)
lineAdmin    = 16    (0x10000000)
lineAlloc    = 16    (0x10000000)
store_id     = 126   (0x7E000000)
shmIsReadOnly = 0     (0x00000000)
>>>>> 1st level extension part <<<<<
regHook      = Not allocated
hsdir        = Not allocated
ext2         = Not allocated
>>>>> 2nd level extension part <<<<<
tabhBack     = Not allocated
delta_head   = Not allocated
pb_func      = Not allocated
pb_handle    = Not allocated
IT_CAP_REQS
Table IT_276[1x112]
PROGRAM=/SAPAPO/OM_TB_FLOW_QUANTITYFORM=CHANGE_DATADATA=LT_CAP_REQS
Table reference: 39
TABH+ 0(20) = 48BB06E000000000000000002700000014010000
TABH+ 20(20) = 0100000070000000FFFFFFFF04870000C0290000
TABH+ 40( 8) = 10000000C1308000
store        = 0x48BB06E0
ext1         = 0x00000000
shmId        = 0     (0x00000000)
id           = 39    (0x27000000)
label        = 276   (0x14010000)
fill         = 1     (0x01000000)
leng         = 112   (0x70000000)
loop         = -1    (0xFFFFFFFF)
xtyp         = TYPE#000209
occu         = 16    (0x10000000)
access       = 1     (ItAccessStandard)
idxKind      = 0     (ItIndexNone)
uniKind      = 2     (ItUniqueNon)
keyKind      = 1     (default)
cmpMode      = 8     (cmpManyEq)
occu0        = 1
collHash     = 0
groupCntl    = 0
rfc          = 0
unShareable = 0
mightBeShared = 0
sharedWithShmTab = 0
isShmLockId = 0
gcKind       = 0
isUsed       = 1
>>>>> Shareable Table Header Data <<<<<
tabi         = 0x188D04E0
pghook       = 0x00000000
idxPtr       = 0x00000000
refCount     = 0     (0x00000000)
tstRefCount = 0     (0x00000000)
lineAdmin    = 16    (0x10000000)
lineAlloc    = 16    (0x10000000)
store_id     = 124   (0x7C000000)
shmIsReadOnly = 0     (0x00000000)
>>>>> 1st level extension part <<<<<
regHook      = Not allocated
hsdir        = Not allocated
ext2         = Not allocated
>>>>> 2nd level extension part <<<<<
tabhBack     = Not allocated
delta_head   = Not allocated
pb_func      = Not allocated
pb_handle    = Not allocated
IT_CHARACT_REQ_INPNODE
Table IT_418[0x140]
FUNCTION=/SAPAPO/OM_ORDER_CHANGEDATA=IT_CHARACT_REQ_INPNODE
Table reference: 32
TABH+ 0(20) = 00000000000000000000000020000000A2010000
TABH+ 20(20) = 000000008C000000FFFFFFFF04870000301D0000
TABH+ 40( 8) = 10000000C1308000
store        = 0x00000000
ext1         = 0x00000000
shmId        = 0     (0x00000000)
id           = 32    (0x20000000)
label        = 418   (0xA2010000)
fill         = 0     (0x00000000)
leng         = 140   (0x8C000000)
loop         = -1    (0xFFFFFFFF)
xtyp         = TYPE#000142
occu         = 16    (0x10000000)
access       = 1     (ItAccessStandard)
idxKind      = 0     (ItIndexNone)
uniKind      = 2     (ItUniqueNon)
keyKind      = 1     (default)
cmpMode      = 8     (cmpManyEq)
occu0        = 1
collHash     = 0
groupCntl    = 0
rfc          = 0
unShareable = 0
mightBeShared = 0
sharedWithShmTab = 0
isShmLockId = 0
gcKind       = 0
isUsed       = 1
>>>>> Shareable Table Header Data <<<<<
tabi         = Not allocated
pghook       = Not allocated
idxPtr       = Not allocated
refCount     = Not allocated
tstRefCount = Not allocated
lineAdmin    = Not allocated
lineAlloc    = Not allocated
store_id     = Not allocated
shmIsReadOnly = Not allocated
>>>>> 1st level extension part <<<<<
regHook      = Not allocated
hsdir        = Not allocated
ext2         = Not allocated
>>>>> 2nd level extension part <<<<<
tabhBack     = Not allocated
delta_head   = Not allocated
pb_func      = Not allocated
pb_handle    = Not allocated
IT_CHARACT_VAL_ACTS
Table IT_417[0x156]
FUNCTION=/SAPAPO/OM_ORDER_CHANGEDATA=IT_CHARACT_VAL_ACTS
Table reference: 50
TABH+ 0(20) = 00000000000000000000000032000000A1010000
TABH+ 20(20) = 000000009C000000FFFFFFFF04870000901D0000
TABH+ 40( 8) = 10000000C1308000
store        = 0x00000000
ext1         = 0x00000000
shmId        = 0     (0x00000000)
id           = 50    (0x32000000)
label        = 417   (0xA1010000)
fill         = 0     (0x00000000)
leng         = 156   (0x9C000000)
loop         = -1    (0xFFFFFFFF)
xtyp         = TYPE#000144
occu         = 16    (0x10000000)
access       = 1     (ItAccessStandard)
idxKind      = 0     (ItIndexNone)
uniKind      = 2     (ItUniqueNon)
keyKind      = 1     (default)
cmpMode      = 8     (cmpManyEq)
occu0        = 1
collHash     = 0
groupCntl    = 0
rfc          = 0
unShareable = 0
mightBeShared = 0
sharedWithShmTab = 0
isShmLockId = 0
gcKind       = 0
isUsed       = 1
>>>>> Shareable Table Header Data <<<<<
tabi         = Not allocated
pghook       = Not allocated
idxPtr       = Not allocated
refCount     = Not allocated
tstRefCount = Not allocated
lineAdmin    = Not allocated
lineAlloc    = Not allocated
store_id     = Not allocated
shmIsReadOnly = Not allocated
>>>>> 1st level extension part <<<<<
regHook      = Not allocated
hsdir        = Not allocated
ext2         = Not allocated
>>>>> 2nd level extension part <<<<<
tabhBack     = Not allocated
delta_head   = Not allocated
pb_func      = Not allocated
pb_handle    = Not allocated
IT_CHARACT_VAL_OUTNODE
Table IT_419[0x156]
FUNCTION=/SAPAPO/OM_ORDER_CHANGEDATA=IT_CHARACT_VAL_OUTNODE
Table reference: 60
TABH+ 0(20) = 0000000000000000000000003C000000A3010000
TABH+ 20(20) = 000000009C000000FFFFFFFF04870000901D0000
TABH+ 40( 8) = 10000000C1308000
store        = 0x00000000
ext1         = 0x00000000
shmId        = 0     (0x00000000)
id           = 60    (0x3C000000)
label        = 419   (0xA3010000)
fill         = 0     (0x00000000)
leng         = 156   (0x9C000000)
loop         = -1    (0xFFFFFFFF)
xtyp         = TYPE#000144
occu         = 16    (0x10000000)
access       = 1     (ItAccessStandard)
idxKind      = 0     (ItIndexNone)
uniKind      = 2     (ItUniqueNon)
keyKind      = 1     (default)
cmpMode      = 8     (cmpManyEq)
occu0        = 1
collHash     = 0
groupCntl    = 0
rfc          = 0
unShareable = 0
mightBeShared = 0
sharedWithShmTab = 0
isShmLockId = 0
gcKind       = 0
isUsed       = 1
>>>>> Shareable Table Header Data <<<<<
tabi         = Not allocated
pghook       = Not allocated
idxPtr       = Not allocated
refCount     = Not allocated
tstRefCount = Not allocated
lineAdmin    = Not allocated
lineAlloc    = Not allocated
store_id     = Not allocated
shmIsReadOnly = Not allocated
>>>>> 1st level extension part <<<<<
regHook      = Not allocated
hsdir        = Not allocated
ext2         = Not allocated
>>>>> 2nd level extension part <<<<<
tabhBack     = Not allocated
delta_head   = Not allocated
pb_func      = Not allocated
pb_handle    = Not allocated
IT_EXTERN_CONSTRAINTS
Table IT_416[0x124]
FUNCTION=/SAPAPO/OM_ORDER_CHANGEDATA=IT_EXTERN_CONSTRAINTS
Table reference: 71
TABH+ 0(20) = 00000000000000000000000047000000A0010000
TABH+ 20(20) = 000000007C000000FFFFFFFF04870000E02A0000
TABH+ 40( 8) = 10000000C1308000
store        = 0x00000000
ext1         = 0x00000000
shmId        = 0     (0x00000000)
id           = 71    (0x47000000)
label        = 416   (0xA0010000)
fill         = 0     (0x00000000)
leng         = 124   (0x7C000000)
loop         = -1    (0xFFFFFFFF)
xtyp         = TYPE#000215
occu         = 16    (0x10000000)
access       = 1     (ItAccessStandard)
idxKind      = 0     (ItIndexNone)
uniKind      = 2     (ItUniqueNon)
keyKind      = 1     (default)
cmpMode      = 8     (cmpManyEq)
occu0        = 1
collHash     = 0
groupCntl    = 0
rfc          = 0
unShareable = 0
mightBeShared = 0
sharedWithShmTab = 0
isShmLockId = 0
gcKind       = 0
isUsed       = 1
>>>>> Shareable Table Header Data <<<<<
tabi         = Not allocated
pghook       = Not allocated
idxPtr       = Not allocated
refCount     = Not allocated
tstRefCount = Not allocated
lineAdmin    = Not allocated
lineAlloc    = Not allocated
store_id     = Not allocated
shmIsReadOnly = Not allocated
>>>>> 1st level extension part <<<<<
regHook      = Not allocated
hsdir        = Not allocated
ext2         = Not allocated
>>>>> 2nd level extension part <<<<<
tabhBack     = Not allocated
delta_head   = Not allocated
pb_func      = Not allocated
pb_handle    = Not allocated
IT_INPUTS
Table IT_278[1x420]
PROGRAM=/SAPAPO/OM_TB_FLOW_QUANTITYFORM=CHANGE_DATADATA=LT_INPUTS
Table reference: 63
TABH+ 0(20) = 087400E0C0E303E0000000003F00000016010000
TABH+ 20(20) = 01000000A4010000FFFFFFFF04870000202A0000
TABH+ 40( 8) = 10000000C1308000
store        = 0x087400E0
ext1         = 0xC0E303E0
shmId        = 0     (0x00000000)
id           = 63    (0x3F000000)
label        = 278   (0x16010000)
fill         = 1     (0x01000000)
leng         = 420   (0xA4010000)
loop         = -1    (0xFFFFFFFF)
xtyp         = TYPE#000211
occu         = 16    (0x10000000)
access       = 1     (ItAccessStandard)
idxKind      = 0     (ItIndexNone)
uniKind      = 2     (ItUniqueNon)
keyKind      = 1     (default)
cmpMode      = 8     (cmpManyEq)
occu0        = 1
collHash     = 0
groupCntl    = 0
rfc          = 0
unShareable = 0
mightBeShared = 0
sharedWithShmTab = 0
isShmLockId = 0
gcKind       = 0
isUsed       = 1
>>>>> Shareable Table Header Data <<<<<
tabi         = 0x78DC11E0
pghook       = 0x00000000
idxPtr       = 0x00000000
refCount     = 0     (0x00000000)
tstRefCount = 0     (0x00000000)
lineAdmin    = 16    (0x10000000)
lineAlloc    = 16    (0x10000000)
store_id     = 123   (0x7B000000)
shmIsReadOnly = 0     (0x00000000)
>>>>> 1st level extension part <<<<<
regHook      = 0x2029FFDF
hsdir        = 0x00000000
ext2         = 0x00000000
>>>>> 2nd level extension part <<<<<
tabhBack     = Not allocated
delta_head   = Not allocated
pb_func      = Not allocated
pb_handle    = Not allocated
IT_INTERN_CONSTRAINTS
Table IT_415[0x124]
FUNCTION=/SAPAPO/OM_ORDER_CHANGEDATA=IT_INTERN_CONSTRAINTS
Table reference: 49
TABH+ 0(20) = 000000000000000000000000310000009F010000
TABH+ 20(20) = 000000007C000000FFFFFFFF04870000E02A0000
TABH+ 40( 8) = 10000000C1308000
store        = 0x00000000
ext1         = 0x00000000
shmId        = 0     (0x00000000)
id           = 49    (0x31000000)
label        = 415   (0x9F010000)
fill         = 0     (0x00000000)
leng         = 124   (0x7C000000)
loop         = -1    (0xFFFFFFFF)
xtyp         = TYPE#000215
occu         = 16    (0x10000000)
access       = 1     (ItAccessStandard)
idxKind      = 0     (ItIndexNone)
uniKind      = 2     (ItUniqueNon)
keyKind      = 1     (default)
cmpMode      = 8     (cmpManyEq)
occu0        = 1
collHash     = 0
groupCntl    = 0
rfc          = 0
unShareable = 0
mightBeShared = 0
sharedWithShmTab = 0
isShmLockId = 0
gcKind       = 0
isUsed       = 1
>>>>> Shareable Table Header Data <<<<<
tabi         = Not allocated
pghook       = Not allocated
idxPtr       = Not allocated
refCount     = Not allocated
tstRefCount = Not allocated
lineAdmin    = Not allocated
lineAlloc    = Not allocated
store_id     = Not allocated
shmIsReadOnly = Not allocated
>>>>> 1st level extension part <<<<<
regHook      = Not allocated
hsdir        = Not allocated
ext2         = Not allocated
>>>>> 2nd level extension part <<<<<
tabhBack     = Not allocated
delta_head   = Not allocated
pb_func      = Not allocated
pb_handle    = Not allocated
IT_MODE
Table IT_275[1x164]
PROGRAM=/SAPAPO/OM_TB_FLOW_QUANTITYFORM=CHANGE_DATADATA=LT_MODES
Table reference: 52
TABH+ 0(20) = A03C00E000000000000000003400000013010000
TABH+ 20(20) = 01000000A4000000FFFFFFFF0487000060290000
TABH+ 40( 8) = 10000000C1308000
store        = 0xA03C00E0
ext1         = 0x00000000
shmId        = 0     (0x00000000)
id           = 52    (0x34000000)
label        = 275   (0x13010000)
fill         = 1     (0x01000000)
leng         = 164   (0xA4000000)
loop         = -1    (0xFFFFFFFF)
xtyp         = TYPE#000207
occu         = 16    (0x10000000)
access       = 1     (ItAccessStandard)
idxKind      = 0     (ItIndexNone)
uniKind      = 2     (ItUniqueNon)
keyKind      = 1     (default)
cmpMode      = 8     (cmpManyEq)
occu0        = 1
collHash     = 0
groupCntl    = 0
rfc          = 0
unShareable = 0
mightBeShared = 0
sharedWithShmTab = 0
isShmLockId = 0
gcKind       = 0
isUsed       = 1
>>>>> Shareable Table Header Data <<<<<
tabi         = 0xC8F611E0
pghook       = 0x00000000
idxPtr       = 0x00000000
refCount     = 0     (0x00000000)
tstRefCount = 0     (0x00000000)
lineAdmin    = 16    (0x10000000)
lineAlloc    = 16    (0x10000000)
store_id     = 125   (0x7D000000)
shmIsReadOnly = 0     (0x00000000)
>>>>> 1st level extension part <<<<<
regHook      = Not allocated
hsdir        = Not allocated
ext2         = Not allocated
>>>>> 2nd level extension part <<<<<
tabhBack     = Not allocated
delta_head   = Not allocated
pb_func      = Not allocated
pb_handle    = Not allocated
IT_ORDERS
Table IT_293[1x320]
PROGRAM=/SAPAPO/OM_TB_FLOW_QUANTITYFORM=CHANGE_DATADATA=LT_ORDERS1
Table reference: 47
TABH+ 0(20) = 20B403E000000000000000002F00000025010000
TABH+ 20(20) = 0100000040010000FFFFFFFF0400000030380000
TABH+ 40( 8) = 01000000C1308000
store        = 0x20B403E0
ext1         = 0x00000000
shmId        = 0     (0x00000000)
id           = 47    (0x2F000000)
label        = 293   (0x25010000)
fill         = 1     (0x01000000)
leng         = 320   (0x40010000)
loop         = -1    (0xFFFFFFFF)
xtyp         = TYPE#000286
occu         = 1     (0x01000000)
access       = 1     (ItAccessStandard)
idxKind      = 0     (ItIndexNone)
uniKind      = 2     (ItUniqueNon)
keyKind      = 1     (default)
cmpMode      = 8     (cmpManyEq)
occu0        = 1
collHash     = 0
groupCntl    = 0
rfc          = 0
unShareable = 0
mightBeShared = 0
sharedWithShmTab = 0
isShmLockId = 0
gcKind       = 0
isUsed       = 1
>>>>> Shareable Table Header Data <<<<<
tabi         = 0x9080FFDF
pghook       = 0x00000000
idxPtr       = 0x00000000
refCount     = 0     (0x00000000)
tstRefCount = 0     (0x00000000)
lineAdmin    = 1     (0x01000000)
lineAlloc    = 1     (0x01000000)
store_id     = 130   (0x82000000)
shmIsReadOnly = 0     (0x00000000)
>>>>> 1st level extension part <<<<<
regHook      = Not allocated
hsdir        = Not allocated
ext2         = Not allocated
>>>>> 2nd level extension part <<<<<
tabhBack     = Not allocated
delta_head   = Not allocated
pb_func      = Not allocated
pb_handle    = Not allocated
IT_ORDER_METHOD
Table IT_268[2x62]
PROGRAM=/SAPAPO/OM_TB_FLOW_QUANTITYFORM=CHANGE_DATADATA=LT_ORDER_METHOD
Table reference: 51
TABH+ 0(20) = 8882FFDF0000000000000000330000000C010000
TABH+ 20(20) = 020000003E000000FFFFFFFF04000000B0360000
TABH+ 40( 8) = 10000000C1248000
store        = 0x8882FFDF
ext1         = 0x00000000
shmId        = 0     (0x00000000)
id           = 51    (0x33000000)
label        = 268   (0x0C010000)
fill         = 2     (0x02000000)
leng         = 62    (0x3E000000)
loop         = -1    (0xFFFFFFFF)
xtyp         = TYPE#000278
occu         = 16    (0x10000000)
access       = 1     (ItAccessStandard)
idxKind      = 0     (ItIndexNone)
uniKind      = 2     (ItUniqueNon)
keyKind      = 1     (default)
cmpMode      = 2     (cmpSingleMcmpR)
occu0        = 1
collHash     = 0
groupCntl    = 0
rfc          = 0
unShareable = 0
mightBeShared = 0
sharedWithShmTab = 0
isShmLockId = 0
gcKind       = 0
isUsed       = 1
>>>>> Shareable Table Header Data <<<<<
tabi         = 0x0868FFDF
pghook       = 0x00000000
idxPtr       = 0x00000000
refCount     = 0     (0x00000000)
tstRefCount = 0     (0x00000000)
lineAdmin    = 16    (0x10000000)
lineAlloc    = 16    (0x10000000)
store_id     = 122   (0x7A000000)
shmIsReadOnly = 0     (0x00000000)
>>>>> 1st level extension part <<<<<
regHook      = Not allocated
hsdir        = Not allocated
ext2         = Not allocated
>>>>> 2nd level extension part <<<<<
tabhBack     = Not allocated
delta_head   = Not allocated
pb_func      = Not allocated
pb_handle    = Not allocated
IT_ORDKEYS
Table IT_271[1x332]
PROGRAM=/SAPAPO/OM_TB_FLOW_QUANTITYFORM=CHANGE_DATADATA=LT_ORDKEYS
Table reference: 29
TABH+ 0(20) = 80E303E000000000000000001D0000000F010000
TABH+ 20(20) = 010000004C010000FFFFFFFF04870000E0270000
TABH+ 40( 8) = 10000000C1308000
store        = 0x80E303E0
ext1         = 0x00000000
shmId        = 0     (0x00000000)
id           = 29    (0x1D000000)
label        = 271   (0x0F010000)
fill         = 1     (0x01000000)
leng         = 332   (0x4C010000)
loop         = -1    (0xFFFFFFFF)
xtyp         = TYPE#000199
occu         = 16    (0x10000000)
access       = 1     (ItAccessStandard)
idxKind      = 0     (ItIndexNone)
uniKind      = 2     (ItUniqueNon)
keyKind      = 1     (default)
cmpMode      = 8     (cmpManyEq)
occu0        = 1
collHash     = 0
groupCntl    = 0
rfc          = 0
unShareable = 0
mightBeShared = 0
sharedWithShmTab = 0

Hi,
the error DbpError -28814 denotes that an object cannot be found.
Can you maybe tell me your exact liveCache version (incl. Build level) and LCA Build?
Additionally, please copy the relevant error information from the file (/sapdb/data/wrk/<SID>/)knldiag.err into this thread.
Which exact 'liveCache test program' are your referring to (which of the /SAPAPO/... transactions)?
Kind regards,
Roland

"Memory Sizing" error on Sun Fire V65x

Hello.
I have some trouble with my old Sun Fire V65x and i hope that you guys can help me out.
I had 2,5GB RAM installed in my server, working flawless. 2 x 256MB and 2 x 1GB modules. 256-modules in Bank 1 and 1GB´s in Bank 2.
To get rid of the boot up warning of wrong memory configuration i moved the 2 1GB modules to bank 3 (as stated in the manual) but that was when the problem started.
In this configuration the server won't go to POST, i tried moving the 1GB modules around between bank 1, 2 & 3 without any result.
The server will not go to POST. No beeps, no nothing. When turning the server on line it starts up, the fans starts running on at maximum speed and that's all, no picture and no POST and the system warning LED turns to red. After a couple of minutes in this state the fans slow down for a couple of seconds and then back to 100% (repeating cycle)
The POST diagnostics LEDs at the back of the main board indicates POST code 13h, "Memory sizing". The main board does not report any defective DIMMs, also worth mentioning is that the 2 256MB DIMMs are working flawlessly in all banks.
I have tried:
Resetting the memory config in BIOS (using the 2x256 DIMMs and then installing the 2 1GB modules.
Moving the memory modules around between different banks, both alone and with the 2 256MB DIMMs present.
Clearing the CMOS settings.
Searching manuals and Google for hours without answer to my problem or what "memory sizing " means in this situation.
System:
Sun Fire V65x
1 CPU
If anyone know the answer to my dilemma and are willing to help me, i would be really grateful.
Sadly i do not have the possibility to test the memory modules in another system.
Best regards. Erik Järlestrand, Sweden.

Hardware. A reboot will probably not do anything. From what I can tell, it's a CPU cache problem. If you do anything, shut the system down completely, turn the power off for a minimum of 20 seconds to let any residual electricty go away, the turn it back on. If the problem returns, you'll most likely need to either get a new CPU module or a new V100. I don't know if the CPU can be removed from the V100 motherboard, but since there are jumper settings for the speed I would assume that you can.

I publish a 41mb newsletter monthly into interactive pdf. It always becomes a file size of 4mb, 10% of original, when I save to pdf. This month my newsletter is 41mb and it drops to 11mb, 25% of original. I have re-sized all pictures, deleted pages separa

I publish a 41mb InDesign newsletter monthly into interactive pdf. It always becomes a file size of 4mb, 10% of original, when I save to pdf. This month my newsletter is 41mb and it drops to 11mb, 25% of original. I have re-sized all pictures, deleted pages separately, have gotten the file size down to 16mb and it drops to 7mb, 45% of original.
I have gone back and saved Feb and March and it saves to 10% of original, as it did before, and I use the same mechanism to save now.
I have gone to Acrobat Pro and optimized down to 8.8mb, but the quality is not acceptable.
What other variable is there that I haven't discovered?

My daughter has had her Razr for about 9 months now. About two weeks ago she picked up her phone in the morning on her way to school when she noticed two cracks, both starting at the camera lens. One goes completely to the bottom and the other goes sharply to the side. She has never dropped it and me and my husband went over it with a fine tooth comb. We looked under a magnifying glass and could no find any reason for the glass to crack. Not one ding, scratch or bang. Our daughter really takes good care of her stuff, but we still wanted to make sure before we sent it in for repairs. Well we did and we got a reply from Motorola with a picture of the cracks saying this was customer abuse and that it is not covered under warranty. Even though they did not find any physical damage to back it up. Well I e-mailed them back and told them I did a little research and found pages of people having the same problems. Well I did not hear from them until I received a notice from Fed Ex that they were sending the phone back. NOT FIXED!!! I went to look up why and guess what there is no case open any more for the phone. It has been wiped clean. I put in the RMA # it comes back not found, I put in the ID #, the SN# and all comes back not found. Yet a day earlier all the info was there. I know there is a lot more people like me and all of you, but they just don't want to be bothered so they pay to have it fix, just to have it do it again. Unless they have found the problem and only fixing it on a customer pay only set up. I am furious and will not be recommending this phone to anyone. And to think I was considering this phone for my next up grade! NOT!!!!

Problem with JPanel sizing!

Hi,
Just having a bit of difficulty with the sizing of JPanels. For example, if I create a JPanel and add it to a Frame, no matter what I set the size to the JPanel fills the entire Frame. I don't really know whats going on here and I'm just making guesses! If anyone has a good resource on the whole sizing thing or can point out what I'm doing wrong, that would be great. Thanks!
// Constructor
public void ClassName()
        mainWindow = new JFrame();
        mainWindow.setSize(mainWindowWidth, mainWindowHeight);
        mainWindow.setDefaultCloseOperation(JFrame.EXIT_ON_CLOSE);
        JPanel aPanel = new JPanel();
        aPanel.setSize(mainWindowWidth/2,mainWindowHeight/2); );
        aPanel.setBackground(Color.GREEN);
        mainWindow.add(aPanel);
        mainWindow.validate();
}Edited by: LeWalrus on May 18, 2009 5:03 AM

By default, JFrame uses a BorderLayout which gives the center component (your panel in this case) all available height and width.
For absolute positioning you need to use a null layout.
If you want a layout manager that can let your panel fill half the height/width, I think it might be possible with GridBagLayout or more recommended MiGLayout (but that adds a third party jar dependency).
See the [layout tutorial|http://java.sun.com/docs/books/tutorial/uiswing/layout/index.html].

Problem with Photos and Camera and Sizing Set

I have a 3gs and upgraded to 4.0. Things seemed fine but yesterday when I opened up the Camera Roll in Photos there was 1 picture showing and a large black rectangular box. No other photos were showing. I tapped on the black box and it showed all the photos using the slider to go from 1 to the next. I couldn't figure out how to get rid of the black box so that all the photos showed up normally, so I deleted each of the photos. The size of the box shrank as each photo was deleted. Then when I went into Photos, it opened with an empty screen and immediately closed. I then tried to use the Camera and it started up and immediately closed. So I sent myself an email with a photo and saved it to Photos. Its there and so is the black box! Now the camera will work! To further complicate, I decided I'd use the photo for wallpaper. Problem is I can't size it!! I can move it and size it with my fingers, but then when I release, it immediately pops back to full size and I can't "Set" the image size. Does anyone have any idea what's going on!!

Well I solved it. I uploaded my photos to My Gallery. Then I took a photo with the camera and saved it. I then deleted all the other photos except the one I just took. Then I exited Photos and then came back in and it was working fine, so I then downloaded the photos that I had just uploaded to My Gallery. Still have a problem though with sizing the photos for the Lock and Home screens. I can't get the Set button to hold a size. Any ideas on that?

LiveCache sizing

Similar Messages

Maybe you are looking for