ORA-12505: TNS: listener does not currently know of SID given in connect descriptor
ORA-12541: TNS: no listener
ORA-12514: TNS: listener does not currently know of service requested in connect descriptor
| TSCO cannot connect to the database due to network issues or misconfiguration (client or server-side). | Verify the tnsnames.ora file
Verify the SID and/or the service name
Ask to DBA to check if listener is running
Verify if the Database instance is up and running |
ORA-12519: TNS: no appropriate service handler found
ORA-12516: TNS: listener could not find available handler with a matching protocol stack | The problem in the configuration in limits on sessions/processes DB side | How to fix errors ORA-12516 and ORA-12519 |
| ORA-00018: maximum number of sessions exceeded | The Oracle server is configured to support a limited number of direct sessions, defined in the Oracle configuration parameter sessions. | Verify the configuration of connection pools and check ETL parallelism.
If none of the above can be safely reduced, ask the DBA team to increase the sessions parameter; this action requires a restart of the Oracle instance |
ORA-01034: ORACLE not available
ORA-27101: shared memory realm does not exist
ORA-01033: ORACLE initialization or shutdown in progress | The Database instance is down. | Contact the DBA team and verify if this might be due to a scheduled activity, such as a planned shutdown. |
| ORA-03114: not connected to ORACLE | The DB is not reachable: or is down or there is a network issue | Contact DBA and network team to restore connectivity between TSCO servers and DB server |
ORA-00257: archiver error. Connect internal only, until freed.
or
ORA-00257: Archiver error. Connect AS SYSDBA only until resolved. | The database instance has saturated the configured archive space. | Contact the DBA team and ask to perform an archive of the redo log and check rman backup scheduling. Investigate extraordinary activities such as historical imports. The error could also happen if there is not enough space on the file system to write new or enhance the existing Archive logs. |
| ORA-01017: invalid username/password; logon denied | Wrong username or password | Ask DBA the right credentials.
Check TSCO configuration. |
| ORA-28000: the account is locked | The account is locked. | Ask DBA to unlock the account.
Verify if the DBA changed the password and if a TSCO reconfiguration is needed |
| ORA-28001: the password has expired | The user's account has expired and the password needs to be changed | Change the password (TSCO reconfiguration) or contact the DBA |
ORA-28002 The Password Will Expire in x Days
ORA-28011: The account will expire soon; Change your password |
The password for the account or the account is going to expire. | Please contact the DBA to fix it |
| ORA-01688: unable to extend table XXXX | One (or more) of the tablespace is saturated | Work with the DBA in order to fix the space allocated for the tablespace. |
| 12170 TNS-12535/TNS-00505: Operation Timed Out
https://helpx.adobe.com/experience-manager/kb/OracleFirewallProblems.html
https://asktom.oracle.com/pls/apex/f?p=100:11:::NO::P11_QUESTION_ID:9539262200346176966
| The error can be for many reasons, firewall issue, database down, listener down, bad sqlnet.ora param, network trouble, Firewall is dropping idle session
-System Task Triggered by the Primary Scheduler are generating a Timeout or Similar timeouts for Datahub | Work with DBA or Network Admin to understand what causes the problem in communication between TSCO and Database.
-Reconfigure the firewall, to not drop idle connections over the Oracle port
-Tune the OS TCP stack on AS and set keep (tcp_keepalive_time, tcp_keepalive_intvl, tcp_keepalive_probes)
- Set SQLNET.EXPIRE_TIME = 1 on the database server in sqlnet.ora file,
|
| ORA-04031 unable to allocate XXX bytes of shared memory | There is an issue in memory allocation on the DB server | Look to the official documentation at the page Database requirements. In detail, in the Oracle section, there is a set of parameters: verify with DBA if the ones under Memory Management are set as per recommendation |
| ORA-16000: database or pluggable database open for read-only access | This error is generated when the database has been opened for read-only access. Attempts to modify the database generates this error. | Work with the DBA to shutdown and re-open the database for read-write access. |
| ORA-03179: NOCACHE or ORDER sequences cannot be accessed from the Active Data Guard standby | NOCACHE or ORDER sequences were not supported for Active Data Guard standby. | Work with the DBA to fix the issue |
ORA-02396: exceeded maximum idle time, please connect again
| This happens when you have a resource profile enabled in oracle with a limited idle time set.
If you omit a resource profile then you will have an unlimited idle_time and you will never get an ORA-02396 error. | Resolving the problem requires asking to the DBA to remove this idle time limit removed.
this also causes ORA-01012, when trying to do an oracle call without being logged on, since you've been cut off by idle time.
Please ask the DBa to remove the idle time limit setting from DB to solve the issue, we are using conneciton pools, so we need connection to stay active, not to be killed after a certian amount of inactivity time. |