Azerbaijan Oracle User Group - II Meeting

I’ll be speaking at Azerbaijan Oracle User Group II Meeting on July 28th at Qafqaz University. 
As expected, I’ll talk about  "Different operating systems  in same Data Guard configuration"
Here’s the speakers and subjects:
More info (In Azerbaijani) : http://www.azeroug.org/?p=40 

Waiting you to Azerbaijan Oracle User Group II  Meeting
Location: Baku, Azerbaijan

Comments

  1. Ilham AliyevSeptember 22, 2012 at 11:40 PM

    Salam Mahir müəllim, Oracle Database System öyrənmək üçün mənə kömək edə bilərsiniz?Mən Əliyev İlham Elçin oğlu ADNA-nın 2 ci kurs tələbəsiyəm Kompyuter elmleri ixtisası üzrə təhsil alıram

    ReplyDelete
  2. Mahir M. QuluzadeSeptember 24, 2012 at 10:48 AM

    Salam İlham, elimden gelen qeder komek etmek isteyerem.
    Sual olduqca mail yazmagini isteyerdim.

    Mahir

    ReplyDelete
  3. Ilham AliyevSeptember 25, 2012 at 3:50 AM

    men bu systemi oyrenmek cetinliklerine yiyelenmek isterdim bunun ucun ne edim bir derslik vesait kurs ve s. vasiteler bilirsiniz?

    ReplyDelete
  4. Ilham AliyevOctober 2, 2012 at 8:23 PM

    sizden cavab gozleyirem...

    ReplyDelete
  5. Mahir M. QuluzadeOctober 3, 2012 at 9:31 AM

    Ilham mene mail adresini yaza bilersen?

    ReplyDelete
  6. Ilham AliyevOctober 8, 2012 at 6:06 PM

    Aliyev_019@mail.ru

    ReplyDelete
  7. Ilham AliyevOctober 17, 2012 at 12:59 AM

    Salam Mahir muellim size mailler yazmisam gelib?

    ReplyDelete

Post a Comment

Popular posts from this blog

Which device is mapped Oracle ASM disk?

Hi,

Yesterday Yuva Kishore is commented on my Oracleasm - Instantiating disk : failed post and asked a question: We can list the asm disks (listdisks) but where can we find the mapping that ASMDISK1 is mapped to /dev/sda1 and so on? 

I want answer this question with this post.

If you  are using ASMLib for configure ASM Disks, then you can use following steps for define which device mapped which ASM Disk.

As you  know, oracleasm listdisks is return only ASM disk names

[grid@oel62-rac1 ~]$ oracleasm listdisks ASMDISK01 ASMDISK02 ASMDISK03 ASMDISK04 ASMDISK05 [grid@oel62-rac1 ~]$
If you want find which ASM disk is mapped which device, then you must use oracleasm querydisk with ASM disk name.

[grid@oel62-rac1 ~]$ oracleasm querydisk -d ASMDISK01 Disk "ASMDISK01"  Is a valid ASM disk On device[8,17]
As see you, ASMDISK01 is valid ASM disk on device [8,17].

What is means?

It means ASMDISK01 is mapped to device [8,17].

How to find [8,17] device?

 We must use Linux ls –l  c…
Read more

Oracle Data Guard 11g - How to safely remove a Data Guard Broker configuration?

Image
When you need safely remove broker-managed Data Guard Configuration then, oracle recommend following steps…

You know dg_broker_start parameter is TRUE and data guard configuration information contains in broker configuration files dg_broker_config_file1, dg_broker_config_file2 with broker-managed Data Guard Configuration.

Following steps I use on my test machines witch is running on Oracle Virtual Box. I captures video on this machines, too. Primary and Standby Database running on Oracle Linux Server 6.2 and installed Oracle Database 11g Release 2 (11.2.0.3).

DG – is my breoker-managed Data Guard configuration. admdb is primary database, stldb – is standby database.

DGMGRL> show configuration Configuration - dg Protection Mode: MaxPerformance Databases: admdb - Primary database stldb - Physical standby database Fast-Start Failover: DISABLED Configuration Status: SUCCESS
Archive log destinations like as

SQL> show parameter log_archive_dest_ NAME …
Read more

Oracle Database 12c Release 2 - Long Identifiers

Image
Prior to Oracle Database 12c Release 2 have a problem with long identifier name, for example, in 11.2 version you cannot create long name (max 30 Bytes) tables.  As you see, from screenshots length of table name column is maximum 30.



In Oracle Database 12c Release 2 changed the length of identifier names, and this change depends on the COMPATIBLE initialization parameter. Documentation says:

If COMPATIBLE is set to a value of 12.2 or higher, then names must be from 1 to 128 bytes long with these exceptions: Names of databases are limited to 8 bytes. Names of disk groups, pluggable databases (PDBs), rollback segments, tablespaces, and tablespace sets are limited to 30 bytes. If an identifier includes multiple parts separated by periods, then each attribute can be up to 128 bytes long. Each period separator, as well as any surrounding double quotation marks, counts as one byte. For example, suppose you identify a column like this: "schema"."table"."column" …
Read more