Lately, I’ve stumbled upon this error while trying to create ADVM volume equal 100Tb.
Today I’ve came across strange error related to srvctl add service.
$ srvctl add service -d db -s SERVICE_NAME -preferred INST1,INST2 PRCR-1006 : Failed to add resource ora.db.db_service.svc for SERVICE_NAME PRCT-1011 : Failed to run "osdbagrp". Detailed error:
In our test environment we are using flashback technology. This technology afford to us to keep our test servers in the actual state regarding to production server, and the same time give the opportunity for testers make their tests for the new features for our system. We can roll back all changes which has made our testers, and roll forward all new changes which has made on primary server without restore whole database. This is very convenient. Couple days ago my colleague asked me if I can convert snapshot standby to primary without roll back changes which has made on this standby. This is important point, because in a normal way if you want to convert snapshot standby you have to flashback your database, and roll back all changes. But we can escape this.
Hey. Hypothetical situation. You have freshly installed OS Linux, and you wanna install Oracle GRID+RDBMS there. But you have another server with has already installed Oracle. All you need it’s just copy Oracle homes, and do couple steps.
Hey fellas. As you know from previous article, I’ve got the error around ASM block header. Which I also tried to solve with scrubbing mechanism which has appeared in 12c Oracle. You know this mechanism is working well, but only one’s you need to know, you must have at least one type of block (primary or mirror) in correct state, and then the scrubbing mechanism can afford to save your data. But not in my situation which I’ve described in previous article.
Today I’ve stumbled upon on ORA-15196: invalid ASM block header during making backup through RMAN.
Another terse post. Since 12c you can use individual disk bigger than 2Tb in ASM. During creating diskgroup just use compatible attribute.
create diskgroup DATA normal redundancy failgroup FG1 disk 'ORCL:DISK[1-7]' failgroup FG2 disk 'ORCL:DISK[8-9]','ORCL:DISK1[0-4]' ATTRIBUTE 'compatible.asm' = '22.214.171.124', 'compatible.rdbms' = '126.96.36.199'
compatible.rdbms and compatible.asm – is a mandatory attributes.