Blog dedicated to Oracle Applications (E-Business Suite) Technology; covers Apps Architecture, Administration and third party bolt-ons to Apps

Monday, February 16, 2009

ORA-01403 ORA-06512 at "APPS.AD_FILE_SYS_SNAPSHOTS_PKG", line 2472

Recently while doing shared APPL_TOP migration, we got this error while trying to update current snapshot:

About to attempt instantiating the current-view snapshot: Fri Feb 13 2009 22:24:14

Attempting to instantiate the current-view snapshot...
ORA-01403: no data found
ORA-06512: at "APPS.AD_FILE_SYS_SNAPSHOTS_PKG", line 2472
ORA-06512: at line 2

AD Administration error:
Error while executing statement (curr-vw inst)

AD Administration error:
Error calling adusnapInstCurrVwSnapshot

AD Administration error:
Could not get SnapshotId

Failed to store APPL_TOP Snapshot to tables
adusnapMaintainSnapshot() : Error calling adusnapUpdateCurrentView()
Error calling adusnapMaintainSnapshot

Metalink Note 284759.1 gave a clue as it described this error on the clone of Production. However we were doing this on Production and had not faced this error in any of the iterations before. I checked the name of the appl_top in ad_appl_tops table and found that it was incorrect. The name of the appl_top refereed to the old server name on which the application was running 6 months ago. 6 months ago we had migrated to the new server but never changed the appl_top name. I went through the code of AD_FILE_SYS_SNAPSHOTS_PKG and found that it was calling ad_snapshots. The appl_top id in ad_appl_tops and the appl_top_id in ad_snapshots was not matching. This was because we had cleaned up ad_appl_tops and run autoconfig on all tiers. I searched in dba_tab_columns and found that there were 16 tables which had appl_top_id column. Updating all these tables with the new appl_top_id would have been a pain. So instead I suggested the DBAs to

update ad_appl_tops
set appl_top_id = 'appl_top_id of the old server'
where appl_top_id = 'newly generated appl_top_id for new server';

Once the DBAs did this, the update current snapshot process completed without errors.

No comments: