Version Cue Log Files Corrupted.

Address:
Version Cue CS2 > config > configuration.
I'm trying to create a back up of my hard drive, as a precaution whilst running an Adobe Clean script but the back up software is finding corrupt Version Cue log files.
Are these files critical?
Is it okay for me to delete one or two if they have become corrupted?

This is why I don't use Version Cue.
But you will get much better help in the Version Cue Forum http://www.adobeforums.com/webx/.2ccdf13f/

Similar Messages

  • Log file corrupt and can't open the database.

    I use Replication Manager to manage my Replication; and there is only one site currently in my application.
    I killed the App process with signal -9. (ie. $ kill -9 appID).
    Then I try to restart the App, but the event_callback function got a PANIC event when to open the envirment.
    The open flag is:
    flags = DB_CREATE | DB_INIT_LOCK | DB_INIT_LOG | DB_INIT_MPOOL |
    DB_INIT_REP | DB_INIT_TXN | DB_RECOVER | DB_THREAD;
    ret = dbenv->open(dbenv, path, flags | DB_SYSTEM_MEM, 0);
    What's the reason cause this problem?
    How can recover it ?
    The logs list as below:
    [D 11/19 09:44] dbpf using shm key: 977431433
    [E 11/19 09:44] [src/io/dbpf-mgmt.c, 400]
    [E 11/19 09:44] yuga: DB_LOGC->get: LSN 1/9776: invalid log record header
    [E 11/19 09:44] yuga: Log file corrupt at LSN: [1][9906]
    [E 11/19 09:44] yuga: PANIC: Invalid argument
    [E 11/19 09:44] [src/io/dbpf-mgmt.c] Rep EventGot a panic: Invalid argument (22)
    Edited by: dbnicker on Nov 18, 2010 6:08 PM

    First, what version of Berkeley DB are you running and on what system?
    The error indicates something amiss in the log. The LSN values are quite
    small. Can you run 'db_printlog -N -h <env path>' and post the log
    contents?
    If you are using BDB 5.0 or later, can you also post the contents of
    the __db.rep.diag00 file in the environment home directory? Thanks.
    Sue LoVerso
    Oracle

  • Transaction log shipping restore with standby failed: log file corrupted

    Restore transaction log failed and I get this error: for only 04 no of database in same SQL server, renaming are working fine.
    Date                     
    9/10/2014 6:09:27 AM
    Log                        
    Job History (LSRestore_DATA_TPSSYS)
    Step ID                
    1
    Server                  
    DATADR
    Job Name                           
    LSRestore_DATA_TPSSYS
    Step Name                        
    Log shipping restore log job step.
    Duration                             
    00:00:03
    Sql Severity        0
    Sql Message ID 0
    Operator Emailed           
    Operator Net sent          
    Operator Paged               
    Retries Attempted         
    0
    Message
    2014-09-10 06:09:30.37  *** Error: Could not apply log backup file '\\10.227.32.27\LsSecondery\TPSSYS\TPSSYS_20140910003724.trn' to secondary database 'TPSSYS'.(Microsoft.SqlServer.Management.LogShipping) ***
    2014-09-10 06:09:30.37  *** Error: An error occurred while processing the log for database 'TPSSYS'. 
    If possible, restore from backup. If a backup is not available, it might be necessary to rebuild the log.
    An error occurred during recovery, preventing the database 'TPSSYS' (13:0) from restarting. Diagnose the recovery errors and fix them, or restore from a known good backup. If errors are not corrected or expected, contact Technical Support.
    RESTORE LOG is terminating abnormally.
    Processed 0 pages for database 'TPSSYS', file 'TPSSYS' on file 1.
    Processed 1 pages for database 'TPSSYS', file 'TPSSYS_log' on file 1.(.Net SqlClient Data Provider) ***
    2014-09-10 06:09:30.37  *** Error: Could not log history/error message.(Microsoft.SqlServer.Management.LogShipping) ***
    2014-09-10 06:09:30.37  *** Error: ExecuteNonQuery requires an open and available Connection. The connection's current state is closed.(System.Data) ***
    2014-09-10 06:09:30.37  Skipping log backup file '\\10.227.32.27\LsSecondery\TPSSYS\TPSSYS_20140910003724.trn' for secondary database 'TPSSYS' because the file could not be verified.
    2014-09-10 06:09:30.37  *** Error: Could not log history/error message.(Microsoft.SqlServer.Management.LogShipping) ***
    2014-09-10 06:09:30.37  *** Error: ExecuteNonQuery requires an open and available Connection. The connection's current state is closed.(System.Data) ***
    2014-09-10 06:09:30.37  *** Error: An error occurred restoring the database access mode.(Microsoft.SqlServer.Management.LogShipping) ***
    2014-09-10 06:09:30.37  *** Error: ExecuteScalar requires an open and available Connection. The connection's current state is closed.(System.Data) ***
    2014-09-10 06:09:30.37  *** Error: Could not log history/error message.(Microsoft.SqlServer.Management.LogShipping) ***
    2014-09-10 06:09:30.37  *** Error: ExecuteNonQuery requires an open and available Connection. The connection's current state is closed.(System.Data) ***
    2014-09-10 06:09:30.37  *** Error: An error occurred restoring the database access mode.(Microsoft.SqlServer.Management.LogShipping) ***
    2014-09-10 06:09:30.37  *** Error: ExecuteScalar requires an open and available Connection. The connection's current state is closed.(System.Data) ***
    2014-09-10 06:09:30.37  *** Error: Could not log history/error message.(Microsoft.SqlServer.Management.LogShipping) ***
    2014-09-10 06:09:30.37  *** Error: ExecuteNonQuery requires an open and available Connection. The connection's current state is closed.(System.Data) ***
    2014-09-10 06:09:30.37  Deleting old log backup files. Primary Database: 'TPSSYS'
    2014-09-10 06:09:30.37  *** Error: Could not log history/error message.(Microsoft.SqlServer.Management.LogShipping) ***
    2014-09-10 06:09:30.37  *** Error: ExecuteNonQuery requires an open and available Connection. The connection's current state is closed.(System.Data) ***
    2014-09-10 06:09:30.37  The restore operation completed with errors. Secondary ID: 'dd25135a-24dd-4642-83d2-424f29e9e04c'
    2014-09-10 06:09:30.37  *** Error: Could not log history/error message.(Microsoft.SqlServer.Management.LogShipping) ***
    2014-09-10 06:09:30.37  *** Error: ExecuteNonQuery requires an open and available Connection. The connection's current state is closed.(System.Data) ***
    2014-09-10 06:09:30.37  *** Error: Could not cleanup history.(Microsoft.SqlServer.Management.LogShipping) ***
    2014-09-10 06:09:30.37  *** Error: ExecuteNonQuery requires an open and available Connection. The connection's current state is closed.(System.Data) ***
    2014-09-10 06:09:30.38  ----- END OF TRANSACTION LOG RESTORE    
    Exit Status: 1 (Error)

    I Have restore the database to new server and check with new log shipping but its give this same error again, If it is network issue i believe issue need to occur on every database in  that server with log shipping configuration
    error :
    Message
    2014-09-12 10:50:03.18    *** Error: Could not apply log backup file 'E:\LsSecondery\EAPDAT\EAPDAT_20140912051511.trn' to secondary database 'EAPDAT'.(Microsoft.SqlServer.Management.LogShipping) ***
    2014-09-12 10:50:03.18    *** Error: An error occurred while processing the log for database 'EAPDAT'.  If possible, restore from backup. If a backup is not available, it might be necessary to rebuild the log.
    An error occurred during recovery, preventing the database 'EAPDAT' (8:0) from restarting. Diagnose the recovery errors and fix them, or restore from a known good backup. If errors are not corrected or expected, contact Technical Support.
    RESTORE LOG is terminating abnormally.
    can this happened due to data base or log file corruption, if so how can i check on that to verify the issue
    Its not necessary if the issue is with network it would happen every day IMO it basically happens when load on network is high and you transfer log file which is big in size.
    As per message database engine was not able to restore log backup and said that you must rebuild log because it did not find out log to be consistent. From here it seems log corruption.
    Is it the same log file you restored ? if that is the case since log file was corrupt it would ofcourse give error on wehatever server you restore.
    Can you try creating logshipping on new server by taking fresh full and log backup and see if you get issue there as well. I would also say you to raise case with Microsoft and let them tell what is root cause to this problem
    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 Articles

  • Recovering data when log files corrupt

    I am interested to understand if you can easily salvage the data files if the log files corrupt for some reason. Thus far I cannot see how this can be easilly achieved as db_backup requires a working environment, and since the log files may have vanished, the LSN of the data files will be greater than of the last log - and therefore refuse to create the environment.
    Ideally I guess, I am looking for a tool that can reset the LSN in place. It would be better to have access to your 100's of GB of data and accept a small amount of inconsistency or data loss than have nothing.
    Thanks

    Hi,
    Resetting LSNs can be done using db_load -r lsn or using the lsn_reset() method, and it is done in place.
    If your log files are corrupted, you would need to verify the database files (you can use the db_verify BDB utility or the verify() method). The actions you will further take depend on the result of verifying the database files:
    - if they verify correctly then you just need to reset the LSNs and the file IDs in the databases and start with a fresh environment,
    - if they do not verify correctly, you could restore the data from the most recent backup, or you can perform a salvage dump of the data in the database files using db_dump -r or db_dump -R and than reload the data using db_load; see the Dumping and Reloading Databases doc section in the Berkeley DB Programmer's Reference Guide.
    Regards,
    Andrei

  • Version Cue Data Files on iSCSI target?

    I know the documentation for Version Cue server says you can't save the data files on a network drive, but what about a NAS or SAN via iSCSI? I attempted to make the connection on my system, but Version Cue complains about an open file condition. Anyone have any success doing this or is Version Cue just not robust enough?

    What you want to do is add a DVD-ROM folder to your DVD. That is a folder that can contain any type of file and is invisible when played on a set top player but can be accessed on any computer.
    Since you don't have DVDSP I'm guessing that you're using iDVD. If so have a look at this:
    http://www.peachpit.com/articles/article.aspx?p=1355450&seqNum=12
    If you're using Toast, there should be a "Include DVD ROM content" somewhere near the bottom of the window.
    mish

  • Log File Corruption

    hi,
    I have a problem, Can you help me.
    I receive the following error messages when i tried open oracle instance.
    ORA-00368:checksum error in redo log block
    ORA-00353:log corruption near block 20116 change 10067984 time 08/22/2005 10:13:18
    ORA-00312:online log 1 thread 1: 'D:\ORACLE\ORADATA\MYDB\REDO01.LOG'

    I realized that you were getting this error when you are starting the database.
    Rename this file and copy over a good member from the same group
    or
    Drop the file and allow the database to use the other members

  • Recover from currnet log file corruption in archive mode

    Hi,
    I am using oracle 10.2.0 on windows xp. my database is in archivelog mode. I am learning recovery. I take backup of database using
    RMAN> backup database;
    Starting backup at 03-SEP-09
    using channel ORA_DISK_1
    channel ORA_DISK_1: starting full datafile backupset
    channel ORA_DISK_1: specifying datafile(s) in backupset
    input datafile fno=00004 name=D:\ORACLE\PRODUCT\10.2.0\ORADATA\ORCL\USERS01.DBF
    input datafile fno=00001 name=D:\ORACLE\PRODUCT\10.2.0\ORADATA\ORCL\SYSTEM01.DBF
    input datafile fno=00003 name=D:\ORACLE\PRODUCT\10.2.0\ORADATA\ORCL\SYSAUX01.DBF
    input datafile fno=00002 name=D:\ORACLE\PRODUCT\10.2.0\ORADATA\ORCL\UNDOTBS01.DBF
    channel ORA_DISK_1: starting piece 1 at 03-SEP-09which completed.
    my current logfile and current sequence no is
    SQL> select * from v$log;
        GROUP#    THREAD#  SEQUENCE#      BYTES    MEMBERS ARC STATUS
    FIRST_CHANGE# FIRST_TIM
             1          1         88   52428800          1 NO  CURRENT
          4475270 01-SEP-09
             2          1         86   52428800          1 YES INACTIVE
          4426127 31-AUG-09
             3          1         87   52428800          1 YES INACTIVEThen i delete my only one redolog file in my current group. my instance crashes i want to recover now first i try
    SQL> startup
    ORACLE instance started.
    Total System Global Area  289406976 bytes
    Fixed Size                  1248576 bytes
    Variable Size              92275392 bytes
    Database Buffers          188743680 bytes
    Redo Buffers                7139328 bytes
    Database mounted.
    ORA-00313: open failed for members of log group 1 of thread 1
    ORA-00312: online log 1 thread 1:
    'D:\ORACLE\PRODUCT\10.2.0\ORADATA\ORCL\REDO01.LOG'
    ORA-27041: unable to open file
    OSD-04002: unable to open file
    O/S-Error: (OS 2) The system cannot find the file specified.
    SQL> select open_mode from v$database;
    OPEN_MODE
    MOUNTED
    SQL> recover database until cancel;
    ORA-00279: change 4500421 generated at 09/03/2009 10:49:48 needed for thread 1
    ORA-00289: suggestion : D:\1\ARC00088_0693601900.001
    ORA-00280: change 4500421 for thread 1 is in sequence #88
    Specify log: {<RET>=suggested | filename | AUTO | CANCEL}
    cancel
    ORA-01547: warning: RECOVER succeeded but OPEN RESETLOGS would get error below
    ORA-01194: file 1 needs more recovery to be consistent
    ORA-01110: data file 1: 'D:\ORACLE\PRODUCT\10.2.0\ORADATA\ORCL\SYSTEM01.DBF'
    ORA-01112: media recovery not startedit doesn't work then i do
    RMAN> restore database
    2> ;
    Starting restore at 03-SEP-09
    using target database control file instead of recovery catalog
    allocated channel: ORA_DISK_1
    channel ORA_DISK_1: sid=156 devtype=DISK
    channel ORA_DISK_1: starting datafile backupset restore
    channel ORA_DISK_1: specifying datafile(s) to restore from backup set
    restoring datafile 00001 to D:\ORACLE\PRODUCT\10.2.0\ORADATA\ORCL\SYSTEM01.DBF
    restoring datafile 00002 to D:\ORACLE\PRODUCT\10.2.0\ORADATA\ORCL\UNDOTBS01.DBF
    restoring datafile 00003 to D:\ORACLE\PRODUCT\10.2.0\ORADATA\ORCL\SYSAUX01.DBF
    restoring datafile 00004 to D:\ORACLE\PRODUCT\10.2.0\ORADATA\ORCL\USERS01.DBF
    channel ORA_DISK_1: reading from backup piece D:\ORACLE\PRODUCT\10.2.0\FLASH_RECOVERY_AREA\ORCL\BACKUPSET\2009_09_03
    KP
    channel ORA_DISK_1: restored backup piece 1
    piece handle=D:\ORACLE\PRODUCT\10.2.0\FLASH_RECOVERY_AREA\ORCL\BACKUPSET\2009_09_03\O1_MF_NNNDF_TAG20090903T104947_5
    channel ORA_DISK_1: restore complete, elapsed time: 00:02:16
    Finished restore at 03-SEP-09
    RMAN>
    RMAN> recover database until sequence 87;
    Starting recover at 03-SEP-09
    using channel ORA_DISK_1
    RMAN-00571: ===========================================================
    RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
    RMAN-00571: ===========================================================
    RMAN-03002: failure of recover command at 09/03/2009 11:06:06
    RMAN-06556: datafile 1 must be restored from backup older than scn 4444743It means i need an older backup but i have new backup how to restore or get my database up.
    Thanks
    umesh

    Thanks for reply
    i have this in my hand
    RMAN> list backupset;
    List of Backup Sets
    ===================
    BS Key  Type LV Size       Device Type Elapsed Time Completion Time
    1       Full    1.38G      DISK        00:02:21     03-SEP-09
            BP Key: 1   Status: AVAILABLE  Compressed: NO  Tag: TAG20090903T104947
            Piece Name: D:\ORACLE\PRODUCT\10.2.0\FLASH_RECOVERY_AREA\ORCL\BACKUPSET\2009_09_03\O1_MF_NNNDF_TAG20090903T104947_59YNHNSK_.BKP
      List of Datafiles in backup set 1
      File LV Type Ckp SCN    Ckp Time  Name
      1       Full 4500421    03-SEP-09 D:\ORACLE\PRODUCT\10.2.0\ORADATA\ORCL\SYSTEM01.DBF
      2       Full 4500421    03-SEP-09 D:\ORACLE\PRODUCT\10.2.0\ORADATA\ORCL\UNDOTBS01.DBF
      3       Full 4500421    03-SEP-09 D:\ORACLE\PRODUCT\10.2.0\ORADATA\ORCL\SYSAUX01.DBF
      4       Full 4500421    03-SEP-09 D:\ORACLE\PRODUCT\10.2.0\ORADATA\ORCL\USERS01.DBF
    BS Key  Type LV Size       Device Type Elapsed Time Completion Time
    2       Full    6.80M      DISK        00:00:03     03-SEP-09
            BP Key: 2   Status: AVAILABLE  Compressed: NO  Tag: TAG20090903T104947
            Piece Name: D:\ORACLE\PRODUCT\10.2.0\FLASH_RECOVERY_AREA\ORCL\BACKUPSET\2009_09_03\O1_MF_NCSNF_TAG20090903T104947_59YNN8J9_.BKP
      Control File Included: Ckp SCN: 4500486      Ckp time: 03-SEP-09
      SPFILE Included: Modification time: 03-SEP-09
    RMAN> restore database preview;
    Starting restore at 03-SEP-09
    using channel ORA_DISK_1
    List of Backup Sets
    ===================
    BS Key  Type LV Size       Device Type Elapsed Time Completion Time
    1       Full    1.38G      DISK        00:02:21     03-SEP-09
            BP Key: 1   Status: AVAILABLE  Compressed: NO  Tag: TAG20090903T104947
            Piece Name: D:\ORACLE\PRODUCT\10.2.0\FLASH_RECOVERY_AREA\ORCL\BACKUPSET\2009_09_03\O1_MF_NNNDF_TAG20090903T104947_59YNHNSK_.BKP
      List of Datafiles in backup set 1
      File LV Type Ckp SCN    Ckp Time  Name
      1       Full 4500421    03-SEP-09 D:\ORACLE\PRODUCT\10.2.0\ORADATA\ORCL\SYSTEM01.DBF
      2       Full 4500421    03-SEP-09 D:\ORACLE\PRODUCT\10.2.0\ORADATA\ORCL\UNDOTBS01.DBF
      3       Full 4500421    03-SEP-09 D:\ORACLE\PRODUCT\10.2.0\ORADATA\ORCL\SYSAUX01.DBF
      4       Full 4500421    03-SEP-09 D:\ORACLE\PRODUCT\10.2.0\ORADATA\ORCL\USERS01.DBF
    archive logs generated after SCN 4500421 not found in repository
    Media recovery start SCN is 4500421
    Recovery must be done beyond SCN 4500421 to clear data files fuzziness
    Finished restore at 03-SEP-09
    RMAN> backup archivelog all ;
    Starting backup at 03-SEP-09
    using channel ORA_DISK_1
    channel ORA_DISK_1: starting archive log backupset
    channel ORA_DISK_1: specifying archive log(s) in backup set
    input archive log thread=1 sequence=60 recid=3 stamp=694522772
    input archive log thread=1 sequence=61 recid=4 stamp=694543115
    input archive log thread=1 sequence=62 recid=5 stamp=694693173
    input archive log thread=1 sequence=63 recid=6 stamp=694707783
    input archive log thread=1 sequence=64 recid=7 stamp=694785054
    input archive log thread=1 sequence=65 recid=8 stamp=694787797
    input archive log thread=1 sequence=66 recid=9 stamp=694794198
    input archive log thread=1 sequence=67 recid=10 stamp=694799765
    input archive log thread=1 sequence=68 recid=11 stamp=694806827
    input archive log thread=1 sequence=69 recid=12 stamp=694809124
    input archive log thread=1 sequence=70 recid=13 stamp=694868744
    input archive log thread=1 sequence=71 recid=14 stamp=695132728
    input archive log thread=1 sequence=72 recid=15 stamp=695210729
    input archive log thread=1 sequence=73 recid=16 stamp=695330401
    input archive log thread=1 sequence=74 recid=17 stamp=695399695
    input archive log thread=1 sequence=75 recid=18 stamp=695412690
    input archive log thread=1 sequence=76 recid=19 stamp=695511043
    input archive log thread=1 sequence=77 recid=20 stamp=695557945
    input archive log thread=1 sequence=78 recid=21 stamp=695597432
    input archive log thread=1 sequence=79 recid=22 stamp=695728451
    input archive log thread=1 sequence=80 recid=23 stamp=695729334
    input archive log thread=1 sequence=81 recid=24 stamp=695729976
    input archive log thread=1 sequence=82 recid=25 stamp=695835471
    input archive log thread=1 sequence=83 recid=26 stamp=695988878
    input archive log thread=1 sequence=84 recid=27 stamp=696160938
    input archive log thread=1 sequence=85 recid=28 stamp=696333853
    input archive log thread=1 sequence=86 recid=29 stamp=696360658
    input archive log thread=1 sequence=87 recid=30 stamp=696454218
    channel ORA_DISK_1: starting piece 1 at 03-SEP-09
    channel ORA_DISK_1: finished piece 1 at 03-SEP-09
    piece handle=D:\ORACLE\PRODUCT\10.2.0\FLASH_RECOVERY_AREA\ORCL\BACKUPSET\2009_09_03\O1_MF_ANNNN_TAG20090903T115246_59YR5VRV_.BKP tag=TAG20090903T1
    =NONE
    channel ORA_DISK_1: backup set complete, elapsed time: 00:01:08
    Finished backup at 03-SEP-09
    RMAN> restore database preview;
    Starting restore at 03-SEP-09
    using channel ORA_DISK_1
    List of Backup Sets
    ===================
    BS Key  Type LV Size       Device Type Elapsed Time Completion Time
    1       Full    1.38G      DISK        00:02:21     03-SEP-09
            BP Key: 1   Status: AVAILABLE  Compressed: NO  Tag: TAG20090903T104947
            Piece Name: D:\ORACLE\PRODUCT\10.2.0\FLASH_RECOVERY_AREA\ORCL\BACKUPSET\2009_09_03\O1_MF_NNNDF_TAG20090903T104947_59YNHNSK_.BKP
      List of Datafiles in backup set 1
      File LV Type Ckp SCN    Ckp Time  Name
      1       Full 4500421    03-SEP-09 D:\ORACLE\PRODUCT\10.2.0\ORADATA\ORCL\SYSTEM01.DBF
      2       Full 4500421    03-SEP-09 D:\ORACLE\PRODUCT\10.2.0\ORADATA\ORCL\UNDOTBS01.DBF
      3       Full 4500421    03-SEP-09 D:\ORACLE\PRODUCT\10.2.0\ORADATA\ORCL\SYSAUX01.DBF
      4       Full 4500421    03-SEP-09 D:\ORACLE\PRODUCT\10.2.0\ORADATA\ORCL\USERS01.DBF
    archive logs generated after SCN 4500421 not found in repository
    Media recovery start SCN is 4500421
    Recovery must be done beyond SCN 4500421 to clear data files fuzziness
    Finished restore at 03-SEP-09now i have two backup one is full database backup which will not work another is backup of all archivelog upto sequence 87 i think it should work.
    but rman is choosing full database backup for restore.
    so i need to force rman to choose archivelog backups for restore but don't know how to do it. please suggest.
    Thanks
    umesh

  • Corrupt log file, but how does db keep working?

    We recently had a fairly devastating outage involving a hard drive failure, but are a little mystified about the mechanics of what went on with berkeleydb which I hope someone here can clear up.
    A hard drive running a production instance failed because of a disk error, and we had to do a hard reboot to get the system to come back up and right itself (we are running RedHat Enterprise). We actually had three production environments running on that machine, and two came back just fine, but in one, we would get this during recovery:
    BDBStorage> Running recovery.
    BerkeleyDB> : Log file corrupt at LSN: [4906][8294478]
    BerkeleyDB> : PANIC: Invalid argument
    BerkeleyDB> : /usr/local/BerkeleyDB.4.8/lib/libdb_java-4.8.so(__os_stack+0x20) [0x2c23af2380]
    BerkeleyDB> : /usr/local/BerkeleyDB.4.8/lib/libdb_java-4.8.so(__os_abort+0x15) [0x2c23aee9c9]
    BerkeleyDB> : /usr/local/BerkeleyDB.4.8/lib/libdb_java-4.8.so(__env_panic+0xef) [0x2c23a796f9]
    BerkeleyDB> : /usr/local/BerkeleyDB.4.8/lib/libdb_java-4.8.so(__env_attach_regions+0x788) [0x2c23aae82c]
    BerkeleyDB> : /usr/local/BerkeleyDB.4.8/lib/libdb_java-4.8.so(__env_open+0x130) [0x2c23aad1e7]
    BerkeleyDB> : /usr/local/BerkeleyDB.4.8/lib/libdb_java-4.8.so(__env_open_pp+0x2e7) [0x2c23aad0af]
    BerkeleyDB> : /usr/local/BerkeleyDB.4.8/lib/libdb_java-4.8.so [0x2c23949dc7]
    BerkeleyDB> : /usr/local/BerkeleyDB.4.8/lib/libdb_java-4.8.so(Java_com_sleepycat_db_internal_db_1javaJNI_DbEnv_1open+0xbc) [0x2c239526ea]
    BerkeleyDB> : [0x2a99596e77]
    We thought, well, perhaps this is related to the disk error, it corrupted a log file and then died. Luckily (or so we thought) we diligently do backups twice a day, and keep a week's worth around. These are made using the standard backup procedure described in the developer's guide, and whenever we've had to restore them, they have been just fine (we've been using our basic setup for something like 9 years now). However, as we retrieved backup after backup, going back three or four days, they all had similar errors, always starting with [4096]. Then we noticed an odd log file, numbered with 4096, which sat around in our logs directory ever since it was created. Eventually we found a good backup, but the customer lost several days' worth of work.
    My question here is, how could a log file be corrupted for days and days but not be noticed, say during a checkpoint (which we run every minute or so)? Doesn't a checkpoint itself basically scan the logs, and shouldn't that have hit the corrupt part not long after it was written? The system was running without incident, getting fairly heavy use, so it really mystifies me as to how that issue could be sitting around for days and days like that.
    For now all we can promise the customer is that we will automatically restore every backup as soon as it's made, and if something like this happens, we immediately try a graceful shutdown, and if that doesn't come back up, we automatically go back to the 12-hour-old backup. And perhaps we should be doing that anyway, but still, I would like to understand what happened here. Any ideas?

    Please note, I don't want to make it sound like I'm somehow blaming berkeleydb for the outage-- we realize in hindsight there were better things to do than go back to an old backup, but the customer wanted an immediate answer, even if it was suboptimal. I just feel like I am missing something major about how the system works.

  • Version Cue CS4 Missing, Fatal Error!!! (Mac OS)

    I bought the PS CS4 for OSX alone, without the suite. Although I figured that this would be great and all and everything would work. Although what I learned is that without buying the suite you dont get a copy of version cue. Okay, Im thinking this is fine and all, untill I then start up Photoshop and start a new image, at which point Im greeted with this error:
    Fatal error - missing component
    The complete error message is in the picture
    I checked out the forums and found help on disabling the options for versioncue, although they didnt help at all and the issue is still there.
    Please help, I have to get PS working for my job, and Adobe Support wont help me.

    michaelkemp2 wrote:
    …what I learned is that without buying the suite you dont get a copy of version cue.
    That is not true at all, Michael.
    I have never bought any version of the suite, and the Adobe Version Cue support files have been installed by Photoshop 10.x and 11.x.
    For some reason you have a bad install.
    Try using the Adobe Uninstaller to uninstall Photoshop 11.  Then Repair Permissions with Apple's Disk Utility.  Then install Photoshop, and Repair Permissions once again.
    DO NOT move the Photoshop icon, nor the Photoshop folder from the default install location in the root Applications folder.
    Once you're up and running, apply all available updates.
    If you're still having problems after that, please give details about your machine, OS, etc.

  • SNTP log file on cRIO9024

    Hello,
    I have a question regarding the file "ts_sntp_log.txt" that is written on the internal disc of the cRIO when the device is synchronized to an NTP server. I have performed a measurement where the network latency is relevant to know. I am now trying to analyze the log file in Matlab.
    This is the only info I can find regarding the time format on the file:
    http://digital.ni.com/public.nsf/allkb/F2B057C72B5​37EA2862572D100646D43
    and
    http://www.faqs.org/rfcs/rfc2030.html
    The timestamps in my Tdms file are correct, so I suppose that the cRIO managed to synchronize to the NTP server during the measurement.
    This is a few lines from my log file
    2eb2c57243acbbd3: 98999630.450878, 000008199a840185, 2eb2c5724049c687, 2eb2c572404be4a6, 000008199a876693
    2eb2c5803c13647d: 98999633.822424, 0000081afc93ea5f, 2eb2c58038b10bbc, 2eb2c58038b32a62, 0000081afc976f60
    2eb2c58e347e54d9: 98999644.899869, 0000081c5ea3cdb7, 2eb2c58e3120db8b, 2eb2c58e312365e0, 0000081c5ea85bd3
    As I have interpreted the reference documents, the first number is the time on the cRIO formatted so that the first 8 digits are the number of whole seconds starting from 1900-01-01. My measurement was carried out in 2010 so this number should be
    (2011-1900)*365*24*3600 = 3.500496e+009
    I use the following Matlab lines to convert the hex-number into whole seconds
    ts = '2eb2c57243acbbd3';
    sec_from_1900 = hex2dec(['00000000',ts(1:8)])
    which turns out to be 783468043, i.e., approx 25 years.
    Am I doing something wrong, or is the log file corrupt? If it is corrupt, how can the timing info in my Tdms file still be correct?
    I would be very greatful for some help on this.
    Regards // Johan

    Hello again everyone,
    Is there really nobody out there who has got some information on this? I still believe that the hexadecimal numbers in the file ts_sntp_log.txt are correct since the timestamps written i my TDMS files are correct. I cannot understand the format in the log file though, and the support people at NI sweden has not been able to help me either. I now get the year 1999.
    Does anyone know where to find the exact algorithm for recalculating timestamps (in seconds) in LabView into yy-mm-dd HH:MMS.FFFFFF - format?
    I attach my files and would be very helpful if somebody could have a look at them. Unfortunately the upload function rejected Matlab files so I had to change the file extension into .txt. Just change the following:
       replaceinfile.txt --> replaceinfile.m 
       import_ts_sntp_log.txt --> import_ts_sntp_log.m
    and it should work fine.
    Regards
    Johan
    Attachments:
    ts_sntp_log.txt ‏157 KB
    replaceinfile.txt ‏3 KB
    import_ts_sntp_log.txt ‏3 KB

  • Version cue.dll missing and cannot right click

    Whenever I try to right click on any of my desktop files I get a pop up menu which says entitled explorer.exe – Fatal Application Exit and then the following error message:
    The specified module could not be found. C:\Program Files\Common Files\Adobe\Adobe Version Cue CS4\Client\4.0.0\Version Cue.dll
    I’ve uninstalled all Adobe files on my computer and still get this error message.
    I have looked at some of the Adobe forums messages which suggest copying the Version Cue.dll files in C:\Program Files\Common Files\Adobe\Adobe Version Cue CS4\Client\4.0.0\Version Cue.dll into a 4.0.1 folder however I do no have a Version Cue folder in my Common files\Adobe folder.
    Please advise asap as my company does not provide IT support for Adobe products and want to reimage my computer to resolve this problem.
    Thanks

    I just wanted to make a note that I read some of the other solutions posted to similar questions and was able to resolve the
    issue by moving the Adobe Drive folder out of the Adobe folder within the Common files folder.
    The right click problem went away however I'm having problems now reinstalling Acrobat Pro Extended. I'm not sure if this is related.

  • Redo log files lost in Disk Corruption/failure

    DB version:10gR2
    In one of our test databases, I have lost all members of a group due to disk corruption(it was a bad practise to store both members on the same filesystem)
    Database is still up. We don't have a backup of the lost redo log group. Altogether we had 3 redo log groups. this is what i am going to do to fix this issue.
    Step 1. Add a redo log group
    ALTER DATABASE
    ADD LOGFILE ('/u04/oradata/ora67tst/log4a.rdo',
       '/u05/oradata/ora67tst/log4b.rdo') SIZE 15m;Step 2. Drop the corrupted redo log group
    ALTER DATABASE DROP LOGFILE GROUP 2;Is this the right way to go about fixing this issue?
    The documentation says that you need to make sure a redo log group is archived before you DROP it.
    When i use the query
    SQL>SELECT GROUP#, ARCHIVED, STATUS FROM V$LOG;
        GROUP# ARC STATUS
             1 YES  ACTIVE
             2 NO  CURRENT
             3 NO  INACTIVE
    How can i force the archiving of a redo log group 2?
    Edited by: Citizen_2 on May 28, 2009 10:10 AM
    Edited by: Citizen_2 on May 28, 2009 10:11 AM

    Citizen_2 wrote:
    How can i force the archiving of a redo log group 2?How could you archive a log group when you have lost all members of that group?
    Have you checked out this documentation: [Recovering After the Loss of Online Redo Log Files|file://///castle/1862/Home%20Directories/Vaillancourt/Oracle%2010gR2%20Doc/backup.102/b14191/recoscen008.htm#sthref1872]
    More specifically:
    If the group is . . .      Current      
    Then . . .
    It is the log that the database is currently writing to.
    And you should . . .
    Attempt to clear the log; if impossible, then you must restore a backup and perform incomplete recovery up to the most recent available redo log.
    >
    HTH!

  • Block corruption error keep on repeating in alert log file

    Hi,
    Oracle version : 9.2.0.8.0
    os : sun soalris
    error in alert log file:
    Errors in file /u01/app/oracle/admin/qtrain/bdump/qtrain_smon_24925.trc:
    ORA-00604: error occurred at recursive SQL level 1
    ORA-01578: ORACLE data block corrupted (file # 1, block # 19750)
    ORA-01110: data file 1: '/u01/app/oracle/admin/qtrain/dbfiles/system.dbf'system datafile is restored from backup still the error is logged in alert log file
    Inputs are appreciated.
    Thanks
    Prakash

    Hi,
    Thanks for the inputs
    OWNER                          SEGMENT_NAME                                                                      PARTITION_NAME                 SEGMENT_TYPE       TABLESPACE_NAME                 EXTENT_ID    FILE_ID   BLOCK_ID      BYTES     BLOCKS RELATIVE_FNO
    SYS                            SMON_SCN_TO_TIME                                                                                                 CLUSTER            SYSTEM                                  1          1      19749      16384          1            1
    SYS                            SMON_SCN_TO_TIME                                                                                                 CLUSTER            SYSTEM                                  2          1      19750      32768          2            1Thanks
    Prakash

  • Two separate versions of the same file corrupted in different ways...

    I was working on a Photoshop CS4 file last night that was created in CS4 and has only been opened on this machine in CS4. I saved the file and closed Photoshop. When I open the file today, all my layers are gone, flattened into one Background layer, and the image looks like colored TV static. On top of that, the separate, older version of this file with a different name (created earlier in the week on the same machine in the same CS4) will not open at all - I get the error message, "Could not complete your request because the file is empty" and the file size has mysteriously shrunk to 76 KB from 20+ MB. What happened?! I'm guessing these files are corrupted beyond recovery, but why and how did this happen? Has anyone had this or a similar problem? I want to know how to prevent this from happening in the future. Please help! Thank you. =)

    Thanks for the suggestion, Chris.
    Same issue, new question - don't ask me why I did this, but while both Photoshop and the now corrupted file were open, I changed the name of the folder containing the file, then continued to save the open version of the file without first closing it and reopening it from the newly renamed folder. Could this have caused both files in that folder to become corrupted in different ways? The other file that gives me the "file is empty" error was not open at the time, but it was in that folder. I'm thinking maybe by changing the path to the files while Photoshop was running, that could have triggered this. ?? I have 3 1TB internal drives raided to read as 1 drive, so I'm really hoping that one of these disks is not dying on me as you suggested. I was also backing up an external drive using BackBlaze when this all occurred - any possible connection? How can I find out if one of my three raided drives (and which one) might be going bad?
    Thanks!!

  • Corrupt LOG File MaxDB 7.5 (Netweaver 04)

    At the Installation the LOG went full. LOG-Mode = SINGLE.
    Then I have added a new LOG File. Nothing happens. After rebooting the maschine,
    the database doesnt come up, in krnldiag there is following:
    2004-11-14 22:46:30  7579     11000 vattach  '/sapdb/XI3/sapdata/DISKD0001' devno 1 T58 succeeded
    2004-11-14 22:46:30  7520     11597 IO       Open '/sapdb/XI3/saplog/DISKL001' successfull, fd: 16
    2004-11-14 22:46:30  7633     12821 TASKING  Thread 7633 starting
    2004-11-14 22:46:30  7632     11565 startup  DEVi started
    2004-11-14 22:46:30  7520     11597 IO       Open '/sapdb/XI3/saplog/DISKL001' successfull, fd: 17
    2004-11-14 22:46:30  7634     12821 TASKING  Thread 7634 starting
    2004-11-14 22:46:30  7633     11565 startup  DEVi started
    2004-11-14 22:46:30  7579     11000 vattach  '/sapdb/XI3/saplog/DISKL001' devno 2 T58 succeeded
    2004-11-14 22:46:30  7520     11597 IO       Open '/data2/sapdb/XI3/DISKL002' successfull, fd: 19
    2004-11-14 22:46:30  7635     12821 TASKING  Thread 7635 starting
    2004-11-14 22:46:30  7634     11565 startup  DEVi started
    2004-11-14 22:46:30  7520     11597 IO       Open '/data2/sapdb/XI3/DISKL002' successfull, fd: 20
    2004-11-14 22:46:30  7636     12821 TASKING  Thread 7636 starting
    2004-11-14 22:46:30  7635     11565 startup  DEVi started
    2004-11-14 22:46:30  7579     11000 vattach  '/data2/sapdb/XI3/DISKL002' devno 3 T58 succeeded
    2004-11-14 22:46:30  7579 ERR    30 IOMan    Log volume configuration corrupted: Linkage missmatch between volume 1 and 2
    2004-11-14 22:46:30  7579     11000 vdetach  '/sapdb/XI3/sapdata/DISKD0001' devno 1 T58
    2004-11-14 22:46:30  7520     12822 TASKING  Thread 7631 joining
    2004-11-14 22:46:30  7636     11565 startup  DEVi started
    2004-11-14 22:46:30  7631     11566 stop     DEVi stopped
    2004-11-14 22:46:30  7520     12822 TASKING  Thread 7632 joining
    2004-11-14 22:46:30  7579 ERR    16 Admin    RestartFilesystem failed with 'I/O error'
    2004-11-14 22:46:30  7579 ERR     8 Admin    ERROR 'disk_not_accessibl' CAUSED EMERGENCY SHUTDOWN
    2004-11-14 22:46:30  7579     12696 DBSTATE  Change DbState to 'SHUTDOWN'(25)
    Is there any way to delete the corrupt LOG files in order to add new one? The data file is ok.
    Thanks
    Helmut

    Thread was also opened on the Mailing list:
    Here is the answer
    Hi,
    in most situations an "add log volume" does not solve
    a log full situation, because the added logvolume is
    accessible first at the moment, when the write position
    on the log is at the end of the old logvolume.
    If a LOGFULL occurs, the save log!
    All "parts" of the LogVolume are numbered and each one
    has stored the identifying number of it's predecessor and
    it successor in it's header-page. The message
         "Linkage missmatch between volume"
    means, that these values does not match any more.
    Did you somehow changed the contents of this file/device?
    If so: can you revert the change? Then the restart should
    work again. do a logbackup and your database will run again.
    If this doesn't work for you, you could patch the
    header pages of the logvolume (I assume you do not really
    want this).
    Another way to solve the situation is to do a data backup
    in admin-mode, reinstall the database and recover the
    databackup, because the removal of a logvolume is not
    supported.
    kind regards, Martin

Maybe you are looking for

  • Adobe Photoshop CS6 (version étudiante) a cessé de fonctionner

    Bonjour ! Voilà, depuis quelques jours, Photoshop plante à l'initialisation. La fenêtre s'ouvre et bloque pendant le chargement sur "initialisation des menus". En redémarrant mon ordi, photoshop a fini par s'ouvrir, mais à planter sans raison (pas de

  • Mother board failure in Compaq Presario C770TU Notebook PC

    Dear, My  Compaq Presario C770TU Notebook PC has an problem during windows installation. it hangs out during the installation process. when the step of 39 minutes is going on. earlier i have changed my battry from hp care centre. i have shown to IT p

  • Old IMac 17'' video sync problem at boot

    Hi, A friend has brought his IMac 17'', which has a video sync problem. At boot, all screen lines are out of sync, but I can more or less recognize the apple logo, which disappears later. Something happens at least, there is a boot processing going o

  • Up date ups with previus password

    I need to up date severas Apps that i used an old ID of which I forgot the password . How can I retrieve an old password ?

  • CSS files won't upload to server after update

    Hi, I checked 'Automaticaly upload files to server on save' But it when I make changes to the css in the css panel or in the file, the css file is never put on the server. Even if I open the css file and save it, it still doesn't get put on the serve