Skip to main content

HOW TO START AND STOP ORACLE APPS r12

Hi, It is very easy to start or stop the oracle apps r12, but as a fresher you face many issues with starting and stopping the oracle apps. So in this I will tell you the simple steps to start the oracle apps.
What we must remember some rules first about starting and stopping the oracle apps.

SOME RULES:--

To start oracle apps
          when you start the oracle apps you must remember that start your database tier first and then start your listener and after that start your apps tier.
To Stop oracle apps
          When you want to stop oracle apps you have reverse  the starting process . First shutdown your app tier and then shutdown the listener and then at last shutdown the  database.


You must keep these steps in mind that you must follow the rules.


How to start the oracle apps:-

I will tell you the step that I use  to perform to start the oracle apps on LINUX.


Step 1:- Login to putty or any other software that you used to connect to your server.
Step 2:- Login with user that own the permission of that directory where you have installed oracle db.
Step 3:- Now you have to run the .env file located in ORACLE_HOME.
Step 4:- Now, on terminal run this command  Sqlplus '/as sysdba'
Step 5:- Now you will  have sql prompt like this sql> , type startup command to start the database
Step 6:- Now start the listener by typing " lsnrctl start " , this will start our listener.
Step 7:- We have our database up and running. now it's time to start application.
Step 8:- Now open a new terminal with user that own the permission of that directory where you have installed apps.
Step 9:- Now run the .env file from $HOME/apps/apps_st/appl .
Step 10 :- Now, change directory using cd  $ADMIN_SCRIPT_HOME
Step 11 :- Now you will see many .sh file in this directory. run following command on the terminal
                               sh adstartall.sh apps/password
Step 12:- Check  your app on http://hostname:8000/em




How to stop the oracle apps:-

As I have told you that we need to reverse the process of startup to shutdown the oracle apps.Means we have shutdown our application services first and then your database .


Step 1:- Now open a new terminal with user that own the permission of that directory where you have installed apps.
Step 2:- Now run the .env file from $HOME/apps/apps_st/appl .
Step 3 :- Now, change directory using cd  $ADMIN_SCRIPT_HOME
Step 4 :- Now you will see many .sh file in this directory. run following command on the terminal
                               sh adstpall.sh apps/password
Step 5:- Now we have to stop our listener of database.
Step 6:- Login with user that own the permission of that directory where you have installed oracle db.
Step 7:- Now you have to run the .env file located in ORACLE_HOME.
Step 8:- Now stop the listener by typing " lsnrctl stop " , this will stop our listener.
Step 9:- Now, on the same terminal run this command  Sqlplus '/as sysdba'
Step 10:- Now you will  have sql prompt like this sql> , type shutdown  immediate command to stop the database
Step 11 :- Now you have everything down.

Please let me know if you have any quires regarding this :)






Comments

Post a Comment

Popular posts from this blog

DBA_SCHEDULER_JOB_RUN_DETAILS and PURGE_LOG

How to purge DBA_SCHEDULER_JOB_RUN_DETAILS? Manually deleting from DBA_SCHEDULER_JOB_RUN_DETAILS is not recommended by oracle.DBA_SCHEDULER_JOB_RUN_DETAILS is a view that is using two master tables (scheduler$_job_run_details and scheduler$_event_log) and display the information about jobs history. As there is one procedure named PURGE_LOG and Oracle have Scheduler for this procedure. It will purges all rows in the job log that are older than 30 days.This is the default behavior of this procedure. You can change this to any number of days you want by setting the attribute "SET_SCHEDULER_ATTRIBUTE". e.g. exec DBMS_SCHEDULER.SET_SCHEDULER_ATTRIBUTE('log_history','15'); It will purge all logs older than 15days and it will maintain the history of 15days. But If you want manually purge these logs, you can use below solution:- exec DBMS_SCHEDULER.PURGE_LOG(log_history => 15, which_log => 'JOB_LOG'); It will purge all entries from the jog log that are o...
Post a Comment
Read more

ORA-65016: FILE_NAME_CONVERT must be specified

ORA-65016: FILE_NAME_CONVERT must be specified I just started working on 12C version of oracle database.It's new to me and facing many problems. Error code: ORA-65016: FILE_NAME_CONVERT must be specified Description:"ORA-65016: FILE_NAME_CONVERT must be specified" normally occurs when you create a PDB.I will explain later what is a PDB. Cause and solution :  ORA-65016: FILE_NAME_CONVERT must be specified caused when Data files, and possibly other files, needed to be copied as a part of creating a pluggable database.Enable OMF or define PDB_FILE_NAME_CONVERT system parameter before issuing CREATE PLUGGABLE DATABASE statement, or specify FILE_NAME_CONVERT clause as a part of the statement and make sure the path you are giving to convert the file exists. I think if you are creating the PDB's using GUI then you will not face this error "ORA-65016: FILE_NAME_CONVERT must be specified". If you creating ODB using script and you have gave a wrong path then may you f...
2 comments
Read more

ORA-02051 Another Session Or Branch In Same Transaction Failed

ORA-02051 Another Session Or Branch In Same Transaction Failed (Doc ID 2253226.1)          SYMPTOMS for ORA-02051 Another Session Or Branch In Same Transaction Failed. Database performance is slow and caused   the transactions ORA-02051 another session or branch in same transaction failed or finalized CAUSE for ORA-02051 Another Session Or Branch In Same Transaction Failed. Session transactions branches caused the issue Excessive Waits On The Event "Global transaction acquire instance locks" SOLUTION Please use below sql and identified underscore parameter values for ORA-02051 Another Session Or Branch In Same Transaction Failed : SQL> select a.ksppinm "Parameter", b.ksppstvl "Session Value",c.ksppstvl "Instance Value"  FROM x$ksppi a,x$ksppcv b, x$ksppsv c  WHERE a.indx = b.indx AND a.indx = c.indx AND a.ksppinm LIKE '/_%' escape '/'  AND (a.ksppinm like '%clusterwide_global%' or a.ksppinm like '%disable_autotune_...
Post a Comment
Read more