TL;DR: Beginning September 10, you’ll need to use Multi-Factor Authentication (MFA) when signing in with your Oracle Account to access LiveSQL. You’ll see a prompt at login to set it up.
What is changing
Starting September 10, Oracle Accounts used to sign in will require MFA at login. After your password, you’ll confirm it’s you with a one-time code or another verification method.
Why this is required
- Strongly reduces account takeovers
- Protects your projects and data
- Meets security and compliance requirements
What to expect on or after September 10
- The first time you sign in after MFA goes live, you’ll be prompted to enroll.
- Setup happens directly in the Oracle Account login experience.
- You can choose your preferred MFA method:
- Oracle Mobile Authenticator (OMA)
- SMS
- Email one-time code
- Once enrolled, you’ll enter your password plus approve a sign-in or enter a verification code.
How to prepare now
- Download an authenticator app if you plan to use one. Options include Oracle Mobile Authenticator (OMA), Google Authenticator, Microsoft Authenticator, 1Password, and Authy.
- Make sure your account recovery email and phone number are up to date.
- Store any recovery or backup codes in a safe place if offered during enrollment.
Help
- If you run into issues, please follow the official instructions in the MFA Setup Guide. The guide includes information on how to request support for MFA enrollment or login problems.
- You can also post in this forum with the tag
mfa if you’d like to share setup tips or discuss with other LiveSQL users.
We’ll update this post with screenshots and a step-by-step walkthrough as soon as the new Oracle Account MFA flow is live.
Last updated: 10/28/2025