Wednesday, September 10, 2014

CIFS performance problem

Today we encountered some performance problems at our customer site. After checking with the customer it seemed that especially the CIFS shares were having problems. At first CIFS was getting slower until the shares were not even accessible anymore.

Restarting the CIFS on the filer did solve the problem for a few minutes, but within half an hour the the problems were back again.

 Checking the /etc/messages file on the filer showed the following error

 Tue Sep 9 16:00:08 CEST [XXX0011:cifs.stats.pBlkExhaust:info]: CIFS: All CIFS control blocks for the STANDARD pool are in use. The request for a new control block can not be granted. 

We solved this problem by breaking the oplocks using the lock break -p cifs command.

After that the CIFS shares became available again for the customer.


 

Thursday, July 24, 2014

SYNC 2014 !

Vanuit Proact organiseren wij het kennisplatform SYNC 2014 op 17 september in de Rotterdam Cruise Terminal. Alle hedendaagse IT-infrastructuurontwikkelingen in 1 dag:
• Een interactief programma o.l.v. dagvoorzitter Lars Sørensen o.a. bekend van BNR
• Een keynote van Marco Gianotten van Giarte, de Nederlandse “Gartner” op het gebied van Outsoucing/Managed Services
• Huisman Equipment over de uitrol van een nieuwe IT-infrastructuur voor diverse locaties wereldwijd • Closing keynote van de Nachtburgemeester van Rotterdam, Jules Deelder
• Innovatie, keynotes en demonstraties van o.a. Cisco, NetApp, EMC en CommVault Maak daarnaast ter plekke kans op een helikopter vlucht langs het Manhattan aan de Maas!

Bekijk het volledige programma en stap aan boord:
www.sync-event.nl

Monday, November 18, 2013

Resizing MGMT_TABLESPACE in Grid Control 12c

We noticed the MGMT_TABLESPACE in our 12c Grid Control instance was very big. Almost 380gb of data was stored in this tablespace.
Because of all the targets registered in this Grid Control instance and the frequent usage of this Grid Control, I did not think anything was wrong.
Untill someone looked into this and found out it was a bug in 12c...

Note 1502370.1 describes this bug and also the solution for this. I had to install a patch and truncate the em_job_metrics table. After applying the patch and truncating the table, there was only around 10gb of data left in the MGMT_TABLESPACE.
Because I already experienced something like this 5 years ago in a 10g OEM instance (
http://basklaassen.blogspot.com/2008/06/resizing-oem-database-10g.html), I knew that is was not easy to reclaim the space in this tablespace. And we had a a lot to reclaim, only 10gb data in this tablespace of 380gb...

I decided to check my Oracle support, maybe someone els already had the same problem. I found bug 17461366, making it impossible to reorg the mgmt_tablespace because of aq objects. Same problem I faced five years ago. Because I really wanted to reclaim the free space (370gb), I decided to follow my own notes. Allthough these steps ware performed on a 10g OEM environment and now I was working with a 12c Grid Control environment.

Just like 5 years ago, I could think of two ways to reclaim the space.
1. export mgmt_tablespace, drop the tablespace and import it again 
2. export sysman, drop repository and, run scripts from the oms_home and import sysman again

Export MGMT_TABLESPACE

Unfortunately, dropping the mgmt_tablespace was a mission impossible. The export succeeded without errors, but I was not able to drop the tablespace. After dropping some related objects that were showing in the errors I recieved, I decided this was not going to work. I restored the database and executed option 2.

Export Sysman user(s)

I decided to follow note 388090.1. This note describes a platform migration for a 10g Grid Control environment, but I could not find any document about a 12c Grid Control environment.

 Just to be sure, I also exported (expdp) the other sysman users (sysman_apm, sysman_mds, sysman_opss and sysman). Also set job_queue_processes to zero
 
The next step was to drop the current repository using the repmanger utility ($OMS_HOME/sysman/admin/emdrep/bin)
The repmanager also did not drop the mgmt_tablespace, I had to drop the tablespace myself. But after deleting the repository I was able to drop the tablespace. The drop repository did drop all the sysman users and other tablespaces

According to the note, before the impdp, I had to run some scripts from the $OMS_HOME/sysman/admin/emdrep/sql/core/latest/admin directory.
These script should create the sysman users and tablespaces. The following sql's were executed :
- admin_create_tablespaces.sql
- admin_create_repos_user.sql
- admin_pre_import.sql
- admin_sys_procs.sql
- admin_profiles.sql
- admin_grants_repos_user.sql
- admin_grants_view_user.sql

Now, you should be ready to inport the sysman scheme again (impdp). But the import showed a lot of errors. Mean reason, the sysman_ro user was not available and the mgmt_ad4j_ts tablespace was not created. Again I decided to drop the sysman user again and start over again. But this time, instead of running the scripts before the import I created a whole new repository using Repmanager.

The new repository did have the sysman_ro user and also the missing tablespace.
At this time I started the import againg, using the 'table_exist_action=replace' option. The repository creation already created the sysman objects, so I wanted the impdp to replace the already created tables with the tables from the dump. I noticed one table creation error in the logfile, the em_job_type_creds_info table was not created by impdp. I had to create this one after the impdp.
Also the other sysman users were not created by the repmanager. I had to create and import these users  (sysman_.mds, sysman_apm and sysman_opss). 

After the import I returned to the note again, to check for post import steps.
Again in $OMS_HOME/sysman/admin/emdrep/sql/core/latest/admin
- admin_recompile_invalid.sql
- admin_create_synonyms.sql
- admin_post_import.sql

Reset the job_queue_processes to its original  value and submit the EM dbms jobs
- admin_submit_dbms_jobs.sql


After compiling, there were still problems with aq objects.
I dropped the aq objects (exec dbms_aqadm.drop_queue_table) and created (dbms_aqadm.create_queue_table) them again. This solved the problemens and also cleared the invalid objects

At this point, there were no invalid objects anymore, so the oms could be started again to see what happens.
Oms started oke and I was able to login 12c Grid Control.

With 12c Grid Control running, I noticed the oms was bouncing every 12 minutes by itself.
I checked the  emctl.msg file in /gc_inst/em/EMGC_OMS1/sysman/log for errors and found the following error.

HealthMonitor Nov 15, 2013 12:57:48 PM PbsAdminMsgListener error: PbsAdminMsgListener thread timed out.
Critical error err=3 detected in module PbsAdminMsgListener
OMS will be restarted. A full thread dump will be generated in the log file






It seemed the em_cntr_queue was missing ? I checked and found out some other queues were also missing (not in the dump ?) I recreated the missing queues (check the queues in an ota Grid environment) and that solved the restart error. Now oms was not restarting by itself anymore.

Reclaimable free space 

After these steps (took me two days...) I reclaimed 370gb. The mgmt_tablespace is now 10gb (instead of the 380gb before). The total size of the entiry database was shrinked from more then 400gb to 22gb !!


Friday, October 18, 2013

Oracle 12c beta exam...

This morning I will be taking the Oracle 12c database install/admin beta exam..
Hoping I am well prepared for this three hour exam...

Friday, September 20, 2013

Strange...

I was checking Oracle 12c again, because of a beta exam end of october, and noticed something strange.

This time I decided to install 12c Grid software first to use the 12c ASM for the 12c database.

After installing ASM, I tried to check the disks available in ASM...


[oracle@localhost ~]$ . oraenv
ORACLE_SID = [oracle] ? +ASM
The Oracle base has been set to /opt/oracle
[oracle@localhost ~]$ sqlplus / as sysasm

SQL*Plus: Release 12.1.0.1.0 Production on Fri Sep 20 16:17:22 2013

Copyright (c) 1982, 2013, Oracle.  All rights reserved.

Connected to:
Oracle Database 12c Enterprise Edition Release 12.1.0.1.0 - 64bit Production
With the Automatic Storage Management option

SQL> select name  from v$asm_disk;

NAME
------------------------------
DBDATA_0000
GRIDDATA_0000


Nothing strange so far..
But before getting this result I made mistake in the query.. instead of v$asm_disk I try to query v$asm_disks. Let's see what happens...

SQL> select name from v$asm_disks;
select name from v$asm_disks
                 *
ERROR at line 1:
ORA-01219: database or pluggable database not open: queries allowed on fixed
tables or views only


A ORA-01219 is the result of this typo ? Strange, I was expecting the ORA-00942 ??

Let's check the Oracle 12c database..

[oracle@localhost ~]$ . oraenv
ORACLE_SID = [+ASM] ? orcl12c
The Oracle base remains unchanged with value /opt/oracle
[oracle@localhost ~]$ sqlplus / as sysdba

SQL*Plus: Release 12.1.0.1.0 Production on Fri Sep 20 16:23:04 2013

Copyright (c) 1982, 2013, Oracle.  All rights reserved.

Connected to:
Oracle Database 12c Enterprise Edition Release 12.1.0.1.0 - 64bit Production
With the Partitioning, Automatic Storage Management, OLAP, Advanced Analytics
and Real Application Testing options

SQL> select name from v$asm_disk;

NAME
------------------------------
DBDATA_0000
GRIDDATA_0000

SQL> select name from v$asm_disks;
select name from v$asm_disks
                 *
ERROR at line 1:
ORA-00942: table or view does not exist

This time the right error is shown.
Just to be sure, how does this look in the 11g version ??

[oracle@localhost ~]$ sqlplus / as sysasm

SQL*Plus: Release 11.2.0.1.0 Production on Fri Sep 20 16:25:18 2013

Copyright (c) 1982, 2009, Oracle.  All rights reserved.

Connected to:
Oracle Database 11g Enterprise Edition Release 11.2.0.1.0 - 64bit Production
With the Real Application Clusters and Automatic Storage Management options

SQL> select name from v$asm_disks;
select name from v$asm_disks
                 *
ERROR at line 1:
ORA-01219: database not open: queries allowed on fixed tables/views only


Same error. So, it's not something in 12c. It looks like normal behaviour...

Friday, July 05, 2013

Connect to pluggable database

After creating the second pluggable database, next step is to connect to the pluggable databases and cretae a tablespace in one of them.

Before connecting, be sure the pluggable databases are listed in the listener.ora..

LISTENER =
  (DESCRIPTION_LIST =
    (DESCRIPTION =
      (ADDRESS = (PROTOCOL = IPC)(KEY = EXTPROC1521))
      (ADDRESS = (PROTOCOL = TCP)(HOST = localhost.localdomain)(PORT = 1521))
    )
  )
SID_LIST_LISTENER =
  (SID_LIST =
    (SID_DESC =
      (SID_NAME = PDBORATEST)
      (ORACLE_HOME = /u01/app/oracle/product/12.1.0)
    )
    (SID_DESC =
      (SID_NAME = PLUGDB02)
      (ORACLE_HOME = /u01/app/oracle/product/12.1.0)
    )
)


So now we are able to make a connection to one of the pluggable databases

[oracle@localhost admin]$ sqlplus / as sysdba

SQL*Plus: Release 12.1.0.1.0 Production on Fri Jul 5 11:05:13 2013

Copyright (c) 1982, 2013, Oracle.  All rights reserved.

Connected to:
Oracle Database 12c Enterprise Edition Release 12.1.0.1.0 - 64bit Production
With the Partitioning, OLAP, Advanced Analytics and Real Application Testing options

SQL> show con_name

CON_NAME
------------------------------
CDB$ROOT


This is still the container database, to connect to the pluggable database..

[oracle@localhost admin]$ sqlplus sys@pdboratest as sysdba

SQL*Plus: Release 12.1.0.1.0 Production on Fri Jul 5 11:06:59 2013

Copyright (c) 1982, 2013, Oracle.  All rights reserved.

Enter password:

Connected to:
Oracle Database 12c Enterprise Edition Release 12.1.0.1.0 - 64bit Production
With the Partitioning, OLAP, Advanced Analytics and Real Application Testing options

SQL> show con_name

CON_NAME
------------------------------
PDBORATEST


In the pdboratest I have created a basefarm tablespace..

SQL> select tablespace_name from dba_tablespaces;

TABLESPACE_NAME
------------------------------
SYSTEM
SYSAUX
TEMP
USERS
BASEFARM01











Let's check the other pluggable database

SQL> show con_name

CON_NAME
------------------------------
PLUGDB02

SQL> select tablespace_name from dba_tablespaces;

TABLESPACE_NAME
------------------------------
SYSTEM
SYSAUX
TEMP
USERS


Tablespace just created is not there.
Lets check the container database..

SQL> show con_name

CON_NAME
------------------------------
CDB$ROOT
SQL> select tablespace_name from dba_tablespaces;

TABLESPACE_NAME
------------------------------
SYSTEM
SYSAUX
UNDOTBS1
TEMP
USERS


Also not visible...

Wednesday, July 03, 2013

Oracle 12c plugable databases

Last week I downloaded the new Oracle 12c database to check this new feature called 'Plugable database'.
Using the runnstaller I fist created the 12c database with the 'Create as container database' option enabled.












After installing the database, I dicided to use the dbca to create another plugable database.



So, there should be 2 plugable databases and one container database right now.
I checked the datafiles location.
Datafiles are located in this example in /media/oracle_data
cd /media/oracle_data/ORATEST
[oracle@localhost ORATEST]$ ls
controlfile  datafile  E0982A74548A0DF8E0430100007FA928  E098787A3ED20F81E0430100007FFC1B  onlinelog






 The E0... directories are the two plugable database directories. Inside these directories are datafiles that belong to that plugable database. Controlfiles and onlinelog files are not in the plugable database directories, only in the container database directory.
At first the plugable directories only have a users, temp, system and sysaux datafile.

Connect to the database (container)

[oracle@localhost ~]$ . oraenv
ORACLE_SID = [oracle] ? oratest
The Oracle base has been set to /u01/app/oracle
 [oracle@localhost ~]$ sqlplus / as sysdba

SQL*Plus: Release 12.1.0.1.0 Production on Wed Jul 3 13:46:34 2013

Copyright (c) 1982, 2013, Oracle.  All rights reserved.


Connected to:
Oracle Database 12c Enterprise Edition Release 12.1.0.1.0 - 64bit Production
With the Partitioning, OLAP, Advanced Analytics and Real Application Testing options


SQL> show con_name

CON_NAME
------------------------------
CDB$ROOT
 


SQL> SELECT v.name, v.open_mode, NVL(v.restricted, 'n/a') "RESTRICTED", d.status
  2  FROM v$pdbs v, dba_pdbs d
  3  WHERE v.guid = d.guid
  4  ORDER BY v.create_scn;

NAME                                OPEN_MODE    RES   STATUS
------------------------------   -----------------      ----    ------------
PDB$SEED                       READ  ONLY      NO    NORMAL
PDBORATEST                  READ  WRITE    NO    NORMAL
PLUGDB02                      READ  WRITE    NO    NORMAL



Next step is to connect to a plugable database and create tablespaces for example...