Search Attributes

Hi,
In the PORTAL, I am created some attributes. Its also displays my SES advanced search LOV. I dont want this attributes to my SES. How to delete this? Already i am trying to delete this attributes. I can't delete this. Its display the error.
Oracle Secure Enterprise Search Error
The search attribute "codcc_shift" is still in use.
How to delete this attributes or hide this on my SES lov?
Regards,
Deva

You cannot delete an attribute if it's in use. You need to find the mapped attributes in your content source(s), delete them, re-index the content source in full index mode.
If this doesn't work, try dropping the content source that contains the mapped attributes, delete the attributes, and recreate the content source.

Similar Messages

  • Problem with Search Attributes iView in MDM Business package

    Hello Everybody,
    I am configuring MDM Search Attributes iView in Portal.
    This iView should show data based on selected record in Search Hierarchy iView. But it is not showing any attribute data on Search Attributes iView.
    Any idea what could be the problem.
    I have MDM 5.5. SP01
    Appreciate your help.
    Thanks,
    Bhavik Devisha

    Hi,
    I tried the scenario on MDM 5.5 SP06 and its working fine.
    Following are the steps:
    1. Create the MDM System.
    2. Create the Search Hierarchy iView
    3. Create the Search Attributes iView
    4. Create the page and place both the iViews into that page.
    Now when i am changing the hierarchy,its corresponding attributes appear in the Search Attributes iView as expected.
    Try the same on some different version.Then only we can conclude that it might be because of version.
    Regards,
    Jitesh Talreja

  • Changing LDAP "Search Attribute"

    Hello:
    I am authenticating against LDAP as such:
    Hashtable authEnv = new Hashtable();
    String dn =
    "CN=" + userAuth.getFirstName() + " " + userAuth.getLastName() +
    ",OU=zzzzzzzz,DC=yyyyy,DC=xxx";
    authEnv.put(Context.INITIAL_CONTEXT_FACTORY,
    "com.sun.jndi.ldap.LdapCtxFactory");
    authEnv.put(Context.PROVIDER_URL, "ldap://999.999.199.999:389");
    authEnv.put(Context.SECURITY_AUTHENTICATION, "simple");
    authEnv.put(Context.SECURITY_PRINCIPAL, dn);
    authEnv.put(Context.SECURITY_CREDENTIALS, password);
    I am using the user's first and last name to authenticate. Now, I want to use their login id to authenticate. I was told "to change the Search Attribute from 'uid' to 'sAMAccountName'". I don't know what this refers to. Does anybody have any ideas?
    Thanks
    Eric

    A call to Apple support helped solve this problem, especially to deal with a typo in the Apple Snow Leopard Server documentation:
    1. Export all of your users, groups, etc. to files. Passwords will be reset but everything else will work.
    2. In OD, change the server to be "stand alone" (basically turning off OD).
    3. From the command line run the following command, noting that you literally put the string "HostName" in the position specified, not the old host name specified in the documentation:
    sudo scutil --set HostName <fully qualified domain name>
    4. Reboot
    5. Restart Server Admin and recreate the OD master using the fully qualified name.
    6. Go to KeyChain and look for the entries for system -> com.apple.opendirectory. One should point to your server and one should be blank. Delete the bank entry.
    Done!

  • Missing Finder/Spotlight search attributes!

    When searching in the finder, after pressing the icon from the search bar and then selecting "other" from the drop down menu, there is no search attributes to check mark. I am not on an root or guest account. I am the administrator. Is there a preference file anywhere I can delete? Thanks in advance.

    I just finished an archive and install, and the spotlight search attribute list that comes up from selecting other is still blank. I checked right after the archive and install, and it was blank, and I checked after applying each update, and it remained blank after each update.
    I have also applied the directly downloaded (rather than using software update) update to 10.5.1, and still no items appear on the list.
    I have not tried a full slash and burn reformat and install yet, but that may be what it comes down to. I am weighing whether the annoyance of being unable to search my Library folder outweighs the annoyance of a reformat and install from scratch.

  • Lack of search attributes?

    When I try to search for something (in addition to the ridiculous long wait times), I can not specify any search attributes other then the default (kind, open date, modified date, created date, name, and contents.) How can I get any search attributes to chow up when I select "Other..."? I would like to search amongst the system files as well as just the computer.

    At the risk of asking the obvious, you followed the sequence exactly as described, as there's a second sequence that I've seen documented at some web sites and that sequence does not work with SLS and SL. When you get the selection sheet, you are not on the line that has the +Kind is Any+ stuff. You're on the next line, with the Other... on that next line.
    There are suggestions around the com.apple.spotlight.plist plist preferences file (that I've not tried), but I'd tend to try a repair permissions and a reboot, and than (failing that) go for an archive and install here. I'd get a backup before that, regardless.

  • Adding Another LDAP Search Attribute

    Hi,
    Can you please point me to any document for adding another ldap search attribute apart from uid.
    Regards,
    Edited by: IDM1312 on Jun 9, 2008 4:28 PM

    Yes, here is what happens when your user tries to login:
    They enter some username & password. The username can be any attribute you wish it to be (email, UID, cn, etc). The actual authentication is not done using the value the user enters. This is because you need to authenticate with the user's DN. To get the DN, access manager does a lookup on the directory server to see if what the user entered exists in any of the attributes in the search alias list. If the search is successful, it returns the user's DN. Access Manager then uses the DN and password to authenticate the user.
    So, if you expect your users to enter their email address, you will want your email attribute in this list. You can have multiple values in the list, if for example you want to allow users to enter uid OR email address. I would be careful about allowing this flexibility if you are in a large organization because this will bring increased overhead to both AM & DS.
    Also, be sure that whatever attribute you use is indexed!!
    I hope this helps,
    Eric

  • Using LDAP to search attribute bit flags using attribute OID values

    Hello everyone,
    My question stems from trying to understand the OID and syntax behind this classic LDAP search to find disabled users:
    "(useraccountcontrol:1.2.840.113556.1.4.803:=2)"
    What I am interested in is the value 1.2.840.113556.1.4.803, specifically how it differentiates from the value 1.2.840.113556.1.4.8, which is the OID of the useraccountcontrol attribute:
    http://msdn.microsoft.com/en-us/library/ms680832(v=vs.85).aspx
    Now, this website below says that the 03 and 04 are designators of the AND and OR operations, respectively, and are added on to the end of the OID:
    https://www.appliedtrust.com/blog/2011/04/keeping-your-active-directory-pantry-order
    However, using this logic, I can't get these 03 and 04 operators to work with other attribute OID's that use flags as values, such as the "searchflags" attribute, e.g. a LDAP search of "(searchflags:=1.2.840.113556.1.2.33404:=0)
    returns nothing, using the OR (04) operation at the end of the "searchflags" OID of 1.2.840.113556.1.2.334.
    So back to my original question, for the useraccountcontrol OID of 1.2.840.113556.1.4.8, is this OID at all related to the bitwise AND extensible match of 1.2.840.113556.1.4.803 (like just adding a 03 to designate an AND operation), or is this
    extensible match
    value of 1.2.840.113556.1.4.803 completely separate from the useraccountcontrol OID of 1.2.840.113556.1.4.8?
    If I have my terms mixed up, please feel free to correct me on what the proper terms are.
    Thanks!

    Hmm yeah I posted that link above in my OP as well, and I was hoping that the OID values of these bitwise filters were somehow related to the shorter OID of the "useraccountcontrol" attribute, but it looks like it's just a coincidence.
    So I wonder if the "useraccountcontrol" section of
    this article from my OP is a little misleading when it says:
    To make a comparison, we either need to use the LDAP_MATCHING_RULE_BIT_AND rule (1.2.840.113556.1.4.803), or the LDAP_MATCHING_RULE_BIT_OR rule (1.2.840.113556.1.4.804) for our attribute OID (the AND rule adds a 03 suffix to denote the AND operation,
    and the OR rule adds a 04 suffix).
    Following this logic, I should be able to use the "03" and "04" in other bitwise operations with different OID's to search "AND" or "OR", but as I pointed out in my OP above, I can't seem to make this work with adding the 
    "03" and "04" onto the end of other OID's. So I will go with Christoffer that these bitwise OID's (1.2.840.113556.1.4.803 and 1.2.840.113556.1.4.804) are unique in themselves, and the fact that they are 2 characters away from the OID of the "useraccountcontrol"
    attribute (1.2.840.113556.1.4.8) is just coincidence.
    This does seem strange however, and it seems like there should be some correlation here....
    If anyone has any more info, I would love to hear it!

  • SES TREX Search Attribute + Fulltext

    Hello ,
    i have my own WebDynpro for the ses Search.
    Now I would search
    printer* and type="servicecall"
    this is in trex admin tool working.
    At the moment my ls_query look like this :
    ls_query-value1       ='print'
        ls_query-operator     = 'EQ'.
        ls_query-content_type = 'C'.
        ls_query-rowtype = 'TERM'.
        append ls_query to lt_query.
        ls_query-rowtype = 'Operator'.
        ls_query-value1 = 'AND'.
        append ls_query to lt_query.
        ls_query-rowtype = 'ATTRIBUTE'.
        ls_query-location = 'type'.
        ls_query-value1 = 'servicecall'.
        ls_query-operator = 'EQ'.
        ls_query-term_action = 'E'.
        append ls_query to lt_query.
    But I receive an error :
    syntax error (parsing query);
    any solution for this problem ? or have someone solved this problem other ?
    Edited by: Daniel Rothmund on Nov 26, 2009 7:35 PM

    Hi Marcin
    I think you should create this message in the Enterprise Search forum, if you haven't done already.
    Kind regards,
    Martin Søgaard

  • Is it possible to change ldap search attribute telephonenumber to an other

    Hello, I have a directory that holds the users phones number in an alternate ldap attribute "numeroCourt".
    The default Directory search asp files are displaying the content of the telephonenumber attribute in the LDAP Directory.
    What do I need to edit to change "telephonenumber" with "numeroCourt"?
    Thanks in advance.

    Since telephone number is not populated the logical thing for the CorpDir application to do would be to see that the
    "ciscoatUserProfileString" has a value and go retrieve the extension information from there.
    http://www.cisco.com/en/US/products/sw/voicesw/ps556/products_tech_note09186a0080094493.shtml

  • Weights on search attributes (9iAS Rel. 1)

    Hi,
    we have customers complaining about the fact that simple searches on a word appearing in a document title, returns several pages results, with first documents where the word appears just in the document text, then (on the third, fourth page result) the documents where the word is in the title and/or description.
    Is there any way to configure the search (with intermedia) to assign a different weight to the various attributes?
    Thanks

    Giorgio
    I'm afraid there is currently no functionality to achieve a user defined weighting of the attributes.
    However, I would suggest that this is possibly a bug because we would expect the default weighting to favour items which contained the search term in the title and description.
    I will verify this behaviour. If you require a fix to this then please persue it with Oracle Support.
    thanks
    Ross

  • How to search attribute values

    How to find the attribute values ("0_0_0_1" ) in the following xml example.
    Example:
    var xml:XML=
    <root>
    <country id="0">
    <states id="0_0">
    <city id="0_0_0">
    <village id="0_0_0_0"></village>
    <village id="0_0_0_1"></village>
    <village id="0_0_0_2"></village>
    </city>
    </states>
    <states id="0_1">
    </states>
    </country>
    <country id="1"></country>
    </root>

    Do you mean like a depth first search?
    package
              import flash.display.Sprite;
              public class XmlAttributes extends Sprite
                        protected var xml:XML = <root>
                                                                                              <country id="0">
                                                                                                        <states id="0_0">
                                                                                                                  <city id="0_0_0">
                                                                                                                            <village id="0_0_0_0"></village>
                                                                                                                            <village id="0_0_0_1"></village>
                                                                                                                            <village id="0_0_0_2"></village>
                                                                                                                  </city>
                                                                                                        </states>
                                                                                                        <states id="0_1">
                                                                                                        </states>
                                                                                              </country>
                                                                                              <country id="1"></country>
                                                                                    </root>;
                        public function XmlAttributes()
                                  super();
                                  var result:XML = depthFirstSearch(xml);
                                  trace(result.localName());
                        public function depthFirstSearch(node:XML):XML
                                  for each (var child:XML in node.children())
                                            if (("@id" in child) && (child.@id == "0_0_0_1"))
                                                      return child;
                                            else
                                                      var result:XML = depthFirstSearch(child);
                                                      if(result)
                                                                return result;
                                  return null;
    The XML tags in the code example above are being stripped - not sure why they cannot be encoded / escaped.  It is the XML from your example.

  • Default model search attributes

    Hi guys,
    Using JDeveloper 11.1.1.6 and JHeadstart 11.1.1.4.26.
    I'm having problems with the default model search component. As per section 7.1.2 of the JHS Developers guide, I have "not specified any view criteria which results in a default search where the user can select all attributes that have "Queryable" checked in the view object attribute editor".
    This works fine until I need to change the queryable status of some of the view attributes. Even after unselecting the queryable attribute in the view object, the attribute is still being shown in the quick and advanced search fields. I have tried deleting the page/page def/task flow etc and regenerating but the original attributes always remain in the search area. This seems to work ok for view objects based on entities but does not for non-entity view objects.
    I can see in the pageDef that the searchregion component has an attribute "Criteria" populated with "__ImplicitViewCriteria__". How does this criteria get populated ? And why do my original attributes remain in the search fields even though they no longer are specified as "queryable" in the view object.
    I'm tearing my hair out trying to get these old fields to disappear from the search components - HELP !
    Cheers,
    Brent

    Brent,
    Can you create a drag and drop page without JHeadstart on the same VO?
    Do you get the same behavior? If so, you might try the JDeveloper forum, maybe it is a known issue.
    Steven Davelaar,
    JHeadstart Team.

  • Ldap search attribut result "cn=Klaus", I want this only "Klaus"

    Hello,
    of course i could remove the position 0-2 from the String "cn=Klaus" to get a substring like "Klaus" but i don`t wanna use an extra "for loop" if there maybe exists another possibility to get a clean output like "Klaus"
    someone knows an ldap method to get ONLY the pure value of the cn attribute?

    A picture says more then 1000 words ;-)
    http://666kb.com/i/aq0uxeznt366h8z2b.jpg
    check out my both JList filled with return attribut "cn"
    The full string always has the "cn:" included which i have to remove with the following code:
    String realCN = attrb.toString().substring(4);
    well this line of code doesnt matter much but well its additional work :D

  • Help needed in enhancing Search attribute Created at - Parameters

    Hi All,
    I am facing a strange issue in enhancing search criteria maintained for sales contracts search.
    I have brought in CREATED AT Field. By default, it is diplaying only IS Option in WEB UI. as per the req, we should display Contains, Does not contain, is on or earlier than etc.
    for this we identified the Maintenance view table, CRMC_DQ_ATTROP and selected the needed values by ticking the needed options. Now the parameters displayed on UI are coming as expected but Search is not working with these parameters.
    Any idea on this will be of great help.
    Thanks,
    udaya

    Hi,
    I do not have the time to research this completely, but I had a short look into the class you posted.
    In the GET_DYNAMIC_QUERY_RESULT there is a call to CL_CRM_QCOD_HELPER->PREPROCESS( )
    A little bit lower there are blocks marked by comments for the single searches that are handled by this class. I had a look into the campaign_serach() method. There if you scroll a little bit down (around line 123) they set all search parameters to SIGN = 'I' OPTION = 'EQ'. This is done several times below as well.
    Set a breakpoint in the proprocess() method and check which of the blocks is called and how they handle your search criteria.
    Hope it helps.
    cheers Carsten

  • Page search attributes

    Hi,
    Can anyone tell me what is actually searched by a basic search for pages? I can't find this in the docs.
    I have set up a search which returns pages (not items) and I expected it to find all pages displaying the word I search for.
    It finds them in item content and (I think) in display names, but not in item descriptions, even though the descriptions are displayed on the page.
    Can I tell it to include item descriptions in the search?
    Rob

    hi robert,
    if you are just displayin pages as your search results and you are searching for a search term only the page metadata is searched. e.g. display name, description, etc.
    no item metadata or content is searched if you are displaying the pages (search results tab).
    i guess what you want to do is searching for an item but rerturn the page where this item lives.
    to achieve this please check out the following technote:
    http://www.oracle.com/technology/products/ias/portal/pdf/cm_search_10g_associated_functions_search.pdf
    one other possibility is using ultrasearch which is an enterprise search engine that also can search the portal repository.
    find more on ultra search on OTN:
    http://www.oracle.com/technology/products/ultrasearch/content2.html
    regards,
    christian

Maybe you are looking for