Nothing concrete but;

I would check the use of memory, and depending on the O/S maybe there are
kernel parameters or user limits etc.. that you may be coming up against.

I also wonder if this could be a problem with semaphores not being cleared?

_______________________________
Matthew Warren.          GZPTXW
MatthewJames.Warren AT eds DOT com <mailto:MatthewJames.Warren AT eds DOT com>
EDS Core Infrastructure,
UK Technical Services Group,
Wavendon Tower, Milton Keynes.
_______________________________


> -----Original Message-----
> From: Chan, Kien [mailto:Chan_K AT CI.WICHITA.KS DOT US]
> Sent: 27 August 2001 19:38
> To: ADSM-L AT VM.MARIST DOT EDU
> Subject: Error ANR9999D - Thread can't be created!
> Sensitivity: Private
>
>
> Hi, *SM administrators. I haven't seen this error showed up
> on the activity
> log on the server before and I don't have a clue how to solve
> this. It has
> to do with thread and migration. The following are the errors
> I got from the
> activity log:
>
> 08/25/2001 22:55:15      ANR9999D dfmigr.c(1280): Error creating disk
> migration
>                           thread.
>
> 08/25/2001 22:55:15      ANR9999D dfmigr.c(591): Migration
> agent stalled -
> retry in
>                           30 seconds.
>
> 08/25/2001 22:55:35      ANR9999D afmigr.c(2499): Error
> creating archival
>
>                           reclamation thread.
>
> 08/25/2001 22:55:35      ANR9999D afmigr.c(582): Arch
> reclamation agent
> stalled -
>                           retry in 30 seconds.
>
> 08/25/2001 22:55:46      ANR1030W Migration process 588 terminated for
> storage pool
>                           DISKPOOL - thread resource not available.
>
> 08/25/2001 22:55:46      ANR0985I Process 588 for MIGRATION
> running in the
>
>                           BACKGROUND completed with
> completion state FAILURE
> at
>                           22:55:46.
>
> 08/25/2001 22:55:46      ANR1002I Migration for storage pool
> DISKPOOL will
> be
>                           retried in 60 seconds.
>
> 08/25/2001 22:55:46      ANR1003I Migration retry delay
> ended; checking
> migration
>                           status for storage pool DISKPOOL.
>
> 08/25/2001 22:55:46      ANR0984I Process 589 for MIGRATION
> started in the
>
>                           BACKGROUND at 22:55:46.
>
> 08/25/2001 22:55:46      ANR1000I Migration process 589
> started for storage
> pool
>                           DISKPOOL.
>
> 08/25/2001 22:55:46      ANR9999D pkthread.c(962): Unable to
> create new
> Thread.
>                           CreateThread error.
>
> 08/25/2001 22:55:46      ANR9999D sstrans.c(5383): Error
> starting auxiliary
> data
>                           transfer thread.
>
> 08/25/2001 22:55:46      ANR1030W Migration process 589 terminated for
> storage pool
>                           DISKPOOL - thread resource not available.
>
> 08/25/2001 22:55:46      ANR0985I Process 589 for MIGRATION
> running in the
>
>                           BACKGROUND completed with
> completion state FAILURE
> at
>                           22:55:46.
>
>
>
> On the client side, I got these errors as well. I think they
> were related.
>
> ANR0528W        Transaction failed for session 139271 for node GISLYNX
> (WinNT) - thread resource not available.
> ANR0530W        Transaction failed for session 139278 for node KITTY -
> internal server error.
>
> I looked it up these errors and it had to do with allocation
> of the memory
> and additional storage to server. Does this mean I don't have
> enough disk
> space for the server to migration the data out of the disk or
> perhaps not
> enough memory?
>
> Any help will be greatly appreciated! Thanks again....
>
>
> Kien Chan
>