We added -t parameter to arserverd in the armonitor.conf file and got arsystem startup log file. By looking at the log file, we found out that arserverd took about one hour to get some data dictionary tables such as field_dispprop. It eventually completed startup process but took about ONE hour and 40 minutes
We then checked the network configuration again on the database server (initially the sys admin told us it's properly set) and turn out NIC was set up with the wrong configuration i.e. 100 MB when it should have been running at Gigabit speed. Once the NIC was changed to Gigabit speed, the startup process took only 4 minutes. Thnaks, Eric _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org ARSlist:"Where the Answers Are"
