Installation Guide for P6 Professional Primavera R15.1

About This Document

This document table about how to install and configure P6 Professional Primavera R15.1. Read this section to install P6 Professional. Run the Setup wizard on the client/desktop computers that will be used by project personnel. Install P6 Professional only after you install and configure the database server. The setup wizard needs to connect to the database server when install P6 Professional.

About Technical:

Database Client Software:

Before you install P6 Professional, first install the client software for the database you will be using. The database client software enables the client computer to connect over the network to the database on the server computer.

Note: Database client software is not required if your organization plans to use the P6 Pro Cloud Connect or the Primavera Compression Server driver type.

About Architecture:

Contents

Chapter 1: Download the software for P6 Professional R15.1

Download Oracle instance client for Windows

Download P6 Professional R15.1

Chapter 2: Installation the software

Setting Environment for Oracle instance client for Windows

Installation P6 Professional R 15.1

Chapter 3: Configuration Database for P6 Professional R15.1

Option 1: Configuration database via Oracle driver

Option 2: Configuration database via P6 Cloud Connect driver

Chapter 4: Login to P6 Professional R15.1

Chapter 5: Contact us

Chapter 1: Download the software for P6 Professional R15.1

Download Oracle instance client for Windows :

File name: instantclient-basic-nt-12.1.0.2.0.zip

Link download: http://www.vestco.ru/downloads/sibur/stg_oracle/instantclient-basic-nt-12.1.0.2.0.zip

Or: http://www.vestco.ru/downloads/sibur/stg_oracle/

Or: http://www.oracle.com/technetwork/topics/winx64soft-089540.html

Download P6 Professional R15.1:

File name: V75027-01.zip

You  download from https://edelivery.oracle.com

Step 1: Access https://edelivery.oracle.com

Step 2: Click Sign in / Register.  Enter username, password to login.

Step 3: Tick select button or box. Click Continue

Step 4: In Select a Project Pack, you choose Primavera Applications. In Platform, you choose your OS system. For example, my platform is Microsoft Windows x64 (64 bit). Then click Go.

Step 5: Select Primavera P6 Professional Project Management 15.1, Microsoft Windows

Step 6:  Download Primavera P6 Professional Applications 15.1 (V75027-01.zip) . Click Download

Primavera P6 Professional Applications 15.1

V75027-01

286M

Chapter 2: Installation the software

Setting Environment for Oracle instance client for Windows:

Step 1: Unzip file instantclient-basic-nt-12.1.0.2.0.zip

Step 2: Start à Computer, right mouse choose Properties

Step 3: Click Advanced system settings

Step 4: Click Environment Variables

Step 5: On System variables, insert value directory of instant client on step 1(E:\instantclient_12_1) into variable value of Path. Click OK.

 

Installation P6 Professional R 15.1:

Step 1: unzip file V75027-01.zip we have directory: P6_Pro_R151

Step 2: Run file setup.exe on P6_Pro_R151 directory

Step 3: Welcome Dialog appear. Click Next.

Step 4: Choose Setup Type. You choose Typical

Step 5: Click Install

Step 6: Database Configuration. You can click Next then do steps on Chapter 3 or Click Cancel and config later. I choose Cancel and config later.

Step 7: Click Finish

Chapter 3: Database Configuration for P6 Professional R15.1

Database Configuration step by step

Step 1: Start à Oracle – Primavera P6 à P6 Professional R15.1 à P6 Professional R15.1 Help & Tools à Database Configuration.

Step 2: Welcome window appear

Step 3: Click Next

 

Option 1: Configuration database via Oracle driver

Step 4a: Select or Create Alias

Step 5a: Configure Oracle Connection

Syntax: //{HOSTNAME}:{PORT}/{SID}

Step 6a: Enter Public Login Information ( contract administrator to get password)

Step 7a: Validata Database Connection. Click Next

Step 8a: Connection Successful of Fail

 

Option 2: Configuration database via P6 Cloud Connect driver

Step 4b: Select or Create Alias

Step 5b: Configure P6 Professional Cloud Connect Server

Database : {SID/Service}

URL: http://{HOSTNAME}:{PORT}/p6procloudconnect

Example: http://192.168.2.149:7001/p6procloudconnect

Step 6b: Connection Successful or Fail.

Chapter 4: Login to P6 Professional R15.1

Step 1: Start à Oracle- Primavera P6 à P6 Professional P6 à P6 Professional R 15.1

Step 2: Enter Username, Password, Database click …. Or click OK.

Step 3: (Optional) Select or Add or Configure Database Connections.

Step 4: After you login successfully, Main process appear.

Download the document:
https://drive.google.com/open?id=0B7a3DEnQ0-uzOWY4czdvclI1bHc

Check services running on port on linux

[oracle@ptud1 ~]$ netstat -an | grep "1521"
tcp        0      0 127.0.0.1:41247             127.0.0.1:1521              ESTABLISHED
tcp        0      0 :::1521                     :::*                        LISTEN     
tcp        0      0 ::ffff:192.168.2.156:50967  ::ffff:192.168.2.156:1521   ESTABLISHED
tcp        0      0 ::ffff:192.168.2.156:50971  ::ffff:192.168.2.156:1521   ESTABLISHED
tcp        0      0 ::ffff:192.168.2.156:50595  ::ffff:192.168.2.156:1521   ESTABLISHED
tcp        0      0 ::ffff:192.168.2.156:1521   ::ffff:192.168.2.156:50967  ESTABLISHED
tcp        0      0 ::ffff:127.0.0.1:1521       ::ffff:127.0.0.1:41247      ESTABLISHED
tcp        0      0 ::ffff:192.168.2.156:1521   ::ffff:192.168.2.156:50595  ESTABLISHED
tcp        0      0 ::ffff:192.168.2.156:1521   ::ffff:192.168.2.156:50971  ESTABLISHED
unix  2      [ ACC ]     STREAM     LISTENING     15211  /var/run/uuidd/request
unix  2      [ ACC ]     STREAM     LISTENING     205472 /var/tmp/.oracle/sEXTPROC1521

java.lang.OutOfMemoryError: PermGen space

On 64 bit platforms, the MaxPermSize should be set to 512M. Before launching the Installer, you can set the MaxPermSize in the environment as follows:
export _JAVA_OPTIONS=-XX:MaxPermSize=512m
If the MaxPermSize is not set to 512M, you will see the following error message:
java.lang.OutOfMemoryError: PermGen space

Ora-04031 Unable to allocate nn bytes of shared memory

1 ps -ef|grep oracle
2 find the smon and kill the pid for it
3 SQL> startup mount

ORACLE instance started.

Total System Global Area 4831838208 bytes Fixed Size 2027320 bytes Variable Size 4764729544 bytes Database Buffers 50331648 bytes Redo Buffers 14749696 bytes Database mounted. SQL>
4 SQL> alter system set shared_pool_size=100M scope=spfile;

System altered.
5 SQL> shutdown immediate

ORA-01109: database not open

Database dismounted. ORACLE instance shut down.
6 SQL> startup

ORACLE instance started.

Total System Global Area 4831838208 bytes Fixed Size 2027320 bytes Variable Size 4764729544 bytes Database Buffers 50331648 bytes Redo Buffers 14749696 bytes Database mounted. Database opened.
7 SQL> create pfile from spfile;

File created.

SOLVED

ORA-19809: limit exceeded for recovery files ORA-19804: cannot reclaim 35536384 bytes disk space from 4781506560 limit

Cause:

When use db_recovery_file_dest for archive log destination and the size given to it is full. Check both parameters using following command.

SQL> show parameter db_recovery_file_dest
NAME                                 TYPE        VALUE
------------------------------------ ----------- ------------------------------
db_recovery_file_dest                string      /test01/archive
db_recovery_file_dest_size           big integer 91G

Here 91G is allocated to db_recovery_file_dest which is at "/test01/archive" location. If this location is full up to 91G, it will start giving above errors.

Solution:

There are two ways for Database Administrator to solve this Problem.

Resize DB_Recovery_File_Dest_Size:

Increase the parameter db_recovery_file_dest_size, which is dynamic.

SQL> alter system set db_recovery_file_dest_size=XG; (larger amount)

This is only possible if you have enough free space on disk to increase the size of db_recovery_file_dest_size. Database Administrator has to check space on file system and then resize db_recovery_file_dest_size parameter accordingly. If Resize is not the option DBA can also Change Location of db_recovery_file_dest.

If Disk space doesn't have enough free space and resize is not an option then DBA has to Delete expired archive log files.

Delete Expired Archive log Files:

Delete unwanted archive log files and update rman repository. Delete old archive log files from db_recovery_file_dest using (rm/del) command on UNIX prompt.

Update RMAN Repository. Use following steps:

#[dba01] /home/oracle> export ORACLE_SID=test01
#[dba01] /home/oracle> rman target sys/sys

Recovery Manager: Release 11.2.0.1.0 - Production on Fri Jun 10 06:23:22 2011
Copyright (c) 1982, 2009, Oracle and/or its affiliates. All rights reserved.
connected to target database: TEST01 (DBID=2546571239)

RMAN> crosscheck archivelog all;

using target database control file instead of recovery catalog
allocated channel: ORA_DISK_1
channel ORA_DISK_1: SID=698 device type=DISK
allocated channel: ORA_DISK_2
channel ORA_DISK_2: SID=1030 device type=DISK
validation succeeded for archived log
archived log file name=/test01/archive/TEST01/archivelog/2011_06_10/o1_mf_1_26652_6z3s0r5o_.arc RECID=26789 STAMP=753427802
validation succeeded for archived log
archived log file name=/test01/archive/TEST01/archivelog/2011_06_10/o1_mf_1_26653_6z3t6b5x_.arc RECID=26790 STAMP=753429002
validation succeeded for archived log
RMAN> delete expired archivelog all;
using target database control file instead of recovery catalog
allocated channel: ORA_DISK_1
channel ORA_DISK_1: SID=699 device type=DISK
allocated channel: ORA_DISK_2
channel ORA_DISK_2: SID=689 device type=DISK
List of Archived Log Copies for database with db_unique_name TEST01
=====================================================================
Key Thrd Seq S Low Time
------- ---- ------- - ---------
26780 1 26650 X 10-JUN-11
Name: /test01/archive/TEST01/archivelog/2011_06_10/o1_mf_1_26650_6z3q5vmm_.arc
26781 1 26650 X 10-JUN-11
Name: /test01/archive/TEST01/archivelog/2011_06_10/o1_mf_1_26650_6z3q5vmm_.arc
26782 1 26650 X 10-JUN-11
Name: /test01/archive/TEST01/archivelog/2011_06_10/o1_mf_1_26650_6z3q5vmm_.arc
26786 1 26650 X 10-JUN-11
Name: /test01/archive/TEST01/archivelog/2011_06_10/o1_mf_1_26650_6z3q5vmm_.arc
26784 1 26650 X 10-JUN-11
Name: /test01/archive/TEST01/archivelog/2011_06_10/o1_mf_1_26650_6z3q5vmm_.arc
26785 1 26650 X 10-JUN-11
Name: /test01/archive/TEST01/archivelog/2011_06_10/o1_mf_1_26650_6z3q5vmm_.arc
26783 1 26650 X 10-JUN-11
Name: /test01/archive/TEST01/archivelog/2011_06_10/o1_mf_1_26650_6z3q5vmm_.arc

Do you really want to delete the above objects (enter YES or NO)? yes

/test01/archive/TEST01/archivelog/2011_06_10/o1_mf_1_26650_6z3q5vmm_.arc deleted.
-------------
------------
-------------
/test01/archive/TEST01/archivelog/2011_06_10/o1_mf_1_26650_6z3q5vmm_.arc deleted.

Now use below command in database to check for solution:

SQL> alter system switch logfile;
System altered.

If DBA is successfully able to switch log file, this means enough space is generated at db_recovery_file_dest_size location.

Read more: http://www.dbas-oracle.com/2011/06/ora-19809-limit-exceeded-for-recovery.html

ORA-00838: Specified value of MEMORY_TARGET is too small, needs to be at least 3072M – Oracle 12c

Cause: Existing MEMORY_TARGET value not enough to start database.
Solution: Increase MEMORY_TARGET value.

Consider following workaround:
[oracle@12c bin]$ sqlplus “/ as sysdba”
SQL*Plus: Release 12.1.0.1.0 Production on Mon Jun 9 11:15:45 2014
Copyright (c) 1982, 2013, Oracle. All rights reserved.
Connected to an idle instance.
SQL> startup
ORA-00838: Specified value of MEMORY_TARGET is too small, needs to be at least 3072M
// As we know spfile isn’t human readable or editable, create pfile from spfile. So that we able to change oracle system parameter. ( i.e. MEMORY_TARGET )
SQL> create pfile=’/tmp/pfile.bac’ from spfile;
File created.
// After file has created, change MEMORY_TARGET parameter value from pfile.
[oracle@12c ~]$ nano /tmp/pfile.bac
*.memory_target=3072M
// Start oracle database with newly updated pfile as follows.
[oracle@12c ~]$ sqlplus “/ as sysdba”
SQL*Plus: Release 12.1.0.1.0 Production on Mon Jun 9 11:24:56 2014
Copyright (c) 1982, 2013, Oracle. All rights reserved.
Connected to an idle instance.
SQL> startup pfile=/tmp/pfile.bac
ORACLE instance started.
Total System Global Area 3206836224 bytes
Fixed Size 2293496 bytes
Variable Size 1879048456 bytes
Database Buffers 1308622848 bytes
Redo Buffers 16871424 bytes
Database mounted.
Database opened.
// Create spfile from newly created pfile. As we are using spfile for our database.
SQL> create spfile from pfile=’/tmp/pfile.backup';
File created.
// Bounce the database after creating spfile to reflect changes in environment.
SQL> startup force;
ORACLE instance started.
Total System Global Area 3206836224 bytes
Fixed Size 2293496 bytes
Variable Size 1879048456 bytes
Database Buffers 1308622848 bytes
Redo Buffers 16871424 bytes
Database mounted.
Database opened.
// Ensure changes by following command.
SQL> show parameter memory_target
NAME TYPE VALUE
———————————— ———– ——————————
memory_target    big integer    3G

Cheers!! Now you are free to do your pending works
Read more : http://dbatricksworld.com/ora-00838-specified-value-of-memory_target-is-too-small-needs-to-be-at-least-3072m-oracle-12c/

ORA-00845: MEMORY_TARGET not supported on this system

This error pops up due to we are using Automatic Memory Management (AMM) feature of Oracle 11g R2 on shared memory filesystem (shmfs) which is found less than required.
Solutions for the mentioned error:

• Increase value of oracle parameter: ‘memory_max_target’ & ‘memory_target’ and try to startup database.
• If above not working than delete ‘memory_target’ parameter from parameter file & try to startup database.
• If above not working than increase ‘tmpfs’ space.

// Trying to startup oracle database:
[oracle@localhost ~]$ sqlplus “/ as sysdba”
SQL*Plus: Release 11.2.0.1.0 Production on Wed May 28 09:52:19 2014
Copyright (c) 1982, 2009, Oracle. All rights reserved.
Connected to an idle instance.
SQL> startup
ORA-00845: MEMORY_TARGET not supported on this system
// Ensure ‘tmpfs’ space available with the help of ‘df -h’ linux command:
[root@localhost ~]# df -h
Filesystem Size Used Avail Use% Mounted on
/dev/mapper/VolGroup-lv_root 18G 14G 3.3G 81% /
tmpfs 497M 255M 242M 52% /dev/shm
/dev/xvda1 485M 61M 400M 14% /boot
// Available space of ‘tmpfs’ is not enough to start oracle, Issue the following command to increase size of ‘tmpfs':
[root@localhost ~]# mount -t tmpfs shmfs -o size=3500m /dev/shm
// Ensure your changes by following:
[root@localhost ~]# df -h
Filesystem Size Used Avail Use% Mounted on
/dev/mapper/VolGroup-lv_root 18G 14G 3.3G 81% /
tmpfs 3.5G 0 3.5G 0% /dev/shm
/dev/xvda1 485M 61M 400M 14% /boot
shmfs 3.5G 0 3.5G 0% /dev/shm
// To make above changes persistence do edit your ‘/etc/fstab' file as follows:
cat  /etc/fstab
…
tmpfs          /dev/shm         tmpfs          size=3500m         0 0
…

// Startup database:
SQL*Plus: Release 11.2.0.1.0 Production on Wed May 28 10:05:45 2014
Copyright (c) 1982, 2009, Oracle. All rights reserved.
Connected to an idle instance.
SQL> startup
ORACLE instance started.
Total System Global Area 409194496 bytes
Fixed Size 2213856 bytes
Variable Size 310380576 bytes
Database Buffers 92274688 bytes
Redo Buffers 4325376 bytes
Database mounted.
Database opened.
Cheers!! Database has been opened successfully.

Read more: http://dbatricksworld.com/ora-00845-memory_target-not-supported-on-this-system/

MySQL - Resetting a lost MySQL root password

Not the Server root user

A common issue is confusing the Server root user with the MySQL root user.
The Server root user is the server's main user. The MySQL root user has complete control over MySQL only. The two 'root' users are not connected in any way.

Stop MySQL

The first thing to do is stop MySQL. If you are using Ubuntu or Debian the command is as follows:

sudo /etc/init.d/mysql stop

For CentOS, Fedora, and RHEL the command is:

sudo /etc/init.d/mysqld stop

Safe mode

Next we need to start MySQL in safe mode - that is to say, we will start MySQL but skip the user privileges table. Again, note that you will need to have sudo access for these commands so you don't need to worry about any user being able to reset the MySQL root password:

sudo mysqld_safe --skip-grant-tables &

Note: The ampersand (&) at the end of the command is required.

Login

All we need to do now is to log into MySQL and set the password.

mysql -u root

Note: No password is required at this stage as when we started MySQL we skipped the user privileges table.
Next, instruct MySQL which database to use:

use mysql;

Reset Password

Enter the new password for the root user as follows:

update user set password=PASSWORD("mynewpassword") where User='root';

and finally, flush the privileges:

flush privileges;

Restart

Now the password has been reset, we need to restart MySQL by logging out:

quit

and simply stopping and starting MySQL.

On Ubuntu and Debian:

sudo /etc/init.d/mysql stop
...
sudo /etc/init.d/mysql start

On CentOS and Fedora and RHEL:

sudo /etc/init.d/mysqld stop
...
sudo /etc/init.d/mysql start

Login

Test the new password by logging in:

mysql -u root -p

You will be prompted for your new password.

View more: http://www.rackspace.com/knowledge_center/article/mysql-resetting-a-lost-mysql-root-password

The command line help you fix Oracle error

Dear all!
Syntax: oerr ora [Code Err]
Example:
[oracle@ptud1 ~]$ oerr ora 838
00838, 00000, "Specified value of MEMORY_TARGET is too small, needs to be at least %sM"
// *Cause: The specified value of MEMORY_TARGET was less than the sum of the
// specified values for SGA_TARGET and PGA_AGGREGATE_TARGET.
// *Action: Set MEMORY_TARGET to at least the recommended value.

We think the command is very helpful for you
Thanks!

How to drop connected users in Oracle database

Solution 1:
sql>Shutdown immediate;
sql>startup restrict;
sql>drop user TEST cascade;
If you want to re-activate DB normally either reset the server or :
sql>Shutdown immediate;
sql>startup;

Solution 2: find the sessions for the users/schema , as a DBA use :

select sid,serial# from v$session where username = '<user_schema>'
Then kill them with :

 alter system kill session '<sid>,<serial#>'
Now Drop the user :  

drop user <user_schema_name> cascade;


Or: 
 select 'alter system kill session ''' || sid || ',' || serial# || ''';' from v$session where username = 'USER_SCHEMA';