If Clarity stops collecting data, the issue often appears in the Collector Log. Click Settings in the left sidebar and select Collector. Then, go to the Collector Log tab and look for one of the following errors:
- OCI_ATTR_PASSWORD
- Connection cannot be closed when open statements or LOBs exist
- Local variable active_sql referenced before assignment
- get_db_mgr
OCI_ATTR_PASSWORD
Error log found:
Traceback (most recent call last):\n File "collectors\\e1n_dbmgr.py", line 76, in f_conn\ncx_Oracle.DatabaseError: ORA-24960: the attribute OCI_ATTR_PASSWORD is greater than the maximum allowable length of 255\n
What it means:
The Database Manager username or password is incorrect.
How to resolve the issue:
- Click Settings in the left sidebar and select Update Settings.
- Click the Change Setting button and select DB Manager from the drop-down menu.
- Re-enter username and/or password.
- Don't forget to click the Action icon to update your settings.
Connection cannot be closed when open statements
or LOBs exist
Error log found:
Traceback (most recent call last):\n File "collectors\\e1n_dbmgr.py", line 319, in get_waits\n File "collectors\\e1n_dbmgr.py", line 107, in f_conn\ncx_Oracle.DatabaseError: DPI-1054: connection cannot be closed when open statements or LOBs exist
What it means:
Clarity is unable to disconnect from the database and pull information.
How to resolve the issue:
- Click Settings in the left sidebar and select Update Settings.
- Click the Change Setting button and select DB Manager from the drop-down menu.
- Deactivate the setting.
- Contact your DBA immediately. An account that is unable to disconnect can cause database queries to stack up and CPU to rise.
Local variable active_sql referenced before assignment
Error log found:
Traceback (most recent call last):\n File "collectors\\e1n_dbmgr.py", line 450, in get_sql\nUnboundLocalError: local variable active_sql referenced before assignment\n
What it means:
Clarity is unable to pull information from one of four queries:
- Active query statements
- Wait type
- Expensive Queries
- CPU
How to resolve the issue:
- Go to the Database Management module to find which graph or chart is missing data.
In this example, the Most Expensive Queries chart is missing data.
- Next, check the error log inside your database to see if any tables are erroring out.
- Make sure the table exists and contains data.
get_db_mgr
Error log found:
Traceback (most recent call last):\n File "tools\\e1n_api_bridge.py", line 774, in get_db_mgr\nTypeError: NoneType object is not iterable\n
What it means:
The Database Manager configuration is inactive and/or the Collector interval is set to zero.
How to resolve the issue:
- Click Settings in the left sidebar and select Update Settings.
- Click the Change Setting button and select DB Manager from the drop-down menu.
- Make sure the Active box is checked for each configuration.
- Next, go to the Change Collector Intervals tab.
- Scroll down to find dbmgr/run and set the interval to 2 minutes.
- Click the action icon to update your settings.
User does not have permission
Error log found:
Traceback (most recent call last):\n File "src\\pymssql.pyx", line 448, in pymssql.Cursor.execute\n File "src\\_mssql.pyx", line 1064, in _mssql.MSSQLConnection.execute_query\n File "src\\_mssql.pyx", line 1095, in _mssql.MSSQLConnection.execute_query\n File "src\\_mssql.pyx", line 1228, in _mssql.MSSQLConnection.format_and_run_query\n File "src\\_mssql.pyx", line 1639, in _mssql.check_cancel_and_raise\n File "src\\_mssql.pyx", line 1683, in _mssql.maybe_raise_MSSQLDatabaseException\n_mssql.MSSQLDatabaseException: (297, bThe user does not have permission to perform this action.DB-Lib error message 20018, severity 16:\\nGeneral SQL Server error: Check messages from the SQL Server\\n)\n\nDuring handling of the above exception, another exception occurred:\n\nTraceback (most recent call last):\n File "collectors\\e1n_dbmgr.py", line 56, in f_conn\n File "src\\pymssql.pyx", line 468, in pymssql.Cursor.execute\npymssql.OperationalError: (297, bThe user does not have permission to perform this action.DB-Lib error message 20018, severity 16:\\nGeneral SQL Server error: Check messages from the SQL Server\\n)\n
What it means:
Clarity cannot connect to the database.
How to resolve the issue:
- Click Settings in the left sidebar and select Update Settings.
- Click the Change Setting button and select DB Manager from the drop-down menu.
- Check that the DNS Name is correct.
- If you do not have the appropriate permissions for these database credentials,
contact your DBA.
Topics: