Oracle Applications1204 Mainteance Documentv2 by MBbHOp1

VIEWS: 5 PAGES: 12

									www.FullInterview.com




                    NZCL ORACLE APPLICATIONS
                    MAINTENANCE DOCUMENT




www.FullInterview.com
                                               Page 1 of 12
www.FullInterview.com




                    Contents


                    PROD Instance Startup and Shutdown Procedure ............................................................ 3
                         Production Instance Startup Procedure ........................................................................ 3
                         Production Instance Shutdown Procedure .................................................................. 3
                    PROD Instance Maintenance Procedures ............................................................................ 4
                         After Server Restart ......................................................................................................... 4
                    PROD Instance Monitoring Checklist .................................................................................. 5
                         Disk Space Monitoring .................................................................................................... 5
                         Tablespace Monitoring ................................................................................................... 5
                    Changing Super User’s Password ........................................................................................ 8

                    Concurrent Program Registration in Oracle Applications .............................................. 10




www.FullInterview.com
                                                                                                                                      Page 2 of 12
www.FullInterview.com

PROD Instance Startup and Shutdown Procedure


Production Instance Startup Procedure

                      While starting the instance start the database first then start the application.

                      Login as ‘oraprod’ user into the server snzclakl026.nzc.co.nz (10.200.2.45),
                          $ cd /u01/oraprod/appsutil/scripts/PROD_snzclakl026
                          $ sh addbctl.sh start
                          $ sh addlnctl.sh start PROD


                      Login as ‘applprod’ user into the server snzclakl026.nzc.co.nz (10.200.2.45),
                          $ cd /u01/appldev/inst/apps/PROD_snzclakl026/admin/scripts/
                          $ sh adstrtal.sh apps/<apps password>


                      Login as ‘oradisc’ user into the server snzclakl026.nzc.co.nz (10.200.2.45),
                          $ cd /u01/oradisc/OraHome_1/opmn/bin
                          $ opmnctl startall



Production Instance Shutdown Procedure

                      While shutting down the instance you have to make sure that application is
                      completely down including concurrent managers before shutting down the database.

                      Login as ‘applprod’ user into the server snzclakl026.nzc.co.nz (10.200.2.45),
                          $ cd /u01/applprod/inst/apps/PROD_snzclakl026/admin/scripts
                          $sh adstpall.sh apps/<apps password>
                          Make sure that Application is completely down.
                                  $ ps –ef | grep –i applprod


                      Login as ‘oraprod’ user into the server snzclakl026.nzc.co.nz (10.200.2.45),
                          $ cd $ORACLE_HOME/appsutil/scripts/PROD_snzclakl026
                          $sh addlnctl.sh stop PROD
                          $sh addbctl.sh stop immediate


                      Login as ‘oradisc’ user into the server snzclakl026.nzc.co.nz (10.200.2.45),
                          $ cd /u01/oradisc/OraHome_1/opmn/bin
                          $ opmnctl stopall




www.FullInterview.com
                                                                                                    Page 3 of 12
www.FullInterview.com

PROD Instance Maintenance Procedures



After Server Restart

                       Whenever restrting the server, After restrart, enable Display server connectivity. If
                       the Display server is not enabled to connect then the .pdf type reports will fail. For
                       that run xhost command from the server console.

                            Login as ‘root’ user in the server Graphics console.
                            Run the command $ xhost +




www.FullInterview.com
                                                                                                  Page 4 of 12
www.FullInterview.com

PROD Instance Monitoring Checklist
            Weekly once in Monday we have to run a monitoring on the database and server.



Disk Space Monitoring
                        Login into snzclakl026 server and check all mount points are having enough space.
                        Especially /u01

                            $ df –h




Tablespace Monitoring
                        Check any tablespaces filled more than 90%. If then increase the tablespace size. No
                        datafile size should not exceed more than 2GB.

                        SQL Command to check Free space:-

                        $ sqlplus system/<password>

                        SELECT d.status "Status", d.tablespace_name "Name", d.contents "Type",
                        d.extent_management "Extent Management", TO_CHAR(NVL(a.bytes / 1024 / 1024,
                        0),'99G999G990D900') "Size (M)", TO_CHAR(NVL(NVL(f.bytes, 0), 0)/1024/1024
                        ,'99G999G990D900') "Free (MB)", TO_CHAR(NVL((NVL(f.bytes, 0)) / a.bytes * 100,
                        0), '990D00') "Free %" FROM sys.dba_tablespaces d, (select tablespace_name,
                        sum(bytes) bytes from dba_data_files group by tablespace_name) a, (select
                        tablespace_name, sum(bytes) bytes from dba_free_space group by tablespace_name)
                        f WHERE d.tablespace_name = a.tablespace_name(+) AND d.tablespace_name =
                        f.tablespace_name(+) AND NOT (d.extent_management like 'LOCAL' AND
                        d.contents like 'TEMPORARY')
                        UNION ALL
                        SELECT d.status "Status", d.tablespace_name "Name", d.contents "Type",
                        d.extent_management "Extent Management", TO_CHAR(NVL(a.bytes / 1024 / 1024,
                        0),'99G999G990D900') "Size (M)", TO_CHAR(NVL((a.bytes-t.bytes),
                        a.bytes)/1024/1024,'99G999G990D900') "Free (MB)", TO_CHAR(NVL((a.bytes-
                        t.bytes) / a.bytes * 100, 100), '990D00') "Free %" FROM sys.dba_tablespaces d, (select
                        tablespace_name, sum(bytes) bytes from dba_temp_files group by tablespace_name)
                        a, (select tablespace_name, sum(bytes_cached) bytes from v$temp_extent_pool group
                        by tablespace_name) t WHERE d.tablespace_name = a.tablespace_name(+) AND
                        d.tablespace_name = t.tablespace_name(+) AND d.extent_management like 'LOCAL'
                        AND d.contents like 'TEMPORARY';



                        List out all tablespaces in the database:-
                        SELECT * FROM DBA_TABLESPACSES;
                        SELECT * FROM DBA_DATA_FILES;

                        Add a datafile to existing tablespace:-
                        ALTER TABLESPACE <tablespace_name> ADD DATAFILE
www.FullInterview.com
                                                                                                  Page 5 of 12
www.FullInterview.com
                      ‘/u01/oraprod/db/apps_st/data/datafile01.dbf’ SIZE 1024m;

                      Resize the existing datafile:-
                      ALTER DATABASE DATAFILE ‘/u01/oraprod/db/apps_st/data/datafile01.dbf’
                      RESIZE 1024m;


Compiling Invalid Objects
                      Sometimes we may find some invalid objects (PL/SQL procedures/packages) in the
                      database. To compile those invalid objects we can use ‘adadmin’ utility.

                      To check for invalid objects,
                      Login as applprod
                      $ sqlplus apps/<apps password>
                      SQL> SELECT COUNT(1) FROM dba_objects WHERE status=’INVALID’;
                      SQL> SELECT owner, object_name, object_type FROM dba_objects WHERE
                      status=’INVALID’;

                      To recompile the invalid objects,
                      Login as applprod
                      $ adadmin -> 3. Compile/Reload Applications Database Entities menu -> 1.Compile
                      APPS schema




Compiling Forms/Reports
                      We may required to recompile the forms which is already in the applications as
                      instructed by Oracle Support Analyst. To compile a form starting with name PO we
                      have to do the following.
                      Login as applprod
                      $ adadmin -> 1. Generate Applications Files menu -> 2. Generate form files

                      Enter your choice [5] : 2

                      Enter the number of workers [8] : 2

                      Your current character set is "US7ASCII".
                      Do you want to generate Oracle Forms objects
                      using this character set [Yes] ? Yes

                      Do you want to regenerate Oracle Forms PL/SQL library files [Yes] ? Yes
                      Do you want to regenerate Oracle Forms menu files [Yes] ? Yes
                      Do you want to regenerate Oracle Forms executable files [Yes] ? Yes
                      Enter list of products ('all' for all products) [all] : po

                      Generate specific forms objects for each selected product [No] ? No


                      The current set of installed languages is: US

                      Please select languages for generating Oracle Forms files.
                      You may select all of the above languages, or just a subset.


www.FullInterview.com
                                                                                                Page 6 of 12
www.FullInterview.com
                    Enter list of languages ('all' for all of the above) [all] : all


                    You selected the following languages: US

                    Is this the correct set of languages [Yes] ? Yes

                    << Compiles the forms>>
                    << After completion….>>
                    Review the messages above, then press [Return] to continue.




www.FullInterview.com
                                                                                       Page 7 of 12
www.FullInterview.com

Changing Super User’s Password
We have to periodically the database, applications and OS super user’s password for security
reason.

Database Super Users
      sys – Super user used for startup/shutdown database, recovery, managing database
      system – Super user used for managing database (adding/resizing datafiles, creating users,
       etc.)

Applications Super Users
      sysadmin – Super user used for managing application users, responsibilities, concurrent
       managers, registering reports, etc.
apps - Database User
    apps – Super database user which works as a bridge between applications and database. All
       connections made to database from applications are via apps database user.

OS Super Users
    oraprod – Owner of database software (/u01/oraprod). All maintenance activities related to
      database need to be done by oraprod user.
    applprod - Owner of applications software (/u01/applprod). All maintenance activities related
      to applications need to be done by applprod user.
    oradisc - Owner of discoverer software (/u01/oradisc). All maintenance activities related to
      discoverer need to be done by oradisc user.


sys, system Passwords
       Sys and system database user’s password can be changed in the traditional way, when the
       database is up and running.
       Command Syntax:
              Login as ‘oraprod’ OS user into server.

              $ sqlplus “ / as sysdba”
              SQL> alter user sys identified by wT5b23ky;
              SQL> alter user system identified by vt8qmsz;


sysadmin Password
       sysadmin is the application super user who has a responsibility System Administrator. Using
       this responsibility we can do user management and applications system administration.

       To change sysadmin Password:
                 1. Login into applications as sysadmin user -> Choose System Administrator
                    Responsibility -> Security : User -> Define
                 2. Query for SYSADMIN and set a new password


oraprod, applprod Password

www.FullInterview.com
                                                                                          Page 8 of 12
www.FullInterview.com
       As oraprod, applprod and oradisc are OS accounts change their password to corresponding OS
       commands.

       Command Syntax:
               # passwd oraprod
               # passwd applprod
               # passwd oradisc



apps - Database User Password
       ‘apps’ database user acts as a bridge between applications and database. Hence in some of the
applications configuration files and in database tables apps user’s password is encrypted and stored.

Hence it is necessary to use FNDCPAAS utility to change apps’s password. FNDCPASS changes apps
account’s password as well as updates the necessary tables. Also we have to run Autoconfig utility to
update the configuration files in Applications Tier.

       To change apps password:
       1. Shutdown the applications services.
       2. As ‘applprod’ OS user run,
               $ FNDCPASS apps/<current password> 0 Y system/<system password> SYSTEM
            APPLSYS <new password>

       3. Ensure you are able to login into SQL*Plus with new password
               $ sqlplus apps/<new password>

       4. Run Autocofig from $INST_TOP/admin/scripts, This step reconfigures the applications.
               $ cd /u01/applprod/inst/apps/PROD_snzclakl026/admin/scripts
               $ ./adautocfg.sh

       5.   Start the applications services and ensure it is working.




www.FullInterview.com
                                                                                            Page 9 of 12
www.FullInterview.com

Concurrent Program Registration in Oracle Applications

Steps   to Register a Oracle Report in Applications
   1.    FTP the report to server $XXNZCL_TOP/reports/US location.
   2.    Register the report as Executable
   3.    Define a concurrent program with the executable registered in Step 1
   4.    Attach the concurrent program to mentioned Request Group

1. FTP the report to server $XXNZCL_TOP/reports/US location.
        CMD> ftp 10.200.2.45
        Connected to 10.200.2.45.
        220 (vsFTPd 2.0.1)
        User (10.200.2.45:(none)): applprod
        331 Please specify the password.
        Password:
        230 Login successful.
        ftp> cd /u01/applprod/apps/apps_st/appl/xxnzcl/12.0.0/reports/US
        250 Directory successfully changed.
        ftp> bin
        200 Switching to Binary mode.
        ftp> mput XXNZCL_TEST.rdf
        mput XXNZCL_TEST.rdf? y
        200 PORT command successful. Consider using PASV.
        150 Ok to send data.
        226 File receive OK.
        ftp: 40960 bytes sent in 0.00Seconds 40960000.00Kbytes/sec.
        ftp>




www.FullInterview.com
                                                                                Page 10 of 12
www.FullInterview.com




Navigate to System Administrator Responsibility -> Concurrent -> Program -> Executable
2. Register the report as Executable
Press CTL+S to Save.




www.FullInterview.com
                                                                                         Page 11 of 12
www.FullInterview.com
Navigate to System Administrator Responsibility -> Concurrent -> Program -> Define
3. a. Define a concurrent program with the executable registered in Step 1



3. b. Define Parameters if any.



Navigate to System Administrator Responsibility -> Security -> Responsibilities -> Request Group
4.a. Query for mentioned Request Group



Select a row then Press File -> New to insert a new row
4. b. Assign the report to the Request Group.


                                      -------- End of Document ----------




www.FullInterview.com
                                                                                                   Page 12 of 12

								
To top