Partition Attributes

The Partition Attributes change from read/write to read only is there any way to monitor this in SCOM2012?

Hi Jensen,
According to your description, you want to get the Measure group partition process state and last processed date through DMV, right?
As mentioned above, there is no other query other then Olaf posted. Another option for you is using SSAS AMO to programmatically get the state and last processed date time. The cube, measure group and partition classes of AMO has 2 properties that might
helps State and Last Processed. You can refer to the link below to see more information AMO.
http://msdn.microsoft.com/en-US/library/ms124924(v=sql.90)
Regards,
Charlie Liao
TechNet Community Support

Similar Messages

Change partitioning attribute

Hi,
I have a big table partitioned by a date column (one partition for each month). I need to change the partitioning column to another date column (partitions would also be one per month). Does any one know a simple way to do that?
Database version is 11gR2.
Thanks!

You would almost certainly need to recreate the table and move all the data from the old table to the new table. You can combine or split partitions with DDL but you can't fundamentally change how partitioning is done.
Justin

Hide partition and attribute dynamically

Hello everyone,
We can hide partition & attributes manually by using AttributeHierarchyVisibility Property from False.
but can we hide these all at process time or dynamically.
Thanks in advance.
Regards,
Jvora

Hi jvora,
According to your description, you want to dynamically hide partition and attributes. Right?
In Analysis Services, the only way to hide the attributes is setting the AttributeHierarchyVisibility to false. It's not supported to apply any condition when setting this property. Also for processing dimensions and partitions, it's not supported to
skip attributes during processing. You requirement can't be achieved.
Reference:
Hiding and Disabling Attribute Hierarchies
Best Regards,
Simon Hou
TechNet Community Support

Hard time for selecting Startup Disk (partition) in Mac Classic II.

Dear coleagues, I'd like your help to understand and solve a tricky trouble. I'm sorry for the long text, but the issue is probably living in a small detail.
The issue regards a Mac Classic II with internal and external HDDs. Internal HDD has two partitions, a smaller with System 7.1 (first) and a larger with System 7.5.3 (second). This one is installed there since 5 years ago, working fine.
The (just installed) external HDD has 6 partitions (because of its size 9 Gb). It has been formated runing VCP in this Classic II itself and all partitions are initialized with HFS. It is intended to be a backup for my Classic II as well as my Mac Plus. I've started Installing System 7.5.3 in its third partition. Other partitions remain still empty.
Using only internal HDD I can already perceive that "Startup Disk" control panel is unable to change the boot partition attribute between partitions in the same drive. When I open "Startup Disk" it usualy both partitions of internal HDD are highlighted. I can select a Zip Drive, for instance, and it will boot from Zip. But, when I switch it back to HDD, doesn't bother wich partition I select, it will always boot with the same partition (usually 7.5.3). Then, If i open Startup Disk CP again, both partitions are again highlighted.
To switch between partitions in the same drive, I use Lido 7.5.6 PMount and there I select the boot partition. Then every time I select my HDD, that'll be the default boot partition.
My conclusion is that in Mac Classic II the Startup Disk CP is unable to set a partition within a drive, it selects the drive only. The boot will obey the drive's partition table flag. That's why I can do it whith Lido, writing directly at HDD's flags.
Now, attaching the external HDD, I can see all its partitions in Startup Disk CP and then I select one of them (the 3rd, with 7.5.3). Before rebooting, I close and open again the Startup Disk CP, then I can see all its 6 partitions highlighted. Just like I've been doing with the internal HDD, probably the solution to set a specific boot partition would be through Lido 7.5.6 PMount again. But Lido is unable to handle this drive. It appears gray in the drives list.
What does it sound to you? What would you recommend to test? Is there an alternative for Startup Disk CP?
Thank you.
Regards, Ciro (Brazil)

Dear Jan, good Evening.
Thank you for your time.
In fact I can select a specific partition, but by closing and reopenning Startup Disk CP I realize that the selection has been attributed to the physical drive (all partitions highlighted).
I have tried Startup Disk CP in both System 7.1 and System 7.5.3. They do the same way.
Internal HDD has been formated, partitioned and initialized with Apple HD CS Setup.
This external HDD in a different way. Apple HD SC Setup hasn't been able to "see" it, probably because of its prior format system. Lido neither. That's why I went to VCP. Moreover, as it is too big for 68030, I had to format it attached to a Performa 6360. After formating, I've let VCP make set the partitions in HFS mode (partitions with 512, 1024 and 2032 Mb).
I've mounted VCP in Mini VMac to get some screenshots for you:
Bringing it back to Mac Classic II, it could be mounted with Lido, but System 7 has asked to initialize all partitions again. I've accepted, installed system 7 on it, and it didn't boot. Then I've repeated the partitioning and initializing procedures using Apple HD SC Setup (since now there's a Mac HDD with "small" logical drives). Nothing changed.
I'm following your tip about System Picker. I've downloaded the sit file and read about it. It seems to be able to overlay the problem. I'm gonna try it and report back here.
But I feel still uncomfortable not to be able to do things the regular way. As far as I know, the boot partition is an attribute of a drive partition in partition map, just like the "Active Partition" found in FAT systems. I should be able to write there as I can do with Lido in internal HDD.
Thank you, Jan.
Best regards,
Ciro Bruno.

Question about attributes, UDAs, Associations, etc

Hello,
In Essbase database (v 9.3.1), can someone tell me the usefulness/benefits of attributes, associations, and UDAs? What can they do/make it easier to do?
Also in my information tab, I have some fields called variance reporting expense (could be true of false). I noticed that some members have this set to true or false. I wonder what this is for. I don't see the benefit of this extra property/information tied to the level 0 member.
Thanks in advance.

Attributes are wondereful things. I don't know if I can do it full justice but here are what I consider to be the highlights:
1) Attributes come in two flavors: member and dimension. Member attributes are applied as a "flag" to specific members so that these members can be easily grouped in a method outside of the normal hierarchy itself. This is the primary purpose, to take an otherwise ungrouped set of members and give them a means to be readily associated as a group. Dimension attributes are a bit more formal, and should be applied to all members in the dimension (ideally). This applies to a given generation or level, of course. For instance, "all" level 0 members of the time dimension could have an attribute association for the day of week, assuming level 0 are the days of a specific year (or set of...). This would then allow you to say you want the entire Month of May as the time member, but then limit it to Fridays only through the "Day of Week" attribute dimension.
2) There are some specific things that attributes do well, and some "not so much". For example, all attribute based retrieves are necessarilly done using a dynamic calculation -- there are no precalculated totals. On the previous example, to filter a single year to all Fridays would add the 52 Fridays in the year together at retrieval time to obtain the result. OUCH. However, when leveraged with other tools, this becomes a very powerful capability. For instance, an Organization structure could have an attribute for status (open/closed/etc.), type (center/overhead/field office/etc...), along with several other attributes. Now you can leverage these individually or in groups to "fine tune" your retrieve, by using these "optional dimensions" in a mix and match set which is not otherwise available within a single given dimension.
3) Expense reporting is best looked up in the DataBase Administrators Guide (DBAG). There are a few easily understood but hard (for me to explain) reasons to use expense reporting, but it mostly boils down to the way expenses are handled for variance analysis purposes. Instead of needing if/then logic to deal with reporting good/bad news variances, expense account flags can make it all be perfectly understood by the finance team.
I realize that a raw list of features doesn't easily translate into a "when/how/why would you use them", so here are some example scenarios that illustrate when/how/why these items may help:
- If you need to make an alternate hierarchy based on subsets of members, perhaps UDA's are a better option here?
- If you have multiple elements of information (attributes!) that relate to most/all of a single dimension, an attribute dimension will generally be better.
- If you use partitions, attribute dimensions become an issue.
- If you have a small subset of members that are spread throughout the dimension but need to be related in a different way, your options are pretty much UDA or Alternate Hierarchy.
- If you do variance reports within the model, tagging expense accounts appropriately will automatically handle the sign flip associated with good news/bad news issues.

Deploying to Different Partition

Hi,
i want to deploy AIA Composits and EBS to partition other than default. Is there away to do do this for AIA
I am using following commands
_ant -f ${AIA_HOME}/Infrastructure/Install/AID/AIAInstallDriver.xml -DPropertiesFile=${AIA_HOME}/aia_instances/CTMSAIADEV/config/AIAInstallProperties.xml -DDeploymentPlan=${AIA_HOME}/pips/CTD/DeploymentPlans/CTDDP.xml -l ${AIA_HOME}/pips/CTD/DeploymentPlans/CTDDeploymentPlanLog.log
i have seen in forums , but issue is in point number 3 for update ant call not sure what i have to do.
*1. Add "partition" attribute to "Composite" macrodef $AIA_HOME/Infrastructure/Install/AID/lib/AIDDeploymentLibraryTasks.xml*
*<macrodef name="Composite">*
*<Attribute name="partition" default="default"/>*
*2. Add "partition" attribute to "DeployComposite" macrodef $AIA_HOME/Infrastructure/Install/AID/lib/AIDDeploymentLibraryTasks.xml*
*<macrodef name="DeployComposite">*
*<Attribute name="partition"/>*
*3. Update the ant call step to deploy by passing this attribute.*
*<ant antfile="${SOA_HOME}/bin/ant-sca-deploy.xml"*
*target="deploy" dir="${SOA_HOME}/bin">*
*<property name="partition"*
*value="@{partition}"/>*
*So in the DeploymentPlan we can use following:*
*<Composite compositeName="SyncCustomerReqABCSImpl" compositedir="${AIA_HOME}/Services/Customer/SyncCustomerReqABCSImpl" revision="1.0" wlserver="fp" action="deploy" partition="masterdata"/>*

Hi,
I happen to have researched this.
It is not possible to change the deployment partition using the AIA deployment plan because the paramater is missing.
There is a Hack I found here:
AIA Deployment Questions and Answers
AID Support for Deployment to SOA Partitions:
One more thing I am looking is to update the AID deployment script to support deployment to partitions on SOA. Seems like this isn't supported in the new version of AID also. Here are the steps I have to customize AID to support composite deployment to different SOA Partitions. Please correct me if I am wrong.
1. Add "partition" attribute to "Composite" macrodef $AIA_HOME/Infrastructure/Install/AID/lib/AIDDeploymentLibraryTasks.xml
<macrodef name="Composite">
<Attribute name="partition" default="default"/>
2. Add "partition" attribute to "DeployComposite" macrodef $AIA_HOME/Infrastructure/Install/AID/lib/AIDDeploymentLibraryTasks.xml
<macrodef name="Composite">
<Attribute name="partition"/>
3. Update the ant call step to deploy by passing this attribute.
<ant antfile="${SOA_HOME}/bin/ant-sca-deploy.xml"
target="deploy" dir="${SOA_HOME}/bin">
<property name="partition"
value="@{partition}"/>
So in the DeploymentPlan we can use following:
<Composite compositeName="SyncCustomerReqABCSImpl" compositedir="${AIA_HOME}/Services/Customer/SyncCustomerReqABCSImpl" revision="1.0" wlserver="fp" action="deploy" partition="masterdata"/>

MAXL Warning Messages

Hi All,
Issue is regarding the MAXL limit when we have warnings during Data Load...
In the CFG file i have DATAERRORLIMIT set as 65000 and i have rejections in the dataload when using Maxl Import command and the errors were directed to one logfile.
Am able to see the log file with rejections, but one more what we have done in the shell script is capturing the STDERR and throwing a communication when there are rejections... the issue is when i have rejections less than 65000, it won't display the Warning message.
Done these many things:
- Modified the CFG and set the DataErrorLimit as 1 and checked..this time we have the warning message in the App.log(DATAERRORLIMIT crossed the specified Limit[1]) but not getting captured as the STDERR and hence not to the file.
- i was not able to see the Warning message along with other OK/INFO messages in the maxl output log file (but in app.log)
- Tried using set message level option but it is also not working.
Can anybody help me in this regard and your help is deeply appreciated..
Thanks

We're definitely in agreement. I think I was just explaining the value of using the expedient approach and you were emphasizing the "correct" approach, which is why I put my answer the way I did (do the expedient thing but don't forget to address the underlying needs which you already indicated).
Fundamentally, I find that many of the guru's out there do tend to look at the "correct way" as the only answer (mostly because they rarely get boxed into less than this). The reality for a lot of users is that a compromise is often inevitable along the way. So I tend to only disagree on matters of feasibility.
I'm struggling with this very thing at my company here. It boils down to the need to split a database up, and the partition/attribute dimension issue is slamming us hard. I'd like to do it the "right way", but I'm ending up with a compromise that adds a little risk and a lot more effort (on my part) than I'm comfortable with. In the end, however, I'm sure things will stabilize in a more comfortable compromise (meaning I'm more likely to become comfortable with the risk and added effort than the CFO and VP of Finance are of letting me deal with it the "right way"). -- it all boils down to choosing your battles, LOL.

SSAS 2008 - How to get processing times per dimension / measure group?

Hi experts!
SSAS 2008. I am doing analysis and I'm trying to get information (from dmv or log) about processing times per dimension / measure group. Any ideas how to do that?
Thanks,

also in DMV there's no column recording the processing time, so we suggest you using SSAS AMO to programmatically get the state and last processed date time. Please see:
Analysis Management Objects (AMO)
Hi John,
Thanks for you info, As
Simon Suggested there is no DMV columns available.
You can use below link for more information.
Programming Administrative Tasks with AMO
Cube
partition attributes for last processed (timestamp and status)
Thanks
Suhas
Mark as Answer if this resolves your problem or "Vote as Helpful" if you find it helpful.
My Blog
Follow @SuhasKudekar

MBR lost, standard restoration doesn't work

Hi,
i messed up my MBR on the macbook pro, grub was installed by mistake on the first disk....
So i lost the bootcamp partition.... (not bootable)
here is some information :
sudo fdisk /dev/disk0
Disk: /dev/disk0     geometry: 30401/255/63 [488397168 sectors]
Signature: 0xAA55
         Starting       Ending
#: id cyl hd sec - cyl hd sec [     start -       size]
1: EE 1023 254 63 - 1023 254 63 [         1 -     409639] Unknown ID
2: AF 1023 254 63 - 1023 254 63 [    409640 - 361719984] HFS+
3: AB 1023 254 63 - 1023 254 63 [ 362129624 -    1269544] Darwin Boot
*4: 07 1023 254 63 - 1023 254 63 [ 363399168 - 124997632] HPFS/QNX/AUX
sudo gdisk /dev/disk0
Disk /dev/disk0: 488397168 sectors, 232.9 GiB
Logical sector size: 512 bytes
Disk identifier (GUID): 345AB806-3EB5-4BAD-A5ED-061B689DD199
Partition table holds up to 128 entries
First usable sector is 34, last usable sector is 488397134
Partitions will be aligned on 8-sector boundaries
Total free space is 341 sectors (170.5 KiB)
Number Start (sector)    End (sector) Size       Code Name
   1              40          409639   200.0 MiB   EF00 EFI System
   2          409640       362129623   172.5 GiB   AF00 Apple HFS/HFS+
   3       362129624       363399167   619.9 MiB   AB00 Apple boot
   4       363399168       488396799   59.6 GiB    0700 Microsoft basic data
sudo gdisk /dev/disk0 : then x a 4 (flags on BOOTCAMP partitions)
Attribute value is 0000000000000004. Set fields are:
2 (legacy BIOS bootable)
sudo gdisk /dev/disk0 : then r o (protective MBR data)
Disk size is 488397168 sectors (232.9 GiB)
MBR disk identifier: 0x00000000
MBR partitions:
Number Boot Start Sector   End Sector   Status      Code
   1                     1       409639   primary     0xEE
   2                409640    362129623   primary     0xAF
   3             362129624    363399167   primary     0xAB
   4      *      363399168    488396799   primary     0x07
I already tried the solution at https://discussions.apple.com/thread/4144252 without success.
I booted on the restoration partition and i had the bootcamp boot option in the reboot menu, but it didn't boot...
I know that my bootcamp partition is not dead, i can boot it with Parallels.
Bootcamp : Windows 8
OS X : Mavericks

Everything there looks ok to me for a standard Bootcamp Windows installation.
Can you view the Bootcamp partition and its contents in a Finder window?
If you can please navigate to Bootcamp > Windows > Panther folder and in that folder open the file setupact.log
In the top menu bar click Edit > Find > find
and in the search box top right enter
Detected boot environment
The ouput will show either
Callback_BootEnvironmentDetect: Detected boot environment: BIOS
or
Callback_BootEnvironmentDetect: Detected boot environment: EFI

Buggy client restore - error c000000e winload.exe

Looks like the bare metal client restore is a big buggy
Scenario - old SSD 256GB, restore to brand new 500Gb SSD
Old Partitions: RESTORE(no drive letter), OS C: (bitlocked)
After restore: RESTORE(C:), OS (D:)
Windows won't boot with error c000000e winload.exe
Booted into Windows repair mode (off Windows 8 CD)
- repair windows states it has no idea how to fix it
- went into command line mode and used diskpart not exactly sure what I did, but it included resetting drive letters
       select volume 1
       remove
      select volume 2
      assign letter=C
- still won't boot
- re-ran repair mode. this time it fixed it and windows boots
The system is now happy and all files seem to be there
Conclusion: The partition attributes aren't being restored correctly, but the contents are ?
I don't know if this is SSD specific, but something is definitely broken

Hi,
Based on the error code you posted c000000e, i checked with my inernal tool and found the following information
C:\Users\v-yanwen>err.exe c000000e
# for hex 0xc000000e / decimal -1073741810
STATUS_NO_SUCH_DEVICE
ntstatus.h
# A device which does not exist was specified.
# as an HRESULT: Severity: FAILURE (1), FACILITY_NULL (0x0), Code 0xe
# for hex 0xe / decimal 14
ERROR_OUTOFMEMORY
winerror.h
# Not enough storage is available to complete this operation.
# 2 matches found for "c000000e"
After we finished restoring the system we received the error code: Windows won't boot with error c000000e winload.exe. the reason we couldnt boot the system is because of one of the reasons as following:
# A device which does not exist was specified.
# Not enough storage is available to complete this operation.
Hope this inforamtion is helpfulfor you.
Thanks
Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

The issue about prompt

I have three alias tables named 'Attribute I','Attribute II','Attribute III' that derive from 'Attribute' table,and those tables have three columns named 'Partition Attribute I','Partition Attribute II','Partition Attribute III'.
My requirement is that one column can control three columns,if it is prompted, the result will be showed.(*Do not use presentation variables*)
For example, firstly, I have created one column named 'Partition Attribute I' in the dashboard prompt, and drag three columns (I,II,III) into the request .If the three colums has value of one column based on the prompt,the result will be showed.
Is there any idea to solve it in RPD or Answer?Thanks.

Why can't you use a presentation variable ?
Richard Chan
Rittman Mead Oceania

When I restore my Mac with Time Machine and then want to partition my disk, Disk Utility always says incorrect number of extended attributes

When I need to restore my Mac from a time machine backup and then partition my hard disk (the disk inside the computer not the time machine disk), Disk Utility always says "Incorrect Number of Extended Attributes". I then boot into Recovery HD and run disk repair. The result? "The volume Macintosh HD appears to be OK". So then I reboot into normal OS and try the partition again, still Incorrect number of extended attributes. I have even tried /sbin/fsck -fy in single-user mode but it still says the volume is ok. I have tried partition my disk in the recovery HD and it still fails.
Can anyone please help me solve this problem?

Try something stronger, such as DiskWarrior or TechTool Pro.
iMac refurb (27-inch Mid 2011), OS X Mavericks (10.9.4), SL & ML, G4 450 MP w/Leopard, 9.2.2

Physical model attribute "Partition Scheme" not saved. (SS2000)

Hello,
I believe this is a bug report.
Scenario:
I have a physical model of a SQL Server database. The model contains partitioned tables, 1 partitioning function and 1 partitioning scheme. If I open the physical model properties of an index or a table, set the "Partition Scheme" attribute, save, close and re-open the model, the "Partition Scheme" attribute is lost. If I don't close out and just re-open the properties page, the attribute is retained. Some how, the attribute is lost in the persistence layer.
If there is a reason the attribute is being reset, please let me know.
Thank for your help, and all the great products you guys make,
Kurt
DataModeler v 3.1.1

Hi Kurt,
If there is a reason the attribute is being resetUnfortunately there is a bug causing the problem. Fix will be available in next patch release.
Philip

Multiple LDAP Servers and Attribute-Based Data Partitioning

Hello
We currently want to implement following szenario on Netweaver 2004s. From the
following SAP Help documentation we want attribute based data partitioning:
http://help.sap.com/saphelp_nw70/helpdata/EN/4e/4d0d40c04af72ee10000000a1550b0/frameset.htm
The difference to the SAP document is that we want a distribution of attributes over
multiple LDAP servers. So we tried to fit that concept into xml. see attached xml source.
The Portal finds both LDAP Systems but it is NOT that the useres are beeing merged
but they appear as two distict users in the portal UME. If you do a lookup in the portal
usernamagent system you get and see two users.
User1: unique ID = USER.Datasource1.uid
User2: unique ID = USER.Datasource2.uid
Obviously the UME system was not able to merge that information of the two distict
LDAP Systems. MSADS and Lotus Notes.
Hence my questions:
1) is it possible to distribute attributes over multiple ldap data sources
2) any ideas why UME constructs two different users based in Datasource ID's specified in XML
Thanks for any contributions or ideas,
Ulrich Scherb
<?xml version="1.0" encoding="UTF-8"?>
<dataSources>
    <dataSource id="PRIVATE_DATASOURCE"
                className="com.sap.security.core.persistence.datasource.imp.DataBasePersistence"
                isReadonly="false"
                isPrimary="true">
        <homeFor>
            <principals>
                 <principal type="group"/>
                 <principal type="user"/>
                 <principal type="account"/>
                <principal type="team"/>
                <principal type="ROOT" />
                <principal type="OOOO" />
            </principals>
        </homeFor>
        <notHomeFor/>
        <responsibleFor>
            <principals>
                 <principal type="group"/>
                 <principal type="user"/>
                 <principal type="account"/>
                <principal type="team"/>
                <principal type="ROOT" />
                <principal type="OOOO" />
            </principals>
        </responsibleFor>
        <privateSection>
        </privateSection>
    </dataSource>
    <dataSource id="NOTES_LDAP"
          className="com.sap.security.core.persistence.datasource.imp.LDAPPersistence"
          isReadonly="true"
          isPrimary="true">
          <homeFor/>
          <responsibleFor>
               <principal type="account">
                    <nameSpace name="com.sap.security.core.usermanagement">
                         <attribute name="j_user"/>
                         <attribute name="logonalias"/>
                         <attribute name="j_password"/>
                         <attribute name="userid"/>
                    </nameSpace>
                   <nameSpace name="com.sap.security.core.authentication">
                        <attribute name="principal"/>
                   </nameSpace>
               </principal>
               <principal type="user">
                    <nameSpace name="com.sap.security.core.usermanagement">
                         <attribute name="firstname" populateInitially="true"/>
                         <attribute name="lastname" populateInitially="true"/>
                         <attribute name="email"/>
                         <attribute name="uniquename" populateInitially="true"/>
                    </nameSpace>
                    <nameSpace name="$usermapping$">
                         <attribute name="REFERENCE_SYSTEM_USER"/>
                    </nameSpace>
               </principal>
          </responsibleFor>
          <attributeMapping>
               <principal type="account">
                    <nameSpace name="com.sap.security.core.usermanagement">
                         <attribute name="j_user">
                              <physicalAttribute name="uid"/>
                         </attribute>
                         <attribute name="logonalias">
                              <physicalAttribute name="uid"/>
                         </attribute>
                         <attribute name="j_password">
                              <physicalAttribute name="unicodepwd"/>
                         </attribute>
                         <attribute name="userid">
                              <physicalAttribute name="*null*"/>
                         </attribute>
                    </nameSpace>
                   <nameSpace name="com.sap.security.core.authentication">
                        <attribute name="principal">
                             <physicalAttribute name="uid"/>
                        </attribute>
                   </nameSpace>
               </principal>
               <principal type="user">
                    <nameSpace name="com.sap.security.core.usermanagement">
                         <attribute name="firstname">
                              <physicalAttribute name="givenname"/>
                         </attribute>
                         <attribute name="lastname">
                              <physicalAttribute name="sn"/>
                         </attribute>
                         <attribute name="uniquename">
                              <physicalAttribute name="uid"/>
                         </attribute>
                         <attribute name="loginid">
                              <physicalAttribute name="*null*"/>
                         </attribute>
                         <attribute name="email">
                              <physicalAttribute name="mail"/>
                         </attribute>
                    </nameSpace>
                    <nameSpace name="$usermapping$">
                         <attribute name="REFERENCE_SYSTEM_USER">
                              <physicalAttribute name="sapusername"/>
                         </attribute>
                    </nameSpace>
               </principal>
          </attributeMapping>
        <privateSection>
               <ume.ldap.access.server_type>MSADS</ume.ldap.access.server_type>
               <ume.ldap.access.server_name>ldap1</ume.ldap.access.server_name>
               <ume.ldap.access.server_port>389</ume.ldap.access.server_port>
               <ume.ldap.access.authentication>simple</ume.ldap.access.authentication>
               <ume.ldap.access.user>xxxxx</ume.ldap.access.user>
               <ume.ldap.access.password>xxxxx</ume.ldap.access.password>
               <ume.ldap.access.base_path.user>O=SMT_TEST</ume.ldap.access.base_path.user>
               <ume.ldap.record_access>TRUE</ume.ldap.record_access>
               <ume.ldap.unique_uacc_attribute>uid</ume.ldap.unique_uacc_attribute>
               <ume.ldap.unique_user_attribute>uid</ume.ldap.unique_user_attribute>
               <ume.ldap.access.context_factory>com.sun.jndi.ldap.LdapCtxFactory</ume.ldap.access.context_factory>
               <ume.ldap.access.user_as_account>true</ume.ldap.access.user_as_account>
               <ume.ldap.access.ssl_socket_factory>com.sap.security.core.server.https.SecureConnectionFactory</ume.ldap.access.ssl_socket_factory>
               <ume.ldap.access.objectclass.user>person</ume.ldap.access.objectclass.user>
               <ume.ldap.access.objectclass.uacc>person</ume.ldap.access.objectclass.uacc>
               <ume.ldap.access.naming_attribute.user>cn</ume.ldap.access.naming_attribute.user>
               <ume.ldap.access.auxiliary_naming_attribute.user>uid</ume.ldap.access.auxiliary_naming_attribute.user>
               <ume.ldap.access.naming_attribute.uacc>cn</ume.ldap.access.naming_attribute.uacc>
               <ume.ldap.access.auxiliary_naming_attribute.uacc>uid</ume.ldap.access.auxiliary_naming_attribute.uacc>
          </privateSection>
     </dataSource>
    <dataSource id="CORP_LDAP"
          className="com.sap.security.core.persistence.datasource.imp.LDAPPersistence"
          isReadonly="true"
          isPrimary="true">
          <homeFor/>
          <responsibleFor>
               <principal type="account">
                    <nameSpace name="com.sap.security.core.usermanagement">
                         <attribute name="j_user"/>
                         <attribute name="logonalias"/>
                         <attribute name="j_password"/>
                         <attribute name="userid"/>
                    </nameSpace>
                   <nameSpace name="com.sap.security.core.authentication">
                        <attribute name="principal"/>
                        <attribute name="realm"/>
                        <attribute name="domain"/>
                   </nameSpace>
               </principal>
               <principal type="user">
                    <nameSpace name="com.sap.security.core.usermanagement">
                         <attribute name="firstname" populateInitially="true"/>
                         <attribute name="displayname" populateInitially="true"/>
                         <attribute name="lastname" populateInitially="true"/>
                         <attribute name="fax"/>
                         <attribute name="title"/>
                         <attribute name="department"/>
                         <attribute name="description"/>
                         <attribute name="mobile"/>
                         <attribute name="telephone"/>
                         <attribute name="streetaddress"/>
                         <attribute name="uniquename" populateInitially="true"/>
                    </nameSpace>
                    <nameSpace name="com.sap.security.core.usermanagement.relation">
                         <attribute name="PRINCIPAL_RELATION_PARENT_ATTRIBUTE"/>
                    </nameSpace>
                    <nameSpace name="$usermapping$">
                         <attribute name="REFERENCE_SYSTEM_USER"/>
                    </nameSpace>
               </principal>
               <principal type="group">
                    <nameSpace name="com.sap.security.core.usermanagement">
                         <attribute name="displayname" populateInitially="true"/>
                         <attribute name="description" populateInitially="true"/>
                         <attribute name="uniquename"/>
                    </nameSpace>
                    <nameSpace name="com.sap.security.core.usermanagement.relation">
                         <attribute name="PRINCIPAL_RELATION_MEMBER_ATTRIBUTE"/>
                         <attribute name="PRINCIPAL_RELATION_PARENT_ATTRIBUTE"/>
                    </nameSpace>
                    <nameSpace name="com.sap.security.core.bridge">
                         <attribute name="dn"/>
                    </nameSpace>
               </principal>
          </responsibleFor>
          <attributeMapping>
               <principal type="account">
                    <nameSpace name="com.sap.security.core.usermanagement">
                         <attribute name="j_user">
                              <physicalAttribute name="samaccountname"/>
                         </attribute>
                         <attribute name="logonalias">
                              <physicalAttribute name="samaccountname"/>
                         </attribute>
                         <attribute name="j_password">
                              <physicalAttribute name="unicodepwd"/>
                         </attribute>
                         <attribute name="userid">
                              <physicalAttribute name="*null*"/>
                         </attribute>
                    </nameSpace>
                   <nameSpace name="com.sap.security.core.authentication">
                        <attribute name="principal">
                             <physicalAttribute name="samaccountname"/>
                        </attribute>
                        <attribute name="realm">
                             <physicalAttribute name="*null*"/>
                        </attribute>
                        <attribute name="domain">
                             <physicalAttribute name="*null*"/>
                        </attribute>
                   </nameSpace>
               </principal>
               <principal type="user">
                    <nameSpace name="com.sap.security.core.usermanagement">
                         <attribute name="firstname">
                              <physicalAttribute name="givenname"/>
                         </attribute>
                         <attribute name="displayname">
                              <physicalAttribute name="displayname"/>
                         </attribute>
                         <attribute name="lastname">
                              <physicalAttribute name="sn"/>
                         </attribute>
                         <attribute name="fax">
                              <physicalAttribute name="facsimiletelephonenumber"/>
                         </attribute>
                         <attribute name="uniquename">
                              <physicalAttribute name="samaccountname"/>
                         </attribute>
                         <attribute name="loginid">
                              <physicalAttribute name="*null*"/>
                         </attribute>
                         <attribute name="mobile">
                              <physicalAttribute name="mobile"/>
                         </attribute>
                         <attribute name="telephone">
                              <physicalAttribute name="telephonenumber"/>
                         </attribute>
                         <attribute name="department">
                              <physicalAttribute name="ou"/>
                         </attribute>
                         <attribute name="description">
                              <physicalAttribute name="description"/>
                         </attribute>
                         <attribute name="streetaddress">
                              <physicalAttribute name="postaladdress"/>
                         </attribute>
                         <attribute name="pobox">
                              <physicalAttribute name="postofficebox"/>
                         </attribute>
                    </nameSpace>
                    <nameSpace name="com.sap.security.core.usermanagement.relation">
                         <attribute name="PRINCIPAL_RELATION_PARENT_ATTRIBUTE">
                              <physicalAttribute name="memberof"/>
                         </attribute>
                    </nameSpace>
                    <nameSpace name="$usermapping$">
                         <attribute name="REFERENCE_SYSTEM_USER">
                              <physicalAttribute name="sapusername"/>
                         </attribute>
                    </nameSpace>
               </principal>
               <principal type="group">
                    <nameSpace name="com.sap.security.core.usermanagement">
                         <attribute name="displayname">
                              <physicalAttribute name="displayname"/>
                         </attribute>
                         <attribute name="description">
                              <physicalAttribute name="description"/>
                         </attribute>
                         <attribute name="uniquename" populateInitially="true">
                              <physicalAttribute name="cn"/>
                         </attribute>
                    </nameSpace>
                    <nameSpace name="com.sap.security.core.usermanagement.relation">
                         <attribute name="PRINCIPAL_RELATION_MEMBER_ATTRIBUTE">
                              <physicalAttribute name="member"/>
                         </attribute>
                         <attribute name="PRINCIPAL_RELATION_PARENT_ATTRIBUTE">
                              <physicalAttribute name="memberof"/>
                         </attribute>
                    </nameSpace>
                    <nameSpace name="com.sap.security.core.bridge">
                        <attribute name="dn">
                              <physicalAttribute name="*null*"/>
                         </attribute>
                    </nameSpace>
               </principal>
          </attributeMapping>
        <privateSection>
               <ume.ldap.access.server_type>MSADS</ume.ldap.access.server_type>
               <ume.ldap.access.server_name>ldap2</ume.ldap.access.server_name>
               <ume.ldap.access.server_port>389</ume.ldap.access.server_port>
               <ume.ldap.access.authentication>simple</ume.ldap.access.authentication>
               <ume.ldap.access.user>yyyyy</ume.ldap.access.user>
               <ume.ldap.access.password>yyyyy</ume.ldap.access.password>
               <ume.ldap.access.base_path.user>O=SMT_TEST</ume.ldap.access.base_path.user>
               <ume.ldap.access.base_path.grup>O=SMT_TEST</ume.ldap.access.base_path.grup>
               <ume.ldap.record_access>TRUE</ume.ldap.record_access>
               <ume.ldap.unique_uacc_attribute>samaccountname</ume.ldap.unique_uacc_attribute>
               <ume.ldap.unique_user_attribute>samaccountname</ume.ldap.unique_user_attribute>
               <ume.ldap.access.context_factory>com.sun.jndi.ldap.LdapCtxFactory</ume.ldap.access.context_factory>
               <ume.ldap.access.authentication>simple</ume.ldap.access.authentication>
               <ume.ldap.access.flat_group_hierachy>true</ume.ldap.access.flat_group_hierachy>
               <ume.ldap.access.user_as_account>true</ume.ldap.access.user_as_account>
               <ume.ldap.access.dynamic_groups>false</ume.ldap.access.dynamic_groups>
               <ume.ldap.access.ssl_socket_factory>com.sap.security.core.server.https.SecureConnectionFactory</ume.ldap.access.ssl_socket_factory>
               <ume.ldap.access.objectclass.user>User</ume.ldap.access.objectclass.user>
               <ume.ldap.access.objectclass.uacc>User</ume.ldap.access.objectclass.uacc>
               <ume.ldap.access.objectclass.grup>Group</ume.ldap.access.objectclass.grup>
               <ume.ldap.access.naming_attribute.user>cn</ume.ldap.access.naming_attribute.user>
               <ume.ldap.access.auxiliary_naming_attribute.user>samaccountname</ume.ldap.access.auxiliary_naming_attribute.user>
               <ume.ldap.access.naming_attribute.uacc>cn</ume.ldap.access.naming_attribute.uacc>
               <ume.ldap.access.auxiliary_naming_attribute.uacc>samaccountname</ume.ldap.access.auxiliary_naming_attribute.uacc>
               <ume.ldap.access.naming_attribute.grup>cn</ume.ldap.access.naming_attribute.grup>
          </privateSection>
     </dataSource>
</dataSources>

Hi Ulrich,
Hope your problem is resolved. We are using EP7 and SP18. We are doing some study on your first issue. i.e. Distributing a user attribute into multiple LDAPs. Can you please let me know the feasibility? If yes, what are all step do I have to follow? Expecting your valuable answer. Thanks in advance!
Regards,
Kabali

Changing phisycal attribute for a sub partition

Hi
oracle version : 10.2.0.4 on Solaris
I have a table with subpartitions and I need to reduce the initial extent of the subpartition without dropping and recreating .
I can do that on a table level and on a partition level using :
alter table xxx move storage (initial 65k);
alter table XXX move partition YYY storage (initial 65k);
But I cannot do a similar thing for subpartition
alter table xxx move subpartition yyy storage (initial 65k);
ORA-14160: this physical attribute may not be specified for a table subpartition
Any way to accpmplish this without dropping and recreating the table ?
This is needed as part of a huge data structure copy .
I get the structure from a production DB and I am importing them ( using datapump ) to development.
I need to "shrink" the tables because the initial extents defined are big and there are so many of them that the copied schema, thoufght empty of data is taking many GB of space.
I managed to "shrink " everything , only subpartitioned tables are still occupying a lot of space
Any advise ?
Thanks
Orna

Some more info :
I am using LMT in both production and test
but when I export and import ( datapump ) - the initial extents are not 'adjusting' themselves to the new tablespace in test.
So the original tablespace in production have a 100MG initial and next extent and the target tablespace to which I remap during the import has 65k initial/next extent - but nevertheless - the tables are getting created with the old extent sizes of 100MG.
The only way I found to fix this is to actually run alter table commands on the empty tables after import, and that works fine for everything other then subpartitions.
thanks
Orna

Partition Attributes

Similar Messages

Maybe you are looking for