Oracle apps DBA at Apps Associates · Remote only · 4 - 6 years · ₹5L - ₹16L / yr · Profitable · Remote only · Posted 14 Feb 2023

Role: Oracle Apps DBA Consultant
Exp: 4-6 years
As Oracle Apps DBA, able to implement Patching, Cloning, Backup and restoring RMAN. Having experience in Oracle 11i RAC, ERP 12.2 & experience in Performance tuning.
Responsibilities:
- · The Oracle Applications DBA will be responsible for the overall management and maintenance of Oracle EBS R12.2 applications & database, and other non-ERP Oracle databases.
- · The DBA will provide technical and operational DBA support for the day to day operations on ERP oracle database, ERP applications, and non-ERP Oracle databases for data warehouse and other applications.
- · The DBA will partner with technical, functional, development and business groups to ensure that database performance standards adhere to enterprise service level agreements

About Apps Associates
About
Similar jobs (1)
Applications on this job are not being reviewed actively. You may apply but please follow up with the company via other channels too.
Full-time, permanent position implementing, supporting, and optimizing enterprise ERP systems for clients, with a focus on supply chain, manufacturing, and planning modules. The role is client-facing first: success depends as much on clear, polished communication as on functional expertise.
Required
Polished client communication: able to run status calls, present findings, and manage escalations with professionalism and composure
Ability to translate technical concepts — configurations, integrations, system behavior — into plain language for business and executive audiences
Career at an IT services company, systems integrator, ERP vendor, or consulting firm (e.g., Accenture, NTT Data, Wipro, Infosys, ERP-partner boutiques) — required; candidates whose ERP experience is exclusively in-house at a single employer will not be a fit
5–8 years in enterprise ERP (any major platform: Oracle, SAP, Workday, Dynamics, NetSuite)
At least one full-cycle implementation: requirements, configuration, testing, cutover, post-go-live support
Functional depth in SCM-adjacent modules: inventory, order management, procurement, costing, or planning
Integration exposure: REST/SOAP APIs, third-party system connections, data migration
Clear written deliverables: documentation, status reports, and issue summaries that nontechnical stakeholders can act on
Preferred
Experience presenting to steering committees or client leadership
Multi-industry client exposure
Experience automating support or testing workflows
Reporting/analytics tooling (BI, embedded ERP analytics)






