Forum Stats

  • 3,751,465 Users
  • 2,250,366 Discussions
  • 7,867,433 Comments

Discussions

APEX 5.1.4 Patch Issue on non-CDB database (p26795231_514_Generic.zip)

TimHall
TimHall Member Posts: 293 Bronze Badge
edited Jan 23, 2018 2:20PM in APEX Discussions

Hi.

I've just applied the APEX 5.1.4 patch (p26795231_514_Generic.zip) to two databases:

1) APEX 5.1.3 to APEX 5.1.4 upgrade inside a PDB (DB 12.2.0.1). Worked fine.

2) APEX 5.1.3 to APEX 5.1.4 in a non-CDB (DB 12.1.0.2). Failed with the following errors.

...Validating Application Express

...(11:11:50) Starting validate_apex for APEX_050100

...(11:11:52) Checking missing sys privileges

...(11:11:52) Recompiling APEX_050100

...(11:11:55) Checking for objects that are still invalid

ORA-20001: COMPILE FAILURE: PACKAGE BODY APEX_050100.WWV_FLOW_AUTHORIZATION

...361/9    PL/SQL: SQL Statement ignored

...361/21   PL/SQL: ORA-00600: internal error code, arguments: [qctbyt : bfc],

[65532], [18446744073709551612], [1], [873], [1], [1], [0], [], [], [], []

ORA-20001: COMPILE FAILURE: PACKAGE BODY APEX_050100.WWV_FLOW_WIZARD_API

...1052/7   PL/SQL: SQL Statement ignored

...1089/14  PL/SQL: ORA-00600: internal error code, arguments: [qctbyt : bfc],

[65532], [18446744073709551612], [1], [873], [1], [1], [0], [], [], [], []

...(11:11:56) Key object existence check

...(11:11:56) Setting DBMS registry for APEX to INVALID

...(11:11:56) Exiting validate_apex

A quick scan on MOS links through to people trying to install APEX into a PDB when there is a CDB installation is already present, which is not the case here. It's a non-CDB instance.

Now I know the underlying DB versions are different as the architectures, but both versions are supported, as are both architectures. Anyone else seen this type of thing with the 5.1.4 patch?

Note. All instances were previously patched from 5.1.2 to 5.1.3 with no problems.

BTW: Just uninstalled APEX and reinstalled a clean 5.1.3 so people can continue while I investigate, so I don't have a problem with anything real at the moment.

Cheers

Tim...

Tagged:
Pierre Yotti

Answers

  • TimHall
    TimHall Member Posts: 293 Bronze Badge
    edited Jan 17, 2018 3:40PM

    Update:

    I did the following clean installations + upgrades and they all worked fine.

    1) DB 12.1.0.2 multitentant. Installed APEX 5.1.3 and patched to APEX 5.1.4.

    2) DB 12.1.0.2 non-CDB. Installed APEX 5.1.3 and patched to APEX 5.1.4.

    3) DB 12.2.0.1 multitentant. Installed APEX 5.1.3 and patched to APEX 5.1.4.

    4) DB 12.2.0.1 non-CDB. Installed APEX 5.1.3 and patched to APEX 5.1.4.

    So I've not been able to recreate the issue on a clean install. No idea why the patch is failing on that other server. I'll try again now the server has a clean 5.1.3 installation on it.

    Cheers

    Tim...

    Pierre Yotti
  • Mary Bagir
    Mary Bagir Member Posts: 148 Blue Ribbon
    edited Jan 23, 2018 2:00PM

    Hi guys,

    I have exactly the same error

    The database versions:12.1.0.1.0 and 12.1.0.2.0

    patch applied on apex versions 5.1.1 and 5.1.3.

    I do Apex installation start from htmldb 1.5  never ever had problems with installation and patching. It is defiantly bug.

    No another solution besides reinstall. I have multiple workspaces, users 20 applications. I need all exported and imported again.

    it is at least test database. I don't want repeat this process for prod. maybe it is some rollback process can be done.

    Thanks MB

  • Mary Bagir
    Mary Bagir Member Posts: 148 Blue Ribbon
    edited Jan 23, 2018 2:07PM

    sorry I didn't mention; the databases non-CDB.

  • Mary Bagir
    Mary Bagir Member Posts: 148 Blue Ribbon
    edited Jan 23, 2018 2:20PM

    Hi Guys,

    I found solution in Metalink

    Connect as sys user and execute the below command:

    SQL> alter system set nls_length_semantics=byte scope=both

    Run patch

    change back nls_length_semantics

    Thanks Mary

This discussion has been closed.