Problem with redirected restore

Collapse
This topic is closed.
X
X
 
  • Time
  • Show
Clear All
new posts
  • GL

    Problem with redirected restore

    I am running DB2 8.1.1 on AIX 5.1

    Having a problem with a redirected restore.

    Once into the restore continue phase, I immediately get the following

    “SQL2059W A device full warning was encountered on device "TBS_IDX".
    Do you want to continue(c), terminate this device only(d), abort the
    utility(t)
    ? (c/d/t) t

    I'm not allowed to continue as if I try I just get the 'warning' again.

    This is the first DMS tablespace in the script.

    Space does not seem to be the issue. The path in question is showing
    49610752 in 1024 blocks allocated and only 17% used.

    The tablespace in question was defined as 1000000 4k pages.

    The permissions down the entire path are good.

    I have checked and tried the following.

    Checked ulimit and ulimit -a. Showing unlimited on ulimit.

    Ulimit -a yields

    time(seconds) unlimited
    file(blocks) unlimited
    data(kbytes) 245760
    stack(kbytes) 16384
    memory(kbytes) unlimited
    coredump(blocks ) unlimited
    nofiles(descrip tors) unlimited

    Went into smitty and made sure both the soft and hard file size limit
    were set to -1 for the user (instance owner).

    Tried breaking up the containers into separate directories for each
    container. Tried using various size combinations from 100000 4k pages
    each container to 200000 4k pages.

    Tried defining the containers to total 1200000 4k pages, larger than
    originally defined.

    Tried defining one container at 100000 4k pages, 1/10th the original
    sizing.

    I get the same SQL error whatever I try.

    In etc/security/limits the values for the instance owner show the
    following

    fsize = -1
    core = -1
    data = 491519
    rss = -1
    stack = 32767

    I
    fsize_hard = -1

    So the size of the file I am defining does not seem to get rid of the
    error.

    As I've mentioned, the file permissions seem to be ok.

    Would appreciate any comments or thoughts.

    Many Thanks
    Gerry
  • zeb nest

    #2
    Re: Problem with redirected restore

    Do you have another error messages in the db2diag.log ?
    the answer of the ulimit command : are you using the userid of the instance
    owner ?

    do you have a db2 list tablespace containers for x before the restore ?
    do you have a db2 list tablespaces show detail before the restore ?

    "GL" <gl@nospam.ne t> a écrit dans le message de
    news:Xns9561E5A CFE9D2glnospamn et@216.196.97.1 31...[color=blue]
    > I am running DB2 8.1.1 on AIX 5.1
    >
    > Having a problem with a redirected restore.
    >
    > Once into the restore continue phase, I immediately get the following
    >
    > "SQL2059W A device full warning was encountered on device "TBS_IDX".
    > Do you want to continue(c), terminate this device only(d), abort the
    > utility(t)
    > ? (c/d/t) t
    >
    > I'm not allowed to continue as if I try I just get the 'warning' again.
    >
    > This is the first DMS tablespace in the script.
    >
    > Space does not seem to be the issue. The path in question is showing
    > 49610752 in 1024 blocks allocated and only 17% used.
    >
    > The tablespace in question was defined as 1000000 4k pages.
    >
    > The permissions down the entire path are good.
    >
    > I have checked and tried the following.
    >
    > Checked ulimit and ulimit -a. Showing unlimited on ulimit.
    >
    > Ulimit -a yields
    >
    > time(seconds) unlimited
    > file(blocks) unlimited
    > data(kbytes) 245760
    > stack(kbytes) 16384
    > memory(kbytes) unlimited
    > coredump(blocks ) unlimited
    > nofiles(descrip tors) unlimited
    >
    > Went into smitty and made sure both the soft and hard file size limit
    > were set to -1 for the user (instance owner).
    >
    > Tried breaking up the containers into separate directories for each
    > container. Tried using various size combinations from 100000 4k pages
    > each container to 200000 4k pages.
    >
    > Tried defining the containers to total 1200000 4k pages, larger than
    > originally defined.
    >
    > Tried defining one container at 100000 4k pages, 1/10th the original
    > sizing.
    >
    > I get the same SQL error whatever I try.
    >
    > In etc/security/limits the values for the instance owner show the
    > following
    >
    > fsize = -1
    > core = -1
    > data = 491519
    > rss = -1
    > stack = 32767
    >
    > I
    > fsize_hard = -1
    >
    > So the size of the file I am defining does not seem to get rid of the
    > error.
    >
    > As I've mentioned, the file permissions seem to be ok.
    >
    > Would appreciate any comments or thoughts.
    >
    > Many Thanks
    > Gerry[/color]


    Comment

    • GL

      #3
      Re: Problem with redirected restore

      "zeb nest" <kariboo1@tisca li.fr> wrote in
      news:ci16sa$spk $1@news.tiscali .fr:


      First, thanks...I really appreciate any thoughts you might have.

      [color=blue]
      > Do you have another error messages in the db2diag.log ?[/color]

      Yes, please see below
      [color=blue]
      > the answer of the ulimit command : are you using the userid of the
      > instance owner ?[/color]

      Yes



      ? do you have a db2 list tablespaces show detail before the restore ?


      Yes, this is the tablespace in question of the database being restored

      Tablespace ID = 5
      Name = TBS_IDX
      Type = Database managed space
      Contents = Any data
      State = 0x0000
      Detailed explanation:
      Normal
      Total pages = 1000000
      Useable pages = 999808
      Used pages = 604864
      Free pages = 394944
      High water mark (pages) = 910720
      Page size (bytes) = 4096
      Extent size (pages) = 32
      Prefetch size (pages) = 128
      Number of containers = 4
      Minimum recovery time = 2004-09-10-12.49.31.000000

      [color=blue]
      > do you have a db2 list tablespace containers for x before the restore[/color]

      Yes
      Tablespace Containers for Tablespace 5

      Container ID = 0
      Name = /db2idx/scioltpt/baseidx/sieb01
      _idx.dat
      Type = File

      Container ID = 1
      Name = /db2idx/scioltpt/baseidx/sieb02
      _idx.dat
      Type = File

      Container ID = 2
      Name = /db2idx/scioltpt/baseidx/sieb03
      _idx.dat
      Type = File

      Container ID = 3
      Name = /db2idx/scioltpt/baseidx/sieb04
      _idx.dat
      Type = File

      This is the way the containers are defined in the restore script

      set tablespace containers for 5 using
      (File '/siebel/db2/instance/siebdev/idx/siebts01_idx4k. dat' 250000,
      File '/siebel/db2/instance/siebdev/idx/siebts02_idx4k. dat' 250000,
      File '/siebel/db2/instance/siebdev/idx/siebts03_idx4k. dat' 250000,
      File '/siebel/db2/instance/siebdev/idx/siebts04_idx4k. dat' 250000)
      DB20000I The SET TABLESPACE CONTAINERS command completed successfully.

      here are the entries from the db2diag.log when the redirected restore
      script is started. I don't know if the unexpected end of file is typical
      of entries for a redirected restore.

      2004-09-12-10.07.59.075466 Instance:siebde v Node:000
      PID:58916(db2ag ent (SIEBEL) 0) TID:1 Appid:
      *LOCAL.siebdev. 00EB32140759
      buffer pool services sqlbReadBufferP oolTable Probe:905

      DIA8506C Unexpected end of file was reached.
      ZRC=0x870F0009

      Immediately after that entry, I get many, many repeated entries of
      ZRC=0xFFFFFBA1 This translates to SQL1119 The restore utility is most
      definitely terminated before the restore..to the point where I have been
      restarting db2 between runs, so I don't understand this message.

      SQL1119N A connection to or activation of database "<name>" cannot be
      made because a previous restore is incomplete.

      Explanation: The database is in an inconsistent state because a system
      error occurred during a restore function.

      No connection was made.

      Federated system users: this situation can be detected by the data
      source.

      User Response: Issue the RESTORE command and then try the command again.

      2004-09-12-10.07.59.298834 Instance:siebde v Node:000
      PID:58916(db2ag ent (SIEBEL) 0) TID:1 Appid:
      *LOCAL.siebdev. 00EB32140759
      buffer pool services sqlbinit Probe:620

      Database will come up with hidden buffer pools.
      totalBufferPool Pages: 0000 0000 0000 0040
      ........@


      2004-09-12-10.07.59.366280 Instance:siebde v Node:000
      PID:58916(db2ag ent (SIEBEL) 0) TID:1 Appid:
      *LOCAL.siebdev. 00EB32140759
      database utilities sqludPrintStart ingMsg Probe:1 Database:SIEBEL

      Starting a full database restore.
      Agent PID: 58916


      2004-09-12-10.07.59.823955 Instance:siebde v Node:000
      PID:78808(db2bm .58916.0 0) TID:1 Appid:none
      database utilities sqludProcessHis toryFile Probe:3

      An empty database history has been detected.
      The database history will be overwritten by the backup image.


      2004-09-12-10.11.41.039258 Instance:siebde v Node:000
      PID:21150(db2ag ent (SIEBEL) 0) TID:1 Appid:
      *LOCAL.siebdev. 040912141141
      base sys utilities sqleCheckForBac kupRestore Probe:10

      DIA0001E An internal error occurred. Report the following error code :
      "ZRC=0xFFFFFBA1 ".

      2004-09-12-10.11.41.081622 Instance:siebde v Node:000
      PID:21150(db2ag ent (SIEBEL) 0) TID:1 Appid:
      *LOCAL.siebdev. 040912141141
      base sys utilities sqlePrepareForS erialization Probe:20

      DIA0001E An internal error occurred. Report the following error code :
      "ZRC=0xFFFFFBA1 ".

      Could these be referring to the image copy of the database?
      Also, I am wondering if large file enabling is set on the target system.

      Comment

      • zeb nest

        #4
        Re: Problem with redirected restore


        Have you made a db2ckbkp on the backup files to check them ?

        perhaps ,the SQL1119 error comes during the different restore after the
        first restore KO.
        I usualy stop and restart the instance before try to restore the database.
        Sometimes, then the restore stop before the end (on a problem), I drop the
        database before trying a new restore (If you don't have the comand
        "replace exisiting" in your script)

        I see different path before and after the restore
        (/db2idx/scioltpt/baseidx/ ->
        '/siebel/db2/instance/siebdev/idx/siebts04_idx4k. dat' ). Have you created
        the new entire path before the restore ? Are you restoring with the userid
        of the instance ?


        "GL" <gl@nospam.ne t> a écrit dans le message de
        news:Xns9562703 6FE10Dglnospamn et@216.196.97.1 31...[color=blue]
        > "zeb nest" <kariboo1@tisca li.fr> wrote in
        > news:ci16sa$spk $1@news.tiscali .fr:
        >
        >
        > First, thanks...I really appreciate any thoughts you might have.
        >
        >[color=green]
        > > Do you have another error messages in the db2diag.log ?[/color]
        >
        > Yes, please see below
        >[color=green]
        > > the answer of the ulimit command : are you using the userid of the
        > > instance owner ?[/color]
        >
        > Yes
        >
        >
        >
        > ? do you have a db2 list tablespaces show detail before the restore ?
        >
        >
        > Yes, this is the tablespace in question of the database being restored
        >
        > Tablespace ID = 5
        > Name = TBS_IDX
        > Type = Database managed space
        > Contents = Any data
        > State = 0x0000
        > Detailed explanation:
        > Normal
        > Total pages = 1000000
        > Useable pages = 999808
        > Used pages = 604864
        > Free pages = 394944
        > High water mark (pages) = 910720
        > Page size (bytes) = 4096
        > Extent size (pages) = 32
        > Prefetch size (pages) = 128
        > Number of containers = 4
        > Minimum recovery time = 2004-09-10-12.49.31.000000
        >
        >[color=green]
        > > do you have a db2 list tablespace containers for x before the restore[/color]
        >
        > Yes
        > Tablespace Containers for Tablespace 5
        >
        > Container ID = 0
        > Name = /db2idx/scioltpt/baseidx/sieb01
        > _idx.dat
        > Type = File
        >
        > Container ID = 1
        > Name = /db2idx/scioltpt/baseidx/sieb02
        > _idx.dat
        > Type = File
        >
        > Container ID = 2
        > Name = /db2idx/scioltpt/baseidx/sieb03
        > _idx.dat
        > Type = File
        >
        > Container ID = 3
        > Name = /db2idx/scioltpt/baseidx/sieb04
        > _idx.dat
        > Type = File
        >
        > This is the way the containers are defined in the restore script
        >
        > set tablespace containers for 5 using
        > (File '/siebel/db2/instance/siebdev/idx/siebts01_idx4k. dat' 250000,
        > File '/siebel/db2/instance/siebdev/idx/siebts02_idx4k. dat' 250000,
        > File '/siebel/db2/instance/siebdev/idx/siebts03_idx4k. dat' 250000,
        > File '/siebel/db2/instance/siebdev/idx/siebts04_idx4k. dat' 250000)
        > DB20000I The SET TABLESPACE CONTAINERS command completed successfully.
        >
        > here are the entries from the db2diag.log when the redirected restore
        > script is started. I don't know if the unexpected end of file is typical
        > of entries for a redirected restore.
        >
        > 2004-09-12-10.07.59.075466 Instance:siebde v Node:000
        > PID:58916(db2ag ent (SIEBEL) 0) TID:1 Appid:
        > *LOCAL.siebdev. 00EB32140759
        > buffer pool services sqlbReadBufferP oolTable Probe:905
        >
        > DIA8506C Unexpected end of file was reached.
        > ZRC=0x870F0009
        >
        > Immediately after that entry, I get many, many repeated entries of
        > ZRC=0xFFFFFBA1 This translates to SQL1119 The restore utility is most
        > definitely terminated before the restore..to the point where I have been
        > restarting db2 between runs, so I don't understand this message.
        >
        > SQL1119N A connection to or activation of database "<name>" cannot be
        > made because a previous restore is incomplete.
        >
        > Explanation: The database is in an inconsistent state because a system
        > error occurred during a restore function.
        >
        > No connection was made.
        >
        > Federated system users: this situation can be detected by the data
        > source.
        >
        > User Response: Issue the RESTORE command and then try the command again.
        >
        > 2004-09-12-10.07.59.298834 Instance:siebde v Node:000
        > PID:58916(db2ag ent (SIEBEL) 0) TID:1 Appid:
        > *LOCAL.siebdev. 00EB32140759
        > buffer pool services sqlbinit Probe:620
        >
        > Database will come up with hidden buffer pools.
        > totalBufferPool Pages: 0000 0000 0000 0040
        > .......@
        >
        >
        > 2004-09-12-10.07.59.366280 Instance:siebde v Node:000
        > PID:58916(db2ag ent (SIEBEL) 0) TID:1 Appid:
        > *LOCAL.siebdev. 00EB32140759
        > database utilities sqludPrintStart ingMsg Probe:1 Database:SIEBEL
        >
        > Starting a full database restore.
        > Agent PID: 58916
        >
        >
        > 2004-09-12-10.07.59.823955 Instance:siebde v Node:000
        > PID:78808(db2bm .58916.0 0) TID:1 Appid:none
        > database utilities sqludProcessHis toryFile Probe:3
        >
        > An empty database history has been detected.
        > The database history will be overwritten by the backup image.
        >
        >
        > 2004-09-12-10.11.41.039258 Instance:siebde v Node:000
        > PID:21150(db2ag ent (SIEBEL) 0) TID:1 Appid:
        > *LOCAL.siebdev. 040912141141
        > base sys utilities sqleCheckForBac kupRestore Probe:10
        >
        > DIA0001E An internal error occurred. Report the following error code :
        > "ZRC=0xFFFFFBA1 ".
        >
        > 2004-09-12-10.11.41.081622 Instance:siebde v Node:000
        > PID:21150(db2ag ent (SIEBEL) 0) TID:1 Appid:
        > *LOCAL.siebdev. 040912141141
        > base sys utilities sqlePrepareForS erialization Probe:20
        >
        > DIA0001E An internal error occurred. Report the following error code :
        > "ZRC=0xFFFFFBA1 ".
        >
        > Could these be referring to the image copy of the database?
        > Also, I am wondering if large file enabling is set on the target system.[/color]


        Comment

        • GL

          #5
          Re: Problem with redirected restore

          Yes the target system has a different file structure but the paths and
          permissions have all been validated.

          I am restoring with the user id of the target (into) instance owner.

          I did drop the db as there is no replace existing in the script.

          I will check the backup files in the AM

          Thanks again
          Gerry

          "zeb nest" <kariboo1@tisca li.fr> wrote in
          news:ci1uf9$90f $1@news.tiscali .fr:
          [color=blue]
          >
          > Have you made a db2ckbkp on the backup files to check them ?
          >
          > perhaps ,the SQL1119 error comes during the different restore after
          > the first restore KO.
          > I usualy stop and restart the instance before try to restore the
          > database. Sometimes, then the restore stop before the end (on a
          > problem), I drop the database before trying a new restore (If you
          > don't have the comand "replace exisiting" in your script)
          >
          > I see different path before and after the restore
          > (/db2idx/scioltpt/baseidx/ ->
          > '/siebel/db2/instance/siebdev/idx/siebts04_idx4k. dat' ). Have you
          > created the new entire path before the restore ? Are you restoring
          > with the userid of the instance ?
          >
          >
          > "GL" <gl@nospam.ne t> a écrit dans le message de
          > news:Xns9562703 6FE10Dglnospamn et@216.196.97.1 31...[color=green]
          >> "zeb nest" <kariboo1@tisca li.fr> wrote in
          >> news:ci16sa$spk $1@news.tiscali .fr:
          >>
          >>
          >> First, thanks...I really appreciate any thoughts you might have.
          >>
          >>[color=darkred]
          >> > Do you have another error messages in the db2diag.log ?[/color]
          >>
          >> Yes, please see below
          >>[color=darkred]
          >> > the answer of the ulimit command : are you using the userid of the
          >> > instance owner ?[/color]
          >>
          >> Yes
          >>
          >>
          >>
          >> ? do you have a db2 list tablespaces show detail before the restore ?
          >>
          >>
          >> Yes, this is the tablespace in question of the database being
          >> restored
          >>
          >> Tablespace ID = 5
          >> Name = TBS_IDX
          >> Type = Database managed space
          >> Contents = Any data
          >> State = 0x0000
          >> Detailed explanation:
          >> Normal
          >> Total pages = 1000000
          >> Useable pages = 999808
          >> Used pages = 604864
          >> Free pages = 394944
          >> High water mark (pages) = 910720
          >> Page size (bytes) = 4096
          >> Extent size (pages) = 32
          >> Prefetch size (pages) = 128
          >> Number of containers = 4
          >> Minimum recovery time = 2004-09-10-12.49.31.000000
          >>
          >>[color=darkred]
          >> > do you have a db2 list tablespace containers for x before the
          >> > restore[/color]
          >>
          >> Yes
          >> Tablespace Containers for Tablespace 5
          >>
          >> Container ID = 0
          >> Name =
          >> /db2idx/scioltpt/baseidx/sieb01
          >> _idx.dat
          >> Type = File
          >>
          >> Container ID = 1
          >> Name =
          >> /db2idx/scioltpt/baseidx/sieb02
          >> _idx.dat
          >> Type = File
          >>
          >> Container ID = 2
          >> Name =
          >> /db2idx/scioltpt/baseidx/sieb03
          >> _idx.dat
          >> Type = File
          >>
          >> Container ID = 3
          >> Name =
          >> /db2idx/scioltpt/baseidx/sieb04
          >> _idx.dat
          >> Type = File
          >>
          >> This is the way the containers are defined in the restore script
          >>
          >> set tablespace containers for 5 using
          >> (File '/siebel/db2/instance/siebdev/idx/siebts01_idx4k. dat' 250000,
          >> File '/siebel/db2/instance/siebdev/idx/siebts02_idx4k. dat' 250000,
          >> File '/siebel/db2/instance/siebdev/idx/siebts03_idx4k. dat' 250000,
          >> File '/siebel/db2/instance/siebdev/idx/siebts04_idx4k. dat' 250000)
          >> DB20000I The SET TABLESPACE CONTAINERS command completed
          >> successfully.
          >>
          >> here are the entries from the db2diag.log when the redirected restore
          >> script is started. I don't know if the unexpected end of file is
          >> typical of entries for a redirected restore.
          >>
          >> 2004-09-12-10.07.59.075466 Instance:siebde v Node:000
          >> PID:58916(db2ag ent (SIEBEL) 0) TID:1 Appid:
          >> *LOCAL.siebdev. 00EB32140759
          >> buffer pool services sqlbReadBufferP oolTable Probe:905
          >>
          >> DIA8506C Unexpected end of file was reached.
          >> ZRC=0x870F0009
          >>
          >> Immediately after that entry, I get many, many repeated entries of
          >> ZRC=0xFFFFFBA1 This translates to SQL1119 The restore utility is
          >> most definitely terminated before the restore..to the point where I
          >> have been restarting db2 between runs, so I don't understand this
          >> message.
          >>
          >> SQL1119N A connection to or activation of database "<name>" cannot be
          >> made because a previous restore is incomplete.
          >>
          >> Explanation: The database is in an inconsistent state because a
          >> system error occurred during a restore function.
          >>
          >> No connection was made.
          >>
          >> Federated system users: this situation can be detected by the data
          >> source.
          >>
          >> User Response: Issue the RESTORE command and then try the command
          >> again.
          >>
          >> 2004-09-12-10.07.59.298834 Instance:siebde v Node:000
          >> PID:58916(db2ag ent (SIEBEL) 0) TID:1 Appid:
          >> *LOCAL.siebdev. 00EB32140759
          >> buffer pool services sqlbinit Probe:620
          >>
          >> Database will come up with hidden buffer pools.
          >> totalBufferPool Pages: 0000 0000 0000 0040
          >> .......@
          >>
          >>
          >> 2004-09-12-10.07.59.366280 Instance:siebde v Node:000
          >> PID:58916(db2ag ent (SIEBEL) 0) TID:1 Appid:
          >> *LOCAL.siebdev. 00EB32140759
          >> database utilities sqludPrintStart ingMsg Probe:1 Database:SIEBEL
          >>
          >> Starting a full database restore.
          >> Agent PID: 58916
          >>
          >>
          >> 2004-09-12-10.07.59.823955 Instance:siebde v Node:000
          >> PID:78808(db2bm .58916.0 0) TID:1 Appid:none
          >> database utilities sqludProcessHis toryFile Probe:3
          >>
          >> An empty database history has been detected.
          >> The database history will be overwritten by the backup image.
          >>
          >>
          >> 2004-09-12-10.11.41.039258 Instance:siebde v Node:000
          >> PID:21150(db2ag ent (SIEBEL) 0) TID:1 Appid:
          >> *LOCAL.siebdev. 040912141141
          >> base sys utilities sqleCheckForBac kupRestore Probe:10
          >>
          >> DIA0001E An internal error occurred. Report the following error code
          >> : "ZRC=0xFFFFFBA1 ".
          >>
          >> 2004-09-12-10.11.41.081622 Instance:siebde v Node:000
          >> PID:21150(db2ag ent (SIEBEL) 0) TID:1 Appid:
          >> *LOCAL.siebdev. 040912141141
          >> base sys utilities sqlePrepareForS erialization Probe:20
          >>
          >> DIA0001E An internal error occurred. Report the following error code
          >> : "ZRC=0xFFFFFBA1 ".
          >>
          >> Could these be referring to the image copy of the database?
          >> Also, I am wondering if large file enabling is set on the target
          >> system.[/color]
          >
          >[/color]

          Comment

          • GL

            #6
            Re: Problem with redirected restore -- solved

            Problem is solved. Turns out that deep within the bowels of the diaglog
            there were actually a few error messages that were useful. Sizing was based
            on an inacurate list tablespaces.
            Thanks[color=blue]
            >[/color]

            Comment

            • duoduo

              #7
              Re: Problem with redirected restore

              Hey GL, What's going on with your redirect restore problem? I am
              meeting the same problem and my tablespaces is 64GB 4k page size and I
              can't even extend this tablespace.

              GL <gl@nospam.ne t> wrote in message news:<Xns9562DE AD9FB3Bglnospam net@216.196.97. 131>...[color=blue]
              > Yes the target system has a different file structure but the paths and
              > permissions have all been validated.
              >
              > I am restoring with the user id of the target (into) instance owner.
              >
              > I did drop the db as there is no replace existing in the script.
              >
              > I will check the backup files in the AM
              >
              > Thanks again
              > Gerry
              >
              > "zeb nest" <kariboo1@tisca li.fr> wrote in
              > news:ci1uf9$90f $1@news.tiscali .fr:
              >[color=green]
              > >
              > > Have you made a db2ckbkp on the backup files to check them ?
              > >
              > > perhaps ,the SQL1119 error comes during the different restore after
              > > the first restore KO.
              > > I usualy stop and restart the instance before try to restore the
              > > database. Sometimes, then the restore stop before the end (on a
              > > problem), I drop the database before trying a new restore (If you
              > > don't have the comand "replace exisiting" in your script)
              > >
              > > I see different path before and after the restore
              > > (/db2idx/scioltpt/baseidx/ ->
              > > '/siebel/db2/instance/siebdev/idx/siebts04_idx4k. dat' ). Have you
              > > created the new entire path before the restore ? Are you restoring
              > > with the userid of the instance ?
              > >
              > >
              > > "GL" <gl@nospam.ne t> a écrit dans le message de
              > > news:Xns9562703 6FE10Dglnospamn et@216.196.97.1 31...[color=darkred]
              > >> "zeb nest" <kariboo1@tisca li.fr> wrote in
              > >> news:ci16sa$spk $1@news.tiscali .fr:
              > >>
              > >>
              > >> First, thanks...I really appreciate any thoughts you might have.
              > >>
              > >>
              > >> > Do you have another error messages in the db2diag.log ?
              > >>
              > >> Yes, please see below
              > >>
              > >> > the answer of the ulimit command : are you using the userid of the
              > >> > instance owner ?
              > >>
              > >> Yes
              > >>
              > >>
              > >>
              > >> ? do you have a db2 list tablespaces show detail before the restore ?
              > >>
              > >>
              > >> Yes, this is the tablespace in question of the database being
              > >> restored
              > >>
              > >> Tablespace ID = 5
              > >> Name = TBS_IDX
              > >> Type = Database managed space
              > >> Contents = Any data
              > >> State = 0x0000
              > >> Detailed explanation:
              > >> Normal
              > >> Total pages = 1000000
              > >> Useable pages = 999808
              > >> Used pages = 604864
              > >> Free pages = 394944
              > >> High water mark (pages) = 910720
              > >> Page size (bytes) = 4096
              > >> Extent size (pages) = 32
              > >> Prefetch size (pages) = 128
              > >> Number of containers = 4
              > >> Minimum recovery time = 2004-09-10-12.49.31.000000
              > >>
              > >>
              > >> > do you have a db2 list tablespace containers for x before the
              > >> > restore
              > >>
              > >> Yes
              > >> Tablespace Containers for Tablespace 5
              > >>
              > >> Container ID = 0
              > >> Name =
              > >> /db2idx/scioltpt/baseidx/sieb01
              > >> _idx.dat
              > >> Type = File
              > >>
              > >> Container ID = 1
              > >> Name =
              > >> /db2idx/scioltpt/baseidx/sieb02
              > >> _idx.dat
              > >> Type = File
              > >>
              > >> Container ID = 2
              > >> Name =
              > >> /db2idx/scioltpt/baseidx/sieb03
              > >> _idx.dat
              > >> Type = File
              > >>
              > >> Container ID = 3
              > >> Name =
              > >> /db2idx/scioltpt/baseidx/sieb04
              > >> _idx.dat
              > >> Type = File
              > >>
              > >> This is the way the containers are defined in the restore script
              > >>
              > >> set tablespace containers for 5 using
              > >> (File '/siebel/db2/instance/siebdev/idx/siebts01_idx4k. dat' 250000,
              > >> File '/siebel/db2/instance/siebdev/idx/siebts02_idx4k. dat' 250000,
              > >> File '/siebel/db2/instance/siebdev/idx/siebts03_idx4k. dat' 250000,
              > >> File '/siebel/db2/instance/siebdev/idx/siebts04_idx4k. dat' 250000)
              > >> DB20000I The SET TABLESPACE CONTAINERS command completed
              > >> successfully.
              > >>
              > >> here are the entries from the db2diag.log when the redirected restore
              > >> script is started. I don't know if the unexpected end of file is
              > >> typical of entries for a redirected restore.
              > >>
              > >> 2004-09-12-10.07.59.075466 Instance:siebde v Node:000
              > >> PID:58916(db2ag ent (SIEBEL) 0) TID:1 Appid:
              > >> *LOCAL.siebdev. 00EB32140759
              > >> buffer pool services sqlbReadBufferP oolTable Probe:905
              > >>
              > >> DIA8506C Unexpected end of file was reached.
              > >> ZRC=0x870F0009
              > >>
              > >> Immediately after that entry, I get many, many repeated entries of
              > >> ZRC=0xFFFFFBA1 This translates to SQL1119 The restore utility is
              > >> most definitely terminated before the restore..to the point where I
              > >> have been restarting db2 between runs, so I don't understand this
              > >> message.
              > >>
              > >> SQL1119N A connection to or activation of database "<name>" cannot be
              > >> made because a previous restore is incomplete.
              > >>
              > >> Explanation: The database is in an inconsistent state because a
              > >> system error occurred during a restore function.
              > >>
              > >> No connection was made.
              > >>
              > >> Federated system users: this situation can be detected by the data
              > >> source.
              > >>
              > >> User Response: Issue the RESTORE command and then try the command
              > >> again.
              > >>
              > >> 2004-09-12-10.07.59.298834 Instance:siebde v Node:000
              > >> PID:58916(db2ag ent (SIEBEL) 0) TID:1 Appid:
              > >> *LOCAL.siebdev. 00EB32140759
              > >> buffer pool services sqlbinit Probe:620
              > >>
              > >> Database will come up with hidden buffer pools.
              > >> totalBufferPool Pages: 0000 0000 0000 0040
              > >> .......@
              > >>
              > >>
              > >> 2004-09-12-10.07.59.366280 Instance:siebde v Node:000
              > >> PID:58916(db2ag ent (SIEBEL) 0) TID:1 Appid:
              > >> *LOCAL.siebdev. 00EB32140759
              > >> database utilities sqludPrintStart ingMsg Probe:1 Database:SIEBEL
              > >>
              > >> Starting a full database restore.
              > >> Agent PID: 58916
              > >>
              > >>
              > >> 2004-09-12-10.07.59.823955 Instance:siebde v Node:000
              > >> PID:78808(db2bm .58916.0 0) TID:1 Appid:none
              > >> database utilities sqludProcessHis toryFile Probe:3
              > >>
              > >> An empty database history has been detected.
              > >> The database history will be overwritten by the backup image.
              > >>
              > >>
              > >> 2004-09-12-10.11.41.039258 Instance:siebde v Node:000
              > >> PID:21150(db2ag ent (SIEBEL) 0) TID:1 Appid:
              > >> *LOCAL.siebdev. 040912141141
              > >> base sys utilities sqleCheckForBac kupRestore Probe:10
              > >>
              > >> DIA0001E An internal error occurred. Report the following error code
              > >> : "ZRC=0xFFFFFBA1 ".
              > >>
              > >> 2004-09-12-10.11.41.081622 Instance:siebde v Node:000
              > >> PID:21150(db2ag ent (SIEBEL) 0) TID:1 Appid:
              > >> *LOCAL.siebdev. 040912141141
              > >> base sys utilities sqlePrepareForS erialization Probe:20
              > >>
              > >> DIA0001E An internal error occurred. Report the following error code
              > >> : "ZRC=0xFFFFFBA1 ".
              > >>
              > >> Could these be referring to the image copy of the database?
              > >> Also, I am wondering if large file enabling is set on the target
              > >> system.[/color]
              > >
              > >[/color][/color]

              Comment

              • duoduo

                #8
                Re: Problem with redirected restore -- solved

                good for you. I also solved my problem because of sizing. 16
                containers with 64GB, it is just 100 usable pages less than original.
                change back to 8 containers, everything is okay.
                GL <gl@nospam.ne t> wrote in message news:<Xns9563CE 3346743glnospam net@216.196.97. 131>...[color=blue]
                > Problem is solved. Turns out that deep within the bowels of the diaglog
                > there were actually a few error messages that were useful. Sizing was based
                > on an inacurate list tablespaces.
                > Thanks[color=green]
                > >[/color][/color]

                Comment

                • Dany

                  #9
                  Re: Problem with redirected restore


                  If I am not mistaken the limit filesize for 4k pages is 64GB. To solve this
                  you could use an 8k page tablespace witch could grow to 128 GB (you would
                  also need to create an 8k page buffer pool and temporary tablespace).

                  If you go with 8k pages tablespace make sure that the operating system /file
                  system is supporting file greater than 64GB ... if not build a tablespace
                  with more smaller file.


                  "duoduo" <duoduo.deng@gm ail.com> wrote in message
                  news:d3c653d9.0 409140134.527ec 951@posting.goo gle.com...[color=blue]
                  > Hey GL, What's going on with your redirect restore problem? I am
                  > meeting the same problem and my tablespaces is 64GB 4k page size and I
                  > can't even extend this tablespace.
                  >
                  > GL <gl@nospam.ne t> wrote in message
                  > news:<Xns9562DE AD9FB3Bglnospam net@216.196.97. 131>...[color=green]
                  >> Yes the target system has a different file structure but the paths and
                  >> permissions have all been validated.
                  >>
                  >> I am restoring with the user id of the target (into) instance owner.
                  >>
                  >> I did drop the db as there is no replace existing in the script.
                  >>
                  >> I will check the backup files in the AM
                  >>
                  >> Thanks again
                  >> Gerry
                  >>
                  >> "zeb nest" <kariboo1@tisca li.fr> wrote in
                  >> news:ci1uf9$90f $1@news.tiscali .fr:
                  >>[color=darkred]
                  >> >
                  >> > Have you made a db2ckbkp on the backup files to check them ?
                  >> >
                  >> > perhaps ,the SQL1119 error comes during the different restore after
                  >> > the first restore KO.
                  >> > I usualy stop and restart the instance before try to restore the
                  >> > database. Sometimes, then the restore stop before the end (on a
                  >> > problem), I drop the database before trying a new restore (If you
                  >> > don't have the comand "replace exisiting" in your script)
                  >> >
                  >> > I see different path before and after the restore
                  >> > (/db2idx/scioltpt/baseidx/ ->
                  >> > '/siebel/db2/instance/siebdev/idx/siebts04_idx4k. dat' ). Have you
                  >> > created the new entire path before the restore ? Are you restoring
                  >> > with the userid of the instance ?
                  >> >
                  >> >
                  >> > "GL" <gl@nospam.ne t> a écrit dans le message de
                  >> > news:Xns9562703 6FE10Dglnospamn et@216.196.97.1 31...
                  >> >> "zeb nest" <kariboo1@tisca li.fr> wrote in
                  >> >> news:ci16sa$spk $1@news.tiscali .fr:
                  >> >>
                  >> >>
                  >> >> First, thanks...I really appreciate any thoughts you might have.
                  >> >>
                  >> >>
                  >> >> > Do you have another error messages in the db2diag.log ?
                  >> >>
                  >> >> Yes, please see below
                  >> >>
                  >> >> > the answer of the ulimit command : are you using the userid of the
                  >> >> > instance owner ?
                  >> >>
                  >> >> Yes
                  >> >>
                  >> >>
                  >> >>
                  >> >> ? do you have a db2 list tablespaces show detail before the restore ?
                  >> >>
                  >> >>
                  >> >> Yes, this is the tablespace in question of the database being
                  >> >> restored
                  >> >>
                  >> >> Tablespace ID = 5
                  >> >> Name = TBS_IDX
                  >> >> Type = Database managed space
                  >> >> Contents = Any data
                  >> >> State = 0x0000
                  >> >> Detailed explanation:
                  >> >> Normal
                  >> >> Total pages = 1000000
                  >> >> Useable pages = 999808
                  >> >> Used pages = 604864
                  >> >> Free pages = 394944
                  >> >> High water mark (pages) = 910720
                  >> >> Page size (bytes) = 4096
                  >> >> Extent size (pages) = 32
                  >> >> Prefetch size (pages) = 128
                  >> >> Number of containers = 4
                  >> >> Minimum recovery time = 2004-09-10-12.49.31.000000
                  >> >>
                  >> >>
                  >> >> > do you have a db2 list tablespace containers for x before the
                  >> >> > restore
                  >> >>
                  >> >> Yes
                  >> >> Tablespace Containers for Tablespace 5
                  >> >>
                  >> >> Container ID = 0
                  >> >> Name =
                  >> >> /db2idx/scioltpt/baseidx/sieb01
                  >> >> _idx.dat
                  >> >> Type = File
                  >> >>
                  >> >> Container ID = 1
                  >> >> Name =
                  >> >> /db2idx/scioltpt/baseidx/sieb02
                  >> >> _idx.dat
                  >> >> Type = File
                  >> >>
                  >> >> Container ID = 2
                  >> >> Name =
                  >> >> /db2idx/scioltpt/baseidx/sieb03
                  >> >> _idx.dat
                  >> >> Type = File
                  >> >>
                  >> >> Container ID = 3
                  >> >> Name =
                  >> >> /db2idx/scioltpt/baseidx/sieb04
                  >> >> _idx.dat
                  >> >> Type = File
                  >> >>
                  >> >> This is the way the containers are defined in the restore script
                  >> >>
                  >> >> set tablespace containers for 5 using
                  >> >> (File '/siebel/db2/instance/siebdev/idx/siebts01_idx4k. dat' 250000,
                  >> >> File '/siebel/db2/instance/siebdev/idx/siebts02_idx4k. dat' 250000,
                  >> >> File '/siebel/db2/instance/siebdev/idx/siebts03_idx4k. dat' 250000,
                  >> >> File '/siebel/db2/instance/siebdev/idx/siebts04_idx4k. dat' 250000)
                  >> >> DB20000I The SET TABLESPACE CONTAINERS command completed
                  >> >> successfully.
                  >> >>
                  >> >> here are the entries from the db2diag.log when the redirected restore
                  >> >> script is started. I don't know if the unexpected end of file is
                  >> >> typical of entries for a redirected restore.
                  >> >>
                  >> >> 2004-09-12-10.07.59.075466 Instance:siebde v Node:000
                  >> >> PID:58916(db2ag ent (SIEBEL) 0) TID:1 Appid:
                  >> >> *LOCAL.siebdev. 00EB32140759
                  >> >> buffer pool services sqlbReadBufferP oolTable Probe:905
                  >> >>
                  >> >> DIA8506C Unexpected end of file was reached.
                  >> >> ZRC=0x870F0009
                  >> >>
                  >> >> Immediately after that entry, I get many, many repeated entries of
                  >> >> ZRC=0xFFFFFBA1 This translates to SQL1119 The restore utility is
                  >> >> most definitely terminated before the restore..to the point where I
                  >> >> have been restarting db2 between runs, so I don't understand this
                  >> >> message.
                  >> >>
                  >> >> SQL1119N A connection to or activation of database "<name>" cannot be
                  >> >> made because a previous restore is incomplete.
                  >> >>
                  >> >> Explanation: The database is in an inconsistent state because a
                  >> >> system error occurred during a restore function.
                  >> >>
                  >> >> No connection was made.
                  >> >>
                  >> >> Federated system users: this situation can be detected by the data
                  >> >> source.
                  >> >>
                  >> >> User Response: Issue the RESTORE command and then try the command
                  >> >> again.
                  >> >>
                  >> >> 2004-09-12-10.07.59.298834 Instance:siebde v Node:000
                  >> >> PID:58916(db2ag ent (SIEBEL) 0) TID:1 Appid:
                  >> >> *LOCAL.siebdev. 00EB32140759
                  >> >> buffer pool services sqlbinit Probe:620
                  >> >>
                  >> >> Database will come up with hidden buffer pools.
                  >> >> totalBufferPool Pages: 0000 0000 0000 0040
                  >> >> .......@
                  >> >>
                  >> >>
                  >> >> 2004-09-12-10.07.59.366280 Instance:siebde v Node:000
                  >> >> PID:58916(db2ag ent (SIEBEL) 0) TID:1 Appid:
                  >> >> *LOCAL.siebdev. 00EB32140759
                  >> >> database utilities sqludPrintStart ingMsg Probe:1 Database:SIEBEL
                  >> >>
                  >> >> Starting a full database restore.
                  >> >> Agent PID: 58916
                  >> >>
                  >> >>
                  >> >> 2004-09-12-10.07.59.823955 Instance:siebde v Node:000
                  >> >> PID:78808(db2bm .58916.0 0) TID:1 Appid:none
                  >> >> database utilities sqludProcessHis toryFile Probe:3
                  >> >>
                  >> >> An empty database history has been detected.
                  >> >> The database history will be overwritten by the backup image.
                  >> >>
                  >> >>
                  >> >> 2004-09-12-10.11.41.039258 Instance:siebde v Node:000
                  >> >> PID:21150(db2ag ent (SIEBEL) 0) TID:1 Appid:
                  >> >> *LOCAL.siebdev. 040912141141
                  >> >> base sys utilities sqleCheckForBac kupRestore Probe:10
                  >> >>
                  >> >> DIA0001E An internal error occurred. Report the following error code
                  >> >> : "ZRC=0xFFFFFBA1 ".
                  >> >>
                  >> >> 2004-09-12-10.11.41.081622 Instance:siebde v Node:000
                  >> >> PID:21150(db2ag ent (SIEBEL) 0) TID:1 Appid:
                  >> >> *LOCAL.siebdev. 040912141141
                  >> >> base sys utilities sqlePrepareForS erialization Probe:20
                  >> >>
                  >> >> DIA0001E An internal error occurred. Report the following error code
                  >> >> : "ZRC=0xFFFFFBA1 ".
                  >> >>
                  >> >> Could these be referring to the image copy of the database?
                  >> >> Also, I am wondering if large file enabling is set on the target
                  >> >> system.
                  >> >
                  >> >[/color][/color][/color]


                  Comment

                  • duoduo

                    #10
                    Re: Problem with redirected restore

                    Dany, in my case, I did the redirect restore and changed the 64GB
                    tablespace containers from 8 * 8GB to 16 * 4GB. Unfortunately, the
                    original tablespace had the 16383872 pages "High Water Mark" same as
                    "Usable Pages", once I changed the number of containers, my "Usable
                    Pages" had droped to 16383744, just 128 pages short. I was so sad that
                    the "set container" did not tell me the message until 11 hours later I
                    ran "restore continue". IBM should fix this and doesn't waste our
                    time.


                    "Dany" <danyboy_@video tron.ca> wrote in message news:<ciiakb$11 d1@news1.stadia .fi>...[color=blue]
                    > If I am not mistaken the limit filesize for 4k pages is 64GB. To solve this
                    > you could use an 8k page tablespace witch could grow to 128 GB (you would
                    > also need to create an 8k page buffer pool and temporary tablespace).
                    >
                    > If you go with 8k pages tablespace make sure that the operating system /file
                    > system is supporting file greater than 64GB ... if not build a tablespace
                    > with more smaller file.
                    >
                    >
                    > "duoduo" <duoduo.deng@gm ail.com> wrote in message
                    > news:d3c653d9.0 409140134.527ec 951@posting.goo gle.com...[color=green]
                    > > Hey GL, What's going on with your redirect restore problem? I am
                    > > meeting the same problem and my tablespaces is 64GB 4k page size and I
                    > > can't even extend this tablespace.
                    > >
                    > > GL <gl@nospam.ne t> wrote in message
                    > > news:<Xns9562DE AD9FB3Bglnospam net@216.196.97. 131>...[color=darkred]
                    > >> Yes the target system has a different file structure but the paths and
                    > >> permissions have all been validated.
                    > >>
                    > >> I am restoring with the user id of the target (into) instance owner.
                    > >>
                    > >> I did drop the db as there is no replace existing in the script.
                    > >>
                    > >> I will check the backup files in the AM
                    > >>
                    > >> Thanks again
                    > >> Gerry
                    > >>
                    > >> "zeb nest" <kariboo1@tisca li.fr> wrote in
                    > >> news:ci1uf9$90f $1@news.tiscali .fr:
                    > >>
                    > >> >
                    > >> > Have you made a db2ckbkp on the backup files to check them ?
                    > >> >
                    > >> > perhaps ,the SQL1119 error comes during the different restore after
                    > >> > the first restore KO.
                    > >> > I usualy stop and restart the instance before try to restore the
                    > >> > database. Sometimes, then the restore stop before the end (on a
                    > >> > problem), I drop the database before trying a new restore (If you
                    > >> > don't have the comand "replace exisiting" in your script)
                    > >> >
                    > >> > I see different path before and after the restore
                    > >> > (/db2idx/scioltpt/baseidx/ ->
                    > >> > '/siebel/db2/instance/siebdev/idx/siebts04_idx4k. dat' ). Have you
                    > >> > created the new entire path before the restore ? Are you restoring
                    > >> > with the userid of the instance ?
                    > >> >
                    > >> >
                    > >> > "GL" <gl@nospam.ne t> a écrit dans le message de
                    > >> > news:Xns9562703 6FE10Dglnospamn et@216.196.97.1 31...
                    > >> >> "zeb nest" <kariboo1@tisca li.fr> wrote in
                    > >> >> news:ci16sa$spk $1@news.tiscali .fr:
                    > >> >>
                    > >> >>
                    > >> >> First, thanks...I really appreciate any thoughts you might have.
                    > >> >>
                    > >> >>
                    > >> >> > Do you have another error messages in the db2diag.log ?
                    > >> >>
                    > >> >> Yes, please see below
                    > >> >>
                    > >> >> > the answer of the ulimit command : are you using the userid of the
                    > >> >> > instance owner ?
                    > >> >>
                    > >> >> Yes
                    > >> >>
                    > >> >>
                    > >> >>
                    > >> >> ? do you have a db2 list tablespaces show detail before the restore ?
                    > >> >>
                    > >> >>
                    > >> >> Yes, this is the tablespace in question of the database being
                    > >> >> restored
                    > >> >>
                    > >> >> Tablespace ID = 5
                    > >> >> Name = TBS_IDX
                    > >> >> Type = Database managed space
                    > >> >> Contents = Any data
                    > >> >> State = 0x0000
                    > >> >> Detailed explanation:
                    > >> >> Normal
                    > >> >> Total pages = 1000000
                    > >> >> Useable pages = 999808
                    > >> >> Used pages = 604864
                    > >> >> Free pages = 394944
                    > >> >> High water mark (pages) = 910720
                    > >> >> Page size (bytes) = 4096
                    > >> >> Extent size (pages) = 32
                    > >> >> Prefetch size (pages) = 128
                    > >> >> Number of containers = 4
                    > >> >> Minimum recovery time = 2004-09-10-12.49.31.000000
                    > >> >>
                    > >> >>
                    > >> >> > do you have a db2 list tablespace containers for x before the
                    > >> >> > restore
                    > >> >>
                    > >> >> Yes
                    > >> >> Tablespace Containers for Tablespace 5
                    > >> >>
                    > >> >> Container ID = 0
                    > >> >> Name =
                    > >> >> /db2idx/scioltpt/baseidx/sieb01
                    > >> >> _idx.dat
                    > >> >> Type = File
                    > >> >>
                    > >> >> Container ID = 1
                    > >> >> Name =
                    > >> >> /db2idx/scioltpt/baseidx/sieb02
                    > >> >> _idx.dat
                    > >> >> Type = File
                    > >> >>
                    > >> >> Container ID = 2
                    > >> >> Name =
                    > >> >> /db2idx/scioltpt/baseidx/sieb03
                    > >> >> _idx.dat
                    > >> >> Type = File
                    > >> >>
                    > >> >> Container ID = 3
                    > >> >> Name =
                    > >> >> /db2idx/scioltpt/baseidx/sieb04
                    > >> >> _idx.dat
                    > >> >> Type = File
                    > >> >>
                    > >> >> This is the way the containers are defined in the restore script
                    > >> >>
                    > >> >> set tablespace containers for 5 using
                    > >> >> (File '/siebel/db2/instance/siebdev/idx/siebts01_idx4k. dat' 250000,
                    > >> >> File '/siebel/db2/instance/siebdev/idx/siebts02_idx4k. dat' 250000,
                    > >> >> File '/siebel/db2/instance/siebdev/idx/siebts03_idx4k. dat' 250000,
                    > >> >> File '/siebel/db2/instance/siebdev/idx/siebts04_idx4k. dat' 250000)
                    > >> >> DB20000I The SET TABLESPACE CONTAINERS command completed
                    > >> >> successfully.
                    > >> >>
                    > >> >> here are the entries from the db2diag.log when the redirected restore
                    > >> >> script is started. I don't know if the unexpected end of file is
                    > >> >> typical of entries for a redirected restore.
                    > >> >>
                    > >> >> 2004-09-12-10.07.59.075466 Instance:siebde v Node:000
                    > >> >> PID:58916(db2ag ent (SIEBEL) 0) TID:1 Appid:
                    > >> >> *LOCAL.siebdev. 00EB32140759
                    > >> >> buffer pool services sqlbReadBufferP oolTable Probe:905
                    > >> >>
                    > >> >> DIA8506C Unexpected end of file was reached.
                    > >> >> ZRC=0x870F0009
                    > >> >>
                    > >> >> Immediately after that entry, I get many, many repeated entries of
                    > >> >> ZRC=0xFFFFFBA1 This translates to SQL1119 The restore utility is
                    > >> >> most definitely terminated before the restore..to the point where I
                    > >> >> have been restarting db2 between runs, so I don't understand this
                    > >> >> message.
                    > >> >>
                    > >> >> SQL1119N A connection to or activation of database "<name>" cannot be
                    > >> >> made because a previous restore is incomplete.
                    > >> >>
                    > >> >> Explanation: The database is in an inconsistent state because a
                    > >> >> system error occurred during a restore function.
                    > >> >>
                    > >> >> No connection was made.
                    > >> >>
                    > >> >> Federated system users: this situation can be detected by the data
                    > >> >> source.
                    > >> >>
                    > >> >> User Response: Issue the RESTORE command and then try the command
                    > >> >> again.
                    > >> >>
                    > >> >> 2004-09-12-10.07.59.298834 Instance:siebde v Node:000
                    > >> >> PID:58916(db2ag ent (SIEBEL) 0) TID:1 Appid:
                    > >> >> *LOCAL.siebdev. 00EB32140759
                    > >> >> buffer pool services sqlbinit Probe:620
                    > >> >>
                    > >> >> Database will come up with hidden buffer pools.
                    > >> >> totalBufferPool Pages: 0000 0000 0000 0040
                    > >> >> .......@
                    > >> >>
                    > >> >>
                    > >> >> 2004-09-12-10.07.59.366280 Instance:siebde v Node:000
                    > >> >> PID:58916(db2ag ent (SIEBEL) 0) TID:1 Appid:
                    > >> >> *LOCAL.siebdev. 00EB32140759
                    > >> >> database utilities sqludPrintStart ingMsg Probe:1 Database:SIEBEL
                    > >> >>
                    > >> >> Starting a full database restore.
                    > >> >> Agent PID: 58916
                    > >> >>
                    > >> >>
                    > >> >> 2004-09-12-10.07.59.823955 Instance:siebde v Node:000
                    > >> >> PID:78808(db2bm .58916.0 0) TID:1 Appid:none
                    > >> >> database utilities sqludProcessHis toryFile Probe:3
                    > >> >>
                    > >> >> An empty database history has been detected.
                    > >> >> The database history will be overwritten by the backup image.
                    > >> >>
                    > >> >>
                    > >> >> 2004-09-12-10.11.41.039258 Instance:siebde v Node:000
                    > >> >> PID:21150(db2ag ent (SIEBEL) 0) TID:1 Appid:
                    > >> >> *LOCAL.siebdev. 040912141141
                    > >> >> base sys utilities sqleCheckForBac kupRestore Probe:10
                    > >> >>
                    > >> >> DIA0001E An internal error occurred. Report the following error code
                    > >> >> : "ZRC=0xFFFFFBA1 ".
                    > >> >>
                    > >> >> 2004-09-12-10.11.41.081622 Instance:siebde v Node:000
                    > >> >> PID:21150(db2ag ent (SIEBEL) 0) TID:1 Appid:
                    > >> >> *LOCAL.siebdev. 040912141141
                    > >> >> base sys utilities sqlePrepareForS erialization Probe:20
                    > >> >>
                    > >> >> DIA0001E An internal error occurred. Report the following error code
                    > >> >> : "ZRC=0xFFFFFBA1 ".
                    > >> >>
                    > >> >> Could these be referring to the image copy of the database?
                    > >> >> Also, I am wondering if large file enabling is set on the target
                    > >> >> system.
                    > >> >
                    > >> >[/color][/color][/color]

                    Comment

                    Working...