R12.2 upgrade patch driver (u10124646.drv) fails on apstca01.sql and ceburgrp.sql
Comments
-
chk if its related... there is some pre-patch to be applied.
Alert: Possible Installed Base Transaction SubType Corruption Caused by R12.2.0 Upgrade Driver u10124646.drv (Doc ID 1679947.1)
0 -
Hi,
Thanks for quick reply.
We applied all the pre-install patches by following this doc id
R12.1 and 12.2 Oracle E-Business Suite Preinstall Patches Report [Video] (Doc ID 1448102.2)
But the in the mentioned document 1679947.1, we have a patch 18756380: R12.2.3 UPGRADE: TRANSACTION SUBTYPE DUPLICATES AFTER UPGRADE. But this patch wasnot applied.
And i would like to tell the error as well::
sqlplus -s APPS/***** @/u01/apps/fs1/EBSapps/appl/ad/12.0.0/patch/115/sql/adsqlwrapper.sql '/u01/apps/fs1/EBSapps/appl/ce/12.0.0/patch/115/sql/ceburgrp.sql '
Connected.
PL/SQL procedure successfully completed.
DECLARE
*
ERROR at line 1:
ORA-00001: unique constraint (AR.HZ_PARTY_SITES_U2) violated
ORA-06512: at line 3760
This error was on all the workers.Having two sql's
apstca01.sql and ceburgrp.sql
Can we go a head of applying the patch which is 18756380.
0 -
Hi,
Thanks for quick reply.
We applied all the pre-install patches by following this doc id
R12.1 and 12.2 Oracle E-Business Suite Preinstall Patches Report [Video] (Doc ID 1448102.2)
But the in the mentioned document 1679947.1, we have a patch 18756380: R12.2.3 UPGRADE: TRANSACTION SUBTYPE DUPLICATES AFTER UPGRADE. But this patch wasnot applied.
And i would like to tell the error as well::
sqlplus -s APPS/***** @/u01/apps/fs1/EBSapps/appl/ad/12.0.0/patch/115/sql/adsqlwrapper.sql '/u01/apps/fs1/EBSapps/appl/ce/12.0.0/patch/115/sql/ceburgrp.sql '
Connected.
PL/SQL procedure successfully completed.
DECLARE
*
ERROR at line 1:
ORA-00001: unique constraint (AR.HZ_PARTY_SITES_U2) violated
ORA-06512: at line 3760
This error was on all the workers.Having two sql's
apstca01.sql and ceburgrp.sql
Can we go a head of applying the patch which is 18756380.
Yes. You should apply the preinstall patch 18756380 and then attempt to reapply the current patch.
It looks like the issue you are getting and the unique constraint error could potentially justify it.
Hope this helps!
John Khamissi
0 -
Yes. You should apply the preinstall patch 18756380 and then attempt to reapply the current patch.
It looks like the issue you are getting and the unique constraint error could potentially justify it.
Hope this helps!
John Khamissi
Hi John,
we were doing the following:::
This is for the issue where the error is ORA-00001: unique constraint (AR.HZ_PARTY_SITES_U2) violated.
1. Identify what the MAX party site number is on HZ_PARTY_SITES:
set serveroutput on
declare
n number;
maxn number := -1;
begin
for c in (select party_site_number from HZ_party_sites) loop
begin
n := 0;
n := to_number(c.party_site_number);
exception
when others then null;
end;
if n > maxn then maxn := n; end if;
end loop;
dbms_output.put_line ('Max is: '||maxn);
end;
/
2. If MAX returned is greater than the LAST_NUMBER of the query below, you will need to alter the sequence on step 3:
SELECT sequence_name, last_number FROM dba_sequences WHERE SEQUENCE_NAME LIKE '%HZ%PARTY%SITE%NUM%';
3. Drop sequence and re-create with higher start value greater than max party_site_number query on 1.
DROP SEQUENCE AR.HZ_PARTY_SITE_NUMBER_S;
CREATE SEQUENCE AR.HZ_PARTY_SITE_NUMBER_S START WITH XXXXX MINVALUE 1 MAXVALUE 2147483647 CACHE 1000;
0 -
Hi John,
we were doing the following:::
This is for the issue where the error is ORA-00001: unique constraint (AR.HZ_PARTY_SITES_U2) violated.
1. Identify what the MAX party site number is on HZ_PARTY_SITES:
set serveroutput on
declare
n number;
maxn number := -1;
begin
for c in (select party_site_number from HZ_party_sites) loop
begin
n := 0;
n := to_number(c.party_site_number);
exception
when others then null;
end;
if n > maxn then maxn := n; end if;
end loop;
dbms_output.put_line ('Max is: '||maxn);
end;
/
2. If MAX returned is greater than the LAST_NUMBER of the query below, you will need to alter the sequence on step 3:
SELECT sequence_name, last_number FROM dba_sequences WHERE SEQUENCE_NAME LIKE '%HZ%PARTY%SITE%NUM%';
3. Drop sequence and re-create with higher start value greater than max party_site_number query on 1.
DROP SEQUENCE AR.HZ_PARTY_SITE_NUMBER_S;
CREATE SEQUENCE AR.HZ_PARTY_SITE_NUMBER_S START WITH XXXXX MINVALUE 1 MAXVALUE 2147483647 CACHE 1000;
Thanks for the additional input. You should still apply the preinstall patch mentioned and then try to apply the patch in question.
Let us know how you progress.
John Khamissi
0
