Versions Compared


  • This line was added.
  • This line was removed.
  • Formatting was changed.


  1. Purpose

  2. Support

  3. Additional Resources


1. Purpose – The purpose of this page is to provide users who are experiencing direct connection problems with various, thorough instructions to solve their specific issue. 


2. Instructions – 

  • Update TNS Entries: 

    1. TNSNames Entry: For instruction on how to update and test your TNS file please go here. 
      • PSDBKB01_NEW.
        world = 
           (DESCRIPTION = 
             (ADDRESS_LIST = 
               (ADDRESS = 
                 (PROTOCOL = TCP)
                 (HOST =
                 (PORT = 1531)
             (CONNECT_DATA =


               (SERVICE_NAME =

    2. Interactive Reporting (Brio) .OCE: We have also published the .oce to the Interactive Reporting (Brio) portal so you can select it from the list when publishing relevant BQYs.  The oce file can be found in the root\catalog extensions folder and the bqy in the root\Data Gateway folder. 

    3. Testing Your Connection: 
      1. Click on your Start menu icon. 
      2. Type "cmd" and click Enter.
      3. A command window will open. Type "tnsping" and the name of the database that you wish to test your connection to. The name should match the entry in your tnsnames.ora file entry (e.g. "tnsping epmny01p"). 
      4. Please wait a few seconds for a response. If successful, you will recieve a message that reads "...attempting to contact..." which 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)



  • Updating Your Queries: 

    1. Joining an Interactive Reporting (Brio) Query to UDW+ for the First Time: Please select DataModel ---> Synch with Database. This will notify you of any columns or tables in which the names might have changed so that you may update your query accordingly and decide whether to synch or wait. 

    2. Considerations for Creating Student Records Queries: Regardless of the tool that you are using to create your student records queries, the following considerations must be taken into account:
      • 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_Sld
          3. In general, if your existing queries leverage NYU_D_Person, you should switch 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/
      • Reporting Department – Use this to group schools and departments consistently across different areas. This is centrally updated by NYU Office of Institutional Research.
      • HR Instructor Data – Instructor dimension has been enriched with data job data elements from the HR data mart.
      • 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.
      • All Class Instructors (Grain Change on Class Enrollment) – The instructor dimension contains all instructors for a given course. Limit to Primary Instructor Flag = Y to refine your result set to one record per class.
      • Test score data is now available. 
      • Note – All tables that exist in EPM Prod also exist in UDW+.