My Oracle Support Banner

Datapatch -verbose failed with ORA-00372: file 325 cannot be modified at this time (Doc ID 3049112.1)

Last updated on SEPTEMBER 22, 2024

Applies to:

Oracle Database - Enterprise Edition - Version 19.3.0.0.0 and later
Gen 1 Exadata Cloud at Customer (Oracle Exadata Database Cloud Machine) - Version N/A to N/A
Oracle Cloud Infrastructure - Database Service - Version N/A to N/A [Release 1.0]
Information in this document applies to any platform.

Symptoms

While running datapatch -verbose, it is failing with the following error:

Current state of release update SQL patches:
Binary registry:

19.24.0.0.0 Release_Update 240627235157: Installed
PDB CDB$ROOT:
No release update patches installed
Adding patches to installation queue and performing prereq checks...done

Installation queue:
For the following PDBs: CDB$ROOT
No interim patches need to be rolled back
Patch 36582781 (Database Release Update : 19.24.0.0.240716 (36582781)):
Apply from 19.1.0.0.0 Feature Release to 19.24.0.0.0 Release_Update 240627235157

The following interim patches will be applied:
36414915 (OJVM RELEASE UPDATE: 19.24.0.0.240716 (36414915))

Installing patches...
Patch installation complete. Total patches installed: 2
Validating logfiles...done
Patch 36582781 apply (pdb CDB$ROOT): WITH ERRORS
logfile: <ORACLE_BASE>/cfgtoollogs/sqlpatch/36582781/25751445/36582781_apply_ABC_CDBROOT_Date_And_TimeStamp.log (errors)

-> Error at line 16945: script rdbms/admin/backport_files/bug_36104744_apply.sql
- ORA-00372: file 325 cannot be modified at this time

Patch 36414915 apply (pdb CDB$ROOT): WITH ERRORS (PREV PATCH)
logfile: <ORACLE_BASE>/cfgtoollogs/sqlpatch/36414915/25700138/36414915_apply_ABC_CDBROOT_Date_And_TimeStamp.log (no errors)

Adding patches to retry installation queue...done
Retry installation queue:
For the following PDBs: CDB$ROOT
No interim patches need to be rolled back
Patch 36582781 (Database Release Update : 19.24.0.0.240716 (36582781)):
Apply from 19.1.0.0.0 Feature Release to 19.24.0.0.0 Release_Update 240627235157
The following interim patches will be applied:
36414915 (OJVM RELEASE UPDATE: 19.24.0.0.240716 (36414915))

Installing patches...
Patch installation complete. Total patches installed: 2
Validating logfiles...done
Patch 36582781 apply (pdb CDB$ROOT): WITH ERRORS

logfile: <ORACLE_BASE>/cfgtoollogs/sqlpatch/36582781/25751445/36582781_apply_ABC_CDBROOT_Date_And_TimeStamp.log (errors)
-> Error at line 16945: script rdbms/admin/backport_files/bug_36104744_apply.sql
- ORA-00372: file 325 cannot be modified at this time

Patch 36414915 apply (pdb CDB$ROOT): WITH ERRORS (PREV PATCH)
logfile: <ORACLE_BASE>/cfgtoollogs/sqlpatch/36414915/25700138/36414915_apply_ABC_CDBROOT_2Date_And_TimeStamp.log (no errors)
Please refer to MOS Note 1609718.1 and/or the invocation log
<ORACLE_BASE>/cfgtoollogs/sqlpatch/sqlpatch_<Date_And_TimeStamp>/sqlpatch_invocation.log
for information on how to resolve the above errors. 

As noted in sqlpatch_catcon_0.log

SQL> CREATE TABLE WRR$_REPLAY_WORKLOADS
2 ( dbid INTEGER NOT NULL
3 , rep_wl_id INTEGER NOT NULL
4 , rep_wl_name VARCHAR2(128) NOT NULL
5 , rep_wl_magic_num NUMBER NOT NULL
6 , cap_wl_dbid INTEGER NOT NULL
7 , cap_wl_id INTEGER NOT NULL
8 , plsql_mode INTEGER NOT NULL
9 , status VARCHAR2(128)
10 ,constraint WRR$_REPLAY_WORKLOADS_PK primary key
11 (dbid, rep_wl_id)
12 ,constraint WRR$_REPLAY_WORKLOADS_U unique
13 (rep_wl_name)
14 ,constraint WRR$_REPLAY_WORKLOADS_U2 unique
15 (cap_wl_dbid, cap_wl_id, plsql_mode)
16 ) tablespace SYSAUX
17 /

CREATE TABLE WRR$_REPLAY_WORKLOADS

*
ERROR at line 1:
ORA-00955: name is already used by an existing object

Elapsed: 00:00:00.01

SQL> ALTER TABLE wrr$_replays ADD (rep_wl_name varchar2(128));

ALTER TABLE wrr$_replays ADD (rep_wl_name varchar2(128))

*
ERROR at line 1:
ORA-01430: column being added already exists in table

Elapsed: 00:00:00.00

SQL> -- Truncate the tables that contain the processed data. No need to carry
SQL> -- forward the data to new release because (1) the tables gets truncated
SQL> -- at the beginning of each replay and the data is only valid in the
SQL> -- previous release and (2) prevent ORA-01449 when adding the primary key
SQL> -- with the new columns (dbid and rep_wl_id).

SQL> TRUNCATE TABLE wrr$_commit_data;

Table truncated.

Elapsed: 00:00:00.01

SQL> TRUNCATE TABLE wrr$_replay_call_info;

TRUNCATE TABLE wrr$_replay_call_info

*
ERROR at line 1:
ORA-00372: file 325 cannot be modified at this time

Elapsed: 00:00:00.17

SQL> TRUNCATE TABLE wrr$_sequence_data;

Table truncated.

Elapsed: 00:00:00.01

SQL> TRUNCATE TABLE wrr$_replay_data;

Table truncated.

Upon investigating the violation error:

SQL>column message format a85
SQL>column status format a9
SQL>column type format a9
SQL>column con_id format 9
SQL>select con_id, type, message, status from PDB_PLUG_IN_VIOLATIONS where status<>'RESOLVED' order by time;

CON_ID TYPE MESSAGE STATUS
2 ERROR Interim patch 36414915/25700138 (OJVM RELEASE UPDATE: 19.24.0.0.240716 (36414915 )): APPLY with status WITH ERRORS (PREV PATCH) in the CDB. PENDING
2 ERROR Interim patch 36414915/25700138 (OJVM RELEASE UPDATE: 19.24.0.0.240716 (36414915 )): Not installed in the CDB but installed in the PDB PENDING
2 ERROR 19.24.0.0.0 Release_Update 2406272351: APPLY with status WITH ERRORS in the CDB PENDING

Session altered.

 In checking the status of PDB$SEED

SQL> show pdbs
CON_ID CON_NPME OPEN MODE RESTRICTED
---------- ------------------------------ ---------- ----------

2 PDB$SEED READ ONLY YES
5 PDB_XYZ READ WRITE NO

 After examining the registry query:

SQL> col version format a20
SQL> col ACTION_TIME format a30
SQL>col ACTION format a15
SQL> col version format a15
SQL> col status format a15
SQL> col bundle_series format a15
SQL> col DESCRIPTION format a60
SQL> set lines 999 pages 1000
SQL> col target_build_description for a15
SQL> select target_build_description,PATCH_UID,PATCH_ID,ACTION,STATUS,ACTION_TIME,DESCRIPTION from dba_registry_sqlpatch;

CDB$ROOT

Release_Update 25751445 36582781 APPLY WITH ERRORS 10-Aug24 01.02.03.299458 PM Database Release Update : 19.24.0.0.240716 (36582781)
Release_Update 25700138 36414915 APPLY WITH ERRORS (PR EV PATCH) 10-Aug24 01.02.08.840759 PM OJVM RELEASE UPDATE: 19.24.0.0.240716 (36414915)
Release_Update 25751445 36582781 APPLY WITH ERRORS 10-Aug24 01.02.42.542559 PM Database Release Update : 19.24.0.0.240716 (36582781)

PDB$SEED

Release_Update 25601966 36199232 ROLLBACK SUCCESS 10-Aug24 12.49.45.401121 PM OJVM RELEASE UPDATE: 19.23.0.0.240416 (36199232)
Release_Update 25700138 36414915 APPLY SUCCESS 10-Aug24 12.49.45.509722 PM OJVM RELEASE UPDATE: 19.24.0.0.240716 (36414915)
Release_Update 25751445 36582781 APPLY SUCCESS 10-Aug24 12.50.15.384308 PM Database Release Update : 19.24.0.0.240716 (36582781)

PDB_XYZ

19.23.0.0.240416 (36233263)
Release_Update 25601966 36199232 ROLLBACK SUCCESS 10-Aug24 12.49.45.377585 PM OJVM RELEASE UPDATE: 19.23.0.0.240416 (36199232)
Release_Update 25700138 36414915 APPLY SUCCESS 10-Aug24 12.49.45.479302 PM OJVM RELEASE UPDATE: 19.24.0.0.240716 (36414915)
Release_Update 25751445 36582781 APPLY SUCCESS 10-Aug24 12.50.12.674613 PM Database Release Update : 19.24.0.0.240716 (36582781)

38 rows selected.

Cause

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!


In this Document
Symptoms
Cause
Solution
References


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.