IDS Forum

Re: -25572 Network driver cannot bind a name to the port.

Posted By: More, Shailesh
Date: Friday, 28 January 2005, at 3:42 a.m.

The problem is solved...thanks a lot for all ur support

Added and modified following entries in ONCONFIG file, SQLHOSTS and
services
file

ONCONFIG
DBSERVERNAME kam940shm # Name of default database server
DBSERVERALIASES kam940q1 # List of alternate dbservernames
NETTYPE ipcshm,1,20,CPU # Override sqlhosts defaults
NETTYPE tlitcp,1,20,NET # Override sqlhosts defaults


SQLHOSTS
kam940q1 ontlitcp kamal infsrv0
kam940shm onipcshm kamal kamal

SERVICES
#shailesh 8000/tcp # Informix database
client
connection
infsrv0 8000/tcp # Informix database client
connection
Regards,
Shailesh M
Board no.: - 30215000
Ext. no.: - 8774

-----Original Message-----
From: François Dénommée [mailto:francois.denommee@videotron.ca]
Sent: Saturday, January 22, 2005 6:25 PM
To: ids@iiug.org; Shailesh_More@bmc.com
Subject: Re: -25572 Network driver cannot bind a name to the port.
[4068]

Recently I solved a situation generating that same error message on a
SCO
5.06 box with SE 7.31 installed.

The source of the problem had very few about informix. Someone
scheduled a
task looking for a specific process, that was not running, and this was
the
error message about the result of that query. Essentially, they were
investigating for the informix sqlexec process and launching the
process if
not found.


I would suggest that you verify some few more things:
1- Make an audit of all cron contents, for all users crontab -l
2- Make a verification of all root or priviliged users and see if this
error message is also present.
3-If it is a SCO box, do also a check within those 2 files:
/usr/adm/messages and /usr/adm/syslog
4- As much as possible, do a manual execution of any scripts, tasks
scheduled from what you might have found in 1

Regards

Francois

More, Shailesh wrote:
>
> Hi,
>
> I am getting following error message
>
> "-25572 Network driver cannot bind a name to the port."
>
> Please find the contain of INFORMIX environment variables, sqlhosts,
> services and onconfig file.
>
> INFORMIX environment variables
> INFORMIXDIR=/usr/informix/9.40.UC1
> INFORMIXSERVER=kam940q1
> ONCONFIG=onconfig.kam940q1
>
> SQLHOSTS
> kam940q1 ontlitcp kamal shailesh
> kamxpsq1.1 onipcshm kamal infsrv2
>
> SERVICES
> shailesh 8000/tcp # Informix database
client
> connection
> #infsrv0 8000/tcp # Informix database
client
> connection
> infsrv2 7206/tcp # Informix database client
> connection
> infsrv6 7201/tcp # Informix database client
> connection
> infsrv7 7202/tcp # Informix database client
> connection
> infsrv8 7203/tcp # Informix database client
> connection
> infsrv9 7204/tcp # Informix database client
> connection
> infsrv13 7266/tcp # Informix database client
> connection
> infsrv14 7267/tcp # Informix database client
> connection
>
> onconfig.kam940q1
> # Root Dbspace Configuration
>
> ROOTNAME rootdbs # Root dbspace name
> ROOTPATH /usr/informix/databases/kam940q1/datafiles/root.dbf
> ROOTOFFSET 0 # Offset of root dbspace into device
> (Kbytes)
> ROOTSIZE 35000 # Size of root dbspace (Kbytes) 9/96:changed
from
> 20000
> # 1/7/97: changed from 22500 to 25000
>
> # Disk Mirroring Configuration Parameters
>
> MIRROR 0 # Mirroring flag (Yes = 1, No =
0)
> # Path for device containing mirrored root
> # MIRRORPATH /usr/informix/databases/kam940q1/mirrorfiles/mirror.dbf
> MIRROROFFSET 0 # Offset into mirrored device
(Kbytes)
>
> # Physical Log Configuration
>
> PHYSDBS rootdbs # Location (dbspace) of physical log
> PHYSFILE 2000 # Physical log file size (Kbytes)
> # Logical Log Configuration
>
> LOGFILES 6 # Number of logical log files
> LOGSIZE 1000 # Logical log size (Kbytes)
>
> # Diagnostics
>
> # System message log file path
> MSGPATH /usr/informix/databases/kam940q1/logfiles/online.log
> CONSOLE /usr/informix/databases/kam940q1/logfiles/console.log
> ALARMPROGRAM # Alarm program path
>
> # System Archive Tape Device
>
> TAPEDEV /usr/informix/databases/kam940q1/logfiles/tape #
Tape
> device path
> TAPEBLK 32 # Tape block size (Kbytes)
> TAPESIZE 1024000 # Maximum amount of data to put on
tape
> (Kbytes)
>
> # Log Archive Tape Device
>
> LTAPEDEV /usr/informix/databases/kam940q1/logfiles/ltape # Log
tape
> device path
> LTAPEBLK 32 # Log tape block size (Kbytes)
> LTAPESIZE 1024000 # Max amount of data to put on log
tape
> (Kbytes)
>
> # Optical
>
> STAGEBLOB # INFORMIX-OnLine/Optical staging
area
>
> # System Configuration
>
> SERVERNUM 1 # Unique id corresponding to a OnLine
> instance
> DBSERVERNAME kam940q1 # Name of default database
server
> DBSERVERALIASES # List of alternate dbservernames
> DEADLOCK_TIMEOUT 60 # Max time to wait of lock in
distributed
> env.
> RESIDENT 0 # Forced residency flag (Yes = 1,
No = 0)
>
> MULTIPROCESSOR 0 # 0 for single-processor, 1 for
> multi-processor
> NUMCPUVPS 1 # Number of user (cpu) vps
> SINGLE_CPU_VP 1 # If non-zero, limit number of cpu
vps to
> one
>
> NOAGE 0 # Process aging
> AFF_SPROC 0 # Affinity start processor
> AFF_NPROCS 0 # Affinity number of processors
>
> # Shared Memory Parameters
>
> LOCKS 5000 # Maximum number of locks
> BUFFERS 200 # Maximum number of shared buffers
> NUMAIOVPS 2 # Number of IO vps
> PHYSBUFF 32 # Physical log buffer size (Kbytes)
> LOGBUFF 32 # Logical log buffer size (Kbytes)
> LOGSMAX 6 # Maximum number of logical log files
> CLEANERS 1 # Number of buffer cleaner processes
> SHMBASE 0x0A000000L # Shared memory base address
> NETTYPE ipcshm,1,20,CPU # Override sqlhosts defaults
> # NETTYPE tlitcp,1,20,NET # Override sqlhosts defaults
> SHMVIRTSIZE 8000 # initial virtual shared memory
segment
size
> SHMADD 8192 # Size of new shared memory segments
> (Kbytes)
> SHMTOTAL 0 # Total shared memory (Kbytes).
0=>unlimited
> CKPTINTVL 300 # Check point interval (in sec)
> LRUS 8 # Number of LRU queues
> LRU_MAX_DIRTY 60 # LRU percent dirty begin cleaning
limit
> LRU_MIN_DIRTY 50 # LRU percent dirty end cleaning
limit
> LTXHWM 50 # Long transaction high water mark
> percentage
> LTXEHWM 60 # Long transaction high water mark
> (exclusive)
> TXTIMEOUT 300 # Transaction timeout (in sec)
> STACKSIZE 32 # Stack size (Kbytes)
>
> # System Page Size
> # BUFFSIZE - OnLine no longer supports this configuration parameter.
> # To determine the page size used by OnLine on your
platform
> # see the last line of output from the command, 'onstat
* b'.nate
> dbservernames
>
> # Recovery Variables
> # OFF_RECVRY_THREADS:
> # Number of parallel worker threads during fast recovery or an
offline
> restore.
> # ON_RECVRY_THREADS:
> # Number of parallel worker threads during an online restore.
>
> OFF_RECVRY_THREADS 10 # Default number of offline worker
threads
> ON_RECVRY_THREADS 1 # Default number of online worker
threads
>
> # Data Replication Variables
> # DRAUTO: 0 manual, 1 retain type, 2 reverse type
> DRAUTO 0 # DR automatic switchover
> DRINTERVAL 30 # DR max time between DR buffer
flushes
(in
> sec)
> DRTIMEOUT 30 # DR network timeout (in sec)
> # DR lost+found file path
> DRLOSTFOUND
/usr/informix/databases/kam940q1/logfiles/dr.lostfound
>
> # Read Ahead Variables
> RA_PAGES # Number of pages to attempt to read
ahead
> RA_THRESHOLD # Number of pages left before next
group
>
> # CDR Variables
> CDR_EVALTHREADS 1,2 # evaluator threads
(per-cpu-vp,additional)
> CDR_DSLOCKWAIT 5 # DS lockwait timeout (seconds)
> CDR_QUEUEMEM 4096 # Maximum amount of memory for any
CDR
queue
> (Kbytes)
> CDR_NIFCOMPRESS 0 # Link level compression (-1 never, 0
none,
> 9 max)
>
> # Backup/Restore variables
> BAR_ACT_LOG /usr/informix/9.40.UC1/bar_act.log
> BAR_MAX_BACKUP 0
> BAR_RETRY 1
> BAR_DEBUG 9
> BAR_DEBUG_LOG /usr/informix/9.40.UC1/bar_debug.log
> BAR_NB_XPORT_COUNT 10
> BAR_XFER_BUF_SIZE 31
> BAR_PROGRESS_FREQ 0
> BAR_BSALIB_PATH /usr/informix/9.40.UC1/lib/libbsa.so
>
> # DBSPACETEMP:
> # OnLine equivalent of DBTEMP for SE. This is the list of dbspaces
> # that the OnLine SQL Engine will use to create temp tables etc.
> # If specified it must be a colon separated list of dbspaces that
exist
> # when the OnLine system is brought online. If not specified, or if
> # all dbspaces specified are invalid, various ad hoc queries will
create
> # temporary files in /tmp instead.
>
> # Default temp dbspaces
> DBSPACETEMP tempdbs1
>
> # DUMP*:
> # The following parameters control the type of diagnostics
information
which
> # is preserved when an unanticipated error condition (assertion
failure)
> occurs
> # during OnLine operations.
> # For DUMPSHMEM, DUMPGCORE and DUMPCORE 1 means Yes, 0 means No.
>
> DUMPDIR /usr/informix/databases/kam940q1/dumpfiles # Preserve
diagnostics
in
> this directory
> DUMPSHMEM 1 # Dump a copy of shared memory
> DUMPGCORE 0 # Dump a core image using 'gcore'
> DUMPCORE 0 # Dump a core image (Warning:this
aborts
> OnLine)
> DUMPCNT 1 # Number of shared memory or gcore
dumps
for
> # a single user's session
>
> # ADT*
> # The following parameters control the type and level of secure
auditing
> # present in the OnLine system. By default, ADTMODE is 0 and auditing
> # is disabled
>
> ADTMODE 0 # Auditing mode
> ADTPATH /usr/informix/databases/kam940q1/auditfiles # Directory where
audit
> trails will be written by OnLine
> ADTSIZE 50000 # Maximum size of any single audit trail file
> ADTERR 0 # 0 ==> retry failed audit writes; 1
==> log
failure
>
> FILLFACTOR 90 # Fill factor for building indexes
>
> # method for OnLine to use when determining current time
> USEOSTIME 0 # 0: use internal time(fast), 1: get time
from
> OS(slow)
>
> # Parallel Database Queries (pdq)
> PDQPRIORITY 0 # Degree of parallelism: 0 ... 100,
> # OFF => 0, LOW =>
1, HIGH
=>
> 100
> MAX_PDQPRIORITY 100 # Maximum allowed pdqpriority
> DS_MAX_QUERIES # Maximum number of decision support queries
> DS_TOTAL_MEMORY # Decision support memory (Kbytes)
> DS_MAX_SCANS 1048576 # Maximum number of decision support scans
> DATASKIP # List of dbspaces to skip
>
> # OPTCOMPIND
> # 0 => Nested loop joins will be preferred (where
> # possible) over sortmerge joins and hash joins.
> # 1 => If the transaction isolation mode is not
> # "repeatable read", optimizer behaves as in (2)
> # below. Otherwise it behaves as in (0) above.
> # 2 => Use costs regardless of the transaction isolation
> # mode. Nested loop joins are not necessarily
> # preferred. Optimizer bases its decision purely
> # on costs.
> OPTCOMPIND 2 # To hint the optimizer
>
> ONDBSPACEDOWN 0 # Dbspace down option: 0 = CONTINUE, 1 =
ABORT, 2 =
> WAIT
> LBU_PRESERVE 0 # Preserve last log for log backup
> OPCACHEMAX 0 # Maximum optical cache size (Kbytes)
>
> Regards,
> Shailesh M

IDS Forum is maintained by Administrator with WebBBS 5.12.