Forum Stats

  • 3,769,586 Users
  • 2,252,984 Discussions
  • 7,875,105 Comments

Discussions

Error During Installation of APEX 21.3, ORA-06512: at "APEX_210100.WWV_INSTALL_API", line 465

User_LELD2
User_LELD2 Member Posts: 2 Green Ribbon

My database is:

Oracle Database 19c Enterprise Edition Release 19.0.0.0.0 - Production

(Recently patched with the latest update)

Dear all,

I am getting the following error during my installation of APEX 21.3


Errors found. Drop APEX_210100 before re-starting the installation.

#

# Actions in Phase 1:

#

  ok 1 - BEGIN                            |  0.00

  ok 2 - Creating APEX_GRANTS_FOR_NEW_USERS_ROLE           |  0.02

  ok 3 - Creating SYS Objects                     |  0.00

  ok 4 - Creating APEX Tables                     |  0.22

  ok 5 - Installing Package Specs (Runtime)              |  0.33

  ok 6 - Installing Package Bodies (Runtime)             |  0.37

  ok 7 - Dev Grants                          |  0.00

  ok 8 - Creating Dev-Only Tables and Triggers            |  0.00

  ok 9 - Installing Package Specs (Dev)                |  0.08

  ok 10 - Installing Views (Dev)                   |  0.03

  ok 11 - Installing Package Bodies (Dev)               |  0.08

  not ok 12 - Recompiling APEX_210100                 |  0.52

  # Message: PL/SQL: Statement ignored

  # Statement: PACKAGE BODY APEX_210100.WWV_FLOW_MAP_REGION, Line 2036/21

  # Message: PLS-00201: identifier 'MDSYS.SDO_CS' must be declared

  # Statement: PACKAGE BODY APEX_210100.WWV_FLOW_MAP_REGION, Line 2037/44

  # Message: PL/SQL: Statement ignored

  # Statement: PACKAGE BODY APEX_210100.WWV_FLOW_MAP_REGION, Line 2051/25

  # Message: PLS-00201: identifier 'MDSYS.SDO_GEOM' must be declared

  # Statement: PACKAGE BODY APEX_210100.WWV_FLOW_MAP_REGION, Line 2051/43

  # Message: PL/SQL: Statement ignored

  # Statement: PACKAGE BODY APEX_210100.WWV_FLOW_MAP_REGION, Line 2619/29

  # Message: PLS-00201: identifier 'MDSYS.SDO_CS' must be declared

  # Statement: PACKAGE BODY APEX_210100.WWV_FLOW_MAP_REGION, Line 2620/52

  ok 13 - Creating APEX$ objects in APEX_210100            |  0.02

  ok 14 - Creating Instance Parameter Defaults            |  0.00

  ok 15 - Loading PDF font data                    |  0.60

  ok 16 - Installing Page Designer Metadata              |  0.07

  ok 17 - Inherit Privileges                     |  0.00

not ok 1 - 16 actions passed, 1 actions failed             |  2.33

begin

*

ERROR at line 1:

ORA-20001: Install errors found in phase 1, see "not ok" messages above for

details.

ORA-06512: at "APEX_210100.WWV_INSTALL_API", line 465

ORA-06512: at line 5


Would love some help.

Best Answer

  • Carsten Czarski-Oracle
    Carsten Czarski-Oracle Member Posts: 1,257 Employee
    edited Sep 8, 2021 7:52AM Accepted Answer

    Hi,

    this is odd ...

    The APEX installer checks whether Oracle Spatial (the SDO_GEOMETRY) data type is available in your database. If that is the case, then spatial-dependent functionality will be installed. If not, these parts will not be installed.

    The error messages indicate that the installer attempted to install such Oracle Spatial related functionality, although Oracle Spatial appears to be nonexistent in your database (MDSYS.SDO_GEOM, MDSYS.SDO_CS). However, the check for SDO_GEOMETRY at the beginning must have been positive - so there should be an MDSYS.SDO_GEOMETRY data type available.

    Can you verify the Spatial / Locator setup in your database?

    • Is the MDSYS.SDO_GEOMETRY data type present or not present in your database
    • Are the MDSYS.SDO_GEOM and MDSYS.SDO_CS packages present or not present in your database
    • Does your database have any special setup regarding Oracle Spatial - have Spatial objects been manually dropped or changed ...?

    Best regards

    -Carsten

Answers

  • Carsten Czarski-Oracle
    Carsten Czarski-Oracle Member Posts: 1,257 Employee
    edited Sep 8, 2021 7:52AM Accepted Answer

    Hi,

    this is odd ...

    The APEX installer checks whether Oracle Spatial (the SDO_GEOMETRY) data type is available in your database. If that is the case, then spatial-dependent functionality will be installed. If not, these parts will not be installed.

    The error messages indicate that the installer attempted to install such Oracle Spatial related functionality, although Oracle Spatial appears to be nonexistent in your database (MDSYS.SDO_GEOM, MDSYS.SDO_CS). However, the check for SDO_GEOMETRY at the beginning must have been positive - so there should be an MDSYS.SDO_GEOMETRY data type available.

    Can you verify the Spatial / Locator setup in your database?

    • Is the MDSYS.SDO_GEOMETRY data type present or not present in your database
    • Are the MDSYS.SDO_GEOM and MDSYS.SDO_CS packages present or not present in your database
    • Does your database have any special setup regarding Oracle Spatial - have Spatial objects been manually dropped or changed ...?

    Best regards

    -Carsten

  • User_LELD2
    User_LELD2 Member Posts: 2 Green Ribbon

    Hello,


    -MDSYS.SDO_GEOM and MDSYS.SDO_CS packages are not present in the database

    -MDSYS.SDO_GEOMETRY data type was present, that's why the check was positive

    I dropped the MDSYS.SDO_GEOMETRY data type and the installation finished without problems.


    Thank you very much for your help.

  • Carsten Czarski-Oracle
    Carsten Czarski-Oracle Member Posts: 1,257 Employee

    Hi,

    great that things are working now.

    Just one remark. Oracle Spatial no longer requires a separate license; so from a licensing point of view there is no need any more to remove Oracle Spatial from the database.

    Best regards

    -Carsten

  • User284650
    User284650 Member Posts: 3 Blue Ribbon

    Hello

    i got the same issue but we are using oracle spatial MDSYS.SDO_GEOM .

    Any workaround ?

  • Carsten Czarski-Oracle
    Carsten Czarski-Oracle Member Posts: 1,257 Employee

    Hi,

    when you're using the MDSYS.SDO_GEOM package, then you should also have the SDO_GEOMETRY data type available, as SDO_GEOM uses that data type in its signatures. And then, you should also have the SDO_CS package, as this is part of Oracle Locator (SDO_CS was always part of Locator, even when Oracle Spatial required a license).

    • Are you having the same errors as described above - is the SDO_CS package missing in your database?
    • SDO_CS is normally installed together with SDO_GEOMETRY and SDO_GEOM. So why is it missing in your database? Has it intentionally been dropped? If yes, why?

    The workaround would be to rectify the Locator / Spatial installation in your database.

    Best regards

    -Carsten

  • User284650
    User284650 Member Posts: 3 Blue Ribbon

    here the message :

    not ok 2 - 312 actions passed, 1 actions failed                        | 19.97

    begin

    *

    ERROR at line 1:

    ORA-20001: Install errors found in phase 2, see "not ok" messages above for

    details.

    ORA-06512: at "APEX_210100.WWV_INSTALL_API", line 465

    ORA-06512: at line 8

     


    I got the datatype , and package of oracle spatial mentionned in your answer.

  • Carsten Czarski-Oracle
    Carsten Czarski-Oracle Member Posts: 1,257 Employee

    Hi,

    this log snippet is insufficient - it only tells us that there have been errors. Can you either look up the section with the detailed message or share the complete log here?

    regards

    -Carsten

  • User284650
    User284650 Member Posts: 3 Blue Ribbon

    first thank you for helping.

    The log is big here the error

     not ok 281 - Upgrade Before Enabling Constraints          |  0.50

      # Message: ORA-01422: exact fetch returns more than requested number of rows

      # Statement:

      ok 282 - Enabling Constraints/Triggers               |  0.32

      ok 283 - Upgrade Metadata (2)                    |  0.00

      ok 284 - Upgrade with enabled constraints              |  2.23

      # Message: PERF: Statement took 2.03 min

      # Statement:

      #       declare

      #         c_old_import_in_progress constant boolean := wwv_flow.g_im

    port_in_progress;

      #       begin

      #         wwv_flow_api.set_security_group_id(11);

      #         wwv_flow.g_import_in_progress := true;

      #

      #         -- Remove Database Applications

      #         for c1 in (select id

      #               from wwv_flows

      #               where security_group_id = 11

      #                and id >= 7000 and id < 8000

      #                or id in (8950,8951) ) loop

      #           --

      #           wwv_flow_api.remove_application( c1.id );

      #         end loop;

      #

      #         -- Remove Templates

      #         for c1 in (select id

      #               from wwv_flows

      #               where security_group_id = 11

      #                and id >= 8801 and id < 8900 ) loop

      #           --

      #           wwv_flow_api.remove_application( c1.id );

      #         end loop;

      #

      #         -- Remove Websheet Applications

      #         for c2 in (select id

      #               from wwv_flow_ws_applications

      #               where security_group_id = 11

      #                and id in (1097894920371103914,1097895031667

    104017) ) loop

      #           --

      #           wwv_flow_api.remove_ws_app( c2.id );

      #           wwv_flow_ws_import_api.remove_ws_components( c2.id );

      #         end loop;

      #         commit;

      #

      #         wwv_flow.g_import_in_progress := c_old_import_in_progress;

      #       end;

      #

      ok 285 - Recompiling APEX_210100 schema               |  0.70

      ok 286 - Configuring Restricted Schemas               |  0.00

      ok 287 - Upgrading ACL                       |  0.02

      ok 288 - Installing 4411                      |  0.92

      ok 289 - Installing 4155                      |  0.05

      ok 290 - Installing Internal Themes                 |  0.77

      ok 291 - Installing 4000                      |  6.17

      ok 292 - Installing 4020                      |  0.45

      ok 293 - Installing 4350                      |  0.62

      ok 294 - Installing 4050                      |  0.87

      ok 295 - Installing 4550                      |  0.05

      ok 296 - Installing 4600                      |  0.28

      ok 297 - Installing 4650                      |  0.15

      ok 298 - Installing 4700                      |  0.08

      ok 299 - Installing 4750                      |  0.07

      ok 300 - Installing 4500                      |  1.35

      ok 301 - Installing 4300                      |  0.12

      ok 302 - Installing 4900                      |  0.48

      ok 303 - Installing 4850                      |  0.27

      ok 304 - Resetting Internal Authentication             |  0.00

      ok 305 - Installing Dictionary View Metadata            |  0.00

      ok 306 - Installing Advisor Metadata                |  0.02

      ok 307 - Updating App Owner/Version                 |  0.00

      ok 308 - Updating Plug-in settings of Applications         |  0.00

      ok 309 - Update Plug-In Settings of Applications          |  0.00

      ok 310 - Copying Instance settings                 |  0.00

      ok 311 - Copying Instance Settings                 |  0.03

      ok 312 - Enabling WS Constraints                  |  0.25

      ok 313 - Dropping Upgrade Triggers in APEX_040200          |  0.07

    not ok 2 - 312 actions passed, 1 actions failed             | 19.97

    begin

    *

    ERROR at line 1:

    ORA-20001: Install errors found in phase 2, see "not ok" messages above for

    details.

    ORA-06512: at "APEX_210100.WWV_INSTALL_API", line 465

    ORA-06512: at line 8

  • Carsten Czarski-Oracle
    Carsten Czarski-Oracle Member Posts: 1,257 Employee

    Hi,

    OK - this looks like a completely different issue and not related to Spatial or SDO_GEOMETRY.

    Can you send the full log privately to me ...? Either as a PM in the forum, or by email: {firstname}.{lastname}<at>oracle.com.

    Best regards

    -Carsten