Connection status

Typical meaning

What to do next

Failed to resolve the hostname

This normally means one of two things: the server no longer exists, or the server does exist but there is no network path between the AssetStudio server and the server it is trying to connect to.

Confirm if the server AssetStudio trying to connect to does exist. If it does not exist, then the Database connector can be archived. If the server exists, then verify that it is running and you have opened up some more network routes to enable the connection.

An unknown error occurred

Typically the Oracle database credentials being used to connect to the database doesn’t have the correct access rights, causing this error when we are trying to run a database query.

Verify the Oracle database credentials have the correct permissions. Refer to this knowledge base article for more information.

The server specified does not exist

This normally means one of two things: the server no longer exists, or the server does exist but there is no network path between the AssetStudio server and the server it is trying to connect to.

Confirm if the server AssetStudio trying to connect to does exist. If it does not exist, then the Database connector can be archived. If the server exists, then verify that it is running and you have opened up some more network routes to enable the connection. Equally, you may want to verify the network where this host resides exists within those to scan in AssetStudio under Dashboard > Networks .

No Oracle listener could be found on the specified port

The port specified in the connector may be incorrect or there is no Oracle Listener running on the server.

Verify whether Oracle is running on the server and the port is correct. In some cases such as where a server is for business continuity purposes, the Oracle database may exists but it not up and running when the inventory was performed.

ORA-00257: Archiver error. Connect AS SYSDBA only until resolved

The archiver process received an error while trying to archive a redo log. If the problem is not resolved soon, the database will stop executing transactions. The most likely cause of this message is that the destination device is out of space to store the redo log file. Another possible cause is that a destination marked as MANDATORY has failed.

Connect AS SYSDBA only until resolved" indicates an issue with the Oracle Automatic Archival process. Potential resolutions include:

Free Up Space in FRA:

This is the most likely solution. Connect as SYSDBA and use Recovery Manager (RMAN) to manage archived redo logs.

You can delete old archive logs using RMAN commands like DELETE ARCHIVELOG ALL .

Increase FRA Size (if necessary):

If insufficient space is a recurring issue, consider extending the FRA. However, plan for future storage needs to avoid frequent expansion.

Investigate Other Causes (if space isn't the issue):

In rare cases, the archiver error might have other causes. Check the archiver trace file for detailed error messages. A DBA can assist with further troubleshooting.

More information at: https://docs.oracle.com/en/error-help/db/ora-00257/

ORA-01005: null password given - login denied

Indicates a failed login attempt due to an incorrect password or a password-related issue.

The database wasn't provided with a valid password during the login attempt. This could be due to several reasons:

Incorrect Password: You might have simply typed the password wrong.

Missing Password: Some tools or applications might accidentally omit the password when trying to connect.

Connection String Issue: The connection string you're using might not include the password information.

More information at: https://docs.oracle.com/en/error-help/db/ora-01005/

ORA-01017 Invalid Username & Password

This message verifies that AssetStudio has connected to the host and that Oracle resides on the machine. However, the Oracle database credential username and/or password is incorrect.

The most likely reason is that the username and password combination you provided doesn't match any valid user account in the Oracle database. However, there could be other contributing factors:

Incorrect Username: You might have misspelled the username or used the wrong one entirely.

Incorrect Password: The password you entered might be wrong, have typos, or be case-sensitive (not matching the way it's stored in the database).

Account Disabled: It's possible the user account you're trying to use is disabled or locked.

More information at: https://docs.oracle.com/en/error-help/db/ora-01017/

ORA-01033 Oracle Initialization or Shutdown in Progres

Indicates that you attempted to connect to an Oracle database while it's either starting up or shutting down. In simpler terms, the database is currently unavailable for connections because it's busy with its own startup or shutdown routine.

Cause:

Oracle doesn't allow connections during its initialization or shutdown process to ensure data consistency and avoid conflicts. This error occurs when you try to connect at an inconvenient time.

Solution :

The most straightforward solution is to wait a few minutes and try connecting again. Once the database finishes starting up or shutting down completely, it will be available for connections.

Additional Tips :

You can check with your database administrator to see if they are aware of any planned maintenance or downtime that might explain the startup or shutdown process.
If the error persists even after waiting a reasonable amount of time, it's possible the startup or shutdown process has encountered an issue. In such cases, consult your administrator for further investigation.

More information at: https://docs.oracle.com/en/error-help/db/ora-01033/

ORA-01034: ORACLE not available

Indicates that the Oracle database you're trying to connect to is currently unavailable.

Cause:

There are several reasons why the Oracle database might be unavailable:

Not Started Up: The most common cause is that the Oracle instance simply hasn't been started yet. It's like trying to use a computer before it's fully booted up.

Listener Not Running: The Oracle listener process, responsible for facilitating client connections, might not be running.

Network Issues: Firewall restrictions or other network problems could prevent your client machine from reaching the database server.

Configuration Errors: Incorrect settings in the tnsnames.ora file (maps service names to connection details) or other configuration issues might be hindering the connection.

Troubleshooting Steps:

Check Database Status: Verify with your database administrator if the Oracle instance is running.

Confirm Listener Status: Ensure the listener process is operational on the database server.

Review Network Connectivity: Make sure there are no firewall restrictions or network connectivity problems between your client and the server.

Check tnsnames.ora : If you're using a service name to connect, review the tnsnames.ora file for any typos or incorrect configuration related to the service name, hostname, port, and SID (if used).

Additional Tips:

The error message might sometimes be accompanied by other codes providing more specific details about the cause. Pay attention to any additional error information.

You can use the tnsping <service_name> command from your client machine to test the connection to the database and identify network-related issues.

More information at: https://docs.oracle.com/en/error-help/db/ora-01034/

ORA-01109: database not open

This error signifies that you're attempting to connect to an Oracle database that is currently unavailable because it's not operational. In simpler terms, the database is closed and cannot accept connections.

Causes:

Intentional Shutdown: The Oracle database instance might have been shut down deliberately for maintenance activities, upgrades, or other administrative tasks.

Unexpected Crash: The database might have encountered an unexpected issue and crashed, leading to an unavailable state.

Pluggable Database Not Opened (CDB Environments): In Oracle versions supporting pluggable databases (PDBs), this error can occur if the specific PDB you're trying to connect to is not open within the Container Database (CDB).

Resolving ORA-01109:

Verify Database Status: Contact your database administrator to confirm the database's current state. They can tell you if it's intentionally shut down or has crashed.

Wait for Startup: If it's a planned shutdown, wait until the administrator restarts the database instance. Once the startup process is complete, you should be able to connect successfully.

Open Pluggable Database (if applicable): In a PDB environment, the administrator might need to activate the specific PDB you're trying to access using the ALTER PLUGGABLE DATABASE command. This makes the PDB operational and allows you to establish a connection.

Additional Tips:

Automatic Retries: Some tools might have built-in mechanisms to automatically retry the connection after a brief delay. This can be helpful in situations where the database is temporarily unavailable due to network fluctuations or transient issues.

Seek Assistance: If you're unsure about the database status or don't have the necessary privileges to open a PDB, the best course of action is to contact your database administrator. They can provide more specific guidance based on your environment and troubleshoot any underlying problems that might be preventing the database from opening.

More information at: https://docs.oracle.com/en/error-help/db/ora-01109/

ORA-03113 End-of-file on Communication Channel

More information at: https://docs.oracle.com/en/error-help/db/ora-03113/

ORA-12505: TNS:listener does not currently know of SID given in connect descriptor

More information at: https://docs.oracle.com/en/error-help/db/ora-12505/

ORA-12514: TNS Listener Does Not Know of Service Requested in Connect Descriptor

More information at: https://docs.oracle.com/en/error-help/db/ora-12154/

ORA-12518: TNS:listener could not hand off client connection

More information at: https://docs.oracle.com/en/error-help/db/ora-12518/

ORA-12541: No TNS Listener

This message verifies that AssetStudio has connected to the host and that the port being used to connect to the Oracle database is valid. However, the service name or Oracle SID is incorrect.

Check if the database exists and archive the Database connector if it does not. If the database has been renamed the Database connector details should be updated with the correct details to allow an inventory. More information at: https://docs.oracle.com/en/error-help/db/ora-12541/

ORA-27101 Shared Memory Realm Does not Exist

More information at: https://docs.oracle.com/en/error-help/db/ora-27101/

ORA-28001: the password has expired

More information at: https://docs.oracle.com/en/error-help/db/ora-28001/

Success

The target Oracle database was successfully inventoried by Certero

Failed to connect using Oracle direct mode

This typically indicates that the target database is legacy and Certero is unable to connect

Consult your DBA to identify the version of Database to verify if is supported by Certero.

Where it is a supported version please contact support.