Modify DatafileHeader to circumvent ORA-01190

Cause 1 that triggers a ORA-01190 error first throws a ora-01190 error that uses the bbed tool to construct SQLstartupORACLEinstancestarted. TotalSystemGlobalArea322961408bytesFixedSize & nb

Cause 1 that triggers a ORA-01190 error first throws a ora-01190 error that uses the bbed tool to construct SQLstartupORACLEinstancestarted. TotalSystemGlobalArea322961408bytesFixedSize & nb

One reason for triggering ORA-01190 errors

1 throws a ora-01190 error first, which is constructed using the bbed Tool

SQL> startup

ORACLE instance started.

Total System Global Area 322961408 bytes

Fixed Size 2020480 bytes

Variable Size 96471936 bytes

Database Buffers 218103808 bytes

Redo Buffers 6365184 bytes

Database mounted.

ORA-01190: control file or data file 11 is from before the last RESETLOGS

ORA-01110: data file 11: '/oracle/test/jiujian1.dbf'

2 oerr ora 01190 provides an explanation of this error

[Oracle @ oracle ~] $ Oerr ora 1, 01190

01190,000 00, "control file or data file % s is from before the last RESETLOGS"

// * Cause: Attempting to use a data file when the log reset information in

// The file does not match the control file. Either the data file

// Or the control file is a backup that was made before the most

// Recent alter database open resetlogs.

// * Action: Restore file from a more recent backup.

In general

When a data file is called, it is found that the resetlogs information of the data file does not match the resetlogs information in the control file.

3. query the resetlogs information in the data file header and control file.

The resetlogs information in the control file is as follows:

SQL> select resetlogs_change #, to_char (resetlogs_time, 'Mm/dd/yyyy hh24: mi: ss') time from v $ database;

RESETLOGS_CHANGE # TIME

-------------------------------------------

2781464667 21:51:45

The resetlogs information in each data file header is as follows:

Fhrls: resetlogs scn Value

Fhrlc: resetlogs count value

Fhrlc_ I: resetlogs count is converted to a 10-digit value.

Resetlogs count is described as follows:

Reset logs count and scn: The counter with the SCN is called the Reset Log Stamp,

And is a unique identification. The counter is in fact a timestamp

SQL> select hxfil, fhrls change #, fhrlc_ I, fhrlc time from x $ kcvfh;

Hxfil change # FHRLC_ I TIME

-------------------------------------------------------------------------------

1 2781464667 804808305 21:51:45

2 2781464667 804808305 21:51:45

3 2781464667 804808305 21:51:45

4 2781464667 804808305 21:51:45

5 2781464667 804808305 21:51:45

6 2781464667 804808305 21:51:45

7 2781464667 804808305 21:51:45

8 2781464667 804808305 21:51:45

11 2781455194 804803925 20:38:45

12 2781464667 804808305 21:51:45

13 2781464667 804808305 21:51:45

11 rows selected.

By comparing the resetlogs scn and resetlogs count values of file 11, it is not difficult to find the cause of triggering the ora-01190: that is, the resetlogs scn of the data file header, resetlogs count and resetlogs information in the control file do not match. So, to avoid ora-01190 errors, we can modify the resetlogs related values in the data file header Through bbed

Second, use bbed to modify the data file header to avoid this error.

1 position of resetlogs count and resetlogs scn in the Data File Header

Resetlogs count is at the offset of 112 in the Data File Header

Resetlogs scn is located at the offset of 116 in the Data File Header

BBED & gt; p offset 112

Kcvfh. kcvfhrlc

--------------