July 28 - AZEROUG II Meeting

Azerbaijan Oracle User Group Members

On July 28, AZEROUG's (Azerbaijan Oracle User Group) - second meeting took place.This was a technical meeting. We are planned three speech. I, Javid Hasanov and Ramin Orujov.

I spoke about Oracle Data Guard 11g concepts, new features of data guard and  mainly "Different operating systems in same Data Guard configuration". End of the my session I showed video demo on Linux and Windows operating system on  same data guard configuration.

After my speech, Javid Hasanov was speech about Oracle Resource Manager. He showed examples for testing management resources with Oracle Resource Manger . 


Ramin Orujov  showed new features of Oracle PL/SQL. He showed very interesting examples on new features PL/SQL. 
Mahir M. Quluzade


Javid Hasanov

Ramin Orujov
Download my presentation 

You can download all of  speakers presentations from  www.azeroug.org


Regards
Mahir M. Quluzade

Location: Baku, Azerbaijan

Comments

  1. Gokhan AtilAugust 13, 2012 at 1:48 PM

    Hi Mahir,

    It's good to see the activities of AZEROUG. Keep up the good work! By the way, I've felt very proud when I saw the motto "one nation-two states" and Ataturk's picture on the wall, in the first photo.

    Regards

    Gokhan

    ReplyDelete
    Replies
    1. Mahir M. QuluzadeAugust 13, 2012 at 2:52 PM

      This is really we are, one nation - two state!
      Very thanks Gokhan !



      Delete

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