Snapshot creation

i want talk between two oracle server. i decided to go for snapshot creation with periodical refresh. For which i am having two oracle server's with different ip address located inside our office setup.
I have created a database link between two servers.
first server name global
userid scott
password tiger
second server name asil
userid scott
password tiger
both the user have been given dba rights.
in both the server the services and listners are all started. i gave the following command to create database link.
from asil server
create public database link global connect by scott identified by tiger using 'global'
the command was successful and the link was created. Now i tried to access a table of the scott user of the global server.
select * from emp@global;
now it is giving error. I want to know how the link can be created and how it can be accessed. i refered the 8i online documentation and done the things based on that. i expect valuble solution from all possible persons
null

CREATE SNAPSHOT [schema.]snapshot
[ [PCTFREE  integer] [PCTUSED  integer]
[INITRANS integer] [MAXTRANS integer]
[TABLESPACE tablespace]
[STORAGE storage_clause]
[ USING INDEX [  PCTFREE integer | TABLESPACE tablespace
| INITTRANS integer | MAXTRANS integer
| STORAGE storage_clause ] ...
| [CLUSTER cluster (column [, column]...)] ]
[ REFRESH [FAST | COMPLETE | FORCE] [START WITH date] [NEXT date]]
AS subquery
According to documentation create should look like this
CREATE SNAPSHOT test.check tablespace tablespace_name REFRESH FAST START WITH SYSDATE NEXT trunc(SYSDATE + 1) + 2.5/24 WITH ROWID AS SELECT * FROM wpol.test.check@PROD;

Similar Messages

  • Creation of Database link and access the same plus Snapshot creation

    i want talk between two oracle server. i decided to go for snapshot creation with periodical refresh. For which i am having two oracle server's with different ip address located inside our office setup.
    I have created a database link between two servers.
    first server name global
    userid scott
    password tiger
    second server name asil
    userid scott
    password tiger
    both the user have been given dba rights.
    in both the server the services and listners are all started. i gave the following command to create database link.
    from asil server
    create public database link global connect by scott identified by tiger using 'global'
    the command was successful and the link was created. Now i tried to access a table of the scott user of the global server.
    select * from emp@global;
    now it is giving error. I want to know how the link can be created and how it can be accessed. i refered the 8i online documentation and done the things based on that. i expect valuble solution from all possible persons
    null

    A reason for this problem could be that your database is configured that a database link has to have exactly the same name like the global name of the database instance it should connect to.
    Can you please provide the oracle error code / message ? With this information there might be more hints I can give you.

  • Error occured during creation of oracle snapshot

    Dear All,
    I am getting error messange in my SAP Inbox in t.code SBWP.
    In SBWP, the nessage text is as follow.
    =============================
    Error occured during creation of oracle snapshot (Creation aborted)
    (Log see also transaction SLG1, Object ORASNAP, Subobject ORASNAPCR)
    Oracle snapshot creation program aborted
    Error while copying from oracle view to SAP table
    Oracle view SAP$KCBFWAIT
    SAP table ORA_SAPKCBFWAIT
    Return code (ORA-....) 942
    You tried to work with the name of a table or view that does not exist in the database
    The table does not exist on the database. A table name or view name was used that does not exist on                           the database.
    ===============================
    I also check in T.Code SLG1, but i am not getting the reason for this error.
    Regards,
    Nisit

    Hi,
    Check each of the following :
    the spelling of the table or view name.
    that a view is not specified where a table is required.
    that an existing table or view name exists.
    Contact the database administrator if the table needs to be created or if user or application privileges are required to access the table.
    Also, if attempting to access a table or view in another schema, make certain the correct schema is referenced and that access to the object is granted.
    Regards
    Krishna

  • Database Link Creation and Acessing

    i want to talk between two oracle server. i decided to go for snapshot creation with periodical refresh. For which i am having two oracle server's with different ip address located inside our office setup.
    I have created a database link between two servers.
    first server name global
    userid scott
    password tiger
    second server name asil
    userid scott
    password tiger
    both the user have been given dba rights.
    in both the server the services and listners are all started. i gave the following command to create database link.
    from asil server
    create public database link global connect by scott identified by tiger using 'global'
    the command was successful and the link was created. Now i tried to access a table of the scott user of the global server.
    select * from emp@global;
    now it is giving error. I want to know how the link can be created and how it can be accessed. i refered the 8i online documentation and done the things based on that. i expect valuble solution from all possible persons
    null

    See link http://kr.forums.oracle.com/forums/thread.jspa?threadID=221081
    Hope this helps solve your issue.
    thanks
    http://swervedba.wordpress.com/

  • Do not want new version for rdl file for each snapshot rendering

    ssrs 2012 sp1 sharepoint mode, sharepoint 2013
    option set for the report - render from snapshot, a schedule set for the snapshots creation
    each snapshot rendering adds new viersion to the rdl file with updated field
    Execution DateTime - not really sure who needs this "feature" but it would be nice to switch this off/fix a bug
    Sergey Vdovin

    Hi Sergey,
    Sorry for my misunderstanding.
    In SharePoint, the generation of a report version is determined by the modifications of the entire SharePoint list item. If any field of the list item is changed , it will create a new version for the list item. For a report RDL file uploaded to a SharePoint
    document library, the report version is not just created based on the modifications to the report content. In your case, once it has generating a new snapshot, it will modify the column Execution DateTime value.
    Besides, once we configure a report to render based on a snapshot, the Execution Datatime field will be available in the library view. However, if we create snapshots manually rather than based on a schedule, this field won’t be updated, hence, the report
    version won’t be added. If we configure the snapshot to be generated based on a schedule, the Execution Datetime will be updated each time the snapshot is generated, thus the report version will be updated. This is actually a by design inconsistent behavior
    between Reporting Services and SharePoint.
    To avoid this behavior,  on Reporting Services side, you need to either disable the snapshot or configure the snapshot not to run based on a schedule. Taking into account that this may be unacceptable for your, there is a possible approach on the SharePoint
    side. In SharePoint, if we want an item to update without creating a new version based on a judgment condition, we can use Visual Studio workflow and with a code to determine when to update list item. Here is some resource about this topic for your refer:
    http://social.msdn.microsoft.com/Forums/sharepoint/en-US/750658ca-5a5d-49cb-99c2-70335fd5375b/updating-an-item-in-list-with-out-creating-a-version?forum=sharepointdevelopmentprevious
    http://www.codegain.com/articles/sharepoint/developmentprogramming/what-is-the-difference-between-splistitem-systemupdate-and-splistitem-update-method.aspx
    Since the approach is related to SharePoint development, if you need more help, I recommend you post a question in the following forum to get dedicated support:
    http://social.msdn.microsoft.com/Forums/sharepoint/en-US/home?forum=sharepointdevelopmentprevious
    Best Regards,
    Alisa Tang
    If you have any feedback on our support, please click
    here.
    Alisa Tang
    TechNet Community Support

  • Snapshot taking a very long time to generate

    Hi
    Im trying to create a snapshot. I started the snapshot creation at around 1 pm and now after 7 hours the snapshot creation is still not completed. Is this normal. I mean does it take so much time to create a snapshot?
    FYI
    My Project has around 80 mappings and 12 Process flows. The MDL file size is around 12 MB.
    Regards
    Vibhuti

    Hi Bharath
    Thanks for replying.
    I did not use any query. I just used the Create Snapshot feature of OWB. however after 12 hours it gave the following error
    ORA-30036: unable to extend segment by 8 in undo tablespace 'UNDOTBS1'
    ORA-06512: at "SPRO_OWNER.SNAPSHOT", line 937
    ORA-06512: at "SPRO_OWNER.SNAPSHOT", line 991
    ORA-06512: at "SPRO_OWNER.SNAPSHOT", line 1169
    ORA-06512: at "SPRO_OWNER.SNAPSHOT", line 1316
    ORA-06512: at "SPRO_OWNER.SNAPSHOT", line 1365
    ORA-06512: at "SPRO_OWNER.SNAPSHOT", line 1400
    ORA-06512: at "SPRO_OWNER.SNAPSHOT", line 2315
    ORA-06512: at line 1
    ORA-30036: unable to extend segment by 8 in undo tablespace 'UNDOTBS1'
    ORA-06512: at "SPRO_OWNER.SNAPSHOT", line 937
    ORA-06512: at "SPRO_OWNER.SNAPSHOT", line 991
    ORA-06512: at "SPRO_OWNER.SNAPSHOT", line 1169
    ORA-06512: at "SPRO_OWNER.SNAPSHOT", line 1316
    ORA-06512: at "SPRO_OWNER.SNAPSHOT", line 1365
    ORA-06512: at "SPRO_OWNER.SNAPSHOT", line 1400
    ORA-06512: at "SPRO_OWNER.SNAPSHOT", line 2315
    ORA-06512: at line 1
         at oracle.wh.repos.pdl.mcm.MCMUtils.executeStoredProcedure(MCMUtils.java:76)     at oracle.wh.repos.pdl.mcm.MCMUtils.executeStoredProcedure(MCMUtils.java:31)     at oracle.wh.repos.pdl.mcm.MCMServiceImpl.takeSnapshot(MCMServiceImpl.java:1086)     at oracle.wh.repos.pdl.mcm.MCMServiceImpl.takeSnapshot(MCMServiceImpl.java:932)     at oracle.wh.repos.pdl.mcm.MCMServiceImpl.createSnapshotWithDependeeComponents(MCMServiceImpl.java:602)     at oracle.wh.ui.mcm.CreateSnapshotWizard$CreateSnapshotAction.run(CreateSnapshotWizard.java:550)     at oracle.wh.ui.mcm.Task.run(Task.java:45)     at java.lang.Thread.run(Thread.java:534)
    What is this error mean?
    Regards
    Vibhuti

  • Problem Automatic Workload Repository after upgrage to 10.1.0.4.0

    Hello everybody,
    We upgraded last week a database 10g from release 10.1.0.3.0 to 10.1.0.4.0.
    Since this upgrade, the AWR doesn't create any snapshot anymore but the process MMON is still living.
    I tried to modify the interval of creation (reduce from 1H to 30min) of the snapshot using EM. When I execute the command I receive the following error statement:
    Please correct the following error:ORA-13516: SWRF Operation failed: CATPROC not valid ORA-06512: at "SYS.DBMS_WORKLOAD_REPOSITORY", line 83 ORA-06512: at line 1
    Should I re-execute some script(s) from .../RDBMS/ADMIN to fix it?
    Thank a lot in advance for your support to solve this issue.

    Hopefully I could find a post on the Oracle Forum to fix my issue.
    I did the following operations:
    1) SHUTDOWN IMMEDIATE;
    2) STARTUP UPGRADE;
    3) SQLPLUS / AS SYSDBA
    4) @<Oracle_home>/RDBMS/ADMIN/CATPATCH.SQL
    5) When the script completed check that no errors occured.
    6) SHUTDOWN IMMEDIATE
    7) RESTART
    After this the Automatic Workload Repository could execute normally the snapshots and I was able for exemple to modify the frequence of the snapshots creation.
    I only don't understand why I had to execute this sql script to get in running. Should this script not be a part of execution of the upgrade 10.1.0.3.0 to 10.1.0.4.0 ?

  • Hyper-V cluster Backup causes virtual machine reboots for common Cluster Shared Volumes members.

    I am having a problem where my VMs are rebooting while other VMs that share the same CSV are being backed up. I have provided all the information that I have gather to this point below. If I have missed anything, please let me know.
    My HyperV Cluster configuration:
    5 Node Cluster running 2008R2 Core DataCenter w/SP1. All updates as released by WSUS that will install on a Core installation
    Each Node has 8 NICs configured as follows:
     NIC1 - Management/Campus access (26.x VLAN)
     NIC2 - iSCSI dedicated (22.x VLAN)
     NIC3 - Live Migration (28.x VLAN)
     NIC4 - Heartbeat (20.x VLAN)
     NIC5 - VSwitch (26.x VLAN)
     NIC6 - VSwitch (18.x VLAN)
     NIC7 - VSwitch (27.x VLAN)
     NIC8 - VSwitch (22.x VLAN)
    Following hotfixes additional installed by MS guidance (either while build or when troubleshooting stability issue in Jan 2013)
     KB2531907 - Was installed during original building of cluster
     KB2705759 - Installed during troubleshooting in early Jan2013
     KB2684681 - Installed during troubleshooting in early Jan2013
     KB2685891 - Installed during troubleshooting in early Jan2013
     KB2639032 - Installed during troubleshooting in early Jan2013
    Original cluster build was two hosts with quorum drive. Initial two hosts were HST1 and HST5
    Next host added was HST3, then HST6 and finally HST2.
    NOTE: HST4 hardware was used in different project and HST6 will eventually become HST4
    Validation of cluster comes with warning for following things:
     Updates inconsistent across hosts
      I have tried to manually install "missing" updates and they were not applicable
      Most likely cause is different build times for each machine in cluster
       HST1 and HST5 are both the same level because they were built at same time
       HST3 was not rebuilt from scratch due to time constraints and it actually goes back to Pre-SP1 and has a larger list of updates that others are lacking and hence the inconsistency
       HST6 was built from scratch but has more updates missing than 1 or 5 (10 missing instead of 7)
       HST2 was most recently built and it has the most missing updates (15)
     Storage - List Potential Cluster Disks
      It says there are Persistent Reservations on all 14 of my CSV volumes and thinks they are from another cluster.
      They are removed from the validation set for this reason. These iSCSI volumes/disks were all created new for
      this cluster and have never been a part of any other cluster.
     When I run the Cluster Validation wizard, I get a slew of Event ID 5120 from FailoverClustering. Wording of error:
      Cluster Shared Volume 'Volume12' ('Cluster Disk 13') is no longer available on this node because of
      'STATUS_MEDIA_WRITE_PROTECTED(c00000a2)'. All I/O will temporarily be queued until a path to the
      volume is reestablished.
     Under Storage and Cluster Shared VOlumes in Failover Cluster Manager, all disks show online and there is no negative effect of the errors.
    Cluster Shared Volumes
     We have 14 CSVs that are all iSCSI attached to all 5 hosts. They are housed on an HP P4500G2 (LeftHand) SAN.
     I have limited the number of VMs to no more than 7 per CSV as per best practices documentation from HP/Lefthand
     VMs in each CSV are spread out amonst all 5 hosts (as you would expect)
    Backup software we use is BackupChain from BackupChain.com.
    Problem we are having:
     When backup kicks off for a VM, all VMs on same CSV reboot without warning. This normally happens within seconds of the backup starting
    What have to done to troubleshoot this:
     We have tried rebalancing our backups
      Originally, I had backup jobs scheduled to kick off on Friday or Saturday evening after 9pm
      2 or 3 hosts would be backing up VMs (Serially; one VM per host at a time) each night.
      I changed my backup scheduled so that of my 90 VMs, only one per CSV is backing up at the same time
       I mapped out my Hosts and CSVs and scheduled my backups to run on week nights where each night, there
       is only one VM backed up per CSV. All VMs can be backed up over 5 nights (there are some VMs that don't
       get backed up). I also staggered the start times for each Host so that only one Host would be starting
       in the same timeframe. There was some overlap for Hosts that had backups that ran longer than 1 hour.
      Testing this new schedule did not fix my problem. It only made it more clear. As each backup timeframe
      started, whichever CSV the first VM to start was on would have all of their VMs reboot and come back up.
     I then thought maybe I was overloading the network still so I decided to disable all of the scheduled backup
     and run it manually. Kicking off a backup on a single VM, in most cases, will cause the reboot of common
     CSV members.
     Ok, maybe there is something wrong with my backup software.
      Downloaded a Demo of Veeam and installed it onto my cluster.
      Did a test backup of one VM and I had not problems.
      Did a test backup of a second VM and I had the same problem. All VMs on same CSV rebooted
     Ok, it is not my backup software. Apparently it is VSS. I have looked through various websites. The best troubleshooting
     site I have found for VSS in one place it on BackupChain.com (http://backupchain.com/hyper-v-backup/Troubleshooting.html)
     I have tested almost every process on there list and I will lay out results below:
      1. I have rebooted HST6 and problems still persist
      2. When I run VSSADMIN delete shadows /all, I have no shadows to delete on any of my 5 nodes
       When I run VSSADMIN list writers, I have no error messages on any writers on any node...
      3. When I check the listed registry key, I only have the build in MS VSS writer listed (I am using software VSS)
      4. When I run VSSADMIN Resize ShadowStorge command, there is no shadow storage on any node
      5. I have completed the registration and service cycling on HST6 as laid out here and most of the stuff "errors"
       Only a few of the DLL's actually register.
      6. HyperV Integration Services were reconciled when I worked with MS in early January and I have no indication of
       further issue here.
      7. I did not complete the step to delete the Subscriptions because, again, I have no error messages when I list writers
      8. I removed the Veeam software that I had installed to test (it hadn't added any VSS Writer anyway though)
      9. I can't realistically uninstall my HyperV and test VSS
      10. Already have latest SPs and Updates
      11. This is part of step 5 so I already did this. This seems to be a rehash of various other stratgies
     I have used the VSS Troubleshooter that is part of BackupChain (Ctrl-T) and I get the following error:
      ERROR: Selected writer 'Microsoft Hyper-V VSS Writer' is in failed state!
      - Status: 8 (VSS_WS_FAILED_AT_PREPARE_SNAPSHOT)
      - Writer Failure code: 0x800423f0 (<Unknown error code>)
      - Writer ID: {66841cd4-6ded-4f4b-8f17-fd23f8ddc3de}
      - Instance ID: {d55b6934-1c8d-46ab-a43f-4f997f18dc71}
      VSS snapshot creation failed with result: 8000FFFF
    VSS errors in event viewer. Below are representative errors I have received from various Nodes of my cluster:
    I have various of the below spread out over all hosts except for HST6
    Source: VolSnap, Event ID 10, The shadow copy of volume took too long to install
    Source: VolSnap, Event ID 16, The shadow copies of volume x were aborted because volume y, which contains shadow copy storage for this shadow copy, wa force dismounted.
    Source: VolSnap, Event ID 27, The shadow copies of volume x were aborted during detection because a critical control file could not be opened.
    I only have one instance of each of these and both of the below are from HST3
    Source: VSS, Event ID 12293, Volume Shadow Copy Service error: Error calling a routine on a Shadow Copy Provider {b5946137-7b9f-4925-af80-51abd60b20d5}. Routine details RevertToSnashot [hr = 0x80042302, A Volume Shadow Copy Service component encountered an
    unexpected error.
    Source: VSS, Event ID 8193, Volume Shadow Copy Service error: Unexpected error calling routine GetOverlappedResult.  hr = 0x80070057, The parameter is incorrect.
    So, basically, everything I have tried has resulted in no success towards solving this problem.
    I would appreciate anything assistance that can be provided.
    Thanks,
    Charles J. Palmer
    Wright Flood

    Tim,
    Thanks for the reply. I ran the first two commands and got this:
    Name                                                            
    Role Metric
    Cluster Network 1                                              
    3  10000
    Cluster Network 2 - HeartBeat                              1   1300
    Cluster Network 3 - iSCSI                                    0  10100
    Cluster Network 4 - LiveMigration                         1   1200
    When you look at the properties of each network, this is how I have it configured:
    Cluster Network 1 - Allow cluster network communications on this network and Allow clients to connect through this network (26.x subnet)
    Cluster Network 2 - Allow cluster network communications on this network. New network added while working with Microsoft support last month. (28.x subnet)
    Cluster Network 3 - Do not allow cluster network communications on this network. (22.x subnet)
    Cluster Network 4 - Allow cluster network communications on this network. Existing but not configured to be used by VMs for Live Migration until MS corrected. (20.x subnet)
    Should I modify my metrics further or are the current values sufficient.
    I worked with an MS support rep because my cluster (once I added the 5th host) stopped being able to live migrate VMs and I had VMs host jumping on startup. It was a mess for a couple of days. They had me add the Heartbeat network as part of the solution
    to my problem. There doesn't seem to be anywhere to configure a network specifically for CSV so I would assume it would use (based on my metrics above) Cluster Network 4 and then Cluster Network 2 for CSV communications and would fail back to the Cluster Network
    1 if both 2 and 4 were down/inaccessible.
    As to the iSCSI getting a second NIC, I would love to but management wants separation of our VMs by subnet and role and hence why I need the 4 VSwitch NICs. I would have to look at adding an additional quad port NIC to my servers and I would be having to
    use half height cards for 2 of my 5 servers for that to work.
    But, on that note, it doesn't appear to actually be a bandwidth issue. I can run a backup for a single VM and get nothing on the network card (It caused the reboots before any real data has even started to pass apparently) and still the problem occurs.
    As to Backup Chain, I have been working with the vendor and they are telling my the issue is with VSS. They also say they support CSV as well. If you go to this page (http://backupchain.com/Hyper-V-Backup-Software.html)
    they say they support CSVs. Their tech support has been very helpful but unfortunately, nothing has fixed the problem.
    What is annoying is that every backup doesn't cause a problem. I have a daily backup of one of our machines that runs fine without initiating any additional reboots. But most every other backup job will trigger the VMs on the common CSV to reboot.
    I understood about the updates but I had to "prove" it to the MS tech I was on the phone with and hence I brought it up. I understand on the storage as well. Why give a warning for something that is working though... I think that is just a poor indicator
    that it doesn't explain that in the report.
    At a loss for what else I can do,
    Charles J. Palmer

  • Error with SAP_PERIODIC_ORACLE_SNAPSHOT job in PI 7.1

    Gurus,
    I ma getting a dump in PI7.1 SPS 7
    Oracle snapshot creation program aborted
    Error while copying from oracle view to SAP table
    Oracle view SAP$KCBFWAIT
    SAP table ORA_SAPKCBFWAIT
    Return code (ORA-....) 942
    You tried to work with the name of a table or view that does not exist in the database
    The table does not exist in the database. It was processed with the name of a table or a view that does not exist in the databas
    I checked on the system and this is because of  SAP_PERIODIC_ORACLE_SNAPSHOT  job, I am not getting any information about it anywhere and how it is getting fired up on the system.
    Thanks in advance ..
    Regards,
    Surendra

    Hi,
    It looks like there are some problems in accessing Oracle view SAP$KCBFWAIT. Apply SAP note 159510.

  • Converting Debian 7 ESXi 4.1 to 2012R2 host :

    Hi,
    I'm trying to convert Debian 7 VM to hyper-v using MVMC 2.1. In GUI wizard on  Virtual Machine section, under Operating System there is shown Other Linux (x64) instead of Debian 7. Debian version 5 is show correct (for olders dis. VM), as Debian GNU/Linux
    5 (x64). I suppose that is reason for Warning on Summary screen in Wizard :
    Warning (s):
    1. The operating system of the VMWare VM is NOT SUPPORTED. This does not prevent conversion, but no support is provided for this conversion.
    The tool is running on target Hyper-V 2012R2 host with .NET 4,5 installed along with Visual C++ Redist 2012 update.
    After continuing conversion (ignorring the warning above), conversion stops after sucessfuly snapshot creation on ESXi host with following error :
    "One or more errors occurred. ---> System.IO.FileNotFoundException: Could not load file or assembly 'Microsoft.Accelerators.Mvmc.ScxSshWrapper_x86.dll' or one of its dependencies. The specified module could not be found."
    I also reboot Hyper-V host but same error appears every time .
    Thnx.
    Update#1: I have to install both x64 and x86 Visual Studio Redist 2012 Update 4 to avoid stop error on .dll. The main warning (VM not supported stays).
    Now I have new problem, during Uninstall Tools step conversion stops with message: Host does not Exist. When open error log: there is :
    VERBOSE:    Attempting to establish an SSH connection.
    07/23/2014 17:06:56 +02:00  [3]  VERBOSE:    Finished creating snapshot of the source virtual machine
    07/23/2014 17:06:59 +02:00  [3]  DEBUG:    Caught ManagedSshFacadeException trying to open SSH connection: ErrorCode=0xC0040202, Message=Host does not exist
    07/23/2014 17:07:04 +02:00  [3]  VERBOSE:    System.AggregateException: One or more errors occurred. ---> Microsoft.Accelerators.Mvmc.ScxSshCommon.ManagedSshFacadeException: Host does not exist
    Update#2: Host unknown error was because Debian wasn't in internal DNS of Hyper-V host, after adding Linux to DNS error went away (it seems to use DNS name to establish SSH connection). However after that I received errors in same "Uninstall Tools"
    step about connection rejected because of too many failures for root account... I saw that in the "Connection Step" of wizard I was unable to enter Password for Root account for selected VM, (I don't know is that by design for Linux VM's). So I beleive
    that error is reffering to that stage of setup. Anyhow  I decided to manually remove VM Tools , shutdown VM and convert VM in offline mode. Now VM is working on Hyper-V, and I hope that this few hours of troubleshooting will help someone. After all there
    are still some questions :
    1. Why Warning : 1. The operating system of the VMWare VM is NOT SUPPORTED - is displayed for Debian 7 which is on supported list of guest OS
    2. Why online conversion didn't work, and why password for root account in VM (under Connection portion of wizard) could not be entered.
    If anyone have answers to above question please share your knowledge.
    Regards,

    MVMC 3.0 did not include any new features for Linux so I doubt the results will be different. We did add support for RHEL 7, CentOS 7 and Oracle 7.
    For your questions:
    1 - Since VMWare does not have a specific choice for Deb 7, newer versions may by now, we throw the warning as we cannot determine what version of Linux you are trying to convert when you select [Other Linux X64]. Deb 7 is supported by MVMC as
    we've tested it and know it works. Other Linux distros may work as well that are not supported but they have not been tested.
    2 - Most likely you did not have the VMWare VM running when trying to do the online conversion or it could not be resolved in DNS by the vSphere server. When running the MVMC tool did you notice if it had a DNS name associated with it when you selected
    it in VMWare?
    The MVMC requires the VMWare VM to be in a running state and resolvable in DNS by both the MVMC system and the VMWare vSphere server to verify the root password and remove the VMWare tools. As you have stated, you can remove the VMWare tools manually
    and run the MVMC and it will work as well. If you leave the VMWare tools installed and do the conversion we disable the VMWare tools on the Hyper-V VM once booted. They are still there but should not be in a running state and you can remove them if desired
    at this point.
    Regards,
    -Steve

  • Multi-server search failed on some of the servers

    Hi All,
    i am getting below error in our portal/advance search.
    Error during search occurred - com.sapportals.wcm.WcmException: multi-server search failed on some of the servers;error=2972,index=easywcmen;error=2972,index=itec_dept_indexen;error=2972,index=itec_proj_indexen (Errorcode 2975).
    TrexIndexServer_dcwwtrexprdm1.30003.002.trc
    [86380] 2007-12-31 09:31:08.708 e Trex_SE      FuzzyOptimizer.cpp(03951) : rollbackOptimizeFullText 'itec_proj_indexen' failed rc=4527
    [86380] 2007-12-31 09:31:08.708 e SERVER_TRACE DeltaIndexManager.cpp(01260) : rollback failed for itec_proj_indexen
    [86380] 2007-12-31 09:31:08.724 e SERVER_TRACE TRexApiAdmin.cpp(09159) : Index Id: itec_proj_index, index is corrupt.
    [52804] 2007-12-31 09:31:08.740 e TrexSlice    TRexApiSystem.cpp(01248) : IndexID: itec_proj_index, index is corrupt.
    [52804] 2007-12-31 09:31:08.740 e TrexSlice    TrexSlice.cpp(00502) : ERROR: snapshot creation failed with ret=2008!
    [52804] 2007-12-31 09:32:06.100 e Trex_SE      FuzzyOptimizer.cpp(03907) : start rollbackOptimize for index itec_dept_indexen
    [52804] 2007-12-31 09:32:06.225 e TextMining   Trace.cpp(00074) : EX: 'Unable to open input file
    dcwwtrexprdfs1\i$\itec_dept_index\en\trex\index.ini'
    [52804] 2007-12-31 09:32:06.225 e Trex_SE      FuzzyOptimizer.cpp(02490) : getTMHandle: error in opening TM '
    dcwwtrexprdfs1\i$\itec_dept_index\en\trex' rc=9013
    [52804] 2007-12-31 09:32:06.225 e Trex_SE      FuzzyOptimizer.cpp(03945) : rollbackOptimizeTextMining 'itec_dept_indexen' failed rc=9013
    [52804] 2007-12-31 09:32:06.225 e SERVER_TRACE DeltaIndexManager.cpp(01260) : rollback failed for itec_dept_indexen
    [52804] 2007-12-31 09:32:06.241 e Trex_SE      FuzzyOptimizer.cpp(03907) : start rollbackOptimize for index itec_dept_indexde
    [52804] 2007-12-31 09:32:06.366 e MiningAdmin  IndexManager.cpp(00866) : IndexManager::getAttributeInfos in IndexManager.cpp: Unable to read attribute infos from file '
    dcwwtrexprdfs1\i$\itec_dept_index\de\trex\FDocs'! Rollback is only possible option for index '
    dcwwtrexprdfs1\i$\itec_dept_index\de\trex\'.
    [52804] 2007-12-31 09:32:07.397 e Trex_SE      FuzzyOptimizer.cpp(03984) : rollbackOptimize for index itec_dept_indexde finished rc=0
    [52804] 2007-12-31 09:32:07.397 e Trex_SE      FuzzyOptimizer.cpp(03907) : start rollbackOptimize for index itec_dept_indexes
    [52804] 2007-12-31 09:32:08.538 e Trex_SE      FuzzyOptimizer.cpp(03984) : rollbackOptimize for index itec_dept_indexes finished rc=0
    [52804] 2007-12-31 09:32:08.538 e Trex_SE      FuzzyOptimizer.cpp(03907) : start rollbackOptimize for index itec_dept_indexfr
    [52804] 2007-12-31 09:32:09.663 e Trex_SE      FuzzyOptimizer.cpp(03984) : rollbackOptimize for index itec_dept_indexfr finished rc=0
    [52804] 2007-12-31 09:32:09.663 e Trex_SE      FuzzyOptimizer.cpp(03907) : start rollbackOptimize for index itec_dept_indexsh
    [52804] 2007-12-31 09:32:10.788 e Trex_SE      FuzzyOptimizer.cpp(03984) : rollbackOptimize for index itec_dept_indexsh finished rc=0
    [52804] 2007-12-31 09:32:10.803 e SERVER_TRACE TRexApiAdmin.cpp(09159) : Index Id: itec_dept_index, index is corrupt.
    [20892] 2007-12-31 09:33:15.336 e SERVER_TRACE TRexApiAdmin.cpp(09159) : Index Id: easywcm, index is corrupt.
    [71696] 2007-12-31 09:33:15.351 e SERVER_TRACE TRexApiAdmin.cpp(09159) : Index Id: itec_dept_index, index is corrupt.
    [38716] 2007-12-31 09:33:15.367 e SERVER_TRACE TRexApiAdmin.cpp(09159) : Index Id: itec_proj_index, index is corrupt.
    [38716] 2007-12-31 09:36:15.386 e SERVER_TRACE TRexApiAdmin.cpp(09159) : Index Id: easywcm, index is corrupt.
    [71696] 2007-12-31 09:36:15.402 e SERVER_TRACE TRexApiAdmin.cpp(09159) : Index Id: itec_dept_index, index is corrupt.
    [86380] 2007-12-31 09:36:15.417 e SERVER_TRACE TRexApiAdmin.cpp(09159) : Index Id: itec_proj_index, index is corrupt.
    [86380] 2007-12-31 09:39:15.421 e SERVER_TRACE TRexApiAdmin.cpp(09159) : Index Id: easywcm, index is corrupt.
    [71696] 2007-12-31 09:39:15.437 e SERVER_TRACE TRexApiAdmin.cpp(09159) : Index Id: itec_dept_index, index is corrupt.
    [20892] 2007-12-31 09:39:15.452 e SERVER_TRACE TRexApiAdmin.cpp(09159) : Index Id: itec_proj_index, index is corrupt.
    [96940] 2007-12-31 09:40:38.626 e SERVER_TRACE TRexApiAdmin.cpp(09159) : Index Id: itec_dept_index, index is corrupt.
    [86380] 2007-12-31 09:40:38.657 e SERVER_TRACE TRexApiAdmin.cpp(09159) : Index Id: itec_proj_index, index is corrupt.
    [23192] 2007-12-31 09:40:38.688 e SERVER_TRACE TRexApiAdmin.cpp(09159) : Index Id: easywcm, index is corrupt.
    [86380] 2007-12-31 09:40:38.844 e SERVER_TRACE TRexApiAdmin.cpp(09159) : Index Id: itec_dept_index, index is corrupt.
    [71696] 2007-12-31 09:40:38.860 e SERVER_TRACE TRexApiAdmin.cpp(09159) : Index Id: itec_proj_index, index is corrupt.
    [120828] 2007-12-31 09:40:38.891 e SERVER_TRACE TRexApiAdmin.cpp(09159) : Index Id: easywcm, index is corrupt.
    [23192] 2007-12-31 09:40:44.985 e SERVER_TRACE TRexApiAdmin.cpp(09159) : Index Id: itec_dept_index, index is corrupt.
    [120828] 2007-12-31 09:40:45.001 e SERVER_TRACE TRexApiAdmin.cpp(09159) : Index Id: itec_proj_index, index is corrupt.
    [96940] 2007-12-31 09:40:45.032 e SERVER_TRACE TRexApiAdmin.cpp(09159) : Index Id: easywcm, index is corrupt.
    [120828] 2007-12-31 09:40:45.110 e SERVER_TRACE TRexApiAdmin.cpp(09159) : Index Id: itec_dept_index, index is corrupt.
    [103116] 2007-12-31 09:40:45.126 e SERVER_TRACE TRexApiAdmin.cpp(09159) : Index Id: itec_proj_index, index is corrupt.
    [38716] 2007-12-31 09:40:45.141 e SERVER_TRACE TRexApiAdmin.cpp(09159) : Index Id: easywcm, index is corrupt.
    [96940] 2007-12-31 09:42:15.456 e SERVER_TRACE TRexApiAdmin.cpp(09159) : Index Id: easywcm, index is corrupt.
    [83108] 2007-12-31 09:42:15.471 e SERVER_TRACE TRexApiAdmin.cpp(09159) : Index Id: itec_dept_index, index is corrupt.
    [20892] 2007-12-31 09:42:15.487 e SERVER_TRACE TRexApiAdmin.cpp(09159) : Index Id: itec_proj_index, index is corrupt.
    [20892] 2007-12-31 09:45:15.490 e SERVER_TRACE TRexApiAdmin.cpp(09159) : Index Id: easywcm, index is corrupt.
    [83108] 2007-12-31 09:45:15.506 e SERVER_TRACE TRexApiAdmin.cpp(09159) : Index Id: itec_dept_index, index is corrupt.
    [38716] 2007-12-31 09:45:15.522 e SERVER_TRACE TRexApiAdmin.cpp(09159) : Index Id: itec_proj_index, index is corrupt.
    [96940] 2007-12-31 09:48:15.541 e SERVER_TRACE TRexApiAdmin.cpp(09159) : Index Id: easywcm, index is corrupt.
    [23192] 2007-12-31 09:48:15.556 e SERVER_TRACE TRexApiAdmin.cpp(09159) : Index Id: itec_dept_index, index is corrupt.
    [38716] 2007-12-31 09:48:15.572 e SERVER_TRACE TRexApiAdmin.cpp(09159) : Index Id: itec_proj_index, index is corrupt.
    [120828] 2007-12-31 09:48:32.510 e SERVER_TRACE TRexApiAdmin.cpp(09159) : Index Id: itec_dept_index, index is corrupt.
    [52804] 2007-12-31 09:48:32.541 e SERVER_TRACE TRexApiAdmin.cpp(09159) : Index Id: itec_proj_index, index is corrupt.
    [96940] 2007-12-31 09:48:32.557 e SERVER_TRACE TRexApiAdmin.cpp(09159) : Index Id: easywcm, index is corrupt.
    [52804] 2007-12-31 09:48:32.635 e SERVER_TRACE TRexApiAdmin.cpp(09159) : Index Id: itec_dept_index, index is corrupt.
    [20892] 2007-12-31 09:48:32.650 e SERVER_TRACE TRexApiAdmin.cpp(09159) : Index Id: itec_proj_index, index is corrupt.
    [83108] 2007-12-31 09:48:32.682 e SERVER_TRACE TRexApiAdmin.cpp(09159) : Index Id: easywcm, index is corrupt.
    [83108] 2007-12-31 09:48:44.572 e SERVER_TRACE TRexApiAdmin.cpp(09159) : Index Id: itec_dept_index, index is corrupt.
    [71696] 2007-12-31 09:48:44.588 e SERVER_TRACE TRexApiAdmin.cpp(09159) : Index Id: itec_proj_index, index is corrupt.
    [103116] 2007-12-31 09:48:44.619 e SERVER_TRACE TRexApiAdmin.cpp(09159) : Index Id: easywcm, index is corrupt.
    [71696] 2007-12-31 09:48:44.697 e SERVER_TRACE TRexApiAdmin.cpp(09159) : Index Id: itec_dept_index, index is corrupt.
    [120828] 2007-12-31 09:48:44.713 e SERVER_TRACE TRexApiAdmin.cpp(09159) : Index Id: itec_proj_index, index is corrupt.
    [38716] 2007-12-31 09:48:44.729 e SERVER_TRACE TRexApiAdmin.cpp(09159) : Index Id: easywcm, index is corrupt.
    [20892] 2007-12-31 09:48:55.026 e SERVER_TRACE TRexApiAdmin.cpp(09159) : Index Id: itec_dept_index, index is corrupt.
    [86380] 2007-12-31 09:48:55.041 e SERVER_TRACE TRexApiAdmin.cpp(09159) : Index Id: itec_proj_index, index is corrupt.
    [71696] 2007-12-31 09:48:55.073 e SERVER_TRACE TRexApiAdmin.cpp(09159) : Index Id: easywcm, index is corrupt.
    [86380] 2007-12-31 09:48:55.135 e SERVER_TRACE TRexApiAdmin.cpp(09159) : Index Id: itec_dept_index, index is corrupt.
    [23192] 2007-12-31 09:48:55.151 e SERVER_TRACE TRexApiAdmin.cpp(09159) : Index Id: itec_proj_index, index is corrupt.
    [120828] 2007-12-31 09:48:55.182 e SERVER_TRACE TRexApiAdmin.cpp(09159) : Index Id: easywcm, index is corrupt.
    [38716] 2007-12-31 09:49:11.448 e SERVER_TRACE TRexApiAdmin.cpp(09159) : Index Id: itec_dept_index, index is corrupt.
    [96940] 2007-12-31 09:49:11.464 e SERVER_TRACE TRexApiAdmin.cpp(09159) : Index Id: itec_proj_index, index is corrupt.
    [23192] 2007-12-31 09:49:11.479 e SERVER_TRACE TRexApiAdmin.cpp(09159) : Index Id: easywcm, index is corrupt.
    [96940] 2007-12-31 09:49:11.557 e SERVER_TRACE TRexApiAdmin.cpp(09159) : Index Id: itec_dept_index, index is corrupt.
    [83108] 2007-12-31 09:49:11.573 e SERVER_TRACE TRexApiAdmin.cpp(09159) : Index Id: itec_proj_index, index is corrupt.
    [51320] 2007-12-31 09:49:11.604 e SERVER_TRACE TRexApiAdmin.cpp(09159) : Index Id: easywcm, index is corrupt.
    [120828] 2007-12-31 09:49:21.745 e SERVER_TRACE TRexApiAdmin.cpp(09159) : Index Id: itec_dept_index, index is corrupt.
    [52804] 2007-12-31 09:49:21.761 e SERVER_TRACE TRexApiAdmin.cpp(09159) : Index Id: itec_proj_index, index is corrupt.
    [96940] 2007-12-31 09:49:21.776 e SERVER_TRACE TRexApiAdmin.cpp(09159) : Index Id: easywcm, index is corrupt.
    [52804] 2007-12-31 09:49:21.854 e SERVER_TRACE TRexApiAdmin.cpp(09159) : Index Id: itec_dept_index, index is corrupt.
    [20892] 2007-12-31 09:49:21.870 e SERVER_TRACE TRexApiAdmin.cpp(09159) : Index Id: itec_proj_index, index is corrupt.
    [83108] 2007-12-31 09:49:21.901 e SERVER_TRACE TRexApiAdmin.cpp(09159) : Index Id: easywcm, index is corrupt.
    [51320] 2007-12-31 09:50:44.075 e SERVER_TRACE TRexApiAdmin.cpp(09159) : Index Id: itec_dept_index, index is corrupt.
    [103116] 2007-12-31 09:50:44.106 e SERVER_TRACE TRexApiAdmin.cpp(09159) : Index Id: itec_proj_index, index is corrupt.
    [20892] 2007-12-31 09:50:44.137 e SERVER_TRACE TRexApiAdmin.cpp(09159) : Index Id: easywcm, index is corrupt.
    [103116] 2007-12-31 09:50:44.215 e SERVER_TRACE TRexApiAdmin.cpp(09159) : Index Id: itec_dept_index, index is corrupt.
    [38716] 2007-12-31 09:50:44.231 e SERVER_TRACE TRexApiAdmin.cpp(09159) : Index Id: itec_proj_index, index is corrupt.
    [86380] 2007-12-31 09:50:44.247 e SERVER_TRACE TRexApiAdmin.cpp(09159) : Index Id: easywcm, index is corrupt.
    [86380] 2007-12-31 09:50:51.247 e SERVER_TRACE TRexApiAdmin.cpp(09159) : Index Id: itec_dept_index, index is corrupt.
    [23192] 2007-12-31 09:50:51.262 e SERVER_TRACE TRexApiAdmin.cpp(09159) : Index Id: itec_proj_index, index is corrupt.
    [120828] 2007-12-31 09:50:51.294 e SERVER_TRACE TRexApiAdmin.cpp(09159) : Index Id: easywcm, index is corrupt.
    [23192] 2007-12-31 09:50:51.356 e SERVER_TRACE TRexApiAdmin.cpp(09159) : Index Id: itec_dept_index, index is corrupt.
    [51320] 2007-12-31 09:50:51.372 e SERVER_TRACE TRexApiAdmin.cpp(09159) : Index Id: itec_proj_index, index is corrupt.
    [52804] 2007-12-31 09:50:51.403 e SERVER_TRACE TRexApiAdmin.cpp(09159) : Index Id: easywcm, index is corrupt.
    [23192] 2007-12-31 09:51:15.575 e SERVER_TRACE TRexApiAdmin.cpp(09159) : Index Id: easywcm, index is corrupt.
    [103116] 2007-12-31 09:51:15.591 e SERVER_TRACE TRexApiAdmin.cpp(09159) : Index Id: itec_dept_index, index is corrupt.
    [71696] 2007-12-31 09:51:15.607 e SERVER_TRACE TRexApiAdmin.cpp(09159) : Index Id: itec_proj_index, index is corrupt.
    [51320] 2007-12-31 09:54:15.610 e SERVER_TRACE TRexApiAdmin.cpp(09159) : Index Id: easywcm, index is corrupt.
    [52804] 2007-12-31 09:54:15.626 e SERVER_TRACE TRexApiAdmin.cpp(09159) : Index Id: itec_dept_index, index is corrupt.
    [71696] 2007-12-31 09:54:15.641 e SERVER_TRACE TRexApiAdmin.cpp(09159) : Index Id: itec_proj_index, index is corrupt.
    [86380] 2007-12-31 09:57:15.645 e SERVER_TRACE TRexApiAdmin.cpp(09159) : Index Id: easywcm, index is corrupt.
    [103116] 2007-12-31 09:57:15.660 e SERVER_TRACE TRexApiAdmin.cpp(09159) : Index Id: itec_dept_index, index is corrupt.
    [23192] 2007-12-31 09:57:15.676 e SERVER_TRACE TRexApiAdmin.cpp(09159) : Index Id: itec_proj_index, index is corrupt.
    [51320] 2007-12-31 10:00:15.695 e SERVER_TRACE TRexApiAdmin.cpp(09159) : Index Id: easywcm, index is corrupt.
    [52804] 2007-12-31 10:00:15.711 e SERVER_TRACE TRexApiAdmin.cpp(09159) : Index Id: itec_dept_index, index is corrupt.
    [23192] 2007-12-31 10:00:15.726 e SERVER_TRACE TRexApiAdmin.cpp(09159) : Index Id: itec_proj_index, index is corrupt.
    [120828] 2007-12-31 10:01:05.305 e Trex_SE      FuzzyOptimizer.cpp(03907) : start rollbackOptimize for index easywcmen
    [120828] 2007-12-31 10:01:05.837 e TREX_C_STORE CStoreFiler.cpp(01142) : <rollback>
    dcwwtrexprdfs1\i$\easywcm\en\HashKeyStore.read.offset for fall back not availabel
    [120828] 2007-12-31 10:01:05.837 e TREX_C_STORE CStoreFiler.cpp(01193) : ERROR: rollback:
    dcwwtrexprdfs1\i$\easywcm\en\HashKeyStore failed
    [120828] 2007-12-31 10:01:05.837 f TrexStore    PersistentDocStore.cpp(01753) : TrexStore error: TRexCommonObjectsException in DocKeyStore.cpp(222): 'ContentStoreOptimizeError' in function PersistentDocStore::rollback
    [120828] 2007-12-31 10:01:05.837 e Trex_SE      FuzzyOptimizer.cpp(02259) : ERROR: m_docStore->rollback failed.
    [120828] 2007-12-31 10:01:05.837 e Trex_SE      FuzzyOptimizer.cpp(03951) : rollbackOptimizeFullText 'easywcmen' failed rc=4527
    [120828] 2007-12-31 10:01:05.837 e SERVER_TRACE DeltaIndexManager.cpp(01260) : rollback failed for easywcmen
    [120828] 2007-12-31 10:01:05.852 e SERVER_TRACE TRexApiAdmin.cpp(09159) : Index Id: easywcm, index is corrupt.
    [103116] 2007-12-31 10:01:05.852 e TrexSlice    TRexApiSystem.cpp(01248) : IndexID: easywcm, index is corrupt.
    [103116] 2007-12-31 10:01:05.868 e TrexSlice    TrexSlice.cpp(00502) : ERROR: snapshot creation failed with ret=2008!
    [20892] 2007-12-31 10:01:08.774 e Trex_SE      FuzzyOptimizer.cpp(03907) : start rollbackOptimize for index itec_proj_indexen
    [20892] 2007-12-31 10:01:09.321 e TREX_C_STORE CStoreFiler.cpp(01142) : <rollback>
    dcwwtrexprdfs1\i$\itec_proj_index\en\HashKeyStore.read.offset for fall back not availabel
    [20892] 2007-12-31 10:01:09.337 e TREX_C_STORE CStoreFiler.cpp(01193) : ERROR: rollback:
    dcwwtrexprdfs1\i$\itec_proj_index\en\HashKeyStore failed
    [20892] 2007-12-31 10:01:09.337 f TrexStore    PersistentDocStore.cpp(01753) : TrexStore error: TRexCommonObjectsException in DocKeyStore.cpp(222): 'ContentStoreOptimizeError' in function PersistentDocStore::rollback
    [20892] 2007-12-31 10:01:09.337 e Trex_SE      FuzzyOptimizer.cpp(02259) : ERROR: m_docStore->rollback failed.
    [20892] 2007-12-31 10:01:09.337 e Trex_SE      FuzzyOptimizer.cpp(03951) : rollbackOptimizeFullText 'itec_proj_indexen' failed rc=4527
    [20892] 2007-12-31 10:01:09.337 e SERVER_TRACE DeltaIndexManager.cpp(01260) : rollback failed for itec_proj_indexen
    [20892] 2007-12-31 10:01:09.352 e SERVER_TRACE TRexApiAdmin.cpp(09159) : Index Id: itec_proj_index, index is corrupt.
    [96940] 2007-12-31 10:01:09.352 e TrexSlice    TRexApiSystem.cpp(01248) : IndexID: itec_proj_index, index is corrupt.
    [96940] 2007-12-31 10:01:09.352 e TrexSlice    TrexSlice.cpp(00502) : ERROR: snapshot creation failed with ret=2008!
    [96940] 2007-12-31 10:02:00.838 e Trex_SE      FuzzyOptimizer.cpp(03907) : start rollbackOptimize for index itec_dept_indexen
    [96940] 2007-12-31 10:02:00.978 e TextMining   Trace.cpp(00074) : EX: 'Unable to open input file
    dcwwtrexprdfs1\i$\itec_dept_index\en\trex\index.ini'
    [96940] 2007-12-31 10:02:00.978 e Trex_SE      FuzzyOptimizer.cpp(02490) : getTMHandle: error in opening TM '
    dcwwtrexprdfs1\i$\itec_dept_index\en\trex' rc=9013
    [96940] 2007-12-31 10:02:00.978 e Trex_SE      FuzzyOptimizer.cpp(03945) : rollbackOptimizeTextMining 'itec_dept_indexen' failed rc=9013
    [96940] 2007-12-31 10:02:00.978 e SERVER_TRACE DeltaIndexManager.cpp(01260) : rollback failed for itec_dept_indexen
    [96940] 2007-12-31 10:02:00.994 e Trex_SE      FuzzyOptimizer.cpp(03907) : start rollbackOptimize for index itec_dept_indexde
    [96940] 2007-12-31 10:02:01.135 e MiningAdmin  IndexManager.cpp(00866) : IndexManager::getAttributeInfos in IndexManager.cpp: Unable to read attribute infos from file '
    dcwwtrexprdfs1\i$\itec_dept_index\de\trex\FDocs'! Rollback is only possible option for index '
    dcwwtrexprdfs1\i$\itec_dept_index\de\trex\'.
    [96940] 2007-12-31 10:02:02.166 e Trex_SE      FuzzyOptimizer.cpp(03984) : rollbackOptimize for index itec_dept_indexde finished rc=0
    [96940] 2007-12-31 10:02:02.166 e Trex_SE      FuzzyOptimizer.cpp(03907) : start rollbackOptimize for index itec_dept_indexes
    [96940] 2007-12-31 10:02:03.307 e Trex_SE      FuzzyOptimizer.cpp(03984) : rollbackOptimize for index itec_dept_indexes finished rc=0
    [96940] 2007-12-31 10:02:03.307 e Trex_SE      FuzzyOptimizer.cpp(03907) : start rollbackOptimize for index itec_dept_indexfr
    [96940] 2007-12-31 10:02:04.432 e Trex_SE      FuzzyOptimizer.cpp(03984) : rollbackOptimize for index itec_dept_indexfr finished rc=0
    [96940] 2007-12-31 10:02:04.447 e Trex_SE      FuzzyOptimizer.cpp(03907) : start rollbackOptimize for index itec_dept_indexsh
    [96940] 2007-12-31 10:02:05.572 e Trex_SE      FuzzyOptimizer.cpp(03984) : rollbackOptimize for index itec_dept_indexsh finished rc=0
    [96940] 2007-12-31 10:02:05.588 e SERVER_TRACE TRexApiAdmin.cpp(09159) : Index Id: itec_dept_index, index is corrupt.
    [52804] 2007-12-31 10:03:15.730 e SERVER_TRACE TRexApiAdmin.cpp(09159) : Index Id: easywcm, index is corrupt.
    [83108] 2007-12-31 10:03:15.745 e SERVER_TRACE TRexApiAdmin.cpp(09159) : Index Id: itec_dept_index, index is corrupt.
    [38716] 2007-12-31 10:03:15.761 e SERVER_TRACE TRexApiAdmin.cpp(09159) : Index Id: itec_proj_index, index is corrupt.
    [86380] 2007-12-31 10:03:20.636 e SERVER_TRACE TRexApiAdmin.cpp(09159) : Index Id: itec_dept_index, index is corrupt.
    [51320] 2007-12-31 10:03:20.683 e SERVER_TRACE TRexApiAdmin.cpp(09159) : Index Id: itec_proj_index, index is corrupt.
    [38716] 2007-12-31 10:03:20.699 e SERVER_TRACE TRexApiAdmin.cpp(09159) : Index Id: easywcm, index is corrupt.
    [51320] 2007-12-31 10:03:20.777 e SERVER_TRACE TRexApiAdmin.cpp(09159) : Index Id: itec_dept_index, index is corrupt.
    [103116] 2007-12-31 10:03:20.792 e SERVER_TRACE TRexApiAdmin.cpp(09159) : Index Id: itec_proj_index, index is corrupt.
    [52804] 2007-12-31 10:03:20.808 e SERVER_TRACE TRexApiAdmin.cpp(09159) : Index Id: easywcm, index is corrupt.
    [52804] 2007-12-31 10:03:29.636 e SERVER_TRACE TRexApiAdmin.cpp(09159) : Index Id: itec_dept_index, index is corrupt.
    [83108] 2007-12-31 10:03:29.652 e SERVER_TRACE TRexApiAdmin.cpp(09159) : Index Id: itec_proj_index, index is corrupt.
    [23192] 2007-12-31 10:03:29.668 e SERVER_TRACE TRexApiAdmin.cpp(09159) : Index Id: easywcm, index is corrupt.
    [83108] 2007-12-31 10:03:29.746 e SERVER_TRACE TRexApiAdmin.cpp(09159) : Index Id: itec_dept_index, index is corrupt.
    [86380] 2007-12-31 10:03:29.761 e SERVER_TRACE TRexApiAdmin.cpp(09159) : Index Id: itec_proj_index, index is corrupt.
    [120828] 2007-12-31 10:03:29.793 e SERVER_TRACE TRexApiAdmin.cpp(09159) : Index Id: easywcm, index is corrupt.
    [120828] 2007-12-31 10:06:15.764 e SERVER_TRACE TRexApiAdmin.cpp(09159) : Index Id: easywcm, index is corrupt.
    [96940] 2007-12-31 10:06:15.780 e SERVER_TRACE TRexApiAdmin.cpp(09159) : Index Id: itec_dept_index, index is corrupt.
    [38716] 2007-12-31 10:06:15.796 e SERVER_TRACE TRexApiAdmin.cpp(09159) : Index Id: itec_proj_index, index is corrupt.
    [83108] 2007-12-31 10:07:22.266 e SERVER_TRACE TRexApiAdmin.cpp(09658) : Index Id: itec_proj_index, index is corrupt.
    [23192] 2007-12-31 10:07:22.266 e SERVER_TRACE TRexApiAdmin.cpp(09658) : Index Id: itec_proj_index, index is corrupt.
    [20892] 2007-12-31 10:09:15.799 e SERVER_TRACE TRexApiAdmin.cpp(09159) : Index Id: easywcm, index is corrupt.
    [86380] 2007-12-31 10:09:15.815 e SERVER_TRACE TRexApiAdmin.cpp(09159) : Index Id: itec_dept_index, index is corrupt.
    [52804] 2007-12-31 10:09:15.830 e SERVER_TRACE TRexApiAdmin.cpp(09159) : Index Id: itec_proj_index, index is corrupt.
    [120828] 2007-12-31 10:12:15.850 e SERVER_TRACE TRexApiAdmin.cpp(09159) : Index Id: easywcm, index is corrupt.
    [86380] 2007-12-31 10:12:15.865 e SERVER_TRACE TRexApiAdmin.cpp(09159) : Index Id: itec_dept_index, index is corrupt.
    [20892] 2007-12-31 10:12:15.881 e SERVER_TRACE TRexApiAdmin.cpp(09159) : Index Id: itec_proj_index, index is corrupt.
    [20892] 2007-12-31 10:15:15.884 e SERVER_TRACE TRexApiAdmin.cpp(09159) : Index Id: easywcm, index is corrupt.
    [86380] 2007-12-31 10:15:15.900 e SERVER_TRACE TRexApiAdmin.cpp(09159) : Index Id: itec_dept_index, index is corrupt.
    [120828] 2007-12-31 10:15:15.915 e SERVER_TRACE TRexApiAdmin.cpp(09159) : Index Id: itec_proj_index, index is corrupt.
    [52804] 2007-12-31 10:18:15.935 e SERVER_TRACE TRexApiAdmin.cpp(09159) : Index Id: easywcm, index is corrupt.
    [86380] 2007-12-31 10:18:15.950 e SERVER_TRACE TRexApiAdmin.cpp(09159) : Index Id: itec_dept_index, index is corrupt.
    [96940] 2007-12-31 10:18:15.966 e SERVER_TRACE TRexApiAdmin.cpp(09159) : Index Id: itec_proj_index, index is corrupt.
    [83108] 2007-12-31 10:21:07.282 e SERVER_TRACE TRexApiAdmin.cpp(09658) : Index Id: itec_proj_index, index is corrupt.
    [23192] 2007-12-31 10:21:07.282 e SERVER_TRACE TRexApiAdmin.cpp(09658) : Index Id: itec_proj_index, index is corrupt.
    [38716] 2007-12-31 10:21:12.282 e SERVER_TRACE TRexApiAdmin.cpp(09658) : Index Id: itec_proj_index, index is corrupt.
    [120828] 2007-12-31 10:21:12.282 e SERVER_TRACE TRexApiAdmin.cpp(09658) : Index Id: itec_proj_index, index is corrupt.
    [83108] 2007-12-31 10:21:16.001 e SERVER_TRACE TRexApiAdmin.cpp(09159) : Index Id: easywcm, index is corrupt.
    [51320] 2007-12-31 10:21:16.016 e SERVER_TRACE TRexApiAdmin.cpp(09159) : Index Id: itec_dept_index, index is corrupt.
    [86380] 2007-12-31 10:21:16.032 e SERVER_TRACE TRexApiAdmin.cpp(09159) : Index Id: itec_proj_index, index is corrupt.
    [120828] 2007-12-31 10:21:27.344 e SERVER_TRACE TRexApiAdmin.cpp(09159) : Index Id: itec_dept_index, index is corrupt.
    [71696] 2007-12-31 10:21:27.360 e SERVER_TRACE TRexApiAdmin.cpp(09159) : Index Id: itec_proj_index, index is corrupt.
    [23192] 2007-12-31 10:21:27.376 e SERVER_TRACE TRexApiAdmin.cpp(09159) : Index Id: easywcm, index is corrupt.
    [71696] 2007-12-31 10:21:27.454 e SERVER_TRACE TRexApiAdmin.cpp(09159) : Index Id: itec_dept_index, index is corrupt.
    [86380] 2007-12-31 10:21:27.469 e SERVER_TRACE TRexApiAdmin.cpp(09159) : Index Id: itec_proj_index, index is corrupt.
    [103116] 2007-12-31 10:21:27.485 e SERVER_TRACE TRexApiAdmin.cpp(09159) : Index Id: easywcm, index is corrupt.
    [51320] 2007-12-31 10:21:38.563 e SERVER_TRACE TRexApiAdmin.cpp(09159) : Index Id: itec_dept_index, index is corrupt.
    [120828] 2007-12-31 10:21:38.579 e SERVER_TRACE TRexApiAdmin.cpp(09159) : Index Id: itec_proj_index, index is corrupt.
    [20892] 2007-12-31 10:21:38.595 e SERVER_TRACE TRexApiAdmin.cpp(09159) : Index Id: easywcm, index is corrupt.
    [120828] 2007-12-31 10:21:38.673 e SERVER_TRACE TRexApiAdmin.cpp(09159) : Index Id: itec_dept_index, index is corrupt.
    [71696] 2007-12-31 10:21:38.688 e SERVER_TRACE TRexApiAdmin.cpp(09159) : Index Id: itec_proj_index, index is corrupt.
    [83108] 2007-12-31 10:21:38.704 e SERVER_TRACE TRexApiAdmin.cpp(09159) : Index Id: easywcm, index is corrupt.
    [103116] 2007-12-31 10:21:50.376 e SERVER_TRACE TRexApiAdmin.cpp(09159) : Index Id: itec_dept_index, index is corrupt.
    [51320] 2007-12-31 10:21:50.407 e SERVER_TRACE TRexApiAdmin.cpp(09159) : Index Id: itec_proj_index, index is corrupt.
    [52804] 2007-12-31 10:21:50.423 e SERVER_TRACE TRexApiAdmin.cpp(09159) : Index Id: easywcm, index is corrupt.
    [51320] 2007-12-31 10:21:50.501 e SERVER_TRACE TRexApiAdmin.cpp(09159) : Index Id: itec_dept_index, index is corrupt.
    [120828] 2007-12-31 10:21:50.517 e SERVER_TRACE TRexApiAdmin.cpp(09159) : Index Id: itec_proj_index, index is corrupt.
    [20892] 2007-12-31 10:21:50.548 e SERVER_TRACE TRexApiAdmin.cpp(09159) : Index Id: easywcm, index is corrupt.
    [96940] 2007-12-31 10:24:16.035 e SERVER_TRACE TRexApiAdmin.cpp(09159) : Index Id: easywcm, index is corrupt.
    [86380] 2007-12-31 10:24:16.051 e SERVER_TRACE TRexApiAdmin.cpp(09159) : Index Id: itec_dept_index, index is corrupt.
    [52804] 2007-12-31 10:24:16.066 e SERVER_TRACE TRexApiAdmin.cpp(09159) : Index Id: itec_proj_index, index is corrupt.
    [83108] 2007-12-31 10:27:12.289 e SERVER_TRACE TRexApiAdmin.cpp(09658) : Index Id: itec_proj_index, index is corrupt.
    [38716] 2007-12-31 10:27:12.289 e SERVER_TRACE TRexApiAdmin.cpp(09658) : Index Id: itec_proj_index, index is corrupt.
    [96940] 2007-12-31 10:27:16.070 e SERVER_TRACE TRexApiAdmin.cpp(09159) : Index Id: easywcm, index is corrupt.
    [103116] 2007-12-31 10:27:16.086 e SERVER_TRACE TRexApiAdmin.cpp(09159) : Index Id: itec_dept_index, index is corrupt.
    [20892] 2007-12-31 10:27:16.101 e SERVER_TRACE TRexApiAdmin.cpp(09159) : Index Id: itec_proj_index, index is corrupt.
    [71696] 2007-12-31 10:30:16.105 e SERVER_TRACE TRexApiAdmin.cpp(09159) : Index Id: easywcm, index is corrupt.
    [23192] 2007-12-31 10:30:16.105 e SERVER_TRACE TRexApiAdmin.cpp(09159) : Index Id: itec_dept_index, index is corrupt.
    [96940] 2007-12-31 10:30:16.136 e SERVER_TRACE TRexApiAdmin.cpp(09159) : Index Id: itec_proj_index, index is corrupt.
    [83108] 2007-12-31 10:30:22.292 e SERVER_TRACE TRexApiAdmin.cpp(09658) : Index Id: itec_proj_index, index is corrupt.
    [120828] 2007-12-31 10:30:22.292 e SERVER_TRACE TRexApiAdmin.cpp(09658) : Index Id: itec_proj_index, index is corrupt.
    [38716] 2007-12-31 10:31:05.902 e Trex_SE      FuzzyOptimizer.cpp(03907) : start rollbackOptimize for index easywcmen
    [38716] 2007-12-31 10:31:06.418 e TREX_C_STORE CStoreFiler.cpp(01142) : <rollback>
    dcwwtrexprdfs1\i$\easywcm\en\HashKeyStore.read.offset for fall back not availabel
    [38716] 2007-12-31 10:31:06.418 e TREX_C_STORE CStoreFiler.cpp(01193) : ERROR: rollback:
    dcwwtrexprdfs1\i$\easywcm\en\HashKeyStore failed
    [38716] 2007-12-31 10:31:06.434 f TrexStore    PersistentDocStore.cpp(01753) : TrexStore error: TRexCommonObjectsException in DocKeyStore.cpp(222): 'ContentStoreOptimizeError' in function PersistentDocStore::rollback
    [38716] 2007-12-31 10:31:06.434 e Trex_SE      FuzzyOptimizer.cpp(02259) : ERROR: m_docStore->rollback failed.
    [38716] 2007-12-31 10:31:06.434 e Trex_SE      FuzzyOptimizer.cpp(03951) : rollbackOptimizeFullText 'easywcmen' failed rc=4527
    [38716] 2007-12-31 10:31:06.434 e SERVER_TRACE DeltaIndexManager.cpp(01260) : rollback failed for easywcmen
    [38716] 2007-12-31 10:31:06.449 e SERVER_TRACE TRexApiAdmin.cpp(09159) : Index Id: easywcm, index is corrupt.
    [83108] 2007-12-31 10:31:06.449 e TrexSlice    TRexApiSystem.cpp(01248) : IndexID: easywcm, index is corrupt.
    [83108] 2007-12-31 10:31:06.449 e TrexSlice    TrexSlice.cpp(00502) : ERROR: snapshot creation failed with ret=2008!
    [52804] 2007-12-31 10:31:09.387 e Trex_SE      FuzzyOptimizer.cpp(03907) : start rollbackOptimize for index itec_proj_indexen
    [52804] 2007-12-31 10:31:09.934 e TREX_C_STORE CStoreFiler.cpp(01142) : <rollback>
    dcwwtrexprdfs1\i$\itec_proj_index\en\HashKeyStore.read.offset for fall back not availabel
    [52804] 2007-12-31 10:31:09.934 e TREX_C_STORE CStoreFiler.cpp(01193) : ERROR: rollback:
    dcwwtrexprdfs1\i$\itec_proj_index\en\HashKeyStore failed
    [52804] 2007-12-31 10:31:09.934 f TrexStore    PersistentDocStore.cpp(01753) : TrexStore error: TRexCommonObjectsException in DocKeyStore.cpp(222): 'ContentStoreOptimizeError' in function PersistentDocStore::rollback
    [52804] 2007-12-31 10:31:09.934 e Trex_SE      FuzzyOptimizer.cpp(02259) : ERROR: m_docStore->rollback failed.
    [52804] 2007-12-31 10:31:09.949 e Trex_SE      FuzzyOptimizer.cpp(03951) : rollbackOptimizeFullText 'itec_proj_indexen' failed rc=4527
    [52804] 2007-12-31 10:31:09.949 e SERVER_TRACE DeltaIndexManager.cpp(01260) : rollback failed for itec_proj_indexen
    [52804] 2007-12-31 10:31:09.965 e SERVER_TRACE TRexApiAdmin.cpp(09159) : Index Id: itec_proj_index, index is corrupt.
    [71696] 2007-12-31 10:31:09.965 e TrexSlice    TRexApiSystem.cpp(01248) : IndexID: itec_proj_index, index is corrupt.
    [71696] 2007-12-31 10:31:09.965 e TrexSlice    TrexSlice.cpp(00502) : ERROR: snapshot creation failed with ret=2008!
    [96940] 2007-12-31 10:31:12.293 e SERVER_TRACE TRexApiAdmin.cpp(09658) : Index Id: itec_proj_index, index is corrupt.
    [86380] 2007-12-31 10:31:12.293 e SERVER_TRACE TRexApiAdmin.cpp(09658) : Index Id: itec_proj_index, index is corrupt.
    [20892] 2007-12-31 10:31:17.293 e SERVER_TRACE TRexApiAdmin.cpp(09658) : Index Id: itec_proj_index, index is corrupt.
    [103116] 2007-12-31 10:31:17.293 e SERVER_TRACE TRexApiAdmin.cpp(09658) : Index Id: itec_proj_index, index is corrupt.
    [103116] 2007-12-31 10:32:05.622 e Trex_SE      FuzzyOptimizer.cpp(03907) : start rollbackOptimize for index itec_dept_indexen
    [103116] 2007-12-31 10:32:05.747 e TextMining   Trace.cpp(00074) : EX: 'Unable to open input file
    dcwwtrexprdfs1\i$\itec_dept_index\en\trex\index.ini'
    [103116] 2007-12-31 10:32:05.747 e Trex_SE      FuzzyOptimizer.cpp(02490) : getTMHandle: error in opening TM '
    dcwwtrexprdfs1\i$\itec_dept_index\en\trex' rc=9013
    [103116] 2007-12-31 10:32:05.747 e Trex_SE      FuzzyOptimizer.cpp(03945) : rollbackOptimizeTextMining 'itec_dept_indexen' failed rc=9013
    [103116] 2007-12-31 10:32:05.747 e SERVER_TRACE DeltaIndexManager.cpp(01260) : rollback failed for itec_dept_indexen
    [103116] 2007-12-31 10:32:05.747 e Trex_SE      FuzzyOptimizer.cpp(03907) : start rollbackOptimize for index itec_dept_indexde
    [103116] 2007-12-31 10:32:05.888 e MiningAdmin  IndexManager.cpp(00866) : IndexManager::getAttributeInfos in IndexManager.cpp: Unable to read attribute infos from file '
    dcwwtrexprdfs1\i$\itec_dept_index\de\trex\FDocs'! Rollback is only possible option for index '
    dcwwtrexprdfs1\i$\itec_dept_index\de\trex\'.
    [103116] 2007-12-31 10:32:06.888 e Trex_SE      FuzzyOptimizer.cpp(03984) : rollbackOptimize for index itec_dept_indexde finished rc=0
    [103116] 2007-12-31 10:32:06.904 e Trex_SE      FuzzyOptimizer.cpp(03907) : start rollbackOptimize for index itec_dept_indexes
    [103116] 2007-12-31 10:32:08.029 e Trex_SE      FuzzyOptimizer.cpp(03984) : rollbackOptimize for index itec_dept_indexes finished rc=0
    [103116] 2007-12-31 10:32:08.029 e Trex_SE      FuzzyOptimizer.cpp(03907) : start rollbackOptimize for index itec_dept_indexfr
    [103116] 2007-12-31 10:32:09.154 e Trex_SE      FuzzyOptimizer.cpp(03984) : rollbackOptimize for index itec_dept_indexfr finished rc=0
    [103116] 2007-12-31 10:32:09.154 e Trex_SE      FuzzyOptimizer.cpp(03907) : start rollbackOptimize for index itec_dept_indexsh
    [103116] 2007-12-31 10:32:10.279 e Trex_SE      FuzzyOptimizer.cpp(03984) : rollbackOptimize for index itec_dept_indexsh finished rc=0
    [103116] 2007-12-31 10:32:10.279 e SERVER_TRACE TRexApiAdmin.cpp(09159) : Index Id: itec_dept_index, index is corrupt.
    [71696] 2007-12-31 10:33:16.139 e SERVER_TRACE TRexApiAdmin.cpp(09159) : Index Id: easywcm, index is corrupt.
    [38716] 2007-12-31 10:33:16.139 e SERVER_TRACE TRexApiAdmin.cpp(09159) : Index Id: itec_dept_index, index is corrupt.
    [96940] 2007-12-31 10:33:16.171 e SERVER_TRACE TRexApiAdmin.cpp(09159) : Index Id: itec_proj_index, index is corrupt.
    [96940] 2007-12-31 10:36:16.190 e SERVER_TRACE TRexApiAdmin.cpp(09159) : Index Id: easywcm, index is corrupt.
    [38716] 2007-12-31 10:36:16.205 e SERVER_TRACE TRexApiAdmin.cpp(09159) : Index Id: itec_dept_index, index is corrupt.
    [20892] 2007-12-31 10:36:16.221 e SERVER_TRACE TRexApiAdmin.cpp(09159) : Index Id: itec_proj_index, index is corrupt.
    [20892] 2007-12-31 10:39:16.224 e SERVER_TRACE TRexApiAdmin.cpp(09159) : Index Id: easywcm, index is corrupt.
    [38716] 2007-12-31 10:39:16.240 e SERVER_TRACE TRexApiAdmin.cpp(09159) : Index Id: itec_dept_index, index is corrupt.
    [86380] 2007-12-31 10:39:16.256 e SERVER_TRACE TRexApiAdmin.cpp(09159) : Index Id: itec_proj_index, index is corrupt.
    [86380] 2007-12-31 10:42:16.290 e SERVER_TRACE TRexApiAdmin.cpp(09159) : Index Id: easywcm, index is corrupt.
    [103116] 2007-12-31 10:42:16.306 e SERVER_TRACE TRexApiAdmin.cpp(09159) : Index Id: itec_dept_index, index is corrupt.
    [96940] 2007-12-31 10:42:16.322 e SERVER_TRACE TRexApiAdmin.cpp(09159) : Index Id: itec_proj_index, index is corrupt.
    [96940] 2007-12-31 10:45:16.341 e SERVER_TRACE TRexApiAdmin.cpp(09159) : Index Id: easywcm, index is corrupt.
    [103116] 2007-12-31 10:45:16.356 e SERVER_TRACE TRexApiAdmin.cpp(09159) : Index Id: itec_dept_index, index is corrupt.
    [20892] 2007-12-31 10:45:16.372 e SERVER_TRACE TRexApiAdmin.cpp(09159) : Index Id: itec_proj_index, index is corrupt.
    [52804] 2007-12-31 10:48:16.375 e SERVER_TRACE TRexApiAdmin.cpp(09159) : Index Id: easywcm, index is corrupt.
    [38716] 2007-12-31 10:48:16.391 e SERVER_TRACE TRexApiAdmin.cpp(09159) : Index Id: itec_dept_index, index is corrupt.
    [86380] 2007-12-31 10:48:16.407 e SERVER_TRACE TRexApiAdmin.cpp(09159) : Index Id: itec_proj_index, index is corrupt.
    [86380] 2007-12-31 10:51:16.410 e SERVER_TRACE TRexApiAdmin.cpp(09159) : Index Id: easywcm, index is corrupt.
    [83108] 2007-12-31 10:51:16.426 e SERVER_TRACE TRexApiAdmin.cpp(09159) : Index Id: itec_dept_index, index is corrupt.
    [96940] 2007-12-31 10:51:16.441 e SERVER_TRACE TRexApiAdmin.cpp(09159) : Index Id: itec_proj_index, index is corrupt.
    [71696] 2007-12-31 10:54:16.460 e SERVER_TRACE TRexApiAdmin.cpp(09159) : Index Id: easywcm, index is corrupt.
    [38716] 2007-12-31 10:54:16.460 e SERVER_TRACE TRexApiAdmin.cpp(09159) : Index Id: itec_dept_index, index is corrupt.
    [96940] 2007-12-31 10:54:16.492 e SERVER_TRACE TRexApiAdmin.cpp(09159) : Index Id: itec_proj_index, index is corrupt.
    [71696] 2007-12-31 10:57:16.495 e SERVER_TRACE TRexApiAdmin.cpp(09159) : Index Id: easywcm, index is corrupt.
    [38716] 2007-12-31 10:57:16.495 e SERVER_TRACE TRexApiAdmin.cpp(09159) : Index Id: itec_dept_index, index is corrupt.
    [96940] 2007-12-31 10:57:16.526 e SERVER_TRACE TRexApiAdmin.cpp(09159) : Index Id: itec_proj_index, index is corrupt.
    [96940] 2007-12-31 11:00:16.545 e SERVER_TRACE TRexApiAdmin.cpp(09159) : Index Id: easywcm, index is corrupt.
    [38716] 2007-12-31 11:00:16.560 e SERVER_TRACE TRexApiAdmin.cpp(09159) : Index Id: itec_dept_index, index is corrupt.
    [52804] 2007-12-31 11:00:16.576 e SERVER_TRACE TRexApiAdmin.cpp(09159) : Index Id: itec_proj_index, index is corrupt.
    [23192] 2007-12-31 11:01:06.413 e Trex_SE      FuzzyOptimizer.cpp(03907) : start rollbackOptimize for index easywcmen
    [23192] 2007-12-31 11:01:06.929 e TREX_C_STORE CStoreFiler.cpp(01142) : <rollback>
    dcwwtrexprdfs1\i$\easywcm\en\HashKeyStore.read.offset for fall back not availabel
    [23192] 2007-12-31 11:01:06.929 e TREX_C_STORE CStoreFiler.cpp(01193) : ERROR: rollback:
    dcwwtrexprdfs1\i$\easywcm\en\HashKeyStore failed
    [23192] 2007-12-31 11:01:06.944 f TrexStore    PersistentDocStore.cpp(01753) : TrexStore error: TRexCommonObjectsException in DocKeyStore.cpp(222): 'ContentStoreOptimizeError' in function PersistentDocStore::rollback
    [23192] 2007-12-31 11:01:06.944 e Trex_SE      FuzzyOptimizer.cpp(02259) : ERROR: m_docStore->rollback failed.
    [23192] 2007-12-31 11:01:06.944 e Trex_SE      FuzzyOptimizer.cpp(03951) : rollbackOptimizeFullText 'easywcmen' failed rc=4527
    [23192] 2007-12-31 11:01:06.944 e SERVER_TRACE DeltaIndexManager.cpp(01260) : rollback failed for easywcmen
    [23192] 2007-12-31 11:01:06.960 e SERVER_TRACE TRexApiAdmin.cpp(09159) : Index Id: easywcm, index is corrupt.
    [38716] 2007-12-31 11:01:06.960 e TrexSlice    TRexApiSystem.cpp(01248) : IndexID: easywcm, index is corrupt.
    [38716] 2007-12-31 11:01:06.960 e TrexSlice    TrexSlice.cpp(00502) : ERROR: snapshot creation failed with ret=2008!
    [103116] 2007-12-31 11:01:09.927 e Trex_SE      FuzzyOptimizer.cpp(03907) : start rollbackOptimize for index itec_proj_indexen
    [103116] 2007-12-31 11:01:10.474 e TREX_C_STORE CStoreFiler.cpp(01142) : <rollback>
    dcwwtrexprdfs1\i$\itec_proj_index\en\HashKeyStore.read.offset for fall back not availabel
    [103116] 2007-12-31 11:01:10.474 e TREX_C_STORE CStoreFiler.cpp(01193) : ERROR: rollback:
    dcwwtrexprdfs1\i$\itec_proj_index\en\HashKeyStore failed
    [103116] 2007-12-31 11:01:10.474 f TrexStore    PersistentDocStore.cpp(01753) : TrexStore error: TRexCommonObjectsException in DocKeyStore.cpp(222): 'ContentStoreOptimizeError' in function PersistentDocStore::rollback
    [103116] 2007-12-31 11:01:10.474 e Trex_SE      FuzzyOptimizer.cpp(02259) : ERROR: m_docStore->rollback failed.
    [103116] 2007-12-31 11:01:10.474 e Trex_SE      FuzzyOptimizer.cpp(03951) : rollbackOptimizeFullText 'itec_proj_indexen' failed rc=4527
    [103116] 2007-12-31 11:01:10.489 e SERVER_TRACE DeltaIndexManager.cpp(01260) : rollback failed for itec_proj_indexen
    [103116] 2007-12-31 11:01:10.489 e SERVER_TRACE TRexApiAdmin.cpp(09159) : Index Id: itec_proj_index, index is corrupt.
    [51320] 2007-12-31 11:01:10.505 e TrexSlice    TRexApiSystem.cpp(01248) : IndexID: itec_proj_index, index is corrupt.
    [51320] 2007-12-31 11:01:10.505 e TrexSlice    TrexSlice.cpp(00502) : ERROR: snapshot creation failed with ret=2008!
    [51320] 2007-12-31 11:02:00.233 e Trex_SE      FuzzyOptimizer.cpp(03907) : start rollbackOptimize for index itec_dept_indexen
    [51320] 2007-12-31 11:02:00.358 e TextMining   Trace.cpp(00074) : EX: 'Unable to open input file
    dcwwtrexprdfs1\i$\itec_dept_index\en\trex\index.ini'
    [51320] 2007-12-31 11:02:00.358 e Trex_SE      FuzzyOptimizer.cpp(02490) : getTMHandle: error in opening TM '
    dcwwtrexprdfs1\i$\itec_dept_index\en\trex' rc=9013
    [51320] 2007-12-31 11:02:00.358 e Trex_SE      FuzzyOptimizer.cpp(03945) : rollbackOptimizeTextMining 'itec_dept_indexen' failed rc=9013
    [51320] 2007-12-31 11:02:00.358 e SERVER_TRACE DeltaIndexManager.cpp(01260) : rollback failed for itec_dept_indexen
    [51320] 2007-12-31 11:02:00.358 e Trex_SE      FuzzyOptimizer.cpp(03907) : start rollbackOptimize for index itec_dept_indexde
    [51320] 2007-12-31 11:02:00.498 e MiningAdmin  IndexManager.cpp(00866) : IndexManager::getAttributeInfos in IndexManager.cpp: Unable to read attribute infos from file '
    dcwwtrexprdfs1\i$\itec_dept_index\de\trex\FDocs'! Rollback is only possible option for index '
    dcwwtrexprdfs1\i$\itec_dept_index\de\trex\'.
    [51320] 2007-12-31 11:02:01.482 e Trex_SE      FuzzyOptimizer.cpp(03984) : rollbackOptimize for index itec_dept_indexde finished rc=0
    [51320] 2007-12-31 11:02:01.482 e Trex_SE      FuzzyOptimizer.cpp(03907) : start rollbackOptimize for index itec_dept_indexes
    [51320] 2007-12-31 11:02:02.607 e Trex_SE      FuzzyOptimizer.cpp(03984) : rollbackOptimize for index itec_dept_indexes finished rc=0
    [51320] 2007-12-31 11:02:02.607 e Trex_SE      FuzzyOptimizer.cpp(03907) : start rollbackOptimize for index itec_dept_indexfr
    [51320] 2007-12-31 11:02:03.716 e Trex_SE      FuzzyOptimizer.cpp(03984) : rollbackOptimize for index itec_dept_indexfr finished rc=0
    [51320] 2007-12-31 11:02:03.731 e Trex_SE      FuzzyOptimizer.cpp(03907) : start rollbackOptimize for index itec_dept_indexsh
    [51320] 2007-12-31 11:02:04.840 e Trex_SE      FuzzyOptimizer.cpp(03984) : rollbackOptimize for index itec_dept_indexsh finished rc=0
    [51320] 2007-12-31 11:02:04.856 e SERVER_TRACE TRexApiAdmin.cpp(09159) : Index Id: itec_dept_index, index is corrupt.
    [23192] 2007-12-31 11:02:27.705 e SERVER_TRACE TRexApiAdmin.cpp(09159) : Index Id: itec_dept_index, index is corrupt.
    [83108] 2007-12-31 11:02:27.736 e SERVER_TRACE TRexApiAdmin.cpp(09159) : Index Id: itec_proj_index, index is corrupt.
    [51320] 2007-12-31 11:02:27.767 e SERVER_TRACE TRexApiAdmin.cpp(09159) : Index Id: easywcm, index is corrupt.
    [83108] 2007-12-31 11:02:27.845 e SERVER_TRACE TRexApiAdmin.cpp(09159) : Index Id: itec_dept_index, index is corrupt.
    [103116] 2007-12-31 11:02:27.861 e SERVER_TRACE TRexApiAdmin.cpp(09159) : Index Id: itec_proj_index, index is corrupt.
    [71696] 2007-12-31 11:02:27.877 e SERVER_TRACE TRexApiAdmin.cpp(09159) : Index Id: easywcm, index is corrupt.
    [51320] 2007-12-31 11:03:16.589 e SERVER_TRACE TRexApiAdmin.cpp(09159) : Index Id: easywcm, index is corrupt.
    [96940] 2007-12-31 11:03:16.605 e SERVER_TRACE TRexApiAdmin.cpp(09159) : Index Id: itec_dept_index, index is corrupt.
    [71696] 2007-12-31 11:03:16.620 e SERVER_TRACE TRexApiAdmin.cpp(09159) : Index Id: itec_proj_index, index is corrupt.
    [71696] 2007-12-31 11:06:16.682 e SERVER_TRACE TRexApiAdmin.cpp(09159) : Index Id: easywcm, index is corrupt.
    [96940] 2007-12-31 11:06:16.682 e SERVER_TRACE TRexApiAdmin.cpp(09159) : Index Id: itec_dept_index, index is corrupt.
    [71696] 2007-12-31 11:06:16.713 e SERVER_TRACE TRexApiAdmin.cpp(09159) : Index Id: itec_proj_index, index is corrupt.
    [20892] 2007-12-31 11:09:16.785 e SERVER_TRACE TRexApiAdmin.cpp(09159) : Index Id: easywcm, index is corrupt.
    [96940] 2007-12-31 11:09:16.801 e SERVER_TRACE TRexApiAdmin.cpp(09159) : Index Id: itec_dept_index, index is corrupt.
    [52804] 2007-12-31 11:09:16.816 e SERVER_TRACE TRexApiAdmin.cpp(09159) : Index Id: itec_proj_index, index is corrupt.
    [83108] 2007-12-31 11:10:18.345 e SERVER_TRACE TRexApiAdmin.cpp(09159) : Index Id: itec_dept_index, index is corrupt.
    [120828] 2007-12-31 11:10:18.377 e SERVER_TRACE TRexApiAdmin.cpp(09159) : Index Id: itec_proj_index, index is corrupt.
    [52804] 2007-12-31 11:10:18.392 e SERVER_TRACE TRexApiAdmin.cpp(09159) : Index Id: easywcm, index is corrupt.
    [120828] 2007-12-31 11:10:18.470 e SERVER_TRACE TRexApiAdmin.cpp(09159) : Index Id: itec_dept_index, index is corrupt.

    Hi Srinivas,
    I am afraid, but it seems that the indexes of your TREX installation are corrupt. This could happen if, e.g. you use a network storage (SAN or NAS) which is temporarily not available.
    As far as I see it is necessary to perform a reindex or restore a backup of the not working indexes. For further investigation it might be useful to do a backup of the current situation.
    Kind regards,
    Roland

  • Backing up virtual machines in Hyper-V: theory question

    Hello!
    This article http://msdn.microsoft.com/en-us/library/dd405549%28v=vs.85%29.aspx says:
    "Hyper-V uses the Volume Shadow Copy Service (VSS) to backup and restore virtual machines (VMs).
    If the backup (volume snapshot) integration services are installed in the guest operating system, a VSS requester is installed that will allow VSS writers in the guest operating system to participate in the backup of the VM. "
    Backing Up the Virtual Machines
    Hyper-V uses one of two mechanisms to back up each VM. The default backup mechanism is called the "Saved State" method, where the VM is put into a saved state during the processing of the PrepareForSnapshot event,snapshots
    are taken of the appropriate volumes, and the VM is returned to the previous state during the processing of the PostSnapshot event."
    The other backup mechanism is called the "Child VM Snapshot" method, which uses VSS inside the child VM to participate in the backup....
    Backup (volume snapshot) Integration Service is installed and running in the child VM.
    The child VM must be in the running state."
    Putting it all together: the backup integration services are installed in the guest operating systems by default (at least in Win2008-2012R2), but "The default backup mechanism is called the "Saved State" method,...",
    wich does NOT use child vm snapshot creation. It means that checking the "Backup (volume checkpoint)" checkbox changes nothing (at least with running VMs) because the default method is "Saved state":
    Q1: if the default method is "Saved state" and my VMs are running what should I do to take a backup by using
    "Child VM Snapshot" method?
    Q2: is there any difference between a backup created by method 1 and method 2?
    Thank you in advance,
    Michael

    Hi,
    The two backup mechanisms used in the different backup scenario:
    Short to say is:
    Perform a backup from the server running Hyper-V
    (host).
    Perform a backup from
    within the guest operating system of a virtual machine.
    The detail explain is:
    There are two basic methods you can use to perform a backup. You can:
    Perform a backup from the server running Hyper-V. We recommend that you use this method to perform a full server backup because it captures more data than the other method. If the backup application is compatible with Hyper-V and the Hyper-V
    VSS writer, you can perform a full server backup that helps protect all of the data required to fully restore the server, except the virtual networks. The data included in such a backup includes the configuration of virtual machines, snapshots associated with
    the virtual machines, and virtual hard disks used by the virtual machines. As a result, using this method can make it easier to recover the server if you need to, because you do not have to recreate virtual machines or reinstall Hyper-V. However, virtual networks
    are not included in a full server backup. You will need to reconfigure the virtual networking by recreating the virtual networks and then reattaching the virtual network adapters in each virtual machine to the appropriate virtual network. As part of your backup
    planning, make sure you document the configuration and all relevant settings of your virtual network if you want to be able to recreate it.
    • Perform a backup from within the guest operating system of a virtual machine.
    Use this method when you need to back up data from storage that is not supported by the Hyper-V VSS writer. When you use this method, you run a backup application from the guest operating system of the virtual machine. If you need to use this
    method, you should use it in addition to a full server backup and not as an alternative to a full server backup. Perform a backup from within the guest operating system before you perform a full backup of the server running Hyper-V. For more information about
    storage considerations, see the following section.
    The related KB:
    Planning for Backup
    http://technet.microsoft.com/en-us/library/dd252619(v=ws.10).aspx
    Hope this helps.
    We
    are trying to better understand customer views on social support experience, so your participation in this
    interview project would be greatly appreciated if you have time.
    Thanks for helping make community forums a great place.

  • Application hangs and sql log shows "I/O is frozen" for minutes until "I/O was resumed"

    VSS is being invoked to backup our SQL Server 2012 databases throughout the day.  Occasionally, maybe once every few days, the application using the database hangs for a few minutes and coincidentally the sql server log shows that I/O was frozen for
    a few minutes (rather than less then a second for all other backups):
    11/25/2014 09:11:50,spid87,Unknown,I/O was resumed on database ourdatabase. No user action is required.
    11/25/2014 09:09:10,spid87,Unknown,I/O is frozen on database ourdatabase. No user action is required. However<c/> if I/O is not resumed promptly<c/> you could cancel the backup.
    AppAssure (backup software) support said this may be an issue with VSS.  What is the best way to go about troubleshooting this?  I've read many posts with people having similar issues dating back to 2010 and haven't really come across any
    solutions.  Should I simply open a case with MS support?
    SQL Server 2012
    Windows Server 2012 2 node cluster
    Database file on Dell Equallogic iCSCI SAN
    Dell AppAssure for Backups
    Thanks,
    -Bob

    Hi Bob,
    AFAIK yes this issue of ''I/O was frozen'' might occur when you use backup tool which uses VSS to take backups. This is actually how VSS backups works . There are few steps when backup is being taken using TP tool which uses VS. One of the steps is to create
    snapshot so that consistent backup could be taken
    In the snapshot creation phase following happens
    a) SQL Writer talks to SQL Server to prepare for a snapshot backup
    b) Then all I/O for the database being backed up is frozen, and then we create the snapshot.
    c) Once this is done, the I/O is resumed. This process is called "thaw".
    The second step would freeze I/O momentarily and you might see little freezing. AFAIK this is default behavior how VSS backups work
    You must read below excellent article It would help you in understanding how this backup works
    http://blogs.msdn.com/b/sqlserverfaq/archive/2009/04/28/informational-shedding-light-on-vss-vdi-backups-in-sql-server.aspx
    Please mark this reply as answer if it solved your issue or vote as helpful if it helped so that other forum members can benefit from it
    My Technet Wiki Article
    MVP

  • Oracle 9i Lite replication suggestion needed

    when i use the tools to create snapshots and packaged them it always demand files like first page etc in tool but i just want to create snapshots , replication snapshots and sync them on multible laptop for an application that is already install on laptops any suggestions !!!! how to get this done correctly

    I am also searching for this kind of thing, but no idea. My problem is to achieve the snapshot creation thry Powerbuilder application at runtime.

  • Oracle 10g Lite : Two Publication in a single Package

    Hi all,
    I need to have two different publication. One for full refresh(updatable) and other for complete refresh (non updatable) while packaging
    using Package Wizard.
    While packaging the application definition, if I select the publication from the wizard then it is not allowing me to select tables for snapshot creation.
    Is there anyway to have two publication for single application? Can anybody help me?
    Thanks in advance
    Niranjana

    There are sync API settings in 10.3 to control which tables you want to sync. Not used them myself as not on 10.3 (and also control things in a different way), but there are other threads on this in the forum.
    I can see that you might want to supress the sync of your ref data tables, but i think you will get more problems if you try and only upload or download the updateable tables, would be better to do the normal upload/download for these. This would also mean that you have a simpler switch for the sync ie: sync updateable or sync all. The clients would also not get the situation where they are missing jobs because they failed to ask for download, or lose data because they have failed to upload
    One issue you may get is that if you leave the choice to the end user, the client reference data may get out of step and this could cause integrity problems on the server side if FKs stop working
    If the problem is simply the PK and fast refresh issue, then you could look at using queue based publication items for the ref data tables. These work differently to both fast and complete refresh in that you define all of the logic around the sync process from the server end. We use these now for the majority of our publication items as we had issues with the MGP process, and they provide for more of a realtime sync.
    For example, the way that we deal with the download is as follows
    1) select ALL relevant data for the publication item for the client into the download table, with a dummy dmltype$$ of X
    2) compare this data set with a server stored copy of what is on the client.
    - if records are in the new data set, but not in the copy, set the dmltype$$ to I
    - if records are in the new data set AND the old one but there are column level differences, set dmltype$$ to U
    - if records are in the copy, but not in the new data set, set the dmltype$$ to D
    3) delete from the download table where dmltype$$=X
    4) update the backup copy, adding there dmltype$$=I, updating where U and deleting where D
    This level of control needs to be manually coded, can oly be defined using the java APIs for creating publication items, and you need to do much more in terms of ddl, but this would allow you to sync only changes to the ref data objects, without the need for PKs in the same way
    You can also include in your code to ignore certain publication items unless there is flag data else where (ie: only sync when yiou determine the need from the server end)

Maybe you are looking for

  • Arch linux on fujitsu lifebook??

    Hi, I've got a fujitsu lifebook Q2010..... i want to install Arch on it. I just want to check if the hardware is supported? 1. Processor: Intel® CoreTM Solo Processor Ultra Low Voltage U1400 (1.20 GHz, 2 MB L2 cache, 533 MHz FSB) 2. Chipset: Intel® 9

  • 10.4.11 + networking = spinning beachball

    After updating both my MacBook Pro and Mac Pro to 10.4.11, networking them no longer works. SMB doesn't work. Personal File sharing doesn't work. When you try to mount a networked computer's drive, you get the spinning beach ball of death. I tried re

  • Groupwise

    My organization uses Groupwise.  I have been synching my calender by connecting directly to my desktop.  Since the last software upgrade I now get a message that "The organizer applications on your computer on not supported" when I try to synch my ca

  • Message always "scheduled"

    Hi guys, I have a problem : for one of my scenario and only for that one , my message is always in "scheduled" in the monitor, I always have to unlock the queue in smq2, to make it work. Does anybody know why it's always in this status in the monitor

  • If i have deleted my local files, how can i download all my files at once from the creative cloud server?

    Hi, My creative cloud files have all been deleted on my machine, all put in the trash (not by me!) I've recovered some but I want to download everything from the creative cloud server before I sync again.  is there anyway to do this? or do I have to