Before version 22.1 of ORDS, having a database configured for REST APIs and APEX could have as many as 3-4 connection pools established. Let’s say you’re on an older version of ORDS, or you’re not super familiar with the ORDS plumbing. SYSTEM, I can run the following query:ĪCCOUNT UNLOCK But Jeff, I’m not sure which database or which user is having problems? My default ORDS connection pool is going against my ORCLPDB1 database, which is a PDB, and I have a PDB install. Step 2: Go into the database and fix said error(s)

It’s telling us that our database account is locked. The connection pool named: |default|lo| had the following error(s): ORA-28000: The account is locked. This can occur if the database is unavailable, the maximum number of sessions has been reached or the pool is not correctly configured.

Let’s look at scenario #1: T21:45:45.391Z WARNING The pool named: |default|lo| is invalid and will be ignored: ORDS was unable to make a connection to the database. But more often than not, the errors generated on startup up ORDS are pretty straightforward. Sometimes error messages can be vague and even misleading. In this post, I want to give you a set of logical steps you can follow to figure out what’s going on, and how to fix the problem(s)! Step 1: Read the error message(s) And if ORDS can’t connect to the database, then you will see things like your APEX apps not load, your REST APIs not work, or your MODPLSQL apps not come up. If the pool is invalid, then ORDS can’t connect to the database. Minding your own business as one does, you go to startup ORDS and are suddenly informed that one or more of your connection pools are invalid! The pool named: |default | is invalid and will be ignored This means there are no database connections for this database being created.

Easy file locker invalid password