Physical Vs Logical Partitioning
We have 2 million records in the sales infocube for 3 years. We are currently discussing the pros and cons of using Logical partitioning Vs Physical Partitioning. Please give your inputs.
hi
there are two types of partitioning generally talked about with SAP BW, logical and physical partitioning.
Logical partitioning - instead of having all your data in a single cube, you might break into separate cubes, with each cube holding aspecific year's data, e.g. you could have 5 sales cubes, one for each year 2001 thru 2005.
You would then create a Multi-Provider that allowed you to query all of them together.
A query that needs data from all 5 years would then automatically (you can control this) be split into 5 separate queries, one against each cube, running at the same time. The system automatically merges the results from the 5 queries into a single result set.
So it's easy to see when this could be a benefit. If your queries however are primarily run just for a single year, then you don't receive the benefit of the parallel processing. In non-Oracle DBs, splitting the data like this may still be a benefit by reducing the amount of rows in the fact table that must be read, but does not provide as much value to an Oracle DB since Infocube queries are using a Star_Transformation.
Physical Partitioning - I believe only Oracle and Informix currently support Range partitioning. This is a separately licensed option in Oracle.
Physical partitioning allows you to split an Infocube into smaller pieces. The pieces, or partitions, can only be created by 0FISCPER or 0CALMONTH for an InfoCube (ODSs can be partitioned, but require a DBAs involvement). The DB can then take advantage of this partitioning by "pruning" partitions during a query, e.g. a query only needs data form June 2005
The DB is smart enough to restrict the indices and data it will read to the June 2005 partition. This assumes your query restricts/filters on the partitioning characteristic. It can apply this pruning to a range of partitions as well, e.g. 0FISCPER 001/2005 thru 003/2005 would only look at the 3 partitions.
It is NOTsmart enough, however, to figure out that if your restrict to 0FISCYEAR = 2005, that it should only read 000/2005 thru 016/2005 since 0FISCYEAR is NOT the partitioning characteristic.
An InfoCube MUST be empty in order to physically partition it. At this time, there is no way to add additional partitions thru AWB, so you want to make sure that you create partitions out into the future for at least a of couple of years.
If the base cube is partitioned, any aggregates that contain the partitioning characteristic (0CALMONTH or 0FISCPER) will automatically be partitioned.
In summary, you need to figure out if you want to use physical or logical partitioning on the cube(s), or both, as they are not mutually exclusive.
So you would need to know how the data will be queried, and the volume of data. It would make little sense to partition cubes that will not be very large.
physical partitioning is done at database level and logical partitioning done at data target level.
Cube partitioning with time characteristics 0calmonth Fiscper is physical partitioning.
Logical partitioning is u partition ur cube by year or month that is u divide the cube into different cubes and create a multiprovider on top of it.
logical Vs physical partitions ?
Similar Messages
-
Merge physical and logical partitions
How do I extend my physical arch partition with an unallocated space logical partition?
I want to add an unallocated space logical partition to a physical partition
or better said I want to grow my existing arch physical partition with the unallocated space logical partition.
Last edited by karlzt (2010-03-20 15:50:31)It is not that easy. You can resize and/or move either physical partitions or locical partitions inside the space of the (physical) "extended partition". But you cannot simply take space from a logical partion and assign it to a physical partition adjacent to the extended partition it is part of. Which means you can extend a physical partion only from free space which you can produce by a prior shrinking/moving another adjacent physical partition.
The problem is, I currently know of no way to shrink an extended partition without losing some of the enclosed logical partition data (or even all logical partions at once). One could try, as a proper backup is advisable in any case before messing around with partitions. -
0IC_C03 related Inventory Process - Logical Partitioning (Vs) Physical Part
Hello Everyone,
After going through multiple postings throughout the form and documentation from SAP, it states that the 0IC_C03 InfoCube when used with Non Cumulative keyfigures is not recommended to be partitioned logically by physical year/calendar year as the query will read all the data sets due to the stock marker logic.
In our specific scenario,
1. After the InfoCube (0IC_C03) was enhanced with additional characterisitcs such as Doc Number, Movement type and so on due to business requirements I was not able to actually use the Non Cumulative Keyfigures as they were not populated within the report.
2. So, we decided not to use the Non Cumulative keyfigures but rather create two cumulative keyfigures (Issue Stock Quantity - Receipt Stock Quantity) and (Issue Valuated Stock Value - Receipt Valuated Stock Value) and both of these are available in the InfoCube and are calculated during the update process.
These two keyfigures are cumulative with exception aggregation of LAST based on 0CALDAY.
The question is,
Since we are not using the actual Non Cumulative Keyfigures (even though we are not using these, we still have the stock marker updated and data compressed based on this along with Validity table defined) can we do logical partitioning on the InfoCube based on Calendar year.
Thanks....Hello Elango,
Appreciate your response.
First of..I do understand the difference between logical and physical partitioning and the question is not about joining them together.
I am sorry, if others cannot understand the detailed issue posted. My apologies was a part of polite gesture, and please do respond back with proper precise answer if you think you did actually understand the question....
The question here is about how I can leverage the performance and administrative performance by logically breakingdown the data.
The issues due to which I am trying to look into different aspects of logical partitioning are:
1. If I do logical partitioning by Plant due to the stock marker logic then I cannot do archiving as a Plant and its related data cannot be archived by time characteristic as the partitioning is not done by time characteristic.
2. The reason I would have to have document number and movement type in the InfoCube is due to the kind of reporting users perform.
We have a third party system whose data needs to be reconciled to the data in the plants and storage locations.
And in order to do so, the first step users would be running the report is plant, storage location and sku. From here on for the storage locations which have balance they would like to drill down on to the document number and movement type to see what the actual activity is.
So, to support this requirement I would have to have the above characterisitcs in the InfoCube.
The question again is,.....what is the exact list of issues I would be having doing the logical partitioning by time characteristic.
Once again, even though the non cumulative keyfigures are available in the InfoCube we are not using them for any reporting purpose....so please keep that in consideration while replying back.
Thanks
Dharma. -
Cannot create another 2 logical partitions on another physical server
when i installed the BI 7.0 on AIX/DB2 9 platform. i can create 2 logical partition on the main server , yet i couldn't create another 2 logical parttions on the second server. the following is the error message
INFO 2008-02-21 03:49:03.490
"sapinst_dev.log" [Read only] 20411 lines, 744293 characters
TRACE 2008-02-21 03:51:28.513 [iaxxejsexp.cpp:199]
EJS_Installer::writeTraceToLogBook()
Found Error, error_codes[1] = <db2start dbpartitionnum 5 add dbpartitionnum hostname sapaix08 port 3 without tablespaces
SQL6073N Add Node operation failed. SQLCODE = "-1051".>
TRACE 2008-02-21 03:51:28.513 [iaxxejsexp.cpp:199]
EJS_Installer::writeTraceToLogBook()
During execution of <AddPart.sql>, <2> errors occured.
ERROR 2008-02-21 03:51:28.513 [iaxxinscbk.cpp:282]
abortInstallation
MDB-01999 Error occured, first error is: <SQL6073N Add Node operation failed. SQLCODE = "-1051".>
TRACE 2008-02-21 03:51:28.514 [iaxxejsbas.hpp:388]
handleException<ESAPinstException>()
Converting exception into JS Exception Exception.
ERROR 2008-02-21 03:51:28.515
CJSlibModule::writeError_impl()
MUT-03025 Caught ESAPinstException in Modulecall: ESAPinstException: error text undefined.
TRACE 2008-02-21 03:51:28.515 [iaxxejsbas.hpp:460]
EJS_Base::dispatchFunctionCall()
JS Callback has thrown unknown exception. Rethrowing.
ERROR 2008-02-21 03:51:28.516 [iaxxgenimp.cpp:731]
showDialog()
FCO-00011 The step AddDB6Partitions with step key |NW_DB6_DB_ADDPART|ind|ind|ind|ind|0|0|NW_DB6_AddPartitions|ind|ind|ind|ind|12|0|
AddDB6Partitions was executed with status ERROR .
TRACE 2008-02-21 03:51:28.539 [iaxxgenimp.cpp:719]
showDialog()
the following is my prerequisite for the installation
1. the user and group id and property is the same as the primary (server1)
2. the ssh trust relationship has built , i can ssh server1 from server2 or server2 from server1 with db2sid, sidadm users
3. i mount the /db2/db2sid , /db2/SID/db2dumps, /sapmnt/SID/exe on server2 as NFS
4. install the db2 software on /opt/IBM/db2/V9.1 (the location is the same as the primary's)
HI , DB2 experts. Could you give me some suggestion? thanks!Hi,Thomas,
Thanks for your help. the db2 database desn't use the autostoarge method and the relevant permission is the same as server1. i checked the db2dialog.log. the following is the detail information
"Storage path does not exist or is inaccessible" is the error message . i was wondering which storage path does not exit or inaccessible .
at the same time i have login on all /db2 with db2sid and run touch to test the permision . it sounds good. I don't know what happens , could you give me some suggestion ? thanks!
2008-02-21-08.10.56.442000-300 I14165596A287 LEVEL: Event
PID : 843832 TID : 1 PROC : db2stop2
INSTANCE: db2ab7 NODE : 005
FUNCTION: DB2 UDB, base sys utilities, DB2StopMain, probe:240
DATA #1 : String, 26 bytes
Stop phase is in progress.
2008-02-21-08.10.56.444783-300 I14165884A302 LEVEL: Event
PID : 843832 TID : 1 PROC : db2stop2
INSTANCE: db2ab7 NODE : 005
FUNCTION: DB2 UDB, base sys utilities, DB2StopMain, probe:250
DATA #1 : String, 41 bytes
Requesting system controller termination.
2008-02-21-08.10.56.450366-300 I14166187A403 LEVEL: Warning
PID : 712906 TID : 1 PROC : db2sysc 5
INSTANCE: db2ab7 NODE : 005
FUNCTION: DB2 UDB, routine_infrastructure, sqlerKillAllFmps, probe:5
MESSAGE : Bringing down all db2fmp processes as part of db2stop
DATA #1 : Hexdump, 4 bytes
0x0FFFFFFFFFFFE400 : 0000 0000 ....
2008-02-21-08.10.56.456345-300 I14166591A304 LEVEL: Event
PID : 843832 TID : 1 PROC : db2stop2
INSTANCE: db2ab7 NODE : 005
FUNCTION: DB2 UDB, base sys utilities, DB2StopMain, probe:260
DATA #1 : String, 43 bytes
System controller termination is completed.
2008-02-21-08.10.56.461462-300 I14166896A381 LEVEL: Event
PID : 843832 TID : 1 PROC : db2stop2
INSTANCE: db2ab7 NODE : 005
FUNCTION: DB2 UDB, base sys utilities, DB2StopMain, probe:280
DATA #1 : String, 24 bytes
There is no active EDUs.
DATA #2 : Hexdump, 4 bytes
0x0FFFFFFFFFFFCEE0 : 0000 0000 ....
2008-02-21-08.10.56.504322-300 I14167278A342 LEVEL: Severe
PID : 823374 TID : 1 PROC : db2acd 5
INSTANCE: db2ab7 NODE : 005
FUNCTION: DB2 UDB, routine_infrastructure, sqlerFmpOneTimeInit, probe:100
DATA #1 : Hexdump, 4 bytes
0x0FFFFFFFFFFFF5A4 : FFFF FBEE ....
2008-02-21-08.10.56.654959-300 E14167621A301 LEVEL: Event
PID : 843832 TID : 1 PROC : db2stop2
INSTANCE: db2ab7 NODE : 005
FUNCTION: DB2 UDB, base sys utilities, DB2StopMain, probe:911
MESSAGE : ADM7514W Database manager has stopped.
STOP : DB2 DBM
2008-02-21-08.11.09.664000-300 I14167923A417 LEVEL: Event
PID : 639410 TID : 1 PROC : db2stop
INSTANCE: db2ab7 NODE : 000
FUNCTION: DB2 UDB, base sys utilities, sqleIssueStartStop, probe:1100
DATA #1 : String, 53 bytes
/db2/db2ab7/sqllib/adm/db2rstop db2profile FORCE1 0 0
DATA #2 : Hexdump, 4 bytes
0x0FFFFFFFFFFF9CBC : 0000 0022 ..."
2008-02-21-08.11.10.176098-300 I14168341A417 LEVEL: Event
PID : 639410 TID : 1 PROC : db2stop
INSTANCE: db2ab7 NODE : 000
FUNCTION: DB2 UDB, base sys utilities, sqleIssueStartStop, probe:1100
DATA #1 : String, 53 bytes
/db2/db2ab7/sqllib/adm/db2rstop db2profile FORCE1 1 1
DATA #2 : Hexdump, 4 bytes
0x0FFFFFFFFFFF9CBC : 0000 0022 ..."
2008-02-21-08.11.10.595702-300 I14168759A417 LEVEL: Event
PID : 639410 TID : 1 PROC : db2stop
INSTANCE: db2ab7 NODE : 000
FUNCTION: DB2 UDB, base sys utilities, sqleIssueStartStop, probe:1100
DATA #1 : String, 53 bytes
/db2/db2ab7/sqllib/adm/db2rstop db2profile FORCE1 2 0
DATA #2 : Hexdump, 4 bytes
0x0FFFFFFFFFFF9CBC : 0000 0022 ..."
2008-02-21-08.11.11.124888-300 I14169177A417 LEVEL: Event
PID : 639410 TID : 1 PROC : db2stop
INSTANCE: db2ab7 NODE : 000
FUNCTION: DB2 UDB, base sys utilities, sqleIssueStartStop, probe:1100
DATA #1 : String, 53 bytes
/db2/db2ab7/sqllib/adm/db2rstop db2profile FORCE1 3 1
DATA #2 : Hexdump, 4 bytes
0x0FFFFFFFFFFF9CBC : 0000 0022 ..."
2008-02-21-08.11.12.070605-300 I14169595A410 LEVEL: Event
PID : 639410 TID : 1 PROC : db2stop
INSTANCE: db2ab7 NODE : 000
FUNCTION: DB2 UDB, base sys utilities, sqleIssueStartStop, probe:1100
DATA #1 : String, 46 bytes
/db2/db2ab7/sqllib/adm/db2rstop db2profile 0 0
DATA #2 : Hexdump, 4 bytes
0x0FFFFFFFFFFF9CBC : 0000 0020 ...
2008-02-21-08.11.12.694723-300 I14170006A410 LEVEL: Event
PID : 639410 TID : 1 PROC : db2stop
INSTANCE: db2ab7 NODE : 000
FUNCTION: DB2 UDB, base sys utilities, sqleIssueStartStop, probe:1100
DATA #1 : String, 46 bytes
/db2/db2ab7/sqllib/adm/db2rstop db2profile 1 1
DATA #2 : Hexdump, 4 bytes
0x0FFFFFFFFFFF9CBC : 0000 0020 ...
2008-02-21-08.11.13.115940-300 I14170417A410 LEVEL: Event
PID : 639410 TID : 1 PROC : db2stop
INSTANCE: db2ab7 NODE : 000
FUNCTION: DB2 UDB, base sys utilities, sqleIssueStartStop, probe:1100
DATA #1 : String, 46 bytes
/db2/db2ab7/sqllib/adm/db2rstop db2profile 2 0
DATA #2 : Hexdump, 4 bytes
0x0FFFFFFFFFFF9CBC : 0000 0020 ...
2008-02-21-08.11.13.632046-300 I14170828A410 LEVEL: Event
PID : 639410 TID : 1 PROC : db2stop
INSTANCE: db2ab7 NODE : 000
FUNCTION: DB2 UDB, base sys utilities, sqleIssueStartStop, probe:1100
DATA #1 : String, 46 bytes
/db2/db2ab7/sqllib/adm/db2rstop db2profile 3 1
DATA #2 : Hexdump, 4 bytes
0x0FFFFFFFFFFF9CBC : 0000 0020 ...
2008-02-21-08.11.14.577056-300 I14171239A418 LEVEL: Event
PID : 639410 TID : 1 PROC : db2stop
INSTANCE: db2ab7 NODE : 000
FUNCTION: DB2 UDB, base sys utilities, sqleIssueStartStop, probe:1100
DATA #1 : String, 54 bytes
/db2/db2ab7/sqllib/adm/db2rstop db2profile NODEACT 0 0
DATA #2 : Hexdump, 4 bytes
0x0FFFFFFFFFFF9CBC : 0000 0024 ...$
2008-02-21-08.11.15.004794-300 I14171658A418 LEVEL: Event
PID : 639410 TID : 1 PROC : db2stop
INSTANCE: db2ab7 NODE : 000
FUNCTION: DB2 UDB, base sys utilities, sqleIssueStartStop, probe:1100
DATA #1 : String, 54 bytes
/db2/db2ab7/sqllib/adm/db2rstop db2profile NODEACT 1 1
DATA #2 : Hexdump, 4 bytes
0x0FFFFFFFFFFF9CBC : 0000 0024 ...$
2008-02-21-08.11.15.425920-300 I14172077A418 LEVEL: Event
PID : 639410 TID : 1 PROC : db2stop
INSTANCE: db2ab7 NODE : 000
FUNCTION: DB2 UDB, base sys utilities, sqleIssueStartStop, probe:1100
DATA #1 : String, 54 bytes
/db2/db2ab7/sqllib/adm/db2rstop db2profile NODEACT 2 0
DATA #2 : Hexdump, 4 bytes
0x0FFFFFFFFFFF9CBC : 0000 0024 ...$
2008-02-21-08.11.15.941622-300 I14172496A418 LEVEL: Event
PID : 639410 TID : 1 PROC : db2stop
INSTANCE: db2ab7 NODE : 000
FUNCTION: DB2 UDB, base sys utilities, sqleIssueStartStop, probe:1100
DATA #1 : String, 54 bytes
/db2/db2ab7/sqllib/adm/db2rstop db2profile NODEACT 3 1
DATA #2 : Hexdump, 4 bytes
0x0FFFFFFFFFFF9CBC : 0000 0024 ...$
2008-02-21-08.11.17.002107-300 I14172915A422 LEVEL: Event
PID : 639412 TID : 1 PROC : db2start
INSTANCE: db2ab7 NODE : 000
FUNCTION: DB2 UDB, base sys utilities, sqleIssueStartStop, probe:1100
DATA #1 : String, 57 bytes
/db2/db2ab7/sqllib/adm/db2rstar db2profile SN ADDNODE 4 2
DATA #2 : Hexdump, 4 bytes
0x0FFFFFFFFFFF9C2C : 0000 0011 ....
2008-02-21-08.11.18.055723-300 E14173338A856 LEVEL: Warning
PID : 806940 TID : 1 PROC : db2star2
INSTANCE: db2ab7 NODE : 004
FUNCTION: DB2 UDB, license manager, sqllcRequestAccess, probe:1
MESSAGE : ADM12007E There are "80" day(s) left in the evaluation period for
the product "DB2 Enterprise Server Edition". For evaluation license
terms and conditions, refer to the IBM License Acceptance and License
Information document located in the license directory in the
installation path of this product. If you have licensed this product,
ensure the license key is properly registered. You can register the
license via the License Center or db2licm command line utility. The
license file can be obtained from your licensed product CD.
2008-02-21-08.11.18.296453-300 E14174195A1040 LEVEL: Event
PID : 806940 TID : 1 PROC : db2star2
INSTANCE: db2ab7 NODE : 004
FUNCTION: DB2 UDB, base sys utilities, DB2StartMain, probe:911
MESSAGE : ADM7513W Database manager has started.
START : DB2 DBM
DATA #1 : Build Level, 152 bytes
Instance "db2ab7" uses "64" bits and DB2 code release "SQL09012"
with level identifier "01030107".
Informational tokens are "DB2 v9.1.0.2", "special_17253", "U810940_17253", Fix Pack "2".
DATA #2 : System Info, 224 bytes
System: AIX sapaix08 3 5 00CCD7FE4C00
CPU: total:8 online:8 Threading degree per core:2
Physical Memory(MB): total:7744 free:5866
Virtual Memory(MB): total:32832 free:30943
Swap Memory(MB): total:25088 free:25077
Kernel Params: msgMaxMessageSize:4194304 msgMaxQueueSize:4194304
shmMax:68719476736 shmMin:1 shmIDs:131072
shmSegments:68719476736 semIDs:131072 semNumPerID:65535
semOps:1024 semMaxVal:32767 semAdjustOnExit:16384
2008-02-21-08.11.19.312894-300 I14175236A428 LEVEL: Error
PID : 835728 TID : 1 PROC : db2agent (instance) 4
INSTANCE: db2ab7 NODE : 004
APPHDL : 4-7 APPID: *LOCAL.db2ab7.080221131118
FUNCTION: DB2 UDB, base sys utilities, sqleGetAutomaticStorageDetails, probe:111111
DATA #1 : <preformatted>
dataSize 752 pMemAlloc 1110cdac0 sizeof(struct sqleAutoStorageCfg) 16
2008-02-21-08.11.19.346560-300 I14175665A497 LEVEL: Error
PID : 835728 TID : 1 PROC : db2agent (instance) 4
INSTANCE: db2ab7 NODE : 004
APPHDL : 4-7 APPID: *LOCAL.db2ab7.080221131118
FUNCTION: DB2 UDB, buffer pool services, sqlbInitStorageGroupFiles, probe:50
MESSAGE : ZRC=0x800201A5=-2147352155=SQLB_AS_INVALID_STORAGE_PATH
"Storage path does not exist or is inaccessible."
DATA #1 : String, 17 bytes
/db2/AB7/sapdata1
2008-02-21-08.11.19.349637-300 I14176163A619 LEVEL: Severe
PID : 835728 TID : 1 PROC : db2agent (instance) 4
INSTANCE: db2ab7 NODE : 004
APPHDL : 4-7 APPID: *LOCAL.db2ab7.080221131118
FUNCTION: DB2 UDB, buffer pool services, sqlbInitStorageGroupFiles, probe:50
MESSAGE : ZRC=0x800201A5=-2147352155=SQLB_AS_INVALID_STORAGE_PATH
"Storage path does not exist or is inaccessible."
DATA #1 : String, 46 bytes
Error during storage group file initialization
DATA #2 : Pointer, 8 bytes
0x0ffffffffffed006
DATA #3 : Pointer, 8 bytes
0x00000001110b3080
2008-02-21-08.11.19.355029-300 I14176783A435 LEVEL: Error
PID : 835728 TID : 1 PROC : db2agent (instance) 4
INSTANCE: db2ab7 NODE : 004
APPHDL : 4-7 APPID: *LOCAL.db2ab7.080221131118
FUNCTION: DB2 UDB, base sys utilities, sqleStartDb, probe:5
RETCODE : ZRC=0x800201A5=-2147352155=SQLB_AS_INVALID_STORAGE_PATH
"Storage path does not exist or is inaccessible."
2008-02-21-08.11.19.357831-300 I14177219A370 LEVEL: Warning
PID : 835728 TID : 1 PROC : db2agent (instance) 4
INSTANCE: db2ab7 NODE : 004
APPHDL : 4-7 APPID: *LOCAL.db2ab7.080221131118
FUNCTION: DB2 UDB, base sys utilities, sqle_remap_errors, probe:100
MESSAGE : ZRC 0x800201a5 remapped to SQLCODE -1051
2008-02-21-08.11.19.374857-300 I14177590A336 LEVEL: Severe
PID : 803022 TID : 1 PROC : db2sysc 4
INSTANCE: db2ab7 NODE : 004
FUNCTION: DB2 UDB, base sys utilities, sqleSysCtrlAddNode, probe:6
MESSAGE : ADD NODE failed with SQLCODE -1051 MESSAGE TOKEN /db2/AB7/sapdata1 in module SQLECRED
2008-02-21-08.11.19.381604-300 I14177927A440 LEVEL: Event
PID : 639412 TID : 1 PROC : db2start
INSTANCE: db2ab7 NODE : 000
FUNCTION: DB2 UDB, base sys utilities, sqleIssueStartStop, probe:1100
DATA #1 : String, 75 bytes
DB2NODE=4 DB2LPORT=2 /db2/db2ab7/sqllib/adm/db2rstop db2profile NODEACT 4 2
DATA #2 : Hexdump, 4 bytes
0x0FFFFFFFFFFF9C2C : 0000 0024 ...$
2008-02-21-08.11.20.255191-300 I14178368A287 LEVEL: Event
PID : 700804 TID : 1 PROC : db2stop2
INSTANCE: db2ab7 NODE : 004
FUNCTION: DB2 UDB, base sys utilities, DB2StopMain, probe:240
DATA #1 : String, 26 bytes
Stop phase is in progress.
2008-02-21-08.11.20.258575-300 I14178656A302 LEVEL: Event
PID : 700804 TID : 1 PROC : db2stop2
INSTANCE: db2ab7 NODE : 004
FUNCTION: DB2 UDB, base sys utilities, DB2StopMain, probe:250
DATA #1 : String, 41 bytes
Requesting system controller termination.
2008-02-21-08.11.20.265164-300 I14178959A403 LEVEL: Warning
PID : 803022 TID : 1 PROC : db2sysc 4
INSTANCE: db2ab7 NODE : 004
FUNCTION: DB2 UDB, routine_infrastructure, sqlerKillAllFmps, probe:5
MESSAGE : Bringing down all db2fmp processes as part of db2stop
DATA #1 : Hexdump, 4 bytes
0x0FFFFFFFFFFFE400 : 0000 0000 ....
2008-02-21-08.11.20.271570-300 I14179363A304 LEVEL: Event
PID : 700804 TID : 1 PROC : db2stop2
INSTANCE: db2ab7 NODE : 004
FUNCTION: DB2 UDB, base sys utilities, DB2StopMain, probe:260
DATA #1 : String, 43 bytes
System controller termination is completed.
2008-02-21-08.11.20.276550-300 I14179668A381 LEVEL: Event
PID : 700804 TID : 1 PROC : db2stop2
INSTANCE: db2ab7 NODE : 004
FUNCTION: DB2 UDB, base sys utilities, DB2StopMain, probe:280
DATA #1 : String, 24 bytes
There is no active EDUs.
DATA #2 : Hexdump, 4 bytes
0x0FFFFFFFFFFFCEE0 : 0000 0000 ....
2008-02-21-08.11.20.312260-300 I14180050A342 LEVEL: Severe
PID : 774176 TID : 1 PROC : db2acd 4
INSTANCE: db2ab7 NODE : 004
FUNCTION: DB2 UDB, routine_infrastructure, sqlerFmpOneTimeInit, probe:100
DATA #1 : Hexdump, 4 bytes
0x0FFFFFFFFFFFF5A4 : FFFF FBEE ....
2008-02-21-08.11.20.474332-300 E14180393A301 LEVEL: Event
PID : 700804 TID : 1 PROC : db2stop2
INSTANCE: db2ab7 NODE : 004
FUNCTION: DB2 UDB, base sys utilities, DB2StopMain, probe:911
MESSAGE : ADM7514W Database manager has stopped.
STOP : DB2 DBM
2008-02-21-08.11.20.600512-300 I14180695A422 LEVEL: Event
PID : 671870 TID : 1 PROC : db2start
INSTANCE: db2ab7 NODE : 000
FUNCTION: DB2 UDB, base sys utilities, sqleIssueStartStop, probe:1100
DATA #1 : String, 57 bytes
/db2/db2ab7/sqllib/adm/db2rstar db2profile SN ADDNODE 5 3
DATA #2 : Hexdump, 4 bytes
0x0FFFFFFFFFFF9C2C : 0000 0011 ....
2008-02-21-08.11.21.620771-300 E14181118A856 LEVEL: Warning
PID : 819454 TID : 1 PROC : db2star2
INSTANCE: db2ab7 NODE : 005
FUNCTION: DB2 UDB, license manager, sqllcRequestAccess, probe:1
MESSAGE : ADM12007E There are "80" day(s) left in the evaluation period for
the product "DB2 Enterprise Server Edition". For evaluation license
terms and conditions, refer to the IBM License Acceptance and License
Information document located in the license directory in the
installation path of this product. If you have licensed this product,
ensure the license key is properly registered. You can register the
license via the License Center or db2licm command line utility. The
license file can be obtained from your licensed product CD.
2008-02-21-08.11.21.839933-300 E14181975A1040 LEVEL: Event
PID : 819454 TID : 1 PROC : db2star2
INSTANCE: db2ab7 NODE : 005
FUNCTION: DB2 UDB, base sys utilities, DB2StartMain, probe:911
MESSAGE : ADM7513W Database manager has started.
START : DB2 DBM
DATA #1 : Build Level, 152 bytes
Instance "db2ab7" uses "64" bits and DB2 code release "SQL09012"
with level identifier "01030107".
Informational tokens are "DB2 v9.1.0.2", "special_17253", "U810940_17253", Fix Pack "2".
DATA #2 : System Info, 224 bytes
System: AIX sapaix08 3 5 00CCD7FE4C00
CPU: total:8 online:8 Threading degree per core:2
Physical Memory(MB): total:7744 free:5859
Virtual Memory(MB): total:32832 free:30936
Swap Memory(MB): total:25088 free:25077
Kernel Params: msgMaxMessageSize:4194304 msgMaxQueueSize:4194304
shmMax:68719476736 shmMin:1 shmIDs:131072
shmSegments:68719476736 semIDs:131072 semNumPerID:65535
semOps:1024 semMaxVal:32767 semAdjustOnExit:16384
2008-02-21-08.11.22.860106-300 I14183016A428 LEVEL: Error
PID : 37336 TID : 1 PROC : db2agent (instance) 5
INSTANCE: db2ab7 NODE : 005
APPHDL : 5-7 APPID: *LOCAL.db2ab7.080221131121
FUNCTION: DB2 UDB, base sys utilities, sqleGetAutomaticStorageDetails, probe:111111
DATA #1 : <preformatted>
dataSize 752 pMemAlloc 11099bac0 sizeof(struct sqleAutoStorageCfg) 16
2008-02-21-08.11.22.886670-300 I14183445A497 LEVEL: Error
PID : 37336 TID : 1 PROC : db2agent (instance) 5
INSTANCE: db2ab7 NODE : 005
APPHDL : 5-7 APPID: *LOCAL.db2ab7.080221131121
FUNCTION: DB2 UDB, buffer pool services, sqlbInitStorageGroupFiles, probe:50
MESSAGE : ZRC=0x800201A5=-2147352155=SQLB_AS_INVALID_STORAGE_PATH
"Storage path does not exist or is inaccessible."
DATA #1 : String, 17 bytes
/db2/AB7/sapdata1
2008-02-21-08.11.22.889226-300 I14183943A619 LEVEL: Severe
PID : 37336 TID : 1 PROC : db2agent (instance) 5
INSTANCE: db2ab7 NODE : 005
APPHDL : 5-7 APPID: *LOCAL.db2ab7.080221131121
FUNCTION: DB2 UDB, buffer pool services, sqlbInitStorageGroupFiles, probe:50
MESSAGE : ZRC=0x800201A5=-2147352155=SQLB_AS_INVALID_STORAGE_PATH
"Storage path does not exist or is inaccessible."
DATA #1 : String, 46 bytes
Error during storage group file initialization
DATA #2 : Pointer, 8 bytes
0x0ffffffffffed006
DATA #3 : Pointer, 8 bytes
0x0000000110981080
2008-02-21-08.11.22.894826-300 I14184563A435 LEVEL: Error
PID : 37336 TID : 1 PROC : db2agent (instance) 5
INSTANCE: db2ab7 NODE : 005
APPHDL : 5-7 APPID: *LOCAL.db2ab7.080221131121
FUNCTION: DB2 UDB, base sys utilities, sqleStartDb, probe:5
RETCODE : ZRC=0x800201A5=-2147352155=SQLB_AS_INVALID_STORAGE_PATH
"Storage path does not exist or is inaccessible."
2008-02-21-08.11.22.897320-300 I14184999A370 LEVEL: Warning
PID : 37336 TID : 1 PROC : db2agent (instance) 5
INSTANCE: db2ab7 NODE : 005
APPHDL : 5-7 APPID: *LOCAL.db2ab7.080221131121
FUNCTION: DB2 UDB, base sys utilities, sqle_remap_errors, probe:100
MESSAGE : ZRC 0x800201a5 remapped to SQLCODE -1051
2008-02-21-08.11.22.913142-300 I14185370A336 LEVEL: Severe
PID : 758092 TID : 1 PROC : db2sysc 5
INSTANCE: db2ab7 NODE : 005
FUNCTION: DB2 UDB, base sys utilities, sqleSysCtrlAddNode, probe:6
MESSAGE : ADD NODE failed with SQLCODE -1051 MESSAGE TOKEN /db2/AB7/sapdata1 in module SQLECRED
2008-02-21-08.11.22.918953-300 I14185707A440 LEVEL: Event
PID : 671870 TID : 1 PROC : db2start
INSTANCE: db2ab7 NODE : 000
FUNCTION: DB2 UDB, base sys utilities, sqleIssueStartStop, probe:1100
DATA #1 : String, 75 bytes
DB2NODE=5 DB2LPORT=3 /db2/db2ab7/sqllib/adm/db2rstop db2profile NODEACT 5 3
DATA #2 : Hexdump, 4 bytes
0x0FFFFFFFFFFF9C2C : 0000 0024 ...$
2008-02-21-08.11.23.793386-300 I14186148A287 LEVEL: Event
PID : 823654 TID : 1 PROC : db2stop2
INSTANCE: db2ab7 NODE : 005
FUNCTION: DB2 UDB, base sys utilities, DB2StopMain, probe:240
DATA #1 : String, 26 bytes
Stop phase is in progress.
2008-02-21-08.11.23.796267-300 I14186436A302 LEVEL: Event
PID : 823654 TID : 1 PROC : db2stop2
INSTANCE: db2ab7 NODE : 005
FUNCTION: DB2 UDB, base sys utilities, DB2StopMain, probe:250
DATA #1 : String, 41 bytes
Requesting system controller termination.
2008-02-21-08.11.23.802154-300 I14186739A403 LEVEL: Warning
PID : 758092 TID : 1 PROC : db2sysc 5
INSTANCE: db2ab7 NODE : 005
FUNCTION: DB2 UDB, routine_infrastructure, sqlerKillAllFmps, probe:5
MESSAGE : Bringing down all db2fmp processes as part of db2stop
DATA #1 : Hexdump, 4 bytes
0x0FFFFFFFFFFFE400 : 0000 0000 ....
2008-02-21-08.11.23.808100-300 I14187143A304 LEVEL: Event
PID : 823654 TID : 1 PROC : db2stop2
INSTANCE: db2ab7 NODE : 005
FUNCTION: DB2 UDB, base sys utilities, DB2StopMain, probe:260
DATA #1 : String, 43 bytes
System controller termination is completed.
2008-02-21-08.11.23.812951-300 I14187448A381 LEVEL: Event
PID : 823654 TID : 1 PROC : db2stop2
INSTANCE: db2ab7 NODE : 005
FUNCTION: DB2 UDB, base sys utilities, DB2StopMain, probe:280
DATA #1 : String, 24 bytes
There is no active EDUs.
DATA #2 : Hexdump, 4 bytes
0x0FFFFFFFFFFFCEE0 : 0000 0000 ....
2008-02-21-08.11.23.882148-300 I14187830A342 LEVEL: Severe
PID : 684418 TID : 1 PROC : db2acd 5
INSTANCE: db2ab7 NODE : 005
FUNCTION: DB2 UDB, routine_infrastructure, sqlerFmpOneTimeInit, probe:100
DATA #1 : Hexdump, 4 bytes
0x0FFFFFFFFFFFF5A4 : FFFF FBEE ....
2008-02-21-08.11.24.008936-300 E14188173A301 LEVEL: Event
PID : 823654 TID : 1 PROC : db2stop2
INSTANCE: db2ab7 NODE : 005
FUNCTION: DB2 UDB, base sys utilities, DB2StopMain, probe:911
MESSAGE : ADM7514W Database manager has stopped.
STOP : DB2 DBM
2008-02-21-08.41.01.094426-300 I14188475A371 LEVEL: Warning
PID : 741576 TID : 1 PROC : db2bp
INSTANCE: db2ab7 NODE : 002
FUNCTION: DB2 UDB, Connection Manager, sqleUCappImpConnect, probe:150
RETCODE : ZRC=0x8005006D=-2147155859=SQLE_CA_BUILT
"SQLCA has been built and saved in component specific control block."
2008-02-21-08.41.01.109657-300 I14188847A371 LEVEL: Warning
PID : 741576 TID : 1 PROC : db2bp
INSTANCE: db2ab7 NODE : 002
FUNCTION: DB2 UDB, Connection Manager, sqleUCappImpConnect, probe:150
RETCODE : ZRC=0x8005006D=-2147155859=SQLE_CA_BUILT
"SQLCA has been built and saved in component specific control block."
2008-02-21-08.41.01.115152-300 I14189219A371 LEVEL: Warning
PID : 741576 TID : 1 PROC : db2bp
INSTANCE: db2ab7 NODE : 002
FUNCTION: DB2 UDB, Connection Manager, sqleUCappImpConnect, probe:150
RETCODE : ZRC=0x8005006D=-2147155859=SQLE_CA_BUILT
"SQLCA has been built and saved in component specific control block." -
Any real reason for logical partitioning over physical?
Hi!
I have seen a number of scenarios where SAP BI (assuming BI 7.0 for the rest of the discussion), running in high volume scenarios, have been cluttered by a lot of logically partitioned cubes joined by multi providers....
Obviously the disadvantage of using logical partitions is that it increases maintenance efforts: you need a new update rule for each logical partition (cube) , then you need to manually add/delte cubes from the multiprovider, filtering data in the update rules to reach the correct cube based on time characteristic etc etc...
I have seen one clear advantage which is the parallelization of queries run against a multiprovider - assuming you wan't to all underlying cubes ... but are there any other advantages which overcome the mainenance overhead?
For me it feels like using physical database partitions in the same cube would be the correct decision in 90% of the cases. It seems to me that the underlying RDBMS should be able to handle itself to:
1) Parallellize a query over several physical partitions if needed.
2) Be smart enough to only query the needed partition if the query is restricted based on the partitioning characteristic.
Please correct me anyone? - When is logical partitions really motivated?
Best regards,
Christian
Edited by: Christian on May 15, 2008 3:55 PMHi,
This is a great question. Generally it is very difficult to understand the real motivation for the physical partioning - multiple cubes. You are right, it definitely increases the maintenance overhead. And you have already pointed out both the advantages and disadvantages.
Physical Partitioning is more useful where we have huge amounts of data. Imagine a cube with 3 or 4 GB of data - which are not usual - but possible. The Table Partioning is useful with small infocubes, less than 1 GB. With bigger Infocubes, Table level partitioning may not provide the required level of performance. If we have too many small partitions, that would also reduce the perfomance. If we have too few partitions, the query performance will not be as much as we want. In this scenario, we can use Physical partitioning (Multiple Cubes) combined with Table Level Partitioning to achieve the required performance levels. On top, we can even think of using Aggregates for further betterment of the performance.
While all the above seems to be relevant for older versions of BW (upto 3.5), BI 7.0 has the BIA (BI Accelerator), which works on the Blade Server with all the data cached directly on the main memory. I am not sure how much this would impact the data modeling - I have not started working on the BIA as yet.
rgds
naga -
Finding whole mapping from database file - filesystems - logical volume manager - logical partitions
Hello,
Trying to make reverse engeneering of database files and their physical carriers on logical partitions ( fdisk ).
And not able to make whole path from filesystem down to partitions with intermediate logical volumes.
1. select from dba_data_files ...
2. df -k
to get the listing of filesystems
3. vgdisplay
4. lvdisplay
5. cat /proc/partitions
6. fdisk /dev/sda -l
fdisk /dev/sdb -l
Problem I have is that not able to determine which partitions are consisten in logical volumes. And then which logical volumens are consisted in filesystem.
Thank you for hint or direction.Hello Wadhah,
Before start the discussion let me explain I am newcommer to Oracle Linux. My genetic with dba experience of Oracle is from IBM UNIX ( AIX 6.1 ) and Oracle 11gr2.
First task is to get the complete picture of one database on Oracle Linux for future maintenance tasks and make database more flexible and
preparing for more intense work:
-adding datafiles,
-optimize/replace archive redolog files on separated filesystem from ORACLE_BASE
- separating auditing log files from $ORACLE_BASE to own filesystem
- separating diag directory on separated file system ( logging, tracing )
- adding/enlarging TEMP ts
- adding/enlarging undo
- enlarging redo for higher transaction rate ( to reduce number of switched per time perceived in alert_SID.log )
- adding online redo and control files mirrors
So in this context try to inspect content of the disk space from the highest logical level in V$, DBA views down to fdisk partitions.
The idea was to go in these steps:
1. select paths of present online redo groups, datafiles, controlfiles, temp, undo
from V$, dba views
2. For the paths got from the step 1
locate filesystems and for those filesystems inspect which are on logical volumens and which are directly on partitions.
3. For all used logical volumes locate the logical partitions and their disks /dev/sda, /dev/sdb, ... -
Separation of the physical and logical structures
Hi,
I am very new to Oracle database administration. While reading Sam Alapati's book "Expert Oracle9i Database Administration," I came across the concept of the separation of an Oracle database’s physical storage structures from its logical storage structures. In particular, Sam states the following in his book:
“This logical defining of Oracle's database structure has another fundamental motive behind it. By organizing space into logical structures and assigning these logical entities to users of the database, Oracle databases achieve the logical separation of users (owners of the database objects, such as tables) of the database from the physical manifestations of the database in terms of data files and so forth.”
I am not quite convinced about the value this separation of the physical and logical really adds to the task of database administration. Considering the way DBASE worked, i.e. each table used to be stored as a separate file, what would be lost if Oracle’s implementation were similar and each table (i.e. file) were to be assigned to a particular user. I am not sure of the value added by storing the data from more than one table in more than one file, effectively resulting in a many-to-many relationship between tables and files. Please enlighten me. I would really appreciate it.
Karimand each table were to be assigned to a particular user. Don't know what you mean. In Oracle, every table has one and only one owner.
I am not sure of the value added by storing the data from more than one table in more than one fileIf an application has a thousand tables, would you rather manage 1000 files or 1?
In general, separating the physical from the logical allows the physical structure to change without affecting the logical (in theory at least). Even a table is a logical structure. We think of rows and columns, but it isn't stored the way we think of it. When we do a select statement, we don't have to write code to read each block, extract the contents, etc.
With partitioned tables, it is sometimes a good idea to split up partitions in such a way to get a performance gain. Like placing the most recent (and most queried) month of data on the fastest storage device. If you stuffed everything in to one gigantic file, you would lose that ability.
If you want to store each table as a separate file, you can do that with Oracle. For each new table, create a new tablespace, and then create a new file for the tablespace. Then come back to this forum in a year and tell us how it's going. -
Logical partitioning, pass-through layer, query pruning
Hi,
I am dealing with performance guidelines for BW and encountered few interesting topics, which however I do not fully undestand.
1. Mainetance of logical partitioning.
Let's assume logical partitioning is performed on year. Does it mean that every year or so it is necessary to create additional cube/transformation and modify multiprovider? Is there any automatic procedure by SAP that supports creation of new objects, or it is fully manual?
2.Pass- though layer.
There are very few information about this basic concept. Anyway:
- is pass through DSO write optimized one? Does it store only one loading - last one? Is it deleted after lading is sucessfully finished (or before new load starts)? And - does this deletion do not destroy delta mechanism? Is the DSO replacing PSAfunctionally (i.e. PSA can be deleted every load as well)?
3. Query pruning
Does this happen automatically on DB level, or additional developments with exits variables, steering tables and FMs is required?
4. DSOs for master data loads
What is the benefit of using full MD extraction and DSO delta insetad of MD delta extraction?
Thanks,
Marcin1. Mainetance of logical partitioning.
Let's assume logical partitioning is performed on year. Does it mean that every year or so it is necessary to create additional cube/transformation and modify multiprovider? Is there any automatic procedure by SAP that supports creation of new objects, or it is fully manual?
Logical partitioning is when you have separate ODS / Cubes for separate Years etc ....
There is no automated way - however if you want to you can physically partition the cubes using time periods and extend them regularly using the repartitioning options provided.
2.Pass- though layer.
There are very few information about this basic concept. Anyway:
- is pass through DSO write optimized one? Does it store only one loading - last one? Is it deleted after lading is sucessfully finished (or before new load starts)? And - does this deletion do not destroy delta mechanism? Is the DSO replacing PSAfunctionally (i.e. PSA can be deleted every load as well)?
Usually a pass through layer is used to
1. Ensure data consistency
2. Possibly use Deltas
3. Additional transformations
In a write optimized DSo - the request ID is key and hence delta is based on request ID. If you do not have any additional transformations - then a Write optimized DSO is essentially like your PSA.
3. Query pruning
Does this happen automatically on DB level, or additional developments with exits variables, steering tables and FMs is required?
The query pruning - depends on the run based and cost based optimizers within the DB and not much control over how well you can influence the execution of a query other than havin up to date statistics , building aggregates etc etc.
4. DSOs for master data loads
What is the benefit of using full MD extraction and DSO delta insetad of MD delta extraction?
It depends more on the data volumes and also the number of transformation required...
If you have multiple levels of transformations - use a DSO or if you have very high data volumes and want to identify changed records - then use a DSO. -
Standalone report server not found on the network between logical partitions on AIX
Hello,
Here s our architecture:
forms/reports11gr2(patchset 1)
weblogic 10.3.6
on IBM AIX 7.1
Server JRE
Java(TM) SE Runtime Environment (build pap6460sr13ifix-20130303_02(SR13+IV37419) )
IBM J9 VM (build 2.4, JRE 1.6.0 IBM J9 2.4 AIX ppc64-64 jvmap6460sr13-20130114_1
JRE -client - 1.6.0_27
We have 2 logical partitions separated in 2 different physical m/c where cluster of forms /reports is installed.
if i have a report service repsrv11g on one logical partition say, box 100 on Physical box 6000, the other logical partition box101's forms server on physical box 7000 is not able to look up the report service when calling from Forms using the Run_report_object.
Gives, FRM -41213 error.
If i just run the URL(use 2nd box) with http://101:8888/reports/rwservlet/showjobs?server=repsrv11g, it gives REP-51002: Bind to Reports Server repsrv11g failed
We thought/read that as long as they re on the same network / domain, report service is available.
Also did rwdiag.sh on one partition, its not able to find the other one.
Ran the test form which Oracle provides and it s also not able to find the report server on the network when run on the other lpar.
Temporarily, we created another report service on the other lpar but still using loadbalancing dns while doing web.show_document, so, it could potentially fail to bring up a report if load balancer redirects from one form's server to report server on the other partition.
Any thoughts would be greatly appreciated.
Thanks.Hello,
Any inputs on this pls? -
Physical and logical partation of cube
hi
can i get scenerio for logical and physical partation of cube.
based on year or calmonth that is called physical partation? or not
what is logical partationHi sunil,
Partitioning is mainly done to increase the performance by optiomizing the Time Utility.
Physical Partitioning is the partitioning done at the database level and to do so, we can partition based on the Time,date so on... In terms of Cube partitioning we usually use 0CALMONTH, 0CALYEAR or 0FISCYEAR.
And
Logical Partitioning is the partitioning done at the Query level while retriving data from the cube. This is said to be Logical because the data is not partitioned at the database level.
Ex: Restict the Query using 0CALMONT,0CALYEAR.
Hope this helps you and solves your problem,if it helps assgn pnts.
Regards
neelima -
Hello All,
I have a lil knowledge about logical partition. Could you please send me some document related to logical partition?
Where and how it can be used in BW?
Thanks.Hi ,
1.Partitioning the cube in both physical and logical way helps you to increase its performance on Queriying.
Partitioning InfoCubes Using the Characteristic 0FISCPER (At Infocube maintainance)
Prerequisites
When partitioning using 0FISCPER values, values are calculated within the partitioning interval that you specified in the InfoCube maintenance. To do this, the value for 0FISCVARNT must be known at the time of partitioning; it must be set to constant.
Procedure
1. The InfoCube maintenance is displayed. Set the value for the 0FISCVARNT characteristic to constant. Carry out the following steps:
a. Choose the Time Characteristics tab page.
b. In the context menu of the dimension folder, choose Object specific InfoObject properties.
c. Specify a constant for the characteristic 0FISCVARNT. Choose Continue.
2. Choose Extras -->DB Performance --> Partitioning. The Determine Partitioning Conditions dialog box appears. You can now select the 0FISCPER characteristic under Slctn. Choose Continue.
3. The Value Range (Partitioning Condition) dialog box appears. Enter the required data.
Pls chk the below link for partioning..
http://help.sap.com/saphelp_bw33/helpdata/en/33/dc2038aa3bcd23e10000009b38f8cf/content.htm
http://help.sap.com/saphelp_nw2004s/helpdata/en/0a/cd6e3a30aac013e10000000a114084/frameset.htm
Re: logical Vs physical partitions ?
Regarding Partitioning
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/ce7fb368-0601-0010-64ba-fadc985a1f94
/message/4204952#4204952 [original link is broken]
How i can partioning the BW?
Partioning and ETable
What is the use of cube partition?
Re: logical Vs physical partitions ?
*Hope this helps*
Regards
CSM reddy -
Hi BW experts,
Can anyone explain the steps to create logical partitioning of Cube data?
I want to do it per fiscal year. If we create 05 cubes(Same structure) each for say fiscal year 04' 05'...08'
now how will the data flow into respective cubes.
Kindly explain the steps.
thanks,
Nipun Sharma
P.S. points will be rewarded.Hi Nipun,
1.Partitioning the cube in both physical and logical way helps you to increase its performance on Queriying.
Partitioning InfoCubes Using the Characteristic 0FISCPER (At Infocube maintainance)
Prerequisites
When partitioning using 0FISCPER values, values are calculated within the partitioning interval that you specified in the InfoCube maintenance. To do this, the value for 0FISCVARNT must be known at the time of partitioning; it must be set to constant.
Procedure
1. The InfoCube maintenance is displayed. Set the value for the 0FISCVARNT characteristic to constant. Carry out the following steps:
a. Choose the Time Characteristics tab page.
b. In the context menu of the dimension folder, choose Object specific InfoObject properties.
c. Specify a constant for the characteristic 0FISCVARNT. Choose Continue.
2. Choose Extras -->DB Performance --> Partitioning. The Determine Partitioning Conditions dialog box appears. You can now select the 0FISCPER characteristic under Slctn. Choose Continue.
3. The Value Range (Partitioning Condition) dialog box appears. Enter the required data.
Pls chk the below link for partioning..
http://help.sap.com/saphelp_bw33/helpdata/en/33/dc2038aa3bcd23e10000009b38f8cf/content.htm
http://help.sap.com/saphelp_nw2004s/helpdata/en/0a/cd6e3a30aac013e10000000a114084/frameset.htm
Re: logical Vs physical partitions ?
Regarding Partitioning
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/ce7fb368-0601-0010-64ba-fadc985a1f94
/message/4204952#4204952 [original link is broken]
How i can partioning the BW?
Partioning and ETable
What is the use of cube partition?
*pls assign points,if info is useful*
Regards
CSM reddy -
Resizing a logical partition with a LUKS container
I have a logical partition that contains LUKS which holds an LVM2 schema. My goal is to resize the existing logical partition so I can create other partitions in their own LUKS-encrypted container. So far, the LVM2 PV is resized and I'm looking for advice on how to handle shrinking the LUKS container and the logical partition it lives on.
I heard rumors that LUKS containers don't need to be resized and that I can change the size of the block device it lives on without problems. Is this true? If so, it seems like I should be able to delete the logical partition and replace it with a smaller one as usual. How can I calculate the blocks/sectors/etc for the new partition with the LUKS & LVM2 data on there?
Last edited by synthead (2013-02-16 07:42:02)Running into a new problem:
# fdisk /dev/sda
Welcome to fdisk (util-linux 2.22.2).
Changes will remain in memory only, until you decide to write them.
Be careful before using the write command.
Command (m for help): p
Disk /dev/sda: 128.0 GB, 128035676160 bytes, 250069680 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x0005c24e
Device Boot Start End Blocks Id System
/dev/sda1 * 2048 499711 248832 83 Linux
/dev/sda2 501758 250068991 124783617 5 Extended
/dev/sda5 501760 250068991 124783616 83 Linux
Command (m for help): d
Partition number (1-5): 5
Partition 5 is deleted
Command (m for help): p
Disk /dev/sda: 128.0 GB, 128035676160 bytes, 250069680 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x0005c24e
Device Boot Start End Blocks Id System
/dev/sda1 * 2048 499711 248832 83 Linux
/dev/sda2 501758 250068991 124783617 5 Extended
Command (m for help): n
Partition type:
p primary (1 primary, 1 extended, 2 free)
l logical (numbered from 5)
Select (default p): l
Adding logical partition 5
First sector (503806-250068991, default 503808): 501760
Value out of range.
Why can't I create a partition on the same starting sector as before? -
I've seen lots of discussions on Logical Partitioning of InfoCubes, but not a lot on Logical Partitioning of DSO Objects.
Can anyone talk to Logical Partitioning of DSO's or point me to some examples?
ThanksKenneth,
Logical partitioning refers to splitting the data into smaller logical chunks by way of design ... for example having two cubes with one cube for data for 2008 and one for 2009 would be an example of logical partitioning.
Similar approaches can be taken for DSO's as well - have separate DSOs one for each country... things like that.
Also please note that this is not the same as physical partitioning - which refers to the usual cube compression etc.... -
Finding of the Logical and Physical filename,Logical and Physical Path
Hello All
Where and how can I find the below details in an SAP server
Logical filename:
Physical filename:
Logical path:
Physical path:
Regards
Kalyanihi
Physical file is what you see from the OS level.
Logical file is what ABAP code can call certain functions to read/write.
Transaction FILE would link them together. Typically the logical path ends with "<FILENAME>", and the logical file refers to the logical path.
To extract the physical path from the logical path name
DATA: lf_mandt TYPE sy-mandt,
lf_opsys TYPE sy-opsys.
lf_mandt = sy-mandt.
lf_opsys = sy-opsys.
To extract the physical path from the logical path name
CALL FUNCTION 'FILE_GET_NAME'
EXPORTING
client = lf_mandt
logical_filename = p_unix
operating_system = lf_opsys
IMPORTING
file_name = gwa_input
EXCEPTIONS
file_not_found = 1
OTHERS = 2.
IF sy-subrc EQ 0.
Concatenating the physical path and the input unix file name
CONCATENATE gwa_input p_file INTO gf_file .
ENDIF.
You need to tak ehelp of ABAPer for this
Check the link
http://help.sap.com/saphelp_nw04/helpdata/en/fc/eb3deb358411d1829f0000e829fbfe/frameset.htm
Regards
Maybe you are looking for
-
Can I delete an account without loosing all the emails?
I now haw 2 accounts in MacMail, each with their own handfull of mail. One account is for a now obsolete email address. I'd like to delete it, leaving me with only the current and active email account / address. However, I can't loose all of the emai
-
HT1386 my iphone & iPad no longer appear in iTunes - how can i fix this?
When I plugged my iphone 5 and ipad 3 into my laptop (windows8) they were showing fine and syncing ok but now they now longer show when i plug them in. I can see them as devices through windows explorer but not in iTunes. Can anybody assist with the
-
Can't get rid of Realplayer download app
I downloaded the RealPlayer download app and then decided it was annoying and wanted to get rid of it. I dragged it to the trash but it keeps coming back. I searched around and found it in the RealNetworks folder in the library and deleted it from th
-
WHY this DB view is not working
REPORT ZMYTESTPRG24 . DATA : IVIEW LIKE ZMYDBVIEW OCCURS 0 WITH HEADER LINE. SELECT * FROM ZMYDBVIEW INTO TABLE IVIEW. LOOP AT IVIEW. WRITE: / IVIEW-MATNR, IVIEW-BISMT, iview-saiso, IVIEW-VA
-
Does anybody know an app which allows you to use your iPhone as CCTV
I am wondering if anybody knows an app which allows you to use your iPhone as a CCTV camera so I can view what is going on. Please if you know any app which allows you to use your iPhone as CCTV camera. Thanks I am really grateful.