Monday, March 28, 2011

Small Changes can Break Stuff i.e 11.2 ASMCMD

This is a going to be a small post justo to reiterate the fact that Oracle Keeps changing things on us to keep us moving .

In Oracle 11 ASMCMD introduced md_backup and md_restore to help with managing ASM Metadata.

To script around this and make our scripts universal we used


asmcmd -v to detect version and then proceed with backups.



So in 11.1.0.7

oracle@abc:$ asmcmd -v 
asmcmd version 11.1.0.6.0 


When i migrated to 11.2.0 for ASM my scripts for metadata backup Started failing

running the same command in 11.2.0 netted


oracle@abc:$ asmcmd -v

WARNING: Tracing levelnot specified

Default level of tracing is enabled.

ASMCMD> exit





In 11.2.0 to get version from ASM is

oracle@abc:$ asmcmd -V

asmcmd version 11.2.0.2.0

Not sure if this behaviour changed in 11.2.0.1 or 11.2.0.2 .


Although it would be nice if Oracle would not reuse the same flag for something else just makes our lives and scripts miserable.

Monday, March 21, 2011

Relinking causes many warning on AIX for 11.2.0

As i  started applying the first PSU to my 11.2.0.2 instances. I noticed OPatch generating crazy Ld messages

ld: 0711-319="" defined:="" exported="" freeinstance__14txsoqmdm10gtagfv="" not="" symbol="" warning:="">
ld: 0711-319 WARNING: Exported symbol not defined: freeInstance__17TxsOqSQLConstantsFv
ld: 0711-319 WARNING: Exported symbol not defined: freeInstance__19TxsOqPatternMatcherFv
ld: 0711-319 WARNING: Exported symbol not defined: freeInstance__19TxsOqSnapshotCasterFv
ld: 0711-319 WARNING: Exported symbol not defined: freeInstance__21TxsOqExecutionFactoryFv
ld: 0711-319 WARNING: Exported symbol not defined: freeInstance__21TxsOqRollupGIDManagerFv
ld: 0711-319 WARNING: Exported symbol not defined: freeInstance__22TxsOq11gPatternMatcherFv
ld: 0711-319 WARNING: Exported symbol not defined: freeInstance__24TxsOqSQLDerivationFinderFv

This is a Bug and is explained in Relinking causes many warning on AIX [ID 1189533.1].

Apparently all these messages can be ignored

Sunday, March 20, 2011

Oracle 11.2.0.2 Memory Bug

my installs for 11.2.0.2 were going on . I noticed something peculiar . The Memory utilization on my AIX Box was more than 10.2.0.4 . I looked at it and said well Maybe 11.2.0.2 needs more memory and brushed it off. That was till i read kurtvm's blog.
Apparently there is a bug
This is apparently a bug
From Kurtvm's Blog 
Bug 10211065.-P Base Bug 9796810
Abstract: MEMORY FOOTPRINT FOR DEDICATED SERVER PROCESSES MORE THAN DOUBLED AFTER 11G UGP
  Bug 9796810.-P Base Bug 10190759
Abstract: 11G SERVER PROCESSES CONSUMING MUCH MORE MEMORY THAT 10G OR 9I
 
Bug 10190759.-P
Abstract:  PROCESSES CONSUMING ADDITIONAL MEMORY DUE TO 'USLA HEAP'

 
 
The good news is - there's a 'interim' patch - number 10190759.

On to patching my environments.

Wednesday, March 02, 2011

Upgrade From Oracle 10.2.0.4 to Oracle 11.2.0.2

Below is a simple GUI Method to upgrade your Database from 10.2.0.4 to 11.2.0.2
As part of the upgrade Process from 10.2.0.4 the First Step will be to check the Database for issues.
The Process will be to first install the 11.2.0.2 Software. And the run the @utlu112i.sql which is available in your new Software Home $NEW_ORACLE_HOME/rdbms/admin
Once you run this against your old system
You will see a result like this
-- Start Oracle Upgrade Tool --
Oracle Database 11.2 Pre-Upgrade Information Tool 02-23-2011 13:44:07
Script Version: 11.2.0.2.0 Build: 001
Database:
--> name: DTESTDB
--> version: 10.2.0.4.0
--> compatible: 10.2.0.4
--> blocksize: 8192
--> platform: AIX-Based Systems (64-bit)
--> timezone file: V4
Tablespaces: [make adjustments in the current environment]
--> SYSTEM tablespace is adequate for the upgrade.
.... minimum required size: 2635 MB
--> SYSAUX tablespace is adequate for the upgrade.
.... minimum required size: 440 MB
--> TEMP tablespace is adequate for the upgrade.
.... minimum required size: 61 MB
--> UNDO_01 tablespace is adequate for the upgrade.
.... minimum required size: 32 MB.
**********************************************************************
Update Parameters: [Update Oracle Database 11.2 init.ora or spfile]
Note: Pre-upgrade tool was run on a lower version 64-bit database.
**********************************************************************
--> If Target Oracle is 32-Bit, refer here for Update Parameters:
-- No update parameter changes are required.
.--> If Target Oracle is 64-Bit, refer here for Update Parameters:
-- No update parameter changes are required.
.**********************************************************************
Renamed Parameters: [Update Oracle Database 11.2 init.ora or spfile]
**********************************************************************
-- No renamed parameters found. No changes are required.
.**********************************************************************
Obsolete/Deprecated Parameters: [Update Oracle Database 11.2 init.ora or spfile]
**********************************************************************
Remove all Parameterw listed in here
.**********************************************************************
Components: [The following database components will be upgraded or installed]
**********************************************************************
Check If anything is Invalid .
**********************************************************************
Miscellaneous Warnings
**********************************************************************
WARNING: --> Database contains INVALID objects prior to upgrade.
.... The list of invalid SYS/SYSTEM objects was written to
.... registry$sys_inv_objs.
.... The list of non-SYS/SYSTEM objects was written to
.... registry$nonsys_inv_objs.
.... Use utluiobj.sql after the upgrade to identify any new invalid
.... objects due to the upgrade.
.... USER PUBLIC has 7 INVALID objects.
WARNING: --> Your recycle bin is turned on and currently contains no objects.
.... Because it is REQUIRED that the recycle bin be empty prior to upgrading
.... and your recycle bin is turned on, you may need to execute the command:
PURGE DBA_RECYCLEBIN
.... prior to executing your upgrade to confirm the recycle bin is empty.
.**********************************************************************
Recommendations
**********************************************************************
Oracle recommends gathering dictionary statistics prior to upgrading the database.
To gather dictionary statistics execute the following command
while connected as SYSDBA:
EXECUTE dbms_stats.gather_dictionary_stats;
**********************************************************************
Oracle recommends removing all hidden parameters prior to upgrading.
To view existing hidden parameters execute the following command
while connected AS SYSDBA:
SELECT name,description from SYS.V$PARAMETER WHERE name
LIKE '\_%' ESCAPE '\'
Changes will need to be made in the init.ora or spfile.
**********************************************************************
Oracle recommends reviewing any defined events prior to upgrading.
To view existing non-default events execute the following commands
while connected AS SYSDBA:
Events:
SELECT (translate(value,chr(13)||chr(10),' ')) FROM sys.v$parameter2
WHERE UPPER(name) ='EVENT' AND isdefault='FALSE'
Trace Events:
SELECT (translate(value,chr(13)||chr(10),' ')) from sys.v$parameter2
WHERE UPPER(name) = '_TRACE_EVENTS' AND isdefault='FALSE'
--- End Oracle Upgrade Tool -----
After The Process is complete . Start ./dbua
clip_image002clip_image003
As part of the Upgrade you have an option to Move the datafiles. In this we have chosen no
clip_image005
clip_image006
clip_image008
If you are fine with this Please Proceed . it is recommended that you upgrade your TimeZone File
clip_image010
Please Select Next and A warning will show up if you have decided not to turn off archiving
clip_image012
Select the new Values for you FRA & Diag Dest
clip_image014
Select Grid Control of DB Control Options
clip_image016
Add in the Passwords
clip_image018
It will provide with a summary
clip_image020
Oracle will now start the upgrade Process
clip_image021
This will complete and
Technorati Tags:

Google Search

Powered By Blogger