PROJECT MANAGEMENT (PMP-1) - KNOWLEDGE AREAS & PROCESS GROUPS

PROJECT MANAGEMENT - KNOWLEDGE AREAS & PROCESS GROUPS


KNOWLEDGE AREAS
As per PMI (Project Management Institute) below are the 9 Knowledge Areas for a Project Manager to manage the projects.

1. Integration Management
2. Scope Management
3. Time Management
4. Cost Management
5. Quality Management
6. Human Resource Management
7. Communication Management
8. Risk Management
9. Procurement Management


PROCESS GROUPS
Every Knowledge Areas has below mentioned 5 Process Groups.

1. Initiate
2. Plan
3. Execute
4. Monitor & Control
5. Close

TROUBLESHOOTING - X-server Xming unable to take input for Oracle FMW, Weblogic, DBCA wizard redirected using DISPLAY redirection

ISSUE:
X-server Xming unable to take input for Oracle FMW, Weblogic, DBCA wizard redirected using DISPLAY redirection

Recently while doing an OBIEE softtware install on linux server using EXPORT DISPLAY variable and rdirecting outout to a wintel machine using X-server like Xming, I was unable to provide keyboard input for Oracle FMW, Weblogic, DBCA wizard, as given  in below screenshots.





SOLUTION:
There was no solution found on MOS but after investigation it has been found that this kind of issue might appear due to incorrect JAVA version compatibility between XMing, Oracle software wizzards in commEnv.sh.

In order to fix the issue, I had to use a lower JDK version from a temp location.

1.) Download JDK version 1.6.0_45 could be downloaded from below URL:

http://www.oracle.com/technetwork/java/javase/downloads/java-archive-downloads-javase6-419409.html

2.) Once downloaded, extract install JDK in a temp location say /opt/oracle/test_java/jdk1.6.0_45

3.) Take the backup of commEnv.sh present inside <FMW_HOME>/wlserver_10.3/commn/bin

4.) Open the commEnv.sh and find JAVA_HOME
Comment out the exising higher version JAVA_HOME path and add New JAVA_HOME value for lower version JDK.

JAVA_HOME="usr/java/jdk1.7.0_05"
JAVA_HOME="/opt/oracle/test_java/jdk1.6.0_45"



5.) Save the file.

6.) Close the Oracle FMW, Weblogic, DBCA wizard on wintel.

7.) Execute the command fro Lnux machine using XMing & DISPLAY variable and this time you should be able to use keyboard and mouse successfully in the wizzard.

8.) Once wizzard run successfully. Rvert back the JDK version in commEnv.sh to original values for JDK higher version.

TRAINING (ORA-10) - Shutting Down Database & Instance Recovery

Different Shutdown Modes of an Oracle Database

There can be four different shutdown mode.
1.) ABORT

2.) IMMEDIATE

3.) TRANSACTIONAL

4.) NORMAL

What can be done in different shutdown modes



A = ABORT        I = IMMEDIATE        T = TRANSACTIONAL        N = NORMAL

What happens During shutdown

A.) For a Consistent (Clean) Database

B.) For an Inconsistent (Dirty) Database

Instance or crash recovery

> Is caused by attempts to open a database whose files were not synchronized on shutdown

> Is automatic

> Uses information stored in redo log groups to synchronize files

> Involves two distinct operations

         Rolling Forward: Data files are restored to their state before the instance failed.

         Rolling Back: Changes made but not committed are returned to their original state.

Phase of Instance Recovery

- Data files out-of-sync

- Roll forward (redo)

- Committed and non-committed data in files

- Roll back (undo)

- Committed data in files

TRAINING (ORA-9) - Different Stages while Opening an Oracle Database

Different Stages while Opening an Oracle Database

When Oracle software binaries tries to open an Oracle database, it passes through three different stages:

1.) Startup (nomount)
2.) Mount
3.) Open




High level requirements for opening an Oracle database:
> All control files must be present and synchronized
> All online data files must be present and synchronized
> At least one member of each redo log group must be present

Stage-1: Starting Up a Database (NOMOUNT)

Command:
SQL> startup nomount



Stage-2: Starting Up a Database (MOUNT)

Command:
SQL> startup mount
or
SQL> alter database mount



Stage-3: Starting Up a Database (OPEN)

Command:
SQL> startup
or
SQL> alter database open




High level requirements for keep an Oracle database running
Once open, the instance could fail with:
Loss of any control file
Loss of a data file belonging to the system or undo tablespaces
Loss of an entire redo log group. As long as at least one member of the group is available, the instance remains open.