Last updated on SEPTEMBER 07, 2016
Applies to:Oracle Order Management - Version 12.1.3 and later
Information in this document applies to any platform.
On : 12.1.3 version, Patch Application Issues
While applying <patch 18767530:R12.ONT.B> , the log file shows quiet few indexes getting created and some of them failed.
These indexes are on Standard tables (OE_PRICE_ADJ_ASSOCS, OE_PRICE_ADJUSTMENTS,OE_ORDER_HOLDS_ALL).
It also tries to modify table (oe_order_lines_all, oe_order_headers_all).
Per the DBA team, the index structures are new , we need to understand whether we should go ahead with patch deployment.
Are the error generic ones ?
Start time for statement below is: Wed May 18 2016 18:12:15
CREATE UNIQUE INDEX ONT.OE_PRICE_ADJ_ASSOCS_U1 ON ONT.OE_PRICE_ADJ_ASSOCS
(PRICE_ADJ_ASSOC_ID) LOGGING STORAGE (FREELIST GROUPS 4 FREELISTS 4 )
PCTFREE 10 INITRANS 11 MAXTRANS 255 COMPUTE STATISTICS COMPRESS 1
AD Worker error:
The following ORACLE error:
ORA-25193: cannot use COMPRESS option for a single column key
The issue can be reproduced at will with the following steps:
1. Using adpatch apply <patch 18767530:R12.ONT.B>
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
Million Knowledge Articles and hundreds of Community platforms