1. This site uses cookies. By continuing to use this site, you are agreeing to our use of cookies. Learn More.

Remote Device Error During Prorest.

Discussion in 'Database Admin' started by Jack@dba, Jul 21, 2017.

  1. Jack@dba

    Jack@dba Member

    HI All,

    We have created one test database using prod backup to analysis the issue.
    After creating database i not able to start that database.
    I have seen below errors during the database startup.
    Can i know what exactly the issue.
    Is our Backup got corrupted ?
    How to resolve this errors and start this database.

    Please find below for steps we followed

    Thu Jul 20 15:27:44 2017

    15:27:44 prostrct create session begin for pgresdba on /dev/pts/2. (451)

    15:27:45 prostrct create session end. (334)

    Thu Jul 20 15:28:23 2017

    15:28:23 procopy session begin for pgresdba on /dev/pts/2. (451)

    15:28:24 procopy session end. (334)

    Thu Jul 20 15:28:24 2017

    15:28:24 procopy get default SQL DBA session begin for pgresdba on /dev/pts/2. (451)

    15:28:24 procopy get default SQL DBA session end. (334)

    Thu Jul 20 15:30:35 2017

    15:30:35 prorest session begin for pgresdba on /dev/pts/2. (451)

    15:30:41 Full restore started. (1368)

    15:57:09 Full restore completed. (1369)

    15:57:10 prorest session end. (334)

    Thu Jul 20 16:08:18 2017

    16:08:18 BROKER 0: File /progdata/bkup/test/prdcrn_tst.db is on a remote device. (9466)

    16:08:18 BROKER 0: File /progdata/bkup/test/prdcrn_tst.d1 is on a remote device. (9466)

    16:08:18 BROKER 0: File /progdata/bkup/test/prdcrn_tst.d2 is on a remote device. (9466)

    16:08:18 BROKER 0: File /progdata/bkup/test/prdcrn_tst.d3 is on a remote device. (9466)

    16:08:18 BROKER 0: File /progdata/bkup/test/prdcrn_tst.d4 is on a remote device. (9466)

    16:08:18 BROKER 0: File /progdata/bkup/test/prdcrn_tst.d5 is on a remote device. (9466)

    16:08:18 BROKER 0: File /progdata/bkup/test/prdcrn_tst.d6 is on a remote device. (9466)

    16:08:18 BROKER 0: File /progdata/bkup/test/prdcrn_tst.d7 is on a remote device. (9466)

    16:08:18 BROKER 0: File /progdata/bkup/test/prdcrn_tst.d8 is on a remote device. (9466)

    16:08:18 BROKER 0: File /progdata/bkup/test/prdcrn_tst.d9 is on a remote device. (9466)

    16:08:18 BROKER 0: File /progdata/bkup/test/prdcrn_tst.d10 is on a remote device. (9466)
     
  2.  
  3. Rob Fitzpatrick

    Rob Fitzpatrick ProgressTalk.com Sponsor

    It would be helpful to see your command lines, not just their output.
     
  4. Jack@dba

    Jack@dba Member

    HI Rob,

    we have refreshed test database with prob database backup.

    After refresh completed we tried to start database with proserve.
    proserve dbname.
    These are errors identified during db startup.
    Any idea during which conditions we will face these errors.

    16:08:18 BROKER 0: File /progdata/bkup/test/prdcrn_tst.db is on a remote device. (9466)

    16:08:18 BROKER 0: File /progdata/bkup/test/prdcrn_tst.d1 is on a remote device. (9466)

    16:08:18 BROKER 0: File /progdata/bkup/test/prdcrn_tst.d2 is on a remote device. (9466)

    16:08:18 BROKER 0: File /progdata/bkup/test/prdcrn_tst.d3 is on a remote device. (9466)

    16:08:18 BROKER 0: File /progdata/bkup/test/prdcrn_tst.d4 is on a remote device. (9466)

    16:08:18 BROKER 0: File /progdata/bkup/test/prdcrn_tst.d5 is on a remote device. (9466)
     
  5. TomBascom

    TomBascom Curmudgeon

    You have failed to mention the version of Progress and the OS platform.

    The messages look like v9 (or earlier) and some sort of UNIX -- but that's just a guess. If that guess is correct then you should be aware that v9 is ancient, obsolete and unsupported. It is irresponsible, unprofessional and a disservice to the business to be running version 9.

    The message means that Progress believes that your database is on a network share.

    If Progress is correct then this warning is something that you should take seriously -- it is not a good idea to do this. IO to network shares is substantially less reliable than IO to local devices. You can expect data corruption as a reward.

    Under some circumstances and combinations of platform/progress version it is possible to start a database on an NFS mounted filesystem. It is occasionally useful to do this temporarily, perhaps as a step in a migration process, but it is never a good idea to make a habit of it.
     
    Last edited: Jul 24, 2017
    Cringer likes this.

Share This Page