Oracle pushes the database SCN by modifying the control file SCN

Database Current SCN

The code is as follows	Copy Code
Idle> select checkpoint_change# from V$database; checkpoint_change# ------------------ 271743118 idle> Shutdown Abort

The ORACLE routine has been closed.
SCN in Analysis control file

Here we can see the bold section for the database SCN

The code is as follows	Copy Code
Sql>select to_number (' 10327a59 ', ' xxxxxxxxx ') from dual; To_number (' 10327a59 ', ' xxxxxxxxx ') --------------------------------- 271743577

There is a small difference between the SCN value here and the value queried in the database, because there is a time lag between the query point and the fact that I completely shut down the database, which has a SCN change. The Thin red box is part of the control file to block the authentication information

Modifying the control file SCN and authentication information
Validation information modified to all 0,SCN information you can modify according to your needs, here the database SCN modified to 57253932971026, according to the principle of the database, after the start of the SCN should be slightly greater than the SCN value.

The code is as follows	Copy Code
Sql>select to_number (' 341278563412 ', ' xxxxxxxxxxxxxxxxx ') from dual; To_number (' 341278563412 ', ' xxxxxxxxxxxxxxxxx ') --------------------------------------------- 57253932971026

Start the database
Idle> Startup Mount
The ORACLE routine has started.

The code is as follows	Copy Code
Total System Global area 400846848 bytes Fixed Size 2440024 bytes Variable Size 289408168 bytes Database buffers 100663296 bytes Redo buffers 8335360 bytes

Database loading complete.

The code is as follows	Copy Code
idle> Recover database; Complete media recovery. idle> ALTER DATABASE open; The database has changed. Idle> select checkpoint_change# from V$database; checkpoint_change# ------------------ 57253932991028

After database startup, the query SCN is 57253932991028 (the current SCN of the database) is slightly greater than 57253932971026 (Modify the control file SCN), prove that we modify the control file SCN, the implementation of the database SCN push close to completely OK. No experimental risk is greater, Do not test in the production environment, load the consequences of the ego