9 Replies Latest reply on Jul 30, 2008 9:35 AM by MarXtar

    Database exception: SCA90.SCN, LDInv.dll - ORA-03114: not connected to ORACLE (null)

    Rookie

       

      Dear Friends,

       

      I have one a error type as this event viewer on my client windows  connect to IBM-AIX

       

       

      Event Type:Error

       

       

       

      Event Source:LANDesk Inventory Server

       

       

       

      Event Category: None

       

       

       

      Event ID:4100

       

       

       

      Date:7/29/2008

       

       

       

      Time: 9:58:04AM

       

       

       

      User: N/A

       

       

       

      Computer: ESLQXXX

       

       

       

       

       

       

       

       

       

       

       

       

       

      Description: Database exception: SCA90.SCN, LDInv.dll - 2147217900 ORA-03114: not connected to ORACLE (null), Thread ID: 3584

       

       

       

       

       

      What do I do...?

       

       

      TKS

       

       

      Salvatore

       

       

        • 1. Re: Database exception: SCA90.SCN, LDInv.dll - ORA-03114: not connected to ORACLE (null)
          MarXtar ITSMMVPGroup

           

          Get rid of Oracle, go to SQL and have a much easier time with LANDesk support in the future.

           

           

          Surely that has to count as a helpful answer?

           

           

          Alternativel, sounds like the DB connection got dropped.  Is it working again now?

           

           

          • 2. Re: Database exception: SCA90.SCN, LDInv.dll - ORA-03114: not connected to ORACLE (null)
            Rookie

             

            Is not helpful answer.

             

             

            No, my question has not been answered yet.

             

             

            Tks

             

             

            • 3. Re: Database exception: SCA90.SCN, LDInv.dll - ORA-03114: not connected to ORACLE (null)
              MarXtar ITSMMVPGroup

              There was actually a serious part to that post. You didn't say if you had no cnnection at all or if this was a one-off issue.

               

              http://ora-3114.ora-code.com/

               

              This link says this is often linked to a drop in connection. Perhaps the network link was lost for a short time.

               

              If it is working again now it is probably this, just ask your dba to keep an eye on the database. If it is a permanent loss then is your database still available?

               

              I am quite serious about oracle though. Its is difficult to support unless you have a dba at your disposal. You are better in the long run to go with sql if you are not an oracle expert and there is nothing forcing you to go oracle. This is not saying ms-sql is a better product, just that the number of people that can support you is probably upwards of 50 to 1 in favour of ms-sql.

              • 4. Re: Database exception: SCA90.SCN, LDInv.dll - ORA-03114: not connected to ORACLE (null)
                Rookie

                 

                On my client the request is:

                 

                 

                Event Type:       Error

                 

                 

                Event Source:   .NET Runtime 2.0 Error Reporting

                 

                 

                Event Category: None

                 

                 

                Event ID:           1000

                 

                 

                Date:               7/29/2008

                 

                 

                Time:               9:58:09 AM

                 

                 

                User:               N/A

                 

                 

                Computer:        ESLXXX

                 

                 

                Description:

                 

                 

                Faulting application ldinv32.exe, version 8.80.1.3, stamp 47e7b980, faulting module ldinv32.exe, version 8.80.1.3, stamp 47e7b980, debug? 0, fault address 0x0009fca4.

                 

                 

                 

                 

                 

                For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

                 

                 

                Data:

                 

                 

                0000: 41 00 70 00 70 00 6c 00   A.p.p.l.

                 

                 

                0008: 69 00 63 00 61 00 74 00   i.c.a.t.

                 

                 

                0010: 69 00 6f 00 6e 00 20 00   i.o.n. .

                 

                 

                0018: 46 00 61 00 69 00 6c 00   F.a.i.l.

                 

                 

                0020: 75 00 72 00 65 00 20 00   u.r.e. .

                 

                 

                0028: 20 00 6c 00 64 00 69 00    .l.d.i.

                 

                 

                0030: 6e 00 76 00 33 00 32 00   n.v.3.2.

                 

                 

                0038: 2e 00 65 00 78 00 65 00   ..e.x.e.

                 

                 

                0040: 20 00 38 00 2e 00 38 00    .8...8.

                 

                 

                0048: 30 00 2e 00 31 00 2e 00   0...1...

                 

                 

                0050: 33 00 20 00 34 00 37 00   3. .4.7.

                 

                 

                0058: 65 00 37 00 62 00 39 00   e.7.b.9.

                 

                 

                0060: 38 00 30 00 20 00 69 00   8.0. .i.

                 

                 

                0068: 6e 00 20 00 6c 00 64 00   n. .l.d.

                 

                 

                0070: 69 00 6e 00 76 00 33 00   i.n.v.3.

                 

                 

                0078: 32 00 2e 00 65 00 78 00   2...e.x.

                 

                 

                0080: 65 00 20 00 38 00 2e 00   e. .8...

                 

                 

                0088: 38 00 30 00 2e 00 31 00   8.0...1.

                 

                 

                0090: 2e 00 33 00 20 00 34 00   ..3. .4.

                 

                 

                0098: 37 00 65 00 37 00 62 00   7.e.7.b.

                 

                 

                00a0: 39 00 38 00 30 00 20 00   9.8.0. .

                 

                 

                00a8: 66 00 44 00 65 00 62 00   f.D.e.b.

                 

                 

                00b0: 75 00 67 00 20 00 30 00   u.g. .0.

                 

                 

                00b8: 20 00 61 00 74 00 20 00    .a.t. .

                 

                 

                00c0: 6f 00 66 00 66 00 73 00   o.f.f.s.

                 

                 

                00c8: 65 00 74 00 20 00 30 00   e.t. .0.

                 

                 

                00d0: 30 00 30 00 39 00 66 00   0.0.9.f.

                 

                 

                00d8: 63 00 61 00 34 00 0d 00   c.a.4...

                 

                 

                00e0: 0a 00                    ..

                 

                 

                What do you think of this response error...?

                 

                 

                • 5. Re: Database exception: SCA90.SCN, LDInv.dll - ORA-03114: not connected to ORACLE (null)
                  Rookie

                   

                  Analizing again the event viewer, we guess that could be a relationship between the error and a crash of a remote console.

                   

                   

                  Could be this a reason of the problem?

                   

                   

                   

                   

                   

                  Thanks  

                   

                   

                  • 6. Re: Database exception: SCA90.SCN, LDInv.dll - ORA-03114: not connected to ORACLE (null)
                    MarXtar ITSMMVPGroup

                    Unlikely. The module faulting is the inventory service on the core server. This might be as a result of the lost connection. Does this error happen before or after the oracle error?

                    • 7. Re: Database exception: SCA90.SCN, LDInv.dll - ORA-03114: not connected to ORACLE (null)
                      phoffmann SupportEmployee

                      Well - anything "could" be ... but I don't think it likely.

                       

                      That remote console would've had to take the entire Oracle Instance with it (or at least max its utilisation to silly levels), so as to make it unresponsive and unavailable to the rest of LANDesk.

                       

                      32-bit Consoles don't talk to the services per se, and are quite independent of them (a 32-bit Console will start quite happily on the Core when all other LANDesk/Intel Services are stopped). One way or the other it means "Inventory Service could not talk to the DB really" - so if this is something that happens regularly, you definately will want to have a DBA of yours look at this ... the Inventory service is simply complaining "it isn't there".

                       

                      Paul Hoffmann

                      LANDesk EMEA Technical Lead.

                      • 8. Re: Database exception: SCA90.SCN, LDInv.dll - ORA-03114: not connected to ORACLE (null)
                        phoffmann SupportEmployee

                        Or - put another way - If you DO use Oracle, do make sure you have an Oracle DBA (at this point, I assume you do).

                         

                        The error message is pretty normal for the Inventory Service when it doesn't have a DB to talk to. Which is what pretty much what this thread is about.

                         

                        1 - Inventory Service tries to process scan.

                        2 - This fails - because the DB is down/dead/whatever - scan is rejected (one event)

                         

                        3 - Some time later - Inventory Service decides to die, because it cannot reconnect to the DB and gives up.

                         

                        So this can range from networking problems to actual DB problems to "it was being backed up and we forgot to tell people that this is our maintenance window where we take the DB down" (yeah, I've seen that too). Either way, your DBA is the first person to ask.

                         

                        LANDesk is just the "vocal" symptom - the cause is the DB being unavailable. That's the source you need to go look at. LANDesk is just "loud" (or visible) in its complaining :).

                         

                        Paul Hoffmann

                        LANDesk EMEA Technical Lead.

                        • 9. Re: Database exception: SCA90.SCN, LDInv.dll - ORA-03114: not connected to ORACLE (null)
                          MarXtar ITSMMVPGroup

                          Methinks Paul has had his fair share of Oracle pain too.

                           

                          Talk to your DBA. Its amazing what they often forget to tell you about when they don't consider your database mission critical.