Index management in TREX

Hello all,
We have a webshop running and are using TREX for the product catalog. The catalog is replicated from ECC using program ISA_CATALOG_REPLICATION.
Something seems to have gone wrong since there are a lot of indexes on TREX where there should only be a few. I'd like to cleanup the indixes on TREX. This can be done from the administration tool, but then ECC will not be notified and ECC will expect indexes on TREX that are no longer there. This will result in unsuccessfull replications as the cleanup will not work. If I do the cleanup from ECC using SRMO, I'd have to delete about 1900 indices manually. This would take about two years of my time
The big question: is there a way to cleanup these indexes, and keep ECC and TREX in sync? A mass maintenance tool of some sort maybe?
kind regards, Wilbert

Hi Wilbert,
The admin tool in ISA you are using is owned by ISA, right?
That would mean you'd have to inquire there, if a mass deletion is possible - which it should, as TREX itself can handle as you can tell by the fact that the application-independent TREX Admin Tool gives you the option.
Best,
Karsten

Similar Messages

  • The index management service is not running

    Im in the process of creating a web repository  with the following version history
    Version History
    6.0.2.4.3_ContentManagement_Collaboration
    6.0.2.3.5.Enterprise_Portal_Service_Pack_2
    If finished creating the crawler profile, cache, website, sytem,repository.
    when i  go to index admin i get the error 'The index management service is not running '
    tried restarting the servlet engine, the trex server -the error still persists.
    is there any tool/note for correcting this.
    any help apreciated
    prasad badal

    Hello Karsten,
    thank You for your reply.
    We have a lot of entries in our knowledgement.log files as the following:
    #1.5#C000AC17158E0004000004AB005FCB470003E52BC02E9648#1096401000765#com.sapportals.wcm.service.indexmanagement.TaskQueueReaderTask#irj#com.sapportals.wcm.service.indexmanagement.TaskQueueReaderTask#System#0#####com.sapportals.wcm.scheduler##0#0#Error##Plain###null - java.lang.NullPointerException
         at com.sapportals.wcm.service.indexmanagement.TaskQueueReaderTask.run(TaskQueueReaderTask.java:33)
         at com.sapportals.wcm.service.scheduler.wcm.SchedulerEntry.run(SchedulerEntry.java:332)
         at com.sapportals.wcm.service.scheduler.wcm.Scheduler.run(Scheduler.java:367)
         at com.sapportals.wcm.util.factories.ThreadUtils$InternalFixedTimer.run(ThreadUtils.java:91)
         at java.lang.Thread.run(Thread.java:479)
    Do you know what to do?
    Thanks a lot

  • How to display the index generated by TREX?

    We have a need to display the indexes generate by TREX for SM7.0 KM and EP7.0 KM.
    Please help tell how to do it?
    Thanks a lot!

    Hi Ashley jo,
    Well, the above would not help in OS level.
    The Design is, TREX always stores the indexed pointers to the actual data in it's database rather OS level.
    But at OS level, you can find details about how TREX has been configured and managed.
    The typical path would be <Drive>:\usr\sap\<SID>\TRX<Instance number>\<Host name>
    In this path, you find all *.ini files which contains the configuration details apart from regular 'work', 'log', 'trace' directories.
    Regards
    Sekhar

  • Index management web service

    Hi im trying to use Index management web service from a Web dynpro
    Have some one any code example  using searchFirstChunkInFolders function?? this function only works in folders indexed by some TREX index??
    Regards

    Hi Subrato,
    in my opinion that's not correct. In fact it's the crawler service itself that needs the internalIndexDocuments() mathod's implementation.
    So if no crawler was assigned to the index, no problem should arise, as no call to this method should occur. On the other hand, the exception is thrown and this meens that the method is indeed called by someone!
    What I can't figure out is which crawler, since none is actually set for that index!
    Cheers, Davide

  • Improving Index Management

    Which DBCC commands will improve index management performance?

    because I dont know how exactly index management works with DBCC commands . previously i knew 'ALTER INDEX index_name ON tablename rebuild' or reorganize command for index management . but which is more efficient alter index command or dbcc command ?
    Hi wahid.maruf,
    According to your description, the DBCC command is a consistency checker utility inside of SQL Server , whereas ALTER is a DDL SQL command. The DBCC REINDEX command was deprecated in a previous version so it is not as robust as the new ALTER INDEX command
    is today. There is more functionality in the ALTER INDEX than the DBCC REINDEX commands.
    For more information about ALTER INDEX, you can review the following article.
    http://msdn.microsoft.com/en-us/library/ms188388.aspx
    Regards,
    Sofiya Li
    Sofiya Li
    TechNet Community Support

  • Talent Management - TM - Trex 7.1 - Delta Indexing

    luke.....are you out there??
    congrats on your blog being featured right on the SDN homepage... very nice...
    http://scn.sap.com/community/erp/hcm/blog/2010/09/20/setting-up-netweaver-embedded-search-trex-for-sap-ehp4-talent-management
    and congrats to Chris on his first two excellent blogs....
    http://scn.sap.com/people/chris.mcnarney/blog/2010/08/26/whats-included-with-the-predefined-performance-management-process
    http://scn.sap.com/people/chris.mcnarney/blog/2010/09/09/whats-included-with-the-predefined-performance-management-process--part-2
    all 3 blogs are very helpful since there is little information available out there on these topics...
    so we've been testing the delta indexing program very heavily - ESH_IX_PROCESS_CHANGE_POINTERS
    we have found that it does not appear to be able to index new hires (new central_person index does not pick up the new CP).  The only way this data can be indexed is by running a full re-index.  That is problematic for us, b/c we were hoping to only do full re-indexing 1 a week or even 1 a month.  our indexes take 2-3 hrs to complete and trex searching is pretty much inoperable during that time. 
    Have you tested new hires with delta indexing?  it seems as a gap in the change_pointers program.  We opened up OSS message to SAP. 
    some additional thoughts working with the program, relative to your blog.  I would highly recommend that anyone testing this makes sure the following notes are implemented in your system.  The first one is the most recent and we ourselves did not have that implemented.   
    1. 0.350 BC-EIM-ESH 1441190  Error in model assignments to logical system 24.02.2010
      2. 0.230 BC-EIM-ESH 1408655  Alerts in syntax check due to unused indexes 18.11.2009
      3. 0.260 PA-TM 1395703  Positions and termination are missing for indexing 30.10.2009
      4. 0.330 BC-EIM-ESH 1249482  Functional corrections for Enterprise Search 7.01 SP03 26.01.2009
    Another area which we found from testing:  SAP by default does not delta index structural authority view.  What this means is that if a new talent specialist is added with 741 relationship there access to see that structure will not be available in TREX search by default delta indexing.  This would also impact existing organizations and positions shifted under existing 741 relationships. 
    The information in spro is actually quite helpful, you can find it in:  talent management and talent development > basic settings > search > BAdI: Activate Delta Indexing for Authorization Data
    Activtate the BADI, than the program to "create the change pointers" must run periodically in your system.  This is done with RPTMC_CREATE_CHANGEPOINT_AUTH.  Once that program creates the change pointers the next time your scheduled delta program runs (ESH_IX_PROCESS_CHANGE_POINTERS) all of the structural auths will be created and indexed correctly.
    If we can just now get new hires to work with ESH_IX_PROCESS_CHANGE_POINTERS we will probably only run the full re-index once a week or once a month. 
    Let me know your thoughts,
    Michael
    Message was edited by: Luke Marson
    Message was edited by: Luke Marson

    so if anyone is interested, from my previous post I mentioned that new hires were not getting picked up by the change pointers program.
    after further testing though, we found that when the authorization recon program identifies the new hires and appropriately creates a change pointer. 
    conclusion: to avoid full re-indexing of trex indexes, perform the following steps:
    1.  implement / activate the BADI - HRTMC_AUTHORITY_VIEW - talent management -> basic settings -> search
    2.  Schedule program RPTMC_CREATE_CHANGEPOINT_AUTH - every 30 mins, or 1 or 2 hr.  This program will capture whenever anything changes from an authorization data perspective.  This would include identifiying new central persons (new hires) or new TMC specialist being setup with 741 relationship.  This program "creates change pointers" which than feeds the main delta program - ESH_IX_PROCESS_CHANGE_POINTERS.
    3.  Use Luke's blog on the instructions for the delta program - ESH_IX_PROCESS_CHANGE_POINTERS - this program you can have run every 5 mins, 10 mins, 15 mins, based on your needs.  this processes all delta changes, the first time the program runs after the RPTMC_CREATE_CHANGEPOINT_AUTH program finishes it will also processes the data authorization changes, otherwise every other time the program is running it will catch non-data authorization for all the other indexes (employee name change, new performance rating, new potential, position name change, new profiiciency scale, new career profile data, etc). 
    hope this helps somebody!
    michael
    Edited by: Michael L Pappis on Oct 7, 2010 12:05 AM

  • PCD Index Error in Trex Search

    Dear all
    I have tried to configure as mentioned in the URL
    <b>Configuring the Search for Portal Pages and iViews</b>
    http://help.sap.com/saphelp_nw04/helpdata/en/b2/d59a4271c80a31e10000000a1550b0/frameset.htm .
    I am getting the following error.
    <i><b>Search Failure</b></i>
    <i>Error during search occurred – com.sapportals.wcm.WcmException
    An unexpected severe error occurred during the search call.  If the situation persists, inform your system administrator.</i>
    When I remove the index which is created for the PCD and created dummy index for any of the KM folder then its work fine.This scenario is working fine for the administrator and it is not working for the anonymous users.
    Can anybody help in this...
    Regards
    Geogi

    Hi Robert,
    Thanks for your reply.I have done the same way U mentioned in the last reply.
    I have changed the https host name to http,then restarted servlet engine and trex server.After that i have done re-indexing on my particular repository.
    Now it is showing the below status:
    <b>return code :8005
    Time out reached
    To be preprocessed: 780
    Document status: To be preprocessed and preparation failed
    indexed : 175
    Errors :315(preparation failed).</b>its taking too much time to re-index and now errors are going on increasing.
    shall I remove the full alternate host name and delete the old index and create new index.will it work?
    what is the solution for the above condition?
    Waiting for your reply.
    Thanks in Advance
    Amit kumar koyal

  • XCrawlerException on Index creation in TREX

    Hello All,
    We're using EP6 NW04 SP9. TREX 6.1. Database Oracle.
    I've created an index for the KM from 'Index Administrator', that doesn't work. It's a very simple index, called <b>MyIndex</b> and searching only a folder, /documents/Public Documents/hcl, that contains a few text files that I've created.
    I've checked the application log and found this error:
    <b>Failed to create crawler task MyIndex_documents - com.sapportals.wcm.service.xcrawler.XCrawlerException: The SQL statement "SELECT "XCRW_TASK_INDEX" FROM "KMC_XCRW_TASKS" WHERE "XCRW_TASK_ID" = ?" contains the semantics error[s]: type check error: the exp</b>
    does it make sense to any of you?
    On search it is not able to search any documents that is already present under it.
    Any help will be greatly appreciated,
    Indraneel

    Hi Indraneel,
    Check this thread..
    https://forums.sdn.sap.com/thread.jspa?threadID=195694&tstart=0
    Hope this helps.
    Regards,
    Venkat.

  • Where are TREX index stored? TREX server File system? or KM repository?

    hi, friends:
    can  someone tell me where are TREX index stored ?
    in TREX server file system?
    or in portal KM repository? file system or DB?
    thank you
    Carol

    Carol,
    TREX is a separate product. During installation and configuration of TREX you connect it to the portal. The search iViews of the portal will use the configured TREX server to do the actual search:
    SAP Help: http://help.sap.com/saphelp_nw70/helpdata/EN/a4/929d4206b70931e10000000a1550b0/content.htm
    The index is stored on the TREX server: TREX/IndexServer/basepath/index=%(SAP_RETRIEVAL_PATH)/index
    SAP Help: http://help.sap.com/saphelp_nw70/helpdata/EN/4c/d91e40777cdd5fe10000000a155106/content.htm
    br,
    Tobias

  • How to create index category for TREX in ECC for E-recruiting

    Hi guys,
       i have finished the settings in SKPR07 transaction for SSR and attached to the HR_KW the SSR id.
       But i don't know how to create or generate the index category.
       From the posts of this forum someone told me to regenerate the index in SKPR07 , but i failed.
       Can anyone show me the way?
       Thanks in advance.
        sheery

    The solution is so simple you want to kick yourself....
    You need to upload a document. The index catagory is created automatically. I recommend simply adding an attachment to a candidates profile.
    ;p)

  • Is TREX mandatory for Talent Management?

    Dear Experts,
    Is TREX a mandatory component for Talent Management? It's because I am having issue when I click "Search" in Talent Management Specialist Launchpad, telling me "Error occurred during the search; contact your system administrator".
    And it seems to me that TREX supports only LINUX and MaxDB, which is totally out of our company's landscape.
    Thanks,
    Steven

    Hi Steven,
    TREX is the search engine itself. That means Talent management is using enterprise search and enterprise search uses TREX to perform searches and store data.
    Enterprise Search is part of SAP Netweaver ABAP ( also called embedded search ). Enterprise search is responsible to index data from HR to TREX and is responsible to redirect search requests from Talent management to TREX and put back the results back to the UI. It also provides tools to maintain and administer the data models.
    So Enterprise Search is available on your Netweaver ABAP system. But ES uses TREX. That means if you want to get ES up and running you need TREX. (normaly installed on a different box and connexted by RFC to the Netweaver System)
    hope that helps.
    Martin Hastik

  • TREX - Search Talent Management

    Hi All,
    I know that there are many threads on the TREX and have looked at all of them and tried some of the things but i still get the error search not available.
    We have created all search connector in the admin cockpit and have indexed all of them with no errors. All 32 of them are active. I then ran report ESH_TEST_SEARCH to test the searches. All of the objects templates return results except the following:
    HRTMC_AES_DOCUMENTS
    HRTMC_AES_ELEMENTS
    HRTMC_AES_TEMPLATES
    HRTMC_AUTHORITY_VIEW
    HRTMC_CENTRALPERSON
    HRTMC_FUNC_AREA
    HRTMC_JOB
    HRTMC_JOB_FAMILY
    HRTMC_ORG_UNIT
    HRTMC_POSITION
    HRTMC_QUALIFICATION
    HRTMC_REL_CP_JF_744
    HRTMC_REL_CP_Q_032
    HRTMC_TALENT_GROUP
    For most of these templates I get the following error:
    Search Engine Error 29 for DHR310HRTMC_FUNC_AREA : attribute not defined for physical index;index esh:dhr310dhr310hrtmc_func_area~functional_areayy has no attribute 'objid'.
    For the HRTMC_AUTHORITY_VIEW i get no results, it comes back no values and has a yellow traffic light in the Log viewer. In the Job Log in the Admin Cockpit i see the following
    31.05.2011 21:54:23 Object connector DHR310HRTMC_AUTHORITY_VIEW: New status: Indexing
    31.05.2011 21:54:23 The implementing class does not support the iterator by time interface
    31.05.2011 21:54:23 Implementation did not provide any data -> exit indexing
    31.05.2011 21:54:23 Object connector DHR310HRTMC_AUTHORITY_VIEW: New status: Active
    31.05.2011 21:54:23 Job finished
    I also activated BADI HRTMC_AUTHORITY_VIEW_DELTA in the IMG and ran report RPTMC_CREATE_CHANGEPOINT_AUTH. I then scheduled ESH_IX_PROCESS_CHANGE_POINTERS for the HRTMC_AUTHORITY_VIEW, hoping the I would be returned with some results.howver
    I do have a TMS linked to several org units via relation 741 and this is returned in the test search HRTMC_REL_S_O_RESP. In addition if I go to a Talent Review Meeting in the portal and click on 'ADD' to select an org unit, the managers of the Org Units that I am related to appear on the list. However as soon as I select any of them, they are added to the participant list but non of the nominated talents appear, i get the following message:
    'No nominations are displayed since the search is not available'
    for all other searches i get the error 'Search is not available' or 'No Relevant Records Were Found for This Search'
    I Also checked SLG1 logs after attempting the searches and got the following errors:
    2007 for DHR310HRTMC_CENTRALPERSON : NameServer error: no servers found; IndexId:esh:dhr310dhr310hrtmc_centralperson~~sap_talent
    Exception occurred in program CL_ESH_IF_SEARCH_RESPONSE=====CP, include CL_ESH_IF_SEARCH_RESPONSE=====CM006, row 4
    An exception has occurred
    29 for DHR310HRTMC_CENTRALPERSON : attribute not defined for physical index;index esh:dhr310dhr310hrtmc_centralperson~personal_datayy has no attribute 'objid'
    Exception occurred in program CL_ESH_IF_SEARCH_RESPONSE=====CP, include CL_ESH_IF_SEARCH_RESPONSE=====CM006, row 4
    I also tried creating my own serch request using one of the search templates returning results. In this case i used the HRTMC_REL_CP_TB_743 templates with talent group ID as search field and assigned it to one of the search configurations. I then however got the following error.
    The following error text was processed in the system DHR : The ASSERT condition was violated. The error occurred on the application server sivrs106_DHR_00 and in the work process 0 . The termination type was: RABAX_STATE The ABAP call stack was:
    Method: GET_AUTHORIZATION_QUERY of program CL_ESH_IF_SEARCH_REQUEST======CP
    Method: SEARCH_ONE_CONNECTOR of program CL_ESH_IF_SEARCH_REQUEST======CP
    Method: SEARCH of program CL_ESH_IF_SEARCH_REQUEST======CP
    Method: CONSTRUCTOR of program CL_HRTMC_SEARCH_REQUEST=======CP
    Method: GET_INSTANCE of program CL_HRTMC_SEARCH_REQUEST=======CP
    Method: TRIGGER_SIMPLE_SEARCH of program CL_HRTMC_AC_SEARCH============CP
    Method: ONACTIONSTART_SEARCH of program /1BCWDY/JUNQ9FJYULV16JASJHWU==CP
    Method: IF_WDR_VIEW_DELEGATE~WD_INVOKE_EVENT_HANDLER of program /1BCWDY/JUNQ9FJYULV16JASJHWU==CP
    Method: INVOKE_EVENTHANDLER of program CL_WDR_DELEGATING_VIEW========CP
    Method: IF_WDR_ACTION~FIRE of program CL_WDR_ACTION=================
    Anyone have any ideas on how i can resolve this.
    Apologies for posting such a long thread, just trying to provide full picture.
    Regards
    Imraan

    Hi Imraan,
    You should be congratulated on a thorough post! What version and revision of TREX are you using? You should use TREX 7.1 revision 16 or higher. You should also review the PA-TM SAP notes for TREX. I would recommend reviewing some of the following (some you might need to come back to later):
    u2022     1376055 - ESH_ADM_INDEX_ALL_SC: Exception in step 2: Create
    u2022     1384953 - ESH: Error message 'A connection already exists' in cockpit
    u2022     1437946 - TMC search: Frequently asked questions
    u2022     1441190 - Error in model assignments to logical system
    u2022     1457940 - Transporting software components: Error in after-import
    u2022     1476894 - Transporting software components: Paths are lost
    u2022     1483890 - Importing software components directly to target client
    u2022     1492752 - Program to create a join index retroactively
    u2022     1502296 - Too few ESH_OM_LOGSYSA entries after creating a connector
    u2022     1538688 - Indexing Log: Warning "Object 'nw_esh_tst_auto' not ..."
    u2022     1516237 - TMC search: Long runtime for indexing of HRTMC_REL_S_Q_031
    u2022     1518396 - Indexes are not filled after TREX conversion
    u2022     1520538 - TMC search: Performance for extraction of documents
    u2022     1523648 - The search does not find any hits
    u2022     1526710 - TMC search: Error during position switch by TMS
    u2022     1529878 - Performance of authorization indexing
    u2022     1534172 - TREX 7.10: Revision 42
    u2022     1536663 - TMC search: Long runtime during indexing HRTMC_REL_SC_JF_FN
    u2022     1536656 - Missing search attr for person search in Succession Planning
    u2022     1540869 - TMC search authorization indexing with initial user ID
    u2022     1541984 - Search connectors are not found
    u2022     1542741 - Deleting connections
    u2022     1550964 - TMC srch: Qualification srch criteria for CP-Q relationship
    u2022     1551029 - TMC: Incorrect authorization check for PA infotypes
    u2022     1554061 - TMC search: Error in search fields for job evaluation
    u2022     1555950 - Indexing of HRTMC_AUTHORITY_VIEW: Data packages are too big
    u2022     1558355 - TMC search: Empls. that have left company in search result
    u2022     1560966 - TMC search: Error message when copying search configurations
    u2022     1561070 - Termination when saving after deleting system assignments
    u2022     1562742 - TMS / Search: Indexing fails with HRTMC_REL_S_MANAGER
    u2022     1568563 - TMC search: Error when setting up authorization index
    u2022     1567065 - TMC search: Simplifying the authorization indexing
    u2022     1575454 - TMC search: Performance during CP indexing
    u2022     1584309 - TMC search: Change pointer for newly created org. units
    Also, did you follow these steps once TREX was connected?
    [/people/luke.marson/blog/2010/09/20/setting-up-netweaver-embedded-search-trex-for-sap-ehp4-talent-management]
    Best regards,
    Luke

  • Trex Indexing giving HTTP Status Code 401:Unauthorized error

    Dear All,
    We have configured TREX search on KM repository of our EP
    production server and trying to search using the same our KM repository.
    The TREX is installed on the a separate server.
    When we try to Index production repository the documents are failing in
    the Preparation failed status with return code 6401 and error message
    HTTP Status Code 401: Unauthorized.
    I also applied SAP-Note 650521 and checked id index_service user and
    found that its active and not locked but still issue didnu2019t get
    resolved. Moreover i have gone thru most of the previous post regarding this topic but didt help.
    I even checked the URL Generator service too which is fine.
    On one test system also where SPNego is configured we are getting same
    401 error. On this system we disabled SPnego and Indexing started working
    fine. When we reverted back the SPNego configuration for confirmation of
    our observation we found that it again started to give 401 error.
    Any help in this regard will be appreciated.
    Regards,
    Srinath Pillai
    Edited by: Srinath Pillai on Sep 3, 2009 8:59 AM

    Dear
    Open System Administration--> System Configuration> Knowledge Management--> Content Management> Global Services (Mode : Advanced)> Index Management Service--> Check for Crawling Service User  it has to be index_service
    If still you have problem than do let me know where is your Repository located are the documents are stored on Portal Server itself or it is stored on some external server...
    What kind of repository you use CM Repository(Mode:DB,DBFS,FSDB) , File System Repository....e.t.c....
    Regards
    Akshit

  • TREX: indexing problem

    Hi,
    I'm trying to configure TREX in our portal. I've created an index (search index) and I've assigned data to index (html files and pdf files).
    When I test the indexing process in the TREX Monitor, I always see that some pdf files aren't indexed. I assign them to index again and again, but they aren't indexed. I get "Preparation Failed" for these documents and the indexing process doesn't continue (it seems that it stops).
    What can it be the cause?
    Thanks in advance,
    Samantha.

    Hi,
    There is no need to create new repository. You can add that folder as "Data Source" to Index. Then all files and folders under that folder will automatically indexed.
    Please follow the below steps.
    1. Create a new Index.
    2. Add folder (Whatever you created) as "Data Source" to index.
    3. Save data source.
    Now you can get all your documents indexed.
    Here note one points. You will not get all the documents indexed immidiately. This will depend on your TREX load.
    Other wise if you want it immediately flush the particular index.
    1. Logon to portal as Administrator
    2. Navigate to 'System Administrator' -> Monitoring -> Knowledge Management -> Cache Monitor
    3. Note the System ID of you local system from combo box under System ID
    4. Navigate to System Administration -> System Configuration -> Knowledge Management -> Content Management -> Global Service -> System Landscape Definations -> Systems -> Content Management System
    5. Check that the same System ID Should be there. If not there please add it by clicking on button 'New'
    6. Navigate to System Administration -> System Configuration -> Knowledge Management -> Content Management -> Global Service ->Scheduler Tasks -> Index Management Task Queue Reader
    7. Open "IndexServiceTaskQueueReader" for editing
    8. Add the same system ID under "System ID"
    I think this will solve your problem
    Regards,
    Senthil kumar K.

  • Using a ABAP SES TREX Index in KM

    Dear Experts i have created a TREX index with transaction SES_ADMIN for data from the ABAP stack. Is it possible to use this index in EP with KM? The index is created in ABAP Stack and is available in TREX Administration tool.
    I am hoping it is possible to manage this index with KM please tell me how this is possible.
    Regards.
    Martijn

    Hi Martijn,
           No, you must create index in KM Portal. Then if you have integrated stack ABAP with TREX, you can see and manage all created indexes.
          Using TREX you also index ABAP, SAP PI or BI. It's very easy to do.
    Regards,
    Patricio.

Maybe you are looking for

  • Audit Vault Installation problem on windows platform

    Hello! I'm trying to install Audit Vault 10.2.2 on windows platform. The installation procedure is successfull (there are no alerts about errors during installation). The enterprise manager is working at http://localhost:1158/em without any problem.

  • Keep getting Kernel panics on Snow leopard 10.6.3

    I recently messed up my leopard install... long story. When restoring the system I decided to go with Snow leopard, thought why not, would like to become more familiar with it. Ever since I got it I have been getting Kernel Panics out the wazoo. I ha

  • WebUtil file transfer in multiple user implementation

    Hi Installed WebUtil and able to integrate forms/reports in Web enviroenment 10gAs. Around 30 to 40 people will use this application, Now to do client side integration (To Save generated output to Cleint m/c) we are geerating file on AppServer and tr

  • Issue with installing password sync on Windows 2008

    I have installed pwd sync 64 bit on Windows 2008. Configured it in direct mode (no jms). But when I change the password of a user it is not syncing with the IdM. We have the 32 bit pwd sync working fine on Win 2003. Is there any special steps for ins

  • Problem with Delta Links

    I have : - a standard Workset with pages that are delta-linked to standard pages (nothing extraordinary so far...) - a delta-link copy of that Workset Consequently, the pages in my Workset are linked to pages in the standard Workset (themselves delta