Scribd
Upload
17 views

Others Notes

Uploaded by

rishabh mathur
Copyright
© © All Rights Reserved
Available Formats
Download as TXT, PDF, TXT or read online on Scribd
17 views

Others Notes

Uploaded by

rishabh mathur
Copyright
© © All Rights Reserved
Available Formats
Download as TXT, PDF, TXT or read online on Scribd
You are on page 1/ 1

- Migrations, Upgrades, Patching

Q. Upgrade from 12c to 19c ?

Manual:
http://www.br8dba.com/upgrade-oracle-database-manually-from-12-2-0-1-to-19c/

Q. What does Compatible parameter do?

Setting COMPATIBLE ensures that new features do not write data formats or
structures to disk that are not compatible with the earlier release, preventing a
future downgrade. Features that require a higher value of COMPATIBLE to work
correctly may be restricted or disabled to ensure downgrades are possible.The
COMPATIBLE parameter specifies the Oracle version number that the database disk
format must be compatible with. The database can be downgraded to the version
specified in the COMPATIBLE parameter or any later version.

Understanding the COMPATIBLE Initialization Parameter:

When the COMPATIBLE initialization parameter is not set in your parameter file, the
COMPATIBLE parameter value defaults to 12.2.0 for Oracle Database 12c release 2
(12.2). If you do not set the COMPATIBLE initialization parameter to 12.2.0, then
you cannot use the new Oracle Database 12c release 2 (12.2) features, because your
upgraded database is not running in the required COMPATIBILITY setting for Oracle
Database 12c features.

When the Oracle Database COMPATIBLE parameter is increased to 12.2.0, the first
Java call to the database initiates a "name translation" operation. This operation
can require a few minutes to complete. You should expect this delay the first time
a Java call is made to the database after you increase the compatibility parameter.
This initial delay to carry out the name translation occurs only during the initial
Java call.

You might also like