Error duing CLEANUP

[VinodNN]

Hi Erman,

We are hitting this error while doing cleanup on ebs:

Running cleanup in FULL mode.
    Log: @ADZDSHOWLOG.sql "2026/04/23 17:48:44"

 Statement Handler Error Code: 907
 Statement Handler Error Message: ORA-00907: missing right parenthesisADOP_commands.txt
ORA-06512: at "APPS.AD_ZD", line 64
ORA-06512: at "APPS.AD_ZD", line 48
ORA-06512: at "APPS.AD_ZD_TABLE", line 28
ORA-06512: at "APPS.AD_ZD_TABLE", line 2701
ORA-06512: at "APPS.AD_ZD_TABLE", line 2701
ORA-06512: at "APPS.AD_ZD", line 1152
ORA-06512: at line 3 (DBD ERROR: OCIStmtExecute)
 Reference of statement-handler is valid, not attempting database reconnect.
 Failed to execute SQL statement:
      begin
        execute immediate 'alter session set DDL_LOCK_TIMEOUT = 600';
        ad_zd.cleanup('FULL');
      end;

 Error Message:
ORA-00907: missing right parenthesis
ORA-06512: at "APPS.AD_ZD", line 64
ORA-06512: at "APPS.AD_ZD", line 48
ORA-06512: at "APPS.AD_ZD_TABLE", line 28
ORA-06512: at "APPS.AD_ZD_TABLE", line 2701
ORA-06512: at "APPS.AD_ZD_TABLE", line 2701
ORA-06512: at "APPS.AD_ZD", line 1152
ORA-06512: at line 3 (DBD ERROR: OCIStmtExecute)    [UNEXPECTED]Error occurred calling cleanup PL/SQL API.
    [UNEXPECTED]Cleanup phase has failed.


[STATEMENT] Please run adopscanlog utility, using the command

"adopscanlog -latest=yes"

to get the list of the log files along with snippet of the error message corresponding to each log file.


adop exiting with status = 1 (Fail)

Can it be ignored? We need to create a clone for testing a solution. Is it safe to use backup of RUN fs now? Please ugnore the uploaded file. It is not about this environment where we are facing this issue.

adopscanlog does not show any error.

Database alert log has following error:

ORA-06512: at line 48
ORA-04088: error during execution of trigger 'EBS_SYSTEM.EBS_LOGON'
ORA-00604: error occurred at recursive SQL level 1
ORA-20099: E-Business Suite Patch Edition does not exist.
ORA-06512: at line 48
ERP(3):opidcl aborting process unknown ospid (135503) as a result of ORA-1000
ORA-04088: error during execution of trigger 'EBS_SYSTEM.EBS_LOGON'
ORA-00604: error occurred at recursive SQL level 1
ORA-20099: E-Business Suite Patch Edition does not exist.
ORA-06512: at line 48

[VinodNN]

This is perhaps the root cause:

ADZDSHOWLOG

================

 392192724 07:43:20 00:00:00 ad.plsql.ad_zd_table.cleanup               EVENT      Cleanup unused columns
392192724 07:43:46 00:00:26 ad.plsql.ad_zd_table.cleanup               STATEMENT  SQL: alter table "BIDASH"."ST_HR_INTERFACE_STAGING_DATA_EBS1"  set unused (SYS_C00019_26042317:24:34$)
392192724 07:43:46 00:00:00 ad.plsql.ad_zd_table.cleanup               ERROR      ERROR: ORA-00907: missing right parenthesis, SQL: alter table "BIDASH"."ST_HR_INTERFACE_STAGING_DATA_EBS1"  set unused (
                                                                                  SYS_C00019_26042317:24:34$)

392192724 07:43:46 00:00:00 ad.bin.adop                                UNEXPECTED Error occurred calling cleanup PL/SQL API.
392192724 07:43:46 00:00:00 ad.bin.adop                                UNEXPECTED Cleanup phase has failed.
 
BIDASH is a custom schema. Couple of columns were added to a table a few days ago, but most likely ad_zd_patch/upgrade was missed. How can we resolve this so that cleanup runs successfully?

[VinodNN]

Oracle Support is telling us:

First, you need to review which columns were added on 10th April to the custom table -"BIDASH"."ST_HR_INTERFACE_STAGING_DATA_EBS1"

 

Also if any more columns were added to any other custom tables ---> also get those details.

Then remove/drop those columns to bring the custom table to its earlier structure.

 

Review below document for instructions for dropping columns from custom table -

Developing and Deploying Customizations in Oracle E-Business Suite Release 12.2 [KA1068 ]

***

But we haven't been able to find those instructions in the document.

[VinodNN]

This was resolved by dropping "BIDASH"."ST_HR_INTERFACE_STAGING_DATA_EBS1" table.

[ErmanArslansOracleBlog]

Just found the time to look this one, but it seems it is already resolved :) good.