Long Term Release Vs Innovation Release

Oracle has presented a few days ago (on June 16) a new roadmap for its Releases.

Long Term Release; versions as its name indicates long-term, initially with Premier support of at least five years and later three years of extended support (at additional cost). Thought-out
to be more stable versions. The idea or concept is not new, Ubuntu already has an LTS (long-term support) version.

Innovation Release; They are more dynamic versions and they incorporate the latest technologies that are coming out. Now, they will include two years of Premier support and will not have
in no case extended support, so after two years you would be out of support.

My thinking about this is that I do not know very well what Oracle is looking for, or if it is segmenting its database customers, between large installations that are usually difficult to update or at least at the rate of two years and clients with more modest installations. and that they can follow that rhythm.

HTH – Antonio NAVARRO

 

OPW-00010,ORA-15221 Creating Password File in ASM

Today I created a RAC for a migration when in one of the steps I received the error Below. Specifically, I was creating the password file of the database in the ASM.

 

 

orapwd file='+MYDB_DG' password=SECRET dbuniquename=MYBD entries=10 

OPW-00010: Could not create the password file.
ORA-15056: additional error message
ORA-15221: ASM operation requires compatible.asm of 12.1.0.0.0 or higher
ORA-06512: at line 4

 

The problem in this case comes because compatible.asm does not support password files at the level it is on. It can be hot swapped and uploaded. I also take this opportunity to upload the RDBMS.

 

 
select name, database_compatibility,compatibility from v$asm_diskgroup where name like 'MYDB%'  order by 1 asc

NAME                           DATABASE_COMPATIBILITY                                       COMPATIBILITY
------------------------------ ------------------------------------------------------------ ------------------------------------------------------------
MYDB_ARC_DG                    10.1.0.0.0                                                   10.1.0.0.0
MYDB_DAT_DG                    10.1.0.0.0                                                   10.1.0.0.0
MYDB_R1_DG                     10.1.0.0.0                                                   10.1.0.0.0
MYDB_R2_DG                     10.1.0.0.0                                                   10.1.0.0.0

 

We execute from the user owner of the grid the following commands to make the change;

 

 
SYS@ASM>  ALTER DISKGROUP MYDB_ARC_DG SET ATTRIBUTE 'compatible.asm' = '12.1.0.2.0';

Diskgroup altered.

SYS@ASM>  ALTER DISKGROUP MYDB_DATOS_DG    SET ATTRIBUTE 'compatible.asm' = '12.1.0.2.0';

Diskgroup altered.

SYS@ASM>  ALTER DISKGROUP MYDB_PROD_R1_DG      SET ATTRIBUTE 'compatible.asm' = '12.1.0.2.0';

Diskgroup altered.

SYS@ASM>  ALTER DISKGROUP MYDB_PROD_R2_DG      SET ATTRIBUTE 'compatible.asm' = '12.1.0.2.0';

Diskgroup altered.

SYS@ASM>  ALTER DISKGROUP MYDB_ARC_DG SET ATTRIBUTE 'compatible.rdbms' = '12.1.0.2.0';

Diskgroup altered.

SYS@ASM>  ALTER DISKGROUP MYDB_DAT_DG    SET ATTRIBUTE 'compatible.rdbms' = '12.1.0.2.0';

Diskgroup altered.

SYS@ASM>  ALTER DISKGROUP MYDB_R1_DG      SET ATTRIBUTE 'compatible.rdbms' = '12.1.0.2.0';

Diskgroup altered.

SYS@ASM>  ALTER DISKGROUP MYDB_R2_DG      SET ATTRIBUTE 'compatible.rdbms' = '12.1.0.2.0';

Diskgroup altered.

SYS@ASM>

 

Check the result;

 

SQL> select name, database_compatibility,compatibility from v$asm_diskgroup where name like 'MYDB%'  order by 1 asc
  2  ;

NAME                           DATABASE_COMPATIBILITY                                       COMPATIBILITY
------------------------------ ------------------------------------------------------------ ------------------------------------------------------------
MYDB_ARC_DG                    12.1.0.2.0                                                   12.1.0.2.0
MYDB_DAT_DG                    12.1.0.2.0                                                   12.1.0.2.0
MYDB_R1_DG                     12.1.0.2.0                                                   12.1.0.2.0
MYDB_R2_DG                     12.1.0.2.0                                                   12.1.0.2.0

 

HTH – Antonio NAVARRO

 

 

Linux Kernel 5.7 Released

This past weekend Linus Torvalds has released the latest kernel release, 5.7. I would like to highlight some of the characteristics of this new version;

– New implementation of FS exFAT
– Bareudp module to create UDP tunnels
– A new implementation of Curve25519
– 15033 corrections

You can download the new release of Kernel in the next link;

Kernel 5.7

 

HTH – Antonio NAVARRO

 

 

Copying From Solaris View to Clipboard While Using Putty

This morning a coworker had a problem that happened to me long ago. In the latest versions of Solaris, when we use the view editor from Putty we will have noticed that it allows you to select text but does not copy it to the clipboard, in case you want to take it to another app. This does not happen with the vi edition. The solution in this case is to press shift left + mouse bottom left and we can copy to the clipboard.

HTH – Antonio NAVARRO

 

Warning changing permissions to extjob0 While Installing PSU

The other day when putting some PSUs in some bikes I received this warning at the end of the execution of the “opatch apply”

OPatch found the word “warning” in the stderr of the make command.
Please look at this stderr. You can re-run this make command.
Stderr output:
chmod: WARNING: can’t change /xxxx/xxxx/xxxxxx/product/12.1/bin/extjobO

Looking at documentation and notes, you can see that they can be safely ignored or run the root.sh script in the affected RDBMS HOME to resolve this issue.

From what I read it seems that it can happen from 11.2.0.4 onwards.

HTH – Antonio NAVARRO