Skip to main content

Duties of an Oracle Apps DBA

Summary:
What duties, if any, are different for an Apps DBA versus those of an Oracle 8/9i DBA?

Full Article:
Disclaimer: Contents are not reviewed for correctness and are not endorsed or recommended by ITtoolbox or any vendor. Popular Q&A contents include summarized information from Oracle-DB-L discussion unless otherwise noted.

1) Adapted from response by Harshal Dikshit on Tuesday, November 26, 2002

Oracle APPS DBA's duties are almost same as of Oracle DBA but your work will be more specific to the Architecture (or I should say Environment) and OFA of Oracle Application. Apart from that there are few more things you should know like applying patches or adadmin utility and some basic functionality of SYSADMIN responsibility of APPS.

2) Adapted from response by Winston Douglas on Tuesday, November 26, 2002

An APPs DBA knows all that a regular DBA knows plus the following:

- Application fundamentals such as concepts and architecture
- Application Installation and configuration
- Patching and Upgrades
- Patch Management and Version Control
- Customization Updates
- Cloning requirements. This can be frequent in an Apps environment
- Concurrent Managers
- Forms/Report Servers
- Web Servers
- all the "ad" utilities
- all the database restrictions for the applications. That is so that the installation is still supportable and conforms to all vendor (Oracle) requirements.
- All special application related regular and maintenance functions. Such as month end and period end functions.
- Understand any backup and recovery constraints. Such as for table imports (NOT) and partial recoveries.
- special requirements and restrictions for tuning. Example optimizer and index requirements.
- Printer Configuration
- User Access Administration

This could be a matter for further discussion as it could be argued that all DBA's should be aware of the above or equivalent for any database application (Oracle or otherwise).

Comments

Popular posts from this blog

Script to Collect Data Guard Physical Standby Diagnostic Information

Script to Collect Data Guard Physical Standby Diagnostic Information [ID 241438.1] -------------------------------------------------------------------------------- Modified 20-APR-2011 Type SCRIPT Status PUBLISHED Overview -------- This script is intended to provide an easy method to provide information necessary to troubleshoot Data Guard issues. Script Notes ------------- This script is intended to be run via sqlplus as the SYS or Internal user. Script ------- - - - - - - - - - - - - - - - - Script begins here - - - - - - - - - - - - - - - - -- NAME: DG_phy_stby_diag.sql -- ------------------------------------------------------------------------ -- AUTHOR: -- Michael Smith - Oracle Support Services - DataServer Group -- Copyright 2002, Oracle Corporation -- ------------------------------------------------------------------------ -- PURPOSE: -- This script is to be used to assist in collection information to help -

ORA-01501: CREATE DATABASE failed

Problem: ======== During the creation of a new database the CREATE DATABASE command fails with the following errors: ORA-01501: CREATE DATABASE failed ORA-01519: error while processing file '?/rdbms/admin/sql.bsq' near line 406 ORA-00604: error occurred at recursive SQL level 1 ORA-04031: unable to allocate 2192 bytes of shared memory ("shared pool", "unknown object","KQLS heap","KQLS MEM BLOCK") Solution: ========= 1. Increase the shared_pool_size parameter in the init .ora file. 2. Shutdown abort your database. 3. Startup nomount your database. 4. Execute the CREATE DATABASE command again. Explanation: ============ If your shared_pool_size is too small, the CREATE DATABASE command cannot finish successfully. This happens typically on small test instances when you just want to test anything on an empty instance and do not want to waste too much memory on a server. In this case you often edit in