Working with databases and new application installations can be really fun. Problem is, when there is a problem, everyone starts the blame game. Nothing unusual about that, part of an administrators job is to troubleshoot and prove where the problem starts. When dealing with external databases, there can be numerous problem, the firewall could be blocking, the local or remote port could be blocked on the system, or the database credentials could be incorrect. Testing for the last helps troubleshoot all of these. Ruling out the database connection helps focus the application administrator on the real problem! Testing a remote oracle database is pretty simple if you have the oracle client configured with tnsnames, etc. But if that isn’t necessary you may not have it configured. When you don’t this is the easiest way to test the database connection via the command line:
Prior to this make sure your ORACLE_HOME environment variable is set correctly. You may also need the LD_LIBRARY_PATH set to $ORACLE_HOME/lib.
Now that you are in you may want to check a few things out. To give you a quick reminder of the syntax here are a few to get the lay of the land:
To list all tables in a database (accessible to the current user):
SQL> select table_name from user_tables;
To list the contents of a specific table, type:
SQL> select * from name_of_table;