Apply server side patches using adpatch
ADPATCH skill is the basic requirement for an applications DBA.( AD actually means Applications DBA ). Oracle has hundreds and thousands developers who develop the new code, new applications function, new forms, new technology stack all the time. How can you implement these new functions or new code into your environment?
When we talk about development, we actually talk about how to improve. The current applications is not perfect, there must be some bugs in the current 11i applications---customers can find the bugs in the real working environment, Oracle Internal developers can also find lots of bugs during the development. Some bugs may be related to the major teck stack such as OA Framework or Work Flow. Other bugs may be related to product function, such as invoice forms, general ledge hierarchy and so on. How can you fix these bugs?
The answer for the above two question is to use ADPATH. Oracle releases lots of patches every single day. As long as you can the patch, you can go ahead to run adpatch to update your applications to the new cold level and fix the bugs in your environments. So adpatch is one of the ways you use to maintain your applications.
As an applications DBA, you need to apply the patch all the time either to update your applications code or to fix the bug.
Configure the Concurrent Manage
Inside applications, when users run a report or post some data, a request to run the report is generated. The command to run the report is a concurrent request. The program that generates the report is a concurrent program. Concurrent programs are started by a concurrent manager. Some concurrent request or programs examples:
Run Payroll process
Run General ledger cross instance data transfer
Post Journal Entry data
Request to run program==><Request_table>==>Concurrent Manager==>Program started.
Manage Oracle Applications Security
Applications DBA manages the applications security through user level ( control user password, create new user ), responsibility level ( grant responsibility to users ), Menu level, function level and forms level.
APPS schema, and product schemas schema might be also closed ( not published ) at most times.
Apps DBA Activities Pointwise
· Fresh Oracle Apps Installation
· Troubleshooting Applications related problems
· Starting/Stopping CRM Application
· Load balance/Form/Report issues
· Rapid Cloning
· Password change of applications/maintenance policy.
· Purging of Data/Manager log/Request log
· Concurrent Program/Manager Creation, maintenances
· Monitoring Production Servers
· Monitoring/Cleaning stray application/database processes
· Monitoring/Resolving Database alert log
· Monitoring/Resolving Load Balancing across Application Node
· Monitoring Tablespace free space
· Monitoring/Resolving Customer Upload based on mail alert
· Troubleshooting Concurrent Request/Program Issues
· Troubleshooting Concurrent Manager Issues
· Generating Trace from Application
· Performing Network Test
· Tar Creation.
· Node Addition
· Patch Application
· Database Upgradation
· Database Refresh
· APPS front end User Creation
· Backup/Restoration of Database and applications
· Other Utilities - Fulfillment Server
· Cleanup of application log & out files, Apache & Listener files, Database trace, log, core files, Tmp directory
· Analyzing Database Schemas
· Creation of custom TOP
· Analyze important application schemas regularly/weekly
· Tuning Database and Application
· Other Setup’s (Workflow,SSO,Discoverer,SSl,Printer and Webcache)
No comments:
Post a Comment