XI 3.1 Instalation stops at 55%
来源:互联网 发布:菜鸟程序员 编辑:程序博客网 时间:2024/05/29 18:53
1. Recently, encounter one problem when installing XI 3.1, and google it, found the cause in
http://www.forumtopics.com/busobj/viewtopic.php?t=145857&postdays=0&postorder=asc&start=0
it is caused by the PRE_LOAD environment variable.
"Hi
I was planning to put an update on the message when I had something to report. Well, I finally have.
BO Support informed me that BO XI didn't work work if there were more than 64 cores on the server. That's fine, my server has two cpu's each with six cores. Each core is running 8 threads.
If you run psrinfo -p, it does indeed report two cpu's. However, psrinfo alone reports 96 cpu's (2x6x8). It seems Solaris treats every thread as a cpu.
I asked my hardware engineer to disable some of the threads at the system level. He reduced the number to 58.
I re-ran the install and it worked.
Now, having worked out what the problem is a quick google provides a further option of preventing libhoard from loading by commenting out the environment variable LD_PRELOAD="libhoard.so.1" and the subsequent export from env.sh in the bobje/setup folder.
Now, I've tried restarting the cms at this point but for me it didin't work. What I was forced to do was amend env.sh during the installation process itself. This also required changing attributes to make it writeable before the changes take affect. Doing it this way for me meant that the installation completed successfully which meant all I had to do was load up the BIAR file and bingo - a working application. I've done this in a test folder on my server - I have yet to deploy it properly in production.
What I did was built a single cpu/single core server just to be able to provide some kind off live service in the interim.
Although not a monster, the production server has much more grunt. Deployment is planned for this commong weekend (08/03/10). I'll post another update after the deployment if there's anything to add.
Garry Hewett"
checked the /var/adm/messages file, find the following error info.
2. what is hoard?
The Hoard memory allocator is a fast, scalable, and memory-efficient memory allocator. It runs on a variety of platforms, including Linux, Solaris, and Windows. Hoard is a drop-in replacement for malloc() that can dramatically improve application performance, especially for multithreaded programs running on multiprocessors. No change to your source is necessary. Just link it in or set just one environment variable
see http://www.hoard.org/
- XI 3.1 Instalation stops at 55%
- xi
- XI
- xi
- xi
- Fuel Stops
- ESX4.0 host boot stops at the error: VSD mount/Bin/SH:cant access TTY job control turned off
- Studies not stops(学无止尽)
- Cognos Schedule stops working
- XI一些
- SAP XI
- XI笔记
- SAP XI
- BO啊BO,Integrating SAP® BusinessObjects XI 3.1真贵
- The Brick Stops Here dp 01背包
- Hoj 1488 The Brick Stops Here
- Automake stops with “non-POSIX variable name”
- HBase master stops with “Connetion Refused” Error
- SICP section 2.2
- camera相关知识
- 常用的一些算法
- 用mmap写Linux用户空间驱动
- C++ 明智地使用多继承
- XI 3.1 Instalation stops at 55%
- 无奈
- 向着第二层 第一阶段第一天
- 两个文本框内容交换(js收藏1)
- cstring变量与atlsimpstr.h 的异常【创+转】
- TimerTask demo
- 让Libevent 在window下 支持 IOCP
- 动态存储变量和静态存储变量
- 用JAVA,删除文件中前100个字节的内容