Environment Standardize Goal :

To standardize the environment that

- flexible to meet on-going consolidation of existing environment
- server as road map for future new applications

Assumptions:
We understand Oracle license and business requirements will
have big influence in determine how to construct the final
environment, it will be assessed case by case bases

The proposal apply for production environment and pre-prod
environment (we can debate on development environment)





Shared vs. Single -Pros & Cons
Advantages of Sharing the ORACLE_HOME
Redundant copies are not needed
Disk space savings.
Patch Oracle can be done more rapidly.

Disadvantages of Sharing the ORACLE_HOME
One ORACLE_HOME directory is patched, All DB bounced
One ORACLE_HOME downtime cause to DB affected.
One App need to upgrade could affect other Apps (not ready)
Harder to troubleshooting the performance issue

Take in consideration of Future Database New Features

One Dedicated OS and One Dedicated Application
Model A
Mission Critical
ABC DB
File system name convention
for Oracle Home and Datafile
is uniquely/apps specific
/oms_db/oracle OracleHome
/oms_db/oradata1 datafiles
/oms_db/OraGrid11gR2

Shared OS with Multiple Unique Application/Oracle Home
Model B
OraHome1
OraHome2
MC1
MC2
MC3
eGIS, work management, Powerplant,
Ebill, eBusiness, PeopleSoft
OraHome3
MC4
OraHome4
File system name convention
for Oracle Home and Datafile is
uniquely/apps specific
/egis_db/oracle OracleHome
/egis_db/oradata1 datafiles
However Grid_Infrastruture
may be globally avaiable to all
applications, therefore file
system is not apps speciafic
/u01/app/OraGrid11gR2

Multiple Unique OracleHome/Version
Model C
e.g.:webApps, etrace,LVMS and
oracle10
OraHome10
oracle10
app1
app2
app3

OraHome11y
Oracle11.
y
app7
app8
app9

OraHome11x
Oracle11.
x
app4
app5
app6

OraHome12
oracle12
app10
app11
app12
If ASM used, the
Grid_Infrastruture will be
globally available to all
applications, therefore file
system is not apps specific
/u01/app/OraGrid11gR2
Since each Oracle
version/home will be shared by
multiple apps databases, we
use the generic file system
/u02/app/oracle/product/version
/u02/app/oracle/product/version
Would like each one version on
its mount point
Common 'tnsnames.ora' and 'sqlnet.ora' naming conventions.
CURRENT STATE: in the South we include the 'WORLD' suffix,
which is not present in the North.
FUTURE STATE: remove the 'WORLD suffix from the:
tnsnames.ora and sqlnet.ora files on all corporate
desktops.
tnsnames.ora and sqlnet.ora files on all UNIX servers.

IMPLEMENTATON:
Windows: This will be done by utilization of SMS push
and it has to be scheduled and coordinated with the
Integration Lab team. A Change Control will need to be
initiated and presented at two consecutive weekly meetings.
UNIX: This will be coordinated with the timing of the
SMS push and it will be implemented by our team. We will utilize
a script to push the change to all of the servers.
Common 'tnsnames.ora' and 'sqlnet.ora' naming conventions.
Decision:
All databases are listed alphabetically by SID name, but separate
north and south section
Because we still will utilize two different desktop configurations
iwe will wait UNTIL we truly merge our desktop images and
have the same/ single tnsnames.ora file, OR


Checklist for building new databases

-Should we be using dbca, or script, or dbca & Script
- DB instance character size (8?) name,
ora+application+environment
-Tablespace naming conventions
-Roles naming convention
-Setting up backups, netback or not



Standard scripts to pro-actively find issue before it occurs
(Monitoring scripts, export, data pump)
1. Usage file system, tablespace, up and down
2. Backup & Export
3. Statistics
4. Error in the alert log
5. Archiving issue




Paging (on-call) alerts.

Is the current way sufficient, pager send to online DBA
Any improvement we can make ?



Discussion

-Q&A
Next Phase TO LIST
Develop a questionnaire document to help & collectively decide
allocation of the application?
Define whats mission critical application
Define the naming convention of instance name
Backup & recovery strategy and standard scripts
Standard monitoring scripts
Installation and Configuration standards
Have meeting with Unix team to validate our plan






Tools Standardize Goal :
Tools Evaluations Goal is to
-Increase the productivity
-Cut the redundancy
-Standardize the tool cross North and South
-Evaluate the licensed tool to see if Free tool does the same
-Have a set of tool that is robust, intuitive and cost effective






Tools Available From Oracle or Free
Oracle Related Tools Used By License Cost
Recommenda
tion Decision Comment
Oracle SQL Developer
DBA/Develop
er N None
Keep it

Oracle OEM- Fat Client DBA N None
Keep it

Oracle EM - Local Database Control -
Web Based DBA N None
Keep it

Oracle Grid Control DBA Y/N Yes
Keep it
Depends
Putty (freeware) DBA None
Keep it

vnc server / client DBA None
Keep it

WinSCP - freeware, ftp DBA None
Keep it

Tools Licensed
Oracle Related Tools Used By License Cost
Recommenda
tion Decision Comment
SQL Navigator - By Quest Software Developer Y Yes Discontinue
Toad - By Quest Software Kam Y Yes Discontinue
Embarcadero DBArtisan DBA Y
$11,563.00, 6
license copies
for MS SQL,7
license copies
for Oracle
Keep it

Red Gate Schema/ Data Compare
DBA Y
Yes (?)
Keep it

Confio Ignite
DBA Y
Yes (?) Discontinue
ERWin (adminstraterd by the IA Modelers) DBA Y
Yes, license
from
Doug
Keep it

Reflections
DBA Y
None Discontinue
Discussion

- Q&A
- Webex, as a tool, do you think is worth to pay $39/Month?