About DB2 Automatic Storage Management

Does it mean that DB2 will create/resize containers of table spaces automatically if we use Automatic Storage Management to manage?
If yes, when DB2 will create new container within a table space?
If yes, when DB2 will resize containers within a table space?
Please advise. thanks so much.
James

Thanks for you reply, I still have some questions.
Q1: When the size of table space need to be increased, by default, which one will occur, (1)DB2 will increase the size of existing container, or (2)add new container?
Q2: When DB2 add new container, whether the new container is added as new stripe set, or added as existing stripe set. I think it should be new stripe set since it can avoid rebalance.
Q3: What's the threshold to trigger size increasing? Can we configure it?
Thanks so much
James

Similar Messages

INS-20802 Automatic Storage Management Configuration Assistant Failed

Dear all,
Please help me to fix this issue, when I install grid infrastructure I have encounter a problem which describe INS-20802 Automatic Storage Management Configuration Assistant Failed.
Could anyone help me to find out this problem?
Thank before hand for you help.
Best Regards,
Vouthea OUN

Dear all,
Please help me to fix this issue, when I install grid infrastructure I have encounter a problem which describe INS-20802 Automatic Storage Management Configuration Assistant Failed.
Could anyone help me to find out this problem?
Thank before hand for you help.
Best Regards,
Vouthea OUN

Automatic Storage Management

Please can someone help me? How can i tell if my 11g database is using automatic storage management. How do i know if oracle grid infrastructure is installed?
thanks

How can i tell if my 11g database is using automatic storage management.You can check using
sql> show parameter db_create_file_dest
If it shows something like +DISKGORUPNAME, the database is using ASM
Also, you can verfity using
select name,state from v$asm_diskgroup;
Is the state shows CONNECTED,then that particular ASM diskgroup is connected with the instance.
Anand

EHPI and DB2 DMS storage management

Hi Guys,
I am having a trouble with Enhancement package installer while applying enchancement packs to ABAP instances in DB2 environment. I am using DMS storage managementmethod in DB2 for tablespace management. While applying the enhancement pack1 for netweaver the installation tool asks for creation of new tables and I create the required tables spaces as I needed. The tool fails with insufficent space in tablespaces. However the tablesspaces are setup to grow when required not like assigned free space in a tablespace.The file system has total 16GB available and it only needs about 3GB. Since it can't see some required freespace available with in the tablespace it can't proceed.
1) Did any one face this issue. IF so how to overcome this issue.
2) Is there anyway we can bypass this check and cotinue with installation. In some steps we can jump with a password but there is no such thing to this step.
Your early reply is highly appreciated.
Regards
Srini

EHPI tool itself check how much space you needed in a tablespace. You have to add that space in tablespace then only you can proceedd otherwise it will always show the error...
thank sunny

Disadvantages Automatic Storage Management

Hi
I'm writing a paper on ASM an have failed to find some significant limitations or disadvantages concerning ASM. Can any one help please.
Thanx...

917996 wrote:
Hi
I'm writing a paper on ASM an have failed to find some significant limitations or disadvantages concerning ASM. Can any one help please.
Thanx...I can say there is dis advantages in any tool.
I can say one example, i have seen of course i have not performed.
its ASM version is 11gR1 i guess, normally CP command will work in ASM from 11g. One of the datafile size is around 17gb instead of copying by RMAN(copy datafile) used CP by ASM, once after copying the file size comes to < 4gb, So as per the limitations only 4gb of file copied remained truncated? ... may be..
On that need to apply Patch or upgrade to next release.. You can list out disadvantages like that so many. you can see in OTN.
HTH.

10G Database install on Linux 64bit File system Vs. Automatic Storage

Hi,
I'm installing Oracle 10G on a Dell 2950 server with an Intel 64 bit processor. The operating system is Red Hat Linux 4. It has a hardware RAID.
I've downloaded the Install Guide but I have a question about installing.
I'm confused about the File system vs. Automatic Storage management option. I will be installing on the local system, I will not be using a NAS or SAN.
Under Database Storage Options, the guide says that "Oracle recommends that the file system you choose be separate from the file systems used by the operating system or the Oracle software.".
1. Do I need to do that since I'm already using hardware RAID??
2. Which way is recommended / what do most people do: File system or Automatic Storage managment??
3. For Automatic Storage Management I read that I'd have to create an ASM Disk group that can consist of "a multiple disk device such as a RAID storage array or logical volume. However, in most cases disk groups consist of one or more individual physical disks". Do I need to reconfigure my partitions ??
I just need some input on what I should do since this is my first time installing Oracle on Linux.
Thank you.

Besides documentation there's a step-by-step guide :
http://www.oracle.com/technology/pub/articles/smiley_10gdb_install.html#asm
Many questions should be answered here.
Werner

Oracle's 10gR2 Automated Storage Management implementation on CentOS 4.1

Actually there are several nice articles on Oracle Technical Network
devoted to the same topic. Whats new may be said ?
The target of message is to highlight the optimal sequence of steps
required to bring Oracle10g (10.2.0.1) ASM-database up on CentOS4.1 , placing ASM instance and serviced databases in different Oracle Homes.
Oracleasm library install is done immediately after creating "oracle"
linux account and "dba" group to be ready for ASM Instance creating during
the first Installer run supposed to build it. ASM instance for disks and disks
group management is created the first by Installer along with the disks group
for database supposed to be built during the second run of Installer and to be
placed into recently created disks group.
I. Oracle 10gR2 ASM and ASMLib 2.0 I/O.
1.Install CentOS 4.1
2.Run as root:
# groupadd dba # group of users to be granted SYSDBA system privilege
# groupadd oinstall # group owner of Oracle files
# useradd -c "Oracle software owner" -g oinstall -G dba oracle
# passwd oracle
# mkdir -p /u01/app/oracle
# chown -R oracle.oinstall /u01
# mkdir -p /u02/oradata/wtfdata
# chown -R oracle.oinstall /u02
OTN instruction:-
Before installing Automatic Storage Management, it is recommended that you install the optional add-on Automatic Storage Management support library, ASMLib. ASMLib is an application program interface (API) Oracle that is aimed at simplifying the interface between the operating system and the database, and to exploit the capabilities and strengths of storage arrays provided by different vendors.ASMLib provides an alternative interface for the Automatic Storage Management-enabled kernel to discover and access block devices. It provides storage and operating system vendors the opportunity to supply extended storage-related features. These features provide benefits such as improved performance and greater data integrity.
OTN instruction ends.
3.To install ASMLIB 2.0 run as root:-
# rpm -Uvh oracleasm-2.6.9-11.ELsmp-2.0.0-1.i686.rpm \
oracleasmlib-2.0.0-1.i386.rpm \
oracleasm-support-2.0.0-1.i386.rpm
Now you get /etc/init.d/oracleasm ready to go.
Configuring the Oracle ASM library driver:-
# /etc/init.d/oracleasm configure
Default user to own the driver interface [oracle]: oracle
Default group to own the driver interface [dba]: dba
Start Oracle ASM library driver on boot (y/n) [y]: y
Fix permissions of Oracle ASM disks on boot (y/n) [y]: y
Writing Oracle ASM library driver configuration: [ OK ]
Scanning system for ASM disks: [ OK ]
# /etc/init.d/oracleasm enable
Create ASM disks as desired utilizing command:
# /etc/init.d/oracleasm createdisk VLM0X /dev/sdx
Tune /etc/sysctl.conf,/etc/security/limits.conf,/etc/pam.d/login, /etc/profile.
and oracle's shell environment as advised in [1].
Login as oracle:-
$ cd /tmp/database
$./runInstaller
OTN instructions:-
Its recommended that you install Automatic Storage Management in its own Oracle home, regardless of whether you plan to only have one or multiple database instances.Installing Automatic Storage Management in its own Oracle home helps ensure higher availability and manageability.
With separate Oracle homes, you can upgrade Automatic Storage Management and databases independently, and you can remove database software without impacting the Automatic Storage Management instance. Ensure that the Automatic Storage Management version is the same or later than the Oracle Database version.If an Automatic Storage Management installation does not already exist and you select the Oracle Universal Installer option to install and configure Automatic Storage Management only, then Oracle Universal Installer installs Automatic Storage Management in its own Oracle home.
OTN instruction ends.
Select " Advanced installation" and
create ASM instance in $ORACLE_HOME=/u01/app/oracle/oracle/product/10.2.0/db_1
Create disk group during this run .
Exit installer.
$ ./runInstaller
Select " Advanced installation" and create new ASM-database placed into existing disk's group
in $ORACLE_HOME=/u01/app/oracle/oracle/product/10.2.0/db_2 .
Modify ~oracle/.bash_profile correspondently.Relogin as oracle.
Next:-
$ sqlplus /nolog
SQL> conn / as sysdba
Connected.
SQL> shutdown immediate;
Database closed.
Database dismounted.
ORACLE instance shut down.
SQL> startup mount;
ORACLE instance started.
Total System Global Area 285212672 bytes
Fixed Size 1218968 bytes
Variable Size 88082024 bytes
Database Buffers 188743680 bytes
Redo Buffers 7168000 bytes
Database mounted.
SQL> alter database archivelog;
Database altered.
SQL> alter database MastDB flashback on;
Database altered.
SQL> alter database open;
Database altered.
Open Enterpise Manager console.(Enterprise Manager 10g Database Control URL
http://ServerCentOS41:1158/em). Create new disk's group for flashback recovery area and modify corresponding value on Recovery Settings page of EM.
System startup in this case should look like:-
[oracle@ServerCentOS41 ~]$ ./lsnrstart
LSNRCTL for Linux: Version 10.2.0.1.0 - Production on 30-AUG-2005 17:57:41
Copyright (c) 1991, 2005, Oracle. All rights reserved.
Starting /u01/app/oracle/product/10.2.0/db_1/bin/tnslsnr: please wait...
TNSLSNR for Linux: Version 10.2.0.1.0 - Production
System parameter file is /u01/app/oracle/product/10.2.0/db_1/network/admin/listener.ora
Log messages written to /u01/app/oracle/product/10.2.0/db_1/network/log/listener.log
Listening on: (DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=ServerCentOS41)(PORT=1521)))
Listening on: (DESCRIPTION=(ADDRESS=(PROTOCOL=ipc)(KEY=EXTPROC1)))
Connecting to (DESCRIPTION=(ADDRESS=(PROTOCOL=TCP)(HOST=ServerCentOS41)(PORT=1521)))
STATUS of the LISTENER
Alias LISTENER
Version TNSLSNR for Linux: Version 10.2.0.1.0 - Production
Start Date 30-AUG-2005 17:57:42
Uptime 0 days 0 hr. 0 min. 0 sec
Trace Level off
Security ON: Local OS Authentication
SNMP OFF
Listener Parameter File /u01/app/oracle/product/10.2.0/db_1/network/admin/listener.ora
Listener Log File /u01/app/oracle/product/10.2.0/db_1/network/log/listener.log
Listening Endpoints Summary...
(DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=ServerCentOS41)(PORT=1521)))
(DESCRIPTION=(ADDRESS=(PROTOCOL=ipc)(KEY=EXTPROC1)))
Services Summary...
Service "PLSExtProc" has 1 instance(s).
Instance "PLSExtProc", status UNKNOWN, has 1 handler(s) for this service...
The command completed successfully
LSNRCTL for Linux: Version 10.2.0.1.0 - Production on 30-AUG-2005 17:57:42
Copyright (c) 1991, 2005, Oracle. All rights reserved.
Starting /u01/app/oracle/product/10.2.0/db_2/bin/tnslsnr: please wait...
TNSLSNR for Linux: Version 10.2.0.1.0 - Production
System parameter file is /u01/app/oracle/product/10.2.0/db_2/network/admin/listener.ora
Log messages written to /u01/app/oracle/product/10.2.0/db_2/network/log/listener.log
Listening on: (DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=ServerCentOS41)(PORT=1522)))
Listening on: (DESCRIPTION=(ADDRESS=(PROTOCOL=ipc)(KEY=EXTPROC2)))
Connecting to (DESCRIPTION=(ADDRESS=(PROTOCOL=TCP)(HOST=ServerCentOS41)(PORT=1522)))
STATUS of the LISTENER
Alias LISTENER
Version TNSLSNR for Linux: Version 10.2.0.1.0 - Production
Start Date 30-AUG-2005 17:57:42
Uptime 0 days 0 hr. 0 min. 0 sec
Trace Level off
Security ON: Local OS Authentication
SNMP OFF
Listener Parameter File /u01/app/oracle/product/10.2.0/db_2/network/admin/listener.ora
Listener Log File /u01/app/oracle/product/10.2.0/db_2/network/log/listener.log
Listening Endpoints Summary...
(DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=ServerCentOS41)(PORT=1522)))
(DESCRIPTION=(ADDRESS=(PROTOCOL=ipc)(KEY=EXTPROC2)))
Services Summary...
Service "PLSExtProc" has 1 instance(s).
Instance "PLSExtProc", status UNKNOWN, has 1 handler(s) for this service...
The command completed successfully
[oracle@ServerCentOS41 ~]$ dbstart
Processing ASM instance "+ASM": log file /u01/app/oracle/product/10.2.0/db_1/startup.log
Processing Database instance "MastDB": log file /u01/app/oracle/product/10.2.0/db_2/startup.log
[oracle@ServerCentOS41 ~]$ emctl start dbconsole
TZ set to US/Eastern
Oracle Enterprise Manager 10g Database Control Release 10.2.0.1.0
Copyright (c) 1996, 2005 Oracle Corporation. All rights reserved.
http://ServerCentOS41:1158/em/console/aboutApplication
Starting Oracle Enterprise Manager 10g Database Control ........................ started.
Logs are generated in directory /u01/app/oracle/oracle/product/10.2.0/db_2/ServerCentOS41_MastDB/sysman/log
Install described above was done with different Oracle Homes
for ASM instance and ASM-database.
To put ASM instance and ASM-database in same Oracle Home.
Start runInstaller just once to build all stuff at a time.
Login as oracle:-
$ cd /tmp/database
$./runInstaller
Select " Advanced option" and install "Software only"
in ORACLE_HOME - /u01/app/oracle/oracle/product/10.2.0/db_1.
Modify oracle's .bash_profile:-
export ORACLE_HOME and new PATH.
Source new .bash_profile:-
$. ~oracle/.bash_profile
$dbca
During this run the request to start CRS daemons by root will come up.
# $ORACLE_HOME/bin/localconfig add
ASM instance , needed disk's groups and ASM-database itself will be created.
Then perform listener and local TNS names configuration.
$netca
II. Oracle 10gR2 ASM and Standard Linux I/O.
This method creates Oracle database files on raw character devices managed by ASM
using standard Linux I/O system calls.It requires to create RAW devices for all
disk partitions used by ASM.
1.Install CentOS 4.1
2.Run as root:
# groupadd dba # group of users to be granted SYSDBA system privilege
# groupadd oinstall # group owner of Oracle files
# useradd -c "Oracle software owner" -g oinstall -G dba oracle
# passwd oracle
# mkdir -p /u01/app/oracle
# chown -R oracle.oinstall /u01
# mkdir -p /u02/oradata/data
# chown -R oracle.oinstall /u02
Just as an example create 4 partitions:
/dev/hda6,/dev/hdc6 5 GB each one
/dev/hda7,/dev/hdc7 3 GB each one
Create raw devices modifying file /etc/sysconfig/rawdevices as follows:
/dev/raw/raw1 /dev/hda6
/dev/raw/raw2 /dev/hdc6
/dev/raw/raw3 /dev/hda7
/dev/raw/raw4 /dev/hdc7
Put in /etc/rc.d/rc.local
chown oracle:dba /dev/raw/raw*
chmod 660 /dev/raw/raw*
I was experiencing problems with loosing "oracle:dba" permissions after Linux
reboot. Oracle's raw device came up with "root:disk" ownership after reboot.
Restart Linux
Run as root:-
# service rawdevices restart
Tune /etc/sysctl.conf,/etc/security/limits.conf,/etc/pam.d/login,
/etc/profile and oracle's shell environment as advised in [1].
Login as oracle:-
$ cd /tmp/database
$./runInstaller
Select " Advanced installation" and
create ASM instance in ORACLE_HOME=/u01/app/oracle/oracle/product/10.2.0/asm
During this run create diskgroup RAWDATA1 with normal redundancy
mirroring /dev/raw/raw1 and /dev/raw/raw2.
You should be fine with discovering raw devices if permissions are in place (oracle:dba)
Exit installer.
Export ORACLE_HOME for ASM instance and corresponding PATH.
Then run "dbca" to create diskgroup RAWDATA2 with
normal redundancy mirroring /dev/raw/raw3 and /dev/raw/raw4
$ ./runInstaller
Select " Advanced installation" and create new ASM-database placed RAWDATA1 diskgroup
in $ORACLE_HOME=/u01/app/oracle/oracle/product/10.2.0/db_1.
Modify ~oracle/.bash_profile correspondently.Relogin as oracle.
Next:-
$ sqlplus /nolog
SQL> conn / as sysdba
Connected.
SQL> shutdown immediate;
Database closed.
Database dismounted.
ORACLE instance shut down.
SQL> startup mount;
ORACLE instance started.
Total System Global Area 285212672 bytes
Fixed Size 1218968 bytes
Variable Size 88082024 bytes
Database Buffers 188743680 bytes
Redo Buffers 7168000 bytes
Database mounted.
SQL> alter database archivelog;
Database altered.
SQL> alter database rawdbs flashback on;
Database altered.
SQL> alter database open;
Database altered.
Open Enterpise Manager console.(Enterprise Manager 10g Database Control
URL http://ServerCentOS41:1158/em). Put flashback recovery area in RAWDATA2
modifying corresponding value on Recovery Settings page of EM.
References.
1.www.puschitz.com/InstallingOracle10g.shtml

[oracle@casa database]$ df -k
Filesystem 1K-blocks Used Available Use% Mounted on
/dev/hda2 70557084 8674712 58298272 13% /
none 387852 0 387852 0% /dev/shm
/dev/hdc 656964 656964 0 100% /media/cdrecorder1So, you have 58298272 bytes available, which is 55MB, and the installer asks for 60 ;) You should probably use df -h instead of df -k...
PS where are you planning to install to with only 55MB available anyway?
~Jer

Oracle 10gR2 Automated Storage Management implementation on CentOS 4.1

Actually there are several nice articles on Oracle Technical Network devoted to the same topic. Whats new may be said ?
The target of this message is to highlight the optimal sequence of steps required to bring Oracle10g (10.2.0.1) ASM-database up on CentOS4.1 , placing ASM instance and serviced databases in different Oracle Homes.Oracleasm library install is done immediately after creating "oracle" linux account and "dba" group to be ready for ASM Instance creating during the first Installer run supposed to build it. ASM instance for disks and disks group management is created the first by Installer along with the disks group for database supposed to be built during the second run of Installer and to be placed into recently created disks group.
I. Oracle 10gR2 ASM and ASMLib 2.0 I/O.
1.Install CentOS 4.1
2.Run as root:
# groupadd dba # group of users to be granted SYSDBA system privilege
# groupadd oinstall # group owner of Oracle files
# useradd -c "Oracle software owner" -g oinstall -G dba oracle
# passwd oracle
# mkdir -p /u01/app/oracle
# chown -R oracle.oinstall /u01
# mkdir -p /u02/oradata/wtfdata
# chown -R oracle.oinstall /u02
OTN instruction:-
Before installing Automatic Storage Management, it is recommended that you install the optional add-on Automatic Storage Management support library, ASMLib. ASMLib is an application program interface (API) Oracle that is aimed at simplifying the interface between the operating system and the database, and to exploit the capabilities and strengths of storage arrays provided by different vendors ASMLib provides an alternative interface for the Automatic Storage Management-enabled kernel to discover and access block devices. It provides storage and operating system vendors the opportunity to supply extended storage-related features. These features provide benefits such as improved performance and greater data integrity.
OTN instruction ends.
3.To install ASMLIB 2.0 run as root:-
# rpm -Uvh oracleasm-2.6.9-11.ELsmp-2.0.0-1.i686.rpm \
oracleasmlib-2.0.0-1.i386.rpm \
oracleasm-support-2.0.0-1.i386.rpm
Now you get /etc/init.d/oracleasm ready to go.
Configuring the Oracle ASM library driver:-
# /etc/init.d/oracleasm configure
Default user to own the driver interface [oracle]: oracle
Default group to own the driver interface [dba]: dba
Start Oracle ASM library driver on boot (y/n) [y]: y
Fix permissions of Oracle ASM disks on boot (y/n) [y]: y
Writing Oracle ASM library driver configuration: [ OK ]
Scanning system for ASM disks: [ OK ]
# /etc/init.d/oracleasm enable
Create ASM disks as desired utilizing command:
# /etc/init.d/oracleasm createdisk VLM0X /dev/sdx
Tune /etc/sysctl.conf,/etc/security/limits.conf,/etc/pam.d/login, /etc/profile.
and oracle's shell environment as advised in [1].
Login as oracle:-
$ cd /tmp/database
$./runInstaller
OTN instructions:-
Its recommended that you install Automatic Storage Management in its own Oracle home, regardless of whether you plan to only have one or multiple database instances.Installing Automatic Storage Management in its own Oracle home helps ensure higher availability and manageability.With separate Oracle homes, you can upgrade Automatic Storage Management and databases independently, and you can remove database software without impacting the Automatic Storage Management instance. Ensure that the Automatic Storage Management version is the same or later than the Oracle Database version.If an Automatic Storage Management installation does not already exist and you select the Oracle Universal Installer option to install and configure Automatic Storage Management only, then Oracle Universal Installer installs Automatic Storage Management in its own Oracle home.
OTN instruction ends.
Select " Advanced installation" and
create ASM instance in $ORACLE_HOME=/u01/app/oracle/oracle/product/10.2.0/db_1
Create disk group during this run .
Exit installer.
$ ./runInstaller
Select " Advanced installation" and create new ASM-database placed into existing disk's group in $ORACLE_HOME=/u01/app/oracle/oracle/product/10.2.0/db_2 .
Modify ~oracle/.bash_profile correspondently.Relogin as oracle.
Next:-
$ sqlplus /nolog
SQL> conn / as sysdba
Connected.
SQL> shutdown immediate;
Database closed.
Database dismounted.
ORACLE instance shut down.
SQL> startup mount;
ORACLE instance started.
Total System Global Area 285212672 bytes
Fixed Size 1218968 bytes
Variable Size 88082024 bytes
Database Buffers 188743680 bytes
Redo Buffers 7168000 bytes
Database mounted.
SQL> alter database archivelog;
Database altered.
SQL> alter database MastDB flashback on;
Database altered.
SQL> alter database open;
Database altered.
Open Enterpise Manager console.(Enterprise Manager 10g Database Control URL
http://ServerCentOS41:1158/em). Create new disk's group for flashback recovery area and modify corresponding value on Recovery Settings page of EM.
System startup in this case should look like:-
[oracle@ServerCentOS41 ~]$ ./lsnrstart
LSNRCTL for Linux: Version 10.2.0.1.0 - Production on 30-AUG-2005 17:57:41
Copyright (c) 1991, 2005, Oracle. All rights reserved.
Starting /u01/app/oracle/product/10.2.0/db_1/bin/tnslsnr: please wait...
TNSLSNR for Linux: Version 10.2.0.1.0 - Production
System parameter file is /u01/app/oracle/product/10.2.0/db_1/network/admin/listener.ora
Log messages written to /u01/app/oracle/product/10.2.0/db_1/network/log/listener.log
Listening on: (DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=ServerCentOS41)(PORT=1521)))
Listening on: (DESCRIPTION=(ADDRESS=(PROTOCOL=ipc)(KEY=EXTPROC1)))
Connecting to (DESCRIPTION=(ADDRESS=(PROTOCOL=TCP)(HOST=ServerCentOS41)(PORT=1521)))
STATUS of the LISTENER
Alias LISTENER
Version TNSLSNR for Linux: Version 10.2.0.1.0 - Production
Start Date 30-AUG-2005 17:57:42
Uptime 0 days 0 hr. 0 min. 0 sec
Trace Level off
Security ON: Local OS Authentication
SNMP OFF
Listener Parameter File /u01/app/oracle/product/10.2.0/db_1/network/admin/listener.ora
Listener Log File /u01/app/oracle/product/10.2.0/db_1/network/log/listener.log
Listening Endpoints Summary...
(DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=ServerCentOS41)(PORT=1521)))
(DESCRIPTION=(ADDRESS=(PROTOCOL=ipc)(KEY=EXTPROC1)))
Services Summary...
Service "PLSExtProc" has 1 instance(s).
Instance "PLSExtProc", status UNKNOWN, has 1 handler(s) for this service...
The command completed successfully
LSNRCTL for Linux: Version 10.2.0.1.0 - Production on 30-AUG-2005 17:57:42
Copyright (c) 1991, 2005, Oracle. All rights reserved.
Starting /u01/app/oracle/product/10.2.0/db_2/bin/tnslsnr: please wait...
TNSLSNR for Linux: Version 10.2.0.1.0 - Production
System parameter file is /u01/app/oracle/product/10.2.0/db_2/network/admin/listener.ora
Log messages written to /u01/app/oracle/product/10.2.0/db_2/network/log/listener.log
Listening on: (DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=ServerCentOS41)(PORT=1522)))
Listening on: (DESCRIPTION=(ADDRESS=(PROTOCOL=ipc)(KEY=EXTPROC2)))
Connecting to (DESCRIPTION=(ADDRESS=(PROTOCOL=TCP)(HOST=ServerCentOS41)(PORT=1522)))
STATUS of the LISTENER
Alias LISTENER
Version TNSLSNR for Linux: Version 10.2.0.1.0 - Production
Start Date 30-AUG-2005 17:57:42
Uptime 0 days 0 hr. 0 min. 0 sec
Trace Level off
Security ON: Local OS Authentication
SNMP OFF
Listener Parameter File /u01/app/oracle/product/10.2.0/db_2/network/admin/listener.ora
Listener Log File /u01/app/oracle/product/10.2.0/db_2/network/log/listener.log
Listening Endpoints Summary...
(DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=ServerCentOS41)(PORT=1522)))
(DESCRIPTION=(ADDRESS=(PROTOCOL=ipc)(KEY=EXTPROC2)))
Services Summary...
Service "PLSExtProc" has 1 instance(s).
Instance "PLSExtProc", status UNKNOWN, has 1 handler(s) for this service...
The command completed successfully
[oracle@ServerCentOS41 ~]$ dbstart
Processing ASM instance "+ASM": log file /u01/app/oracle/product/10.2.0/db_1/startup.log
Processing Database instance "MastDB": log file /u01/app/oracle/product/10.2.0/db_2/startup.log
[oracle@ServerCentOS41 ~]$ emctl start dbconsole
TZ set to US/Eastern
Oracle Enterprise Manager 10g Database Control Release 10.2.0.1.0
Copyright (c) 1996, 2005 Oracle Corporation. All rights reserved.
http://ServerCentOS41:1158/em/console/aboutApplication
Starting Oracle Enterprise Manager 10g Database Control ........................ started.
Logs are generated in directory /u01/app/oracle/oracle/product/10.2.0/db_2/ServerCentOS41_MastDB/sysman/log
Install described above was done with different Oracle Homes
for ASM instance and ASM-database.
To put ASM instance and ASM-database in same Oracle Home.
Start runInstaller just once to build all stuff at a time.
Login as oracle:-
$ cd /tmp/database
$./runInstaller
Select " Advanced option" and install "Software only"
in ORACLE_HOME - /u01/app/oracle/oracle/product/10.2.0/db_1.
Modify oracle's .bash_profile:-
export ORACLE_HOME and new PATH.
Source new .bash_profile:-
$. ~oracle/.bash_profile
$dbca
During this run the request to start CRS daemons by root will come up.
# $ORACLE_HOME/bin/localconfig add
ASM instance , needed disk's groups and ASM-database itself will be created.
Then perform listener and local TNS names configuration.
$netca
II. Oracle 10gR2 ASM and Standard Linux I/O.
This method creates Oracle database files on raw character devices managed by ASM using standard Linux I/O system calls.It requires to create RAW devices for all disk partitions used by ASM.
1.Install CentOS 4.1
2.Run as root:
# groupadd dba # group of users to be granted SYSDBA system privilege
# groupadd oinstall # group owner of Oracle files
# useradd -c "Oracle software owner" -g oinstall -G dba oracle
# passwd oracle
# mkdir -p /u01/app/oracle
# chown -R oracle.oinstall /u01
# mkdir -p /u02/oradata/data
# chown -R oracle.oinstall /u02
Just as an example create 4 partitions:
/dev/hda6,/dev/hdc6 5 GB each one
/dev/hda7,/dev/hdc7 3 GB each one
Create raw devices modifying file /etc/sysconfig/rawdevices as follows:
/dev/raw/raw1 /dev/hda6
/dev/raw/raw2 /dev/hdc6
/dev/raw/raw3 /dev/hda7
/dev/raw/raw4 /dev/hdc7
Put in /etc/rc.d/rc.local
chown oracle:dba /dev/raw/raw*
chmod 660 /dev/raw/raw*
I was experiencing problems with loosing "oracle:dba" permissions after Linux
reboot. Oracle's raw device came up with "root:disk" ownership after reboot.
Restart Linux
Run as root:-
# service rawdevices restart
Tune /etc/sysctl.conf,/etc/security/limits.conf,/etc/pam.d/login,
/etc/profile and oracle's shell environment as advised in [1].
Login as oracle:-
$ cd /tmp/database
$./runInstaller
Select " Advanced installation" and
create ASM instance in ORACLE_HOME=/u01/app/oracle/oracle/product/10.2.0/asm
During this run create diskgroup RAWDATA1 with normal redundancy
mirroring /dev/raw/raw1 and /dev/raw/raw2.
You should be fine with discovering raw devices if permissions are in place (oracle:dba)
Exit installer.
Export ORACLE_HOME for ASM instance and corresponding PATH.
Then run "dbca" to create diskgroup RAWDATA2 with
normal redundancy mirroring /dev/raw/raw3 and /dev/raw/raw4
$ ./runInstaller
Select " Advanced installation" and create new ASM-database placed RAWDATA1 diskgroup
in $ORACLE_HOME=/u01/app/oracle/oracle/product/10.2.0/db_1.
Modify ~oracle/.bash_profile correspondently.Relogin as oracle.
Next:-
$ sqlplus /nolog
SQL> conn / as sysdba
Connected.
SQL> shutdown immediate;
Database closed.
Database dismounted.
ORACLE instance shut down.
SQL> startup mount;
ORACLE instance started.
Total System Global Area 285212672 bytes
Fixed Size 1218968 bytes
Variable Size 88082024 bytes
Database Buffers 188743680 bytes
Redo Buffers 7168000 bytes
Database mounted.
SQL> alter database archivelog;
Database altered.
SQL> alter database rawdbs flashback on;
Database altered.
SQL> alter database open;
Database altered.
Open Enterpise Manager console.(Enterprise Manager 10g Database Control
URL http://ServerCentOS41:1158/em). Put flashback recovery area in RAWDATA2
modifying corresponding value on Recovery Settings page of EM.
References.
1.www.puschitz.com/InstallingOracle10g.shtml
Message was edited by:
[email protected]

Actually there are several nice articles on Oracle Technical Network devoted to the same topic. Whats new may be said ?
The target of this message is to highlight the optimal sequence of steps required to bring Oracle10g (10.2.0.1) ASM-database up on CentOS4.1 , placing ASM instance and serviced databases in different Oracle Homes.Oracleasm library install is done immediately after creating "oracle" linux account and "dba" group to be ready for ASM Instance creating during the first Installer run supposed to build it. ASM instance for disks and disks group management is created the first by Installer along with the disks group for database supposed to be built during the second run of Installer and to be placed into recently created disks group.
I. Oracle 10gR2 ASM and ASMLib 2.0 I/O.
1.Install CentOS 4.1
2.Run as root:
# groupadd dba # group of users to be granted SYSDBA system privilege
# groupadd oinstall # group owner of Oracle files
# useradd -c "Oracle software owner" -g oinstall -G dba oracle
# passwd oracle
# mkdir -p /u01/app/oracle
# chown -R oracle.oinstall /u01
# mkdir -p /u02/oradata/wtfdata
# chown -R oracle.oinstall /u02
OTN instruction:-
Before installing Automatic Storage Management, it is recommended that you install the optional add-on Automatic Storage Management support library, ASMLib. ASMLib is an application program interface (API) Oracle that is aimed at simplifying the interface between the operating system and the database, and to exploit the capabilities and strengths of storage arrays provided by different vendors ASMLib provides an alternative interface for the Automatic Storage Management-enabled kernel to discover and access block devices. It provides storage and operating system vendors the opportunity to supply extended storage-related features. These features provide benefits such as improved performance and greater data integrity.
OTN instruction ends.
3.To install ASMLIB 2.0 run as root:-
# rpm -Uvh oracleasm-2.6.9-11.ELsmp-2.0.0-1.i686.rpm \
oracleasmlib-2.0.0-1.i386.rpm \
oracleasm-support-2.0.0-1.i386.rpm
Now you get /etc/init.d/oracleasm ready to go.
Configuring the Oracle ASM library driver:-
# /etc/init.d/oracleasm configure
Default user to own the driver interface [oracle]: oracle
Default group to own the driver interface [dba]: dba
Start Oracle ASM library driver on boot (y/n) [y]: y
Fix permissions of Oracle ASM disks on boot (y/n) [y]: y
Writing Oracle ASM library driver configuration: [ OK ]
Scanning system for ASM disks: [ OK ]
# /etc/init.d/oracleasm enable
Create ASM disks as desired utilizing command:
# /etc/init.d/oracleasm createdisk VLM0X /dev/sdx
Tune /etc/sysctl.conf,/etc/security/limits.conf,/etc/pam.d/login, /etc/profile.
and oracle's shell environment as advised in [1].
Login as oracle:-
$ cd /tmp/database
$./runInstaller
OTN instructions:-
Its recommended that you install Automatic Storage Management in its own Oracle home, regardless of whether you plan to only have one or multiple database instances.Installing Automatic Storage Management in its own Oracle home helps ensure higher availability and manageability.With separate Oracle homes, you can upgrade Automatic Storage Management and databases independently, and you can remove database software without impacting the Automatic Storage Management instance. Ensure that the Automatic Storage Management version is the same or later than the Oracle Database version.If an Automatic Storage Management installation does not already exist and you select the Oracle Universal Installer option to install and configure Automatic Storage Management only, then Oracle Universal Installer installs Automatic Storage Management in its own Oracle home.
OTN instruction ends.
Select " Advanced installation" and
create ASM instance in $ORACLE_HOME=/u01/app/oracle/oracle/product/10.2.0/db_1
Create disk group during this run .
Exit installer.
$ ./runInstaller
Select " Advanced installation" and create new ASM-database placed into existing disk's group in $ORACLE_HOME=/u01/app/oracle/oracle/product/10.2.0/db_2 .
Modify ~oracle/.bash_profile correspondently.Relogin as oracle.
Next:-
$ sqlplus /nolog
SQL> conn / as sysdba
Connected.
SQL> shutdown immediate;
Database closed.
Database dismounted.
ORACLE instance shut down.
SQL> startup mount;
ORACLE instance started.
Total System Global Area 285212672 bytes
Fixed Size 1218968 bytes
Variable Size 88082024 bytes
Database Buffers 188743680 bytes
Redo Buffers 7168000 bytes
Database mounted.
SQL> alter database archivelog;
Database altered.
SQL> alter database MastDB flashback on;
Database altered.
SQL> alter database open;
Database altered.
Open Enterpise Manager console.(Enterprise Manager 10g Database Control URL
http://ServerCentOS41:1158/em). Create new disk's group for flashback recovery area and modify corresponding value on Recovery Settings page of EM.
System startup in this case should look like:-
[oracle@ServerCentOS41 ~]$ ./lsnrstart
LSNRCTL for Linux: Version 10.2.0.1.0 - Production on 30-AUG-2005 17:57:41
Copyright (c) 1991, 2005, Oracle. All rights reserved.
Starting /u01/app/oracle/product/10.2.0/db_1/bin/tnslsnr: please wait...
TNSLSNR for Linux: Version 10.2.0.1.0 - Production
System parameter file is /u01/app/oracle/product/10.2.0/db_1/network/admin/listener.ora
Log messages written to /u01/app/oracle/product/10.2.0/db_1/network/log/listener.log
Listening on: (DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=ServerCentOS41)(PORT=1521)))
Listening on: (DESCRIPTION=(ADDRESS=(PROTOCOL=ipc)(KEY=EXTPROC1)))
Connecting to (DESCRIPTION=(ADDRESS=(PROTOCOL=TCP)(HOST=ServerCentOS41)(PORT=1521)))
STATUS of the LISTENER
Alias LISTENER
Version TNSLSNR for Linux: Version 10.2.0.1.0 - Production
Start Date 30-AUG-2005 17:57:42
Uptime 0 days 0 hr. 0 min. 0 sec
Trace Level off
Security ON: Local OS Authentication
SNMP OFF
Listener Parameter File /u01/app/oracle/product/10.2.0/db_1/network/admin/listener.ora
Listener Log File /u01/app/oracle/product/10.2.0/db_1/network/log/listener.log
Listening Endpoints Summary...
(DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=ServerCentOS41)(PORT=1521)))
(DESCRIPTION=(ADDRESS=(PROTOCOL=ipc)(KEY=EXTPROC1)))
Services Summary...
Service "PLSExtProc" has 1 instance(s).
Instance "PLSExtProc", status UNKNOWN, has 1 handler(s) for this service...
The command completed successfully
LSNRCTL for Linux: Version 10.2.0.1.0 - Production on 30-AUG-2005 17:57:42
Copyright (c) 1991, 2005, Oracle. All rights reserved.
Starting /u01/app/oracle/product/10.2.0/db_2/bin/tnslsnr: please wait...
TNSLSNR for Linux: Version 10.2.0.1.0 - Production
System parameter file is /u01/app/oracle/product/10.2.0/db_2/network/admin/listener.ora
Log messages written to /u01/app/oracle/product/10.2.0/db_2/network/log/listener.log
Listening on: (DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=ServerCentOS41)(PORT=1522)))
Listening on: (DESCRIPTION=(ADDRESS=(PROTOCOL=ipc)(KEY=EXTPROC2)))
Connecting to (DESCRIPTION=(ADDRESS=(PROTOCOL=TCP)(HOST=ServerCentOS41)(PORT=1522)))
STATUS of the LISTENER
Alias LISTENER
Version TNSLSNR for Linux: Version 10.2.0.1.0 - Production
Start Date 30-AUG-2005 17:57:42
Uptime 0 days 0 hr. 0 min. 0 sec
Trace Level off
Security ON: Local OS Authentication
SNMP OFF
Listener Parameter File /u01/app/oracle/product/10.2.0/db_2/network/admin/listener.ora
Listener Log File /u01/app/oracle/product/10.2.0/db_2/network/log/listener.log
Listening Endpoints Summary...
(DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=ServerCentOS41)(PORT=1522)))
(DESCRIPTION=(ADDRESS=(PROTOCOL=ipc)(KEY=EXTPROC2)))
Services Summary...
Service "PLSExtProc" has 1 instance(s).
Instance "PLSExtProc", status UNKNOWN, has 1 handler(s) for this service...
The command completed successfully
[oracle@ServerCentOS41 ~]$ dbstart
Processing ASM instance "+ASM": log file /u01/app/oracle/product/10.2.0/db_1/startup.log
Processing Database instance "MastDB": log file /u01/app/oracle/product/10.2.0/db_2/startup.log
[oracle@ServerCentOS41 ~]$ emctl start dbconsole
TZ set to US/Eastern
Oracle Enterprise Manager 10g Database Control Release 10.2.0.1.0
Copyright (c) 1996, 2005 Oracle Corporation. All rights reserved.
http://ServerCentOS41:1158/em/console/aboutApplication
Starting Oracle Enterprise Manager 10g Database Control ........................ started.
Logs are generated in directory /u01/app/oracle/oracle/product/10.2.0/db_2/ServerCentOS41_MastDB/sysman/log
Install described above was done with different Oracle Homes
for ASM instance and ASM-database.
To put ASM instance and ASM-database in same Oracle Home.
Start runInstaller just once to build all stuff at a time.
Login as oracle:-
$ cd /tmp/database
$./runInstaller
Select " Advanced option" and install "Software only"
in ORACLE_HOME - /u01/app/oracle/oracle/product/10.2.0/db_1.
Modify oracle's .bash_profile:-
export ORACLE_HOME and new PATH.
Source new .bash_profile:-
$. ~oracle/.bash_profile
$dbca
During this run the request to start CRS daemons by root will come up.
# $ORACLE_HOME/bin/localconfig add
ASM instance , needed disk's groups and ASM-database itself will be created.
Then perform listener and local TNS names configuration.
$netca
II. Oracle 10gR2 ASM and Standard Linux I/O.
This method creates Oracle database files on raw character devices managed by ASM using standard Linux I/O system calls.It requires to create RAW devices for all disk partitions used by ASM.
1.Install CentOS 4.1
2.Run as root:
# groupadd dba # group of users to be granted SYSDBA system privilege
# groupadd oinstall # group owner of Oracle files
# useradd -c "Oracle software owner" -g oinstall -G dba oracle
# passwd oracle
# mkdir -p /u01/app/oracle
# chown -R oracle.oinstall /u01
# mkdir -p /u02/oradata/data
# chown -R oracle.oinstall /u02
Just as an example create 4 partitions:
/dev/hda6,/dev/hdc6 5 GB each one
/dev/hda7,/dev/hdc7 3 GB each one
Create raw devices modifying file /etc/sysconfig/rawdevices as follows:
/dev/raw/raw1 /dev/hda6
/dev/raw/raw2 /dev/hdc6
/dev/raw/raw3 /dev/hda7
/dev/raw/raw4 /dev/hdc7
Put in /etc/rc.d/rc.local
chown oracle:dba /dev/raw/raw*
chmod 660 /dev/raw/raw*
I was experiencing problems with loosing "oracle:dba" permissions after Linux
reboot. Oracle's raw device came up with "root:disk" ownership after reboot.
Restart Linux
Run as root:-
# service rawdevices restart
Tune /etc/sysctl.conf,/etc/security/limits.conf,/etc/pam.d/login,
/etc/profile and oracle's shell environment as advised in [1].
Login as oracle:-
$ cd /tmp/database
$./runInstaller
Select " Advanced installation" and
create ASM instance in ORACLE_HOME=/u01/app/oracle/oracle/product/10.2.0/asm
During this run create diskgroup RAWDATA1 with normal redundancy
mirroring /dev/raw/raw1 and /dev/raw/raw2.
You should be fine with discovering raw devices if permissions are in place (oracle:dba)
Exit installer.
Export ORACLE_HOME for ASM instance and corresponding PATH.
Then run "dbca" to create diskgroup RAWDATA2 with
normal redundancy mirroring /dev/raw/raw3 and /dev/raw/raw4
$ ./runInstaller
Select " Advanced installation" and create new ASM-database placed RAWDATA1 diskgroup
in $ORACLE_HOME=/u01/app/oracle/oracle/product/10.2.0/db_1.
Modify ~oracle/.bash_profile correspondently.Relogin as oracle.
Next:-
$ sqlplus /nolog
SQL> conn / as sysdba
Connected.
SQL> shutdown immediate;
Database closed.
Database dismounted.
ORACLE instance shut down.
SQL> startup mount;
ORACLE instance started.
Total System Global Area 285212672 bytes
Fixed Size 1218968 bytes
Variable Size 88082024 bytes
Database Buffers 188743680 bytes
Redo Buffers 7168000 bytes
Database mounted.
SQL> alter database archivelog;
Database altered.
SQL> alter database rawdbs flashback on;
Database altered.
SQL> alter database open;
Database altered.
Open Enterpise Manager console.(Enterprise Manager 10g Database Control
URL http://ServerCentOS41:1158/em). Put flashback recovery area in RAWDATA2
modifying corresponding value on Recovery Settings page of EM.
References.
1.www.puschitz.com/InstallingOracle10g.shtml
Message was edited by:
[email protected]

Redirected restore - automatic storage - using DB2 api not br tools

I've done 100+ redirected restores for non-automatic storage databases using TSM only using the DB2 api's - and not the BR tools .
Now, I'm challenged with a redirect automatic storage DB.
*SQL1277N Restore has detected that one or more table space containers are*
inaccessible, or has set their state to 'storage must be defined'.
DB20000I The RESTORE DATABASE command completed successfully.
The backup image gets read and the TAG's for the containers are build. I can see that by doing a "df" on the filesystem level. But as soon as the restores attempts to write data into the containers, I get the above error message.
Here are my steps:
1. offline backup using db2 api on source
2. create restore script
RESTORE DB DCC use adsm open 4 sessions TAKEN AT 20080722155529 on /db2/SCC/sapdata1,/db2/SCC/sapdata2,/db2/SCC/sapdata3,/db2/SCC/sapdata4 ,/db2/SCC/sapdata5,/db2/SCC/sapdata6,/db2/SCC/saptemp1 dbpath on /db2/SCC INTO SCC NEWLOGPATH /db2/SCC/log_dir with 16 buffers REPLACE EXISTING redirect parallelism 2 without rolling forward without prompting
3. drop the target db and clean out all sapdata's and saptemp
4. create db on target:db2 create database scc automatic storage yes on /db2/SCC/sapdata1,/db2/SCC/sapdata2,/db2/SCC/sa**
+pdata3,/db2/SCC/sapdata4,/db2/SCC/sapdata5,/db2/SCC/saptemp1 dbpath on /db2/SCC+
5. update target db cfg with tsm parms so that it will be able to read the TSM tapes. ie tsm_mgmtclass, tsm_nodename, tsm_owner, tsm_password
6. setup my dsm.opt with
+SErvername       redirect_restore+
and the dsm.sys with a new stanza
SErvername redirectrestore_
   SchedMode            PROMPT
   nodename             useagan1743ddb2_
   PasswordAccess       prompt
   COMMMethod         TCPip
   TCPPort            1500
   TCPServeraddress     unixtsm1p.ecolab.com
7. as root I run the /db2/db2<sid>/sqllib/adsm/dsmapipw password to make sure to have access to the tsm nodename.
8. execute restore script on target
RESTORE DB DCC use adsm open 4 sessions TAKEN AT 20080722155529 on /db2/SCC/sapdata1,/db2/SCC/sa
pdata2,/db2/SCC/sapdata3,/db2/SCC/sapdata4 ,/db2/SCC/sapdata5,/db2/SCC/sapdata6,/db2/SCC/saptemp
1 dbpath on /db2/SCC INTO SCC NEWLOGPATH /db2/SCC/log_dir with 16 buffers REPLACE EXISTING redir
ect parallelism 2 without rolling forward without prompting;

Hello Anke,
Looks like your create database statement is missing the collating sequence, codeset etc. Here is a database create statement I got from my sapinst for your reference:
create database SX1
automatic storage yes on /db2/SX1/sapdata1, /db2/SX1/sapdata2, /db2/SX1/sapdat
a3, /db2/SX1/sapdata4
dbpath on /db2/SX1
using codeset UTF-8
territory en_US
collate using IDENTITY_16BIT
pagesize 16 k
dft_extent_sz 2
catalog tablespace managed by automatic storage extentsize 2
with 'SAP database SX1';
Regards,

My ipod wont update any apps, it says something about storage managment but i have 4 gigs left and all of my iclous storage left. Is their ayway to fix this

my app store wont let me update any apps when i click the update all button it doesnt do anything and eventually says i need to manage my storage, i have 4.4 gigs left and all of my icloud storage left and i just deleted 5 app hoping it would make room but it didnt work. is there something that happened to itouch 3rd gen during th ios5 update or something? please let me know if there is anything i can do

it says something about storage management
Try these support articles...
iCloud: Managing your iCloud storage
iCloud: Purchasing iCloud Storage and Billing

Question about 11gR2 Grid, RAC, /dev/shm and Automatic Memory Management

Hello,
i've recently installed grid and rdbms software 11.2.0.2 on a two node Oracle Linux cluster with 128gb ram each node.
I'm using ASM to store data and ocr and I'm testing Automatic Memory Management.
When I finished Grid+RDBMS installation I've seen that /dev/shm size is 64gb (half of my total RAM).
I've created a database with dbca and when I was asked to choose if I wanted to use AMM I've noticed that I could
allocate only about 60gb for Oracle. If I chose more than 90gb I got an error saying:
Using Automatic Memory Management requires 60gb available in my two nodes.
The current available space in the two nodes is only 30gb and 30gb.
If you want to use AMM you should either free up some space in /dev/shm
or reduce the memory allocated to Oracle
I was wondering when (during the installation or the settings of kernel parameters) did I define the space of /dev/shm ?
Since I have 128gb of RAM wouldn't it be better to use more than 64gb of ram for my /dev/shm tmpfs partition ?
Is there a limit or a ratio for best practice for my RAM and the /dev/shm ?
thanks in advance.

user9051299 wrote:
Is the "half of the RAM size" a kernel's default value or Oracle's ? Neither. There are a number of unique factors that determine the best memory size and fit for Oracle - including just how much memory is effectively available (i.e. how much is needed for other services and processes).
And from what I understand i don't "break" any Oracle's best practice by increasing the /dev/shm right ?Correct. (at least none that I'm aware of, and none that I have read in Oracle's RAC Starter Kit documentation).

Automatic storage location view creation in maintenace order (IW31)

Hello,
Seems like I need some help.
Have configured automatic storage location view creation for GR and reservation. Configured movement types are 101, 201, 261. While creating reservations (201, 261 mvmnt. types) with mb21 the sloc view is automatically created in material master, and everything seems fine.
But in iw31 when I specify material number and sloc in a Components tab, I get an error message CO312: "The storage location data is not created". Automatic reservation is not created, and maintenance order can not be saved. Movement type 261 is used for automatic reservations for the maintenance order.
If I configure message CO312 as a (W)arning message, then it allows me to save the order and reservation, but sloc view in material master still is not created. Think that's not good and may lead to MRP issues.
How can I configure automatic sloc view creation in iw31? Is that possible?
Edited by: Konstantin Dudura on Nov 17, 2009 8:11 PM

Hi,
The customization required for Automatic Storage location creation at reservation are:
Goto : SPRO -> MM -> inventory Management and physical inventory -> Goods issue/ Transfer posting -> Create storage location automatically
first of all go to Plant and tick the automatic Storage location creation for the Plant. After that goto Movement type and tick the automatic Storage location for movement type 261.
Regards

How do you set Automatic Acoustic Management (AAM) for new Hard Drive?

I have a new hard drive that I'm about to have installed into my iMac. The drive is a WD1001FALS (Western Digital Caviar Black 1TB). The only concern I have is that by all accounts it is a bit louder than some other drives, although everything being relative I don't know what that means to me since I've not heard it run yet.
Still, the 320GB drive currently in the iMac is absolutely inaudible and while I'll make some concessions for speed and size I'd like to minimize the amount of noise coming out of the box. I know that the drive supports Automatic Acoustic Management (AAM), however its default state is "disabled". Is there a way, either through the OS or third party software to enable this feature?

I just wanted to close out this question.
I never received a clear answer but in the end I don't need to use the function. My concern was that a new WD1001FALS would be louder than the OEM 320GB HDD in my iMac to the point that I wouldn't be happy with it. Not wanting to trade speed for quiet I passed on the Green caviar and went for the Black. After living with it for several weeks I can say that it is very quiet and while I don't know if it's measurably louder than the old drive, it's not enough for me to notice (and I'm pretty picky).
So, I'm happy with the drive as-is, case closed.

Oracle Suggested Backup, to tape only - Tivoli Storage Manager

I´ve been asked to cancel future backups to disk and to setup oracle´s suggested backup to the tape device only (which underwater is the tdpo from Tivoli´s storage manager).
This way the expensive disks can be freed from recovery data.
I´ve had my share of problems with the tdpo, but besides the problem of this gateway driver between RMAN and TSM I would like to know if this is best for the whole suggested backup strategy.
Somehow I´m not convinced in backing up to "tape" devices only; for it is slower than local disks, and because we had problems before with the driver, but there may be a lot more reasosn why I should or should not accept this desired goal to be best for our company.
I hope some of you can help me straighten my vision on this.
Robin

The biggest problems I think we might face are the
big question "who is responsible for what", and the
administration of non Oracle systems/methods to
perform backupsi have no problems with such a setup. i provide the rman skript which will be called by TSM.
the TSM admins notify me if the backup failed. retention on TSM side is disabled, only RMAN deletes obsolete/expired backups.
All I want to care about is performing a backup to
Disk, or Disk and Tape, or just Tape from within
Oracle/RMAN and read the ouput from here.
Now where these external tape labraries like TSM come
in there will be more administration for the total
handling of a backup job. It´s not only RMAN, but a
tdpo and a TSM server which need to be monitored
closely. of course TSM has to be monitored but if you already have invested an infrastructure you should use it for every type of backups.
Sadly Oracle has yet to come up with it´s secure
backup for TSM systems, but I think it would be best
if I could let Oracle solely in charge of its own
backups.if TSM retention is disabled, RMAN has absolute control.
Then again, I don´t know if anyone has good
experiences with TSM as the only backup provider for
Oracle backups. (so no disk backups)it works very good. use staged pools on TSM. primary pool should be diskpool, secondary a tapepool. you can configure TSM to move the data from disk to tape based on fill level or age.
regards,
-ap

Install Real Application Clusters (RAC) and Automated Storage Management (A

Do I have to install Real Application Clusters (RAC) and Automated Storage Management (ASM) for ETL
I have installed Oracle 10g Release 1 on WIndows 2000 with datawarehousing option.
Is it ok
Or do I need to install Oracle database again.
Please help

Greg,
From what you describe you did exactly the right thing. The runtime platform service will by default run on DWH01, but you can shut it down on that node and have it run on DWH02 (in case you wanted to bring down DWH01 but still run Warehouse Builder processes). Note that we strongly recommend using the net service name in the location registration in the deployment manager (so that you automatically take advantage of the client-side load balancing feature of RAC (as well as the server-side load balancing)).
Thanks,
Mark.

About DB2 Automatic Storage Management

Similar Messages

Maybe you are looking for