CA Tuesday Tip: APM Database: Owner's Manual - Upgrades and Migrations
This month's Tip continues to explore the APM database lifecycle by looking at upgrades and migrations. Future months will include database optimization and administration.
An upgrade or migration offers a chance to revisit existing choices and expand existing capabilities. This could include any and all of the following decision points:
Some guidelines in this process include the following:
A successful planning process means a healthy database migration/upgrade. The following should be done during the actual install of software
- Before installing, make sure that you have:
* the needed values for the input items requested during the database installation.
* met all the upgrade pre-reqs (such as having enough disk/table space/memory etc.)
* a successful backup, config export, and business transaction export.
* Use an account with correct permissions to install.
- During/After the software install:
* Check the install and schematools.log
* Check that the permissions and account of database files are correct
* See if you can connect to the database via the appropriate tool.
* See if data is showing up in APM CE GUI.
* Verify that the database is doing aggregation correctly after an upgrade. Otherwise, aggregation issues may lie undetected for weeks or months. I previously distributed a tech note on this topic..
* Review Collector and APM database logs to see if database is logging any errors such as connection
Issues. This will eliminate future issues.
* Review APM Database Supportability metrics/tessperflog to see if the APM database is performing as expected.
* Review the triage map in the APM Investigator to see that all is working as expected
- One area of confusion is doing a Postgres upgrade manually. The basic steps to follow are:
* Drop the database - drops all the tables in the database and deletes the database
* Create the database - Creates the APM CE database
* Create the schema - Creates the schema, tables, etc in the new database.
Questions for Discussion:
1) What best practices have worked for you in terms of APM database and upgrades.
2) What would you like to see changed in APM database upgrades?
3) What other database topics would you like to be covered in Tuesday Tips?
Thank you Hal for another comprehensive Tech Tip!