Home

Results 1 to 7 of 7

Thread: "re-initialize" NSM2.0.3?

Hybrid View

  1. #1
    Chris Glanzer NNTP User

    "re-initialize" NSM2.0.3?

    I initially had NSM2 install on a NW6sp5 server...that server is being
    removed from the tree. I now have 2.0.3 install on a NW6.5sp5 machine. It
    keeps expecting certain data to be in the database...but the DB is fresh...I
    believe that is why I continue to receive these error and can not backfill
    anything.

    07/28 22:56:37 0: E166 Unable to open
    <SYS:FACTORY\DBASE\FF\FF916D2677D5BA6BF019B014F0B5 E4E3>. errno=6 NWErrno=132

    07/28 22:56:37 0: E166 Unable to open
    <SYS:FACTORY\DBASE\9B\9B044A8FF8BE6B82B21684B78586 23FD>. errno=6 NWErrno=132

    07/28 22:56:37 0: E166 Unable to open
    <SYS:FACTORY\DBASE\43\4311B207E2E98364381CFB8AF627 257E>. errno=6 NWErrno=132

    07/28 22:56:37 0: E166 Unable to open
    <SYS:FACTORY\DBASE\A0\A0B814DF03410D62BBFDE8C66B04 E02D>. errno=6 NWErrno=132

    07/28 22:56:37 0: E166 Unable to open
    <SYS:FACTORY\DBASE\7F\7F72826654F339538F15976C1BDA A61A>. errno=6 NWErrno=132

    07/28 22:56:37 0: E166 Unable to open
    <SYS:FACTORY\DBASE\04\0476E5E8C467AD23D26777E1524B 57BB>. errno=6 NWErrno=132
    ...

    Anyway to start from scratch?

    CG

  2. #2
    fsfdev NNTP User

    Re: "re-initialize" NSM2.0.3?

    Chris,

    Can you check to see what clib you are running?
    FSF Development

    "Chris Glanzer" <chrisg@tabor.edu> wrote in message
    news:44CA97DD.3547.0021.0@tabor.edu...
    >I initially had NSM2 install on a NW6sp5 server...that server is being
    > removed from the tree. I now have 2.0.3 install on a NW6.5sp5 machine.
    > It
    > keeps expecting certain data to be in the database...but the DB is
    > fresh...I
    > believe that is why I continue to receive these error and can not backfill
    > anything.
    >
    > 07/28 22:56:37 0: E166 Unable to open
    > <SYS:FACTORY\DBASE\FF\FF916D2677D5BA6BF019B014F0B5 E4E3>. errno=6
    > NWErrno=132
    >
    > 07/28 22:56:37 0: E166 Unable to open
    > <SYS:FACTORY\DBASE\9B\9B044A8FF8BE6B82B21684B78586 23FD>. errno=6
    > NWErrno=132
    >
    > 07/28 22:56:37 0: E166 Unable to open
    > <SYS:FACTORY\DBASE\43\4311B207E2E98364381CFB8AF627 257E>. errno=6
    > NWErrno=132
    >
    > 07/28 22:56:37 0: E166 Unable to open
    > <SYS:FACTORY\DBASE\A0\A0B814DF03410D62BBFDE8C66B04 E02D>. errno=6
    > NWErrno=132
    >
    > 07/28 22:56:37 0: E166 Unable to open
    > <SYS:FACTORY\DBASE\7F\7F72826654F339538F15976C1BDA A61A>. errno=6
    > NWErrno=132
    >
    > 07/28 22:56:37 0: E166 Unable to open
    > <SYS:FACTORY\DBASE\04\0476E5E8C467AD23D26777E1524B 57BB>. errno=6
    > NWErrno=132
    > ...
    >
    > Anyway to start from scratch?
    >
    > CG




  3. #3
    NSM Development NNTP User

    Re: "re-initialize" NSM2.0.3?

    Chris,

    Also verify that your server's simple name is located at the end of the
    servers ip address line in the SYS:/ETC/HOSTS file.

    EXAMPLE:
    123.123.123.123 SERVER1.domain.com SERVER1

    thanks,
    NSM Development

    fsfdev wrote:
    > Chris,
    >
    > Can you check to see what clib you are running?
    > FSF Development
    >
    > "Chris Glanzer" <chrisg@tabor.edu> wrote in message
    > news:44CA97DD.3547.0021.0@tabor.edu...
    >> I initially had NSM2 install on a NW6sp5 server...that server is being
    >> removed from the tree. I now have 2.0.3 install on a NW6.5sp5 machine.
    >> It
    >> keeps expecting certain data to be in the database...but the DB is
    >> fresh...I
    >> believe that is why I continue to receive these error and can not backfill
    >> anything.
    >>
    >> 07/28 22:56:37 0: E166 Unable to open
    >> <SYS:FACTORY\DBASE\FF\FF916D2677D5BA6BF019B014F0B5 E4E3>. errno=6
    >> NWErrno=132
    >>
    >> 07/28 22:56:37 0: E166 Unable to open
    >> <SYS:FACTORY\DBASE\9B\9B044A8FF8BE6B82B21684B78586 23FD>. errno=6
    >> NWErrno=132
    >>
    >> 07/28 22:56:37 0: E166 Unable to open
    >> <SYS:FACTORY\DBASE\43\4311B207E2E98364381CFB8AF627 257E>. errno=6
    >> NWErrno=132
    >>
    >> 07/28 22:56:37 0: E166 Unable to open
    >> <SYS:FACTORY\DBASE\A0\A0B814DF03410D62BBFDE8C66B04 E02D>. errno=6
    >> NWErrno=132
    >>
    >> 07/28 22:56:37 0: E166 Unable to open
    >> <SYS:FACTORY\DBASE\7F\7F72826654F339538F15976C1BDA A61A>. errno=6
    >> NWErrno=132
    >>
    >> 07/28 22:56:37 0: E166 Unable to open
    >> <SYS:FACTORY\DBASE\04\0476E5E8C467AD23D26777E1524B 57BB>. errno=6
    >> NWErrno=132
    >> ...
    >>
    >> Anyway to start from scratch?
    >>
    >> CG

    >
    >


  4. #4
    Chris Glanzer NNTP User

    Re: "re-initialize" NSM2.0.3?

    Hello,

    I am running CLIB 5.90.11. This machine is NW6.5sp5, but that version of CLIB is from SP4. If you think that is the issue, I will re-run the SP5 install.

    I also looked at my hosts file and the server name is in there correctly.

    Thank you for the response.

    Chris G.

    >>> On 8/1/2006 at 8:16 am, in message <PuIzg.1681$P35.1263@prv-forum2.provo.novell.com>, NSM Development<storagemanager@novell.com> wrote:


    Chris,

    Also verify that your server's simple name is located at the end of the
    servers ip address line in the SYS:/ETC/HOSTS file.

    EXAMPLE:
    123.123.123.123 SERVER1.domain.com SERVER1

    thanks,
    NSM Development

    fsfdev wrote:
    > Chris,
    >
    > Can you check to see what clib you are running?
    > FSF Development
    >
    > "Chris Glanzer" <chrisg@tabor.edu> wrote in message
    > news:44CA97DD.3547.0021.0@tabor.edu...
    >> I initially had NSM2 install on a NW6sp5 server...that server is being
    >> removed from the tree. I now have 2.0.3 install on a NW6.5sp5 machine.
    >> It
    >> keeps expecting certain data to be in the database...but the DB is
    >> fresh...I
    >> believe that is why I continue to receive these error and can not backfill
    >> anything.
    >>
    >> 07/28 22:56:37 0: E166 Unable to open
    >> <SYS:FACTORY\DBASE\FF\FF916D2677D5BA6BF019B014F0B5 E4E3>. errno=6
    >> NWErrno=132
    >> |
    >> 07/28 22:56:37 0: E166 Unable to open
    >> <SYS:FACTORY\DBASE\9B\9B044A8FF8BE6B82B21684B78586 23FD>. errno=6
    >> NWErrno=132
    >> |
    >> 07/28 22:56:37 0: E166 Unable to open
    >> <SYS:FACTORY\DBASE\43\4311B207E2E98364381CFB8AF627 257E>. errno=6
    >> NWErrno=132
    >> |
    >> 07/28 22:56:37 0: E166 Unable to open
    >> <SYS:FACTORY\DBASE\A0\A0B814DF03410D62BBFDE8C66B04 E02D>. errno=6
    >> NWErrno=132
    >> |
    >> 07/28 22:56:37 0: E166 Unable to open
    >> <SYS:FACTORY\DBASE\7F\7F72826654F339538F15976C1BDA A61A>. errno=6
    >> NWErrno=132
    >> |
    >> 07/28 22:56:37 0: E166 Unable to open
    >> <SYS:FACTORY\DBASE\04\0476E5E8C467AD23D26777E1524B 57BB>. errno=6
    >> NWErrno=132
    >> |...
    >>
    >> Anyway to start from scratch?
    >>
    >> CG

    >
    >


  5. #5
    NSM Development NNTP User

    Re: "re-initialize" NSM2.0.3?

    Chris,
    CLIB 5.90.11 is the bad clib from SP4/SP4a, and needs to be updated to
    at minimum CLIB 5.90.12. Which is the generally shipping version that
    comes with SP5 or the CLIB update package (TID 2972740).

    thanks,
    NSM Development


    Chris Glanzer wrote:
    > Hello,
    >
    > I am running CLIB 5.90.11. This machine is NW6.5sp5, but that version
    > of CLIB is from SP4. If you think that is the issue, I will re-run the
    > SP5 install.
    >
    > I also looked at my hosts file and the server name is in there correctly.
    >
    > Thank you for the response.
    > Chris G.
    >
    > >>> On 8/1/2006 at 8:16 am, in message

    > <PuIzg.1681$P35.1263@prv-forum2.provo.novell.com>, NSM
    > Development<storagemanager@novell.com> wrote:
    > Chris,
    >
    > Also verify that your server's simple name is located at the end of the
    > servers ip address line in the SYS:/ETC/HOSTS file.
    >
    > EXAMPLE:
    > 123.123.123.123 SERVER1.domain.com SERVER1
    >
    > thanks,
    > NSM Development
    >
    > fsfdev wrote:
    > > Chris,
    > >
    > > Can you check to see what clib you are running?
    > > FSF Development
    > >
    > > "Chris Glanzer" <chrisg@tabor.edu> wrote in message
    > > news:44CA97DD.3547.0021.0@tabor.edu...
    > >> I initially had NSM2 install on a NW6sp5 server...that server is being
    > >> removed from the tree. I now have 2.0.3 install on a NW6.5sp5 machine.
    > >> It
    > >> keeps expecting certain data to be in the database...but the DB is
    > >> fresh...I
    > >> believe that is why I continue to receive these error and can not

    > backfill
    > >> anything.
    > >>
    > >> 07/28 22:56:37 0: E166 Unable to open
    > >> <SYS:FACTORY\DBASE\FF\FF916D2677D5BA6BF019B014F0B5 E4E3>. errno=6
    > >> NWErrno=132
    > >> |
    > >> 07/28 22:56:37 0: E166 Unable to open
    > >> <SYS:FACTORY\DBASE\9B\9B044A8FF8BE6B82B21684B78586 23FD>. errno=6
    > >> NWErrno=132
    > >> |
    > >> 07/28 22:56:37 0: E166 Unable to open
    > >> <SYS:FACTORY\DBASE\43\4311B207E2E98364381CFB8AF627 257E>. errno=6
    > >> NWErrno=132
    > >> |
    > >> 07/28 22:56:37 0: E166 Unable to open
    > >> <SYS:FACTORY\DBASE\A0\A0B814DF03410D62BBFDE8C66B04 E02D>. errno=6
    > >> NWErrno=132
    > >> |
    > >> 07/28 22:56:37 0: E166 Unable to open
    > >> <SYS:FACTORY\DBASE\7F\7F72826654F339538F15976C1BDA A61A>. errno=6
    > >> NWErrno=132
    > >> |
    > >> 07/28 22:56:37 0: E166 Unable to open
    > >> <SYS:FACTORY\DBASE\04\0476E5E8C467AD23D26777E1524B 57BB>. errno=6
    > >> NWErrno=132
    > >> |...
    > >>
    > >> Anyway to start from scratch?
    > >>
    > >> CG

    > >
    > >

    >
    >


  6. #6
    Chris Glanzer NNTP User

    Re: "re-initialize" NSM2.0.3?

    I still do not know why my CLIB was the sp4 version on sp5...but after *re-packing* the box CLIB is now version 5.90.12.
    The backfill thread completes and things seem to be operating properly. Thanks for the help.

    Chris G.

    >>> On 8/2/2006 at 8:18 am, in message <eC1Ag.2768$P35.427@prv-forum2.provo..novell.com>, NSM Development<storagemanager@novell.com> wrote:


    Chris,
    CLIB 5.90.11 is the bad clib from SP4/SP4a, and needs to be updated to
    at minimum CLIB 5.90.12. Which is the generally shipping version that
    comes with SP5 or the CLIB update package (TID 2972740).

    thanks,
    NSM Development


    Chris Glanzer wrote:
    > Hello,
    >
    > I am running CLIB 5.90.11. This machine is NW6.5sp5, but that version
    > of CLIB is from SP4. If you think that is the issue, I will re-run the
    > SP5 install.
    >
    > I also looked at my hosts file and the server name is in there correctly.
    >
    > Thank you for the response.
    > Chris G.
    >
    > >>> On 8/1/2006 at 8:16 am, in message

    > <PuIzg.1681$P35.1263@prv-forum2.provo.novell.com>, NSM
    > Development<storagemanager@novell.com> wrote:
    > Chris,
    >
    > Also verify that your server's simple name is located at the end of the
    > servers ip address line in the SYS:/ETC/HOSTS file.
    >
    > EXAMPLE:
    > 123.123.123.123 SERVER1.domain.com SERVER1
    >
    > thanks,
    > NSM Development
    >
    > fsfdev wrote:
    > > Chris,
    > >
    > > Can you check to see what clib you are running?
    > > FSF Development
    > >
    > > "Chris Glanzer" <chrisg@tabor.edu> wrote in message
    > > news:44CA97DD.3547.0021.0@tabor.edu...
    > >> I initially had NSM2 install on a NW6sp5 server...that server is being
    > >> removed from the tree. I now have 2.0.3 install on a NW6.5sp5 machine.
    > >> It
    > >> keeps expecting certain data to be in the database...but the DB is
    > >> fresh...I
    > >> believe that is why I continue to receive these error and can not

    > backfill
    > >> anything.
    > >>
    > >> 07/28 22:56:37 0: E166 Unable to open
    > >> <SYS:FACTORY\DBASE\FF\FF916D2677D5BA6BF019B014F0B5 E4E3>. errno=6
    > >> NWErrno=132
    > >> |
    > >> 07/28 22:56:37 0: E166 Unable to open
    > >> <SYS:FACTORY\DBASE\9B\9B044A8FF8BE6B82B21684B78586 23FD>. errno=6
    > >> NWErrno=132
    > >> |
    > >> 07/28 22:56:37 0: E166 Unable to open
    > >> <SYS:FACTORY\DBASE\43\4311B207E2E98364381CFB8AF627 257E>. errno=6
    > >> NWErrno=132
    > >> |
    > >> 07/28 22:56:37 0: E166 Unable to open
    > >> <SYS:FACTORY\DBASE\A0\A0B814DF03410D62BBFDE8C66B04 E02D>. errno=6
    > >> NWErrno=132
    > >> |
    > >> 07/28 22:56:37 0: E166 Unable to open
    > >> <SYS:FACTORY\DBASE\7F\7F72826654F339538F15976C1BDA A61A>. errno=6
    > >> NWErrno=132
    > >> |
    > >> 07/28 22:56:37 0: E166 Unable to open
    > >> <SYS:FACTORY\DBASE\04\0476E5E8C467AD23D26777E1524B 57BB>. errno=6
    > >> NWErrno=132
    > >> |...
    > >>
    > >> Anyway to start from scratch?
    > >>
    > >> CG

    > >
    > >

    >
    >


  7. #7
    NSM Development NNTP User

    Re: "re-initialize" NSM2.0.3?

    Chris,

    Did the clib patch fix the problem for you?

    thanks,
    NSM Development

    Chris Glanzer wrote:
    > I still do not know why my CLIB was the sp4 version on sp5...but after
    > *re-packing* the box CLIB is now version 5.90.12.
    > The backfill thread completes and things seem to be operating properly.
    > Thanks for the help.
    >
    > Chris G.
    >
    > >>> On 8/2/2006 at 8:18 am, in message

    > <eC1Ag.2768$P35.427@prv-forum2.provo.novell.com>, NSM
    > Development<storagemanager@novell.com> wrote:
    > Chris,
    > CLIB 5.90.11 is the bad clib from SP4/SP4a, and needs to be updated to
    > at minimum CLIB 5.90.12. Which is the generally shipping version that
    > comes with SP5 or the CLIB update package (TID 2972740).
    >
    > thanks,
    > NSM Development
    >
    >
    > Chris Glanzer wrote:
    > > Hello,
    > >
    > > I am running CLIB 5.90.11. This machine is NW6.5sp5, but that version
    > > of CLIB is from SP4. If you think that is the issue, I will re-run the
    > > SP5 install.
    > >
    > > I also looked at my hosts file and the server name is in there correctly.
    > >
    > > Thank you for the response.
    > > Chris G.
    > >
    > > >>> On 8/1/2006 at 8:16 am, in message

    > > <PuIzg.1681$P35.1263@prv-forum2.provo.novell.com>, NSM
    > > Development<storagemanager@novell.com> wrote:
    > > Chris,
    > >
    > > Also verify that your server's simple name is located at the end of the
    > > servers ip address line in the SYS:/ETC/HOSTS file.
    > >
    > > EXAMPLE:
    > > 123.123.123.123 SERVER1.domain.com SERVER1
    > >
    > > thanks,
    > > NSM Development
    > >
    > > fsfdev wrote:
    > > > Chris,
    > > >
    > > > Can you check to see what clib you are running?
    > > > FSF Development
    > > >
    > > > "Chris Glanzer" <chrisg@tabor.edu> wrote in message
    > > > news:44CA97DD.3547.0021.0@tabor.edu...
    > > >> I initially had NSM2 install on a NW6sp5 server...that server is

    > being
    > > >> removed from the tree. I now have 2.0.3 install on a NW6.5sp5

    > machine.
    > > >> It
    > > >> keeps expecting certain data to be in the database...but the DB is
    > > >> fresh...I
    > > >> believe that is why I continue to receive these error and can not

    > > backfill
    > > >> anything.
    > > >>
    > > >> 07/28 22:56:37 0: E166 Unable to open
    > > >> <SYS:FACTORY\DBASE\FF\FF916D2677D5BA6BF019B014F0B5 E4E3>. errno=6
    > > >> NWErrno=132
    > > >> |
    > > >> 07/28 22:56:37 0: E166 Unable to open
    > > >> <SYS:FACTORY\DBASE\9B\9B044A8FF8BE6B82B21684B78586 23FD>. errno=6
    > > >> NWErrno=132
    > > >> |
    > > >> 07/28 22:56:37 0: E166 Unable to open
    > > >> <SYS:FACTORY\DBASE\43\4311B207E2E98364381CFB8AF627 257E>. errno=6
    > > >> NWErrno=132
    > > >> |
    > > >> 07/28 22:56:37 0: E166 Unable to open
    > > >> <SYS:FACTORY\DBASE\A0\A0B814DF03410D62BBFDE8C66B04 E02D>. errno=6
    > > >> NWErrno=132
    > > >> |
    > > >> 07/28 22:56:37 0: E166 Unable to open
    > > >> <SYS:FACTORY\DBASE\7F\7F72826654F339538F15976C1BDA A61A>. errno=6
    > > >> NWErrno=132
    > > >> |
    > > >> 07/28 22:56:37 0: E166 Unable to open
    > > >> <SYS:FACTORY\DBASE\04\0476E5E8C467AD23D26777E1524B 57BB>. errno=6
    > > >> NWErrno=132
    > > >> |...
    > > >>
    > > >> Anyway to start from scratch?
    > > >>
    > > >> CG
    > > >
    > > >

    > >
    > >

    >
    >


Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •