Changing the passwords that matter

APPS and the schema passwords, WHAT HAS TO BE TOLD AFTERWARDS, and THE ORDER THAT AVOIDS LOCKING YOURSELF OUT. Changing the APPS password is not a database operation — it is an estate-wide change, because a great many things hold a copy of it. SO THE WORK IS ALMOST ENTIRELY IN WHAT HAS TO BE TOLD AFTERWARDS. The application tier holds it in its configuration — which means the context file and an AutoConfig run, Module 2 Lesson 5, rather than editing generated files. Every custom script that connects holds it. Every interface, every reporting tool, every monitoring check — Module 13 Lesson 2's deep check needs a credential too. WHICH MAKES THE INVENTORY THE REAL DELIVERABLE, AND IT IS NEVER COMPLETE. The things you know about are the easy half; the script somebody wrote three years ago that runs every Monday is the one that fails a week later,…

In this module: Module 15 · Security, credentials and audit

1. 1What you are actually holding
2. 2The default accounts
3. 3The credential in the context fileFree preview
4. 4Changing the passwords that matter
5. 5Least privilege for a DBA team
6. 6Auditing: what to record and what it costs
7. 7Encryption, in transit and at rest
8. 8Network exposure
9. 9What breaks: four security findings
10. 10Lab briefing · Audit an estate you did not build