8 Replies Latest reply: Jan 16, 2012 6:08 AM by rdoogan-Oracle RSS

    OSB encounters error in Windows and is closed

    Adam J. Sawyer
      Hi,

      We are using OSB on a number of our servers but on one server the program/service keeps having errors and closing - we get the rather uninformative windows error "Oracle Secure Backup has encountered a problem and needs to close..." The server is an Oracle Application 10.1.2.0.2 application server using a 10.2.0.4 database for infrastructure. We are using Windows Server 2003 R2 and OSB 10.0.3. Can anyone advise what I can do to diagnose this issue - it only happens on this one server and it's the Production one. I've checked and can't find any evidence that there is any Commvault or Backup Exec software left on the server.

      Thanks
      Adam

      Edited by: Adam J. Sawyer on 31-Jan-2010 20:05

      Edited by: Adam J. Sawyer on 31-Jan-2010 20:45
        • 1. Re: OSB encounters error in Windows and is closed
          rdoogan-Oracle
          Hi, please can you do "obtar -V" to confirm the OSB version you are running?

          C:\> obtar -V
          obtar version 10.3.0.1.0 . (nt) -- Mon May 4 23:08:09 CDT 2009
          Copyright (c) 1992, 2009, Oracle. All rights reserved.


          Thanks



          Rich
          • 2. Re: OSB encounters error in Windows and is closed
            Adam J. Sawyer
            Hi,

            Here is the output of that command:
            ---------------------------------------------------
            E:\oracle\product\osb_103\bin>obtar -V
            obtar version 10.3.0.1.0 . (nt) -- Mon May 4 23:08:09 CDT 2009
            Copyright (c) 1992, 2009, Oracle. All rights reserved.
            --------------------------------------------------

            Thanks
            Adam
            • 3. Re: OSB encounters error in Windows and is closed
              Adam J. Sawyer
              An extract from the observiced.log file
              -----------------------------------------------------
              2010/02/01.11:54:26 observiced version 10.3.0.1.0 . (nt) -- Mon May 4 23:10:07 CDT 2009
              Copyright (c) 1992, 2009, Oracle. All rights reserved. on agspsrap03 (domain AGRIC) pid 1192
              2010/02/01.11:54:26 installed as server
              2010/02/01.11:54:26 listening for requests on port 400, interfaces:
              2010/02/01.11:54:26 00-50-56-AA-11-5E (159.207.200.61)
              2010/02/01.11:54:37 can't decode interface list "" - bad interface list format (FSP network database manager)
              2010/02/01.11:54:37 daemon cmd "obproxyd.exe -D" failed - daemon failed to initialize properly (OB service daemon)
              2010/02/01.11:54:37 unable to start obproxyd - daemon failed to initialize properly (OB service daemon)
              2010/02/01.11:54:37 listening for NDMP connections on port 10000, interfaces:
              2010/02/01.11:54:37 00-50-56-AA-11-5E (159.207.200.61)
              2010/02/01.11:54:38 can't decode interface list "" - bad interface list format (FSP network database manager)
              2010/02/01.11:54:38 daemon cmd "obproxyd.exe -D" failed - daemon failed to initialize properly (OB service daemon)
              2010/02/01.11:54:38 unable to start obproxyd - daemon failed to initialize properly (OB service daemon)
              2010/02/01.11:54:38 obproxyd -D pid 9096 exited with code 0x20008F06, value 1
              2010/02/01.11:54:38 obproxyd -D pid 2028 exited with code 0x20008F06, value 1
              2010/02/01.11:54:41 Unknown request from service manager
              -------------------------------------------------------
              • 4. Re: OSB encounters error in Windows and is closed
                Adam J. Sawyer
                An extract from the obroxyd.log file
                ---------------------------------------------------
                file
                2010/01/29.07:48:13 can't listen for connections - All pipe instances are busy.
                2010/01/29.07:48:14 can't listen for connections - All pipe instances are busy.

                2010/01/29.12:13:44 pruned log file
                2010/01/29.20:38:23 can't listen for connections - All pipe instances are busy.
                2010/01/29.20:38:24 can't listen for connections - All pipe instances are busy.
                2010/01/30.12:13:59 pruned log file

                2010/01/31.12:14:26 pruned log file
                2010/02/01.11:53:27 can't listen for connections - All pipe instances are busy.
                2010/02/01.11:53:27 can't listen for connections - All pipe instances are busy.
                2010/02/01.11:54:37 can't listen for connections - All pipe instances are busy.
                2010/02/01.11:54:38 can't listen for connections - All pipe instances are busy.

                2010/02/01.12:14:26 pruned log file
                ------------------------------------------------------

                I hope you can help

                Thanks
                Adam
                • 5. Re: OSB encounters error in Windows and is closed
                  rdoogan-Oracle
                  Yeah I too had the "can't decode interface list "" - bad interface list format (FSP network database manager)" error on some systems. I rebooted them and then they were all OK, so try that.



                  Rich
                  • 6. Re: OSB encounters error in Windows and is closed
                    Adam J. Sawyer
                    Hi,

                    Unfortunately the problem with this app server has been lingering for months and we've rebooted it numerous times.

                    Thanks
                    Adam
                    • 7. Re: OSB encounters error in Windows and is closed
                      OraInsights
                      Hi,
                      have you ever resolved the issue? I'm encountering the same exact issue.
                      Thanks,
                      Ido
                      • 8. Re: OSB encounters error in Windows and is closed
                        rdoogan-Oracle
                        Hi, this thread is quite old. Please make sure you are running the latest 10.4.0.1.0 release of OSB and then post a new thread with whatever the issue is, and then we can look into it.

                        Thanks

                        Rich