Comments
-
Hello, it is not about password, the database is down, error: the database system is in recovery mode run the commands below and let us know: systemctl status 'postgresql*' if status is failed run the command below journalctl -xeu postgresql-16.service
-
Hello, yes, you can have it separately. Best to use PostgreSQL atleast version 16 and TimescaleDB extension atleast 2.10(the newer the better). All you need is to have PostgreSQL open to connections from XormonNG VM. When starting the app you will be asked for credentials to the database and for the first setup you will…
-
Run it on the CDB, the "CONTAINER = ALL" will give the user permissions for all PDBs as well
-
Hi, you need to have sqlplus installed on the machine where XormonNG is running
-
DB name and Instance are meant to be the same. To make it more clear we will change "DB name" and LDB" in forms to Instance Shall I put instance name if it is the default one(single instance)? Yes just put in the Instance you want the application to connect through For a single instance SQLServer cluster you can use the…
-
Hello Alexo, send us logs UI --> settings --> Logs --> support logs: follow the form Send us generated file via https://upload.xormon.com Note a reference pls.
-
There was an issue in earlier versions where microservice was able to collect data one additional time after it was removed and so it would stay in the menu. Fixed since 1.7. You can remove the records that are still there with the following sql query or wait for 7 days and it will be removed automatically. su root su…
-
Hello, send us logs UI --> settings --> Logs --> support logs: follow the form Send us generated file via https://upload.xormon.com Note a reference pls.
-
check last update timestamps under the tables under the Total configuration table and also check it under the configuration table for the affected instances and send us screenshots
-
Hello, that is a status of the database => "Open" or "Closed" from gv$instance view and it is updated once per hour.
-
Hello, sure, you can. Make sure the postgresql database is at least version 14(the newer the better) and timescaledb extension is newer than 2.9.1. Most of our lab and what we provide are versions 2.14.2 and newer so that is what we recommend as of now. this official documentation should guide you through the installation…
-
please send us logs UI --> settings --> Logs --> support logs: follow the form Send us generated file via https://upload.xormon.com
-
Hello, uknown status for databases we cannot connect to is expected, health status for SQLServer is more of a connection status => if we connect OK otherwise NOK. I suppose the message should be "no current health status information". In the future version you will be able to see separate tables for Connection and Data…
-
1. In the Overview section of each SQL Server instance the graph that should contain information about deadlocks does not contain any values (I guess it should report 0 if no deadlocks where found). If there isn't a 0 the metric wasn't returned at all 2. In the Instances/<DB name>/Capacity section of each database the tab…
-
Hello Jesper, when connecting we specify that intent is read only, but unfortunately that seems to not be enough With this patch the script will not crash and will pool data as expected (changes from yesterday are included and will be included in versions going forward)…
-
Hello Jesper, no, that wasn'ŧ a known issue, thanks for letting us know and testing so thoroughly. 1.Here is a patch: https://download.xormon.com/patch/1.5-26-g08e21/sqlserver-service.pl.gz Gunzip it and copy to this path in your Xormon application directory (755, xormon owner): server-nest/microservices/sqlserver/…
-
Hello, you can find more specific info about most of the metrics here: https://www.ibm.com/docs/en/db2/11.5?topic=functions-mon-get-database-get-database-metrics ROWS_MODIFIED he number of rows inserted, updated, or deleted.This monitor element is an alias of the rows_written monitor element. This monitor element includes…
-
Hello, are you sure you have granted the permissions? https://lpar2rrd.com/OracleDB-performance-monitoring-install.php#OracleDB section: Create DB user for LPAR2RRD Solution: Either re-grant them or you can check their status like so("/as sysdba"): SELECT grantee, table_name, privilege FROM DBA_TAB_PRIVS WHERE grantee LIKE…
-
Hello, apply these 2 patches. 1. https://download.stor2rrd.com/patch/7.60-1-6-g116a9/infortrendperf.pl.gz Gunzip it and copy to /home/stor2rrd/stor2rrd/bin (755, stor2rrd owner) -rwxrwxr-x 1 stor2rrd stor2rrd 30378 Feb 20 09:59 infortrendperf.pl If your web browser gunzips it automatically then just rename it: mv…
-
send us output of these commands please cd /home/lpar2rrd/lpar2rrd # or where your LPAR2RRD work dir is tail -1 etc/version.txt ls -l etc/web_config/hosts.json cat etc/web_config/hosts.json | grep DB2
-
Hello, have you upgraded to v7.60 or is it on virtual appliance with v7.60 already preinstalled?
-
It uses the first section for sure. I believe that the issue has been found, download these 2 patches, apply them and try the connection test again, if it goes ok then the data should start collecting as well https://download.lpar2rrd.com/patch/7.43-2-1-g4983/sqlserver-apitest.pl.gz…
-
Hello, 1.check which driver the script is using: cd /home/lpar2rrd/lpar2rrd # or where your LPAR2RRD work dir is cat data/SQLServer/sqlserver_driver.txt {ODBC Driver 13 for SQL Server} 2.and then check file "/etc/odbcinst.ini" to make sure there isn't specified port under the used driver example: [ODBC Driver 13 for SQL…
-
Try this patch, wait for at least 15 minutes, check a few graphs and send us output of the command below. command: tail /home/lpar2rrd/lpar2rrd/logs/error.log-sqlserver patch: https://download.lpar2rrd.com/patch/7.40-2-3-ged4e/sqlserver-db2json.pl.gz Gunzip it and copy to /home/lpar2rrd/lpar2rrd/bin (755, lpar2rrd owner)…
-
Try to apply the patch below and let it run for a while. The affected Instance should collect data, but keep an eye on other SQL Server Instances also and make sure they did not stop collecting data. If they stop and you need them more than this one then reapply the backup. let us know how it went, this will help us…
-
Hello, run these queries, and send us the output select to_char(action_time,'yyyy-mm-dd') "DATE",<br> action,<br> namespace,<br> version,id,<br> …
-
Hello Greg, so after you set up listener.ora and sqlnet.ora the connection test started working, is that correct?
-
We looked at this closely and are you sure the IP address is correct? connection test you sent us output of was done to 172.30.174.96:1433 and the one entered into web form is 172.130.174.96:1433
-
Does this happen every time you test connection or does it sometimes go through?
-
These changes will be accounted for in the upcoming LPAR2RRD version 7.40 In the meantime you can use these patches. This patch is for connection test: https://download.lpar2rrd.com/patch/7.34-5-16-gedc59/sqlserver-apitest.pl.gz Gunzip it and copy to /home/lpar2rrd/lpar2rrd/bin (755, lpar2rrd owner) -rw-rw-r-- 1 lpar2rrd…
Howdy, Stranger!