10 Replies Latest reply on May 20, 2016 12:38 PM by happy10319

    APP-FND-01516

    ViganQ

      Hello community,

       

      The past couple of days, and today when I have received this error: APP-FND-01516.

       

      It is ocurring when I first start working on EBS. I go to log-in page, it displays correctly, i log in, and when I want to use the Apps for example run a concurrent program to generate a report, together with the applications window this error appears. APP-FND-01516.

      App-Fnd-01516 screenshot.png

       

      I have encountered this problem before, and I usually restarted the server where EBS is installed and it started working again.
      But I have never had this problem for 3 days in a row, and I was wondering what might be the cause of it, and is there a better way to handle this error.

       

      Thanks in advance.

        • 1. Re: APP-FND-01516
          Poorvika

          Hello,

           

          Do you find any errors in the database alert log?

          • 2. Re: APP-FND-01516
            ViganQ

            Where can I find that log?

            • 3. Re: APP-FND-01516
              Poorvika

              1) Login to Database server

              2) connect as  sysdba

              sqlplus '/as sysdba'

               

              3) Check the value for background_dump_dest

              SQL > show parameter background_dump_dest

               

              4) Navigate to the above location and search for alert  log file

              ls alert*

               

              Check for any ORA errors in alert log

              • 4. Re: APP-FND-01516
                ViganQ

                Found the DB alert log, but it's pretty big... any idea on what I should be looking for?

                • 5. Re: APP-FND-01516
                  Srini Chavali-Oracle

                  Pl post OS, database and EBS versions. Does this happen for all users ? MOS Doc 1219833.1 may be relevant

                  • 6. Re: APP-FND-01516
                    Poorvika

                    Grep for ORA errors.

                    Tail the alert log file

                     

                    What is the EBS and database version?

                    • 7. Re: APP-FND-01516
                      ViganQ

                      I have:

                      EBS version: 12.1.1

                      DB version: 10.2.0.3.0

                       

                      I did not find any ORA errors in the logs, the last ORA errors date was 1 year ago.


                      However, while reviewing the logs I saw this:

                       

                      Wed May 18 15:46:29 2016

                      Process q005 died, see its trace file

                      Wed May 18 15:46:29 2016

                      ksvcreate: Process(q005) creation failed

                      Wed May 18 15:47:10 2016

                      Process J000 died, see its trace file

                      Wed May 18 15:47:10 2016

                      kkjcre1p: unable to spawn jobq slave process

                      Wed May 18 15:47:10 2016

                      Errors in file d:\oracle\proddb\10.2.0\admin\prod_prod\bdump\prod_cjq0_4696.trc:

                       

                       

                      Wed May 18 15:50:51 2016

                      Incremental checkpoint up to RBA [0x37fba.22e9.0], current log tail at RBA [0x37fba.2423.0]

                      Wed May 18 16:00:15 2016

                      Beginning log switch checkpoint up to RBA [0x37fbb.2.10], SCN: 11444561633

                      Thread 1 advanced to log sequence 229307

                        Current log# 2 seq# 229307 mem# 0: D:\ORACLE\PRODDATA\LOG02A.DBF

                        Current log# 2 seq# 229307 mem# 1: D:\ORACLE\PRODDATA\LOG02B.DBF

                      Wed May 18 16:00:49 2016

                      Process m001 died, see its trace file

                      Wed May 18 16:00:49 2016

                      ksvcreate: Process(m001) creation failed

                      Wed May 18 16:05:21 2016

                      Completed checkpoint up to RBA [0x37fbb.2.10], SCN: 11444561633

                      Wed May 18 16:10:51 2016

                      Incremental checkpoint up to RBA [0x37fbb.a6f.0], current log tail at RBA [0x37fbb.bf1.0]

                      Wed May 18 16:24:42 2016

                      Process q004 died, see its trace file

                      Wed May 18 16:24:42 2016

                      ksvcreate: Process(q004) creation failed

                      Wed May 18 16:30:51 2016

                      Incremental checkpoint up to RBA [0x37fbb.17c6.0], current log tail at RBA [0x37fbb.190f.0]

                      Wed May 18 16:50:51 2016

                      Incremental checkpoint up to RBA [0x37fbb.1d4e.0], current log tail at RBA [0x37fbb.1e58.0]

                      Wed May 18 17:00:33 2016

                      Process m000 died, see its trace file

                      Wed May 18 17:00:33 2016

                      ksvcreate: Process(m000) creation failed

                      Wed May 18 17:01:34 2016

                      Process m000 died, see its trace file

                      Wed May 18 17:01:34 2016

                      ksvcreate: Process(m000) creation failed

                      Wed May 18 17:02:35 2016

                      Process m000 died, see its trace file

                      Wed May 18 17:02:35 2016

                      ksvcreate: Process(m000) creation failed

                      Wed May 18 17:02:58 2016

                      Process q004 died, see its trace file

                      Wed May 18 17:02:58 2016

                      ksvcreate: Process(q004) creation failed

                      Wed May 18 17:03:36 2016

                      Process m000 died, see its trace file

                      Wed May 18 17:03:36 2016

                      ksvcreate: Process(m000) creation failed

                      Wed May 18 17:04:37 2016

                      Process m000 died, see its trace file

                      Wed May 18 17:04:37 2016

                      ksvcreate: Process(m000) creation failed

                      Wed May 18 17:05:38 2016

                      Process m000 died, see its trace file

                      Wed May 18 17:05:38 2016

                      ksvcreate: Process(m000) creation failed

                       

                      This continues until I restart the server and then everything works.
                      You can see the same thing happen for the 4 days now, and today when I opened the log-in page, this was the display:
                      Screenshot_1.jpg


                      I did restart the server, and now everything works.

                       

                      Since in the logs this appeard d:\oracle\proddb\10.2.0\admin\prod_prod\bdump\prod_cjq0_4696.trc:     I took a look at it.
                      Here is it's content:

                      Dump file d:\oracle\proddb\10.2.0\admin\prod_prod\bdump\prod_cjq0_4696.trc

                      Wed May 18 15:47:10 2016

                      ORACLE V10.2.0.3.0 - Production vsnsta=0

                      vsnsql=14 vsnxtr=3

                      Oracle Database 10g Enterprise Edition Release 10.2.0.3.0 - Production

                      With the Partitioning, OLAP and Data Mining options

                      Windows Server 2003 Version V5.2 Service Pack 1

                      CPU                 : 4 - type 586, 4 Physical Cores

                      Process Affinity    : 0x00000000

                      Memory (Avail/Total): Ph:1087M/4095M, Ph+PgF:12748M/16071M, VA:679M/3071M

                      Instance name: prod

                       

                      Redo thread mounted by this instance: 1

                       

                      Oracle process number: 10

                       

                      Windows thread id: 4696, image: ORACLE.EXE (CJQ0)

                       

                       

                      *** SERVICE NAME:(SYS$BACKGROUND) 2016-05-18 15:47:10.718

                      *** SESSION ID:(392.1) 2016-05-18 15:47:10.718

                      *** 2016-05-18 15:47:10.718

                      Process J000 is dead (pid=5168, state=3):

                      *** 2016-05-18 20:02:17.062

                      Process J000 is dead (pid=7280, state=3):

                      *** 2016-05-18 20:53:23.078

                      Process J001 is dead (pid=8188, state=3):

                      *** 2016-05-19 00:02:34.750

                      Process J000 is dead (pid=6832, state=3):

                      *** 2016-05-19 02:00:49.812

                      Process J000 is dead (pid=7324, state=3):

                      *** 2016-05-19 07:47:29.875

                      Process J001 is dead (pid=4320, state=3):

                       

                       

                      I can provide a sample of the last 5 days of the log file text, I can e-mail it to you if you need to take a look at it.
                      But it pretty much looks the same as the part I've posted above.

                       

                      Thanks.

                      • 8. Re: APP-FND-01516
                        ViganQ

                        Any idea?

                        • 9. Re: APP-FND-01516
                          ViganQ

                          Is this a DB related problem?

                          • 10. Re: APP-FND-01516
                            happy10319

                            take a look here :

                            Error APP-FND-01516 INVALID APPLICATION USERNAME, PASSWORD, OF DATABASE

                             

                            It might be a listener problem.

                            Even if database is running the listener is not still listening. It takes some time. That's why (probably) after some restart of DB you can connect because after a while the listener is ready.