1 2 Previous Next 15 Replies Latest reply on Sep 10, 2019 7:54 PM by Mike286

    Upgrade 18.2 to 19.1 - ORA-06512: at "APEX_190100.WWV_INSTALL_API", line 440

    Habib

      Hello

       

      I am upgrading APEX 18.2 running on my 12c  12.1.0.2.0 on Linux. I get following and the upgrade fails:

       

       

      ERROR at line 1:
      ORA-20001: Install errors found in phase 2
      ORA-06512: at "APEX_190100.WWV_INSTALL_API", line 440
      ORA-06512: at line 8
      

       

      My install log file is available at: https://www.dropbox.com/s/v208xrcm5u7chvn/install2019-05-21_06-34-42.log?dl=0

       

      Any help will be appreciated.

       

      Regards,

       

      Habib

        • 1. Re: Upgrade 18.2 to 19.1 - ORA-06512: at "APEX_190100.WWV_INSTALL_API", line 440
          Carsten Czarski-Oracle

          Hi Habib,

           

          that is one we have not seen before ...

           

          -) Are there any database or DDL triggers active which could raise that error message (probably due to some dynamic SQL execution) ...? If yes, those should be disabled before running the APEX upgrade.

          -) If not can you execute the following SQL Statement in order to get more detailed information ...?

           

          alter session set events='1006 trace name errorstack level 3';

           

          After that, run apexins.sql once more ... the trace file (to find in the user-dump-destination on the database server) should then contain more detailed information about what is happening ...

           

          Best regards

           

          -Carsten

          • 2. Re: Upgrade 18.2 to 19.1 - ORA-06512: at "APEX_190100.WWV_INSTALL_API", line 440
            Habib

            Thanks Carsten

             

            There's no database level triggers. I run alter session set events='1006 trace name errorstack level 3'; and then again ran apexins ... but I can see only one file in user_dump_dest . It has following content:

             

            Dump file /opt/app/oracle/product/12.1.0/se2/rdbms/log/mydb_ora_24449.trc
            
            
            *** 2019-05-22 14:57:47.086
            Oracle Database 12c Standard Edition Release 12.1.0.2.0 - 64bit Production
            ORACLE_HOME = /opt/app/oracle/product/12.1.0/se2
            System name:    Linux
            Node name:      mydb-test.mycompany.net
            Release:        3.10.0-957.12.2.el7.x86_64
            Version:        #1 SMP Tue May 14 21:24:32 UTC 2019
            Machine:        x86_64
            Storage:        ?
            Instance name: mydb
            Redo thread mounted by this instance: 0 <none>
            Oracle process number: 0
            Unix process pid: 24449, image:
            
            
            
            
            *** 2019-05-22 14:57:47.086
            KJHA:2phase clscrs_flag:840 instSid:
            KJHA:2phase ctx 2 clscrs_flag:840 instSid:mydb
            KJHA:2phase clscrs_flag:840 dbname:
            KJHA:2phase ctx 2 clscrs_flag:840 dbname:mydb
            KJHA:2phase WARNING!!! Instance:mydb of kspins type:1 does not support 2 phase CRS
            

             

             

            I saw following error message on apexins screeen when errors started:

            ORA-01006: bind variable does not exist
            ORA-06512: at "APEX_190100.WWV_FLOW_UPGRADE", line 1733
            ORA-06512: at "APEX_190100.WWV_FLOW_UPGRADE", line 5058
            ORA-06512: at line 58
            
            • 3. Re: Upgrade 18.2 to 19.1 - ORA-06512: at "APEX_190100.WWV_INSTALL_API", line 440
              Carsten Czarski-Oracle

              Hi,

               

              hmmm ... there should actually be more information on the ORA-1006 in the trace file.  It should begin like this ...

               

              *** 2019-05-23T06:48:33.786296+00:00 (APEXTRUNK(7))
              *** SESSION ID:(280.60709) 2019-05-23T06:48:33.786334+00:00
              *** CLIENT ID:() 2019-05-23T06:48:33.786338+00:00
              *** SERVICE NAME:(apextrunk) 2019-05-23T06:48:33.786341+00:00
              *** MODULE NAME:(SQLcl) 2019-05-23T06:48:33.786344+00:00
              *** ACTION NAME:() 2019-05-23T06:48:33.786347+00:00
              *** CLIENT DRIVER:(jdbcthin : 18.3.0.0.0) 2019-05-23T06:48:33.786350+00:00
              *** CONTAINER ID:(7) 2019-05-23T06:48:33.786353+00:00
              
              
              dbkedDefDump(): Starting a non-incident diagnostic dump (flags=0x0, level=3, mask=0x0)
              ----- Error Stack Dump -----
              ----- Current SQL Statement for this session (sql_id=cq19kprnzkdp9) -----
              insert into hljdslkjsdfljk values (1)
              ----- PL/SQL Stack -----
              ----- PL/SQL Call Stack -----
                object      line  object
                handle    number  name
              0x80dd40d0        2  anonymous block
              
              
              ----- Call Stack Trace -----
              calling              call    entry                argument values in hex
              location            type    point                (? means dubious value)
              

              Did you, by chance, log out and back in between executing the ALTER SESSION and the @apexins.sql ...?

               

              You can also set the event at the system level to catch this case. Would you please ...

               

               

              1. (as sys): ALTER SYSTEM SET EVENTS='1006 trace name errorstack level 3';

              2. run apexins

              3. when all is done: ALTER SYSTEM SET EVENTS='1006 trace name errorstack off'

               

              The alert log file also contains information about the exact trace file to look for ...

               

              APEXTRUNK(7):Errors in file /home/cczarski/app/oracle/diag/rdbms/devenv/devenv/trace/devenv_ora_3546.trc:
              2019-05-23T06:40:21.979907+00:00
              

              Best regards

               

              -Carsten

              • 4. Re: Upgrade 18.2 to 19.1 - ORA-06512: at "APEX_190100.WWV_INSTALL_API", line 440
                2978227

                Just a quick note:  I have also ran into this EXACT error ("APEX_190100.WWV_INSTALL_API", line 440, and found this thread from Google trying to fix the problem.

                 

                Just letting folks know the error is more common that it seems, but no solution yet.  I will probably try to remove the old apex before upgrading and seeing if that works.

                • 5. Re: Upgrade 18.2 to 19.1 - ORA-06512: at "APEX_190100.WWV_INSTALL_API", line 440
                  Habib

                  I ended up with removing old APEX and installing the latest one and that worked.

                  • 6. Re: Upgrade 18.2 to 19.1 - ORA-06512: at "APEX_190100.WWV_INSTALL_API", line 440
                    2891811

                    I got this same error with a fresh install of Apex 19.1 into a  newly created 19.3 database

                     

                    ORA-20001: Install errors found in phase 1

                    ORA-06512: at "APEX_190100.WWV_INSTALL_API", line 440

                    ORA-06512: at line 5

                     

                    It seemed unable to run this command

                     

                        not ok 7 - Installing Package Specs (Runtime)                      |  0.28

                        # Message: ORA-01756: quoted string not properly terminated ORA-06512: at line 2

                        # Statement: begin

                        # execute immediate 'alter session set nls_numeric_characters='''||wwv_flow_api.g_nls_numeric_chars||'''';

                     

                    As it was an empty database which I could play with, I tried various things, finally what worked was uninstalling (apxremov.sql), changing territory to America (was Switzerland) and then it ran through

                    • 7. Re: Upgrade 18.2 to 19.1 - ORA-06512: at "APEX_190100.WWV_INSTALL_API", line 440
                      user3160743

                      I received the same error on a fresh install of 19.1 on a empty database. 

                       

                      ERROR at line 1:

                      ORA-20001: Install errors found in phase 1

                      ORA-06512: at "APEX_190100.WWV_INSTALL_API", line 440

                      ORA-06512: at line 5

                       

                      Looking through the log file, also saw the following error:

                      not ok 12 - Installing Package Bodies (Dev)                         |   0.08

                          # Message: ORA-00980: synonym translation is no longer valid

                       

                      Because of the same 06512 error that eventually kicked me out of the install script, I tried the suggestion by user 2891811 to alter the territory except I went from America to Switzerland.

                       

                      Steps I took:

                      Uninstalled APEX (apxremov.sql)

                      changed the territory from America to Switzerland

                      reinstalled APEX

                       

                      Still got the error that eventually kicked me out of the install but this time I get the same error as user 2891811

                       

                      ERROR at line 1:

                      ORA-20001: Install errors found in phase 1

                      ORA-06512: at "APEX_190100.WWV_INSTALL_API", line 440

                      ORA-06512: at line 5

                       

                      Looking back in the install log for this one, I find the following error this time:

                       

                      not ok 7 - Installing Package Specs (Runtime)                       |   0.82

                          # Message: ORA-01756: quoted string not properly terminated ORA-06512: at li

                      ne 2

                       

                      (NOTE - no problem with 12 this time)

                       

                      3rd times a charm:

                      Uninstalled APEX (apxremov.sql)

                      changed the territory from Switzerland to America (or made sure it was set to America because it was an alter session that I used before - so only good for the current session)

                      reinstalled APEX

                       

                      Install completed successfully this time.

                      • 8. Re: Upgrade 18.2 to 19.1 - ORA-06512: at "APEX_190100.WWV_INSTALL_API", line 440
                        joejetta

                        I'm getting this same error when upgrading my APEX from 5.0 to 19.1 :

                         

                        ERROR at line 1:

                        ORA-20001: Install errors found in phase 2

                        ORA-06512: at "APEX_190100.WWV_INSTALL_API", line 440

                        ORA-06512: at line 8

                         

                        But it is preceded by the following error messages several times:

                         

                        #

                        # Upgrading ACL

                        #

                        begin

                        *

                        ERROR at line 1:

                        ORA-46215: XS entity by the name

                        "SYS"."NETWORK_ACL_001EFB15584543128AB89A26D61DE129" did not exist.

                        ORA-06512: at "SYS.XS_ACL", line 405

                        ORA-06512: at "SYS.DBMS_NETWORK_ACL_ADMIN", line 131

                        ORA-46230: XS administrative operation failed.

                        ORA-06512: at "SYS.XS_ADMIN_UTIL", line 70

                        ORA-06512: at "SYS.XS_ACL_INT", line 221

                        ORA-00001: unique constraint (SYS.XS$ACE_PRIV_UK) violated

                        ORA-06512: at "SYS.DBMS_NETWORK_ACL_ADMIN", line 1089

                        ORA-06512: at line 15

                        • 9. Re: Upgrade 18.2 to 19.1 - ORA-06512: at "APEX_190100.WWV_INSTALL_API", line 440
                          Guilherme Campos

                          I have the same issue, upgrading from the same version (  pass - APEX: version=5.1.1.00.08) to Oracle APEX Release 19.1.0.00.15. Oracle Database 12.1.

                           

                          Here is the full stack.

                           

                          Any hint?

                           

                          not ok 330 - Upgrading ACL

                          # Message: ORA-46230: XS administrative operation failed. ORA-06512: at "SYS

                          .XS_ADMIN_UTIL", line 70

                          # ORA-06512: at "SYS.XS_ACL_INT", line 221

                          # ORA-00001: unique constraint (SYS.XS$ACE_PRIV_UK) violated

                          # ORA-06512: at "SYS.XS_ACL", line 65

                          # ORA-06512: at "SYS.DBMS_NETWORK_ACL_ADMIN", line 1079

                          # ORA-06512: at line 15

                          #

                          # Statement: begin

                          #     if '2' = '2' then

                          #         $if sys.dbms_db_version.version >= 12 $then

                          #             for l_priv in ( select p.acl,

                          #                                    a.host,

                          #                                    cast(collect(p.privilege) as sys.xs$nam

                          e_list) privileges

                          #                               from sys.dba_network_acls           a,

                          #                                    sys.dba_network_acl_privileges p

                          #                              where a.aclid     = p.aclid

                          #                                and p.principal = 'APEX_050100'

                          #                              group by p.acl,

                          #                                       a.host

                          #                              order by 1,2 )

                          #             loop

                          #                 sys.dbms_network_acl_admin.append_host_ace(

                          #                     host => l_priv.host,

                          #                     ace  => sys.xs$ace_type (

                          #                                 privilege_list => l_priv.privileges,

                          #                                 principal_name => 'APEX_190100',

                          #                                 principal_type => sys.xs_acl.ptype_db ));

                          #             end loop;

                          #         $else

                          #             sys.dbms_output.put_line('...not implemented on DB 11');

                          #         $end

                          #     else

                          #         sys.dbms_output.put_line('...not implemented on new install');

                          #     end if;

                          # end;

                          # Message: ORA-06512: at "SYS.XS_ADMIN_UTIL", line 70 ORA-06512: at "SYS.XS_

                          ACL_INT", line 221

                          # ORA-00001: unique constraint (SYS.XS$ACE_PRIV_UK) violated

                          # ORA-06512: at "SYS.XS_ACL", line 65

                          # ORA-06512: at "SYS.DBMS_NETWORK_ACL_ADMIN", line 1079

                          # ORA-06512: at line 15

                          #

                          # Statement: as above

                          # Message: ORA-06512: at "SYS.XS_ACL_INT", line 221 ORA-00001: unique constr

                          aint (SYS.XS$ACE_PRIV_UK) violated

                          # ORA-06512: at "SYS.XS_ACL", line 65

                          # ORA-06512: at "SYS.DBMS_NETWORK_ACL_ADMIN", line 1079

                          # ORA-06512: at line 15

                          #

                          # Statement: as above

                          # Message: ORA-00001: unique constraint (SYS.XS$ACE_PRIV_UK) violated ORA-06

                          512: at "SYS.XS_ACL", line 65

                          # ORA-06512: at "SYS.DBMS_NETWORK_ACL_ADMIN", line 1079

                          # ORA-06512: at line 15

                          #

                          # Statement: as above

                          # Message: ORA-06512: at "SYS.XS_ACL", line 65 ORA-06512: at "SYS.DBMS_NETWO

                          RK_ACL_ADMIN", line 1079

                          # ORA-06512: at line 15

                          #

                          # Statement: as above

                          # Message: ORA-06512: at "SYS.DBMS_NETWORK_ACL_ADMIN", line 1079 ORA-06512:

                          at line 15

                          #

                          # Statement: as above

                          # Message: ORA-06512: at line 15

                          # Statement: as above

                          • 10. Re: Upgrade 18.2 to 19.1 - ORA-06512: at "APEX_190100.WWV_INSTALL_API", line 440
                            Christian Neumueller-Oracle

                            Hi,

                             

                            first of all, you do not all have the same error. This

                             

                              ORA-20001: Install errors found in phase nnn

                              ORA-06512: at "APEX_190100.WWV_INSTALL_API", line 440

                             

                            is a summary error message. It just says that errors occurred in phase nnn. The actual errors are further above. If you encounter install errors, please start different threads for them.

                             

                            The ACL issues typically occur because of inconsistencies in the ACL configuration for the existing APEX_nnnnnn schema. When APEX automatically tries to upgrade the ACL settings to the new schema, it encounters an error. The workaround is to remove the existing ACL settings before upgrading. This is fixed in 19.2 (bug #29802395).

                             

                            The issue with ORA-01756 when e.g. territory is Switzerland is known (bug #29329199) but not fixed yet. The workaround is to change NLS settings, as described above.

                             

                            The "ORA-00980: synonym translation is no longer valid" is new, but the given information is not sufficient for diagnosis.

                             

                            Regards,

                            Christian

                            • 11. Re: Upgrade 18.2 to 19.1 - ORA-06512: at "APEX_190100.WWV_INSTALL_API", line 440
                              Sasha Gomanuke

                              The ACL issues typically occur because of inconsistencies in the ACL configuration for the existing APEX_nnnnnn schema. When APEX automatically tries to upgrade the ACL settings to the new schema, it encounters an error.

                               

                              Would You clarify what's wrong with that ACL configuration, so APEX 19.1 can't upgrade it?

                              Got by SQL:

                               

                              select *

                                  from sys.dba_network_acls  a,

                                  sys.dba_network_acl_privileges p

                                  where a.aclid     = p.aclid

                                  and p.principal = 'APEX_180100'

                              • 12. Re: Upgrade 18.2 to 19.1 - ORA-06512: at "APEX_190100.WWV_INSTALL_API", line 440
                                Christian Neumueller-Oracle

                                In this case, it probably fails because of multiple port declarations for the same host/acl. That's fixed in 19.2 (see above).

                                • 14. Re: Upgrade 18.2 to 19.1 - ORA-06512: at "APEX_190100.WWV_INSTALL_API", line 440
                                  Christian Neumueller-Oracle

                                  Sorry, we are not allowed to share release dates. However, we've been trying to release about every 6 months since 18.1 - no guarantees, of course.

                                  1 2 Previous Next