Tag Archives: Backup/Restore

Sample 11.5.9 to 12.1.1 Upgrade Steps

Posted by on January 7, 2010 No comments

1. Preparing for the Upgrade

Apply 11i.AD.I
Back up database, Applications, and customizations
Prepare an upgrade plan for customizations
Convert to Multiple Organizations architecture
Review sizes of old and new tablespaces
Review Upgrade Tasks and Apply 11i.AD.I

Convert Oracle Alert E-mail Processing to the Workflow Notification Mailer
Financials and Procurement Tasks
Gather schema statistics for CBO
Back up the database
Run Rapid Install
Migrate or upgrade your database to Oracle 10g Release 2
Port application to Linux servers

2. Upgrading to Release 12

Disable AOL Audit Trail
Migrate database to Oracle10g Release 2
Back up the database
Apply Release 12 AD minipack
Run the American English upgrade patch driver
Run the NLS upgrade patch driver
Apply latest product patches
Synchronize NLS and American English product patches
Back up Oracle Applications

Finish the Upgrade
Configure Applications client software for forms applet (required)
Reapply customizations (conditional)
Integrate custom objects and schemas (conditional)

Finish System Administration Tasks
Complete Workflow Notification Mailer configuration (required)
Complete setup for Oracle XML Gateway (required)
Enable PDF printing (required)

3. Post-upgrade Tasks
Install online help
Update/verify custom responsibilities
Migrate custom development to new technologies
Migrate the CUSTOM library
Copy and re-customize modified scripts or reports
Review user responsibility assignments
Associate organization names with custom Alert definitions
Set operating unit mode for customizations
Assign the Report Manager Data Migration Program to a request group
Run the Data Migration Program

Update Status Monitor URLs
Synchronize Product License and Workflow BES license status
Financials and Procurement Tasks
Additional Tasks

Tape Commands for Linux

Posted by on December 15, 2009 No comments

To back up /etc folder:

tar -cvf /dev/st0 /etc

To list contents of tape:

tar -tf /dev/st0

To restore data from tape:

tar -xvf /dev/st0

Script To Export 11i Database

Posted by on December 15, 2009 No comments 
# expprod.sh
#
# Exports the Oracle E-Business Suite HRMS Production database
# which will then be copied over to the backup server
#
# source the environment
. /u0/oracle/proddb/9.2.0/PROD_ebusiness.env
# stop, then restart the production instance
# to overcome 'snapshot too old' error
# (commented out, as users on the system at 6:00 P.M. will be kicked off)
# cd /u0/oracle/proddb/9.2.0/appsutil/scripts/PROD_ebusiness/
# ./addbctl.sh stop immediate
# ./addbctl.sh start
# get name of log file and dump file
export LOGFILE=expprod_`date +%F_%k-%M-%S`.log
export DUMPFILE=expprod.dmp
export BACKUPDIR=/mnt/prodbkup
export EXPORTDIR=/u0/prodbkup
export ZIPFILE=expprod.tar.gz
export ZIPFILE2=expprod_`date +%F_%k-%M-%S`.tar.gz
# remove existing dump file
rm $EXPORTDIR/$DUMPFILE
rm $EXPORTDIR/$ZIPFILE
# export the ONT schema (for testing purposes)
# exp system/manager file=$EXPORTDIR/$DUMPFILE log=$EXPORTDIR/$LOGFILE owner=ONT
# export the database
exp system/manager file=$EXPORTDIR/$DUMPFILE log=$EXPORTDIR/$LOGFILE full=y consistent=y
# tar and gzip export file
tar -czvf $EXPORTDIR/$ZIPFILE $EXPORTDIR/$DUMPFILE
# remove the previous export dump from the test server, then copy the new one
# rm $BACKUPDIR/$DUMPFILE
# rm $BACKUPDIR/$ZIPFILE (Commented out by VS 10-Sep-09)
# copy the zip file and log file to the backup directory (remote NFS directory on ebusinesstest)
cp $EXPORTDIR/$ZIPFILE $BACKUPDIR/
cp $EXPORTDIR/$LOGFILE $BACKUPDIR/
# rename the zip file in the remote directory to reflect today's date
mv $BACKUPDIR/$ZIPFILE $BACKUPDIR/$ZIPFILE2
# rename the zip file in the local directory to reflect today's date (as an archive copy)
mv $EXPORTDIR/$ZIPFILE $EXPORTDIR/$ZIPFILE2

Cloning PeopleSoft Instance

Posted by on February 3, 2009 Comments Off on Cloning PeopleSoft Instance

Here are the steps to clone the PeopleSoft instance:

1. Backup the database (FSDEV) and restore it to another name (FSTST)
2. Clear the GUID field in the PSOPTIONS table in FSTST
3. Set up ODBC connection for FSTST
4. Map PS_HOME network drive and run Configuration Manager to set up shortcuts, PS/nVision path names
5. Create new application server domain for FSTST
6. Create new batch server for FSTST
7. Stop web server and setup new PIA for FSTST
8. Start application server, batch server, web server and log on to FSTST.

[amazon asin=0071664939&template=iframe image&chan=default]     [amazon asin=1430237074&template=iframe image&chan=default]     [amazon asin=0071787925&template=iframe image&chan=default]

Cloning of Production Instance

Posted by on November 4, 2008 No comments

#

Step

Estimated duration
1. Prepare the test machine (echo) that shall be used as the new production machine for cloning:Remove any existing E-Business Suite instance on the machine. Ideally, reinstall the operating system, apply any required service packs, install the additional software such as JDK, Visual C++, MKS Toolkit etc. The software should be installed to the same directory paths as those on the production instance.If the test machine will not reinstalled, then remove the Oracle-related keys from the registry.

1 day
2. Carry out the pre-clone steps for the production instance (adpreclone.pl).

½ day
3. Shutdown the production E-Business Suite instance (application and database tier services) and copy the files from the production machine (delta) to the test machine (echo).

1 day
4. Disconnect the production server from the network. Change the name and IP address of the test machine (echo) to that of the production machine (delta). Update the ‘hosts’ file on the new production server, so that it now contains the new IP address and hostname.

1 hour
5. Clone the new production server. Run the clone scripts on the new production server (adcfgclone.pl).

½ day
6. Perform stress-testing of the new server to ensure that it responds suitably to the load.

1 day
7. Backup and test recovery of the instance on another server.

1 day

Please note:

1. Ensure that the Database processes are properly shut down before proceeding to copy the files; if files aren’t copied correctly, the cloning process would not be executed correctly.

2. Do not run the Gather Schema Statistics concurrent job on the new PROD instance.

oraInst.loc points to an Inventory that does not exist (Cloning)

Posted by on September 17, 2008 No comments

Problem:

/etc/oraInst.loc points to an Inventory that does not exist:

mkdir : No such file or directory at ./adclone.pl line 1274

ERROR: Failed to execute ./adclone.pl

Solution:

As root user, ran /tmp/orainstRoot.sh.

Reran clone again, but it failed.

The root directory had completely filled up because the backup was restored to /oracle and not /u0/oracle. Removed /oracle, then reran /tmp/orainstRoot.sh and tried script again.

Backup Strategy Notes

Posted by on August 14, 2006 No comments

This documentation covers a general backup strategy for the client.

Since a lot of work is being done on the Test instance, it is important that the server housing this instance be backed up on a regular basis.

Backup Media

There are several types of backup media available. For example, CD-ROMs, DVD-ROMs, secondary hard drives etc. CD-ROMs and DVD-ROMs do not possess the required capacity. Secondary hard drives are likely to fail. For example, if a power spike caused the server hard drives to fail, it may also cause the secondary hard drives to fail.

The best medium for backing up servers is tape media. The tape must be capable of backing up the database and related Oracle Application files, as well as the public folder. Storage requirements for these will grow as the project progresses, and this must be taken into consideration. A rough estimate of the tape capacity is about 200GB. This will easily back up the entire server.

Dell sells LTO tape drives (PowerVault 110T LTO Tape Drive) with some of their servers; perhaps this can be used as a starting point for research on tape drives.

Backup Software

There are several commercial backup and recovery solutions available, such as BrightStor ARCserve. ARCserve handles all aspects of job creation, scheduling and recovery from an intuitive GUI. In addition, ARCserve is certified by Microsoft on all of its server platforms.

Windows also comes with it’s own backup software, NT Backup. NT Backup provides much of the basic functionality as ARCserve. However, NT Backup is designed to be a more interactive solution, that is, an operator has to manually choose the files and directories to back up, and then start the backup.

Ideally, the backup should be automated so that an operator does not have to manually start the backup, and the backup can be scheduled in the middle of the night (say 10 o’clock).

NT Backup can be called from the command line with parameters, so the NT Backup command can be placed into a Windows Command Script (with a .cmd extension), which can then be scheduled. However, this method must be diligently tested to ensure that the scheduled backups are going through.

To view the syntax for NTBackup command line parameters, type ‘ntbackup /?’ at the command prompt:

C:> ntbackup /?

NT Backup loads, then the help file appears with the command-line reference.

To use NT Backup, a ‘selection’ of directories to back up has to be created and saved so that it can be referenced on the command line.

Directories to Backup

At the very least, the directories that should be backed up on oracleserver are

  • D:PROD
  • D:PROJECT FOLDER

However, if all directories on all of the drives can be backed up, it would be even better.

Regardless of the backup software used, the backup made should be tested on a regular basis. There should be a separate machine, which can be used to test different disaster recovery scenarios.

Quick And Dirty Backup and Recovery Test Procedure

Posted by on April 21, 2005 No comments

Step 1.      Shutdown the TEST instance:

./oratest/scripts/stopTEST.sh

Step 2.      Backup the directory /oratest/oracle and all it subdirectories.

Step 3.      Rename the directory /oratest/oracle to /oratest/oracle_backup

Step 4.      Restore from backup /oratest/oracle

Step 5.      Verify Recovery by Comparing file sizes between oracle and oracle_backup

Step 6.      Start the TEST instance:

./oratest/scripts/startTEST.sh

Step 7.      Log on to TEST instance and TEST functionality.

Step 8.      Remove directory /oratest/oracle_backup