This document contains official content from the BMC Software Knowledge Base. It is automatically updated when the knowledge article is modified.
TrueSight Capacity Optimization
TrueSight Capacity Optimization all versions
When trying to log into the TrueSight Capacity Optimization (TSCO) console an error was generated and, looking at the log, an Oracle error ORA-XXXX is being reported in the logs.
In order to verify if it is really an Oracle error you can check TrueSight Capacity Optimization (TSCO) database functionality in one of the following ways:
From TSCO 10.5 and later: use the Database Credentials Tool
Search in the official documentation about Validating database connection page.
All Version: how check DB connectivity over a period of time
If you have an intermittent problem with the database connection and want investigate on it, you can use the tool suggested here:
KA 000031771: How can I validate that the TrueSight Capacity Optimization (TSCO) Oracle Java Database Connection String URL (JDBC) that I'm using is valid for my environment?
All Version: use command line (TNSPING and SQL Plus)
- Verify Tnsping
- Test DB name resolution from AS (to see oracle server hostname execute cat /opt/cpit/env.sh | grep ORACLE_SERVER)
- Test DB ping from AS (see ip from nslookup)
ping [Database IP Address]
- Test connection from AS using SQL Plus
- verify your DB is up and the network functionality
- verify your $CPITBASE/env.sh contains the right DB hostname, then check the DNS name resolution on the As and network functionality
- verify your $TNS_ADMIN/tnsnames.ora file to be coherent with your $CPITBASE/env.sh
- check the correctness of the parameters you inserted during setup: $DBUSR, $ORACLE_SID
- check you inserted the right credentials (user/pass) for CO DB
Common Oracle Errors that trigger the TSCO web UI to be unavailable
|Error message||Meaning||Check and repair strategies|
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 matching protocol stack
|Problem in 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.|
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 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.|
|Wrong username or password||Ask to DBA the right credentials.|
Check TSCO configuration.
|ORA-28000: the account is locked||The account is locked.||Ask to 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.|
|ORA-12170: “TNS: Connect Timeout Occurred”||The error can be for many reasons, firewall issue, database down, listener down, bad sqlnet.ora parm, network trouble||Work with DBA or Network Admin to understand what causes the problem in communication between TSCO and Database.|
|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 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 Active Data Guard standby||NOCACHE or ORDER sequences were not supported for Active Data Guard standby.||Work with the DBA to fix the issue|
If the DBA changed the password, you need to reconfigure TSCO as described in KA 000032008: How do I reconfigure TrueSight Capacity Optimization (TSCO) to change environment parameters like the Database host or password, Remedy Single Sign On (RSSO) or TrueSight Presentation Server (TSPS) URL? - INCLUDES VIDEO.
Once an Oracle error has been identified and addressed, it is typically best to stop and restart TSCO in the environment to allow it to reinitialize against a clean database.