Expire log backup info

Looking at m_backup_catalog* views for a monitoring solution for backups I realized that there is no way to expire backup information from the catalog.
After approx 6 months of use I see 60K entries in m_backup_catalog, most of course log backups. With a scale out solution this would be multiplied with amount of hosts AFAIR, and could reach a million+ log backups a year.
Is there truly no expiration command for backup history, or a parameter? Reading through sql guide, backup guide, admin guide and monitoring views guide among others I see nothing on that subject. Perhaps I'm just missing something obvious and there is a way to expire backup info.

Hi Robert,
nice to see you're active in the HANA field :-)
Right now (that is SPS4) there is no supported way to shorten the backup history/catalog.
But afaik there will likelyl be an official feature for that in later versions.
For now, this doesn't pose any problem and should this turn out to become one with larger scale-out systems running OLTP traffic, then this will of course be changed.
BTW: you reported roughly 10K catalog entries per month and node.
For a 5 node cluster - that means it'll take 20 months to reach the million lines.
And if it does - so what?
cheers,
Lars

Similar Messages

  • In Log-shipping what is load delay period on secondary server - Skipping log backup file since load delay period has not expired ....

    During logshipping, job on secondary server is ran successfully BUT give this information
    "Skipping log backup file since load delay period has not expired ...."
    What is this "Load delay period" ? Can we configure this somehow, somewhere ?
    NOTE : The value on "Restore Transasction Log tab", Delay Restoring backups at least = Default (zero minutes)
    Thanks
    Think BIG but Positive, may be GLOBAL better UNIVERSAL.

    How to get the LSBackup, LSCopy, and LSRestore jobs back in sync...
    Last I posted the issue was that my trn backups were not being copied from Primary to Secondary. 
    I found upon further inspection of the LS related tables  in MSDB the following likely candidates for adjustment:
    1) dbo.log_shipping_monitor_secondary, column  last_copied_file 
    change last copied file column to something older than the file that is stuck. For example, the value in the table was 
    E:\SQLLogShip\myDB_20140527150001.trn
    I changed last_copied_file to E:\SQLLogShip\myDB_20140525235000.trn. Note that this is just a made up file name that is a few minutes before the actual file that I would like to restore (myDB_2014525235428.trn). 4 mins and 28 seconds before, to
    be exact.
    LSCOPY runs and voila! now it is copied from primary to secondary. That appears to be the only change needed to get the copy going again.
    2) For LSRestore, see the MSDB table dbo.log_shipping_monitor_secondary, change
    last_restored_file
    again I used the made up file E:\SQLLogShip\myDB_20140525235000.trn
    LSRESTORE runs and my just copied myDB_2014525235428.trn is restored
    ** note that
    dbo.log_shipping_secondary_databases also has a last_restored_file column - this did not seem to have any effect, though I see that it updates after completing the above and LSRestore has run successfully, so now it is correct as well
    3) LSBackup job is still not running, the job still has a last run date in the future. Could just leave it and eventually it will come right, but I made a fairly significant time change, plus it's all an experiment....back to MSDB.
    look at dbo.sysjobs, get the job_id of your LSBackup job
    edit dbo.sysjobschedules - change next_run_date  next_run_time as needed to a datetime before the current time, or when you would like the job to start running. 
    I wouldn't be so cavalier with data that was important, but that's the benefit of being in Test, and it appears that these time comparisons are very rudimentary - a value in the relevant log shipping table and the name of the trn file. That said, if you
    were facing a problem of this nature due to lost trn files, corrupted, or some similar scenario, this wouldn't fix your problem, though it _might_ allow you to continue? But in my case I know I have all the trn files, it's just the time that changed, in this
    case on my Primary server, and thus the names of the trn logs got out sync.

  • RMAN never deletes archive log backups

    Hi all,
    I have same problem as some of you have already faced.
    I have some instances 10.2.0.4 running un archive log mode.
    I take full hot backup daily.
    I setup a rman script to backup and delete obsolete backups according to the following policy:
    CONFIGURE RETENTION POLICY TO RECOVERY WINDOW OF 2 DAYS;
    CONFIGURE RETENTION POLICY TO REDUNDANCY 2;
    and then:
    run {
    ALLOCATE CHANNEL RMAN_BACK_CH01 TYPE DISK;
    BACKUP AS COMPRESSED BACKUPSET DATABASE FORMAT '/mnt/rman_202/pnetpres/db_pres_%U';
    CROSSCHECK ARCHIVELOG ALL;
    BACKUP AS COMPRESSED BACKUPSET ARCHIVELOG ALL FORMAT '/mnt/rman_202/pnetpres/al_pres_%U';
    CROSSCHECK BACKUP;
    DELETE NOPROMPT OBSOLETE;
    DELETE NOPROMPT EXPIRED BACKUP;
    RELEASE CHANNEL RMAN_BACK_CH01;
    crosscheck archivelog all;
    delete noprompt archivelog all completed before 'sysdate -2';
    DB full backups are being deleted, however archive logs backups are not deleted.
    There are no tablespaces in backup or offline mode.
    How can I know the reason why some archive log backups are kept ?
    Even I clear the policy and perform a crosscheck and delete, those are not marked as obsolete neither deleted from disk.
    Thanks in advance.

    Hi Fernando,
    This are the ouputpus of the commands:
    RMAN> REPORT OBSOLETE;
    RMAN retention policy will be applied to the command
    RMAN retention policy is set to redundancy 1
    no obsolete backups found
    RMAN> LIST BACKUP OF ARCHIVELOG ALL;
    List of Backup Sets
    ===================
    BS Key Size Device Type Elapsed Time Completion Time
    1090 69.65M DISK 00:00:16 23-FEB-11
    BP Key: 1093 Status: AVAILABLE Compressed: YES Tag: TAG20110223T061511
    Piece Name: /mnt/rman_202/pnetproy/al_pres_0jm5c6bf_1_1
    List of Archived Logs in backup set 1090
    Thrd Seq Low SCN Low Time Next SCN Next Time
    1 13 2173025156 21-FEB-11 2173028010 21-FEB-11
    1 14 2173028010 21-FEB-11 2173041730 21-FEB-11
    1 15 2173041730 21-FEB-11 2173041813 21-FEB-11
    1 16 2173041813 21-FEB-11 2173106066 22-FEB-11
    1 17 2173106066 22-FEB-11 2173108831 22-FEB-11
    1 18 2173108831 22-FEB-11 2173116745 22-FEB-11
    1 19 2173116745 22-FEB-11 2173117735 22-FEB-11
    1 20 2173117735 22-FEB-11 2173117739 22-FEB-11
    1 21 2173117739 22-FEB-11 2173117753 22-FEB-11
    1 22 2173117753 22-FEB-11 2173165783 23-FEB-11
    1 23 2173165783 23-FEB-11 2173168857 23-FEB-11
    BS Key Size Device Type Elapsed Time Completion Time
    1411 125.43M DISK 00:00:28 24-FEB-11
    BP Key: 1414 Status: AVAILABLE Compressed: YES Tag: TAG20110224T061643
    Piece Name: /mnt/rman_202/pnetproy/al_pres_0mm5eqqb_1_1
    List of Archived Logs in backup set 1411
    Thrd Seq Low SCN Low Time Next SCN Next Time
    1 18 2173108831 22-FEB-11 2173116745 22-FEB-11
    1 19 2173116745 22-FEB-11 2173117735 22-FEB-11
    1 20 2173117735 22-FEB-11 2173117739 22-FEB-11
    1 21 2173117739 22-FEB-11 2173117753 22-FEB-11
    1 22 2173117753 22-FEB-11 2173165783 23-FEB-11
    1 23 2173165783 23-FEB-11 2173168857 23-FEB-11
    1 24 2173168857 23-FEB-11 2173221907 23-FEB-11
    1 25 2173221907 23-FEB-11 2173246002 24-FEB-11
    1 26 2173246002 24-FEB-11 2173249177 24-FEB-11
    BS Key Size Device Type Elapsed Time Completion Time
    1600 164.40M DISK 00:00:37 25-FEB-11
    BP Key: 1603 Status: AVAILABLE Compressed: YES Tag: TAG20110225T061643
    Piece Name: /mnt/rman_202/pnetproy/al_pres_0pm5hf6b_1_1
    List of Archived Logs in backup set 1600
    Thrd Seq Low SCN Low Time Next SCN Next Time
    1 22 2173117753 22-FEB-11 2173165783 23-FEB-11
    1 23 2173165783 23-FEB-11 2173168857 23-FEB-11
    1 24 2173168857 23-FEB-11 2173221907 23-FEB-11
    1 25 2173221907 23-FEB-11 2173246002 24-FEB-11
    1 26 2173246002 24-FEB-11 2173249177 24-FEB-11
    1 27 2173249177 24-FEB-11 2173313111 25-FEB-11
    1 28 2173313111 25-FEB-11 2173316259 25-FEB-11
    BS Key Size Device Type Elapsed Time Completion Time
    1829 132.24M DISK 00:00:30 26-FEB-11
    BP Key: 1832 Status: AVAILABLE Compressed: YES Tag: TAG20110226T061627
    Piece Name: /mnt/rman_202/pnetproy/al_pres_0sm5k3hr_1_1
    List of Archived Logs in backup set 1829
    Thrd Seq Low SCN Low Time Next SCN Next Time
    1 25 2173221907 23-FEB-11 2173246002 24-FEB-11
    1 26 2173246002 24-FEB-11 2173249177 24-FEB-11
    1 27 2173249177 24-FEB-11 2173313111 25-FEB-11
    1 28 2173313111 25-FEB-11 2173316259 25-FEB-11
    1 29 2173316259 25-FEB-11 2173380316 26-FEB-11
    1 30 2173380316 26-FEB-11 2173388686 26-FEB-11
    BS Key Size Device Type Elapsed Time Completion Time
    2058 218.03M DISK 00:00:48 27-FEB-11
    BP Key: 2061 Status: AVAILABLE Compressed: YES Tag: TAG20110227T061628
    Piece Name: /mnt/rman_202/pnetproy/al_pres_0vm5mnts_1_1
    List of Archived Logs in backup set 2058
    Thrd Seq Low SCN Low Time Next SCN Next Time
    1 28 2173313111 25-FEB-11 2173316259 25-FEB-11
    1 29 2173316259 25-FEB-11 2173380316 26-FEB-11
    1 30 2173380316 26-FEB-11 2173388686 26-FEB-11
    1 31 2173388686 26-FEB-11 2173465280 27-FEB-11
    1 32 2173465280 27-FEB-11 2173499757 27-FEB-11
    1 33 2173499757 27-FEB-11 2173527280 27-FEB-11
    1 34 2173527280 27-FEB-11 2173530545 27-FEB-11
    BS Key Size Device Type Elapsed Time Completion Time
    2298 205.39M DISK 00:00:45 28-FEB-11
    BP Key: 2301 Status: AVAILABLE Compressed: YES Tag: TAG20110228T061620
    Piece Name: /mnt/rman_202/pnetproy/al_pres_12m5pc9l_1_1
    List of Archived Logs in backup set 2298
    Thrd Seq Low SCN Low Time Next SCN Next Time
    1 30 2173380316 26-FEB-11 2173388686 26-FEB-11
    1 31 2173388686 26-FEB-11 2173465280 27-FEB-11
    1 32 2173465280 27-FEB-11 2173499757 27-FEB-11
    1 33 2173499757 27-FEB-11 2173527280 27-FEB-11
    1 34 2173527280 27-FEB-11 2173530545 27-FEB-11
    1 35 2173530545 27-FEB-11 2173589000 28-FEB-11
    1 36 2173589000 28-FEB-11 2173592018 28-FEB-11
    BS Key Size Device Type Elapsed Time Completion Time
    2546 180.29M DISK 00:00:39 01-MAR-11
    BP Key: 2549 Status: AVAILABLE Compressed: YES Tag: TAG20110301T061533
    Piece Name: /mnt/rman_202/pnetproy/al_pres_15m63to5_1_1
    List of Archived Logs in backup set 2546
    Thrd Seq Low SCN Low Time Next SCN Next Time
    1 32 2173465280 27-FEB-11 2173499757 27-FEB-11
    1 33 2173499757 27-FEB-11 2173527280 27-FEB-11
    1 34 2173527280 27-FEB-11 2173530545 27-FEB-11
    1 35 2173530545 27-FEB-11 2173589000 28-FEB-11
    1 36 2173589000 28-FEB-11 2173592018 28-FEB-11
    1 37 2173592018 28-FEB-11 2173671730 01-MAR-11
    1 38 2173671730 01-MAR-11 2173674751 01-MAR-11
    BS Key Size Device Type Elapsed Time Completion Time
    2801 85.40M DISK 00:00:19 02-MAR-11
    BP Key: 2804 Status: AVAILABLE Compressed: YES Tag: TAG20110302T061613
    Piece Name: /mnt/rman_202/pnetproy/al_pres_18m66i5d_1_1
    List of Archived Logs in backup set 2801
    Thrd Seq Low SCN Low Time Next SCN Next Time
    1 36 2173589000 28-FEB-11 2173592018 28-FEB-11
    1 37 2173592018 28-FEB-11 2173671730 01-MAR-11
    1 38 2173671730 01-MAR-11 2173674751 01-MAR-11
    1 39 2173674751 01-MAR-11 2173736248 02-MAR-11
    1 40 2173736248 02-MAR-11 2173739307 02-MAR-11
    BS Key Size Device Type Elapsed Time Completion Time
    3058 137.93M DISK 00:00:30 03-MAR-11
    BP Key: 3061 Status: AVAILABLE Compressed: YES Tag: TAG20110303T061548
    Piece Name: /mnt/rman_202/pnetproy/al_pres_1bm696gk_1_1
    List of Archived Logs in backup set 3058
    Thrd Seq Low SCN Low Time Next SCN Next Time
    1 38 2173671730 01-MAR-11 2173674751 01-MAR-11
    1 39 2173674751 01-MAR-11 2173736248 02-MAR-11
    1 40 2173736248 02-MAR-11 2173739307 02-MAR-11
    1 41 2173739307 02-MAR-11 2173784198 02-MAR-11
    1 42 2173784198 02-MAR-11 2173816111 03-MAR-11
    1 43 2173816111 03-MAR-11 2173819171 03-MAR-11
    BS Key Size Device Type Elapsed Time Completion Time
    3324 138.96M DISK 00:00:31 04-MAR-11
    BP Key: 3327 Status: AVAILABLE Compressed: YES Tag: TAG20110304T061559
    Piece Name: /mnt/rman_202/pnetproy/al_pres_1em6bqsv_1_1
    List of Archived Logs in backup set 3324
    Thrd Seq Low SCN Low Time Next SCN Next Time
    1 40 2173736248 02-MAR-11 2173739307 02-MAR-11
    1 41 2173739307 02-MAR-11 2173784198 02-MAR-11
    1 42 2173784198 02-MAR-11 2173816111 03-MAR-11
    1 43 2173816111 03-MAR-11 2173819171 03-MAR-11
    1 44 2173819171 03-MAR-11 2173882472 04-MAR-11
    1 45 2173882472 04-MAR-11 2173885557 04-MAR-11
    BS Key Size Device Type Elapsed Time Completion Time
    3597 178.07M DISK 00:00:39 05-MAR-11
    BP Key: 3600 Status: AVAILABLE Compressed: YES Tag: TAG20110305T061543
    Piece Name: /mnt/rman_202/pnetproy/al_pres_1hm6ef8f_1_1
    List of Archived Logs in backup set 3597
    Thrd Seq Low SCN Low Time Next SCN Next Time
    1 41 2173739307 02-MAR-11 2173784198 02-MAR-11
    1 42 2173784198 02-MAR-11 2173816111 03-MAR-11
    1 43 2173816111 03-MAR-11 2173819171 03-MAR-11
    1 44 2173819171 03-MAR-11 2173882472 04-MAR-11
    1 45 2173882472 04-MAR-11 2173885557 04-MAR-11
    1 46 2173885557 04-MAR-11 2173947612 05-MAR-11
    1 47 2173947612 05-MAR-11 2173951657 05-MAR-11
    BS Key Size Device Type Elapsed Time Completion Time
    3835 198.44M DISK 00:00:43 06-MAR-11
    BP Key: 3838 Status: AVAILABLE Compressed: YES Tag: TAG20110306T061548
    Piece Name: /mnt/rman_202/pnetproy/al_pres_1km6h3kk_1_1
    List of Archived Logs in backup set 3835
    Thrd Seq Low SCN Low Time Next SCN Next Time
    1 45 2173882472 04-MAR-11 2173885557 04-MAR-11
    1 46 2173885557 04-MAR-11 2173947612 05-MAR-11
    1 47 2173947612 05-MAR-11 2173951657 05-MAR-11
    1 48 2173951657 05-MAR-11 2174026607 06-MAR-11
    1 49 2174026607 06-MAR-11 2174062014 06-MAR-11
    1 50 2174062014 06-MAR-11 2174087203 06-MAR-11
    1 51 2174087203 06-MAR-11 2174090299 06-MAR-11
    BS Key Size Device Type Elapsed Time Completion Time
    4131 185.94M DISK 00:00:40 07-MAR-11
    BP Key: 4134 Status: AVAILABLE Compressed: YES Tag: TAG20110307T061546
    Piece Name: /mnt/rman_202/pnetproy/al_pres_1nm6jo0i_1_1
    List of Archived Logs in backup set 4131
    Thrd Seq Low SCN Low Time Next SCN Next Time
    1 47 2173947612 05-MAR-11 2173951657 05-MAR-11
    1 48 2173951657 05-MAR-11 2174026607 06-MAR-11
    1 49 2174026607 06-MAR-11 2174062014 06-MAR-11
    1 50 2174062014 06-MAR-11 2174087203 06-MAR-11
    1 51 2174087203 06-MAR-11 2174090299 06-MAR-11
    1 52 2174090299 06-MAR-11 2174147018 07-MAR-11
    1 53 2174147018 07-MAR-11 2174149955 07-MAR-11
    BS Key Size Device Type Elapsed Time Completion Time
    4435 161.37M DISK 00:00:35 08-MAR-11
    BP Key: 4438 Status: AVAILABLE Compressed: YES Tag: TAG20110308T061540
    Piece Name: /mnt/rman_202/pnetproy/al_pres_1qm6mccc_1_1
    List of Archived Logs in backup set 4435
    Thrd Seq Low SCN Low Time Next SCN Next Time
    1 49 2174026607 06-MAR-11 2174062014 06-MAR-11
    1 50 2174062014 06-MAR-11 2174087203 06-MAR-11
    1 51 2174087203 06-MAR-11 2174090299 06-MAR-11
    1 52 2174090299 06-MAR-11 2174147018 07-MAR-11
    1 53 2174147018 07-MAR-11 2174149955 07-MAR-11
    1 54 2174149955 07-MAR-11 2174239915 08-MAR-11
    1 55 2174239915 08-MAR-11 2174242816 08-MAR-11
    BS Key Size Device Type Elapsed Time Completion Time
    4745 79.24M DISK 00:00:18 09-MAR-11
    BP Key: 4748 Status: AVAILABLE Compressed: YES Tag: TAG20110309T061555
    Piece Name: /mnt/rman_202/pnetproy/al_pres_1tm6p0os_1_1
    List of Archived Logs in backup set 4745
    Thrd Seq Low SCN Low Time Next SCN Next Time
    1 53 2174147018 07-MAR-11 2174149955 07-MAR-11
    1 54 2174149955 07-MAR-11 2174239915 08-MAR-11
    1 55 2174239915 08-MAR-11 2174242816 08-MAR-11
    1 56 2174242816 08-MAR-11 2174304682 09-MAR-11
    1 57 2174304682 09-MAR-11 2174307679 09-MAR-11
    BS Key Size Device Type Elapsed Time Completion Time
    5270 135.13M DISK 00:00:31 10-MAR-11
    BP Key: 5273 Status: AVAILABLE Compressed: YES Tag: TAG20110310T061603
    Piece Name: /mnt/rman_202/pnetproy/al_proy_20m6rl53_1_1
    List of Archived Logs in backup set 5270
    Thrd Seq Low SCN Low Time Next SCN Next Time
    1 55 2174239915 08-MAR-11 2174242816 08-MAR-11
    1 56 2174242816 08-MAR-11 2174304682 09-MAR-11
    1 57 2174304682 09-MAR-11 2174307679 09-MAR-11
    1 58 2174307679 09-MAR-11 2174353241 09-MAR-11
    1 59 2174353241 09-MAR-11 2174384330 10-MAR-11
    1 60 2174384330 10-MAR-11 2174387259 10-MAR-11
    RMAN>
    For example the backups of archivelog from Feb 21st will never be deleted unless I force the delete.
    I'd like to understand why it happens :-)
    Thanks a lot,
    Regards,
    Diego.

  • Need a Walkthrough on How to Create Database & Transaction Log Backups

    Is this the proper forum to ask for this type of guidance?  There has been bad blood between my department (Research) and the MIS department for 30 years, and long story short I have been "given" a virtual server and cut loose by my MIS department
    -- it's my responsibility for installs, updates, backups, etc.  I have everything running really well, I believe, with the exception of my transaction log backups -- my storage unit is running out of space on a daily basis, so I feel like I have to be
    doing something wrong.
    If this is the proper forum, I'll supply the details of how I currently have things set up, and I'm hoping with some loving guidance I can work the kinks out of my backup plan.  High level -- this is for a SQL Server 2012 instance running on a Windows
    2012 Server...

    Thanks all, after posting this I'm going to read the materials provided above.  As for the details:
    I'm running on a virtual Windows Server 2012 Standard, Intel Xeon CPU 2.6 GHz with 16 GB of RAM; 64 bit OS.  The computer name is e275rd8
    Drives (NTFS, Compression off, Indexing on):
    DB_HVSQL_SQL-DAT_RD8-2(E:) 199 GB (47.2 used; 152 free)
    DB_HVSQL_SQL-Dat_RD8(F:) 199 GB (10.1 used; 189 free)
    DB_HVSQL_SQL-LOG_RD8-2(L:) 199 GB (137 used; 62 free) **
    DB_HVSQL_SQL-BAK_RDu-2(S:) 99.8 GB (64.7 used; 35 free)
    DB_HVSQL_SQL-TMP_RD8-2(T:) 99.8 GB (10.6 used; 89.1 free)
    SQL Server:
    Product: SQL Server Enterprise (64-bit)
    OS: Windows NT 6.2 (9200)
    Platform: NT x64
    Version: 11.0.5058.0
    Memory: 16384 (MB)
    Processors: 4
    Root Directory: f:\Program Files\Microsoft SQL Server\MSSQL11.MSSQLSERVER\MSSQL
    Is Clustered: False
    Is HADR Enabled: False
    Database Settings:
    Default index fill factor: 0
    Default backup media retention (in days): 0
    Compress backup is checkmarked/on
    Database default locations:
      Data: E:\SQL\Data
      Log: L:\SQL\LOGs
      Backup: S:\SQLBackups
    There is currently only one database: DistrictAssessmentDW
    To create my backups, I'm using two maintenance plans, and this is where I'm pretty sure I'm not doing something correctly.  My entire setup is me just guessing what to do, so feel free to offer suggestions...
    Maintenance Plan #1: Backup DistrictAssessmentDW
      Scheduled to run daily Monday Through Friday at 3:33 AM
      Step 1: Backup Database (Full) 
        Backup set expires after 8 days 
        Back up to Disk (S:\SQLBackups)
        Set backup compression: using the default server setting
      Step 2: Maintenance Cleanup Task
        Delete files of the following type: Backup files
        Search folder and delete files based on an extension:
          Folder: L:\SQL\Logs
          File extension: trn
          Include first-level subfolders: checkmarked/on
        File age: Delete files based on the age of the file at task run time older than 1 Day
      Step 3: Maintenance Cleanup Task
        Delete files of the following type: Backup files
        Search folder and delete files based on an extension:
          Folder: S:\SQLBackups
          File extension: bak
          Include first-level subfolders: checkmarked/on
        File age: Delete files based on the age of the file at task run time older than 8 Days
    Maintenance Plan #2: Backup DistrictAssessmentDW TRANS LOG ONLY
      Scheduled to run daily Monday through Friday; every 20 minutes starting at 6:30 AM & ending at 7:00 PM
      Step 1: Backup Database Task
        Backup Type: Transaction Log
        Database(s): Specific databases (DistrictAssessmentDW)
        Backup Set will expire after 1 day
        Backup to Disk (L:\SQL\Logs\)
        Set backup compression: Use the default server setting
    Around 2:30 each day my transaction log backup drive (L:) runs out of space.  As you can see, transactions are getting backed up every 20 minutes, and the average size of the backup files is about 5,700,000 KB.
    I hope this covers everything, if not please let me know what other information I need to provide...

  • Session expired, log out.

    After reading or viewing an email attachment, try to return to emails and the message 'session expired, log out' appears and you are logged out. This is just one of numerous problems with BT Mail that never happened with Yahoo.

    Hi RoyL,
    Thanks for the post and welcome to the forum.  I am sorry to hear of the problems that you are having.  Any chance you could send me your details so that I can send on to our email teams to have a look at?
    It would really help if you could supply the following information,
    Time stamp of when the issue occurred?,
    The email address in question? and
    Does the session drop out only when viewing attachments or have you noticed other scenarios?
    If you could send me this info via email that would be great.  You will find the 'Mods contact link' under the 'About me' section of my profile.  Just click on my username (SeanD).
    Cheers
    Sean
    BTCare Community Manager
    If we have asked you to email us with your details, please make sure you are logged in to the forum, otherwise you will not be able to see our ‘Contact Us’ link within our profiles.
    We are sorry that we are unable to deal with service/account queries via the private message(PM) function so please don't PM your account info, we need to deal with this via our email account :-)

  • HT201269 I have an IPhone 4 that turns off.When I plug the phone into a outlet, it says to connect to iTunes. But my phone doesn't connect. I need to backup info to sync to a new iPhone. Is there another way to get the info from the old one?

    I have an IPhone 4 that turns off on its own. When I plug the phone into an outlet, it says to connect to iTunes. When i connect my phone to itunes, the screen displays the apple icon and doesn't connect to iTunes.  I need to backup info on this phone so I can apply my back up to a new iPhone. Is there any another way i can do this? My older phone will not show it's connected to iTunes. I used iCloud on the phone with problems, but I didn't back up all the info thru iCloud. Is there another way to back up?

    Sounds like your phone is in recovery mode.  In this case, all data on it is gone.  There's nothing to back up.

  • Getting error while taking MAX DB trans log backup.

    Hi,
    I am getting error while taking trans log backup of Maxdb database for archived log through data protector as below,
    [Critical] From: OB2BAR_SAPDBBAR@ttcmaxdb "MAX" Time: 08/19/10 02:10:41
    Unable to back up archive logs: no autolog medium found in media list
    But i am able to take complete data and incremental backup through data protector.
    I have already enabled the autolog for MAX DB database and it is writing that log file directly to HP-UX file system. Now i want to take backup of this archived log backup through data protector i.e. through trans log backup. So that the archived log which is on the file system after trans log backup completed will delete the archived logs in filesystem.  So that i don;t have to manually delete the archived logs from file system.
    Thanks,
    Subba

    Hi Lars,
    Thanks for the reply...
    Now i am able to take archive log backup but the problem is i can take only one archive file backup. Not multiple arhive log files generated by autolog at filesystem i.e /sapdb/MAX/saparch.
    I have enabled autolog and it is putting auto log file at unix directory i.e. /sapdb/MAX/saparch
    And then i am using the DataProtector 6.11 with trans log backup to backup the archived files in /sapdb/MAX/saparch. When i start the trans backup session through data protector it uses the archive stage command as "archive_stage BACKDP-Archive LOGBackup NOVERIFY REMOVE" If /sapdb/MAX/saparch has only one archive file it will backup and remove the file successfully. But if /sapdb/MAX/saparch has multiple archive files it gives an error as below,
      Preparing backup.
                Setting environment variable 'BI_CALLER' to value 'DBMSRV'.
                Setting environment variable 'BI_REQUEST' to value 'OLD'.
                Setting environment variable 'BI_BACKUP' to value 'ARCHIVE'.
                Constructed Backint for MaxDB call '/opt/omni/lbin/sapdb_backint -u MAX -f backup -t file -p SAPDB.13576.1283767878.par -i /var/opt/omni/tmp/MAX.
    bsi_in -c'.
                Created temporary file '/var/opt/omni/tmp/MAX.bsi_out' as output for Backint for MaxDB.
                Created temporary file '/var/opt/omni/tmp/MAX.bsi_err' as error output for Backint for MaxDB.
                Writing '/sapdb/data/wrk/MAX/dbm.ebf' to the input file.
                Writing '/sapdb/data/wrk/MAX/dbm.knl' to the input file.
            Prepare passed successfully.
            Starting Backint for MaxDB.
                Starting Backint for MaxDB process '/opt/omni/lbin/sapdb_backint -u MAX -f backup -t file -p SAPDB.13576.1283767878.par -i /var/opt/omni/tmp/MAX.
    bsi_in -c >>/var/opt/omni/tmp/MAX.bsi_out 2>>/var/opt/omni/tmp/MAX.bsi_err'.
                Process was started successfully.
            Backint for MaxDB has been started successfully.
            Waiting for the end of Backint for MaxDB.
                2010-09-06 03:15:21 The backup tool is running.
                2010-09-06 03:15:24 The backup tool process has finished work with return code 0.
            Ended the waiting.
            Checking output of Backint for MaxDB.
            Have found all BID's as expected.
        Have saved the Backup History files successfully.
        Cleaning up.
            Removing data transfer pipes.
                Removing data transfer pipe /var/opt/omni/tmp/MAX.BACKDP-Archive.1 ... Done.
            Removed data transfer pipes successfully.
            Copying output of Backint for MaxDB to this file.
    Begin of output of Backint for MaxDB (/var/opt/omni/tmp/MAX.bsi_out)----
                #SAVED 1009067:1 /sapdb/data/wrk/MAX/dbm.ebf
                #SAVED 1009067:1 /sapdb/data/wrk/MAX/dbm.knl
    End of output of Backint for MaxDB (/var/opt/omni/tmp/MAX.bsi_out)----
            Removed Backint for MaxDB's temporary output file '/var/opt/omni/tmp/MAX.bsi_out'.
            Copying error output of Backint for MaxDB to this file.
    Begin of error output of Backint for MaxDB (/var/opt/omni/tmp/MAX.bsi_err)----
    End of error output of Backint for MaxDB (/var/opt/omni/tmp/MAX.bsi_err)----
            Removed Backint for MaxDB's temporary error output file '/var/opt/omni/tmp/MAX.bsi_err'.
            Removed the Backint for MaxDB input file '/var/opt/omni/tmp/MAX.bsi_in'.
        Have finished clean up successfully.
    The backup of stage file '/export/sapdb/arch/MAX_LOG.040' was successful.
    2010-09-06 03:15:24
    Backing up stage file '/export/sapdb/arch/MAX_LOG.041'.
        Creating pipes for data transfer.
            Creating pipe '/var/opt/omni/tmp/MAX.BACKDP-Archive.1' ... Done.
        All data transfer pipes have been created.
        Preparing backup tool.
            Setting environment variable 'BI_CALLER' to value 'DBMSRV'.
            Setting environment variable 'BI_REQUEST' to value 'OLD'.
            Setting environment variable 'BI_BACKUP' to value 'ARCHIVE'.
            Constructed Backint for MaxDB call '/opt/omni/lbin/sapdb_backint -u MAX -f backup -t file -p SAPDB.13576.1283767878.par -i /var/opt/omni/tmp/MAX.bsi_
    in -c'.
            Created temporary file '/var/opt/omni/tmp/MAX.bsi_out' as output for Backint for MaxDB.
            Created temporary file '/var/opt/omni/tmp/MAX.bsi_err' as error output for Backint for MaxDB.
            Writing '/var/opt/omni/tmp/MAX.BACKDP-Archive.1 #PIPE' to the input file.
        Prepare passed successfully.
        Constructed pipe2file call 'pipe2file -d file2pipe -f /export/sapdb/arch/MAX_LOG.041 -p /var/opt/omni/tmp/MAX.BACKDP-Archive.1 -nowait'.
        Starting pipe2file for stage file '/export/sapdb/arch/MAX_LOG.041'.
            Starting pipe2file process 'pipe2file -d file2pipe -f /export/sapdb/arch/MAX_LOG.041 -p /var/opt/omni/tmp/MAX.BACKDP-Archive.1 -nowait >>/var/tmp/tem
    p1283767880-0 2>>/var/tmp/temp1283767880-1'.
            Process was started successfully.
        Pipe2file has been started successfully.
        Starting Backint for MaxDB.
            Starting Backint for MaxDB process '/opt/omni/lbin/sapdb_backint -u MAX -f backup -t file -p SAPDB.13576.1283767878.par -i /var/opt/omni/tmp/MAX.bsi_
    in -c >>/var/opt/omni/tmp/MAX.bsi_out 2>>/var/opt/omni/tmp/MAX.bsi_err'.
            Process was started successfully.
        Backint for MaxDB has been started successfully.
        Waiting for end of the backup operation.
            2010-09-06 03:15:25 The backup tool process has finished work with return code 2.
            2010-09-06 03:15:25 The backup tool is not running.
            2010-09-06 03:15:25 Pipe2file is running.
            2010-09-06 03:15:25 Pipe2file is running.
            2010-09-06 03:15:30 Pipe2file is running.
            2010-09-06 03:15:40 Pipe2file is running.
            2010-09-06 03:15:55 Pipe2file is running.
            2010-09-06 03:16:15 Pipe2file is running.
            Killing not reacting pipe2file process.
            Pipe2file killed successfully.
            2010-09-06 03:16:26 The pipe2file process has finished work with return code -1.
        The backup operation has ended.
        Filling reply buffer.
            Have encountered error -24920:
                The backup tool failed with 2 as sum of exit codes and pipe2file was killed.
            Constructed the following reply:
                ERR
                -24920,ERR_BACKUPOP: backup operation was unsuccessful
                The backup tool failed with 2 as sum of exit codes and pipe2file was killed.
        Reply buffer filled.
        Cleaning up.
            Removing data transfer pipes.
                Removing data transfer pipe /var/opt/omni/tmp/MAX.BACKDP-Archive.1 ... Done.
            Removed data transfer pipes successfully.
            Copying output of Backint for MaxDB to this file.
    Begin of output of Backint for MaxDB (/var/opt/omni/tmp/MAX.bsi_out)----
    End of output of Backint for MaxDB (/var/opt/omni/tmp/MAX.bsi_out)----
            Removed Backint for MaxDB's temporary output file '/var/opt/omni/tmp/MAX.bsi_out'.
            Copying error output of Backint for MaxDB to this file.
    Begin of error output of Backint for MaxDB (/var/opt/omni/tmp/MAX.bsi_err)----
    End of error output of Backint for MaxDB (/var/opt/omni/tmp/MAX.bsi_err)----
            Removed Backint for MaxDB's temporary error output file '/var/opt/omni/tmp/MAX.bsi_err'.
            Removed the Backint for MaxDB input file '/var/opt/omni/tmp/MAX.bsi_in'.
            Copying pipe2file output to this file.
    Begin of pipe2file output (/var/tmp/temp1283767880-0)----
    End of pipe2file output (/var/tmp/temp1283767880-0)----
            Removed pipe2file output '/var/tmp/temp1283767880-0'.
            Copying pipe2file error output to this file.
    Begin of pipe2file error output (/var/tmp/temp1283767880-1)----
    End of pipe2file error output (/var/tmp/temp1283767880-1)----
            Removed pipe2file error output '/var/tmp/temp1283767880-1'.
        Have finished clean up successfully.
    The backup of stage file '/export/sapdb/arch/MAX_LOG.041' was unsuccessful.
    2010-09-06 03:16:26
    Cleaning up.
        Have encountered error -24919:
            Can not remove file '/var/tmp/temp1283767880-0'.
            (System error 2; No such file or directory)
        Could not remove temporary output file of pipe2file ('/var/tmp/temp1283767880-0' ).
        Have encountered error -24919:
            Can not remove file '/var/tmp/temp1283767880-1'.
            (System error 2; No such file or directory)
        Could not remove temporary output file of pipe2file ('/var/tmp/temp1283767880-1' ).
    Have finished clean up successfully.
    Thanks,
    Subba

  • Error while taking archive log backup

    Dear all,
    We are getting the below mentioned error while taking the archive log backup
    ============================================================================
    BR0208I Volume with name RRPA02 required in device /dev/rmt0.1
    BR0210I Please mount BRARCHIVE volume, if you have not already done so
    BR0280I BRARCHIVE time stamp: 2010-05-27 16.43.41
    BR0256I Enter 'c[ont]' to continue, 's[top]' to cancel BRARCHIVE:
    c
    BR0280I BRARCHIVE time stamp: 2010-05-27 16.43.46
    BR0257I Your reply: 'c'
    BR0259I Program execution will be continued...
    BR0280I BRARCHIVE time stamp: 2010-05-27 16.43.46
    BR0226I Rewinding tape volume in device /dev/rmt0 ...
    BR0351I Restoring /oracle/RRP/sapreorg/.tape.hdr0
    BR0355I from /dev/rmt0.1 ...
    BR0278W Command output of 'LANG=C cd /oracle/RRP/sapreorg && LANG=C cpio -iuvB .tape.hdr0 < /dev/rmt0.1':
    Can't read input
    ===========================================================================
    We are able to take offline, online backups but we are facing the above mentioned problem while taking archive log backup
    We are on ECC 6 / Oracle / AIX
    The kernel is latest
    The drive is working fine and there is no problem with the tapes as we have tried using diffrent tapes
    can this be a permissions issue?
    I ran saproot.sh but somehow it is setting owner as sidadm and group as sapsys to some of the br* files
    I tried by changing the permissions to oraSID : dba but still the error is the same
    Any suggestions?

    Means you have not initialized the medias but trying to take backups.
    First check how many medias you have entered in your tape count parameter for archive log backups (just go to initSID.sap and check)
    Then increase/reduce them to according to your archive backup plan >> Initialize all the tapes according to their name (same as you have initialized in initSID.sap) >> stick physical label to all the medias according to name >> Schedule archive backups
    It will not ask you for initialization as already you have initialized in second step.
    Suggestion: Use 7 medias per week (one tape per day)
    Regards,
    Nick Loy

  • Redo log backup through DB13

    hello,
    if i try to use DB13 for relo log backup it gives error as
    Job started                                                                  
    Step 001 started (program RSDBAJOB, variant &0000000000286, user name BASIS) 
    Execute logical command BRARCHIVE On host dmrctst                            
    Parameters: -u / -c force -p initQAS.sap -cds -v QAS_TUE2_00                 
    BR002I BRARCHIVE 6.10 (76)                                                   
    BR157E Value 'QAS_TUE2_00' for option '-v' longerthan 10 characters          
    BR007I End of offline redo log processing: adxynlbm.log 2008-05-19 18.39.22  
    BR280I Time stamp 2008-05-19 18.39.22                                        
    BR005I BRARCHIVE terminated with errors                                      
    External program terminated with exit code 3                                 
    BRARCHIVE returned error status E                                            
    Job finished                                                                 
    how should i take backup of redo logs,we are using 4.6C version?
    -saurabh

    "BR157E Value 'QAS_TUE2_00' for option '-v' longerthan 10 characters"
    This is the pertinent bit.  Your naming convention for your media does not comply with the limitations ..... i.e, change your tape name to be 10 or less characters.

  • APO Livecache DB Backup and Livecache Auto Log Backup

    Hi Guys,
    Could you please help me here which tranaction code we use to  check APO Livecache DB Backup and Livecache Auto Log Backup
    Thank you

    Hi,
    Livecache DB and log back up looks like can not be accessed from SAP. Database Manager GUI is used.
    Please check the below link for helpful information.
    http://help.sap.com/saphelp_nw04/helpdata/en/f7/499e3c1fbe8c15e10000000a114084/content.htm
    Regards,
    Saravanan V

  • Problem with Whole Database Online+Redo log Backup

    Dear Marcus Sir,
    I am facing while taking "Whole Database Online+Redo log Backup" through DB13 T-Code.
    Below is the "Problem part of the Backup log", however if you need I will send you full log.
    Hope you will find out problem soon
    #FILE..... /oracle/ANP/sapdata2/sr3_8/sr3.data8
    #SAVED.... sr3.data8  ANPB260810/12
    BR0280I BRBACKUP time stamp: 2010-08-27 11.03.22
    BR0063I 9 of 51 files processed - 19400.070 MB of 135986.469 MB done
    BR0204I Percentage done: 14.27%, estimated end time: 11:47
    BR0001I *******___________________________________________
    BR0202I Saving /oracle/ANP/sapdata2/sr3_9/sr3.data9
    BR0203I to /dev/rmt0.1 ...
    BR0278E Command output of 'LANG=C dd obs=1024K bs=1024K if=/oracle/ANP/sapdata2/sr3_9/sr3.data9 of=/dev/rmt0.1':
    dd read error: I/O error
    462+0 records in
    462+0 records out
    BR0280I BRBACKUP time stamp: 2010-08-27 11.03.36
    BR0279E Return code from 'LANG=C dd obs=1024K bs=1024K if=/oracle/ANP/sapdata2/sr3_9/sr3.data9 of=/dev/rmt0.1': 2
    BR0222E Copying /oracle/ANP/sapdata2/sr3_9/sr3.data9 to/from /dev/rmt0.1 failed due to previous errors
    BR0280I BRBACKUP time stamp: 2010-08-27 11.03.41
    BR0317I 'Alter tablespace PSAPSR3 end backup' successful
    BR0056I End of database backup: bedziydp.ant 2010-08-27 11.03.36
    BR0280I BRBACKUP time stamp: 2010-08-27 11.03.41
    BR0054I BRBACKUP terminated with errors
    Warm Regards
    Ahsan

    Hi,
    since you are getting a read error, it might as well be, that your datafile is defective.
    Try the same dd-command to /dev/null, to see if it is possible to read the entire file.
    First make sure that your null-device is existing, otherwise you might face a root-fs full problem.
    dd obs=1024K bs=1024K if=/oracle/ANP/sapdata2/sr3_9/sr3.data9 of=/dev/null
    or try a dbverify on it, which would also read the entire file and do a checksum test.
    brbackup -c -u / -m /oracle/ANP/sapdata2/sr3_9/sr3.data9 -t online -w only_dbv
    Good luck
    Volker

  • Database restore from backup--miss some transaction log backup files.How to restore?

    One database with full recovery model
    it runs full backup at 12:00 am on 1/1 one time.
    Then transaction log backup every 3 hours. 3:00 am, 6:00am,9:00 am, 12:00 Pm, 3:00Pm,6:00PM,9:00pm,12am......
    If we can't find 3:00 am, 6:00am, 9:00am transaction log backup files, could we still restore to 6:00am? We still have all transaction log backup files after 12:00Pm.
    Thanks

    One database with full recovery model
    it runs full backup at 12:00 am on 1/1 one time.
    Then transaction log backup every 3 hours. 3:00 am, 6:00am,9:00 am, 12:00 Pm, 3:00Pm,6:00PM,9:00pm,12am......
    If we can't find 3:00 am, 6:00am, 9:00am transaction log backup files, could we still restore to 6:00am? We still have all transaction log backup files after 12:00Pm.
    Thanks
    NO..log files are incremental and connected.If any log file is missing you cannot restore  to point which comes after backup which is lost or damaged.Like u miss 3 AM trn log backup now even if you have 6,9,12 AM trn log backups its of no use .
    Please mark this reply as the answer or vote as helpful, as appropriate, to make it useful for other readers

  • Full, Differential and log backup or Full and log backup? What to choose?

    Hi All,
    I have a SQL Server 2012 database of size <1 gb and the data of this db is expected to grow by 100 MB every month (i.e., ~ 1 gb per year). We have to backup this database to Azure Blob storage and data loss of 2 hrs. is accepted. Now can you please suggest
    the best database backup policy. The option i have in mind are
    1. Full database backup every week followed by differential backup every 2 hrs (or)
    2. Full database backup every week followed by differential backup every day followed by transactional log backup every 2 hrs (or)
    3. Full database backup every week followed by transactional log backup every 2 hrs
    Note: My database is in Full recovery model

    Well its bit difficult for us to tell what would be best for you as you only told RPO but did not tell us RTO. I mean in how much time, if disaster strikes, would you like database to be up and running. Backup policy would depend on that
    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

  • How to check last log backup happend in sql server

    Hi All,
    How to check last log backup happend in sql server
    Thanks in advance
    Shashikala

    Last Tlog Bakcup details
    SELECT
       CONVERT(CHAR(100), SERVERPROPERTY('Servername')) AS Server,
       msdb.dbo.backupset.database_name,
       MAX(msdb.dbo.backupset.backup_finish_date) AS last_db_backup_date
    FROM   msdb.dbo.backupmediafamily
       INNER JOIN msdb.dbo.backupset ON msdb.dbo.backupmediafamily.media_set_id = msdb.dbo.backupset.media_set_id
    WHERE  msdb..backupset.type = 'L'
    GROUP BY
       msdb.dbo.backupset.database_name
    ORDER BY
       msdb.dbo.backupset.database_name
    --Most Recent Database Backup FULL for Each Database
    SELECT 
       CONVERT(CHAR(100), SERVERPROPERTY('Servername')) AS Server,
       msdb.dbo.backupset.database_name, 
       MAX(msdb.dbo.backupset.backup_finish_date) AS last_db_backup_date
    FROM   msdb.dbo.backupmediafamily 
       INNER JOIN msdb.dbo.backupset ON msdb.dbo.backupmediafamily.media_set_id = msdb.dbo.backupset.media_set_id 
    WHERE  msdb..backupset.type = 'D'
    GROUP BY
       msdb.dbo.backupset.database_name 
    ORDER BY 
       msdb.dbo.backupset.database_name
    http://www.mssqltips.com/sqlservertip/1601/script-to-retrieve-sql-server-database-backup-history-and-no-backups/
    Database -- > Right click -- > Properties -- >
    Raju Rasagounder Sr MSSQL DBA

  • MaxDB 750 LOG Backup failed

    Hello,
    the LOG backup of the database crashes with following error:
    ERR
    -24988,ERR_SQL: sql error
    -8888,connection broken [183]
    KNLDIAG
    2005-12-06 14:18:56      0x370     19633 CONNECT  Connect req. (T4, Node:'', PID:3008)
    2005-12-06 14:18:56      0x370     19651 CONNECT  Connection released, T4
    2005-12-06 14:18:56      0x370     19633 CONNECT  Connect req. (T4, Node:'', PID:3008)
    2005-12-06 14:18:56      0x370     19651 CONNECT  Connection released, T4
    2005-12-06 14:19:57      0x370     19633 CONNECT  Connect req. (T4, Node:'', PID:3008)
    2005-12-06 14:19:59      0x370     19615 VOLUMEIO Attaching volume 'F:\sapdb\EXI\saplog\DISKL001'
    2005-12-06 14:19:59      0x9C8     19613 DBSTATE  I/O thread for 'F:\sapdb\EXI\saplog\DISKL001' started
    2005-12-06 14:19:59      0x370     19617 VOLUMEIO Single I/O attach, 'F:\sapdb\EXI\saplog\DISKL001', UKT:3
    2005-12-06 14:19:59      0xCB4     19625 IO       Async I/O thread started, 'H:\Sicherung_XI\logs\EXI_LOG.017
    2005-12-06 14:19:59      0xEE0     52101 SAVE     Filetype: file
    2005-12-06 14:19:59      0xEE0     52024 SAVE     200 pages -> "erung_XI\logs\EXI_LOG.017"
    2005-12-06 14:20:04      0xEE0     52024 SAVE     10800 pages -> "ung_XI\logs\EXI_LOG.017"
    2005-12-06 14:20:09      0xEE0     52024 SAVE     20000 pages -> "ung_XI\logs\EXI_LOG.017"
    2005-12-06 14:20:14      0xEE0     52024 SAVE     29400 pages -> "ung_XI\logs\EXI_LOG.017"
    2005-12-06 14:20:19      0xEE0     52024 SAVE     39000 pages -> "ung_XI\logs\EXI_LOG.017"
    2005-12-06 14:20:24      0xEE0     52024 SAVE     48200 pages -> "ung_XI\logs\EXI_LOG.017"
    2005-12-06 14:20:29      0xEE0     52024 SAVE     57600 pages -> "ung_XI\logs\EXI_LOG.017"
    2005-12-06 14:20:34      0xEE0     52024 SAVE     66800 pages -> "ung_XI\logs\EXI_LOG.017"
    2005-12-06 14:20:39      0xEE0     52024 SAVE     76400 pages -> "ung_XI\logs\EXI_LOG.017"
    2005-12-06 14:20:44      0xEE0     52024 SAVE     85400 pages -> "ung_XI\logs\EXI_LOG.017"
    2005-12-06 14:20:49      0xEE0     52024 SAVE     94800 pages -> "ung_XI\logs\EXI_LOG.017"
    2005-12-06 14:20:54      0xEE0     52024 SAVE     104000 pages -> "ng_XI\logs\EXI_LOG.017"
    2005-12-06 14:20:59      0xEE0     52024 SAVE     113200 pages -> "ng_XI\logs\EXI_LOG.017"
    2005-12-06 14:21:04      0xEE0     52024 SAVE     122600 pages -> "ng_XI\logs\EXI_LOG.017"
    2005-12-06 14:21:09      0xEE0 ERR     0 SAPDBErr Assertion of state Log_SaveIterator::CheckPageBuffer pagebuffer contains no endOfLogDevice failed!
    2005-12-06 14:21:09      0xEE0 ERR 18196 DBCRASH  vabort:Emergency Shutdown, Log_SaveIterator.cpp: 222
    current write position -
    KNLDIAG.ERR
    2005-12-06 14:18:41                               --- Starting GMT 2005-12-06 13:18:41           7.5.0    Build 031-123-104-253
    2005-12-06 14:21:09      0xEE0 ERR     0 SAPDBErr Assertion of state Log_SaveIterator::CheckPageBuffer pagebuffer contains no endOfLogDevice failed!
    2005-12-06 14:21:09      0xEE0 ERR 18196 DBCRASH  vabort:Emergency Shutdown, Log_SaveIterator.cpp: 222
    in online mode the database works fine, also a full backup...
    Regards,
    Domi

    Hi,
    the reason for the problem might be a partially written logpage on a logvolume, or a non-written, but expected logpage. If this page is not found, the logbackup throws the error you received. This should be a very rare error.
    In order to solve this, you could try the following:
    1. Then bring the database instance to mode <b>online</b>
    2. Then bring the database instance to mode <b>admin</b>
    3. Clear the log:
    dbmcli -d <SID> -u <controluser>,<controlpasswd> -uUTL <controluser>,<controlpasswd> util_execute clear log
    4. Perform full data backup
    5. Perform log backup
    Regards,
    Roland
    P.S.: the clear log command is a 'dangerous' command, please don't use it otherwise.

Maybe you are looking for

  • Checking status of Remote Management (VNC).

    Hi there We use puppet in our business to manage our Macs as well as other machines. I'm currently looking at sending a command to force enable VNC on our OS X machines: /System/Library/CoreServices/RemoteManagement/ARDAgent.app/Contents/Resources/ki

  • Sender SOAP Adapter problem in PI 7.1

    Hello Everyone, I have a problem with Sender SOAP  Adapter In PI 7.0 i am able to receive the messages through sender SOAP Adapter for both HTTP and HTTPS. But when i am testing in PI 7.1 i am unable to receive any messages at Adapter level for both

  • Displaying Client standard header in ALV output

    Hi everybody, I am displaying the ALV report. On the top-of-page Client standard header has to display. Can any one suggest me how to achive this. Thanks in advance. Karunakar

  • Search Server Database problem

    Hi, I have a problem with a creation of a new search server database. (I use search1 default search server ) The command that I used is: psadmin create-search-db -s search1 -u amadmin -d defaultand the log response is: [#|2008-08-29T01:02:24.518+0200

  • My take on the yellow tinge

    Got my 27" i5 a week ago. Didn't notice the yellow tinge initially. I did pick up the 'louder than I'm used to on a Mac' hard drive noise. Nothing that really bugged me that much but I did want to know if it was normal (in the end, my quad-core iMac