My Oracle Support Banner

CLOPT Corrupts When Changing It Via MIB (Doc ID 2055913.1)

Last updated on DECEMBER 11, 2019

Applies to:

Oracle Tuxedo - Version 11.1.1.2.0 and later
Information in this document applies to any platform.

Symptoms

 When changing CLOPT for WSL via a MIB request it will be corrupted.

Initial value in ubbconfig:

"WSL" SRVGRP=WSGROUP1 SRVID=1 CLOPT="-A -- //<IPADDRESS>:<PORT> -H //<IPADRESS>:<PORT> -T 10 -m 250 -M 250 -x 8 -p <PORT> -P <PORT> -T 10 -N 180 -K both -z 0 -Z 0"

 Modify via MIB with following ud script

ud32 -C tpsysadm  <SRVCNM  .TMIB
TA_CLASS        T_SERVER
TA_SRVGRP       WSGROUP1
TA_SRVID        1
TA_CLOPT        -A -- -n //<IPADDRESS>:port# -H //<IPADDRESS>:MMMM -T 10 -m 250 -M 250 -x 8 -p <PORT> -P <PORT>  -N 180 -K both -z 0 -Z 0
TA_MIN  1
TA_MAX  1
TA_OPERATION    SET

!

 tmunloadcf result (old "-H" option value is added at the end of new WSL CLOPT setting):

"WSL"   SRVGRP="WSGROUP1"       SRVID=1
        CLOPT="-A --  -n //<IPADDRESS>:port# -H //<IPADDRESS>:MMMM -m 250 -M 250 -x 8 -p <PORT> -P<PORT> -N 180 -K both -z 0 -Z 0 //<IPADDRESS>:MMMMM 10 10"

 CLOPT is corrupted from tmunloadcf result, but it works well as expected parameter when booting WSL

Changes

 

Cause

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!


In this Document
Symptoms
Changes
Cause
Solution
References


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.