You have not stated which type of data source you are referring to as in certain cases (SRDF especially) the fact that you are on the secondary node and the data source is in warning would be expected.
Also, would be an idea to state which OS version the cluster is on and what other changes you have during the upgrade from 5.2 to 5.2Sp2.
Have you checked through the data source logs on the two nodes... To make things easier with the logs, I would suggest that you record the time when you attempt to bring the data source online , wait for it to enter the warning state and then investigate the logs. There are two logs to look at on each node and these can be found in FT_DIR\domain name\log - and FT_DIR\domain name\log\data_source_types
IKP1
198 Posts
1
May 21st, 2007 02:00
You have not stated which type of data source you are referring to as in certain cases (SRDF especially) the fact that you are on the secondary node and the data source is in warning would be expected.
Also, would be an idea to state which OS version the cluster is on and what other changes you have during the upgrade from 5.2 to 5.2Sp2.
Have you checked through the data source logs on the two nodes... To make things easier with the logs, I would suggest that you record the time when you attempt to bring the data source online , wait for it to enter the warning state and then investigate the logs.
There are two logs to look at on each node and these can be found in FT_DIR\domain name\log - and FT_DIR\domain name\log\data_source_types
IKP
amediratta
2 Intern
•
2K Posts
0
May 21st, 2007 11:00
Anyway we have resolved it by doing the mirroring again.
Thanks for your response.