ODBC Set-Up: Oracle
To set up an Oracle Server DSN:
- Open the Windows Data Sources (ODBC) control panel:
- From the Start menu, choose Control Panel.
- On Windows 2000/XP/Vista, open the Administrative Tools folder.
- Double-click the Data Sources (ODBC) icon.
Generally in this format: [server address]:[port]/[Listener]
PowerSchool:
The [server address] is the ipaddress of your PowerSchool server.
The [port] should be: 1521.
The [Listener] is the name of the Oracle Listener: most likely PSProdDB
SASIxp:
The listener for SASIxp could be anything, the default listener is Listener, please contact your Oracle DBA for more information.
SchoolMAX:
Generally you will only need the service name for connecting to SchoolMAX. Consult your SchoolMAX documentation, or your Oracle DBA for more information.
Troubleshooting:
If after examining the error codes below you still cannot find your issue, please email our support department with your issue, and then try this website: Oracle Error Codes. Please be aware that this site is external to the discovery website.
Solution:
- Open the ODBC Data Source Administrator.
- Select the appropriate DSN. Click Configure
- Ensure that “Enable Query Timeout” is unchecked
- Click OK.
- Re-rerun the extraction, this error should not appear now.
This error occurs because the query for the requested information is taking a inordinate amount of time to return, so Oracle cancels the query.
Possible solutions:
- IP address of the TNS Listener may be incorrect
- Ensure local machine is connected to the network
- Ensure server machine is powered on and connected to the network
[Oracle][ODBC][Ora]ORA-12514: TNS:listener does not currently know of service requested in connect descriptor
![[Oracle][ODBC][Ora]ORA-12514: TNS:listener does not currently know of service requested in connect descriptor](http://media.discoverysoft.com/acorn/screenshots/odbc/errors/ORA-12514.png)
Possible solutions:
- IP address is correct (if any) but the Listener name is probably incorrect
- Ensure Listener is spelled correctly
- Ensure server machine has a listener set up
Possible solutions:
- Oracle administrator will need to ensure that the TNS Listener is running on the server
- This website has some good advice: http://www.dba-oracle.com/t_ora_12541_tns_no_listener.htm




![[Oracle][ODBC][Ora]ORA-01013: user requested cancel of current operation](http://media.discoverysoft.com/acorn/screenshots/odbc/errors/ORA-01013.png)
![[Oracle][ODBC][Ora]ORA-12170: TNS: Connect timeout occurred](http://media.discoverysoft.com/acorn/screenshots/odbc/errors/ORA-12170.png)
![[Oracle][ODBC][Ora]ORA-12541: TNS:no listener](http://media.discoverysoft.com/acorn/screenshots/odbc/errors/ORA-12541.png)