---
description: DMK_DBBACKUP-release_notes
---

# Release notes

```
#########################
# Release Notes         #
#########################

[Next 2.0.0]
Issue #97 : Remove .DMK_PERL reference from all dbbackup bin file
Issue #96 : Since new dmk design dbbackup not working any more with DEBUG=1
Issue #95 : BETA-23-02 test : dbmk_dbbackup is not working any more
Issue #92 : RMAN Report - Possibility to choose the HTML report to be sent into the E-Mails body or into attachment
Issue #85 : replace email address dbi_dmk_support@dbi-services.com to dmk.support@dbi-services.com into the documentation file
Issue #86 : dmk_dtpump create only one dump file for parallel use on windows system
Issue #87 : dbbackup release 22-01 - Wrong version name displayed
Issue #88 : Removed use of log variables in windows registry

[Beta dmk_dbbackup-22-04]
Issue #88 : Appended microsecs to all DMK_LOGFILES names

[dmk_dbbackup-22-01]
Issue #80 : Documentation for Microsoft Windows in DMK_DBACKUP_manual.pdf is wrong and incomplete.
Issue #82 : Email to be sent in case backup path is not existing
Issue #73 : Enable/Disable block change tracking cause ORA-19752 in alertlog
Issue #74 : INC1 rcv script missing
Issue #75 : Documentation: implementation best practise
Issue #78 : BETA Test dmk-dbbackup-BETA-21-07-unix --- PART A
Issue #79 : dmk_backup_report.ksh shows catalog-password as INFO
Issue #81 : Snapshot controlfile fills up 100% the backup share
Issue #67 : Create new rcv template : bck_incr_upd.rcv
Issue #68 : Using target with "AS SYSBACKUP" in rman.cfg
Issue #69 : dmk_dbbackup docu
Issue #70 : dmk_dtpump: no parameter for dumpfile
Issue #71 : templates for dmk_dpdump to add
Issue #72 : Only one dump file name is generated when doing some parallel export
Issue #76 : Change default use catalog option to be always instead of resync_only
Issue #77 : dmk backup --usecatalog always should raise an error when no catalog is defined

[dmk_dbbackup-21-02]
This version includes a new functionality for generating backup report : dmk_backup_report.ksh. Please check attached user guide for more information.
Issue #2 : Extend dmk_dtpump.ksh for the PDBs
Issue #30 : Exclude a SCHEMA from the expdp with dmk_dtpump.ksh
Issue #32 : Generic backup email report for several databases
Issue #33 : add Block Change Tracking enable/disable
Issue #41 : use catalog option error handling (-u resyncshouldnotwork is not failing in error)
Issue #42 : dbbackup release 19-04 not working with Oracle 11.2.0.4
Issue #43 : dmk_dbbackup compatibility with 19c
Issue #44 : dmk_dtpump.ksh is executed 2 times consecutively
Issue #45 : Fix dmk_dtpump.ksh documentation, and more documentation should be provided to export/import a single schema, also with remap_schema
Issue #46 : schema export generate 2 exportfiles
Issue #47 : Dmk_dbbackup fails with post_script_retCode::255, but does neither show the PostScript filename nor send the logfile of the error.
Issue #49 : dmk_dtpump.ksh not taking in account -t option when exporting
Issue #51 : Running dmk_rman.ksh between Oracle from different version is generating perl errors
Issue #52 : Change the rman catalog default in rman.cfg and write a warning message in the mails
Issue #53 : Tar file corruption in email
Issue #54 : Rename file sent by email for tar file
Issue #55 : Update documentation after test/review BETA 20-03
Issue #56 : Backup_dir not taken in account when using tape simulation
Issue #57 : the script dmk_rman.ksh at customer site does not set the PERL environment correct
Issue #58 : dtpump_export.cfg - DumpFile parameter not working when a custome ParFile is used
Issue #59 : dmk_dtpump : parfile not removed after execution on windows
Issue #60 : dmk_dtpump : Minor : Function removing password for log file will remove as well the tns connection in the userid information stored in log file
Issue #61 : Datapump config - parameter DumpFile behaves not like documented
```
