Restoring Emergency Database Logs
It is used to restore the damaged log file when the database has been aborted due to damage to the log file caused by a system conflict and cannot be restarted. To modify the damaged database log, execute the utility without options; to create a new log file, execute the utility with the -r option.
cubrid emergency_patchlog options database_name
options : [ -r | --recreate-log ]
- cubrid : An integrated utility for the CUBRID service and database management.
- emergency_patchlog : It is used to restore the log file. It normally executes only when the database is in a stopped state. At first, you must execute the utility without the -r option to restore corrupted database.
- options : You should use the -r option only when necessary logs do not exist or you cannot restore the corrupted logs. The size of the newly created log file is the size of the generic log volume.
- database_name : The name of the database to be restored.
Restoring with the existing log (1st execution)
cubrid emergency_patchlog testdb
Discarding the existing log and creating a new empty log (-r) (2nd execution)
cubrid emergency_patchlog -r testdb