8 Replies Latest reply: Jun 18, 2012 2:14 AM by 943454 RSS

    TUXEDO11 in MP mode can't boot TMS_ORA on the non-master node

    943454
      I have my Tuxedo 11 installed on Ubuntu9.10 server as the master node (SITE1) and on CentOS6.2 as the non-master node (SITE2). The client program is using WSL to communicate with the servers. Tuxedo 11 has no patch, and both Tuxedo11 and Oracle10gR2 are 32 bits running on 32 bits OS.

      On both node a TMS_ORA associated with an ORACLE 10gR2 database was installed. When I issue "tmboot -y", the servers on the master node booted normally, however, the TMS_ORA server and server that using TMS_ORA on SITE2 reported "Assume started (pipe). ". There is no core file for these servers on SITE2 and in ULOG on SITE2 there is no Error or Warning concerning the failure starting of TMS_ORA.

      In order to check my servers and TMS_ORA works OK on SITE2, I used the master command under tmadmin to first swap the master and non-master node, and after the migration is successful, on SITE2 I issued "tmshutdown -cy" command then "tmboot -y" command. Surprisingly, all the servers booted correctly on both nodes. Then I migrate the master node back to SITE1 and the servers are still there alive and my client program can successfully call these servers which means the TMS_ORA and server using TMS_ORA on both nodes works fine.

      The problem is, when I "tmshutdown -s server" (those on SITE2, either TMS_ORA or server using TMS_ORA), then using "tmboot -s server" to boot them (those on SITE2, either TMS_ORA or server using TMS_ORA) I got "Assume started (pipe). " reported and those server process didn't appear on SITE2.

      It seems that I can't boot TMS_ORA on SITE2 from the master node SITE1 but can boot all the servers correctly if SITE2 are acting as the master node. Server that don't use TMS_ORA on SITE2 can be booted successfully from SITE1.

      Can anybody figure out what's wrong? Thanks in advance.

      Best regards,

      Orlando

      Edited by: user10950876 on 2012-6-13 下午3:02

      Edited by: user10950876 on 2012-6-13 下午3:33
        • 1. Re: TUXEDO11 in MP mode can't boot TMS_ORA on the non-master node
          Todd Little-Oracle
          Hi,

          Does the BRIDGE and BBL get started successfully on the non-Master machine? Is tlisten running on the non-Master machine? Can you post the relevant portions of the master and non-master ULOG files?

          Regards,
          Todd Little
          Oracle Tuxedo Chief Architect
          • 2. Re: TUXEDO11 in MP mode can't boot TMS_ORA on the non-master node
            943454
            Hi Todd,

            Thank you for you reply. Following is my ULOG and tmboot report:

            ubuntu9:~/tuxapp$tmboot -y
            Booting all admin and server processes in /home/xp/tuxapp/tuxconfig
            INFO: Oracle Tuxedo, Version 11.1.1.2.0, 32-bit, Patch Level (none)

            Booting admin processes ...

            exec DBBL -A :
            on SITE1 -> process id=8803 ... Started.
            exec BBL -A :
            on SITE1 -> process id=8804 ... Started.
            exec BBL -A :
            on SITE2 -> process id=3964 ... Started.

            Booting server processes ...

            exec TMS_ORA -A :
            on SITE1 -> process id=8812 ... Started.
            exec TMS_ORA -A :
            on SITE1 -> process id=8838 ... Started.
            exec TMS_ORA2 -A :
            on SITE2 -> CMDTUX_CAT:819: INFO: Process id=3967 Assume started (pipe).
            exec TMS_ORA2 -A :
            on SITE2 -> CMDTUX_CAT:819: INFO: Process id=3968 Assume started (pipe).
            exec WSL -A -- -n //128.0.88.24:5000 -m 3 -M 5 -x 5 :
            on SITE1 -> process id=8841 ... Started.
            8 processes started.

            ********************************************************************************************
            ULOG on ubuntu9

            134547.ubuntu9!DBBL.8803.3071841984.0: 06-14-2012: client high water (0), total client (0)
            134547.ubuntu9!DBBL.8803.3071841984.0: 06-14-2012: Tuxedo Version 11.1.1.2.0, 32-bit
            134547.ubuntu9!DBBL.8803.3071841984.0: LIBTUX_CAT:262: INFO: Standard main starting
            134549.ubuntu9!DBBL.8803.3071841984.0: CMDTUX_CAT:4350: INFO: BBL started on SITE1 - Release 11112
            134550.ubuntu9!BBL.8804.3072861888.0: 06-14-2012: Tuxedo Version 11.1.1.2.0, 32-bit, Patch Level (none)
            134550.ubuntu9!BBL.8804.3072861888.0: LIBTUX_CAT:262: INFO: Standard main starting
            134550.ubuntu9!BRIDGE.8806.3072931520.0: 06-14-2012: Tuxedo Version 11.1.1.2.0, 32-bit
            134550.ubuntu9!BRIDGE.8806.3072931520.0: LIBTUX_CAT:262: INFO: Standard main starting
            134555.ubuntu9!DBBL.8803.3071841984.0: CMDTUX_CAT:4350: INFO: BBL started on SITE2 - Release 11112
            134556.ubuntu9!BRIDGE.8806.3072931520.0: CMDTUX_CAT:1371: INFO: Connection received from redhat62
            134557.ubuntu9!TMS_ORA.8812.3057321664.0: 06-14-2012: Tuxedo Version 11.1.1.2.0, 32-bit
            134557.ubuntu9!TMS_ORA.8812.3057321664.0: LIBTUX_CAT:262: INFO: Standard main starting
            134559.ubuntu9!TMS_ORA.8838.3056805568.0: 06-14-2012: Tuxedo Version 11.1.1.2.0, 32-bit
            134559.ubuntu9!TMS_ORA.8838.3056805568.0: LIBTUX_CAT:262: INFO: Standard main starting
            134559.ubuntu9!WSL.8841.3072153920.0: 06-14-2012: Tuxedo Version 11.1.1.2.0, 32-bit
            134559.ubuntu9!WSL.8841.3072153920.0: LIBTUX_CAT:262: INFO: Standard main starting
            134559.ubuntu9!WSH.8842.3072411328.0: 06-14-2012: Tuxedo Version 11.1.1.2.0, 32-bit
            134559.ubuntu9!WSH.8842.3072411328.0: WSNAT_CAT:1030: INFO: Work Station Handler joining application
            134559.ubuntu9!WSH.8843.3073169088.0: 06-14-2012: Tuxedo Version 11.1.1.2.0, 32-bit
            134559.ubuntu9!WSH.8843.3073169088.0: WSNAT_CAT:1030: INFO: Work Station Handler joining application
            134559.ubuntu9!WSH.8844.3073066688.0: 06-14-2012: Tuxedo Version 11.1.1.2.0, 32-bit
            134559.ubuntu9!WSH.8844.3073066688.0: WSNAT_CAT:1030: INFO: Work Station Handler joining application
            **********************************************************************************************************
            ULOG on redhat62

            134615.redhat62!tmloadcf.3961.3078567616.-2: 06-14-2012: client high water (0), total client (0)
            134615.redhat62!tmloadcf.3961.3078567616.-2: 06-14-2012: Tuxedo Version 11.1.1.2.0, 32-bit
            134615.redhat62!tmloadcf.3961.3078567616.-2: CMDTUX_CAT:872: INFO: TUXCONFIG file /home/tuxedo/tuxedo/simpapp/tuxconfig has been updated
            134617.redhat62!BSBRIDGE.3963.3078089312.0: 06-14-2012: Tuxedo Version 11.1.1.2.0, 32-bit
            134617.redhat62!BSBRIDGE.3963.3078089312.0: LIBTUX_CAT:262: INFO: Standard main starting
            134619.redhat62!BBL.3964.3079420512.0: 06-14-2012: Tuxedo Version 11.1.1.2.0, 32-bit, Patch Level (none)
            134619.redhat62!BBL.3964.3079420512.0: LIBTUX_CAT:262: INFO: Standard main starting
            134620.redhat62!BRIDGE.3965.3077868128.0: 06-14-2012: Tuxedo Version 11.1.1.2.0, 32-bit
            134620.redhat62!BRIDGE.3965.3077868128.0: LIBTUX_CAT:262: INFO: Standard main starting
            134620.redhat62!BRIDGE.3965.3077868128.0: CMDTUX_CAT:4488: INFO: Connecting to ubuntu9 at //128.0.88.24:1800
            ************************************************************************************************************
            ubb file content: (just in case you want to see it too. I've commented all the services in the ubb file, except the TMS_ORA2 on SITE2 to make it more distinct.)

            *RESOURCES
            IPCKEY 123456
            DOMAINID TUXTEST
            MASTER SITE1, SITE2
            MAXACCESSERS 50
            MAXSERVERS 35
            MAXCONV 10
            MAXGTT 20
            MAXSERVICES 70
            OPTIONS LAN, MIGRATE
            MODEL MP
            LDBAL Y

            *MACHINES
            DEFAULT: MAXWSCLIENTS=30

            ubuntu9 LMID=SITE1
            APPDIR="/home/xp/tuxapp"
            TUXCONFIG="/home/xp/tuxapp/tuxconfig"
            TUXDIR="/home/xp/tuxedo11gR1"
            TLOGDEVICE="/home/xp/tuxapp/TLOG"
            TLOGNAME="TLOG"
            TLOGSIZE=100
            TYPE=Linux
            ULOGPFX="/home/xp/tuxapp/ULOG"
            ENVFILE="/home/xp/tuxapp/ENVFILE"
            UID=1000
            GID=1000

            redhat62 LMID=SITE2
            TUXDIR="/usr/oracle/tuxedo11gR1"
            APPDIR="/home/tuxedo/tuxedo/simpapp"
            TLOGDEVICE="/home/tuxedo/tuxedo/simpapp/TLOG"
            TLOGNAME="TLOG"
            TUXCONFIG="/home/tuxedo/tuxedo/simpapp/tuxconfig"
            TYPE=Linux
            ULOGPFX="/home/tuxedo/tuxedo/simpapp/ULOG"
            ENVFILE="/home/tuxedo/tuxedo/simpapp/ENVFILE"
            UID=501
            GID=501

            *GROUPS
            BANK1
            LMID=SITE1 GRPNO=1 TMSNAME=TMS_ORA TMSCOUNT=2
            OPENINFO="Oracle_XA:Oracle_XA+Acc=P/scott/tiger+SesTm=120+MaxCur=5+LogDir=.+SqlNet=xpdev"
            CLOSEINFO="NONE"

            BANK2
            LMID=SITE2 GRPNO=2 TMSNAME=TMS_ORA2 TMSCOUNT=2
            OPENINFO="Oracle_XA:Oracle_XA+Acc=P/scott/scott+SesTm=120+MaxCur=5+LogDir=.+SqlNet=tuxdev"
            CLOSEINFO="NONE"

            WSGRP
            LMID=SITE1 GRPNO=3
            OPENINFO=NONE

            *NETGROUPS
            DEFAULTNET NETGRPNO=0 NETPRIO=100
            SITE1_SITE2 NETGRPNO=1 NETPRIO=200

            *NETWORK
            SITE1 NETGROUP=DEFAULTNET
            NADDR="//128.0.88.24:1800"
            NLSADDR="//128.0.88.24:1500"

            SITE2 NETGROUP=DEFAULTNET
            NADDR="//128.0.88.215:1800"
            NLSADDR="//128.0.88.215:1500"

            *SERVERS
            DEFAULT:
            CLOPT="-A"

            #XFER SRVGRP=BANK1 SRVID=1
            #TLR_ORA SRVGRP=BANK1 SRVID=2
            #TLR_ORA2 SRVGRP=BANK2 SRVID=3
            WSL SRVGRP=WSGRP SRVID=4
            CLOPT="-A -- -n //128.0.88.24:5000 -m 3 -M 5 -x 5"

            *SERVICES
            #INQUIRY
            #WITHDRAW
            #DEPOSIT
            #XFER_NOXA
            #XFER_XA

            Edited by: user10950876 on 2012-6-13 下午10:58
            • 3. Re: TUXEDO11 in MP mode can't boot TMS_ORA on the non-master node
              Todd Little-Oracle
              Hi,

              What's the difference between TMS_ORA and TMS_ORA2? Also are the contents of the RM file the same on the two systems? How about the tnsnames.ora files? And is the password for the database really different on the RedHat machine? Do you find any .trc files (database log files) that might share some insight into what is happening?

              Regards,
              Todd Little
              Oracle Tuxedo Chief Architect
              • 4. Re: TUXEDO11 in MP mode can't boot TMS_ORA on the non-master node
                943454
                Hi, Todd,
                1. There is no difference between TMS_ORA and TMS_ORA2. I just name them like that so that I can see which TMS_ORA is which. (TMS_ORA on master node and TMS_ORA2 on SITE2)

                2. The content of RM on both machines should be the same, since I installed TUXEDO11 on both of them using the same install package.
                # Oracle 9, 10
                Oracle_XA:xaosw:-L${ORACLE_HOME}/lib -lclntsh

                3. tnsnames.ora files are like following:

                tnsnames.ora on Ubuntu9.10 server (SITE1, Master Node)

                XPDEV =
                (DESCRIPTION =
                (ADDRESS = (PROTOCOL = TCP)(HOST = ubuntu9)(POST =1521))
                (CONNECT_DATA =
                (SERVER = DEDICATED)
                (SERVICE_NAME = xpdev)
                )
                )

                EXTPROC_CONNECTION_DATA =
                (DESCRIPTION =
                (ADDRESS_LIST =
                (ADDRESS = (PROTOCOL = IPC)(KEY = EXTPROC1))
                )
                (CONNECT_DATA =
                (SID = PLSExtProc)
                (PRESENTATION = RO)
                )
                )
                **********************************************************************
                tnsnames.ora on Redhat6.2 (SITE2)

                TUXDEV =
                (DESCRIPTION =
                (ADDRESS = (PROTOCOL = TCP)(HOST = localhost)(PORT = 1521))
                (CONNECT_DATA =
                (SERVER = DEDICATED)
                (SERVICE_NAME = tuxdev)
                )
                )

                EXTPROC_CONNECTION_DATA =
                (DESCRIPTION =
                (ADDRESS_LIST =
                (ADDRESS = (PROTOCOL = IPC)(KEY = EXTPROC1))
                )
                (CONNECT_DATA =
                (SID = PLSExtProc)
                (PRESENTATION = RO)
                )
                )
                *****************************************************************
                4. Yes. Password for the two Databases are different. For database on SITE1, master node, it's scott/tiger, and for database on SITE2, it's scott/scott. I've tested them using TUXEDO users by issuing sqlplus command and can login databases correctly on each machine.

                5. There is no *.trc files under the $TUXAPP folder.

                First, I'm not sure if the UID and GID in ubb file is used only for TUXEDO administration. My TUXEDO user has supplementary GID of oinstall to access $ORACLE_HOME, but I don't know how to give GID two values in ubb, would that be a problem?

                Second, when I create TLOG on both machine, only on master node the command "crlog -m SITE1" complete successful, the "crlog -m SITE2" failed. And I saw someone said that there is no need to issue "crlog -m SITE2" command since TUXEDO will do it for you. Is that true?

                Best Regards,

                Orlando
                • 5. Re: TUXEDO11 in MP mode can't boot TMS_ORA on the non-master node
                  Todd Little-Oracle
                  Hi Orlando,

                  The UID and GID are used to define the owner of Tuxedo IPC resources and PERM defines the permissions in standard Unix style. As long as the user booting the system has access as defined by their UID/GID and the value of PERM, there should be no problem.

                  Regarding creating transaction logs, an administrator must create the transaction logs. The only transaction logs Tuxedo creates automatically are the logs used by the domain gateways. I'm fairly certain this is why the TMS process on the backup won't boot.

                  Regards,
                  Todd Little
                  Oracle Tuxedo Chief Architect
                  • 6. Re: TUXEDO11 in MP mode can't boot TMS_ORA on the non-master node
                    943454
                    Hi, Todd,

                    Thank you for your analysis. I'll try to issue "crlog -m SITE2" on the non-master node to see if it solves the problem and report back on Monday.

                    By the way, last time when I tried to issue "crlog -m SITE2" on SITE1, the master node, after issuing tmadmin command, I got something like "failed to create on the remote node". Should I login on the SITE2 machine and issue tmadmin command on SITE2 directly and then issue "crlog -m SITE2" or can I perform the task on the master node? As far as I can remember, I've tried both and both of the ways failed.

                    Following is exactly what I do:
                    1. On SITE1, I entered tmadmin -c then >crdl -z $TUXAPP/TLOG -b 200
                    2. I entered tmadmin, then >crlog -m SITE1
                    Step1 and 2 finished successfully and the TLOG was created on SITE1 and associated with LMID SITE1.

                    3. On SITE2, I entered tmadmin -c then >crdl -z $TUXAPP/TLOG -b 200;
                    Step 3 finished successfully and I got TLOG created on SITE2
                    4. Either on SITE2 or SITE1 I entered tmadmin, then >crlog -m SITE2
                    Step 4 failed. If I remembered correctly, it said that crlog -m SITE2 cannot be performed on a non-master node, and on the master node it probably said that it failed to create TLOG on the remote node.

                    I'm wondering what does command "crlog -m LMID" really do behind. The command do failed on SITE2, but why can I still run all the servers that using TMS_ORA and involving transactions when I migrate from SITE1 to SITE2 and tmshutdown and tmboot all of them on SITE2?

                    Your advise on how to associate the created TLOG with the non-master node and explaination on the weird thing would be appreciated.

                    Best Regards,

                    Orlando
                    • 7. Re: TUXEDO11 in MP mode can't boot TMS_ORA on the non-master node
                      Todd Little-Oracle
                      Hi Orlando,

                      Can you post the exact error messages you are getting from tmadmin?

                      Regards,
                      Todd Little
                      Oracle Tuxedo Chief Architect
                      • 8. Re: TUXEDO11 in MP mode can't boot TMS_ORA on the non-master node
                        943454
                        Hi Todd,

                        Following is what I got after issuing crlog -m SITE2 under tmadmin:
                        *****************************************************************
                        First boot TUXEDO on SITE1, the master node
                        ubuntu9:~$tmboot -y
                        Booting all admin and server processes in /home/xp/tuxapp/tuxconfig
                        INFO: Oracle Tuxedo, Version 11.1.1.2.0, 32-bit, Patch Level (none)

                        Booting admin processes ...

                        exec DBBL -A :
                        on SITE1 -> process id=5529 ... Started.
                        exec BBL -A :
                        on SITE1 -> process id=5530 ... Started.
                        exec BBL -A :
                        on SITE2 -> process id=2689 ... Started.

                        Booting server processes ...

                        exec TMS_ORA -A :
                        on SITE1 -> process id=5532 ... Started.
                        exec TMS_ORA -A :
                        on SITE1 -> process id=5535 ... Started.
                        exec TLR_ORA -A :
                        on SITE1 -> process id=5538 ... Started.
                        exec TMS_ORA2 -A :
                        on SITE2 -> CMDTUX_CAT:819: INFO: Process id=2691 Assume started (pipe).
                        exec TMS_ORA2 -A :
                        on SITE2 -> CMDTUX_CAT:819: INFO: Process id=2692 Assume started (pipe).
                        exec XFER_NOXA -A :
                        on SITE2 -> CMDTUX_CAT:819: INFO: Process id=2693 Assume started (pipe).
                        exec XFER_XA -A :
                        on SITE2 -> CMDTUX_CAT:819: INFO: Process id=2694 Assume started (pipe).
                        exec TLR_ORA2 -A :
                        on SITE2 -> CMDTUX_CAT:819: INFO: Process id=2695 Assume started (pipe).
                        exec WSL -A -- -n //128.0.88.24:5000 -m 3 -M 5 -x 5 :
                        on SITE1 -> process id=5541 ... Started.
                        12 processes started.

                        ***************************************************************************
                        Second try to issue crlog command to create TLOG on SITE1, the master node, and got a failed message:

                        ubuntu9:~$tmadmin
                        tmadmin - Copyright (c) 1996-2010 Oracle.
                        Portions * Copyright 1986-1997 RSA Data Security, Inc.
                        All Rights Reserved.
                        Distributed under license by Oracle.
                        Tuxedo is a registered trademark.
                        crlog -m SITE2
                        TMADMIN_CAT:565: ERROR: remote log creation failed

                        ******************************************************************************
                        Third, I try to issue the crlog command on the non-master node, SITE2, and being told that the crlog can only be issued on master node:
                        [tuxedo@redhat62 simpapp]$ tmadmin
                        tmadmin - Copyright (c) 1996-2010 Oracle.
                        Portions * Copyright 1986-1997 RSA Data Security, Inc.
                        All Rights Reserved.
                        Distributed under license by Oracle.
                        Tuxedo is a registered trademark.
                        crlog -m SITE2
                        TMADMIN_CAT:562: ERROR: Not running on Master

                        *******************************************************************************
                        I tried to migrate from SITE1 to SITE2 to in order to create the TLOG on SITE2:
                        master
                        Are you sure? [y, n] y

                        Migrating active DBBL from SITE1 to SITE2, please wait ...
                        DBBL has been migrated from SITE1 to SITE2

                        crlog -m SITE2
                        TMADMIN_CAT:566: ERROR: local log creation failed

                        ********************************************************************************
                        Following is the ULOG content on SITE2. It seems to me that only one TLOG associated with one node is needed and allowed(the original master node).

                        094120.redhat62!BSBRIDGE.2688.3079412320.0: 06-18-2012: client high water (0), total client (0)
                        094120.redhat62!BSBRIDGE.2688.3079412320.0: 06-18-2012: Tuxedo Version 11.1.1.2.0, 32-bit
                        094120.redhat62!BSBRIDGE.2688.3079412320.0: LIBTUX_CAT:262: INFO: Standard main starting
                        094122.redhat62!BBL.2689.3078392416.0: 06-18-2012: Tuxedo Version 11.1.1.2.0, 32-bit, Patch Level (none)
                        094122.redhat62!BBL.2689.3078392416.0: LIBTUX_CAT:262: INFO: Standard main starting
                        094122.redhat62!BRIDGE.2690.3077896800.0: 06-18-2012: Tuxedo Version 11.1.1.2.0, 32-bit
                        094122.redhat62!BRIDGE.2690.3077896800.0: LIBTUX_CAT:262: INFO: Standard main starting
                        094122.redhat62!BRIDGE.2690.3077896800.0: CMDTUX_CAT:4488: INFO: Connecting to ubuntu9 at //128.0.88.24:1800
                        094203.redhat62!tmadmin.2699.3079223904.-2: 06-18-2012: Tuxedo Version 11.1.1.2.0, 32-bit
                        094203.redhat62!tmadmin.2699.3079223904.-2: TMADMIN_CAT:1330: INFO: Command: crlog -m SITE2
                        094229.redhat62!tmadmin.2699.3079223904.-2: TMADMIN_CAT:1330: INFO: Command: master
                        094232.redhat62!BBL.2689.3078392416.0: LIBTUX_CAT:557: INFO: Server DBBL/0 being restarted
                        094232.redhat62!BBL.2689.3078392416.0: INFO: schedule to restart DBBL
                        094234.redhat62!DBBL.2708.3079408224.0: 06-18-2012: Tuxedo Version 11.1.1.2.0, 32-bit
                        094234.redhat62!DBBL.2708.3079408224.0: LIBTUX_CAT:262: INFO: Standard main starting
                        094234.redhat62!restartsrv.2707.3078375104.-2: 06-18-2012: Tuxedo Version 11.1.1.2.0, 32-bit
                        094234.redhat62!restartsrv.2707.3078375104.-2: server DBBL/0: CMDTUX_CAT:580: INFO: A server process has restarted: 2708
                        094234.redhat62!DBBL.2708.3079408224.0: LIBTUX_CAT:476: WARN: Server 30001/0: client process 2699: lost message
                        094234.redhat62!DBBL.2708.3079408224.0: LIBTUX_CAT:477: WARN: SERVICE=MIGRATE MSG_ID=0 REASON=server died
                        094241.redhat62!tmadmin.2699.3079223904.-2: TMADMIN_CAT:1330: INFO: Command: crlog -m SITE2
                        094241.redhat62!tmadmin.2699.3079223904.-2: LIBTUX_CAT:302: ERROR: tlogcreate: gpcrtbl: bad table name specified
                        094241.redhat62!tmadmin.2699.3079223904.-2: LIBTUX_CAT:316: ERROR: Transaction log file exists

                        Do you think the TUXEDO allows only one crlog command to be issued on the master node and there after the TLOG device created on the master node is used as an associated TLOG even if a migration occured?

                        By the way, when I migrated from SITE1 to SITE2 and using lidl command I can see TLOG2 is set correctly like following. (TLOG2 is the TLOG on SITE2) And meanwhile, the TLOG on SITE1 seems not working anymore.
                        lidl -z /home/tuxedo/tuxedo/simpapp/TLOG2
                        universal device index 0:
                             name: /home/tuxedo/tuxedo/simpapp/TLOG2
                             start: 0
                             size: 200
                             free space map: 1 entry used 47 available
                        lidl -z /home/xp/tuxapp/TLOG
                        TMADMIN_CAT:530: ERROR: Device list not initialized

                        When I migrate from SITE2 back to SITE1 again, the lidl reported that TLOG on SITE1 is fine, while TLOG2 on SITE2 is not initialized.

                        Best regards,

                        Orlando

                        Edited by: user10950876 on 2012-6-18 上午12:08