Safeguard Release: 5.0.2
November 30, 2010 Filed in: Safeguard
Safeguard 5.0.2 has been released, featuring a number of new changes:
- for schema export, should limit table exclusion list to tables in included schemas
- need visual indicator of report agent
- need indicator to provide catalog username and service name
- mail server settings test should be from the report server agent
- need log message for reporting job
- deletion of schedule job not refreshing jobs list on agent
- calendar based deletion of scheduled backup jobs using incorrect data context
- buttons to edit and delete agent and database items should be disabled if selected node is of wrong type
- database registration wizard, changing properties of existing database does not update database context in main form tree properly
- agent registration wizard, changing properties of existing agent does not update agent context in main form tree properly
- getting started wizard, specifying invalid username/password for existing oracle user shows exception handler then allows to proceed
- selecting a dump file, double click on file not returning selected file
- add job status notifications to windows event log
- add log feedback for user killed job
- edit a regularly scheduled job, radio buttons on schedule control do not accurately reflect scheduled job
- add ability to retrieve event log entries from remote server
- ping database should respond with current database state
- write of parameter files and/or control files should rename, not delete the current files
- incorrect catalog credentials not recovering properly
- list oracle homes in database registration and recovery wizards
- list instance names in database registration and recovery wizards
- relocate files in recovery wizard should have button to select all
- writing a new parameter file should stop instance
- parameter file editor not committing current change before writing parameter file
- crosscheck during duplication to same host fails
- crosschecking currently applying to source target, needs to apply to destination target (recovery to a different server crosschecks the original)
- choose control file path in parameters editor disabled
- list of server names in recovery agent should be ordered alphabetically
- recovery should not allow renaming of database
- duplication should take max scn of v$backup_redolog, not current scn of database (recovery should use database scn)
