The Performance Warehouse only creates the required tables in the database.
The default ports are:
- SQL Server 1433.
- Oracle 1521.
- DB2 50000.
- PostgreSQL 5432.
SQL Server instance with static port
To connect to a specific instance of Microsoft SQL, add
;instance=<instancename> to the Database Name in the AppMon Client and choose Settings > Dynatrace Server > Performance Warehouse > Connection Details.
The valid string for Database Name and the database instance
SQLEXPRESS would look like
<databasename>;instance=SQLEXPRESS. The named parameter
instance is added to the connection string.
Leave out the host portion in the instance name. In the example below, the host's name is
db.sample.net. A host/instance combo is
SQL Server instance with dynamic port
To connect to an instance with a dynamic port setting, click Settings > Dynatrace Server > Performance Warehouse tab > Connection Details tab in the AppMon Client and leave the Port field blank.
To run more than one or run the default SQL Server instance on a machine, make sure instances communicate using distinct ports with their respective clients. To do this, set different ports manually or let the SS instances dynamically change ports if a conflict occurs.
Ensure that the SQL Server Browser service is started, so it can broker the dynamic port for the named SQL Server instance using UDP port 1434. Also ensure that the firewall is configured accordingly if you access SQL Server remotely. The UDP port is 1434 for SQL Server and Browser and TCP dynamic port range for SQL Server.
The following is the resulting code at the bottom of
<repositoryconfig memento.version="188.8.131.5254" lowduration="-1" highduration="1209600000" deletefromhigh="true" midduration="5184000000" querytimeout="7200" ddl=""> <repository> <database name="dynaTrace4;instance=DYNASQLSERVER" dbms="SQLServer" /> <credential password="xxxxxxxxxxxx" user="gy" /> <connection port="" usessl="false" host="GCW8" ignorewarnnonproduction="false" useurl="false" connectonstartup="true" embededdatapath="repository" url="jdbc:jtds:sqlserver://GCW8:/dynaTrace4;instance=DYNASQLSERVER" /> </repository> </repositoryconfig>
connection port="" is empty and there is no port specified after
//<hostname>:. The latter is not relevant, as
Microsoft recommends connecting to SQL Server using Windows Authentication. This is necessary if you want to use Active Directory services for this purpose.
To enable Windows Authentication for a SQL Server Performance Warehouse database, you must add two lines to
SQLSERVERDOMAIN is the machine's domain or its name / the host name, if you don't use a domain.
You must also add the two lines to
dtfrontendserver.ini, because the Frontend Server can now directly connect to the Performance Warehouse. Add the options before the
See How to connect the Performance Warehouse to a MS SQL Server using Windows Authentication for more information. You can also find a detailed description for Single Sign On to SQL Server and AppMon Server, which needs the previously listed lines in
You can specify a schema other than the users default schema. To do this, add
:currentSchema= to the database name. A valid string for the database name
dynaTrace4, and the custom schema
dynaschema, would look like dynaTrace4:currentSchema=dynaschema.
Instead of a database name in the connection UI, you can apply an Oracle SID to access an RAC.
The default value for the maximum number of connections is 100. You can change this value using the
maxconnections command line parameter. For example:
If you see the following:
com.ibm.db2.jcc.b.nm: DB2 SQL Error: SQLCODE=-286, SQLSTATE=42727, SQLERRMC=8192; DB2ADMIN, DRIVER=3.50.152 on DB2
Drop and recreate the database using the following code:
CREATE DB database_name PAGESIZE 16384
If you see the following:
com.ibm.db2.jcc.am.mo: A default table space could not be found with a page size of at least "4096" that authorization ID "<dynatrace_user>" is authorized to use.. SQLCODE=-286, SQLSTATE=42727, DRIVER=4.7.85
To create this, use the following code:
CREATE USER TEMPORARY TABLESPACE <user_temporary_tablespace_name> MANAGED BY AUTOMATIC STORAGE; GRANT USE OF TABLESPACE <user_temporary_tablespace_name> TO USER <dynatrace_user>;
If the database connection does not work, use the following steps to diagnose problems:
- Verify that the database machine is reachable from the AppMon Server machine by pinging the machine.
- Verify that a vendor specific database client like SQLPlus for Oracle can reach the database.
- Verify that it is possible to connect to the database with a JDBC client like Squirrel SQL Client).
If every step is successful, but the AppMon Server is still unable to connect to the database, contact AppMon support.
AppMon triggered this incident after the clean up job was executed, when one of the following events, and or exceptions, occurred:
|Not written measurements||Skipping Data occurred where it was not possible to write data in the Performance Warehouse|
|Exceeded time for writing measurements||It was not possible to write data within one minute (see the Performance Warehouse Write Dashboards). Frequent messages can lead to skipped data|
|Written duplicated percentiles||If this message occurs frequently contact support.|
|Written duplicated measurements||If this message occurs frequently contact support. Try to drop the content of the measurement_temp1 or measurement_temp2 tables.|
|Errors while getting baseline Settings||Check server log and contact support if necessary.|
|A problem occurred during cleanup job||Check server log and contact support if necessary.|
|Exception text and Count||The text of the exception, and how often the exception occurred, is contained in the message. See the server log and contact support, if necessary.|