progress安装...

河边星星

PROGRESS Version 9.1D08 as of Tue Jan 20 11:59:26 EST 2004
Incorrectly built binary which accesses errno or h_errno directly. Needs to be fixed.
14:51:35 BROKER  0: Last open date mismatch. (9215)
14:51:35 BROKER  0: Extent /dbs/v9db/admapsh.d1 has a different last opened date Sat Mar 26 12:14:18 2005, (9213)
14:51:35 BROKER  0: Control Area has a last open date of Mon Mar 28 13:45:54 2005. (9217)
14:51:35 BROKER  0: Probable backup/restore error. (605)
14:51:35 BROKER  0: Database is damaged, see documentation. (1486)
14:51:35 BROKER   : Removed shared memory with segment_id: 2654208
14:51:35 BROKER   : Removed shared memory with segment_id: 2686977
14:51:35 BROKER   : ** This process terminated with exit code 2. (8619)


抱歉转移后有点问题....可能是-u的关系...
我现在正在不要用-u 去同步移目录..

河边星星

夸自己一下.....

真的是这样的,兄弟今后移植的数据库的时候要注意了...
用rsync 时请不要用-u

公司ERP dbserver移植成功.................恭喜......哈哈哈..............

河边星星

91D09-linux-178_101089.tar

已有可以安裝了成功了.

河边星星

即可实现每一客户机同时只能连接1个ERP.

1. #!/bin/sh
   
2. sh /sbin/service iptables stop
   
3. sh /sbin/service iptables start
   
4. netstat | grep ESTABLISHED | cut -d ":" -f2 | cut -d " " -f2|sort|uniq -c |cut -d " " -f6,7,8|sort|cut -d " " -f1,2|sort |uniq -c |cut -d " " -f9|sed -n -e '/[:alpha:]/p'|cut -d "." -f1 > /tmp/erpnot1
   
5. echo "peter" > /tmp/allowerp2
   
6. echo "erpserver" >> /tmp/allowerp2
   
7. echo "erp0" >> /tmp/allowerp2
   
8. echo "erp7" >> /tmp/allowerp2
   
9. 
   
10. # diff /tmp/allowerp2 /tmp/erpnot1 | tail +2| cut -d " " -f2 > /tmp/dropuser
    
11. 
    
12. cat /tmp/erpnot1 | while read kuser
    
13. do
    
14.         echo 0 > /tmp/kyn
    
15.                 cat /tmp/allowerp2 | while read allowuser
    
16.                         do
    
17.                         if [ "$kuser" == "$allowuser" ] ; then
    
18.                         echo 1 > /tmp/kyn
    
19.                         fi
    
20.                         done
    
21.                 cat /tmp/kyn | while read killyn
    
22.                         do
    
23.                         if [ "$killyn" == "0" ]; then
    
24.                  /sbin/iptables -t nat -A OUTPUT -d $kuser -j DROP
    
25.                  /sbin/iptables -t nat -A POSTROUTING -s $kuser -j DROP
    
26.                  /sbin/iptables -t nat -A PREROUTING -s $kuser -j DROP
    
27.                         fi
    
28.                         done
    
29. done
    

复制代码

雖然腳本很差勁,
但是根据我们的数据库有5个,
客户端通过程式server连接到erp db server
因为程式server是windows
所以以上脚本在linux下即可.
每一个用户登录后正常与db server有五个established
如果超过10个即在使用多个erp
放到crontab -e中
*/5 7-17 * * 1-5 /etc/rl.sh

即可实现每一客户机同时只能连接1个ERP.
因为ERP买授权少啊,没办法

以上为抛砖引玉,如有更好方法就好了.谁叫我不熟悉progress呢?

河边星星

一般一台電腦dbserver如作為ERP的dbserver
如公司是五個庫為一套ERP所用,也就是一個公司可以有多套ERP同時運行,
如有一個測試版,一個正式版.
在progress是如何實現的呢/

其中也就是不同的資料庫,不同的連接端口,
但是實際中我們往往直接將以往的正試版的複製後當今後的測試版用.
如下是progress 關於exsh這一套ERP的資料庫文件

admexsh.b1  admexsh.db   disexsh.d3        finexsh.b1  finexsh.db   humexsh.d3   mfgexsh.b4   mfgexsh.d8
admexsh.b2  admexsh.lg   disexsh.d4        finexsh.b2  finexsh.lg   humexsh.d4   mfgexsh.d1   mfgexsh.d9
admexsh.b3  admexsh.lic  disexsh.d5        finexsh.b3  finexsh.lic  humexsh.db   mfgexsh.d10  mfgexsh.db
admexsh.b4  admexsh.lk   disexsh.d6        finexsh.b4  finexsh.lk   humexsh.lg   mfgexsh.d11  mfgexsh.lg
admexsh.d1  disexsh.b1   disexsh.db        finexsh.d1  finexsh.srt  humexsh.lic  mfgexsh.d2   mfgexsh.lic
admexsh.d2  disexsh.b2   disexsh.lg        finexsh.d2  humexsh.b1   humexsh.lk   mfgexsh.d3   mfgexsh.lk
admexsh.d3  disexsh.b3   disexsh.lic       finexsh.d3  humexsh.b2   humexsh.srt  mfgexsh.d4   mfgexsh.srt
admexsh.d4  disexsh.b4   disexsh.lk        finexsh.d4  humexsh.b3   mfgexsh.b1   mfgexsh.d5
admexsh.d5  disexsh.d1   disexsh.srt       finexsh.d5  humexsh.d1   mfgexsh.b2   mfgexsh.d6
admexsh.d6  disexsh.d2     finexsh.d6  humexsh.d2   mfgexsh.b3   mfgexsh.d7

備註:其中副檔名為d數字,以及b數位的都是資料庫文件
.lg為日志文件如
14:03:47 BROKER  0: Service Name (-S): db131sv. (4262)
14:03:47 BROKER  0: Network Type (-N): tcp. (4263)
14:03:47 BROKER  0: Character Set (-cpinternal): cp950. (4264)
14:03:47 BROKER  0: Parameter File: Not Enabled. (4282)
14:03:47 BROKER  0: Maximum Servers Per Broker (-Mpb): 16. (5647)
14:03:47 BROKER  0: Minimum Port for Auto Servers (-minport): 1025. (5648)
14:03:47 BROKER  0: Maximum Port for Auto Servers (-maxport): 2000. (5649)
14:03:47 BROKER  0: This broker supports both 4GL and SQL server groups. (8865)
14:03:47 BROKER  0: SQL Server Stack Size (-SQLStack): 1000. (10026)
14:03:47 BROKER  0: SQL Server Statement Cache Size (-SQLStmtCache): 100. (10027)
14:03:47 BROKER  0: SQL Server Max Open Cursors (-SQLCursors): 50. (10028)
14:03:47 BROKER  0: Created shared memory with segment_id: 7176207 (9336)
14:03:54 SRV     2: Started on port 1190 using tcp, pid 31298. (5646)

tail admexsh.lic
06/10/08  09:00:00  10 2 2 2 2 2 2 0 0 0
06/10/08  10:00:00  10 2 2 2 2 2 2 0 0 0
06/10/08  11:00:00  10 2 2 2 2 2 2 0 0 0
06/10/08  12:00:00  10 2 2 2 2 2 2 0 0 0
06/10/08  13:00:00  10 2 2 2 2 2 2 0 0 0
06/10/08  14:00:00  10 2 2 2 2 2 2 0 0 0
06/10/08  15:00:00  10 2 2 2 2 2 2 0 0 0
06/10/08  16:00:00  10 2 2 2 2 2 2 0 0 0
06/10/08  17:00:00  10 2 2 2 2 2 2 0 0 0


比較不容易引起注意的而正是.lk文件
它是資料庫啟動時所産生,所以當你由不同的主機這樣去複製的資料庫的時候要注意
將.lk文件刪除

至於多套ERP的資料庫的啟動參考以上貼子.

感謝版主的加精,有空繼續補充.

河边星星

因为ERP更换主机，主机的配置高很多，
因为progress公司有版权的并不是很高
可是旧的操作系统对新的主机支持又不是很好

如华硕p5wd2的主板安装mandrike 10.0就是不认硬盘（它有四个SATA＋2个IDE口）
原来我们是用复制替代vmlinuz来做测试版的，不过有其隐患 如一些iptables这些kernel内部的程式会有问题。

所以现在我们正常安装操作系统然后

废话少说：先把原主机上的progress停止
scp /etc/services root@newhost:/etc/

scp -rp /usr/dlc91d root@newhost:/usr/dlc91d

scp -rp /dbs/v9db root@newhost:/dbs/v9db

scp -rp /usr/java/ root@newhost:/usr/java
结果虽正常

（但ERP涉及信息比较多，数据最重要，不可冒然使用，如果各位操作后所带来的一切后果本人概不负责）


[root@xxx1 java]# cat /proc/version
Linux version 2.6.17-5mdv (rtp@octopus.mandriva.com) (gcc version 4.1.1 20060724 (prerelease) (4.1.1-3mdk)) #1 SMP Wed Sep 13 14:32:31 EDT 2006

[root@xxx1 java]# cat /usr/dlc91d/version
PROGRESS Version 9.1D09 as of Tue May 25 05:35:09 EDT 2004


  
[root@xxx1 ~]# /dbs/v9db/v9dbup.APSH
PROGRESS Version 9.1D09 as of Tue May 25 05:35:09 EDT 2004
15:19:53 BROKER  0: Multi-user session begin. (333)
15:19:53 BROKER  0: Begin Physical Redo Phase at 1024 . (5326)
15:19:55 BROKER  0: Physical Redo Phase Completed at blk 288 off 16066 upd 0. (7161)
15:19:55 BROKER  0: Started for db151sv using tcp, pid 24547. (5644)
PROGRESS Version 9.1D09 as of Tue May 25 05:35:09 EDT 2004
15:19:55 BROKER  1: Started for db51sv using tcp, pid 24584. (5644)
15:19:55 BROKER  1: This is an additional broker for this protocol. (5645)
15:19:55 BROKER  1: This broker supports both 4GL and SQL server groups. (8865)
PROGRESS Version 9.1D09 as of Tue May 25 05:35:09 EDT 2004
15:19:56 BROKER  0: Multi-user session begin. (333)
15:19:56 BROKER  0: Begin Physical Redo Phase at 768 . (5326)
15:20:08 BROKER  0: Physical Redo Phase Completed at blk 133 off 2963 upd 32977. (7161)
15:20:08 BROKER  0: Started for db152sv using tcp, pid 24597. (5644)
PROGRESS Version 9.1D09 as of Tue May 25 05:35:09 EDT 2004
15:20:09 BROKER  1: Started for db52sv using tcp, pid 24769. (5644)
15:20:09 BROKER  1: This is an additional broker for this protocol. (5645)
15:20:09 BROKER  1: This broker supports both 4GL and SQL server groups. (8865)
PROGRESS Version 9.1D09 as of Tue May 25 05:35:09 EDT 2004
15:20:09 BROKER  0: Multi-user session begin. (333)
15:20:09 BROKER  0: Begin Physical Redo Phase at 0 . (5326)
15:20:20 BROKER  0: Physical Redo Phase Completed at blk 455 off 228 upd 31745. (7161)
15:20:21 BROKER  0: Started for db153sv using tcp, pid 24780. (5644)
PROGRESS Version 9.1D09 as of Tue May 25 05:35:09 EDT 2004
15:20:21 BROKER  1: Started for db53sv using tcp, pid 24864. (5644)
15:20:21 BROKER  1: This is an additional broker for this protocol. (5645)
15:20:21 BROKER  1: This broker supports both 4GL and SQL server groups. (8865)
PROGRESS Version 9.1D09 as of Tue May 25 05:35:09 EDT 2004
15:20:23 BROKER  0: The last backup was not completed successfully. (1553)
15:20:23 BROKER  0: Multi-user session begin. (333)
15:20:25 BROKER  0: Begin Physical Redo Phase at 14592 . (5326)
15:20:34 BROKER  0: Physical Redo Phase Completed at blk 15006 off 10997 upd 770. (7161)
15:20:36 BROKER  0: Started for db154sv using tcp, pid 24873. (5644)
PROGRESS Version 9.1D09 as of Tue May 25 05:35:09 EDT 2004
15:20:36 BROKER  1: Started for db54sv using tcp, pid 24914. (5644)
15:20:36 BROKER  1: This is an additional broker for this protocol. (5645)
15:20:36 BROKER  1: This broker supports both 4GL and SQL server groups. (8865)
PROGRESS Version 9.1D09 as of Tue May 25 05:35:09 EDT 2004
15:20:37 BROKER  0: Multi-user session begin. (333)
15:20:37 BROKER  0: Begin Physical Redo Phase at 0 . (5326)
15:20:38 BROKER  0: Physical Redo Phase Completed at blk 8 off 761 upd 0. (7161)
15:20:38 BROKER  0: Started for db155sv using tcp, pid 24924. (5644)
PROGRESS Version 9.1D09 as of Tue May 25 05:35:09 EDT 2004
15:20:38 BROKER  1: Started for db55sv using tcp, pid 24935. (5644)
15:20:38 BROKER  1: This is an additional broker for this protocol. (5645)
15:20:38 BROKER  1: This broker supports both 4GL and SQL server groups. (8865)


odbc测试通过，ERP使用正常。