Run the following SQL to determine the time it failed at
select
value
from
_SYS_STATISTICS.STATISTICS_PROPERTIES
where key = ‘internal.installation.state’
This will return the time that the switch failed at
Check the indexserver and nameserver trace file for an error at this particular time
The following are the most common reasons why the migration will fail
Example 1
NAMESERVER
INDEXSERVER
There are several known errors related to the switching to the migrated statistic server
In the above example if you do a note search for
“exception 9002001: SQL error 129”
It will return the required note which in this case is
2036630 – statisticsserver migration fails with ‘error installing’/ ‘SQL error 129’
EXAMPLE 2
Indexserver.trc
Nameserver.trc
In the above example if you do a note search for
“ exception 9002002: Duplicate catalog object”
It will return the required note which in this case is
2006652 – SAP HANA Statistics Server – Switch to Embedded Statistics Service fails
Example 3
if the parameter nameserver.ini [statisticsserver] active = true was revert back to “false” automatically and the migration failed
Then the note you need to refer to is
It’s always nice to see experiences with the software to be published.
But this blog can and should be re-worked.
The first link URL to the SAP note goes to a SAP internal server – nobody outside the SAP network can access it.
Also the blog is posted in your personal blog list and not at all tagged to belong to SAP HANA. That’s a good way to avoid people reading it. Either posting it directly in the SAP HANA and In-Memory Computing space or at least adding the ‘hana’ tag would help with that.
Finally, this blog doesn’t contain a personal insight, opinion or specific experience. Therefore, the content would be better suited for a document or a WIKI page. (see e.g. Troubleshooting SAP HANA High CPU Utilisation as an example).