Our Oracle Analytics Cloud data model refresh jobs started failing yesterday with ORA-01017 errors. This happened right after our quarterly database credential rotation. The impact is significant - we have stale reports and failed scheduled refreshes affecting multiple dashboards.
The connection was working fine before the password change. We updated the database credentials in OAC connection settings, tested the connection successfully, but the scheduled data model refresh jobs continue to fail with the same authentication error.
Error from the job log:
ORA-01017: invalid username/password; logon denied
at oracle.jdbc.driver.T4CTTIoer.processError
Has anyone dealt with credential rotation in Analytics Cloud connections? I’m wondering if there’s a caching issue or if scheduled jobs use a different credential store than the connection test.
Another thing to check - make sure the database user account isn’t locked or expired. Sometimes after credential rotation, the old password attempts from cached connections can lock the account. Log into the database directly and check:
SELECT username, account_status FROM dba_users WHERE username = 'YOUR_OAC_USER';
If it shows LOCKED or EXPIRED, that’s your problem right there.
I’ve seen this before. When you update connection credentials in OAC, you need to do more than just edit the connection properties. The data models themselves cache connection information, and scheduled jobs may use a different credential reference.
Did you re-save each data model after updating the connection? Sometimes you need to open the data model, go to the data source, and explicitly refresh the connection reference even if it shows as connected.
That’s interesting. I did update the connection and test it, but I didn’t explicitly re-save the data models. We have about 15 data models using this connection, so that could definitely be the issue. Is there a way to bulk update them, or do I need to open each one individually?
Also check if you have multiple connections with similar names. I once spent hours debugging this only to find that some data models were pointing to an old connection definition that I thought I’d deleted but was still cached in the system. The connection test passes because it’s testing the updated connection, but the data models might be using the old one.
Unfortunately, there’s no bulk update option for data model connections in OAC. You’ll need to open each data model, verify the connection reference, and re-save. When you open the data model, go to ‘Data’ tab, right-click the connection, select ‘Inspect’, and verify it’s pointing to the correct connection with updated credentials.
Also, after re-saving, I recommend manually triggering a data refresh for each model to verify it works before relying on scheduled jobs again. The scheduled jobs have their own execution context that sometimes needs to be reset.
I’ve dealt with this exact scenario multiple times during credential rotation cycles. Here’s the complete solution:
Root Cause Analysis:
The ORA-01017 error after credential rotation occurs because Analytics Cloud has multiple layers where connection credentials are referenced: the connection definition, data model metadata, and scheduled job execution context. Simply updating the connection and testing it doesn’t propagate the new credentials to all these layers.
Complete Resolution Steps:
1. Analytics Cloud Connection Management:
First, verify your connection update was complete:
- Navigate to Console → Connections → Find your database connection
- Edit the connection, update password, and test - you’ve done this
- Important: Note the exact connection name (case-sensitive)
2. Database Credential Verification:
Before proceeding, verify the database account isn’t locked from failed attempts:
SELECT username, account_status, lock_date
FROM dba_users
WHERE username = 'OAC_SERVICE_USER';
If locked, unlock it: `ALTER USER oac_service_user ACCOUNT UNLOCK;
3. Data Model Refresh (Critical Step):
For each data model using the connection:
- Open the data model in OAC
- Go to Data tab → right-click the connection → Inspect
- Verify it shows the correct connection name
- Even if it looks correct, click ‘Reload Metadata’ to force refresh
- Save the data model (this updates the cached credential reference)
- Manually trigger a data refresh to test
4. Scheduled Job Context Reset:
This is the step most people miss - scheduled jobs maintain their own execution context:
- Go to Console → Jobs → Find affected scheduled refresh jobs
- Edit each job, even if you’re not changing anything
- Click through to the final step and save
- This forces the job execution context to pick up the new credentials
- Alternative: Delete and recreate the scheduled jobs (cleaner but more work)
5. Connection Pool Refresh:
If issues persist, the connection pool might be holding stale credentials:
- In OAC Console, go to System Settings → Performance and Compatibility
- Find ‘Connection Pool Settings’
- Set ‘Maximum Idle Time’ to 1 minute temporarily
- Wait 2-3 minutes for connections to cycle
- Reset to normal value (usually 30 minutes)
Prevention for Future Rotations:
Create a credential rotation checklist:
- Update database password
- Update OAC connection definition
- Test connection
- Re-save all affected data models with metadata reload
- Edit and re-save all scheduled jobs
- Manually test one scheduled job
- Monitor for 24 hours
Verification:
After completing these steps:
- Manually trigger each scheduled job from the Jobs console
- Check job execution logs for successful completion
- Verify data freshness in reports
- Monitor for 24-48 hours to ensure scheduled runs succeed
This comprehensive approach addresses all three focus areas: proper Analytics Cloud connection management with metadata reload, handling database credential rotation across all layers, and ensuring scheduled data model refresh jobs pick up the new credentials through execution context reset.