In this case, you should consider starting the workload capture at an earlier time, so that the database can be restarted at a time that is less disruptive. However, to avoid service interruption during normal business hours, you may not want to restart the database during this time. For example, you may want to capture a workload that begins at 8:00 a.m. On a busy system, it is normal to see some replay divergence, but the replay can still be used to perform meaningful analysis of a system change if the diverged calls do not make up a significant portion of the replay in terms of DB time and other such key attributes.Д«efore restarting the database, determine an appropriate time to shut down the production database before the workload capture when it is the least disruptive. Any subsequent transactions with dependencies on the incomplete transactions may also generate errors during replay. This may result in undesired replay divergence when the workload is replayed. Ongoing transactions will thus not be replayed properly, because only the part of the transaction whose calls were captured will be replayed. If the database is not restarted before the capture begins, transactions that are in progress or have yet to be committed will not be fully captured in the workload. init.d/oracle /etc/rc.d/rc6.While this step is not required, Oracle recommends that the database be restarted before capturing the workload to ensure that ongoing and dependent transactions are allowed to be completed or rolled back before the capture begins. init.d/oracle /etc/rc.d/rc0.d/K01oracle # Halting To stop the databases on reboot or restart we need the following links: The following commands will ensure that the databases will come up in runlevels 2,3 and 4:

Once this script is working we need to create start and kill symbolic links in the appropriate runlevel directories /etc/rc.d/rcX.d. Check the log file, /var/log/oracle for error messages. It is worth checking that this file actually correctly stops and starts the databases for your system. Su - oracle -c 'lsnrctl stop' > /var/log/oracleД®cho -n 'Shutting Down Oracle Databases: 'Дate +'! %T %a %D : Restarting Oracle Databases as part of system up.' > /var/log/oracleД®cho 'Usage: oracle ' Su - oracle -c 'lsnrctl start' > /var/log/oracleДate +'! %T %a %D : Finished.' > /var/log/oracleД®cho -n 'Shutting Down Oracle Listeners: 'Дate +'! %T %a %D : Shutting Down Oracle Databases as part of system down.' > /var/log/oracle # Description: Starts and stops the Oracle database and listenersД®cho '-' > /var/log/oracleДate +'! %T %a %D : Starting Oracle Databases as part of system up.' > /var/log/oracle

Create the following file as /etc/rc.d/init.d/oracle: (Although it should hold true for any Sys V type UNIX).ДЇirstly, we need to create the script which will run dbshut and dbstart in the /etc/rc.d/init.d directory. To modify these for your own flavour of Linux, please see your Linux documentation sets. I will show examples which work for Redhat Linux 5.0. This is quite easy, although I should point out here that this may change depending on which flavour of Linux (slackware, debian, redhat, etc). To start and stop the database when the machine comes up and goes down by modifying the startup routines for the Linux machine. The format of the /etc/oratab file is as follows: These files rely on the existance of the file /etc/oratab to work (although by altering the dbshut and dbstart files this can be moved). The automatic startup and shutdown of the Oracle database can be achieved (in 7.3.3.0.0) with the files dbstart and dbshut both provided by Oracle. Automatic Startup and Shutdown 6.1 dbstart & dbstop Oracle Database HOWTO: Automatic Startup and Shutdown Next Previous ContentsД¦.

Restart oracle database