No relevant resource is found in the selected language.

This site uses cookies. By continuing to browse the site you are agreeing to our use of cookies. Read our privacy policy>

Reminder

To have a better experience, please upgrade your IE browser.

upgrade

Due to the incorrect format of tnsnames.ora, LAS failed to start.

Publication Date:  2012-07-25 Views:  109 Downloads:  0
Issue Description
Operator C in country R adopted MBCU+DCCU solution for N2510. After MBCU installation completed, we installed DCCU according to product manual, but when we tried to start LAS, following wrong messages prompted:
[ /opt/n2510/bin ]./startlas.sh 
kernel.core_pattern = /opt/n2510/var/logs/core.%e.%p
starting LAS ....
---------------------------------------------------------------
LasAgentDm is running! Not need to start!!
nohup: appending output to `nohup.out'
Starting LasGuardDm ..... failure !!
Starting LasPerfTaskScheduleDm ..... failure !!
Starting LasExpertDm ..... failure !!
Starting LasSbiframeDm ..... failure !!
Starting LasTrapreceiverDm ..... failure !!
Starting LasSbiAdapterDm ..... failure !!
Starting LasNWAnalyseDataCopyDm ..... failure !!
---------------------------------------------------------------
Done.  Press Enter to continue...
The version of OS, DB and N2510 are listed as following:
1.Suse Linux 10 SP1
2.Oracle 11g
3.N2510 V200R002C00
Alarm Information
None
Handling Process
1.Firstly, we checked the installation manual very carefully. We concluded that the installation operations were correct after confirmed with R&D and HQ speciallist.
2.Secondly, we tried to reinstall the DCCU, however, the problem still existed after reinstallation completed.
3.Based on prevoius two steps, we suspected the reason to this problem might be that LAS failed to connect to DB.
4.We checked the running status of DB, it worked normally.
5.We compared the normal DCCU with this abnormal DCCU, and we found that there was a little difference between them, which was that the format of file tnsnames.ora were different.
6.We changed the format of tnsnames.ora on abnormal DCCU and kept it the same as normal one, after that LAS started successfully.
How could such mistake come out? we replayed the whole installation procedure, for normal DCCU, during the installation, we copied the content of tnsnames.ora from installation manual directly and it kept the format as in manual, but for abnormal DCCU, we copied the content firstly to notepad then to DCCU, which lost the format. Then, problem happened. 
Please refer to the attachment for correct and incorrect formats.
Root Cause
The possible reasons to this problem are:
1.Wrong operations during the installation of DCCU.
2.LAS couldn't connect to DB.
Suggestions
None

END