If you are running the Oracle instance in a production environment there are some additional steps to take notice of.
These steps are mandatory for a production environment.
Note: Run as SYS! Start SQL*Plus and log on as user SYS.
If your installation of IFS Applications is a production environment you must make sure that archiving of Redo Logs is activated. Otherwise Oracle cannot recover to the last completed transaction if a crash occurs.
Checklist for putting the database in Archive log mode:
SHUTDOWN IMMEDIATE
# if using Oracle Flash Recovery Area
DB_RECOVERY_FILE_DEST=<your_Flash_Recovery_Area>
DB_RECOVERY_FILE_DEST_SIZE = <you_Flash_Recovery_Area_Size>
LOG_ARCHIVE_START = TRUE
# if NOT using Oracle Flash Recovery Area
LOG_ARCHIVE_DEST = <your_log_archive_dest>
LOG_ARCHIVE_START = TRUE
ALTER DATABASE ARCHIVELOG;
ALTER DATABASE OPEN;
SHUTDOWN IMMEDIATE;
STARTUP;
ARCHIVE LOG LIST
Note: Remember to set the Database in NOARCHIVELOG mode during installation and upgrade. Otherwise thee installation/upgrade will generate lots of redo log information and performance will decrease. After installation/upgrade has finished set the database in ARCHIVELOG mode. Always take a backup of the database before installing/upgrading the database.
Make sure to create a functional backup strategy for your production environment.
This is what you at least need to backup from a database perspective:
There are different types of backups and you need to choose the right solution for your needs. The optimal backup solution would include a combination of offline, online and exports.
Offline backup requires you to shut down the database and the take a file copy backup of all files described above. You also need to find a time window large enough to complete the backup.
Online backups allow you to backup database files on a running database without shutting down the database. Online backup requires that the database be run in Archive log mode.
ALTER TABLESPACE <tablespace name> BEGIN BACKUP;
Backup the data filesALTER TABLESPACE <tablespace name> END BACKUP;
ALTER SYSTEM SWITCH LOGFILE;
ALTER SYSTEM SWITCH LOGFILE;
ALTER DATABASE BACKUP CONTROLFILE TO TRACE AS
'c:\backup\control.txt';
ALTER DATABASE BACKUP
CONTROLFILE TO 'c:\backup\control.ctl';
The above file backups are convenient to complement a data backup. Export allows you to extract data to a binary file that can be used to restore a table removed by mistake.
Last but not least make sure that your backup strategy works. Simulate a disk crash and verify your backup by making a complete restore of your database.