Error: "No Data Is Available Because Your P6 Username Is Not Valid For Connecting To The

Reporting Database" When Clicking On The Reports Tab in P6 R8.x Web Access [ID 1278903.1]
Applies to:
Primavera P6 Reporting Database - Version R2.1 and later
Primavera P6 Enterprise Project Portfolio Management - Version 8.0 and later
Information in this document applies to any platform.
Symptoms
The following error is encountered when clicking on the Reports tab in the P6 R8.x Web Access:
"No data is available because your P6 user name is not valid for connecting to the reporting database."
Cause
Depending on your current version, there are several potential causes for this error:

P6 R8.0
1.
2.
3.
4.
5.
6.
7.
8.
9.

The Reporting Database R2.1 has not been installed and configured with P6 R8.
The Reporting Database has been installed but the ETL process failed to complete successfully.
The Reporting Database has been installed but the Incremental process failed to complete successfully.
The P6 user has not been given access to the ODS schema.
The BI Publisher configuration in the Primavera P6 Administrator is incorrect.
The Java Application server was not restarted after changes were made to the BI Publisher configuration in
the Primavera P6 Administrator.
Using a cloned database or PMDB schema with existing Stage and ODS schemas,
The ODSUSER has not been granted the XMLP_ADMIN role within the ODS Schema (P6r8 only)
User access control (UAC) is preventing the application from being run with the highest level of privileges.

If using P6 R8.1 or later releases

1.
2.
3.
4.
5.
6.
7.

The BI Publisher configuration in the Primavera P6 Administrator is incorrect.

The Px Publication Services have not been configured
The P6 user has not been given Enterprise Reporting module access
The Java Application server was not restarted after changes were made to the BI Publisher configuration in
the Primavera P6 Administrator.
The P6 user does not exist in BI Publisher
User access control (UAC) is preventing the application from being run with the highest level of privileges.
BI Publisher has not been configured correctly in order to integrate with P6

To determine the true cause in your environment, the P6WebAccess.html log file should be reviewed to determine
the exception which is being logged when the reported error occurs accessing the Reports tab in P6. In the
P6WebAccess.html log file, search for an exception with the category name =
com.primavera.guisupport.reporting.JAXWSReportServiceWrapper
If you do not see any exceptions with a category =
com.primavera.guisupport.reporting.JAXWSReportServiceWrapper, it is possible the logging is being written to a
WARN level, and not an ERROR level. To ensure that you capture the excpetion causing the Reports tab failure, set
the logging level for P6 to the WARN level, and restart P6 to ensure the change takes effect. Then, reproduce the
issue from the P6 application, and review the log file again to determine the cause of your issue. For instruction to
configure the logging level of P6, please see: How To Set The Web Access HTML Log File Logging Level (Doc ID

898793.1)

Solution

If Using P6 R8.0
The Reporting Database R2.1 has not been installed and configured with P6 R8.0:
Install Reporting Database R2.1. Refer to the Reporting Database Administrator's Guide on Oracle Technology
Network for installation instructions.
The Reporting Database has been installed but the ETL process failed to complete successfully:
Review the ETLprocess.log (which can be found in %RDBHome%\p6rdb\log) and correct the errors. Then re-run the
runETL.bat (Windows platform) or runETL.sh (non-Windows platform).
The Reporting Database has been installed but the Incremental process failed to complete
successfully:
Review the Incremental.log (which can be found in %RDBHome%\p6rdb\log) and correct the errors. Then re-run the
incremental.bat (Windows platform) or incremental.sh (non-Windows platform).
The P6 user has not been given access to the ODS schema:
Use the following procedure to add a new user for the ODS:
1. Login to the P6
2. Assign the Enterprise Reports module to the P6 user that will be using the Reports feature within P6
3. On the machine where the Stage database resides, run one of the following files:

incremental.bat (on a Windows platform)

incremental.sh (on a non-Windows platform)

This file is in the <P6 Reporting home>\p6rdb for incremental directory. This adds the user to the ODS database,
creates Views for the user, and adds the user to Server Logins. When the ETL process or incremental.bat (or
incremental.sh for non-Windows systems) is run, a new database user will be created in the ODS instance.
The BI Publisher configuration in the Primavera P6 Administrator is incorrect:
The BI Publisher configuration in the Primavera P6 Administrator should look similar to the following:
Setting
Name

Description

Default
Value

Valid
Example
Values/Range

Server URL

The URL used to establish a

connection to the BI Publisher
web service from P6.

http://serverIP:port/BI Publisher
domain/services/PublicReportService_v11

Folder
Paths

The paths to the BI Publisher

folder where P6 will search for
reports.
Note: This setting is casesensitive and needs to match

/P6Reports

the folder name on the BI

Publisher server exactly.
Admin
Username

A BI Publisher web services

user name with administrative
privileges.

odsuser

Password

The password for the

administrative user name.

odsuser

Personal
Folders

Set to true to allow the use of

BI Publisher personal folders.

False

Cache
Timeout

Set how long cached report

definitions should appear.

1d

False/True

False
1d

For further information on the above configuration parameters, please refer to page 230-231 of the Administrator's
Guide for Oracle database users (page 226-227 of the Administrator's Guide for SQL Server users)
The Java Application Server service was not restarted after changes where made to the BI Publisher
configuration in the Primavera P6 Administrator:
If changes are made to the BI Publisher configuration within the Primavera P6 Administrator, you will need to restart
the Java Application server for the changes to take effect.
Using a cloned database or PMDB schema with existing Stage and ODS schemas
To resolve this, perform the following:
1.
2.
3.
4.
5.

Drop the stageuser and odsuser if applicable.

Drop the existing Stage and ODS tablespaces.
Recreate the Stage and ODS tablespaces (refer to the Reporting Database Administration
Guide for instructions).
Open a command prompt or terminal session and navigate to the p6rdb directory.
Run config.cmd (or sh) FULL to recreate the Stage and ODS schemas for the new or
cloned PMDB database.

The ODSUSER has not been granted the XMLP_ADMIN role within the ODS Schema (P6r8 only)
1.
2.

Log into the ODS schema (as SYSTEM)

Run the following query:
GRANT XMLP_ADMIN to ODSUSER;

User access control (UAC) is preventing the application from being run with the highest level of
privileges
1.

Start BI Publisher and P6 Web Access by right clicking on the shortcut to start the application and
selecting the option "Run as Administrator"
Even if you are logged in as an Administrator you should still perform these steps.

If Using P6 R8.1 or Later Releases

The BI Publisher configuration in the Primavera P6 Administrator is incorrect:

The BI Publisher configuration in the Primavera P6 Administrator should look similar to the following:
Setting
Name

Description

Defaul Valid
Example
t Value Values/Range

Server
URL

The URL used to

establish a
connection to the BI
Publisher web service
from P6.

Example format for WebLogic:

For 10g: http://serverIP:port/xmlpserver/services/PublicReportService_v11
For 11g: http://serverIP:port/xmlpserver/services/PublicReportService

Folder
Paths

The paths to the BI

Publisher folder
where P6 will search
for reports.
Note: This setting is
case-sensitive and
needs to match the
folder name on the
BI Publisher server
exactly.

/P6Reports

Admin
Username

A BI Publisher web
services user name
assigned to the BI
Administrator role.
This user must exist
in BI Publisher.

Administrator

Password

The password for the

administrative user
name.

password

Personal
Folders

Set to true to allow

the use of BI
Publisher personal
folders.

False

Cache
Timeout

Set how long cached

report definitions
should appear.

1d

Example format for WebSphere:

For 10g:
http://serverIP:port/xmlpserver/services/PublicReportService_v11?WSDL
For 11g: http://serverIP:port/xmlpserver/services/PublicReportService?WSDL

False/True

False

1d

For further information on the above configuration parameters, please refer to the following document, which is part
of the P6 EPPM r8.2 media pack: Connecting BI Publisher To P6. This documement can be used for both r8.1 and
r8.2.
The Px Publication Services have not been configured
Refer to Document 1324828.1 for instructions on how to configure the Px Publication Services
The P6 user has not been given Enterprise Reporting module access
1.
2.
3.
4.
5.
6.

Log into P6 as an Admin Superuser

Click Administer > User Access
Highlight the user
Click the Module Access tab at the bottom of the screen
Place a check in the Access column next to Enterprise Reporting
Save Changes

The Java Application server was not restarted after changes were made to the BI Publisher
configuration in the Primavera P6 Administrator
If changes are made to the BI Publisher configuration within the Primavera P6 Administrator, you will need to restart
the Java Application server for the changes to take effect.
The The P6 user does not exist in BI Publisher
1.
2.
3.
4.
5.
6.
7.
8.

Log into BI Publisher as Administrator

Select the Admin tab
Under Security Center, click Users
Click Create User
Enter Username and Password, i.e. user1
Click Apply
Click Assign Roles next to the new user
Assign the P6Reports role and click Apply

User access control (UAC) is preventing the application from being run with the highest level of
privileges.
Start BI Publisher and P6 Web Access by right clicking on the shortcut to start the application and selecting the
option "Run as Administrator". Even if you are logged in as an Administrator you should still perform these steps.
BI Publisher has not been configured correctly in order to integrate with P6

How To Configure P6 R8.1 Enterprise Reporting With BI Publisher 10g (Oracle): Doc ID
1328054.1

How To Configure P6 R8.1 Enterprise Reporting With BI Publisher 10g (SQL): Doc ID 1328422.1

How To Configure P6 R8.1 Enterprise Reporting With BI Publisher 11g (Oracle and SQL): Doc ID
1337940.1