Skip to end of metadata
Go to start of metadata


I. Firewall Access

  1. Request EPMPROD/QNYEPM03/EPMNY01P/EPMTEST firewall access by emailing or
    1. Include the IP address of your work PC.
  2. Make sure that all entries are up to date in the tnsnames.ora and sqlnet.ora files.
  3. The files should reside in the Oracle folder:

  4. Test the connections using telnet:
    1. Type "cmd" in the Start window and hit Enter;
    2. Type the following commands at the cmd line. Each command should be typed individually:
      1. telnet 1530
        telnet 1531
        telnet 1533
        telnet 1533

      2. A successful connection will look like the sample screen below:

If you encounter connection problems, follow the instruction in the PDF document attached below:



II.  Update TNS Entries





Below in red is listed the tnsnames entry for UDW+ (EPMNY01P) which you will need to add to your Oracle client tnsnames.ora file.  The location of your tnsnames.ora file may be in the following (or similar) path: C:\Oracle\product\11.2.0\client_1\network\admin



    (ADDRESS = (PROTOCOL = TCP)(HOST = = 1531))
You may or may not need the ".WORLD" suffix in the entry above depending on whether that exists in all your other entries.
2. Interactive Reporting (Brio) .OCE:
Attached is an .oce file I created locally to connect to UDW+ (EPMNY01P).  I have also published the .oce to the Interactive Reporting (Brio) portal so you can select it from the list when publishing relevant BQYs.


3. Testing Your Connection:


  1. Click on your Start menu icon.
  2. Type "cmd" and [Enter]
  3. A command window will open. Type "tnsping" and the name of the database you want to test your connection to. The name should match the entry in your tnsnames.ora file entry (eg. "tnsping epmny01p").
  4. Wait a few seconds for a response. If successful, you will get a text message "....Attempting to contact..." that will end with "OK". See example below.



Used TNSNAMES adapter to resolve the alias
 Attempting to contact (DESCRIPTION= (ADDRESS= (PROTOCOL=TCP) (HOST=webprod-scan. (PORT=1531)) (CONNECT_DATA= (SERVER=dedicated) (SERVICE_NAME=we
 OK (30 msec)


III.  Updating your Queries


Note on joining a Interactive Reporting (Brio) query to UDW+ for the first time 

  • Select DataModel ->Synch with Database.  
  • This will let you know of any columns or any tables in which the names might have changed so that you can update your query accordingly and decide if you want to synch or wait.

Regardless of the tool that you are using today to create your Student Records queries, the following considerations must be taken into account:


UDW+ version of Student Records EPM contains the following enhancements:

  1. Use D_Person or D_Student to replace NYU_D_Person
    1. D_Student
      1.  has everything as D_person
      2. D_Student joins to the Student _SId
      3. In general, if your existing queries leverage NYU_D_Person, you should swith to D_Student
    2. D_Person 
      1. is a conformed dimension that is used throughout the warehouse
      2. D_Person joins on a Fact to the Person_SID
      3. In general, use of D_Person is specific to joining Person information across Student, HR and UDM data marts
  2. Reporting Department - use this to group schools and departments consistently accross different areas.  This is centrally updated by NYU Office of Institutuional Research.
  3. HR Instructor Data - Instructor Dimension has been enriched with data Job data elements from the HR data mart
  4. Full CPP Stack (Grain change on all Subject Areas due to multiple Plans/Subplans) - Queries will now need to be filtered on Primary Plan = Y if you wish to limit to only the primary plan for each student.
  5. All Class Instructors (Grain Change on Class Enrollment) - The instructor dimension contains all intstructors for a given course; limit to Primary Instructor Flag = Y  to refine your result set to 1 record per class.
  6. Test Score Data is now available

Key Point:  All tables that exist in EPM Prod also exist in UDW+


  • No labels